IDOC-FILE mapping

Hi all,
I'm doing a file-idoc scenario and this is my out structure:
0000300027,xxxxxxxxxxxxxxxxxxxx,SOLD_TO,SHIP_TO,BILL_TO,0000300027,0000300016,0000300016
But I want the structure in 3 different rows like:
0000300027,xxxxxxxxxxxxxxxxxxxx,SOLD_TO,0000300027
0000300027,xxxxxxxxxxxxxxxxxxxx,SHIP_TO,0000300016
0000300027,xxxxxxxxxxxxxxxxxxxx,BILL_TO,0000300016
so is there a way to do it with FCC or with the mapping?
Thanks,
Srini
Edited by: Srinivas Davuluri on Jul 3, 2008 12:55 PM

Hi,
My target looks like this with some sample test data:
MT
-DT
---Recordset (0..unbounded)
field1
field2
field3
field4
field5
---Record (0..unbounded)
field1 (SHIP_TO)
field2 (100)
---Record (0..unbounded)
field1 (SOLD_TO)
field2 (200)
---Record (0..unbounded)
field1 (BILL_TO)
field2 (100)  
This my source structure with the same sample data:
<DEBMAS06> (1..1)
---<IDOC>        (1..1)
<E1KNA1M> (1..1)
<f1>field1</f1> (0..1)
<f2>field2</f2> (0..1)
<f3>field3</f3> (0..1)
<f4>field4</f4> (0..1)
<f5>field5</f5> (0..1)
<E1KNVVM>  (0..unbounded)
<E1KNVPM> (0..unbounded)
<field1>SHIP_TO</field1> (0..1)
<field2>100</field2> (0..1)
</E1KNVPM>
<E1KNVPM>
<field1>SOLD_TO</field1>
<field2>200</field2>
</E1KNVPM>
<E1KNVPM>
<field1>BILL_TO</field1>
<field2>100</field2>
</E1KNVPM>
</E1KNVVM>
</E1KNA1M>
---</IDOC>
</DEBMAS06>
Even if I use the node function useOneAsMany I'm not able to produce result like this:
MT
-DT
---Recordset (0..unbounded)
field1
field2
field3
field4
field5
---Record (0..unbounded)
field1 (SHIP_TO)
field2 (100)
---Recordset (0..unbounded)
field1
field2
field3
field4
field5
---Record (0..unbounded)
field1 (SOLD_TO)
field2 (200)
---Recordset (0..unbounded)
field1
field2
field3
field4
field5
---Record (0..unbounded)
field1 (BILL_TO)
field2 (100)  
Can you guys suggest what are the 3 input fields to the node function useOneAsMany and the context.
Thanks,
Srini
Edited by: Srinivas Davuluri on Jul 8, 2008 11:20 AM

