SXMB_MONI : Query  XMB

Dear Collegues,
                In sxmb_moni for the message,in trace i could see this line
<u><i><b>XMB was called with external pipeline PID = ENTRY</b></i></u>
can any one help me in clarifing me what xmb means?
Regards
shekar chandra

Dear UDO,
         May be i am wrong   in framing the query.
I want to know what exactly <b>XMB</b> means , the other part ur right .
Regards
shekar chandra

Similar Messages

  • Error "system not configured as xmb" in transaction "sxmb_moni"

    Hi,
    when I send an IDoc from R3 to XI I get this error:
    system not configured as xmb" in transaction "sxmb_moni"
    also, in the adaptermonitor of the runtime workbench there is an error in the integration engine.
    "no rules for business-system are definied in SXMS_CONF_ITEMS"
    This error refers from a another error in transaction idx. so, we have assigned the integration engine client 100, because we work with this client. So, we can start transaction idx5 but, we get the other error, as mentioned.
    Can anybody help me please?
    Regards
    Stefan

    Hi Stefen,
    try to chk SLD-->Business systems...and check the role of business system Web AS ABAP (tht was created during installation)...check if the role is integration server if not  try sxi_cache and in the menu tool bar goto "GoTo" and click AE cache and see if the link is fine
    pls chk for this links
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ceba9b90-0201-0010-9687-a8b279e388bb
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/909760cb-0ec8-2a10-4a96-ee8417acfbc9
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/909760cb-0ec8-2a10-4a96-ee8417acfbc9
    if found worth pls do the req
    Thanx
    Sampath

  • Dynamic Interface in Query String does not work?

    Hi All,
    i have exposed a interface as a webservice with the help of the Define Web Service in Configuration Builder.
    In the SOAP Sender Communication Channel i have checked the options Use Encoded Headers and Use Query String
    The url of the webservice looks like this:
    http://server:50000/XISOAPAdapter/MessageServlet?channel=:BS:CC_SOAP_SENDER&version=3.0&Sender.Service=BS&Interface=http%3A%2F%2Fnamespace.com%2Fabc%2HER%2FGlobal%5EMIOS_GetDetails
    This works which is great, i can now retrieve supplier details with this webservice. Now i want to expose another interface as a webservice. That URL looks like this:
    http://server:50000/XISOAPAdapter/MessageServlet?channel=:BS:CC_SOAP_SENDER&version=3.0&Sender.Service=BS&Interface=http%3A%2F%2Fnamespace.com%2Fabc%2HER%2FGlobal%5EMIOS_EventBooking
    As you can see i have a different interface in the URL's of the Webservices. I want to have both make use of the same Communication Channel which is possible according to [SAP Note 856597|https://websmp130.sap-ag.de/sap(bD1ubCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=856597] See Q: Can I set the interface name dynamically from the client? also in this document : [How to Use the XI 3.0 Soap Adapter|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d23cbe11-0d01-0010-5287-873a22024f79]
    The problem is that when i try to call the second web service (EventBooking) that is routes to the mapping of the GetDetails interface, i can see this in SXMB_MONI. Therefore it gives an Error.
    When i try both scenarios in Configuration Builder they both work fine, only the webservice call of EventBooking ends up in the Message Mapping of GetDetail.... Why? And how to solve this?
    Anyone have experience with the feature mentioned in the SAP note?

    After some further examination it seems that both calls are picked up by the same interface. In the RWB both the messages are picked up by the MIOS_GetDetails...
    How can i fix this?

  • Error in SXMB_MONI

    Hi,
      I created a scenario in my XI development scenario.i tested it and it worked there correctly.but once i put all these scenarios into my XI production i get the following error in the transaction sxmb_moni
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Receiver Grouping
      -->
    - <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 =</Trace>
      <Trace level="1" type="T">Sender agency external =</Trace>
      <Trace level="1" type="T">Sender party external =</Trace>
      <Trace level="1" type="T">Sender party normalized =</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="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="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">XMB entry processing</Trace>
      <Trace level="1" type="T">system-ID = XIP</Trace>
      <Trace level="1" type="T">client = 200</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = XIAPPLUSER</Trace>
      <Trace level="1" type="Timestamp">2005-10-12T10:39:28Z 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 = 4349D7D080A900FE00000000AC15012C</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="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="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>
      <Trace level="1" type="T">Queue name : XBTI0011</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTI0011</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Going to persist message</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>
      <Trace level="1" type="T">system-ID = XIP</Trace>
      <Trace level="1" type="T">client = 200</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = XIAPPLUSER</Trace>
      <Trace level="1" type="Timestamp">2005-10-12T10:39:28Z 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="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>
      <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">
      <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N</Trace>
      <Trace level="1" type="T">Cache Content is up to date</Trace>
      <Trace level="1" type="T">No Relation found - accept given receivers.</Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      </SAP:Trace>
    Thanks and Regards,
    Jishi

    Hi Jishi
    Not enough information in the trace.
    Boost up ur trace level as Manish said, also check the entry for your pipeline url as well in your SLD for the business system you are using.
    It should be something like this,
    http://XIServer:8000/sap/xi/engine?type=entry
    cheers
    Sameer

  • Error in Out bound status in sxmb_moni in WS to IDOC  scenario

    HI all,
    This question remains unresolved I have Provided the trace contents as asked by XIans.
    I am Again sending the contents of the trace.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!-- Response
    -->
    - <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 =</Trace>
    <Trace level="1" type="T">Sender agency external =</Trace>
    <Trace level="1" type="T">Sender party external =</Trace>
    <Trace level="1" type="T">Sender party normalized =</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.0</Trace>
    <Trace level="2" type="T">Host = pitest.monet.local:8001</Trace>
    <Trace level="2" type="T">Server protocol = HTTP/1.0</Trace>
    <Trace level="2" type="T">Remote address = 10.10.10.26</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 = PIT</Trace>
    <Trace level="3" type="T">client = 001</Trace>
    <Trace level="3" type="T">language = E</Trace>
    <Trace level="3" type="T">user = ZPIAPPLUSER</Trace>
    <Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST</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 = 4B7D33199091C54592B7B94A466ED9C2</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 = 4B7D33199091C54592B7B94A466ED9C2</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 : XBTI0004</Trace>
    <Trace level="1" type="T">Generated prefixed queue name = XBTI0004</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 = 4B7D33199091C54592B7B94A466ED9C2</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 = PIT</Trace>
    <Trace level="3" type="T">client = 001</Trace>
    <Trace level="3" type="T">language = E</Trace>
    <Trace level="3" type="T">user = ZPIAPPLUSER</Trace>
    <Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST</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">2007-02-01T05:40:57Z CST Begin of pipeline processing PLSRVID = CENTRAL</Trace>
    - <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">
    <Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST 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: - ERP_D_ADR200</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">2007-02-01T05:40:57Z CST 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">2007-02-01T05:40:57Z CST 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) ERP_D_ADR200 ATT_ABS.ATT_ABS01</Trace>
    <Trace level="2" type="T">...valid InbIf without Condition: ATT_ABS.ATT_ABS01</Trace>
    <Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST 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">2007-02-01T05:40:57Z CST 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 = XBTO4___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="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= 004</Trace>
    <Trace level="2" type="T">Increment log sequence to 005</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 = PIT</Trace>
    <Trace level="3" type="T">client = 001</Trace>
    <Trace level="3" type="T">language = E</Trace>
    <Trace level="3" type="T">user = ZPIAPPLUSER</Trace>
    <Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST</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">2007-02-01T05:40:57Z CST 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">2007-02-01T05:40:57Z CST 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 4AE42F31B3BC3733A792B4DDEDD54756</Trace>
    <Trace level="3" type="T">Version ID of Interface Mapping 1D47292048CD11DB8AD9FDDE0A0A0A5E</Trace>
    <Trace level="1" type="T">Interface Mapping http://www.gemsconsult.com/LAB_ABA/wstoidoc PublishLeaveStatusSoapIN_to_ATT_ABS01</Trace>
    <Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_PublishLeaveStatusSoapIN_to_ATT_ABS01_</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/_PublishLeaveStatusSoapIN_to_ATT_ABS01_.</Trace>
    <Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._PublishLeaveStatusSoapIN_to_ATT_ABS01_</Trace>
    <Trace level="2" type="T">Java mapping com/sap/xi/tf/_PublishLeaveStatusSoapIN_to_ATT_ABS01_ completed. (executeStep() of com.sap.xi.tf._PublishLeaveStatusSoapIN_to_ATT_ABS01_</Trace>
    <Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST 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">2007-02-01T05:40:57Z CST 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">-KCRS_3RDP_D</Trace>
    <Trace level="2" type="T">-ERP_D_ADR200</Trace>
    <Trace level="2" type="T">urn:sap-com:document:sap:idoc:messages.ATT_ABS.ATT_ABS01</Trace>
    <Trace level="2" type="T">Channel found: - ERP_D_ADR200 - IDOC</Trace>
    <Trace level="2" type="T">no header mapping defined</Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST 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">2007-02-01T05:40:57Z CST 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">Channel for IDOC adapter: IDoc</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 = IDOC</Trace>
    <Trace level="3" type="T">ADRESSMOD = SD</Trace>
    <Trace level="3" type="T">P_CLASS = CL_IDX_IDOC_SERVICE</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="T">----
    </Trace>
    <Trace level="1" type="T">---- Outbound IDoc-Adapter -
    </Trace>
    <Trace level="1" type="T">----
    </Trace>
    - <Trace level="1" type="B" name="CL_IDX_IDOC_SERVICE-ENTER_PLSRV">
    <Trace level="1" type="T">Pipeline Service ID: PLSRV_CALL_ADAPTER</Trace>
    <Trace level="1" type="T">Get Information from IS-Header Objekt</Trace>
    <Trace level="1" type="T">Get Information from SD-IDoc-Endpoint</Trace>
    <Trace level="2" type="T">----
    </Trace>
    <Trace level="2" type="T">IDoc-Endpoint Channel :</Trace>
    <Trace level="2" type="T">RFCDEST : ADR_200</Trace>
    <Trace level="2" type="T">Port : SAPADR</Trace>
    <Trace level="2" type="T">Docrel :</Trace>
    <Trace level="2" type="T">Version : 3</Trace>
    <Trace level="2" type="T">Saprel : 700</Trace>
    <Trace level="2" type="T">Queue-ID:</Trace>
    <Trace level="2" type="T">----
    </Trace>
    <Trace level="1" type="T">Sender and Receiver after Header-Mapping</Trace>
    <Trace level="1" type="T">Sender service KCRS_3RDP_D</Trace>
    <Trace level="1" type="T">Receiver service ERP_D_ADR200</Trace>
    <Trace level="1" type="T">Get IDoc-XML from the Resource Objekt</Trace>
    - <Trace level="1" type="B" name="IDX_XML_TO_IDOC">
    <Trace level="1" type="T">Parse XML-BODY</Trace>
    <Trace level="1" type="T">Get the Metadata for port SAPADR</Trace>
    <Trace level="2" type="T">----
    </Trace>
    <Trace level="2" type="T">IDX_STRUCTURE_GET Details</Trace>
    <Trace level="2" type="T">Port : SAPADR</Trace>
    <Trace level="2" type="T">IDoctyp : ATT_ABS01</Trace>
    <Trace level="2" type="T">Cimtyp :</Trace>
    <Trace level="2" type="T">Release :</Trace>
    <Trace level="2" type="T">Version : 3</Trace>
    <Trace level="2" type="T">Direction : 2</Trace>
    <Trace level="2" type="T">SAPREL : 700</Trace>
    <Trace level="2" type="T">----
    </Trace>
    <Trace level="1" type="T">Convert one IDoc</Trace>
    <Trace level="2" type="T">Convert Control Record</Trace>
    <Trace level="2" type="T">Convert Data Records</Trace>
    <Trace level="3" type="T">Segment= E1BP7011_1</Trace>
    <Trace level="2" type="T">Number of found Data records: 1</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 : SAPADR</Trace>
    <Trace level="2" type="T">IDoctyp : ATT_ABS01</Trace>
    <Trace level="2" type="T">Cimtyp :</Trace>
    <Trace level="2" type="T">RFC-Dest :</Trace>
    <Trace level="2" type="T">----
    </Trace>
    <Trace level="1" type="T">Convert Segment-Types to Segment-Definitions</Trace>
    </Trace>
    <Trace level="1" type="T">Call Outbound IDoc-Adapter</Trace>
    <Trace level="1" type="T">Call Outbound IDoc-Adapter</Trace>
    - <Trace level="1" type="B" name="IDX_OUTBOUND_XMB">
    <Trace level="1" type="T">FM IDOC_INBOUND_ASYNCHRONOUS with RFCDEST= ADR_200</Trace>
    <Trace level="2" type="T">Used TID = 0A0A0A57187045C17D691641</Trace>
    </Trace>
    <Trace level="2" type="T">TID : 0A0A0A57187045C17D691641</Trace>
    </Trace>
    </Trace>
    </Trace>
    <Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST 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 = 007</Trace>
    <Trace level="3" type="T">Message version 007</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 = PIT</Trace>
    <Trace level="3" type="T">client = 001</Trace>
    <Trace level="3" type="T">language = E</Trace>
    <Trace level="3" type="T">user = ZPIAPPLUSER</Trace>
    <Trace level="1" type="Timestamp">2007-02-01T05:40:57Z CST</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 008</Trace>
    <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    </SAP:Trace>
    Please let me know where the problem is?
    Thanks,
    SrinivasaP

    Srinivas,
    This is your error msg. Right? This is what the others are asking you...
    Have you checked Wojcitech's reply? Do that. Let us know the result...
    P.S: I copied this from one of your previous threads.
    Regards,
    Jai Shankar
    <i>HI I am Gettin the following error in SXMB_MONI
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!-- Call Adapter
    -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
    <SAP:Category>XIAdapter</SAP:Category>
    <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
    <SAP:P1>XML IDoc conversion: No known segments identified</SAP:P1>
    <SAP:P2 />
    <SAP:P3 />
    <SAP:P4 />
    <SAP:AdditionalText />
    <SAP:ApplicationFaultMessage namespace="" />
    <SAP:Stack>Error: XML IDoc conversion: No known segments identified</SAP:Stack>
    <SAP:Retry>M</SAP:Retry>
    </SAP:Error>
    att_abs01is the Idoc used.
    Thanks
    <b>Hi,
    Please check your configuration in IDX1 and verify if port is the same in IDOC receiver communication channel. Check also if in IDX2 you have current IDOC metadata, you can try to download it manually.
    Regards,
    Wojciech</b>
    </i>

  • 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>

  • MAPPING GENERIC (Split mapping created no messages) error is sxmb_moni

    Hello,
    We are having thousands of messages failing in sxmb_moni due to MAPPING GENERIC error. It also states that <i>Split mapping created no messages</i>. Where will I start my investiagtion? I already checked both ID and IR but I could hardly determine what causes this error.
    Here is a part of the error message from the trace:
    <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 6FB317EF58B136D6BEAB6E567934CC40</Trace>
      <Trace level="3" type="T">Version ID of Interface Mapping A872F380930B11DAAB6EF47891374079</Trace>
      <Trace level="1" type="T">Mapping-Object-Id:6FB317EF58B136D6BEAB6E567934CC40</Trace>
      <Trace level="1" type="T">Mapping-SWCV:A872F380930B11DAAB6EF47891374079</Trace>
      <Trace level="1" type="T">Mapping-Step:1</Trace>
      <Trace level="1" type="T">Mapping-Type:JAVA</Trace>
      <Trace level="1" type="T">Mapping-Program:com/sap/xi/tf/_GBO_MaterialMaster_StandardBusinessDocument_TO_LOCAL_Governor_</Trace>
      <Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
      <Trace level="3" type="T">Multi mapping required.</Trace>
      <Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_GBO_MaterialMaster_StandardBusinessDocument_TO_LOCAL_Governor_.</Trace>
      <Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._GBO_MaterialMaster_StandardBusinessDocument_TO_LOCAL_Governor_</Trace>
      <Trace level="1" type="T">*** START APPLICATION TRACE ***</Trace>
      <Trace level="3" type="T">Using existing</Trace>
      <Trace level="3" type="T">Executing Query: SELECT TO_VALUE FROM ICC_MAPPING_VIEW WHERE FROM_CODING = SIRIUS AND TO_CODING = GS1 AND OBJECT = TRADE-ITEM-TYPE AND FROM_VALUE = 30</Trace>
      <Trace level="1" type="T">SELECT TO_VALUE FROM ICC_MAPPING_VIEW WHERE FROM_CODING = SIRIUS AND TO_CODING = GS1 AND OBJECT = TRADE-ITEM-TYPE AND FROM_VALUE = 30 successfully returned: E-HPC_PRODUCTS</Trace>
      <Trace level="1" type="T">ret: :E-HPC_PRODUCTS</Trace>
      <Trace level="2" type="T">noReceiverFound</Trace>
      <Trace level="1" type="T">*** END APPLICATION TRACE ***</Trace>
      <Trace level="2" type="T">Java mapping com/sap/xi/tf/_GBO_MaterialMaster_StandardBusinessDocument_TO_LOCAL_Governor_ completed. (executeStep() of com.sap.xi.tf._GBO_MaterialMaster_StandardBusinessDocument_TO_LOCAL_Governor_</Trace>
      <Trace level="3" type="T">Message Type 1 Number of Messages 0</Trace>
      <Trace level="3" type="T">Message Type 2 Number of Messages 0</Trace>
      <Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
      </Trace>
    - <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
      <Trace level="3" type="T">No persisting of message after plsrv call, because of config</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" />
    - <!--  ************************************
      -->
    Thanks in advance!

    <Trace level="3" type="T">Using existing</Trace>
    <Trace level="3" type="T">Executing Query: SELECT TO_VALUE FROM ICC_MAPPING_VIEW WHERE FROM_CODING = SIRIUS AND TO_CODING = GS1 AND OBJECT = TRADE-ITEM-TYPE AND FROM_VALUE = 30</Trace>
    <Trace level="1" type="T">SELECT TO_VALUE FROM ICC_MAPPING_VIEW WHERE FROM_CODING = SIRIUS AND TO_CODING = GS1 AND OBJECT = TRADE-ITEM-TYPE AND FROM_VALUE = 30 successfully returned: E-HPC_PRODUCTS</Trace>
    <Trace level="1" type="T">ret: :E-HPC_PRODUCTS</Trace>
    <Trace level="2" type="T">noReceiverFound</Trace>
    <Trace level="1" type="T">*** END APPLICATION TRACE ***</Trace>
    You have used the Trace object to write some Trace in your User Defined Functions. Does this trace make sense in terms of your mapping logic to you?
    Did you remove the <messages> tag from your source message?
    Also, If you are using multimapping make sure that the mapping creates all the messages in the Target Side and that the Inbound adapter is neither Idoc nor HTTP.
    Regards
    Bhavesh

  • JDBC Sender - Select Query without Update Query

    In this case, how many times data will be polled within some minutes, if my polling interval is 1 day.
    How many messages in sxmb_moni?
    Thanks,
    Greg

    >>In this case, how many times data will be polled within some minutes, if my polling interval is 1 day.
    The communication channel executes once as soon as you activate your sender communication channel.  Now a single msg is sent to XI(with many as many rows as the select query fetches from the db).
    After that, it waits for the polling interval(in your case 24 hrs) and then executes again.
    This cycle continues. If you resart the communication channel, the cycle is disrupted and a new cycle starts.
    Hope I dont add to your confusion
    Regards,
    Jai Shankar

  • Message has error on outbound side in sxmb_moni

    Dear All,
    I have a query related to sxmb_moni messages.
    Scenario : FILE - XI - IDOC
    In sxmb_moni, message is successfully processed by XI but <b>it is showing error " message has error on outbound side".</b>
    My questions are:
    <b>1)Is it possible to restart the message . When I tried to restart the sucessful message with error on outbound side it showed me message " You cannot restart xml message".</b>
    2)I tried to analyze error for outbound side using SM58, it showed me message "No connection to database,session terminated" .
    Can anyone please advice what could be the reason for this .
    Thanks & Regards
    Prabhat

    Hi Prabhat,
    the message was send to the IDoc adapter. The error occures there.
    Control, if the send XML can be translated to IDocs (use a message mapping).
    Control, if the SM59 destination to R/3 is working.
    Conrol, if the communication channel is customized in the right way. Control, if the port is customized (transaction IDX1).
    Also the metadata for that IDoc should be in IDX2, that should happen automaticly, if not, assumedly the destination is not working.
    Regards,
    Udo

  • Show me my error in SXMB_MONI

    Hello All!
    At SAPPIDEMO (airlines demo examples) process executing, its not working.
    In this case the cause of error is "Flight booking order sent. Awaiting confirmation."
    Its wait for eternal.
    I saw all Trace logs in SXMB_MONI and dont understand where are my errors.
    Listing below. Thanx!
    <Trace level="1" type="T">CL_XMS_MAIN->DETERMINE_EXT_PID: CENTRAL</Trace>
      <Trace level="1" type="T">Party normalization: sender</Trace>
      <Trace level="1" type="T">Sender scheme external =</Trace>
      <Trace level="1" type="T">Sender agency external =</Trace>
      <Trace level="1" type="T">Sender party external =</Trace>
      <Trace level="1" type="T">Sender party normalized =</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="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">CL_XMS_MAIN->DETERMINE_INT_PID: SAP_CENTRAL</Trace>
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      <Trace level="1" type="T">system-ID = API</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIISUSER</Trace>
      <Trace level="1" type="Timestamp">2008-12-04T12:08:40Z CET</Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--
      -->
      <Trace level="1" type="T">Message-GUID = 003048C1DDAC1DDDB0BF8930B1F0C0C7</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="1" type="T">Queue name : XBTI0009</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="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="1" type="T">----</Trace>
      <Trace level="1" type="T">Going to persist message</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----</Trace>
      </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--
      -->
      <Trace level="1" type="T">--start sender interface action determination</Trace>
      <Trace level="1" type="T">select interface BookingOrderRequest_Out</Trace>
      <Trace level="1" type="T">select interface namespace http://sap.com/xi/XI/Demo/Agency</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <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">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="1" type="T">system-ID = API</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = PIISUSER</Trace>
      <Trace level="1" type="Timestamp">2008-12-04T12:08:40Z 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">>>>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>
      </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>
      </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_SPLIT-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="T">Post-split internal queue name = XBTO2___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="T">Generated prefixed queue name =</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--
      -->
      <Trace level="1" type="T">--start sender interface action determination</Trace>
      <Trace level="1" type="T">select interface BookingOrderRequest_Out</Trace>
      <Trace level="1" type="T">select interface namespace http://sap.com/xi/XI/Demo/Agency</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 FlightBookingOrderRequest_In</Trace>
      <Trace level="1" type="T">select interface namespace http://sap.com/xi/XI/Demo/Airline</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>
      </SAP:Trace>

    Hi!
    But in well-correct-constructed business-scenarios have the same errors (or warnings). Its working.
    The "business confirmation" (about flight data) return. And I see green indicator.
    In my causes, I see yellow indicators.=(
    I think that the problem is in Sender-Receiver agreements.
    I set all Sender Communication Components And all Receiver Communication components.
    Several scenarios worked from time to time, but its not helps.
    Help me! What I must customize?

  • 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

  • Receiver JDBC query

    Hi Experts,
    I would like to know can we find the Query in the PI system at runtime  if the JDBC channel is at the receiver end.
    I am sending the values from SAP to database for updating the data.
    Thanks,

    Could you please let me know where exactly I can see the information in SXMB_MONI ?

  • Dynamic Sql Select Query : getting no response

    Hi
    I am working on a synchronous interface that has jdbc at the receiver side..
    I need to be doing a select dynamically based on a filed from the request like
    select locationId from dbTablename  where empId = 'xxx' AND delFlag =0
    the xxx will be populated from a filed in the request
    For this i have set up a request structure with action as "SQL_QUERY" and the following query in the access field
    SELECT location_id from dbtablename where empID='$cv_EMPID$' and delFlag=0
    I have a key element which has a sub-element "cv_EMPID"
    Unfortunately, the query doestn pull any records from the dbtable..
    In sxmb_moni , I get a query like this
    - <STATEMENT>
    - <TABLENAME action="SQL_QUERY">
      <TABLE>tablename</TABLE>
      </TABLENAME>
      <access>select cv_locationID from tablename where cv_empID='$cv_EmpID$'</access>
    - <key>
      <cv_EmpID>60000016</cv_EmpID>
      </key>
      </STATEMENT>
    but there is no response
    What do u  think is the problem here?
    Thanks
    Krishna

    Hi,
    Refer these links:
    http://help.sap.com/saphelp_nw70/helpdata/en/b0/676b3c255b1475e10000000a114084/content.htm
    RDBMS system integration using XI 3.0 JDBC Sender/Receiver adapter
    SYNCHRONOUS SOAP TO JDBC - END TO END WALKTHROUGH
    Check out this-
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm
    Also check that, JDBC driver is installed correctly- for this
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10
    Check out these links
    http://help.sap.com/saphelp_nw04/helpdata/en/64/ce4e886334ec4ea7c2712e11cc567c/content.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm
    JDBC Receiver Adapter -- Synchronous Select – Step by Step
    Regards,
    Nithiyanandam

  • SQL query for JDBC adapter

    Hello Everyone,
    I am using a simple SELECT to fetch data from sql DB. The only SELECT it seems to fetch data is when it is getting data from sys tables. It does not work for fetching data from application tables created in the sql DB. Could this be a authorization issue? Listed below are the different SELECT  statements used in PI and that works in SQL too.
    1. SELECT Query :  SELECT * from sys.tables
         UPDATE : <TEST>
    The above SELECT works and I can see all the xml messages in SXMB_MONI.
    2. SELECT Query : SELECT * from  sql_ztable
         UPDATE : <TEST>
    The above SELECT does not show any xml messages. There are records in the sql_ztable.  When checking the CC monitoring I get the following message below.
    Polling interval started. Length: 60.0 seconds
      Processing finished successfully
    Any suggestions?
    Thanks,
    Teresa

    Hi Teresa,
    You have to maintain the select and update statements like below.
    Select statement should be like
    Select * from TableName where fieldname = ''
    The field name should be either status field or date field or anything. You will be having some unique field in the table. This field name will ignore the unneccesary fetching records those are already fetched.
    Update statement should be like
    Update TableName set fieldname = '' where filedname = ''
    Here the field name should be same as the select statement filed name. What ever you have used in the filed name in the select statement you have to use same fieldname in the update fieldname.
    Let me know if you have any doubts. If your issue has resolved close this thread.
    Thanks,
    Raju

  • Statistics report using ABAP- SXMB_MONI output

    Dear all,
    I would like to create an ABAP report which should  giveme the details of one particular interface. The details are like How many messages processed, how many of them are success status and how many of them are in error status on daily basis.
    Ideally this is like our SXMB_MONI output where we can choose Sender interface and time interval to get these details. But i want to have a daily job to run this query only for one interface.
    Is it really possible? If yes, how?
    Note: DO NOT SEND any links for SAP PI enhanced monitoring, Payload Search using ABAP report..etc. i had implemented this in my project:)
    Thanks
    Rajesh
    Edited by: Rajesh on Jan 25, 2011 2:38 PM

    Not sure if you already refered this
    http://wiki.sdn.sap.com/wiki/display/Snippets/PIMonitoringFunctionality-FetchingDatafromSXMB_MONIStandardTables-PartIII
    Regards,
    srinivas

