IDOC "Tunneling"

Hello all,
We are currently implementing a IDOC->XI->JMS scenario.
We would like to use the IDOC Tunneling option:
SXMB_ADM -> Integration Engine Configuration
IDoc -> XML Conversion = 2 or 0
2 questions:
When setting the XML_Conversion parameter to 0 XI seems to be ignoring our request and the IDOC is still being converted to XML.
Does anybody have any idea why this happens?
When setting the XML_Conversion parameter to 2 how do we get the service NOT to request the IDOC conversion?
Thanks in advance.
Claus

Hi Holger,
Thank You for Your answer.
We have tried the IDOC->XI->IDOC scenario.
However the payload shows that the IDOC is converted to XML.
Can we expect to see a non-converted IDOC in the payload if we use the XML_CONVERSION parameter value 0 or 2?
Regards
Claus Borre Nielsen

Similar Messages

  • Idoc to idoc scenario with idoc tunneling

    IN idoc to idoc scenario with idoc tunneling  the XML_CONVERSION parameter to value 2  is set whish means An IDoc is converted to IDoc-XML if requested by the service
    I want to know where we specify this and how we specify?

    1. /people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
    2. /people/alessandro.guarneri/blog/2006/03/05/managing-bulky-flat-messages-with-sap-xi-tunneling-once-again--updated
    ref these weblogs.
    It is given under;
    <i>TCODE - SXMB_ADM
    - Integration Engine configuration
    - set the XML_CONVERSION parameter to value 2</i>

  • IDoc tunneling (Parameter  XML_CONVERSION)

    The parameter in the SXMB_ADM transaction defines whether the IDoc is transported as a table and is not converted to IDoc-XML in the IDoc adapter. This is only recommended if IDocs are received and sent as IDocs in the Integration Server. If none of the services in the Integration Engine use IDoc-XML, you can avoid unnecessary conversion from and to XML, thereby improving system performance.
    Possible Values
    '<b>0</b>' Every IDoc is saved as a table; no IDoc-XML conversion.
    '<b>1</b>' Every IDoc is converted to IDoc-XML.
    '<b>2</b>' An IDoc is converted to IDoc-XML only <i>if requested by the service</i>.
    The question is: does anybody know what "<i>if requested by the service</i>" exaclty means ?
    Regards,
    Sandro

    Think about a scenario SAP-XI -JMS (or Flat file) vice versa . I will do the transformation with ABAP-Mapping in both direction and theres no need for receiveing an XML-Stream from IDOC-Adpater or send an XML-stream to IDOC-Adpater.
    We would receive a better performance if we could avoid the expensive XML-Transformation.
    There is a check of an existing Mapping for Sender-Message in the Table SMPPREL3 .
    There could be an special XML-flag in this Table and in the Receiver-Determination you could set this flag or not . 
    XI uses CL_IDX_IDOC_RESOURCE for the IDOC-Tunnel. In this class  EDIDC and EDIDD are serialized in an XSTRING . In my ABAP-Mapping first i would check Content_Type via  PARAM->GET.  For transforming the binary Content into  EDIDC and EDIDD a static method should be implemented by SAP in CL_IDX_IDOC_RESOURCE  . I think I could implement such a method myself, but its risky if SAP changes their ITAB_TO_BINARY-method in an incompatible way.  
    In the XI-SAP -direction  I would like  to set the content_type in ABAP-Mapping to bin and convert the EDIDC and EDIDD  in X-string  (like in CL_IDX_IDOC_RESOURCE ->ITAB_TO_BINARY ).
    Regards Josef

  • IDoc-Tunnel - IDoc is rejected

    Hi guys,
    well i have an internal EDIserver which will send IDoc native via XI (IDoc-Tunnel) to a R/3 target System. Therefore for EDIserver a RFC-Destination of type TCP/IP exists where a registered Serverprogram is applied, also with given gateway values from the XI-System.
    After configuring an IDoc-Channel in the Integration Directory the testing of the SM59 RFC-Destination works fine. Well because of Michal's Blog for IDoc-Tunneling i already did the configuration of the integration engine (XML CONVERSION).
    Ok i imported the IDocs in IR, announced them in IDX2 and did the ID-Part with Sender-Agreement and so on.
    But when we try to send an IDoc from EDI to XI we get following error:
    <i>rfc_error_info.message="No service for system SNDPOR, client 100 in Integration Directory"</i>
    The EDI-Consult thinks that he needs the Header-data from the IDoc like RCVPOR, RCVPRT, RCVPRN but i think we don't.
    So where could be the problem?! perhaps at the registered server program of the EDIServer?!
    br

    Hi Udo, thx for ur reply.
    Well that might be the problem. I have applied an EDI_Test in SLD for EDIServer but the EDI-Consultant might not have used this field so that there is a standard value in it (SNDPOR) which indicates what kind of info is needed there.
    So he should enter EDI_Test for let XI accept the IDoc when it is posted!
    br

  • IDoc-Tunneling -- No Receiver Agreement

    Hi, i am trying to do the IDoc-Tunneling scenario from Michal.
    Well everything looks fine so far except that i get following error:
    +<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIServer</SAP:Category>
      <SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_NOT_FOUND</SAP:Code>
      <SAP:P1>-Q01CLNT010</SAP:P1>
      <SAP:P2>0000010007-,urn:sap-com:document:sap:idoc:messages.DELFOR.DELFOR01</SAP:P2>
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Es konnte keine Empfängervereinbarung für den Sender -Q01CLNT010 zum Empfänger 0000010007-,urn:sap-com:document:sap:idoc:messages.DELFOR.DELFOR01 gefunden werden</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>+
    Well i have Receiver Agreement that looks like:
    Sender Service: Q01CLNT010
    Receiver Service: EDI
    Interface: DELFOR.DELFOR02
    Namespace: urn:sap-com:document:sap:idoc:messages
    CC: IDOC_RECEIVER_EDI
    In this Receiver-CC i also activated
    - Apply Control Record Values
    - Take sender from payload
    However, i have no clue what is wrong.
    Can somebody help? br Jens

    Hi Jens
    (6) Error Category - CO_TXT_OUTBINDING_NOT_FOUND
    The problem is in Technical routing.
    Check whether the receiver determination and interface determination objects are active in change lists tab. If they are not active, activate the objects.
    check the if the receiver determination and interface determination objects are referenced to the same namespace or not. Sender and receiver interface objects should always refer to the same Namespace.
    Please refer the follwoing blog for details
    <b>/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
    Thanks
    AbhishekMahajan
    *****Please reward points if helpful*********

  • IDoc Tunneling and XML_CONVERSION

    Hi,
    I'm developing a File 2 IDoc / IDoc 2 File Scenario.
    The Partner who receives and send files wants to use the idoc flat table structure.
    I noticed that wasn't so easy to convert IDoc XML to flat file, till i found IDoc Tunelling which perfectly fits my scenario!
    The research i've done, explains that we just have to set the IDOC / XML_CONVERSION  parameter:
    Possible Values
    <i>'0' Every IDoc is saved as a table; no IDoc-XML conversion
    '1' Every IDoc is converted to IDoc-XML
    <b>'2' An IDoc is converted to IDoc-XML if requested by the service</b></i>
    But, setting value to '2', how can i control if i want or not Xml conversion to occur? Is a setting made in R/3 or XI?
    I have scenarios where i really need XML (to use mapping features). Value 2 looks perfect, but where is this controlled?

    Hi Jose,
    Sounds good idea and approach..
    Check out this blog by Michal..you will get all your answer on idoc tunelling..
    /people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
    Hope this will help.
    Let me know if you need more details.
    Nilesh

  • IDoc Tunnelling

    All,
       I was going through the Michals Blog for IDoc tunnelling and I'm little confiused here. As per the blog,
    setting the "XML_CONVERSION parameter to value 2" enables the IDoc tunnelling.
    1) Does all the IDocs coming out of R3 will be in the flat file format.
    2) Also the blog says as per SAP help "2 - An IDoc is converted to IDoc-XML if requested by the service" - Can someone tell me what service request that we need to use for IDoc - XML conversion with a value of 2?
    Thanks.

    My question is
    1) if we set the XML_Conversion parameter to 2, are all the IDocs coming out of ECC will be in the flatfile   
       format?
    2) If all the IDocs coming into XI are flatfile's, what service do we need to request for the IDoc to be in IDoc XML format with the XML_Conversion parameter set to "2"
    Thanks.

  • Tunnelling in IDOC To IDOC and payload size

    Hi XI Experts,
    We runned in a PI 7.0 SP13 an IDOC To IDOc scenario with non conversion XML (Tunnelling with IDOC/XML_CONVERSION parameter set). Refer to Michal Krawczyk blog : /people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
    All seems good : payload in message monitoring is flagged as 'application/x-sap.idoc.bin' et scenario works fine.
    But we have 2 questions :
    Q1 : in monitoring, payload document is displaied in right bottom window like XML representation....like an XML-converted document.
    Q2 : value parameter 'SIZE_PAYLOAD' in message with non conversion XML is greater than....in conversion XML ?!?....
    Thanks for yours responses.
    Etienne

    Hi
    Please find here with you the clarification,
    *Q1 : in monitoring, payload document is displaied in right bottom window like XML representation....like an XML-converted document.
    the value is set to XML_CONVERSION parameter to value 2
    a) 0 - Every IDoc is saved as a table; no IDoc-XML conversion
    b) 1 - Every IDoc is converted to IDoc-XML
    c) 2 - An IDoc is converted to IDoc-XML if requested by the service
    Here the IDOC is internally be treated as IDOC-XML as you would be using the Business systems with SAP. And it depends upon the services.
    Q2 : value parameter 'SIZE_PAYLOAD' in message with non conversion XML is greater than....in conversion XML ?!?....
    The SIZE_PAYLOAD will be always more with non-conversion XML includes the header details also..(I am not sure with it).
    Its better that you copy the XML Payload and save on local PC. Then check with its size.
    thanks
    Swarup

  • Sender Namespace and Sender Interface in the IDOC to IDOC scenario

    My question maybe very basic...
    It is SAP IDOC to SAP IDOC scenario.
    Lets assume that I have done config in XI for:
                 Sender  = A,
                 Interface = B,
                 Namespace = C.
    My question is:
    Is there a place in the source system or somewhere to point that
    when an IDOC e.g. DEBMAS is triggered in the source system,
    then the Interface should be B and  Namespace should be C in the xml file ?
    Cheers
    Agnie

    Hi Agnieszka,
         Check these threads/blogs from you may get some help:
    /people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
    Idoc-to-idoc scenario
    IDoc to IDoc scenario  necessary configuration steps
    For A-Z help on IDOC, you can refer Michal's book:
    <a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi IDoc Business Scenarios with SAP XI</a>
    Regards,
    Subhasha Ranjan

  • IDoc to Flat File in SAP PI 7.11

    Hi Experts,
    I am working on PI 7.11 and I have scenario from Idoc to Flat File.
    Idoc is posted from source side R/3 system.My requirement is "With out Converting the Idoc structure to XML Structure  i want to send the data to Target system i.e. File system.
    But the structure of the target structure is different from source structure.
    My questions are:
    1). Is it Possible to send the data to Target system without converting Idoc structure in to xml format through our PI 7.11 ?
    2). If possible please provide me the way that executes in the Interface is?
    Could you please provide the Inputs.
    Best regards,
    satya.T
    Edited by: satyatanuku on May 24, 2010 3:26 PM
    <Moved from Trial, Preview~ forum>
    Edited by: Prateek Raj Srivastava on May 25, 2010 1:02 PM

    Hello Folks ,
    I am also facing the same scenario please provide me any options to achieve this scenario .
    I am searched in Forums of SDN but no inputs or blogs available.
    Let me know i am having one solution is it right or wrong ?
    we have to achieve this IDOC Tunneling .... is it right  friends ?
    Still inputs required....
    Regards,
    Ravi.

  • 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

  • Sending Production orders via Idoc to external system

    Hello,
    I want to generate an Idoc for a production order when releasing or saving it. Is there an output control where I define the message link the purchase order?
    Thanks!!

    By IDoc-Tunneling i am thinking of just putting the IDoc through XI without transformation in XML (like in one blogs of Michal). Because of this blog there seems only to be one step in IR - import IDoc. in ID there are the mandatory steps.
    But if i want the ext. Admin to tell what parameters i need to communicate with the ext. system i have doubts in telling him just the IP and perhaps a program which we have to start via RFC configured in XI.
    regards

  • PI 7.0 settings to avoid IDOC conversion to XML

    Hi Experts,
    In order to have idoc tunneling in PI 7.0 I know I have to:
    --set the parameter in IE: XML_CONVERSION = 2.
    --add entry in the exception table IDXIDOCINB using the report IDX_SELECT_IDOCTYP_WITHOUT_IS
    Actually performing the 2nd step I can only add idocs from a List.but unfortunately we need to enter idocs out of the list.
    Can we extend the list ?
    How?
    Regards,
    Giamma

    hi,
    >>--set the parameter in IE: XML_CONVERSION = 2.
    >>--add entry in the exception table IDXIDOCINB using the report IDX_SELECT_IDOCTYP_WITHOUT_IS
    these are completely different things
    a) XML_CONVERSION  - for tunneling
    b) IDX_SELECT_IDOCTYP_WITHOUT_IS - for processing IDOC without XI
    (so as normal IDOCs with WE20 etc.)
    so first you need to decide that do you want - a) or b)
    obviously those 2 parameters are described in my book:
    www.sap-press.com/product.cfm?account=&product=H1935
    Regards,
    Michal Krawczyk

  • IDOC to flat file without XML conversion

    Hi,
    I want to implement a scenario like this:
    IDOC --> XI --> flat file
    The flat file has to have the IDOC structure as you have when you write an IDOC to the R/3 file port. But we want to have this process running through XI.
    When you use the IDOC Adapter the IDOC is converted to XML first, which is time consuming. So this I want to skip this step.
    So is it possible to receive the IDOC directly in XI without converting it to XML? How should this process be designed.
    Ron

    Ron
    Looks like you need IDOC tunneling. It is possible by making a configuration parameter.
    You can find more information in http://help.sap.com/saphelp_nw04/helpdata/en/ab/bdb13b00ae793be10000000a11402f/content.htm
    While you try it, I will try to simulate this requirement in our system and let you know the result.
    KK

  • Integration of Idoc to OAGIS XML...

    Hi All,
    Can any one please help me how to integrate IDOC to OAGIS XML for Delivery alert in sap PI.
    any document or steps to integrate would be really helpful.
    As a start i have done the below steps :
    1. downloaded all the XSD file from OAGIS site.
    2. imported the XSD as external system into PI.
    3. imported required idoc into sap PI.
    4. created service interface for external system (OAGIS XSD).
    5. during mapping there multiple nodes that has to be selected in target, but i think this is wrong because mapping can only be done with single node.
    i am stuck with the mapping of idoc to OAGIS.
    any help would be appreciated.
    Thanks & Regards,
    akshay ruia

    Hi,
    I managed to Integrate Idoc to OAGIS asynchronously, but now i am getting an error for "No party or service found" in SXMB_MONI. Please find the trace below :
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--
    Message Branch According to Receiver List
    -->
    - <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: SAPUSER</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="1" type="T">Syntax-Check-Flag X</Trace> 
    <Trace level="1" type="T">IDoc-Tunnel-Flag X</Trace> 
    <Trace level="1" type="T">Queueid</Trace> 
    - <Trace level="1" type="B" name="IDX_IDOC_TO_XML"> 
    <Trace level="1" type="T">Docnum 0000000001010778</Trace> 
    <Trace level="1" type="T">Get the Metadata for port SAPEED</Trace> 
    <Trace level="1" type="T">Convert Segment-Definitions to Types</Trace> 
    <Trace level="1" type="T">Make Syntax check of current IDoc</Trace> 
    </Trace>
    <Trace level="1" type="T">party normalization error: scheme = ALE#KU#WE</Trace> 
    <Trace level="1" type="T">Set Receiver Routing-object</Trace> 
    <Trace level="1" type="T">---------------------------------------------</Trace> 
    <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-SET_IDOC" /> 
    <Trace level="1" type="T">Exit Function IDX_INBOUND_XMB</Trace> 
    <Trace level="1" type="T">Work Process ID: 3140</Trace> 
    - <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-GETBLOBDATA"> 
    <Trace level="1" type="B" name="CL_IDX_IDOC_RESOURCE-ITAB_TO_BINARY" /> 
    </Trace>
    <Trace level="1" type="T">Message ID = 94DE801F74491ED48E831FB43F6DF2A8</Trace> 
    - <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"> 
    <Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace> 
    <Trace level="1" type="T">Hop engine name = is.00.sapsrv5</Trace> 
    <Trace level="1" type="T">Hop engine type = IS</Trace> 
    <Trace level="1" type="T">Hop adapter name = XI</Trace> 
    <Trace level="1" type="T">Hop adapter namespace = http://sap.com/xi/XI/System</Trace> 
    <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" /> 
    <Trace level="1" type="T">system-ID = EP1</Trace> 
    <Trace level="1" type="T">client = 001</Trace> 
    <Trace level="1" type="T">language = E</Trace> 
    <Trace level="1" type="T">user = SAPUSER</Trace> 
    <Trace level="1" type="Timestamp">2014-09-09T12:01:12Z CET</Trace> 
    <Trace level="1" type="T">ACL Check is performed</Trace> 
    <Trace level="1" type="T">XML validation is executed</Trace> 
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" /> 
    - <!-- ************************************
    -->  
    <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="1" type="T">Queue name : XBTI0003</Trace> 
    <Trace level="1" type="T">Going to persist message</Trace> 
    </Trace>
    <Trace level="1" type="T">Generated prefixed queue name =</Trace> 
    <Trace level="1" type="T">Schedule message in qRFC environment</Trace> 
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" /> 
    - <!-- ************************************
    -->  
    <Trace level="1" type="T">--start determination of sender interface action</Trace> 
    <Trace level="1" type="T">select interface CARNOT.DELVRY03</Trace> 
    <Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace> 
    <Trace level="1" type="T">--start determination of receiver interface action</Trace> 
    <Trace level="1" type="T">Loop 0000000001</Trace> 
    <Trace level="1" type="T">ALE receiver ALE#KU#WE found during inbound processing. Quit determination of receiver interface action.</Trace> 
    <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" /> 
    <Trace level="1" type="T">Work Process ID: 3864</Trace> 
    <Trace level="1" type="T">Exception from packaging: No messages for constructing a package available.</Trace> 
    <Trace level="1" type="T">Continue single processing</Trace> 
    <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace> 
    <Trace level="1" type="T">system-ID = EP1</Trace> 
    <Trace level="1" type="T">client = 001</Trace> 
    <Trace level="1" type="T">language = E</Trace> 
    <Trace level="1" type="T">user = SAPUSER</Trace> 
    <Trace level="1" type="Timestamp">2014-09-09T12:01:12Z CET</Trace> 
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" /> 
    - <!-- ************************************
    -->  
    <Trace level="1" type="T">>>>PID delete old pid determination coding</Trace> 
    - <Trace level="1" type="B" name="PLSRV_XML_VALIDATION_RQ_INB"> 
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV"> 
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"> 
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_VALIDATION-ENTER_PLSRV"> 
    <Trace level="1" type="T">Reading sender agreement</Trace> 
    <Trace level="1" type="T">Message does not contain a sender agreement</Trace> 
    <Trace level="1" type="T">Inbound validation by Integration Engine does not take place</Trace> 
    </Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" /> 
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION"> 
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV"> 
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"> 
    - <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV"> 
    <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace> 
    <Trace level="1" type="T">Cache content is up to date</Trace> 
    <Trace level="1" type="T">No Relation found - accept given Receivers.</Trace> 
    </Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" /> 
    - <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION"> 
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV"> 
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"> 
    - <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV"> 
    <Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N</Trace> 
    <Trace level="1" type="T">Cache content is up to date</Trace> 
    <Trace level="1" type="T">...There is no Interface Determination configured for receiver party 0000003271 and receiver service</Trace> 
    </Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" /> 
    <Trace level="1" type="B" name="PLSRV_RECEIVER_MESSAGE_SPLIT" /> 
    - <!-- ************************************
    -->  
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV"> 
    <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" /> 
    - <!-- ************************************
    -->  
    - <Trace level="1" type="B" name="CL_XMS_PLSRV_RECEIVER_SPLIT2->ENTER_PLSRV"> 
    <Trace level="1" type="T">number of receivers: 1</Trace> 
    <Trace level="1" type="T">Single-receiver split case</Trace> 
    <Trace level="1" type="System_Error">Party and service not defined</Trace> 
    </Trace>
    </Trace>
    <Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace> 
    <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" /> 
    - <!-- ************************************
    --> </SAP:Trace>
    Please help with the solution.
    Thanks & Regards,
    Akshay Ruia

