Database to RFC scenerio.

Hi all,
I am working on a scenario where in my sender is a database(SQL) and receiver is SAP system(BAPI).
1. On the sender side i have to pick data fron 5 database tables,for which a stored procedure needs to be written, kindly help me on this.
2. Since receiver is a RFC it cannot receive batch data how should i go about it.

Could you please elaborate on this
Thank you,

Similar Messages

  • Problem in FILE to RFC scenerio

    Hi,
    I am working on File to RFC Scenerio
    I am getting a problime in Communication channel (Sender).
    The problem is coming in File COntent Conversion
    Parameters are like
    Documenet name : MT_ROXY ( ->Header -> EMPNO
                                                                 -> EMPNAME
                                                                 -> DEPTNAME)
    Recordset Name: Details
    Recordset str     : HEADER,*
    Recordset Seq   : Variable
    " per message   :*
    Conersion Params:
    ignoreRecordsetName  : True
    HEADER.addHeaderLine : 0
    HEADER.fieldSeperator: ,
    HEADER.endSeperator: 'nl'
    HEADER.fieldFixedLengths : 12,40,40
    HEADER.fieldNames          :EMPNO,EMPNAME,DEPARTMENTNAME
    HEADER.lastFieldsOptional : YES
    Problem:The message content i am getting is like
    <ns:MT_ABAPPROXY>
    &#8722;
         <HEADER>
    <EMPNO>IT,Munish,22</EMPNO>
    </HEADER>
    &#8722;
         <HEADER>
    <EMPNO>IP,Munish1,2</EMPNO>
    </HEADER>
    &#8722;
         <HEADER>
    <EMPNO>IS,Munish2,2</EMPNO>
    </HEADER>
    &#8722;
         <HEADER>
    <EMPNO>IQ,Munish3,2</EMPNO>
    </HEADER>
    &#8722;
         <HEADER>
    <EMPNO>IR,Munish4,2</EMPNO>
    </HEADER>
    </ns:MT_ABAPPROXY>
    as  it does not dividing the Fields by ,
    as it shud come like
    <EMPNO>IR,2</EMPNO>
    <EMPNAME>Munish5</EMPNAME>?
    <DEPARTMENTNAME>2</DEPARTMENTNAME>
    but its not taking the other 2 filds and not separating by , sepreator,
    Kindly guide me in solving this problem on urgent basis
    Thanks in Advance
    Munish SIngh

    HI,
    Then use only fieldSeparator see the spelling it should be in proper case.
    refer the below weblog for more information:
    /people/venkat.donela/blog/2005/06/08/how-to-send-a-flat-file-with-various-field-lengths-and-variable-substructures-to-xi-30
    Also refer the file FCC parameters.
    http://help.sap.com/saphelp_nw04/helpdata/en/e3/94007075cae04f930cc4c034e411e1/frameset.htm
    Thnx
    Chirag

  • Problem in Picking the file in  FTP to RFC Scenerio

    Hi,
    I am using FTP to RFC scenerio, i have a CSV file and need to use file Content COnversion at the sender Communication Channel. But its not picking up the file from my  FTP..
    My data is like
    11    Munish     IT
    My Message Type is like :
    MT_ABAPPROXY ->
                 HEADER    ->>
                                    Empno
                                    Empname
                                    Departmentname
    My Communication channel is like this..
    Transport Protocol:FTP
    Message Protocol:FIle COntent COnversion
    SOurce Directory : /
    File name:            file.csv
    then Server name and port is corrwctly configured
    My messe Content COnversion is like this
    Doc Name:MT_ABAPPROXY
    Namespace:http://www.munnamespace.com
    Recordsetname:Details
    Rec Str :            HEADER,*
    HEADER.fieldSeperator     ','
    HEADER.fieldNames    Empno,Empname,Departmenname
    HEADER.lastFieldsOptional   YES
    HEADER.fieldFixedLengths    12,24,24
    ignoreRecordsetName         true
    HEADER.endSeperator     'nl'
    But it is unable to pick the file , but if i wont use file conten conversion , it picks but it has no use as the date is not in XML
    SO kindly help me in solving this as the problem is mostly in File COnetent Conversion
    Thanks
    Munish SIngh

    Hi arvind,
    thankd for the reply,
    i have done the same what u said but i am getting this error in communcation channel monitoring (RWB)
         Conversion of file content to XML failed at position 0: java.lang.Exception: ERROR converting document line no. 1 according to structure 'HEADER':java.lang.Exception: Consistency error: field(s) missing - specify 'lastFieldsOptional' parameter to allow this

  • Mapping problem on CSV to RFC scenerio

    Hi all,
    I am implementing an CSV to RFC scenerio on SAP XI 3.0, but stuck on a mapping issue. Please find the message, below;
    com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:Z_READ_CSV. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:357) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:60) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at ...
    I do not face any kind of error on mapping test and see the source and result documents, below;
    Source;
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_Csv xmlns:ns0="http://com.sap.astron/tekkasa">
       <mydoc>
          <itemList>
             <items>
                <fld1>1</fld1>
                <fld2>2</fld2>
                <fld3>3</fld3>
             </items>
             <items>
                <fld1>4</fld1>
                <fld2>5</fld2>
                <fld3>6</fld3>
             </items>
          </itemList>
       </mydoc>
    </ns0:MT_Csv>
    Result:
    <?xml version="1.0" encoding="UTF-8"?>
    <ns1:Z_READ_CSV xmlns:ns1="urn:sap-com:document:sap:rfc:functions"><ITAB_ZCSV><item><FLD1>1</FLD1><FLD2>2</FLD2><FLD3>3</FLD3></item><item><FLD1>4</FLD1><FLD2>5</FLD2><FLD3>6</FLD3></item></ITAB_ZCSV></ns1:Z_READ_CSV>
    It is interesting that I see the message in payload, below;
    <?xml version="1.0" encoding="utf-8"?>
    <mydoc>
    <itemList>
         <items>
              <fld1>1</fld1>
              <fld2>2</fld2>
              <fld3>3</fld3>
         </items>
         <items>
              <fld1>4</fld1>
              <fld2>5</fld2>
              <fld3>6</fld3>
         </items>
    </itemList>
    </mydoc>
    Anyone has a suggestion about the problem? Thank you very much.

    Hi Shabarish;
    I pasted  complete output, below. I would be very appreciated, if you could suggest a solution. Thank you.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?><!-- Request Message Mapping --> <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30"><SOAP:Header><SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7"><SAP:MessageClass>ApplicationMessage</SAP:MessageClass><SAP:ProcessingMode>asynchronous</SAP:ProcessingMode><SAP:MessageId>977D6A50-91B1-11DC-A122-00145E6896FD</SAP:MessageId><SAP:TimeSent>2007-11-13T06:28:05Z</SAP:TimeSent><SAP:Sender><SAP:Service>GarantiTekKasaFtp</SAP:Service><SAP:Interface namespace="http://com.sap.astron/tekkasa">MI_Outbound_Async</SAP:Interface></SAP:Sender><SAP:Receiver><SAP:Party agency="" scheme=""/><SAP:Service>B3T003</SAP:Service><SAP:Interface namespace="urn:sap-com:document:sap:rfc:functions">Z_READ_CSV</SAP:Interface><SAP:Mapping notRequired="M"><SAP:ObjectId>5bz79NusOaWn/LbMSmdpTA==</SAP:ObjectId><SAP:SWCV>rsCz8ZEJEdycocVZCkEBQg==</SAP:SWCV><SAP:SP>-1</SAP:SP></SAP:Mapping></SAP:Receiver><SAP:Interface namespace="http://com.sap.astron/tekkasa">MI_Outbound_Async</SAP:Interface></SAP:Main><SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService></SAP:ReliableMessaging><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand=""><SAP:Category>Application</SAP:Category><SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code><SAP:P1>com/sap/xi/tf/_MM_CSV_</SAP:P1><SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2><SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>During the application mapping com/sap/xi/tf/_MM_CSV_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformatio~
    </SAP:Stack><SAP:Retry>M</SAP:Retry></SAP:Error><SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Hop timeStamp="2007-11-13T06:28:05Z" wasRead="false"><SAP:Engine type="AE">af.yxi.yxint01</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter><SAP:MessageId>977D6A50-91B1-11DC-A122-00145E6896FD</SAP:MessageId><SAP:Info/></SAP:Hop><SAP:Hop timeStamp="2007-11-13T06:28:05Z" wasRead="false"><SAP:Engine type="IS">is.00.yxint01</SAP:Engine><SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter><SAP:MessageId>977D6A50-91B1-11DC-A122-00145E6896FD</SAP:MessageId><SAP:Info>3.0</SAP:Info></SAP:Hop></SAP:HopList><SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><SAP:Date>20071113</SAP:Date><SAP:Time>082805</SAP:Time><SAP:Host>yxint01</SAP:Host><SAP:SystemId>YXI</SAP:SystemId><SAP:SystemNr>00</SAP:SystemNr><SAP:OS>Windows NT</SAP:OS><SAP:DB>ORACLE</SAP:DB><SAP:Language/><SAP:ProcStatus>014</SAP:ProcStatus><SAP:AdapterStatus>000</SAP:AdapterStatus><SAP:User>XIAFUSER</SAP:User><SAP:TraceLevel>1</SAP:TraceLevel><SAP:Logging>1</SAP:Logging><SAP:LogSeqNbr>006</SAP:LogSeqNbr><SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr><SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal><SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal><SAP:PipelineElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineElementId><SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId><SAP:PipelineService>PLSRV_MAPPING_REQUEST</SAP:PipelineService><SAP:QIdInternal>XBTO6___0002</SAP:QIdInternal><SAP:CommitActor>X</SAP:CommitActor><SAP:SplitNumber>0</SAP:SplitNumber><SAP:NumberOfRetries>0</SAP:NumberOfRetries><SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries><SAP:TypeOfEngine client="294">CENTRAL</SAP:TypeOfEngine><SAP:PlsrvExceptionCode/><SAP:EOReferenceRuntime type="TID">0A4101420318473943F5015F</SAP:EOReferenceRuntime><SAP:EOReferenceInbound type="TID"/><SAP:EOReferenceOutbound type="TID"/><SAP:MessageSizePayload>234</SAP:MessageSizePayload><SAP:MessageSizeTotal>2690</SAP:MessageSizeTotal><SAP:PayloadSizeRequest>234</SAP:PayloadSizeRequest><SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap><SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse><SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap><SAP:Reorganization>INI</SAP:Reorganization><SAP:AdapterInbound>AENGINE</SAP:AdapterInbound><SAP:InterfaceAction>DEL</SAP:InterfaceAction><SAP:RandomNumber>06</SAP:RandomNumber><SAP:AckStatus>000</SAP:AckStatus><SAP:SkipReceiverDetermination/><SAP:Sender_Agreement_GUID>E8E1DEF39D603F158F70394833EF0ADE</SAP:Sender_Agreement_GUID><SAP:Serialize_Children>X</SAP:Serialize_Children></SAP:RunTime><SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30"><SAP:RunTimeItem><SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name><SAP:Timestamp type="begin" host="yxint01">20071113062805.39</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name><SAP:Timestamp type="end" host="yxint01">20071113062805.406</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name><SAP:Timestamp type="begin" host="yxint01">20071113062805.406</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name><SAP:Timestamp type="end" host="yxint01">20071113062805.406</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name><SAP:Timestamp type="begin" host="yxint01">20071113062805.406</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name><SAP:Timestamp type="end" host="yxint01">20071113062805.515</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name><SAP:Timestamp type="begin" host="yxint01">20071113062805.515</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name><SAP:Timestamp type="end" host="yxint01">20071113062805.531</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name><SAP:Timestamp type="begin" host="yxint01">20071113062805.531</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name><SAP:Timestamp type="end" host="yxint01">20071113062805.531</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name><SAP:Timestamp type="begin" host="yxint01">20071113062805.546</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name><SAP:Timestamp type="end" host="yxint01">20071113062805.546</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name><SAP:Timestamp type="begin" host="yxint01">20071113062805.546</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name><SAP:Timestamp type="end" host="yxint01">20071113062805.64</SAP:Timestamp></SAP:RunTimeItem><SAP:RunTimeItem><SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name><SAP:Timestamp type="begin" host="yxint01">20071113062805.64</SAP:Timestamp></SAP:RunTimeItem></SAP:PerformanceHeader><SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:TraceLevel>Information</SAP:TraceLevel><SAP:Logging>Off</SAP:Logging></SAP:Diagnostic><SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30"><Trace level="1" type="T">Party normalization: sender </Trace>
    <Trace level="1" type="T">Sender scheme external = XIParty</Trace>
    <Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
    <Trace level="1" type="T">Sender party external = </Trace>
    <Trace level="1" type="T">Sender party normalized = </Trace>
    <Trace level="1" type="T">Party normalization: receiver </Trace>
    <Trace level="1" type="T">Receiver scheme external = </Trace>
    <Trace level="1" type="T">Receiver agency external = </Trace>
    <Trace level="1" type="T">Receiver party external = </Trace>
    <Trace level="1" type="T">Receiver party normalized = </Trace>
    <Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST"></Trace><!-- ************************************ -->
    <Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
    <Trace level="1" type="T">COMMIT is done by XMB ! </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE">
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
    </Trace>
    <Trace level="1" type="T">**************************************************** </Trace>
    <Trace level="1" type="T">*                                                  * </Trace>
    <Trace level="1" type="T">*                                                  * </Trace>
    <Trace level="1" type="T">XMB entry processing </Trace>
    <Trace level="1" type="T">system-ID = YXI</Trace>
    <Trace level="1" type="T">client = 294</Trace>
    <Trace level="1" type="T">language = E</Trace>
    <Trace level="1" type="T">user = XIAFUSER</Trace>
    <Trace level="1" type="Timestamp">2007-11-13T06:28:05Z CET  </Trace>
    <Trace level="1" type="T">*                                                  * </Trace>
    <Trace level="1" type="T">*                                                  * </Trace>
    <Trace level="1" type="T">**************************************************** </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE"></Trace><!-- ************************************ -->
    <Trace level="1" type="T">Message-GUID = 977D6A5091B111DCA12200145E6896FD</Trace>
    <Trace level="1" type="T">PLNAME = CENTRAL</Trace>
    <Trace level="1" type="T">QOS = EO</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC"></Trace><!-- ************************************ -->
    <Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
    </Trace>
    <Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
    <Trace level="1" type="T">Queue name : XBTI0002</Trace>
    <Trace level="1" type="T">Generated prefixed queue name = XBTI0002</Trace>
    <Trace level="1" type="T">Schedule message in qRFC environment </Trace>
    <Trace level="1" type="T">Setup qRFC Scheduler OK! </Trace>
    <Trace level="1" type="T">----
    </Trace>
    <Trace level="1" type="T">Going to persist message </Trace>
    <Trace level="1" type="T">NOTE: The following trace entries are always lacking </Trace>
    <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST </Trace>
    <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC </Trace>
    <Trace level="1" type="T">Async barrier reached. Bye-bye ! </Trace>
    <Trace level="1" type="T">----
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
    </Trace>
    <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
    <Trace level="1" type="B" name="SXMS_ASYNC_EXEC"></Trace><!-- ************************************ -->
    <Trace level="1" type="T">----
    </Trace>
    <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
    <Trace level="1" type="T">system-ID = YXI</Trace>
    <Trace level="1" type="T">client = 294</Trace>
    <Trace level="1" type="T">language = E</Trace>
    <Trace level="1" type="T">user = XIAFUSER</Trace>
    <Trace level="1" type="Timestamp">2007-11-13T06:28:05Z CET  </Trace>
    <Trace level="1" type="T">----
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></Trace><!-- ************************************ -->
    <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
    </Trace>
    <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
    <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
    <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N </Trace>
    <Trace level="1" type="T"> Cache Content is up to date </Trace>
    </Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
    </Trace>
    <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">
    <Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N </Trace>
    <Trace level="1" type="T"> Cache Content is up to date </Trace>
    </Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
    </Trace>
    <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV"></Trace><!-- ************************************ -->
    <Trace level="1" type="T">number of receivers: 1 </Trace>
    <Trace level="1" type="T">Single-receiver split case </Trace>
    <Trace level="1" type="T">Post-split internal queue name = XBTO6___0002</Trace>
    <Trace level="1" type="T">----
    </Trace>
    <Trace level="1" type="T">Persisting single message for post-split handling </Trace>
    <Trace level="1" type="T"> </Trace>
    <Trace level="1" type="T">Going to persist message + call qRFC now... </Trace>
    <Trace level="1" type="T">NOTE: The following trace entries are always lacking </Trace>
    <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST </Trace>
    <Trace level="1" type="T">Async barrier reached. Bye-bye ! </Trace>
    <Trace level="1" type="T">----
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
    </Trace>
    <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
    <Trace level="1" type="B" name="SXMS_ASYNC_EXEC"></Trace><!-- ************************************ -->
    <Trace level="1" type="T">----
    </Trace>
    <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
    <Trace level="1" type="T">system-ID = YXI</Trace>
    <Trace level="1" type="T">client = 294</Trace>
    <Trace level="1" type="T">language = E</Trace>
    <Trace level="1" type="T">user = XIAFUSER</Trace>
    <Trace level="1" type="Timestamp">2007-11-13T06:28:05Z CET  </Trace>
    <Trace level="1" type="T">----
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></Trace><!-- ************************************ -->
    <Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID">
    </Trace>
    <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
    <Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
    <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace><!-- ************************************ -->
    <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV"></Trace><!-- ************************************ -->
    <Trace level="1" type="T">Interface Mapping http://com.sap.astron/tekkasa IM_CSV </Trace>
    <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_MM_CSV_ </Trace>
    <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:Z_READ_CSV. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
         at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:357)
         at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:60)
         at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105)
         at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64)
         at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91)
         at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90)
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95)
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68)
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79)
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
         at $Proxy186.processFunction(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:100)
         at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113)
         at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Root Cause:
    com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns1:Z_READ_CSV. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
         at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:212)
         at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:352)
         at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:60)
         at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105)
         at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64)
         at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91)
         at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90)
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95)
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68)
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79)
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
         at $Proxy186.processFunction(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:100)
         at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113)
         at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    </Trace>
    <Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_CSV_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:Z_READ_CSV. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd </Trace>
    <Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_CSV_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:Z_READ_CSV. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
         at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73)
         at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91)
         at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90)
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95)
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68)
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79)
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
         at $Proxy186.processFunction(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:100)
         at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113)
         at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Root Cause:
    com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns1:Z_READ_CSV. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
         at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:357)
         at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:60)
         at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105)
         at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64)
         at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91)
         at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90)
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95)
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68)
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79)
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
         at $Proxy186.processFunction(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:100)
         at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113)
         at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Root Cause:
    com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns1:Z_READ_CSV. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
         at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:212)
         at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:352)
         at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:60)
         at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105)
         at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64)
         at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91)
         at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90)
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95)
         at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68)
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79)
         at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187)
         at $Proxy186.processFunction(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:324)
         at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:100)
         at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequestInternal(RFCJCOServer.java:113)
         at com.sap.engine.services.rfcengine.RFCJCOServer$ApplicationRunnable.run(RFCJCOServer.java:171)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    </Trace>
    <Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
    </Trace>
    <Trace level="1" type="System_Error">Error exception return from pipeline processing! </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST"></Trace><!-- ************************************ -->
    </SAP:Trace></SOAP:Header><SOAP:Body><SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7"><SAP:Payload xlink:href="cid:[email protected]"><SAP:Name>MainDocument</SAP:Name><SAP:Description/><SAP:Type>Application</SAP:Type></SAP:Payload></SAP:Manifest></SOAP:Body></SOAP:Envelope>

  • File to RFC Scenerio in PI 7.1

    Hi Experts,
    Please provide any documents for File to RFC Scenerio in PI 7.1

    The procedure is the same as it was in SAP PI7.0 or lower versions.....no major change on this front.
    Search SDN for documents related to your protocol.
    Regards,
    Abhishek.

  • File 2 RFC scenerio

    Mine is a File toXI to  RFC scenerio.
    File in DAT format  is picked up fro FTP and send to XI. XI further sends it to BI server through RFC adapter. The thing is due to some reasons I hav deliberately entered wrong data  uid and password]  for XI to BI connection in sm59 and in the RFC adapter. Initially just wished to see wether the data movement between File aServer to XI takes place properly.
    Activated the components and carried out the Tools - Test Configuration.
    It is giving following error:
    Receiver Agreement
    More over when ever I place the file in the specified soure path ....I don see any RESULTS IN sxmb_moni or messege monitoring .
    But Communication channel monitoring shows GREEN for file adapter.
    My query is if sender  File adapter is green and polling, why do i not see the same in messee monitoring and sxmb_moni.
    Pls comment.
    Pls revert back if anything is not clear.

    Hi,
    just for check - in ID in sender file comm channel, set mode to delete and see if your test file in source directory is getting deleted.........if it is deleted, then in comm chnnel monitoring, you will get yur msg and also in SXMB_MONI...........if the file is not deleted, then check for file permissions to pick the file..
    Regarding your No receiver agreement found error, in ID just create the reciver agreement for your sneder system, reciver sytem, receiver interface namespace data.............activate it and restart your msg in SXMB_MONI.
    Regards,
    Rajeev Gupta

  • SOAP to RFC Scenerio: HTTP 500: Internal Server Error

    Hi Experts,
        I am facing HTTP 500:Internal server Error. We have SOAP to RFC Scenerio. Interface is working fine, suddenly we are facing this error in Interface. On XI server side - ABAP and JAVA stack are on same Service Pack(SP 13). There is no change done in WSDL and RFC Structure and Mapping side.
    Please suggest to resolve this Issue.

    Hi Subbu,
       I have found this error in adapter monitoring??..  Please find my finding of XI server related to this below:--
    *Error categaory - XI_J2EE_MESSAGING_SYSTEM
    Error Code - CALL_ CONSUMER _ERROR
    Error :Returning synchornous error notification to calling application:com.sap.aii.af.ra.ms.api.RecoverableException: RecievedHTTP Response code 500:internal Server Error.*
       I have refresh the cache already, but problem still exists.
       Please suggest how to resolve this error.

  • RFC scenerio

    Hello All,
    I have simple scenerio SAP(RFC) ---> PI ---> Webservice
    this is a sync scenerio. RFC is sending a request to webservice in return we are reciving some data which needs to go to RFC.
    RFC will store this data in Ztable
    We have done all configuration only problem we are facing is
    Request is going sucessully even we are receiving response from webservice and We can see in sxmb_moni response from webserv and after mapping how this is going in RFC structure.
    Problem is SAP side we are not receiving this data mens table is not getting updated.can anyone point out where problem can be.
    Regards,
    Vikrant

    Hi Vikrant,
    --> Map the response field of the webservice to the response filed of the RFC.
    --> I think you had done the two mapping programs in your IR one is for the request and the other is for the response.
    --> After getting the response from the webservice it should get hold by the response filed of the RFC and insert the filed value in to the db table.
    Thanks

  • Isssue in File To RFC Scenerio

    Hi Experts,
       I am sending a .DAT  file to R/3 using PI.
       File gets successfully picked up from FTP into PI. But sxmb_moni is not showing any error messeges, nothing. In fact I know this is a perfectly OK file as few days ago it was successfully processing the same file, without errorrs.
      I hav checked in messege monitering and got the following error.
    Error Category XI_J2EE_ADAPTER_XI_HANDLER
    Error Code GENERAL_ERROR
    Received XI system error.error Code:SLD_NO_OWN_BS Error Text:Error Stack:error while reading ID of own business system from the SLd for system RXT and client 001 Internal error in Landscape Directory.                
    I hav checked the LOG in SLD and got the fllowing error.
    #1470 03/10/2009 15:00:49.918 [SAPEngine_Application_Thread[impl:3]_18] WARNING com.sap.lcr.cimsrv.ChangePasswordServlet: Password change required for automated client. Please ensure that service client users don't have initial passwords. Alternatively, logon to the SLD user interface with the corresponding user and assign a new password. After the password has been changed, client settings must be updated accordingly.
    I hav done no changes in any where,, no password change or no craetion of new client. This scenerio was working ok, but all of a sudden it started giving this strage issue. Only hint I can giv is,, the file size is some where around 2.5mb,, and i believe this is NOT a constraint..but may be I can be wrong.
    Please comment experts.
    Regards,
    Arnab .

    Hi! Arnab,
    com.sap.lcr.cimsrv.ChangePasswordServlet: Password change required for automated client. Please ensure that service client users don't have initial passwords. Alternatively, logon to the SLD user interface with the corresponding user and assign a new password. After the password has been changed, client settings must be updated accordingly
    According to my knowledge the issue is not related to development side. Please check with your basis guys to check all the conenctions like SLD conenctions and J2EE engine status and also regardign ABAP stack.
    1. Got to ABAP stack and enter T code SLDCHECK.
    2. Also goto T code SMICM and there restart j2ee engine by selecting options J2EE soft Restart in the top menu.
    3. If still issues s there then if possible ask them to do entirre XI server restart once..
    Also go through this SAP note and ask your basis guys if any patches are to be implemented.
    [Note 1225611- com.sap.lcr.cimsrv.ChangePasswordServlet:|
    [1225611|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1225611]
    Regards::
    Amar Srinivas Eli

  • How to get meassges form jms to rfc scenerio

    hi,
    i need to pass the mssges getting from jms qeue with file name .
    my requirement like this ,when i pass the process file from xi
    the msseages should be attached with file name .
    is there is any udf for that.
    please guide me.
    warm regards

    Hello,
    Check this...
    /people/michal.krawczyk2/blog/2005/11/10/xi-the-same-filename-from-a-sender-to-a-receiver-file-adapter--sp14

  • R/3 database monitoring through RFC

    I have code which monitor database.
    There are two servers, one is XID and other is ECD. Messages are flowing from ECD to XID.
    Code is uploaded in XID server .Code monitor XID database .code hits Standard Sap table i.e. SXMSPMAST, check entries and send alert as per condition.
    ECD server requires to monitor ECD database by using same code existing in XID.
    ECD server wonu2019t allow deploying code.
    Requirement is as follows.
    1) Convert code (Existing in XID) into RFC.
    2) Call this RFC from ECD server.
    3) Pass server name u2018ECDu2019 as import parameter to RFC.
    5) Monitor ECD database using same piece of code (Via RFC).
    Let me know whether it is possible to monitor R/3 database using RFC?
    If possible then what are mandatory object I need to add in RFC?

    close

  • Error with Asynchronous RFC call to JDBC

    Hi all,
    We are working on a scenarion where in we have to make an asynchronous RFC call to JDBC.
    We have configured RFC sender adapter following this weblog
    /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
    We have created data types only for the database as RFC does not require any data types.
    And also we have created message types,message interfaces accordingly.
    In Message Mappping,we mapped the export parameters of RFC to the access fields of database message type.
    Also we have created sender agreement,interface determinations etc.... accordingly
    And for sending RFC request asynchronously we followed this weblog
    /people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
    Once done with all the above steps we could able to trigger the RFC call and caught with the following errors in SXMB_MONI and no errors are seen in communication monitoring
    SOAP Error:
    +<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>+
    +- <!--  Request Message Mapping+
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>Application</SAP:Category>
       <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/sap/xi/tf/_curr_exg_mm2_</SAP:P1>
    <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
      <SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" /> <SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_curr_exg_mm2_: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Also trace shows the following error thogh the interface determinations are properly configured
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">--start sender interface action determination</Trace>
      <Trace level="1" type="T">select interface BAPI_EXCHRATE_GETCURRENTRATES*</Trace>
      <Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:rfc:functions</Trace>
      <Trace level="1" type="T">no interface found</Trace>
      <Trace level="1" type="T">--start receiver interface action determination</Trace>
      <Trace level="1" type="T">Loop 0000000001</Trace>
      <Trace level="1" type="T">select interface *</Trace>
      <Trace level="1" type="T">select interface namespace</Trace>
      <Trace level="1" type="T">no interface found</Trace>
      <Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
      <Trace level="1" type="T">Hence set action to DEL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----</Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
    the above errors are shown as part of request mapping..
    Can any one please let me know what other configurations do we need to do?
    I did not map the RFC import parameters,do we need to do that
    Any help in this regard is really appreciated
    Rgds,
    Santhosh

    Hi,
    I am really happy to hear that the problem with mapping is resolved.
    Now as per your requirment It needs to be aynschornous RFC--> XI ---> JDBC call. In XI you should map the RFC Export parameters to the traget structure of JDBC.
    then the question is to how to trigger the RFC Function Module in R/3 to XI.
    Plesae follow below steps to trigger it from SAP R/3
    1. Create a RFC in the R/3 system
    2. Configure the SM59 and Sender Communication channle as given in the Michal's blog. Also test if it is succesful.
    /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
    3. Import the RFC in XI
    4. Do the mapping to the target strucutre
    5. Configure the JDBC receiver adapter
    /people/sameer.shadab/blog/2005/10/24/connecting-to-ms-access-using-receiver-jdbc-adapter-without-dsn
    6. You can trigger the RFC from R/3 sytem by using
    Async Call - in ABAP program use below syntax to call RFC. Here the export parameters will be passed on to XI which further have mapped to JDBC.
    CALL Function "RFC Name" IN BACKGROUND TASK destination <sm59 destination>
    COMMIT WORK.
    Sync Call
    CALL Function "RFC Name" destination <sm59 destination>
    Thanks
    Swarup
    Edited by: Swarup Sawant on Jan 27, 2008 9:14 AM

  • File to JDBC Using RFC Adapter.

    Hi All,
    I've been trying to find out a scenario which is like a File-to-Database where RFC is the sender and JDBC is at Receiver end.
    Kindly guide me in:
    1) What are the steps I need to do when I use a RFC Adapter to pick a file from FTP?
    2) Are the steps same for the JDBC Adapter as we do normally in a JDBC Receiver Adapter?
    3) Is there any other configuration required for this type of scenario?
    4) If I import the RFC only I wanted to know how would the file be picked from FTP Server? Is it likewhile create a RFC we import the File from FTP server.
    My Plan of Action to do the scenario is:
    1) Import the RFC from R/3.
    2) Create the data types for target.
    3) Map them both.
    4) Use JDBC Adapter on the Receiver end.
    These are the steps which I think should be done, if there are any  other steps which I need to do, please do tell me.
    Please do let me know the steps if all the are wrong as I'm doing this type of scenario for the 1st time.
    Regards,
    Sreedhar.

    Hi,
    Though i am not very sure about your interface requirement/design but would suggest you the following links :
    Sender RFC :
    /people/swaroopa.vishwanath/blog/2006/12/28/send-rfc-to-sap-xi-150-asynchronous
    /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
    /people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
    Reciever JDBC:
    JDBC Stored Procedures:
    /people/siva.maranani/blog/2005/05/21/jdbc-stored-procedures 
    JDBC Receiver Adapter -- Synchronous Select u2013 Step by Step
    /people/bhavesh.kantilal/blog/2006/07/03/jdbc-receiver-adapter--synchronous-select-150-step-by-step
    /people/siva.maranani/blog/2005/09/16/xi-how-to-on-jdbc-receiver-response - XI: How-to
    on JDBC receiver response

  • RFC Receiver Adapter error.

    Hi Experts,
                      Mine is a File To RFC Scenerio. data from File is foing into an RFC called /POSDW/CREATE_TRANSACTIONS_EXT, in R/3 system. . RFC adapter is red .Giving the follwoing error!.
       2009-02-18 14:49:41 Error MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling /POSDW/CREATE_TRANSACTIONS_EXT in remote system (RfcClient[GeneratedReceiverChannel_RFC]):com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: The ASSERT condition was violated.: com.sap.aii.af.rfc.afcommunication.RfcAFWException: error while processing message to remote system:com.sap.aii.af.rfc.core.client.RfcClientException: JCO.Exception while calling /POSDW/CREATE_TRANSACTIONS_EXT in remote system (RfcClient[
    Comments Pls!
    Regards,
    Arnab.
    Do I need to make a seperate TCP/IP connection from XI to R/3. If so, what will b the settings, Pls comment, !
    Arnab .
    Edited by: Arnab Mondal on Feb 18, 2009 11:04 AM

    Rajesh,
         you  mean to say apart from ABAP type 3 connection in XI as well as BI , I need to create TCP/IP connection in XI as well as BI ? Well In that case can you tell me when I am making the TCP/IP setting in XI, what will be the selection in
    Technical setings: Activation type?
    and in the gateway options, when I am doin the settings in XI server , whose gate way host and service , and  am i goin to put, XI or BI .
    Pls comment.
    Regards

  • SAP database updations through Java program

    Hi All,
    From Java program, I want to access SAP database batch RFC
    Please tell me which batch RFC's I have to use for read and update of a table.
    Please also tell me how to find out a batch RFC for a particular table.Is there any way to find it out like BAPI.
    What are the steps and settings ?
    Detailed steps help the requirement.
    Thanks,
    Giri

    Giri,
    Ya...Java APP sents data to XI and XI needs to insert the data into the database.
    Before the next round of data is sent by the Application, Xi should sent back info on the status of the records.
    Is this what you want?
    This will be like I have pointed earlier possible without a BPM. But, make the call from the sending application Synchronous. And then map the JDBC response to the calling aplication.
    But this updation is only possible through XI.
    If i got the requirement wrong can you let me know in more detail, what is it that you are trying?
    Reward if solved

Maybe you are looking for

  • Javascript create parent xml element from selection

    Hello, With help from these forums I finally learned how to script creating a parent xml element from a selection in the Structure Pane. var myDoc = app.activeDocument; var mySel = app.selection; var newParent = myDoc.xmlElements[0].xmlElements.add({

  • Craeting data fiel for data from KNA1 and ADRC table...

    Hi, I want to create a data file (tab delimited) which will have data from two tables, KNA1 and ADRC. The customer number, Name1 and Name2 fields data will come from KNA1 but the Street field data will come from ADRC table. The ADRNR number will be a

  • Urgent HELP needed: Problems transfer from Bold 9900 to Z10

    Dear helpdesk, I've just received my new Z10 and want to transfer all data from my old 9900. Using Link software seems to work fine.... until the copying from the 9900 is almost finished. Then I get the message "Data could not be copied from your dev

  • AIR Native extensions Hello World Example for iphone ios

    I need help as i am having runnable code library for Hello world which i took from the url, "http://akabana.info/2011/08/11/air-native-extension-10-try-air-for-ios-ane/" in which we are making static library in Xcode by using ADOBE AIR.framework so t

  • X6 connection problems and ovi problems

    My new X6 won't connect to the ovi software through my computer, it connects but then says errors and i cant sync it wih the computer or check my messages for things i need to save. i also cant use the phone as a modem as it says its not found althou