Maybe you are looking for

  • Can't install AMD driver properly lost all CCC options and 3D

    Hi everyone, I have HP pavilion g6 , win 7 64 bit. Amd Radeon HD 7400M series and Intel HD graphics. My problem started when my screen was getting  black for seconds  alot and when it comes back it said amd stopped so I decided to update the driver. 

  • Database connector error:Unexpected when connecting to salesforce in CR2008

    ISSUE:: Unable to connect to salesforce in CR2008 as when he tries to select the table in the Database expert he gets an error 'Database connector error: Unexpected' however he is able to connect to salesforce and then select the tables using CR XI R

  • Kernel panic in os x.5

    I have never had a problem with sudden crashes with my mac or os x. In fact, that's why I preffered os x to windows and had decided to make mac my primary computer. However, in the past few days, I have had 3 "kernel panics" which have crashed my com

  • Previous day date to pick up

    i want to pick up the previous latest date from a column. that means if i have a column name batch_id and the dates avaiable are batch_id Previous date 27-06-07 26-06-07 26-06-07 25-06-07 25-06-07 23-06-07 -----saturday date out here Its a sunday the

  • Where can i find the link to download 10.6 to update my computer?

    I have 10.5.8 and i cant find where to upgrade to 10.6 i found all the other ones but i need 10.6 before i can update anything. PLEASE HELPPPP