Maybe you are looking for

  • Error 21, I have tried everything, nothing seems to work

    Today I tried to upgrade my iPhone's firmware to 5.0.1 but ERROR 21 came up so I tried everything to fix it but nothing seems to work at all. Plus my iPhone is on DFU mode so I can not use it either. Please help me.

  • Mail says my e-mail is junk

    I have a rule that the domain @test.com is OK so everything that comes from this domain is not junk. I get e-mail from this domain and mail always flags it as junk. How can I get the "rules" to accept that anything from this domain is OK? The rule sa

  • Splitting iTunes Library Based On Content

    Hello, Is there any tool or any method to split where iTunes stores certain types of files. I would like to have iTunes store all music on my iDisk but keep all video content on my local hard drive. Preferably, even if I buy music I would like it to

  • MacBook MB466LL/A has loose connection Any suggestions?

    MacBook MB466LL/A has loose connection in screen producing line down the middle, if I mess with it (or even wedge something between hinge by the power button) it goes away. Repair center wants to replace whole thing which I can not afford. Any sugges

  • Status of delivery of mail

    Hi Friends, Here i am copying my code. everything is wroking fine. but if i give wrong id also its showing the delivery status message delivered only. It is not showing the not delivered and partially delivered status. Plz help me any one. Thanks in