Similar Messages

  • Multi mapping.. is it possible File to Idoc & FIle .. its urgent?????

    Hi All,
    File to Idoc & File.
    I need to pick the file and i need to do multi mapping, so that from the file we can generate
    one idoc which has to go to SAP and
    one acknowledgment's file and sent back to partner.
    Based on the below blog, looks like we can't use Idoc adapter when the target message is Idoc using Multi mapping.
    /people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
    Can anyone suggest me how i can achieve this scenario without using BPM.??
    Regards
    Seema.

    Hi,
    The Multi mapping is possible without BPM but not for IDOC as its not part of Java Stack. IDOC adapter is on ABAP stack.
    As Raj have suggested,
    You could create two different Mappings one for file to IDOC and another for file to file as an acknowledgment.
    In Receiver determination you need to use multiple receivers as IDOC --R/3 receiver and the File receiver system.
    It will create the IDOC as well as push the acknowledgment to file also.
    But incase if you get any problem with sending the IDOC then also you will get successful acknowledgment via file. So directly there will not be any relation between these IDOC and File receivers as an delivery recipt of IDOC.
    Here either you have to use the IDOC acknowledgment feature or BPM or Alert notification to get the exact notification about the IDOC posting to receiver system.
    Please refer below links
    1. IDOC acknowledgment
    This Feature is Available under SP 18 and we are on SP16
    http://help.sap.com/saphelp_nw04/helpdata/en/42/c8f66bc7a56bb0e10000000a1553f6/frameset.htm
    Check this document on handling IDOC acknowledgements. This might give you some pointers.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
    This Feature is Available under SP 18 and we are on SP16
    http://help.sap.com/saphelp_nw04/helpdata/en/42/c8f66bc7a56bb0e10000000a1553f6/frameset.htm
    Check this document on handling IDOC acknowledgements. This might give you some pointers.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
    How to Handle Acknowledgments for IDoc (NW7.0)
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/903a0abc-e56e-2910-51a8-9dc616df56eb
    IDOC acknowledgements
    2. BPM
    File to IDOC with BPM
    File to idoc with BPM
    Problem in BPM implementation
    Use Aleaud in BPM
    /people/udo.martens/blog/2005/09/30/one-logical-system-name-for-serveral-bpm-acknowledgements
    /people/pooja.pandey/blog/2005/07/27/idocs-multiple-types-collection-in-bpm
    3. Alert Notification
    /people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step - Alert Configuration
    /people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide - Trouble shoot alert config
    Thanks
    Swarup

  • IDOC -- File (Multi-Mapping )

    Hi Guys,
    iam working on an IDOC --> File scenario.
    I had used a multimapping to split the source file into three target files and for creating those three files i had used three differemt Inbound MI and Three different Comm Channels. The file is getting created in the designated directory but the data is not getting written.
    Iam using NFS file system for this.
    The message Monitoring is also showing that everything is getting processed with some bytes of data written into the file. Iam not able to find what is not working in this case.....
    Can anyone tell me why the data is not getting written in the created file.
    Any suggestion is appreciated.
    Regards,
    Kittu.

    Hi Kittu,
    1. Please check in SXMB_MONI if 'Call Adapter' is happening.
    Check the payload here and see if payload is correct.
    After this if the file is not written then check on the File content conversion.
    Regards
    Vijaya

  • File mapping in R/3

    Hey guys,
    is there a mapping module in R/3 like on PI Enterprise Service Builder? I mean, i want to know whether it is possible to use a standard tool from SAP to do a file mapping to a ABAP structure? E.g. a get a XML file via PI (i know, i could do the mapping in PI) which is routed to R/3. Now i want to do my mapping in R/3. Is there a tool in R/3? I could build such a tool but i want to know, does SAP deliver such a tool for R/3? Is it possible to use the module of PI for mapping in R/3?
    thx for your answers,
          W.

    You do not need another mapping in SAP once the mapping is done in PI. PI will map from external format to SAP IDOC format (either in IDOC flat file based or IDOC XML format). After you drop this mapped file which is in IDOC format (flat file/XML) into the application server (configured in the receiving systems) and trigger the startrfc.exe, SAP would take care of the rest (provided all inbound setting are setup).
    Now if you want a custom ABAP structure, you'll have to mimic the standard FM's. If you have a predefined structure, then create an custom IDOC and a custom FM to process it. Set it up just like the standards and then do the same process - map into the custom format from PI and then trigger the RFC, this would trigger the process code and invoke your custom FM to process this custom IDOC/structure.

  • XML IDoc file to IDOC .

    Hi,
    I am receiving XML idoc (Orders05) file from 3rd party to PI system , PI needs to create sales order IDoc ( Orders05) in ECC system. 
    1) Do I need to create source structure for XML IDoc file ? If yes should I create the structure as Orders05 ?
    2) How to map line items of xml file to Orders05 IDoc line items ?
    Please help.
    Thanks - Vinay.

    Hi Vinay,
    Please see Mikes reply in this thread. You may follow the same procedure:
    XML to FlatFile IDOC
    Regards,
    ---Satish

  • Problem adapter idoc - file ATTRIBUTE_INV_SND_SERV

    Hello All,
    please help me for my problem on adapter in my system XI for a scenario idoc -> file an I have an message error.
    <b>xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
      <SAP:P1>BS_ADONIX</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Unable to convert the sender service BS_ADONIX to an ALE logical system</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error></b>
    Please help if you have some idea BS_ADONIx is a business service.
    Thanks for your reply

    Steps IDOC to File.
    IN IR
    1. Import the IDOC in XI (input).
    2. Create a Data type of (output) i.e. file.
    3. Create a Message type of (output) i.e. file used the above data type.i.e.Step 2
    4. Create a Message interface of(output) .i.e file used the above messagetype. i.e.Step3.
    5. create Mappping select source as IDOC and target as Message type you created.
    6, In Interface mapping select source as IDOC and Target Interface Message Interface of file i.e.Step 4.
    In ID.
    Select the recevier determination of .
    1.select sender system as R/3 system recivr as File Bunisees system
    2. create interface determination select sender system as R/3 Sender interface as IDOC . in interface determination select inbound message whihc createdin step 4
    and message interface we created in step 5.
    3. create recevier determination sender r/3 interface IDOC and reciver File business system . so create reciver file adapter and assign to file business system
    Please reward points
    Thanks
    Sreeram.G.Reddy

  • Acknowledgement - IDoc-File & File-IDoc scenario

    Hi All,
       Acknowledgement is possible in case of asynchronous IDoc-XI-File scenario? If yes, how to setup?
       Same as above question for File-XI-IDoc scenario.
       In case of synchronous scenario, how to setup email with acknowledgement?
    Thanks a lot in advance.
    Sree

    Hi Rama,
    While doing an IDOC -> XI -> File scenario, The Points to noted are:
    1. You don’t need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
    2. You import the IDOC and use the same in your mapping.
    3. In this configuration note that you don’t have a sender agreement as you don’t have a sender IDOC adapter.
    If it is that you wanted to send an IDOC from XI (File to IDOC) , then in this case:
    points 1 and 2 will remain, but the 3 will not. You will need a sender agreement for the file and a receiver agreement for the IDOC.
    IDOC -> File scenario ref:
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    File -> IDOC ->
    /people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping
    (It concentrates on XSLT mapping but also gives an idea about the configuration part. Do go thru that, it might help you.)
    I hope I have answered your query.
    Regards,
    Abhy
    PS: AWARD POINTS FOR HELPFUL ANSWERS.

  • Production Time Issues on IDOC---File Scenario

    Hi All,
    We have done all the IDOC--File scenarios Successfully in DEV System.
    Now its time to Production and Go-Live.
    Q1) Assume If Bulk messages are Failed in RWB-----Receiver CC Due to some error, Then how to Handle these Error messages
    Regards
    Suman

    Hi Mahesh,
    This is My Trace File
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="B" name="IDX_INBOUND_XMB" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">User: 116866</Trace>
      <Trace level="1" type="T">Language: E</Trace>
      <Trace level="1" type="T">ALE-AUDIT-IDoc-Inbound Handling</Trace>
      <Trace level="1" type="T">IDoc-Inbound-Handling</Trace>
      <Trace level="2" type="T">Tunneling needed?</Trace>
      <Trace level="2" type="T">Partytype = LS fallback to logical system</Trace>
      <Trace level="3" type="T">Sender Interface</Trace>
      <Trace level="3" type="T">WP_PLU.WP_PLU03 urn:sap-com:document:sap:idoc:messages</Trace>
      <Trace level="1" type="T">Syntax-Check-Flag X</Trace>
      <Trace level="1" type="T">IDoc-Tunnel-Flag</Trace>
      <Trace level="1" type="T">Queueid</Trace>
    - <Trace level="1" type="B" name="IDX_IDOC_TO_XML">
      <Trace level="1" type="T">Get the Metadata for port SAPPIS</Trace>
      <Trace level="2" type="T">----
    </Trace>
      <Trace level="2" type="T">IDX_STRUCTURE_GET Details</Trace>
      <Trace level="2" type="T">Port : SAPPIS</Trace>
      <Trace level="2" type="T">IDoctyp : WP_PLU03</Trace>
      <Trace level="2" type="T">Cimtyp :</Trace>
      <Trace level="2" type="T">RFCDest :</Trace>
      <Trace level="2" type="T">Release : 700</Trace>
      <Trace level="2" type="T">Version : 3</Trace>
      <Trace level="2" type="T">Direct : 1</Trace>
      <Trace level="2" type="T">SAPREL : 700</Trace>
      <Trace level="2" type="T">----
    </Trace>
      <Trace level="1" type="T">Convert Segment-Definitions to Types</Trace>
      <Trace level="1" type="T">Make Syntax check of actual Idoc</Trace>
      <Trace level="2" type="T">----
    </Trace>
      <Trace level="2" type="T">IDX_SYNTAX_CHECK</Trace>
      <Trace level="2" type="T">Port : SAPPIS</Trace>
      <Trace level="2" type="T">IDoctyp : WP_PLU03</Trace>
      <Trace level="2" type="T">Cimtyp :</Trace>
      <Trace level="2" type="T">----
    </Trace>
      <Trace level="2" type="T">Create XML-Control Record</Trace>
      <Trace level="2" type="T">Create XML-Data Records</Trace>
      <Trace level="3" type="T">Create data Record E1WPA01</Trace>
      <Trace level="3" type="T">Create data Record E1WPA02</Trace>
      <Trace level="3" type="T">Create data Record E1WPA03</Trace>
      <Trace level="3" type="T">Create data Record E1WPA04</Trace>
      <Trace level="3" type="T">Create data Record E1WPA05</Trace>
      <Trace level="3" type="T">Create data Record E1WPA04</Trace>
      <Trace level="3" type="T">Create data Record E1WPA05</Trace>
      <Trace level="3" type="T">Create data Record E1WPA04</Trace>
      <Trace level="3" type="T">Create data Record E1WPA05</Trace>
      <Trace level="3" type="T">Create data Record E1WPA07</Trace>
      <Trace level="3" type="T">Create data Record E1WXX01</Trace>
      <Trace level="3" type="T">Create data Record E1WXX01</Trace>
      <Trace level="3" type="T">Create data Record E1WXX01</Trace>
      <Trace level="3" type="T">Create data Record E1WXX01</Trace>
      <Trace level="3" type="T">Create data Record E1WXX01</Trace>
      <Trace level="3" type="T">Create data Record E1WXX01</Trace>
      <Trace level="3" type="T">Create data Record E1WXX01</Trace>
      <Trace level="3" type="T">Create data Record E1WXX01</Trace>
      <Trace level="3" type="T">Create data Record E1WXX01</Trace>
      <Trace level="3" type="T">Create data Record E1WXX01</Trace>
      <Trace level="3" type="T">Create data Record E1WXX01</Trace>
      <Trace level="3" type="T">Create data Record E1WXX01</Trace>
      <Trace level="3" type="T">Create data Record E1WXX01</Trace>
      <Trace level="3" type="T">Create data Record E1WXX01</Trace>
      <Trace level="3" type="T">Create data Record E1WXX01</Trace>
      <Trace level="3" type="T">Create data Record E1WXX01</Trace>
      <Trace level="3" type="T">Create data Record E1WXX01</Trace>
      <Trace level="3" type="T">Create data Record E1WXX01</Trace>
      <Trace level="3" type="T">Create data Record E1WXX01</Trace>
      <Trace level="3" type="T">Create data Record E1WXX01</Trace>
      </Trace>
      <Trace level="2" type="T">party-scheme: ALE#KU</Trace>
      <Trace level="1" type="T">party normalization error: scheme = ALE#KU</Trace>
      <Trace level="2" type="T">Set Sender Routing-object</Trace>
      <Trace level="1" type="T">Set Receiver Routing-object</Trace>
      <Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace>
      <Trace level="1" type="T">COMMIT is expected by application !</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">XMB was called with external pipeline PID = ENTRY</Trace>
      <Trace level="3" type="T">Getting type of XMB...</Trace>
      <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="2" type="T">XMB kind = CENTRAL</Trace>
      <Trace level="3" type="T">Start pipeline found</Trace>
      <Trace level="2" type="T">Switch to external start pipeline PID = CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">
      <Trace level="3" type="T">No triggers found. OK.</Trace>
      </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="3" type="T">system-ID = PSX</Trace>
      <Trace level="3" type="T">client = 100</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = 116866</Trace>
      <Trace level="1" type="Timestamp">2008-05-05T13:15:27Z INDIA</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 level="1" type="T">Message-GUID = 481ADC34F6CF1214E1000000AC10100D</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 level="3" type="T">QOS = EO</Trace>
      <Trace level="3" type="T">Message-GUID = 481ADC34F6CF1214E1000000AC10100D</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 level="3" type="T">External PLID = CENTRAL</Trace>
      <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
      <Trace level="3" type="T">Generate prefixed queue name</Trace>
      <Trace level="1" type="T">Queue name : XBTI0001</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTI0001</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="3" type="T">Setup qRFC Scheduler</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="3" type="T">Call qRFC .... MsgGuid = 481ADC34F6CF1214E1000000AC10100D</Trace>
      <Trace level="3" type="T">Call qRFC .... Version = 000</Trace>
      <Trace level="3" type="T">Call qRFC .... Pipeline = CENTRAL</Trace>
      <Trace level="3" type="T">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="3" type="T">Version number = 000</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 001</Trace>
      <Trace level="3" type="T">Message version 000</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      <Trace level="1" type="T">--start sender interface action determination</Trace>
      <Trace level="1" type="T">select interface WP_PLU.WP_PLU03*</Trace>
      <Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</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="3" type="T">Trace object available again now. OK.</Trace>
      <Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
      <Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
      <Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
      <Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
      </Trace>
      <Trace level="3" type="T">message version successfully read from persist version= 000</Trace>
      <Trace level="2" type="T">Increment log sequence to 001</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 level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="3" type="T">system-ID = PSX</Trace>
      <Trace level="3" type="T">client = 100</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = 116866</Trace>
      <Trace level="1" type="Timestamp">2008-05-05T13:16:48Z INDIA</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <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 level="3" type="T">External PLID = CENTRAL</Trace>
      <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline attributes</Trace>
      <Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
      <Trace level="3" type="T">ENABLE = 1</Trace>
      <Trace level="3" type="T">TRACELEVEL = 0</Trace>
      <Trace level="3" type="T">EXEMODE = A</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline elements</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
      <Trace level="3" type="T" />
      <Trace level="1" type="Timestamp">2008-05-05T13:16:48Z INDIA Begin of pipeline processing PLSRVID = CENTRAL</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
      <Trace level="1" type="Timestamp">2008-05-05T13:16:48Z INDIA Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_RD_PLSRV</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <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 level="2" type="T">Start with given receiver C086 -</Trace>
      <Trace level="2" type="T">Classic Receiver Determination via Rules.</Trace>
      <Trace level="2" type="T">Check conditions for rule line no. 1</Trace>
      <Trace level="2" type="T">...valid Receiver w/o Condition: - BS_Soap_Service_Qty</Trace>
      <Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
      <Trace level="2" type="T">Number of Receivers:1</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2008-05-05T13:16:48Z INDIA End of pipeline service processing PLSRVID= PLSRV_RECEIVER_DETERMINATION</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 001</Trace>
      <Trace level="3" type="T">Message version 001</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
    - <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">
      <Trace level="1" type="Timestamp">2008-05-05T13:16:48Z INDIA Start of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_ID_PLSRV</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <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 level="2" type="T">Check conditions for (Inb: Party Srvc If) BS_Soap_Service_Qty MI_POS_Itemmaster_OB</Trace>
      <Trace level="2" type="T">...valid InbIf without Condition: MI_POS_Itemmaster_OB</Trace>
      <Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2008-05-05T13:16:48Z INDIA End of pipeline service processing PLSRVID= PLSRV_INTERFACE_DETERMINATION</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 002</Trace>
      <Trace level="3" type="T">Message version 002</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" />
    - <!--  ************************************
      -->
      <Trace level="1" type="Timestamp">2008-05-05T13:16:48Z INDIA Start of pipeline service processing PLSRVID= PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_RECEIVER_SPLIT</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
      <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT-ENTER_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Case handling for different plsrv_ids PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="2" type="T">got property produced by receiver determination</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 = XBTO0___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 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 level="3" type="T">Persisting message Status = 012</Trace>
      <Trace level="3" type="T">Message version 003</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE">
      <Trace level="3" type="T">Trace object available again now. OK.</Trace>
      <Trace level="3" type="T">Message was read from persist layer. OK.</Trace>
      <Trace level="3" type="T">Message properties in XMB object were setup. OK.</Trace>
      <Trace level="3" type="ToDo">Make sure we catch exceptions in persist read</Trace>
      <Trace level="3" type="ToDo">Tracing obj. not avail. before return of CL_XMS_MAIN-PERSIST_READ_MESSAGE</Trace>
      </Trace>
      <Trace level="3" type="T">message version successfully read from persist version= 004</Trace>
      <Trace level="2" type="T">Increment log sequence to 005</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 level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="3" type="T">system-ID = PSX</Trace>
      <Trace level="3" type="T">client = 100</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = 116866</Trace>
      <Trace level="1" type="Timestamp">2008-05-05T13:18:58Z INDIA</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <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 level="3" type="T">External PLID = CENTRAL</Trace>
      <Trace level="3" type="T">Internal PLID = SAP_CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline attributes</Trace>
      <Trace level="3" type="T">PID = SAP_CENTRAL</Trace>
      <Trace level="3" type="T">ENABLE = 1</Trace>
      <Trace level="3" type="T">TRACELEVEL = 0</Trace>
      <Trace level="3" type="T">EXEMODE = A</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline elements</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
      <Trace level="3" type="T" />
      <Trace level="1" type="Timestamp">2008-05-05T13:18:58Z INDIA Begin of pipeline processing PLSRVID = CENTRAL</Trace>
      <Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>
    - <Trace level="1" type="B" name="PLSRV_MAPPING_REQUEST">
      <Trace level="1" type="Timestamp">2008-05-05T13:18:58Z INDIA Start of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL">
    - <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
      <Trace level="2" type="T">......attachment XI_Context not found</Trace>
      <Trace level="3" type="T">Mapping already defined in interface determination</Trace>
      <Trace level="3" type="T">Object ID of Interface Mapping C5523ABE7D9A35BDABE2082468D67E41</Trace>
      <Trace level="3" type="T">Version ID of Interface Mapping 1FB1D8C0010B11DD9AB1F535AC101018</Trace>
      <Trace level="1" type="T">Interface Mapping http://sub-sapretail-pos.com/Itemmaster IM_POS_Itemmaster_OB</Trace>
      <Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_MM_POS_Itemmaster_multi_OB_</Trace>
      <Trace level="3" type="T">Dynamic Configuration ( http://sap.com/xi/XI/System/IDoc SNDPOR SAPPIS ) ( http://sap.com/xi/XI/System/IDoc SNDPRN PISCLNT900 ) ( http://sap.com/xi/XI/System/IDoc SNDPRT LS ) ( http://sap.com/xi/XI/System/IDoc RCVPOR A000000015 ) ( http://sap.com/xi/XI/System/IDoc RCVPRN C086 ) ( http://sap.com/xi/XI/System/IDoc RCVPRT KU ) ( http://sap.com/xi/XI/System/IDoc MESTYP WP_PLU ) ( http://sap.com/xi/XI/System/IDoc IDOCTYP WP_PLU03 ) ( http://sap.com/xi/XI/System/IDoc CIMTYP )</Trace>
      <Trace level="2" type="T">Mode 0</Trace>
      <Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_POS_Itemmaster_multi_OB_.</Trace>
      <Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_POS_Itemmaster_multi_OB_</Trace>
      <Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_POS_Itemmaster_multi_OB_ completed. (executeStep() of com.sap.xi.tf._MM_POS_Itemmaster_multi_OB_</Trace>
      <Trace level="3" type="T">Dynamic Configuration ( http://sap.com/xi/XI/System/IDoc RCVPOR A000000015 ) ( http://sap.com/xi/XI/System/IDoc SNDPRT LS ) ( http://sap.com/xi/XI/System/IDoc RCVPRN C086 ) ( http://sap.com/xi/XI/System/IDoc SNDPOR SAPPIS ) ( http://sap.com/xi/XI/System/IDoc SNDPRN PISCLNT900 ) ( http://sap.com/xi/XI/System/IDoc CIMTYP ) ( http://sap.com/xi/XI/System/IDoc IDOCTYP WP_PLU03 ) ( http://sap.com/xi/XI/System/IDoc MESTYP WP_PLU ) ( http://sap.com/xi/XI/System/IDoc RCVPRT KU )</Trace>
      <Trace level="1" type="T">ContentType application/xml</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2008-05-05T13:18:58Z INDIA End of pipeline service processing PLSRVID= PLSRV_MAPPING_REQUEST</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 005</Trace>
      <Trace level="3" type="T">Message version 005</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
    - <Trace level="1" type="B" name="PLSRV_OUTBOUND_BINDING">
      <Trace level="1" type="Timestamp">2008-05-05T13:18:58Z INDIA Start of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="3" type="T">Calling pipeline service: PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
      <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_OUTBINDING</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV">
      <Trace level="2" type="T">O U T B O U N D - B I N D I N G</Trace>
      <Trace level="2" type="T">Cache Content is up to date</Trace>
      <Trace level="2" type="T">determine OUTBOUND BINDING for:</Trace>
      <Trace level="2" type="T">-Subhiksha_PIS_subprd1</Trace>
      <Trace level="2" type="T">-BS_Soap_Service_Qty</Trace>
      <Trace level="2" type="T">http://sub-sapretail-pos.com/Itemmaster.MI_POS_Itemmaster_OB</Trace>
      <Trace level="2" type="T">Channel found: - BS_Soap_Service_Qty - CC_POS_Itemmaster_OB_Qty</Trace>
      <Trace level="2" type="T">no header mapping defined</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2008-05-05T13:18:58Z INDIA End of pipeline service processing PLSRVID= PLSRV_OUTBOUND_BINDING</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 006</Trace>
      <Trace level="3" type="T">Message version 006</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
      <Trace level="1" type="B" name="PLSRV_CALL_ADAPTER" />
    - <!--  ************************************
      -->
      <Trace level="1" type="Timestamp">2008-05-05T13:18:58Z INDIA Start of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">Reading Pipeline-Service specification...</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
      <Trace level="3" type="T">ADRESSMOD = SD</Trace>
      <Trace level="3" type="T">P_CLASS =</Trace>
      <Trace level="3" type="T">P_IFNAME =</Trace>
      <Trace level="3" type="T">P_METHOD =</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Unknown channel type: SOAP</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">Pipeline service specification (table SXMSPLSRV)</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = AENGINE</Trace>
      <Trace level="3" type="T">ADRESSMOD = SD</Trace>
      <Trace level="3" type="T">P_CLASS = CL_XMS_PLSRV_IE_ADAPTER</Trace>
      <Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
      <Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
      <Trace level="3" type="T">FL_LOG =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
      <Trace level="3" type="T">Channel for adapter engine: SOAP</Trace>
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
      <Trace level="2" type="T">return fresh values from cache</Trace>
      <Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET):</Trace>
      <Trace level="3" type="T">URL = http://psxprd:51000/MessagingSystem/receive/AFW/XI</Trace>
      <Trace level="3" type="T">User = PIISUSER</Trace>
      <Trace level="3" type="T">Cached = X</Trace>
      <Trace level="3" type="T">Creating HTTP-client</Trace>
      <Trace level="3" type="T">HTTP-client: creation finished</Trace>
      <Trace level="3" type="T">Security: Basic authentication</Trace>
      <Trace level="3" type="T">Serializing message object...</Trace>
      <Trace level="3" type="T">HTTP-client: sending http-request...</Trace>
      <Trace level="3" type="T">HTTP-client: request sent</Trace>
      <Trace level="3" type="T">HTTP-client: Receiving http-response...</Trace>
      <Trace level="3" type="T">HTTP-client: response received</Trace>
      <Trace level="3" type="T">HTTP-client: checking status code...</Trace>
      <Trace level="3" type="T">HTTP-client: status code = 200</Trace>
      <Trace level="3" type="T">Deserializing message object...</Trace>
      <Trace level="3" type="T">HTTP-client: closing...</Trace>
      </Trace>
      </Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">Persisting message after plsrv call</Trace>
      <Trace level="3" type="T">Message-Version = 007</Trace>
      <Trace level="3" type="T">Message version 007</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
      <Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 014</Trace>
      <Trace level="3" type="T">Message version 008</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </SAP:Trace>
    Regards
    Suman

  • Runtime error (idoc-file)

    Hi  experts
    iam working on IDOC-file scenarion. after mapping design i have tesed my message mapping (without any data) iam getting error "RuntimeException in Message-Mapping transformation: Unparseable date: ""
    then i tetsed the scenario end to end , an outbound IDOC is genarted but in sxmb_moni the status is RED and the error is "RuntimeException in Message-Mapping "
    i copied the payload XML message and retested in IR this time the error is :
    "Cannot produce target element /ns0:MT_porder. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd"
    please suggest me what could be the error
    regards
    vasavi

    hi suddha,
    tahnks for your reply.
    i checked in RWB>adapterengine->FTP-->
    Receiver Adapter v2123 for Party '', Service 'Sys_DMattec':
    Configured at 2008-07-28 17:01:23 EDT
    History:
    - 2008-08-06 10:36:02 EDT: Processing finished successfully
    - 2008-08-06 10:36:01 EDT: Processing started
    - 2008-08-06 10:29:36 EDT: Processing finished successfully
    - 2008-08-06 10:29:35 EDT: Processing started
    - 2008-08-05 16:38:04 EDT: Processing finished successfully
    but as u said i didnt find anywhere
    >>>if successful you get a Status Msg DLVD (Delivered)
    please tell me how can i check auditlog?
    Iam not sure what kind of ack message you are looking at for FTP protocol. Can be a bit more clear on that?
    in sxmb_moni --XML message
    status                                ack.status
    processed sucessfully      ? (still waiting )
    regards
    vasavi

  • Configuring a multiple IDOC-File using BPM

    HI,
    My scenario involves 2different idocs which are to be mapped to a file structure,the steps that i have followed in IR is ,
    1.Create target MesageType
    message Interfaces.
    2.Create 2 Abs interfaces based on IDOC
    3.Create 1 Abs for o/p of BPM.
    4.Create 1 Inb for target.
    Message mapping.
    5.Two dummy mappings for outbound idocs to abstract idocs.
    6.One multimapping(two idocs-->File)
    7.One Dummy mapping for Abstract Intf(output of BPM) to target Filestructure(inbound).
    Interface Mapping.
    8.Two Mesage intf for changing Outbound idocs to Abstract using the dummy mapping programs)
    9.One Message Intf using 2 abs Idocs to One Abs File(using the multimapping pgm)
    10.one msg Intf for BPM Out --> Inb File (using the dummy mapping pgm)
    Integration Process.
    I have used a fork step under which there are 2 recieve steps to recieve the IDOCS and then a Transformation step that would multi-map the idocs to the file,then a send step.
    Please let me know if the approach is right.
    Also Could anybody please let me know what steps do i need to take in the Configuration part and should i use the wizard or should i do it manually.
    the problem using the wizard is it doesnt let me choose 2 Message interfaces for the sender ie; IDOCS,
    Please help me on this.Thank you waiting for a reply....)

    John,
    <i>5.Two dummy mappings for outbound idocs to abstract idocs.
    7.One Dummy mapping for Abstract Intf(output of BPM) to target Filestructure(inbound).</i>
    These dummy mappings are needed. As both the Abstract Message Interfaces and the Idoc / Inbound interface will use the same message type, no dummy mapping needed. In the interface determination for these, no interface mapping needs to be mnetioned.
    ID.
    Receiver Determaintions
    1. Sender Service -- IDOC1  and Reciver Service is -- BPM. Sender Interface will be IDOC1 and Receiver Interafce will be The IDOC abs interface . No Interface mapping.
    2. Sender Service --- IDOC2 and Receiver Service is -- BPM. Sender Interface will be IDOC2 and Receiver Interafce will be The IDOC abs interface . No Interface mapping.
    3. Sender Service is BPM , and receiver servcice is File. Sender Interface is File Abs interface and reciver interface is the Inbound File interface.
    1 Reciver Agreement for the File adapter.
    Regards,
    Bhavesh

  • Idoc file to R/3 interface

    Hi All,
    I have a scenario to send EDI flat file to R/3. I need to write an interface program to read the file and map it to idoc and post it in the backend FI system
    Any sample program code or process would be helpful and appreciated. The reqmt is so urgent
    Thanks
    Ricky

    Read the Idoc file using standard upload methodes OPEN DATASET, TRANSFER or GUI_UPLOAD.
    Once the file is got into the program use IDOC_INBOUND_SYNCHRONOUS to create Idoc from the file data. Its interface is fairly simple, it just has an internal table which  takes the file and creates idoc, if the file data forms syntactically correct idoc.
    You can also use EDI_DATA_INCOMING function which can directly read the file from file port and create idoc.

  • Read/write operation on SAP IDOC file

    Hi All,
    We are developing an application, which will be used for registering and processing of travel data for a client.One of itu2019s functionality is to get the data from external system in different format(like CSV, Excel, Fixed Flat file, XML, main frame file, DBF and SAP IDOC) and import it into Oracle databases.
    One of the design considerations for it, is to read these files and convert it into predefined XML format
    and then import these data from XML to oracle database.
    Currently we are analyzing the requirement and trying to find out all the Open Source JAVA API which can convert these different format files to predefined XML format, using some mapping file.
    We have found out Open Source JAVA API for all the file format, except SAP IDOC files.
    Any Java API to read/write the SAP IDOC file, Please advise
    Regards,
    Madhu
    Edited by: Madhu Sudhan on Feb 17, 2009 12:06 PM

    Hi All,
    We are developing an application, which will be used for registering and processing of travel data for a client.One of itu2019s functionality is to get the data from external system in different format(like CSV, Excel, Fixed Flat file, XML, main frame file, DBF and SAP IDOC) and import it into Oracle databases.
    One of the design considerations for it, is to read these files and convert it into predefined XML format
    and then import these data from XML to oracle database.
    Currently we are analyzing the requirement and trying to find out all the Open Source JAVA API which can convert these different format files to predefined XML format, using some mapping file.
    We have found out Open Source JAVA API for all the file format, except SAP IDOC files.
    Any Java API to read/write the SAP IDOC file, Please advise
    Regards,
    Madhu
    Edited by: Madhu Sudhan on Feb 17, 2009 12:06 PM

  • Requirement  for Idoc-- File

    I am Doing Idoc----->File  mean R/3 -
    > Legasy.(at Receiver side save File as idoc no)
    I want save the file name    with number of Idoc(Receiver side).

    Follow the steps that is for dynamic file name ... using udf  in message mapping in IR and adapter specific mesage attributes in ID
    In the UDF,
    1. for file name == tGIve the name of the IDOC
    File propery--- Give the Source /IDOC field name which contains the IDOC number
    when performing mapping map    Source field (Field that contains IDOC number)->UDF--> Target/File root node..

  • IDOC -FILE ERROR

    HI experts,
    My scenario is sending IDOC(DEBMAS06) to FILE.
    I have configured all the requirements BD54,SM59,WE21,WE20 IN R/3 and SM59,IDX1,IDX2.
    WHEN I AM SENDING AN IDOC USING TrCode:BD12, I AM GETTING AN ERROR IN WE02 THAT "EDI: Partner profile inbound not available".
    AND IN IDX5 I AM GETTING AN ERROR "No receiver could be determined"
    NOTE: IT IS IDOC - FILE SCENARIO
    THANKS IN ADVANCE

    HI SWARUP,
    AFTER DOING ALL THE STEPS U GUIDED, THE RESULT IS AS FOLLOWS IN ID,
    Interface Mapping
    <Not found>
    Runtime error
    java.lang.NullPointerException thrown during application mapping com/sap/xi/tf/_CUSTOMER_MM_:
    <Trace level="1" type="B">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace>... (109 lines)
    THANKS IN ADVANCE

  • IDOC File target - file not getting created

    I am using Realtime job for sending idoc from data services to sap. I am using idoc message as source, query and idoc file as target transform in the data flow. I have following settings in IDOC file as target
    Idoc file : /tmp/costcentertest.txt
    Idoc type: COSMAS01
    Data store name: DS_SAP
    Application server: saptest
    When i send the idoc I can load the data into table or create the file in /tmp directory. After changing target to idoc file and entering the above settings i don't see any file getting created. I do see idoc was received from we05 and also show green in data management console.
    I was checking if i have to change something or missing some steps.

    Hi Satheesh
    Check whether the order qty field is there in flat file or not. Second if the data is there then it is getting uploaded
    in read the file or not. Subsequently in converted data . When the mapping  is correct and  data is getting populated
    in read file and converted file it will get uploaded. Hope it will help you.
    Thanks
    Sushant

