IDOC-XI scenario problem

I have a IDOC - XI scenario,
where IDOC is generating from a R/3,
the problem is, an IDOC was sent from R/3, but has not reached XI,
in R/3, i have seen in WE05, there i see this IDOC having status '03',
and, also in SM58, there i no error corresponding to this IDOC,
but in XI, in IDX5, i cant see that IDOC,
where the problem lies?

Make sure that the sender partner and receiver partner values corrrespond to the logical system names you have used in your partner profile in we20. Sender Partner Name should be your R3's logical system name, and Receiver Partnr Name should be the Logical System name for which you have created an Outybound Entry in We20.The Sender port and receiver port also should be be the ones created in We21 for XI, and SAP+"SYSID" for R3
) Check your PARTENER PROFILE settings ; is IDOC in outbound messages.
2) You may need to check Bussiness System given for Technical System for r3 and in ID check Adapter Specific Identifiers in OBJECTS ->Bussiness System->Service
Go to bd87 and trigger them. You can only trigger the idocs if they are in yellow color. If it is in red it is having an error.
So try to send the one which are in yellow error so that we can see whether it is reaching XI or not. If everything is OK then you should see the idoc in sxmb_moni.
Please see the below links ,
/people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
idocs - /people/sravya.talanki2/blog/2005/08/24/do-you-like-to-understand-147correlation148-in-xi
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
note:reward points if solution found helpfull.....
regards
chandrakanth.k

