Response payload missing in SXMB_MONI

Dear All,
I have a query related to Response payload in SXMB_MONI.
I am using IDOC-XI-FILE & FILE-XI-IDOC asynchronous scenario . Output xml files and idocs are generated properly.
<b>In SXMB_MONI,when I click on successful processed message it is not showing me the Response payload-MainDocument(application/xml).</b>
<b>I was able to see response payload in my Development server but in production server I am not able to see the reponse payload.</b>
I am using SP15.
I tried to activate services also using t-code SICF but not able to solve the problem yet.
Can anybody suggest me solution to this problem.

Hi Prabhat,
we had the same problem when we upgraded to SP15, we consulted SAP and they came up with the answer that this is a known bug in SP15. This seems to have been fixed in SP16.
Regards,
Roberto
See Re: SXMB_MONI does not show payload after upgrade to SP15
Message was edited by: Roberto Viana

Similar Messages

  • Response payload in SXMB_MONI is missing

    Dear All,
    I have a query related to Response payload in SXMB_MONI.
    I triggered an IDOC and XI has sucessfully generated files in my Outbound folder .
    <b>When I see sxmb_moni , it is showing message successfully processed message . When I click on successful processed message it is not showing me the Response payload-MainDocument(application/xml) in SXMB_MONI.</b>
    PLease help me to find out the solution immediately.
    Thanks in advance.
    Regards
    Prabhat

    Hi,
    >>>1) I am not able to see "Payload" under Response in SXMB_MONI in Production server SP15.
    can you see the payload before CALL adapter service?
    >>>>2) In runtime workbench (Production server sp15) when I click on "Message Monitoring" it is showing error 404 not found.
    go to TCODE - SICF and test this service
    /sap/bc/gui/sap/its/webgui
    navigate from it to the TCODE - SXI_monitor
    that's how the message payload is displayed in RWB
    BTW
    >>>My support pack in development server was sp14 and in production it is SP15.
    I just hope your test XI server was SP15
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

  • Response payload in sxmb_moni

    hi ,
    in my XML Message in sxmb_moni the response payload is missing.
    and this is happening only for one scenario and it is working fine for other interfaces.
    can some one help me the structure of XML message is depend on which configuration exactly?
    Thanks

    Hi,
    Go to RWB->Message Monitoring  and check for the messages.
    Also test your message Mapping with the help of Live datat from SXMB_MONI.
    Is your scenario is Synchronous.
    Regards,
    Moorthy

  • Missing response payload in IE

    Hi,
    System:
    PI 2004s SP 23
    Problem:
    Integration engine does not receive payload from adapter engine.
    Scenario:
    Synchronous scenario
    proxy -> xi -> soap
    Description:
    This is an old scenario that have been working fine for years but after upgrade from SP 14 to SP 23 it no longer works.
    The service is still being called fine. In the AE i can see the response payload being returned to PI.
    When i look in IE however i can no longer see the response payload, only the manifest. Further response processing thus causes an error due to the missing payload.
    For the record it should be stated that im using 'nosoap' in the receiver SOAP adapter.
    This is not an issue related to logging. Logging is fine, but the response payload really is non-existent when entering the IE.
    Apart from this there is no special configuration involved.
    Thanks in advance,
    Daniel

    Hi Daniel,
    Thanks for your response.
    We are 711 SP 6 both on ABAP and Java stacks. This SAP Note# 1522630 alone resolved the problem for you ? What was the parsing issue about ? The only issue I have currently is I could not see the response payload from Receiver SOAP adapter in IE which is causing mapping issues since payload is missing.
    Please let me know.
    Shany

  • Response payload is not updating the SAP tables in Sync Interface

    Dear Experts,
    We are doing the ECC to SFDC sync interface by using the ABAP Proxy to Webservice ICO scenario (SOAP to SOAP).
    The response payload from SFA has having the SOAP envelope, to remove this I have used the Java mapping with this we resolve the normal graphical mapping issue and ECC is able to get the response at MONI level.
    But the response payload is not updating the ECC SE11 tables at the proxy level.
    I have attached ECC synchronous proxy testing results with response payloads. With this original response payload the proxy is not updating the tables.
    Please help me out.
    Regards
    RK

    Hi RK,
    Set run-time parameter( LOGGING_SYNC) to 1 in Integration Engine (SXMB_ADM --> Integration Engine Configuration -> Edit configuration ) . LOGGING_SYNC may have set to 0 in IE. If LOGGING_SYNC is set to 0 , IE will not save or write the messages .
    Note: If PI system is Java only stack , please perform above step in ECC.
    Thanks
    Hari.

  • Why do some messages contain a response payload, and some don't

    I have noticed that when we send a message into an IDoc adapter, the message in XI contains the original data in the Inbound Message (CENTRAL)/Payloads/MainDocument section, and the final version of the transformed message which the IDoc adapter receives appears in the Response/Payloads/MainDocument section.
    However, when we send an IDoc out from the system and the transmitting communication channel is a file adapter in FTP mode, for example, then the IDoc appears in the Inbound Message (CENTRAL)/Payloads/MainDocument section, but the Response/Payloads/MainDocument section is empty.
    What is the reason for this? Does the adapter type determine if you will get a MainDocument back in the Response section of the message? Is there any way to get this with a file adapter?
    BR,
    Tony.

    Hi Anthony,
    It may be because of the engines available on different stacks.
    That is Integration engine is available on ABAP stack and Adapter engine is available on Java stack.
    What ever you explained is on the basis of Integration engine monitoring, then it may be due to IDoc adapter is on Integration Engine. Hence you will get the response message after executing integration logic on Integration engine.
    But if you see file adapter, you will get the output only when it passes through Adapter engine. Perhaps if you see in Message monitoring in Adapter engine, you will get to see the output message.
    Regards,
    Suraj Kumar

  • Messages Missing in sxmb_moni

    Hi every one,
    There are some messages missing in sxmb_moni? I have checked the queues: smq1, smq2
    -Naveen.

    Hi,
    did you activate the trace?
    /people/michal.krawczyk2/blog/2005/05/10/xi-i-cannot-see-some-of-my-messages-in-the-sxmbmoni
    BTw
    are you sure those messages should be in the XI?
    do you see your message in:
    http://hostname:portnumber/MessagingSystem/monitor/monitor.jsp
    Regards,
    michal

  • Incomplete request/response operation missing send

    Brief on orchestration whihc have request response port(published as WCF service)
    1. receive(initialize co-relation)
    2. Looping and do some operation(in scope and exception handling)
    3.listen with receive(follow co-relation )& dynamic set delay shape(this step is also in loop, delay continues untill second request is received)
    4. construct resp message and send
    getting build error incomplete request/response operation missing send

    You have a loop shape, and obviously an condition associated to that loop.
    Now consider a scenario: you receive a message - and your loop condition is not met. In such cases you are coming out of loop (after receiving a message), and you will not be able to send anything back on the Req/Res port. Hence the Compiler restricts you
    this way.
    Thanks
    Abhishek

  • One of my forms and it's responses are missing from "My Forms"

    Two days ago I was working with the responses from one of our forms.  I went to continue to work on the data last night and the form and all it's responses are missing.  Is there any way to restore the form and/or it's responses from a backup?
    Also, I have a pdf copy of the form, but when I go to import it I get an error basically saying I cannot import the form because it has already been distributed.  Is there any kind of workaround to this so I don't have to recreate the form from scratch?
    Thanks
    Max

    Max,
    FormsCentral currently does not import the pdf copy back.  Sorry for that.  If you want to have a backup copy of a FormsCentral form, a better way is export the form design. You could do that in the Form Design, File – Export Design File…, to export the form design and save it locally.  You could then import the form design back to your account in a later time.  Note, export the form design would not include the responses data. 
    Regards,
    Perry

  • Response Payload (Mapped XML) in SXMB_MONI

    Hi,
    I found many posts with the same question and but couldn't get an answer
    Posting it again!
    I can find the request and response( XML after mapping) if it is a X - IDoc scenario. But for IDoc - X scenarios I can find only the request payload which is the IDoc XML not the mapped XML.
    Is there any way I can get the mapped XML also in SXMB_MONI?
    Could you throw some light towards where these XML is stored in J2EE engine?
    Regards,
    Anish

    Hi,
    In the SXMB_MONI I get only 3 menus
    Inbound Message(CENTRAL)
        -SOAP Header
        -SOAP Body
        - Payloads
    Receiver Grouping
        -SOAP Header
        -SOAP Body
        - Payloads
    Response
        -SOAP Header
        -SOAP Body
    Payloads option is not there in the last menu and I need that payload XML and that too in the Runtime.
    Any help on the same?
    Regards,
    Anish

  • Payload missing in File-File scenario

    Hi,
    I have created a scenario which is a combination of File-IDoc and File-File scenario.
    First scenario is working fine.IDoc is getting generated and posted to SAP R/3.
    I could see messages for these two as child messages in sxmb_moni with same message ID.
    But in the second message,payload is missing in Call Adapter block and Response block in sxmb_moni.
    Also,output file is not getting generated though the message is successful in sxmb_moni.
    Could anyone please let me know what could be the reason for this.
    Thanks.
    Best Regards,
    Shweta

    this is the full trace:
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Response
      -->
    - <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SOAP:Header>
    - <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
      <SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
      <SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
      <SAP:MessageId>47A1A2FD-9F90-0066-E100-80028928A9DC</SAP:MessageId>
      <SAP:TimeSent>2008-01-31T10:34:40Z</SAP:TimeSent>
    - <SAP:Sender>
      <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">Logitec_Test</SAP:Party>
      <SAP:Service>POS_MAIL</SAP:Service>
      <SAP:Interface namespace="http://pan.eu/ORDERS/LOGITEC_ORDRS_09">MI_ORDERS_EDIFACT_D96A_AS_OB</SAP:Interface>
      </SAP:Sender>
    - <SAP:Receiver>
      <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">Logitec_Test</SAP:Party>
      <SAP:Service>BS_FILE_RECEIVER</SAP:Service>
      <SAP:Interface namespace="http://pan.eu/ORDERS/LOGITEC_ORDRS_09">MI_ORDERS_EDIFACT_D96A_AS_IB</SAP:Interface>
    - <SAP:Mapping notRequired="M">
      <SAP:ObjectId>s0jXwORWMKCNyteX7/7ysA==</SAP:ObjectId>
      <SAP:SWCV>ftfEkNt0EdqTpexmiSip3w==</SAP:SWCV>
      <SAP:SP>-1</SAP:SP>
      </SAP:Mapping>
      </SAP:Receiver>
      <SAP:Interface namespace="http://pan.eu/ORDERS/LOGITEC_ORDRS_09">MI_ORDERS_EDIFACT_D96A_AS_IB</SAP:Interface>
      </SAP:Main>
    - <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:QualityOfService>ExactlyOnce</SAP:QualityOfService>
      </SAP:ReliableMessaging>
    - <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
    - <SAP:Hop timeStamp="2008-01-31T10:34:40Z" wasRead="false">
      <SAP:Engine type="AE">af.pxe.pandpxe</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XIRA</SAP:Adapter>
      <SAP:MessageId>2100B8D2-CFE8-11DC-CDAA-001125A5DEBE</SAP:MessageId>
      <SAP:Info />
      </SAP:Hop>
    - <SAP:Hop timeStamp="2008-01-31T10:34:40Z" wasRead="false">
      <SAP:Engine type="IS">is.00.pandpxe</SAP:Engine>
      <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
      <SAP:MessageId>47A1A2FD-9F90-0066-E100-80028928A9DC</SAP:MessageId>
    - <SAP:Branch>
      <SAP:MessageId>47A1A2FC-9F90-0066-E100-80028928A9DC</SAP:MessageId>
      <SAP:Service>PAECLNT020</SAP:Service>
      </SAP:Branch>
    - <SAP:Branch>
      <SAP:MessageId>47A1A2FD-9F90-0066-E100-80028928A9DC</SAP:MessageId>
      <SAP:Party agency="http://sap.com/xi/XI" scheme="XIParty">Logitec_Test</SAP:Party>
      <SAP:Service>BS_FILE_RECEIVER</SAP:Service>
      </SAP:Branch>
      <SAP:Info>3.0</SAP:Info>
      </SAP:Hop>
      </SAP:HopList>
    - <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
      <SAP:Date>20080131</SAP:Date>
      <SAP:Time>113441</SAP:Time>
      <SAP:Host>pandpxe</SAP:Host>
      <SAP:SystemId>PXE</SAP:SystemId>
      <SAP:SystemNr>00</SAP:SystemNr>
      <SAP:OS>AIX</SAP:OS>
      <SAP:DB>ORACLE</SAP:DB>
      <SAP:Language />
      <SAP:ProcStatus>003</SAP:ProcStatus>
      <SAP:AdapterStatus>000</SAP:AdapterStatus>
      <SAP:User>XIAFUSER</SAP:User>
      <SAP:TraceLevel>3</SAP:TraceLevel>
      <SAP:Logging>1</SAP:Logging>
      <SAP:LogSeqNbr>004</SAP:LogSeqNbr>
      <SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
      <SAP:PipelineIdInternal>SAP_CENTRAL</SAP:PipelineIdInternal>
      <SAP:PipelineIdExternal>CENTRAL</SAP:PipelineIdExternal>
      <SAP:PipelineElementId />
      <SAP:PipelineStartElementId>5EC3C53B4BB7B62DE10000000A1148F5</SAP:PipelineStartElementId>
      <SAP:PipelineService />
      <SAP:QIdInternal>XBTOW___0002</SAP:QIdInternal>
      <SAP:CommitActor>X</SAP:CommitActor>
      <SAP:ParentId ChildNo="0" ChildTotal="0">2100B8D2CFE811DCCDAA001125A5DEBE</SAP:ParentId>
      <SAP:SplitNumber>0</SAP:SplitNumber>
      <SAP:NumberOfRetries>0</SAP:NumberOfRetries>
      <SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
      <SAP:TypeOfEngine client="010">CENTRAL</SAP:TypeOfEngine>
      <SAP:PlsrvExceptionCode />
      <SAP:EOReferenceRuntime type="TID">8928A9DC00C947A1A441092F</SAP:EOReferenceRuntime>
      <SAP:EOReferenceInbound type="TID" />
      <SAP:EOReferenceOutbound type="TID" />
      <SAP:MessageSizePayload>4272</SAP:MessageSizePayload>
      <SAP:MessageSizeTotal>8041</SAP:MessageSizeTotal>
      <SAP:PayloadSizeRequest>4272</SAP:PayloadSizeRequest>
      <SAP:PayloadSizeRequestMap>2874</SAP:PayloadSizeRequestMap>
      <SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
      <SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
      <SAP:Reorganization>INI</SAP:Reorganization>
      <SAP:AdapterInbound>AENGINE</SAP:AdapterInbound>
      <SAP:AdapterOutbound>AENGINE</SAP:AdapterOutbound>
      <SAP:InterfaceAction>DEL</SAP:InterfaceAction>
      <SAP:RandomNumber>35</SAP:RandomNumber>
      <SAP:AckStatus>000</SAP:AckStatus>
      <SAP:SkipReceiverDetermination />
      <SAP:Sender_Agreement_GUID>C14103EF96A93EF7A416B17522666D3A</SAP:Sender_Agreement_GUID>
      <SAP:Receiver_Agreement_GUID>4E2837E24B083A33A77C5043CBB15379</SAP:Receiver_Agreement_GUID>
      <SAP:Serialize_Children>X</SAP:Serialize_Children>
      </SAP:RunTime>
    - <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="begin" host="pandpxe">20080131103440.920981</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
      <SAP:Timestamp type="end" host="pandpxe">20080131103440.934955</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="begin" host="pandpxe">20080131103440.935459</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
      <SAP:Timestamp type="end" host="pandpxe">20080131103440.945085</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
      <SAP:Timestamp type="begin" host="pandpxe">20080131103440.945102</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
      <SAP:Timestamp type="end" host="pandpxe">20080131103441.062247</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="pandpxe">20080131103441.064953</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="pandpxe">20080131103441.069988</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="begin" host="pandpxe">20080131103441.096849</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_INTERFACE_DETERMINATION</SAP:Name>
      <SAP:Timestamp type="end" host="pandpxe">20080131103441.102084</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="begin" host="pandpxe">20080131103441.11954</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_RECEIVER_MESSAGE_SPLIT</SAP:Name>
      <SAP:Timestamp type="end" host="pandpxe">20080131103441.170827</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
      <SAP:Timestamp type="begin" host="pandpxe">20080131103441.170842</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="DBQUEUE">DB_SPLITTER_QUEUING</SAP:Name>
      <SAP:Timestamp type="end" host="pandpxe">20080131103441.343581</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="begin" host="pandpxe">20080131103441.346447</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_MAPPING_REQUEST</SAP:Name>
      <SAP:Timestamp type="end" host="pandpxe">20080131103441.388572</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
      <SAP:Timestamp type="begin" host="pandpxe">20080131103441.414031</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_OUTBOUND_BINDING</SAP:Name>
      <SAP:Timestamp type="end" host="pandpxe">20080131103441.418165</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
      <SAP:Timestamp type="begin" host="pandpxe">20080131103441.447064</SAP:Timestamp>
      </SAP:RunTimeItem>
    - <SAP:RunTimeItem>
      <SAP:Name type="PLSRV">PLSRV_CALL_ADAPTER</SAP:Name>
      <SAP:Timestamp type="end" host="pandpxe">20080131103441.589866</SAP:Timestamp>
      </SAP:RunTimeItem>
      </SAP:PerformanceHeader>
    - <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
      <SAP:TraceLevel>Information</SAP:TraceLevel>
      <SAP:Logging>Off</SAP:Logging>
      </SAP:Diagnostic>
    - <SAP:OutboundBinding xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    - <SAP:OutboundBindingEntry version="30">
      <SAP:OutboundBindingObjectId>4E2837E24B083A33A77C5043CBB15379</SAP:OutboundBindingObjectId>
      <SAP:FromPartyName>Logitec_Test</SAP:FromPartyName>
      <SAP:FromServiceName>POS_MAIL</SAP:FromServiceName>
      <SAP:ToPartyName>Logitec_Test</SAP:ToPartyName>
      <SAP:ToServiceName>BS_FILE_RECEIVER</SAP:ToServiceName>
      <SAP:ToInterfaceName>MI_ORDERS_EDIFACT_D96A_AS_IB</SAP:ToInterfaceName>
      <SAP:ToInterfaceNamespace>http://pan.eu/ORDERS/LOGITEC_ORDRS_09</SAP:ToInterfaceNamespace>
    - <SAP:OutboundBindingAttributes>
      <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      </SAP:OutboundBindingAttributes>
    - <SAP:HeaderMapping>
      <SAP:FieldMapping xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      </SAP:HeaderMapping>
    - <SAP:ChannelEntry version="30">
      <SAP:PartyName xmlns:SAP="http://sap.com/xi/XI/Message/30">Logitec_Test</SAP:PartyName>
      <SAP:ServiceName xmlns:SAP="http://sap.com/xi/XI/Message/30">BS_FILE_RECEIVER</SAP:ServiceName>
      <SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">CC_FILE_RECEIVER_EDIFACT_ORDERS</SAP:ChannelName>
      <SAP:AdapterName xmlns:SAP="http://sap.com/xi/XI/Message/30">File</SAP:AdapterName>
      <SAP:AdapterNamespace xmlns:SAP="http://sap.com/xi/XI/Message/30">http://sap.com/xi/XI/System</SAP:AdapterNamespace>
      <SAP:AdapterSWCV xmlns:SAP="http://sap.com/xi/XI/Message/30">3B787A8035C111D6BBE0EFE50A1145A5</SAP:AdapterSWCV>
      <SAP:AdapterEngineType xmlns:SAP="http://sap.com/xi/XI/Message/30">AE</SAP:AdapterEngineType>
      <SAP:AdapterEngineName xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:MessageProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">File</SAP:MessageProtocol>
      <SAP:MessageProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30">3.0.0527</SAP:MessageProtocolVersion>
      <SAP:TransportProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">FTP</SAP:TransportProtocol>
      <SAP:TransportProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      <SAP:ChannelDirection xmlns:SAP="http://sap.com/xi/XI/Message/30">O</SAP:ChannelDirection>
      <SAP:FromPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30">Seeburger</SAP:FromPartyAgency>
      <SAP:FromPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30">AS2ID</SAP:FromPartySchema>
      <SAP:ToPartySchema xmlns:SAP="http://sap.com/xi/XI/Message/30">AS2ID</SAP:ToPartySchema>
      <SAP:ToPartyAgency xmlns:SAP="http://sap.com/xi/XI/Message/30">Seeburger</SAP:ToPartyAgency>
    - <SAP:ChannelAttributes xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />
      </SAP:ChannelAttributes>
      </SAP:ChannelEntry>
      </SAP:OutboundBindingEntry>
      </SAP:OutboundBinding>
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <Trace level="1" type="T">Party normalization: sender</Trace>
      <Trace level="1" type="T">Sender scheme external = XIParty</Trace>
      <Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>
      <Trace level="1" type="T">Sender party external = Logitec_Test</Trace>
      <Trace level="1" type="T">Sender party normalized = Logitec_Test</Trace>
      <Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>
      <Trace level="2" type="T">Request Line = POST /sap/xi/engine?type=entry HTTP/1.1</Trace>
      <Trace level="2" type="T">Host = pandpxe.pan.eu:8000</Trace>
      <Trace level="2" type="T">Server protocol = HTTP/1.1</Trace>
      <Trace level="2" type="T">Remote address = 137.40.169.220</Trace>
      <Trace level="1" type="T">COMMIT is done by XMB !</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 = PXE</Trace>
      <Trace level="3" type="T">client = 010</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = XIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2008-01-31T10:34:40Z CET</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = 2100B8D2CFE811DCCDAA001125A5DEBE</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 = 2100B8D2CFE811DCCDAA001125A5DEBE</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 : XBTI0008</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTI0008</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 = 2100B8D2CFE811DCCDAA001125A5DEBE</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="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="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="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">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="3" type="T">system-ID = PXE</Trace>
      <Trace level="3" type="T">client = 010</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = XIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET</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">ELEMPOS = 0001</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0002</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0003</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0004</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0007</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0008</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0009</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET Begin of pipeline processing PLSRVID = CENTRAL</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET 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 without given receiver</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: Logitec_Test - BS_FILE_RECEIVER</Trace>
      <Trace level="2" type="T">Check conditions for rule line no. 2</Trace>
      <Trace level="2" type="T">...valid Receiver w/o Condition: - PAECLNT020</Trace>
      <Trace level="2" type="T">No Receiver found behaviour: 0</Trace>
      <Trace level="2" type="T">Number of Receivers:2</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET 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-01-31T10:34:41Z CET 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) PAECLNT020 ORDERS.ORDERS05</Trace>
      <Trace level="2" type="T">...valid InbIf without Condition: ORDERS.ORDERS05</Trace>
      <Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) Logitec_Test BS_FILE_RECEIVER MI_ORDERS_EDIFACT_D96A_AS_IB</Trace>
      <Trace level="2" type="T">...valid InbIf without Condition: MI_ORDERS_EDIFACT_D96A_AS_IB</Trace>
      <Trace level="2" type="T">Number of receiving Interfaces:2</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET 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-01-31T10:34:41Z CET 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: 2</Trace>
      <Trace level="1" type="T">Multi-receiver split case</Trace>
      <Trace level="1" type="T">Persisting initial (pre-split) message</Trace>
      <Trace level="1" type="T">Persisting split messages (split kids)</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Splitting loop start</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="3" type="T">Split kid MessageGuid: 47A1A2FC9F900066E10080028928A9DC</Trace>
      <Trace level="1" type="T">Post-split internal queue name = XBTO3___0001</Trace>
      <Trace level="1" type="T">Persisting split kid = 47A1A2FC9F900066E10080028928A9DC</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 000</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
      <Trace level="3" type="T">Split kid MessageGuid: 47A1A2FD9F900066E10080028928A9DC</Trace>
      <Trace level="1" type="T">Post-split internal queue name = XBTOW___0002</Trace>
      <Trace level="1" type="T">Persisting split kid = 47A1A2FD9F900066E10080028928A9DC</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 000</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="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="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">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="3" type="T">system-ID = PXE</Trace>
      <Trace level="3" type="T">client = 010</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = XIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET</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">ELEMPOS = 0001</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY = 0</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0002</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_INTERFACE_DETERMINATION</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0003</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_RECEIVER_MESSAGE_SPLIT</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0004</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_REQUEST</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0007</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_OUTBOUND_BINDING</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0008</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_CALL_ADAPTER</Trace>
      <Trace level="3" type="T">PLSRVTYPE = =SWITCH=</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T">ELEMPOS = 0009</Trace>
      <Trace level="3" type="T">PLSRVID = PLSRV_MAPPING_RESPONSE</Trace>
      <Trace level="3" type="T">PLSRVTYPE =</Trace>
      <Trace level="3" type="T">FL_DUMMY =</Trace>
      <Trace level="3" type="T" />
      <Trace level="3" type="T" />
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET 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-01-31T10:34:41Z CET 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 is already determined in the interface determination</Trace>
      <Trace level="3" type="T">Object ID of Interface Mapping B348D7C0E45630A08DCAD797EFFEF2B0</Trace>
      <Trace level="3" type="T">Version ID of Interface Mapping 7ED7C490DB7411DA93A5EC668928A9DF</Trace>
      <Trace level="1" type="T">Interface Mapping http://pan.eu/ORDERS/LOGITEC_ORDRS_09 IM_ORDERS_EDIFACT_to_ORDERS_EDIFACT</Trace>
      <Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_MM_EDIFACT_ORDERS_D96A_to_EDIFACT_ORDERS_D96A_</Trace>
      <Trace level="3" type="T">Dynamic configuration is empty</Trace>
      <Trace level="2" type="T">Mode 0</Trace>
      <Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_EDIFACT_ORDERS_D96A_to_EDIFACT_ORDERS_D96A_.</Trace>
      <Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_EDIFACT_ORDERS_D96A_to_EDIFACT_ORDERS_D96A_</Trace>
      <Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_EDIFACT_ORDERS_D96A_to_EDIFACT_ORDERS_D96A_ completed. (executeStep() of com.sap.xi.tf._MM_EDIFACT_ORDERS_D96A_to_EDIFACT_ORDERS_D96A_</Trace>
      <Trace level="3" type="T">Dynamic configuration is empty</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET 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 = 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_OUTBOUND_BINDING">
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET 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">Logitec_Test-POS_MAIL</Trace>
      <Trace level="2" type="T">Logitec_Test-BS_FILE_RECEIVER</Trace>
      <Trace level="2" type="T">http://pan.eu/ORDERS/LOGITEC_ORDRS_09.MI_ORDERS_EDIFACT_D96A_AS_IB</Trace>
      <Trace level="2" type="T">Channel found: Logitec_Test - BS_FILE_RECEIVER - CC_FILE_RECEIVER_EDIFACT_ORDERS</Trace>
      <Trace level="2" type="T">no header mapping defined</Trace>
      </Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET 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 = 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_CALL_ADAPTER">
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET 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: File</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: File</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://pandpxe:50000/MessagingSystem/receive/AFW/XI</Trace>
      <Trace level="3" type="T">User = XIISUSER</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>
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET End of pipeline service processing PLSRVID= PLSRV_CALL_ADAPTER</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 = 003</Trace>
      <Trace level="3" type="T">Message version 003</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
      <Trace level="3" type="T">Async processing: skip mapping of response</Trace>
      </Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Async processing completed OK.</Trace>
      <Trace level="3" type="T">system-ID = PXE</Trace>
      <Trace level="3" type="T">client = 010</Trace>
      <Trace level="3" type="T">language = E</Trace>
      <Trace level="3" type="T">user = XIAFUSER</Trace>
      <Trace level="1" type="Timestamp">2008-01-31T10:34:41Z CET</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 = 003</Trace>
      <Trace level="3" type="T">Message version 004</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </SAP:Trace>
      </SOAP:Header>
    - <SOAP:Body>
      <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7" />
      </SOAP:Body>
      </SOAP:Envelope>

  • Error during sync integrated configuration - incoming payload missed

    Hi guys,
    we are suing PI 7.11 and trying to use the new feature integrated configuration wherever possible.
    Now I test a sync szeanrio where sender is SOAP and receiver is RFC.
    The messages fails in SOAP Sender channel with the error that there is no suitable receiver found for this message.
    During integrated configuration content based routing is used.
    com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: Receiver Determination failed for message e54dba61-9ded-11de-801a-020000000038(OUTBOUND)
    But the message fails without persisting the payload, so I could check what value is missing in the receiver rules.
    Furthermore the message is only displayed in the sender chanel and is not shown in rwb
    While using the normal way of messsage processing where the integration server is involved, such errors are persisted and the payload is also available.
    Is that the normal behaviour of integrated configurations.
    Could the behaviour be parametrized?
    Any help appreciated
    Kind regards
    Jochen

    Hi,
    thanks for helping.
    Because of integrated configuration the integration server is passed and there is no entry in sxmb_moni.
    I already tried this blog, but it doesn´t work for me.
    I changed the parameter according to the blog.
    But the message content of sync messages are stilled deleted.
    Does the parameter changed requires restart of adapter engine or complete java stack?
    There two templates one called 'Usage_Type_all_in_One' and above there is an node named equal to the server node name. The parameter of which template have to be changed.
    I tried both with out success.
    Hopefully you could help me using this feature
    Kind regards
    Jochen

  • Payload different in SXMB_MONI and Message Monitoring

    Hi All,
              I am facing a problem. My message Payload in SXMB_MONI (after mapping) is different from what i got from Message Monitoring tab of RWB. In the message monitoring some entries are missing from my actual payload.
    Payload from SXMB_MONI contains 300 entries
    payload from Message monitoring contains 250 entries.
    I am not using any module processor. Any pointer on "Why message payload got changed in RWB. ??
    Thanks
    Ajay

    Hi Nallam,
                    The structure is simple like 300 nodes for items after mapping and these are to be inserted in to SAP tables using RFC. But in the Adapter engine enteries found were 250.
    The same message when sent again worked fine but we have to find the root cause of the error.
    Thanks
    Ajay

  • Error while processing message payload Element PI SXMB_MONI (ECC to TM)

    Dear Experts,
    while processing an XML message in TM using receiver interface IntracompanyTransportationRequestRequest_In , we encounter an error message.
    <SAP:Stack>Error while processing message payload Element &#39;StockTransportOrderReferenceIndicator&#39; missing</SAP:Stack>  
    <SAP:Retry>M</SAP:Retry>
    ssee screenshot attached.
    The field StockTransportOrderReferenceIndicator cannot be located in ECC and I cannot find what the system is expecting to populate here.
    Can somebody propose an approach on how to investigate into this error message for the solution?
    thanks a lot
    Salvador

    Hi Salvador,
    Thanks for your reply. We were able to fix that issue. As of now we have managed to send sales order to TM but getting the following error. Messages are getting failed in SAP TM. Even if the product exists in the system (TM) still the error message persists. I have CIFed location, business partner, product from ECC and everything exists in SAP TM with the same business system group. Kindly advise. Did you happen to face any similar kind of issue during your implementation ?
    Thanks & Regards,
    Aunkur De

  • SOAP sender Adapter - response message missing in adapter engine level

    Hi,
    We have a synchronous scenario SOAP<-> P I <--->Proxy .Request comes from  web service get the response from ECC.
    Issue reported that response message not reached the web service .
    I am able to see the request & response messages in SXMB_MONI. To check the status in message monitoring through RWB synch message are not existing more than a day.
    Is there any possibility of failure of messages at adapter engine level in this case? If so How can I get error log?
    what are the settings required to make the synchronous messages available in RWB?
    Thanks in advance,
    Regards,
    Kartikeya

    what are the settings required to make the synchronous messages available in RWB?
    Set messaging.syncMessageRemover.removeBody = false in NWA / Visual Admin. Have a look at the below link for details -
    /people/william.li/blog/2008/02/07/display-adapter-synchronous-message-content-in-rwb-of-pi-71
    Regards,
    TK

Maybe you are looking for

  • Date & hour in stored procedure

    create or replace PROCEDURE library_portal_home(ldt portal_home_non_login_log.logdatetime%TYPE,   COT portal_home_non_login_log.counter%TYPE) IS lv_count NUMBER; BEGIN   SELECT COUNT(1)   INTO lv_count   FROM portal_home_non_login_log   WHERE to_date

  • Registering for a Topic with own stream & queue in Pub/Sub

    Hi *. I'm working with MQSeries 5.3 on WinXP. I don't know, how to register a subscriber to a topic with the JMS-classes. I found a sample from IBM, but it uses the native (MQ)classes and it does not work, when I try to register an own queue or strea

  • Where are my apps!? They aren't in the library anymore...

    I have bought apps before and then synced and they transferred to my library fine, but suddenly I cant see any of my apps in the library, its just blank, and i've tried syncing it - nothing. It still has all my music etc. but no apps in the library!

  • Failed to login to Solaris

     

  • Clustering VS Load balancing

    Hi All, I want to know the difference between Load Balancing and Clustering. Mainly i want to choose one of the two for J2E based application and Oracle 10 G database. OS will be Sun Solaris 10. Regards Tejas