Maybe you are looking for

  • Backing Up To An External DVD Drive. Any Suggestions?

    I have a question please? How do I change settings in iTunes to backup to an external "DVD" drive instead of an internal "Cd" drive? Everytime I try to back things up in iTunes, the only option I see is to backup to Cd. I rarely backup anything to Cd

  • Error message when installing Mavericks...

    After successfully downloading, the install program error messa 'this version has virus... remove and download new version." After 5 or 6 times of this, still nothing... help!

  • IMac 2011 Thunderbolt - iWires MDP to HDMI

    Hello all - I've had a good trawl through the communities and am unable to find a fix for my issue. I've recently upgraded from a 2010 mac mini, with HDMI to a new iMac 2011 - which has the new thunderbolt port. By my understanding, this will enable

  • Message interface not exist in any software components on business system

    Hi Experts, In development-environment we have an interface (SAP->XI->3rd party system) with a conditional receiver determination (based upon a fieldvalue in RFC that comes from SAP,  "CONTROL_RECEIPE_DOWNLOAD"). This functions properly in developmen

  • Read SOAP Exception

    Hi XI Guys,                     My scenario is Proxy to Soap Synchronous. I want to read Soap Exception generated by target Application From XI Moni. Since this exception is a part of SOAP Body. How can we read this part of Exception from SOAP Body a