Similar Messages

  • IDoc - File Scenario

    Dear SDN,
    We have to develop something like this:
    An IDoc is generated from an ABAP Business System. Using content based routing conditions the IDoc must be sent to different FTP servers. The problem is that the IDoc must be written in its "native plain" format, not in XML format.
    Any ideas?

    hi Gustavo,
    2 ways
    1. https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
    2. send the idoc from R3 in native IDOC (file port) and just tranport it via XI
    both ways will produce native IDOC:)
    for file ports you can check out my book
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • R/3 to XI manually IDOC sending and problem:

    <u><b>R/3 to XI manually IDOC sending and problem:</b></u>
    I sent IDOC using we19 transaction from R/3 system. After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
    I check XI (sxmb_moni) but there is nomessage there.
    <b>Problem 1:</b> I don't want R/3 ask me UID and password for XI access
    <b>Problem 2:</b> I want to see message in XI (sxmb_moni)
    Thanks

    Hi Cemil,
    >>>>After sending it asks me userid and password for XI system. I give necessary UID and PASS. R/3 system says me sucessfully sent.
    check the RFC destination from R3 to XI (SM59)
    you will find the right one from your port (We21)
    you can also check step by step procedures
    for IDOC - XI in my book:
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Idoc to file problem.......... IDOC lost

    i have a idoc to file problem,
    the idoc is sent from R/3 to XI,
    the problem is IDOC is sent from R/3,
    it didnt reach to XI.....
    i have checked.......we05 in R/3, it gives a status 3,
    then i checked SM58 in R/3, it shows nothing,
    when i check in idx5 in XI, theres no trace of that idoc....and no trace of the scenario run in SXMB_MONI
    pls help, where can i trace the idoc.....
    pls help

    Hi sudeer,
    Did You Check It In WE19.(Test Tool For Idoc Processing)
    If Not Do The Following Steps:
    <u><b>Step1:</b></u>
      >>      Give Your Existing Idoc Number.
    <u><b>Step 2:</b></u>
      >>      Basic Type is Your Message type.
            Ex: MATMAS05 or CREMAS05.
    <u><b>Step 3:</b></u>
      >>      In Your Existing MATMAS05 or CREMAS05 Structure say EDIDC,
      >>      You Should Fill  Your Mapped Entries In Data Structure of EDIDC.
      >>      So that Those Fields Gets Framed as Segments.
    <u><b>Step 4:</b></u>
      >>      After Doing It goto  Menu Bar and Click Idoc And Goto  Edit Control Record.
    <u><b>Step 5:</b></u>
      >>      Now You Give Your Sender And Receiver Port Number Along With Your 
            Logical System And Message Type again its Your MATMAS05  or
           CREMAS05 .
    <u><b>Step 6:</b></u>
      >>      After Doing It Click Standard Outbound Processing.
    <u><b>Step 7:</b></u>
      >>      It Will Say what Happened To your Idoc.
    <u><b>Step 8:</b></u>
      >>     It Is For Sure That if This Processing Fails It Wont Go To XI..
    Regards,
    Dhayanandh .S
    Dont forget To Provide Points If Found Helpful...
    Message was edited by:
            DHAYANANDH SIVASANKARAN

  • RE:idoc inbound scenario "mapping issue"

    Hi experts,
    we r facing the problem in idoc inbound scenario, while to generate multiple idoc's.
    we need to generate the idoc's based on two fields, Location_code and Date. If any of the field is changing we need to generate the new idoc.
    below is the sender  payload :
    <row>
          <Date>20100111</Date>
          <Sign>+</Sign>
          <Tender_Code>ZSHT</Tender_Code>
          <Tender_Amount>1890.30</Tender_Amount> 
          <Location_Code>0000001000</Location_Code>
       </row>
       <row>
          <Date>20100112</Date>
          <Sign>+</Sign>
          <Tender_Code>ZSHT</Tender_Code>
          <Tender_Amount>1890.30</Tender_Amount>
          <Location_Code>0000001000</Location_Code>
       </row>
       <row>
          <Date>20100112</Date>
          <Sign>+</Sign>
          <Tender_Code>ZSHT</Tender_Code>
          <Tender_Amount>1890.30</Tender_Amount>
          <Location_Code>0000001001</Location_Code>
       </row>
       <row>
          <Date>20100112</Date>
          <Sign>+</Sign>
          <Tender_Code>ZSHT</Tender_Code>
          <Tender_Amount>4532.32</Tender_Amount>
          <Location_Code>0000001001</Location_Code>
       </row>
    for the above payload ,we need 3 idocs as below
    idoc1:
    Location_code>1000    Date->20100111
    idoc2:
    Location_code>1000    Date->20100112
    idoc3:
    Location_code>1001    Date->20100112
    under the third idoc fourth row should get repeated.
    at present we have the following mapping which is generating multiple idocs bsased on only location code, it's like
    Location_code-->removecontext-->sort-->splitbyvalue(valuechange)-->collapsecontext--->idoc
    rgds
    selvam

    Hi,
    Thanks Suraj , logic has worked but there is a simple issue , LOCATION_Code is mapped with SNDRPRN and RCVPRN of the EDI_DC40 segment when i m execuiting the payload it throws error for the second idoc generated , when the LOCATION_CODE changes this should also get updated to that field. Mapping for SDNPRN has been done like this.
    LOCATION_CODE --->removecontext-->|
                                         formatbyexample--->SNDRPRN
    idoc mapping logic---------------->|
    pl suggest...
    rgds
    selvam

  • Logical System in IDOC-XI scenario

    Hi,
         I need help to understand few things in IDOC-XI scenario, could any one help me in this regard.
        we use Adapter specific identifiers to map services, we have following type of identifiers 1) Sys.ID & Client No.  2) Logical System. 
    my questions are
    a) Are we use Logical System in B to B scenario ?
    b) Are we use LS in reference to the SAP system or Non SAP system ? if a non SAP system....how a non SAP system send an IDOC and why a non SAP system receive an IDOC ( conversion is possible in XI ) ?
    Thanks and Regards
    Mahesh.

    Hay Kumar,
    Logical systems can also be used for SAp sytems wich are not installed yet as a virtuall placeholder.
    a) yes. if on of your business is a non sap system or a propritery system that you developed yuo'll ue LS.
    b) non SAP system can send and recieve IDOCs. so it's possiable to get an IDOC from a system and turn it into an RFC for SAP or get an IDOC from an SAP system and then turn it into something else for another system.
    Have a Good One,
    Uri Lifshitz.

  • Issue in IDOC-File Scenario

    Hallo Everybody,
    In one of the requirements,for the interface design which involves IDOC-FILE scenario we have a req as:-
    Multiple IDOCs would be sent from SAP R/3 to SAP XI. Each IDOC can have 0-4 segments and for each segment a file needs to created.
    The files needs to be FTPed to a location, only if all the IDOCs have been processed successfully.
    Requirement:
    1) Even if a single IDOC fails,the files should not be FTPed. --> How do we handle this in XI.
    2) We need to send a notification from XI, in case any IDOC processing fails.
    3) How do we check in XI, if all the IDOCs have been processed successfully.
    Please suggest me with some good stategies to resolve this issue.
    Appreciations and Rewards in line.
    Regards,
    Younus

    Hi
    Are you planning to use BPM as it suits your requirement.
    To collect the idocs in small bunches refer
    Collecting IDocs without using BPM
    1) Even if a single IDOC fails,the files should not be FTPed. --> How do we handle this in XI.
    BPM will allow you to wait for the time all IDOC are processed
    2) We need to send a notification from XI, in case any IDOC processing fails.
    BPM exception handling will allow this functionality even to the exact field you want to send  notification
    3) How do we check in XI, if all the IDOCs have been processed successfully.
    Set Acknowledgment for IDOC's
    refer
    Posting multiple IDocs with Acknowledgement
    Thanks
    Gaurav

  • Issues in IDoc Sender Scenario:IDoc  with errors added

    Hi all
             Am working on an IDoc to JDBC scenario. In R/3 system, I have created distribution model, partner profile, RFC destination and port.The IDoc is generated and is sent to XI successfully. But in XI , there is no entry in SXI_MONITOR for this (unfortunately IDX5 is not available in the XI server! ;as of now). Instead an entry is made in WE05 and WE02 with stautus 56(IDoc with errors added). In the status record:
    status 56 : External segment name E2KOMG003 cannot be interpreted
    status 60 : Basic IDoc type COND_A03 could not be found.
    And the segments displayed in data record  are different from the segments in the data record of the IDoc generated at R/3. (say for E1KOMG at R/3, E2KOMG003 in XI).Earlier the flow was working fine and the DB table was updated successfully. And the entire stuff is believed to be 'unmodified' .
    Would any one help in resolving the issue.
    Thanks,
    Chilanka

    Hi,
    >>>>I have created partenr profile in R/3.Need I create a partner profile in XI for R/3 system?
    no you cannot create any partner profiles in XI
    for more about IDOC configuration in XI check :
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • Soap -- XI -- IDOC/RFC scenario

    Hello,
    I have a jsp page that working in tomcat server.
    I want to send values from jsp page to xi to r/3. I think it will have
    soap-- xi -- IDOC/RFC scenario
    Pls send me pdf /doc to implemet it
    Regards

    Hi,
    Please Refer the Following Links
    /people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
    /people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
    /people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi - Invoke Webservices using SAPXI
    /people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
    /people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2131 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/336365d3-0401-0010-9884-a651295aeaa9
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/336365d3-0401-0010-9884-a651295aeaa9
    Regards
    Khanna

  • IDoc- File scenario: can you explain thses acknowledgments?

    Hi,
    I have an idoc->file scenario. in sxmb_moni I can see a green "OK" mark for my message in acknowldgment status column. when I dblclick the message, I can see my original message and 2 acknowldgment messages under this one in the top left.
    1 acknowledgement is the OK one, the 2nd one is of type AckNotSupported.
    When I dlbclick the OK one ack and click the idocoutbound, I can see:
      <SAP:TABNAM>EDI_DC40</SAP:TABNAM>
      <SAP:MANDT>450</SAP:MANDT>
      <SAP:DOCREL>700</SAP:DOCREL>
      <SAP:DOCNUM>0000000000257842</SAP:DOCNUM>
      <SAP:DIRECT>2</SAP:DIRECT>
      <SAP:IDOCTYP>ALEAUD01</SAP:IDOCTYP>
      <SAP:CIMTYP />
      <SAP:MESTYP>ALEAUD</SAP:MESTYP>
    and when I dblclick the 2nd ack and IdocOutbound, I see:
      <SAP:MANDT>450</SAP:MANDT>
      <SAP:DOCREL>700</SAP:DOCREL>
      <SAP:DOCNUM>0000000000257862</SAP:DOCNUM>
      <SAP:DIRECT>2</SAP:DIRECT>
      <SAP:IDOCTYP>ALEAUD01</SAP:IDOCTYP>
      <SAP:CIMTYP />
      <SAP:MESTYP>ALEAUD</SAP:MESTYP>
      <SAP:MESCOD />
    450 is the client of my IE, not the sender SAP system.
    What should all this mean? What does each ack mean and why do I get 2 of them?
    When I check the Idoc no. in XI, there is no such IDoc. Where are these Idocs sent from?
    POINTS WILL BE ASSIGN FOR SURE FOR CORRECT ANSWER.
    Thanks, Olian

    green:
    hoplist
    <?xml version="1.0" encoding="UTF-8"?>
    <!-- Response -->
    <SAP:HopList SOAP:mustUnderstand="1" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
       <SAP:Hop timeStamp="2008-06-10T21:15:07Z" wasRead="true">
          <SAP:Engine type="IS"/>
          <SAP:Adapter namespace="http://sap.com/xi/XI/System">IDOC</SAP:Adapter>
          <SAP:MessageId>48499DB8-21B6-0329-E100-00000A320B33</SAP:MessageId>
          <SAP:Info>ARTMAS.0000000000026370:20080610211506</SAP:Info>
       </SAP:Hop>
       <SAP:Hop timeStamp="2008-06-10T21:15:07Z" wasRead="true">
          <SAP:Engine type="IS">is.12.shlxiqcis1</SAP:Engine>
          <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
          <SAP:MessageId>48499DB8-21B6-0329-E100-00000A320B33</SAP:MessageId>
          <SAP:Info>3.0</SAP:Info>
       </SAP:Hop>
       <SAP:Hop timeStamp="2008-06-10T21:15:13Z" wasRead="true">
          <SAP:Engine type="AE">af.xiq.shlr3qdbs3</SAP:Engine>
          <SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
          <SAP:MessageId>48499DB8-21B6-0329-E100-00000A320B33</SAP:MessageId>
          <SAP:Info/>
       </SAP:Hop>
    </SAP:HopList>
    content
    <?xml version="1.0" encoding="UTF-8"?>
    <!-- Response -->
    <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
       <SAP:TABNAM>EDI_DC40</SAP:TABNAM>
       <SAP:MANDT>350</SAP:MANDT>
       <SAP:DOCREL>700</SAP:DOCREL>
       <SAP:DOCNUM>0000000000258080</SAP:DOCNUM>
       <SAP:DIRECT>2</SAP:DIRECT>
       <SAP:IDOCTYP>ALEAUD01</SAP:IDOCTYP>
       <SAP:CIMTYP/>
       <SAP:MESTYP>ALEAUD</SAP:MESTYP>
       <SAP:MESCOD/>
       <SAP:MESFCT/>
       <SAP:SNDPOR>SAPXIQ</SAP:SNDPOR>
       <SAP:SNDPRN>SHLSYSQAS</SAP:SNDPRN>
       <SAP:SNDPRT>LS</SAP:SNDPRT>
       <SAP:SNDPFC/>
       <SAP:RCVPOR>SAPR3Q</SAP:RCVPOR>
       <SAP:RCVPRN>R3QCLNT330</SAP:RCVPRN>
       <SAP:RCVPRT>LS</SAP:RCVPRT>
       <SAP:RCVPFC/>
       <SAP:TEST/>
       <SAP:SERIAL/>
       <SAP:EXPRSS/>
       <SAP:STD/>
       <SAP:STDVRS/>
       <SAP:STATUS>03</SAP:STATUS>
       <SAP:OUTMOD/>
       <SAP:SNDSAD/>
       <SAP:SNDLAD/>
       <SAP:RCVSAD/>
       <SAP:RCVLAD/>
       <SAP:STDMES/>
       <SAP:REFINT/>
       <SAP:REFGRP/>
       <SAP:REFMES/>
       <SAP:CREDAT>0000-00-00</SAP:CREDAT>
       <SAP:CRETIM>00:00:00</SAP:CRETIM>
       <SAP:ARCKEY/>
    </SAP:IDocOutbound>
    Red one:
    <?xml version="1.0" encoding="UTF-8"?>
    <!-- Response -->
    <SAP:HopList SOAP:mustUnderstand="1" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
       <SAP:Hop timeStamp="2008-06-10T21:15:07Z" wasRead="true">
          <SAP:Engine type="IS"/>
          <SAP:Adapter namespace="http://sap.com/xi/XI/System">IDOC</SAP:Adapter>
          <SAP:MessageId>48499DB8-21B6-0329-E100-00000A320B33</SAP:MessageId>
          <SAP:Info>ARTMAS.0000000000026370:20080610211506</SAP:Info>
       </SAP:Hop>
       <SAP:Hop timeStamp="2008-06-10T21:15:07Z" wasRead="true">
          <SAP:Engine type="IS">is.12.shlxiqcis1</SAP:Engine>
          <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
          <SAP:MessageId>48499DB8-21B6-0329-E100-00000A320B33</SAP:MessageId>
          <SAP:Info>3.0</SAP:Info>
       </SAP:Hop>
       <SAP:Hop timeStamp="2008-06-10T21:15:13Z" wasRead="true">
          <SAP:Engine type="AE">af.xiq.shlr3qdbs3</SAP:Engine>
          <SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
          <SAP:MessageId>48499DB8-21B6-0329-E100-00000A320B33</SAP:MessageId>
          <SAP:Info/>
       </SAP:Hop>
    </SAP:HopList>
    content
    <?xml version="1.0" encoding="UTF-8"?>
    <!-- Response -->
    <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
       <SAP:TABNAM>EDI_DC40</SAP:TABNAM>
       <SAP:MANDT>350</SAP:MANDT>
       <SAP:DOCREL>700</SAP:DOCREL>
       <SAP:DOCNUM>0000000000258083</SAP:DOCNUM>
       <SAP:DIRECT>2</SAP:DIRECT>
       <SAP:IDOCTYP>ALEAUD01</SAP:IDOCTYP>
       <SAP:CIMTYP/>
       <SAP:MESTYP>ALEAUD</SAP:MESTYP>
       <SAP:MESCOD/>
       <SAP:MESFCT/>
       <SAP:SNDPOR>SAPXIQ</SAP:SNDPOR>
       <SAP:SNDPRN>SHLSYSQAS</SAP:SNDPRN>
       <SAP:SNDPRT>LS</SAP:SNDPRT>
       <SAP:SNDPFC/>
       <SAP:RCVPOR>SAPR3Q</SAP:RCVPOR>
       <SAP:RCVPRN>R3QCLNT330</SAP:RCVPRN>
       <SAP:RCVPRT>LS</SAP:RCVPRT>
       <SAP:RCVPFC/>
       <SAP:TEST/>
       <SAP:SERIAL/>
       <SAP:EXPRSS/>
       <SAP:STD/>
       <SAP:STDVRS/>
       <SAP:STATUS>03</SAP:STATUS>
       <SAP:OUTMOD/>
       <SAP:SNDSAD/>
       <SAP:SNDLAD/>
       <SAP:RCVSAD/>
       <SAP:RCVLAD/>
       <SAP:STDMES/>
       <SAP:REFINT/>
       <SAP:REFGRP/>
       <SAP:REFMES/>
       <SAP:CREDAT>0000-00-00</SAP:CREDAT>
       <SAP:CRETIM>00:00:00</SAP:CRETIM>
       <SAP:ARCKEY/>
    </SAP:IDocOutbound>

  • 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

  • Doubt about RFC Destination in FILE to IDOC Async scenario

    hi
    In FILE-XI-IDOC Async Scenario we are creating RFC Destination in R/3 and XI.
    For Asyn we don't want response But We are Creating RFC Destination in R/3 also.
    Any specific reason.
    Thanks in advance.

    First you need to have a clear understading of how the idoc adapters works.
    In xi we create rfc destination and specify that in the port maintenance on the idoc adapter so that we can establish a connection to the sender / receiver system which contains the IDOC METADATA (IDX2) that is required by the idoc adapter to convert the native idoc into idoc xml format.
    In R/3 as sender we create rfc destination so that when the idoc has to be transported to the xi system first it will be sent to trfc port that rfc desination that  u define the trfc port contains that the target system address(IP) and logon parameters req.So idoc can be sent to the desired destination.
    In R/3 as a receiver to facilitate communication we define rfc dest, partner profile and specify the inbound parameters so that idoc can be posted.
    Hope this answers your ques.
    cheers
    *Raj*
    *POINTS IF SATISFIED WITH ANSWER.

  • File to idoc bypass scenario

    hi all
                I am doing file to idoc bypass scenario....i have to send file containing
    EDIDC segment to respective idoc.I have used the idoc name as interface and its also successfully picking the file but while receiving the idoc receiver is showing some error.in sxmb_moni its showing error as obligatory field eiedk01 is missing while its persent in the pay roll of the messege...........please guide me in bypaas
    can i check my message expect sxmb_moni .
    my receiver adapter is <b>IDOC</b>
    sender adapter is<b> XI........</b>
    regards
    saurabh sharma

    Look into the replies by Bhavesh in this thread.
    https://forums.sdn.sap.com/click.jspa?searchID=3098859&messageID=3484218
    Regards,
    Jai Shankar

  • IDOC - SOAP scenario

    Hi Guys,
    I have configured the IDOC-SOAP scenario and i am sending to the target business partner with the soap receiver adapter.
    I did not get any wsdl from the business partner instead i got the xml structure, target url and soap action. I have created a xsd for the given xml and send the data to the business partner.
    The data is reacing the target system but the xml document has error saying "invalid at the top level of the document" and no xml is seen. I also get an acknowldegment error in sxmb_moni as
    OUTBINDING  CO_TXT_Routing_Back_Error
    Error occured during back routing, error in communication channel
    any help would be appreciated
    Thanks,
    Raj

    I think this comes because XI requests Acknowledgement-IDocs by default. In many cases nobody processes these IDocs and so you get this error. Have a look at OSS-note 777175:
    You are using Exchange Infrastructure 3.0 and receive IDocs using the IDoc
    adapter. You want to be able to request acknowledgments separately in the
    XI for each sending system and interface. In the IDXNOALE exception table,
    you can deactivate acknowledgments for certain systems or interfaces.
    Previously, you could only maintain the table with transaction SE16.
    Report IDX_NOALE is delivered with Support Package 10. With the report, you
    can add, delete and display table entries.
    Report IDX_NOALE is extended with additional functionality as of Support
    Package 11. This allows a sender system to request or deny acknowledgements
    for all message types centrally. You can set exceptions to this central
    setting by message type. Generic exceptions (for example, message type
    'ORD*') are not supported. Entries that are already present in the table
    are unchanged.
    To perform these activities, you need the authorization to maintain IDoc
    metadata (Object 'S_IDOCMETA' ID 'ACTVT' FIELD '02').
    Hope this helps.

  • IDOC-Database Scenario

    Dear All,
    I am working on IDOC -  Database scenario.
    Below is the scenario:
    u2022     The data received through the IDocs will be uploaded into respective temporary tables in Target SQL Sytem by means of stored procedures.
    u2022     The data stored in temporary tables are picked up and distributed to various other main tables by the job running at Target SQL server.
    1) Can I call directly Stored procedures from JDBC Adapter?
    If so, can anyone help me in providing some pointers on this?
    Thanks
    Babu

    For sending IDoc to XI we need to write one ABAP program to trigger the IDoc.
    We will create the Port and partner profiles based on that the XI takes the IDoc.
    We will write the update SQL statement in the Receiver Communication channel
    http://help.sap.com/saphelp_nw04/helpdata/en/64/ce4e886334ec4ea7c2712e11cc567c/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/frameset.htm
    The above document gives a good insight towards the understanding of the JDBC adapter.
    How can i test the whole integration?
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e573e690-0201-0010-e098-f90e8dadc70a
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0111fef-d311-2a10-c0b9-f33a49c1f2e5
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3a67c790-0201-0010-89aa-d27d97dd1374
    http://help.sap.com/bp_bpmv130/Documentation/Operation/TuningGuide.pdf

Maybe you are looking for

  • Way to convert Appleworks 5 docs to Pages

    I have hundreds and hundreds of word processing documents in Appleworks that can not be opened by Pages using OS 10.7.5. These documents go back many years. What's the best way to convert them into Pages documents? My wife has a machine running OS 10

  • On-line keynote platform

    Is anyone aware of an on-line teleconference provider that allows attendees to see a Keynote presentation in PLAY mode?  Go-to-meeting doesn't have program-specific options for the Mac so all they can see is the desktop - even when Keynote is in full

  • Can't connect to Express Edition 11g by sql developer

    hello, i installed the 11g edition and try to connect to it by sql developer. it didn't work, then I noticed there was an older version (10g) on the laptop. So i removed both, and installed the 11g version, but still it doesn't work. My laptop runs o

  • How to show an alert

    Hi: Apex 4.1 I have a report that, when it runs, I want an alert to show if one of the report columns contains a specific value. Can anyone suggest how I might do this? Thanks.

  • The weight of effects exported to PDF

    OS 10.6, CS5 Hi everyone, I have some newsletter documents (8-16 pages) in CS5 that have a few text frames  with drop shadow and bevel effects applied. The resulting PDF (exported using some custom settings, but based on "smallest file size") is 7.5M