SXMB_MONI results

Hi all,
1. Can we view both the source and target messages under the SXMB_MONI   transactions.
2. What all steps of the execution pipeline do we skip, when we testing a interface
    from RWB, i.e Pasting the payload in Test message screen.
Thanks,
Younus

Younus,
Yes you can see both the source and target messages in SXMB_MONI.
For source message - Check the payload under Inbound message node.
For Target message - Check the payload under Request message mapping node.
<i>What all steps of the execution pipeline do we skip!!</i>
I would say nothing. All the steps are executed. Could you check what is the first step in pipeline? Its Receiver determination am i right? So what ever methods u used to trigger the messages the pipelines steps will not be skipped.
I think am right, if not please correct me.!!!
Best regards,
raj.

Similar Messages

  • Parser Exception

    I am working on the scenario : Synchronous Outbound ABAP Proxy->XI HTTP Adapter->String back to Proxy
    I get a string back in XI but returns the parsing error. Please help me to resolve this issue.
    The string value sent by the external service is a URL
    "https://stg1-ss1.expr.com/NC2_0Demo/servlets/NCServlet"
    SXMB_MONI result is as follows.
    Kishor Kolhe
    <Trace level="3" type="T">Loaded class com.sap.xi.tf._MM_I058_EXP_ECALS_RESPONSE_</Trace>
      <Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_I058_EXP_ECALS_RESPONSE_</Trace>
      <Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_MM_I058_EXP_ECALS_RESPONSE_</Trace>
      <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 68, 74, 74(:main:, row:1, col:3) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:174) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at

    Hi Kishor,
    The error indicates that message in XI adapter is not matching the source xsd (usually a message type) u maintained in the IR
    e.g. source data type field is in small case and there is case mismatch
    Refer this
    File adapter mapping -  parser: no data allowed here
    Test your mapping in IR with the payload from SXMB_MONI
    /people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios
    Regards,
    Prateek

  • Enhance SAP XI Monitoring

    Hi all,
    I wanted to implement one new thing as an enhancement to my existing xi scenarios.
    I want to create a webservice or html page through which I can access the features of SXMB_MONI with some enhancements say I want one more column as in SXMB_MONI result say IDoc number, or shipment number.
    I want business users to use an html page with search criteria say sender system, receiver system, date, time and the search result will pull the same records as the SXMB_MONI records with some extra columns as idoc nember. Also can i display the error if any in the same record say one more column as error.I also want to display each sxmb_moni result as hyperlink and on clicking it i want the user to see the payload and trace as we have in SXMB_MONI.
    Also which is better option to expose my Function module(Zsxmb_report_test which is a custom function module i will write) as a webservice or create a interface in xi with receicer rfc adapter calling my custom function module and sender say a webservice.
    How-to enrich XI monitor's output  /people/daniele.conca2/blog/2008/07/31/how-to-enrich-xi-monitors-output
    Exposing the XI monitoring functionality as a Web Service  https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/909760cb-0ec8-2a10-4a96-ee8417acfbc9
    I had links to these articles but want to know if anybody has implemented it and how is the performance. Also would appreciate if you can share some good error handling and exception mechanism implemented in XI to make xi scenarios more stable and better maintenance.
    Thanks in advance
    Ravijeet

    Hi All,
    I came across some findings, one is to do Trex search in RWB. Can anyone tell if TREX comes with PI 7.0 installation or u need to make some configuration settings to enable it. As far as I had heard TREX is a similar tool as other CMS search tool as Filenet and Documentum have, can this be enabled to search the payload of sxmb_MONI.
    The other option is the abap reports
    /people/sravya.talanki2/blog/2006/02/21/abap-based-trex-in-xi-proto
    /people/alessandro.guarneri/blog/2006/02/14/super-message-monitor-for-sap-xi
    Need to check this and see how is the performance in PI 7.0 I wanted a seach on xpath and on other basic filtering criteria as sending busineess system, receiver business system, outbound interface, inbound interface and date time as in moni but with some extra filters which will free me from checking each message in SXMB:MONI-
    Also what are the tables of RWB messages and how I can retrieve them. Say I want to compare the number of messages of RWB( message monitoring results)  and integration server, and by this I can know which messages are stuck in adapter engine and not sent to target system or maybe they are picked by adapter engine but not delivered to Integartion server?
    Thanks in advance
    Ravijeet
    Edited by: RAVIJEET DAS on Apr 13, 2009 11:47 PM
    Edited by: RAVIJEET DAS on Apr 15, 2009 9:57 AM

  • How to clear outbound Queue in  SXMB_MONI

    HI Experts,
    Unable to process the file in SXMB_MONI as a result the files are getting strucked with the QUEUE and now how to clear this queues for processsing the file...
    and another i have configure the server with 611 client but while executing the client of the server is showing 001 and we didn't observe initially as it is working fine but when we observed now it is found
    is this has an impact..
    do we need to do any other certain configurations at the Server end..
    regards,
    Kishore

    > There is no URL in SXMB_ADM, how to provide an url there, and even before we didn't get this problem as the files are successfully processsing for the past 3 months in PDN, and now we are getting this problem.
    >
    Hello,
    I have understood your problem but you are not following the steps which we are mentioning here.
    For your above problem you need to follow ONLY step no1 & 2 mentioned in the blog since steps are common for acitvating the proxy and thats way you are getting confused that why I am asking you to follow that blog.
    In the blog step 1 will simply help you creat the RFC destination.
    Step 2 will help you to use the above RFC destinaiton as an url.
    In opionion if you resolve this problem first then it will be easier to solve your queue problem.
    Please let me know if you need more help/clarification in this regard i will help you.
    Regards,
    Sarvesh

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

  • Hiding Pyload in SXMB_MONI of PI

    Hi Experts,
          We have a scenario in which user sends confidential data from DB to PI to ECC.
    In receiver side i am using one BAPI to post data in ECC.
    User wants that data should not be visible in SXMB_moni  or on java stack.
    I was looking for possible solutions.
    I have thought of 2 approaches.
    1- I will use the Payload Hiding Concept by restricting the ability of users to view the payload of message.
    Check SAP Note: 1370334 for Payload Hiding in Java and 1645413 for Payload Hiding in ABAP.
    2- As suggested by william li
    How about getting the value encrypted, just like William Li has described in this Document:
    Developing Adapter User-Module to Encrypt XML Elements in Process Integration 7.1
    but i have few questions about this approach
    My SAP PI is on AIX server. will there be any difference between windows based and AIX based  libraries used in this module?
    Will libraries name used in this module will be same for AIX based server  and Window based server or will be different?
    William has done this implementation on SAP PI 7.1 but i am using SAP PI 7.3.
    Again my question is:
    Will libraries name used in this module will be same for SAP PI 7.1 and SAP PI 7.3  or will be different?
    Please experts suggest me....
    Thanks & Regards,
    Sandeep Sharma

    Hi Sharma,
    Thanks for your reply. My scenario is SOAP to RFC.(synchronus)
    This William Approach is work for my scenario.?
    I completed the process step by step at end i am getting one warning when i tried to deploy into server. please find the  warning.message.
    Successfully deployed:
          0
    Deployed with warnings:
          1
    Failed deployments:
          0
    ~~~~~~~~~~~~~~~~~~~
    1. File:C:\NWDS\nwds-extsoa-7.3-SP08-PAT0003-win32\eclipse\workspace1\XMLEncryptionEAR\XMLEncryptionEAR.ear
    Name:XMLEncryptionEAR
    Vendor:sap.com
    Location:localhost
    Version:2012.12.24.14.21.50
    Deploy status:Warning
    Version:HIGHER
    Description:
    1. Exception has been returned while the [sap.com/XMLEncryptionEAR] was starting. Warning/Exception :[
    ][ASJ.dpl_ds.006153 Error occurred while starting application [sap.com/XMLEncryptionEAR]: It is not started successfully on server nodes [7874250]. In order to bring the server in consistent state stop operation will be performed.
    Error occurred on server 7874250 during startApp of sap.com/XMLEncryptionEAR : com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application sap.com/XMLEncryptionEAR cannot be started. Reason: it has hard reference to application sap.com/engine.security.facade, which is not active on the server because  application is not deployed. Probably refering application sap.com/XMLEncryptionEAR declares runtime but no deploy-time dependency to the referred application which is wrong. Deploy the component sap.com/engine.security.facade or contact owners of application sap.com/XMLEncryptionEAR to check their references..
    at com.sap.engine.services.deploy.server.LifecycleController.startReferencedApplication(LifecycleController.java:608)
    at com.sap.engine.services.deploy.server.LifecycleController.startReferencedComponent(LifecycleController.java:208)
    at com.sap.engine.services.deploy.server.LifecycleController.startReferencedComponents(LifecycleController.java:179)
    at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:208)
    at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:171)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:421)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:473)
    at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesSequentially(ParallelAdapter.java:311)
    at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhases(StartTransaction.java:646)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:1840)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2490)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationOnInstanceWait(DeployServiceImpl.java:2742)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationOnInstanceAndWaitAuth(DeployServiceImpl.java:2891)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2443)
    at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:109)
    at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:80)
    at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:48)
    at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)
    at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:108)
    at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:72)
    at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:1142)
    at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:1031)
    at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:819)
    at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deployInternal(DeployerImpl.java:454)
    at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:228)
    at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:910)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:466)
    at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)
    at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:72)
    at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:43)
    at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:999)
    at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:59)
    at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
    at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
    at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
    Result
    Status:Warning
    Thanks & Regards
    Pavan

  • Disabling "Application Error" to restart using restart button in sxmb_moni

    Hi Experts,
    I have a scenario of JDBC to inbound Proxy.In this we have created Fault message type to capture any error.The requirement is to disable the option of Restart in SXMB_MONI for application error generated with Fault message.We have done coding for generating application error in inbound proxy code.Looking for a quick reply.
    I am looking for disabling the "Application Error" generated from Fault message of inbound proxy to "Resart" using Resart button in SXMB_moni of Application system ECC.what I am referring to is how to disable u201Crestartu201D (not resend) of the messages in SXMB_MONI if they have errors.
    For example, the interface to load some entries calls a proxy which may load some messages successfully and some may result
    in errors. This would appear in the SXMB_MONI with application errors with restart capability. If the user restarts the message it will post the entries again which were successfully posted earlier. We would like to prevent this from happening.
    I have gone through the below links.But no luck.Please suggest me if anyone know the solution/hint for this.
    Proxy framework: Catch CX_AI_SYSTEM_FAULT
    Re: SXMB_MONI - Message Status - Automatic Restart
    /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically

    I do not think you could do that as Asyn messages are always restartable. May be you should look at changing the proxy code so that it does not through application errors but instead would update a Ztable with list of items need to be reprocessed. And this can be sent to the JDBC system as reprocess request.
    VJ

  • Synchronous Inbound ABAP Proxy - Manage status in SXMB_MONI

    Hi Gurus!!
    I have a synchronous SOAP->PI->ABAP Proxy. This ABAP Proxy sends a response to the Sender SOAP with the result of the process execution.
    If the execution finishes with an error (by example, the material to change is locked by another user), the ABAP Proxy sends the response with this error to the SOAP Sender, in the response of the message, without exception. In SXMB_MONI the execution of the message is correct. Is there any way to set the status of the message on SXMB_MONI to other status, and continue sending the corresponding response to the SOAP Sender? If is possible without exception handling?
    Thanks and regards,
    MML001.

    Hope I understood your question. You can send the response (happy flow without exception) and fault message (application or business exception) from the inbound proxy response. But in both cases , SXMB_MONI treats the response message is success. Only in the case of system or connectivity between systems, it shows error message. You could handle even using a specific field in the payload whether the message is successful or not rather than thinking about setting status in monitoring level.

  • No values found in sxmb_moni

    Hello together,
    We are communicating with different sap application system over ABAP proxies.
    But in the sxmb_moni on application system we can not choose any service in the selection in the xml monitor. The same result is for choosing the interface namespace.
    We got no business system back from f4 help back.
    This message is display:
    No values found
    Message no. DH801
    Have you some idea, what are going wrong on the system.
    Must be in the sxi_cache the status green on the application system?
    Is this an authority problem?
    The sldcheck works on the system and the interface also.
    Have a nice weekend.
    Stefan

    Hello,
    I am talking from the sxmb_moni of an erp system for example.
    The manually way is not the best solution, because between the systems are configured the sld communication. Over the sldcheck the erp knows all business systems.
    Bye
    Stefan

  • Read payload for error messages and throw a red flag in SXMB_MONI

    Hello All,
    I am calling a synchronous web service from PI ccBPM and getting a response back to PI ccBPM itself.
    So the steps in BPM are receive(from CRM), sync step (to call web service) and a control step (to end the BPM process).
    The requirement is to check if error_list node in the response from web service call has a value in it and throw an error in SXMB_MONI so that they can easily identify how many messages errored out  out of thousands of messages.
    This is the response structure for web service if there are errors.
    <manageResponse>
      <result>
                    <ErrorList>
                        <object>
                            <hyatt>partnerupdate--NR</hyattt>
                            <Message />
                            <Operation>jukio</Operation>
                            <User>atuser</User>
                        </object>
                     </ErrorList>
    </result>
    </manageResponse>
    Again I only need to see if error_list is not empty and throw a red flag error in SXMB_MONI.
    Thanks
    Mike

    Hi Mich,
      In Response map when Error segment appear's fail the maping so that you can see the list of message in MONI. and do not need to put any conditions in MONI.
    I mean in your Respoinse when ERROR_LIST segment coman under that one manatory field you select and take that field length say 20 characters.
    source field->Substring (0,100) get the 100 characters from source in that case case from source it won't get 100 characters mapping will fail so that you can see the Error messages in SXMB_MONI.
      Finally what I am saying do the wrong condition mapping in the response mapping so that mapping will fail.
    Regards,
    Venu.

  • SXMB_MONI and BPM acknowledgement status updates

    Hi folks,
    We have a scenario in place where we deliver an IDOC to the backend system via the 'send' step and we had acknowledgement property set to 'transport' as we believed that the IDOC adapter would at least return us with exception information when something went wrong with the delivery of the IDOC.  We also added 'deadline' monitoring as well to prevent the BPM of 'waiting forever' ... In case of exceptions or deadline, an alert is thrown.
    This concept worked fine during development testing - IDOCS with status 56 or even 51 got picked up and resulted in error ... ( huray )
    Once tested in acceptance it didn't work at all anymore and all our BPM's ended up in the deadline branch - even for those IDOCS that were processed successfully ...
    After reading SAP note 'Note 837285 - BPE TS: Acknowledgments in the BPE' we understood that the BPM does not support transient errors and as such our concept would never work as we intented it but still it did in development ... even worse it worked sometimes in acceptance as well ...
    After a while we figured out that it worked when we ran transaction SXMB_MONI while the BPM was still waiting for the acknowledgement ... so basically this transaction triggered somehow the update of the acknowledgement status and as such the BPM continued as expected ...
    Then we noticed as well that the transaction even updates statuses of messages of previous days ... ( the BPM for those was obviously allready completed due to deadline ... )
    We are a bit 'lost' here on the whole concept ...
    We read the 'How to handle Acknowledgements' PDF with ALEAUDIT but that only works for logical systems which is not our case ...
    Why is the SXMB_MONI transaction updating the acknowledgement statuses ?  How does it do that - what does it check ? ( we noticed that although IDOCS had status 56 we still got a positive ack status )?  
    In general it seems that using BPM with send step and waiting for ack with the IDOC adapter is useless due to the transient ack status ( as explained in the note ) ... is that assumption correct ?
    Regards,
    Steven

    Hi Steven,
    I can't answer your specific questions, but it occurs to me that the <a href="http://help.sap.com/saphelp_nw04/helpdata/en/44/a1b46c4c686341e10000000a114a6b/frameset.htm">new functionality in SP18</a> to turn received ALEAUDs into "normal" XI request messages may provide a workaround for your problems. The transformed ALEAUDs could be routed to your BPM by way of a correlation on the IDoc number. This way you could react to <i>all</i> ALEAUDs regardless of status...
    Regards,
    Thorsten

  • Editing Payload in SXMB_MONI

    Hi All,
    Is this possible to edit payload in SXMB_MONI.
    I have already the following url which talks about editing payload from RWB - > Message monitoring.
    https://www.sdn.sap.com/irj/scn/wiki?path=%3fpath=/display/xi/whole%252bpayload%252bto%252ba%252bxml%252bfield
    Actually I am looking into the options of editing payload in SXMB_MONI of ECC.
    Thanks in Advance for the help.
    Best Regards
    Ashok

    Hi ,
    am trying to edit only asynchronous message, here is the requirement that we have
    Our OTC team has escalated a support issue with a call tag
    return that could fail as it comes into SAP. 
    A "call tag" return is the result of a mis-shipment where the customer
    either received damaged product or the wrong product.  These returns
    come in with not only the account but also the invoice number.  The
    return is referenced to the originating invoice and the credits are
    created based on the prices and discounts that are on the invoice.   If
    the invoice number on the return does not match an invoice for the
    account, then the return will fail.
    For some reason, the return fails in the ABAP Proxy layer of SAP ECC
    with Application errors and does not provide the ability for the
    business to repair the data. 
    Unfortunately, this failure occurs frequently in production today (1-2
    a week - as many as 15) and we anticipate that we will continue to see
    these failures with SAP.  The invoice is being manually keyed at the
    returns setup.  Sometimes the error is caused by a keying mistake and
    sometimes the documentation (call tag, invoice, packing list) is not
    legible.  
    We also know that External Vendor cannot correct and resend the
    return.   Their process not only creates the return for credit, but
    also has to account for all of the inventory that is being sent for
    destruction.  Their quality steps lock the return down once it has been
    sent to client for credit.  Their system will not permit the return to
    be corrected and resent. 
    We do, however, need to find a solution for the correction of these
    failed returns that allows us to account for the return and create the
    proper credit.
    Returns (Order To Cash) team require ability to Edit the payload of
    Asynchronous ABAP proxy messages in SAP ECC system, which are failed
    due to Incorrect data with Message Status as "Application Error -
    Manual Restart Possible".
    For this the proposed solution is to Edit the Payload via SAP
    XI's "Message Editor" in Runtime Work Bench -> Message Monitoring ->
    Proxy Runtime of SAP ECC system.
    The message editor is configured in SAP XI and ECC system with the
    required roles and SAP Correction Notes.
    Message Editor is NOT Working for messages with "Application Error -
    Manual Restart Possible" status, while it is working as expected for
    messages with "System Error - Manual Restart Possible" status.
    Below Error Message is seen, while trying to edit the message with
    Application Error in SAP ECC,
    " Message editor can only be used for executable, asynchronous XI
    messages with errors"
    This issue in SAP XI's Message Editor needs to be resolved to complete
    the testing of proposed solution in Sandbox systems and make a decision
    on the solution to be used for this business requirement.

  • Locate an entry in SXMB_MONI for a particular value(IDoc numbe) in payload

    Hi,
         We have an R/3 – XI – Third party scenario. R/3 is sending tones of IDocs. In some cases some IDcos are not going beyond XI. In BD64 we get a status code 40(from XI).
    We would like to locate the entry in SXMB_MONI for one particular IDoc. The only way now is to manually open all entries for the service/interface combination and see the IDoc number which is becoming very painful.
    Since we are in testing phase, there are a lot of entries for the sender/receiver interface combination. We tried to narrow down the result in SXMB_MONI with all possible search criteria like service, interface, etc. Time is ruled out because, we have queues with a lot of messages and never know when a particular message is processed by XI  (so the time of sending from R/3 may not make sense in SXMB_MONI as a search criteria).
    So my question is: it there a way to find an entry in SXMB_MONI for a particular IDoc number (which is present in the payload) ?
    As a programmer, I could think about a program which does this ?! But don’t know in which tables the entries are saved or the relation between the tables ?!
    Can someone please throw some light on it ?
    Thanks in advance
    Cheers
    danus
    null

    There is a way actually.
    Idoc Tracking is available from Sp18 ( I think ).
    http://help.sap.com/saphelp_nw04/helpdata/en/c1/bab13bb3acd607e10000000a11402f/content.htm
    Look into Idoc Tracking in this link.
    Regards
    Bhavesh

  • Still Awaiting Acknowledgement in SXMB_MONI - RFC Adapter

    Have a scenario where we are using an RFC adapter on the reciever end to bring in data into R/3. The message in SXMB_MONI is showing successfully processed, but in column "Ack Status" - the icon states "Still Awaiting Acknowledgement". As a result of this the data is not being posted into R/3.
    What is the best way to check the reason for "Still Awaiting Acknowledgement" and how to fix the problem so that the data is successfully processed in the R/3 system as well. Have already checked the adapter engine for adapter RFC and it does not show the any status - error or successful.

    Hi,
    RFCs usually use application acknowledgements and not system acks, and hence we shouldn't be getting that 'awaiting ack' symbol in the moni.
    Try unchecking the 'maintain order at runtime' checkbox in interface determination and see if that helps.
    Also make sure that the sender adapter's quality of service(QOS) is not EOIO.
    Regards,
    Smitha.

  • SXMB_MONI -- Runtime Table

    Hi,
    In SXMB_MONI -->  Inbound -> SOAP Header --> RunTime I can see this values below (HOST is most interesting).
    I have problems debugging (SXMB_MONI)  in order to see which table(s) data is stored.
    <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
    <SAP:Host>sappi03</SAP:Host>
    Any one knows which table to look in ?
    Br
    Martin
    Edited by: Martin Andersson on Jun 17, 2008 2:42 AM
    Edited by: Martin Andersson on Jun 17, 2008 5:34 AM

    Hi Martin,
    Here are some tables.
    SXMS_AE_AUDITCNF____________XI: Adapter Runtime Data
    SXMS_AS_STATUS__________________Status Table of Synchronous/Asynchronous Bridge
    SXMS_MULTIM_REF__________________Link-Table Leading Message - SubMessages
    SXMS_PACKCOUNT__________________Counter for Packed Messages
    SXMS_QUEUE_PRIO__________________Prioritized EOIO Queues
    SXMS_SYSPAR__________________SAP System Parameter and Storage Location
    SXMSAEADPMOD__________________XI: Adapter and Module Information
    SXMSAEADPMODCHN____________XI: Adapter Module Chains
    SXMSAEAGG________________________XI: Adapter Runtime Data (Aggregated)
    SXMSAERAW________________________XI: Adapter Runtime Data (Raw Data)
    SXMSALERTCNTRL____________ Control Table for XI Alerts
    SXMSALERTCONTROL____________Control Table
    SXMSALERTLOG__________________XI Alert Log
    SXMSALERTLOGGER____________XI Alert Logs
    SXMSALERTRULES__________________Rules for Alert Generation: Msg Header ->Alert Category
    SXMSALERTSTEPS__________________PMI Process Steps for Alerting
    SXMSALERTTMSTMP____________Time Stamp of Last PMI Process Instance Chhecked
    SXMSARCITF________________________XML Message Archiving
    SXMSCLUP________________________XMB: Property Cluster
    SXMSCLUP2________________________XMB: Property Cluster (Switch Table)
    SXMSCLUR________________________XMB: Resources Cluster
    SXMSCLUR2________________________XMB: Resources Cluster (Switch Table)
    SXMSCONFDF__________________XMS: Integration Engine Configuration Para
    SXMSCONFVL__________________XMS: Integration Engine Configuration Data
    SXMSDCONF________________________Integration Engine: Settings for Deletion
    SXMSEPCACHE__________________XI: Runtime Cache for Exchange Profile
    SXMSEPCLOG__________________XI: Log Table for Runtime Cache for Exchange Profile
    SXMSFTEST________________________Table for XI Runtime Engine Test
    SXMSGLOBAL__________________Integration Engine: Obsolete
    SXMSHELP________________________Help Assistant
    SXMSHELPT________________________Help Assistant (Short Text)
    SXMSINTERFACE__________________Sender/Receiver Definition
    SXMSINTF________________________XMB: Container for Application Monitoring(Template)
    SXMSINTFT________________________Sender/Receiver Interfaces
    SXMSITF________________________Search Help for Interface for Archiving (Without Content)
    SXMSJINFO________________________Integration Engine: Job Information
    SXMSJOBS________________________Jobs for Time-Controlled Message Processin
    SXMSMONSEL__________________Selection Table for Integ. Engine Application Monitoring
    SXMSMONSET__________________Selection Table for Integ. Engine Application Monitoring
    SXMSMSGDEF__________________Message Definition
    SXMSMSGFILLED__________________Message for a Message Definition Saved
    SXMSMSGFILTER__________________SAP XI: Filter for Sender/Receiver Attributes
    SXMSMSGINDCUS__________________SAP XI: Configuration Indexing of Messages
    SXMSMSGINDLOG__________________SAP XI: Message Indexing Log
    SXMSMSGINDSRV__________________SAP XI: Services for Indexing Messages
    SXMSMSGPMI__________________Using XI Messages in PMI
    SXMSMSGREF__________________Message Reference Storage
    SXMSMSTAT________________________Exchange Infrastructure: Message Status
    SXMSMSTATT__________________Exchange Infrastructure: Message Status Description
    SXMSPADM________________________XMS Pipeline: Execution Settings
    SXMSPCONF________________________XMB: Administrative Data for Pipeline Conf
    SXMSPEMAS________________________Integration Engine: Enhanced Message Queue(Master)
    SXMSPEMAS2__________________Integration Engine: Extended Message Queue(Switch Table)
    SXMSPENTRY__________________XMS: Map Inbound Pipelines to XMB Pipeline
    SXMSPERFC________________________SXMS: Runtime Measurement Results
    SXMSPERFCD__________________SXMS: Data Table for Online Performance Data
    SXMSPERFCH__________________SXMS: Header Table for Online Performance Data
    SXMSPERFT________________________XMS: Monitor Table for Runtime Measurement
    SXMSPERRO2________________________XMB: Message Queue (Entries with Errors) (Switch Table)
    SXMSPERROR__________________XML Message Broker: Message Queue (Incorrect Entries)
    SXMSPFADDRESS__________________Integration Engine: Sender and Receiver Information
    SXMSPFAGG________________________Integration Engine: Aggregated Data for Performance Display
    SXMSPFCOMPONENT____________Integration Engine: Component Information
    SXMSPFMSGTYPEDB____________XMB: Selektionsdaten für Monitoring
    SXMSPFRAWD__________________Integration Engine: Data Table for Raw Data for Performance
    SXMSPFRAWH__________________Integn Eng: Header Table for Raw Data for Performance Evaln
    SXMSPFSEARCHDB__________________XMB: Selektionsdaten für Monitoring
    SXMSPHIST________________________XML Message Broker: History
    SXMSPHIST2________________________XML Message Broker: History (Switch Table)
    SXMSPIPE________________________XML Message Server: Pipeline Definition
    SXMSPIPEEL________________________Pipeline Element Definition
    SXMSPIPET________________________XMS: Pipeline Description
    SXMSPLELT________________________XMS: Description of Pipeline Elements
    SXMSPLSRV________________________XMS: Pipeline Service Specification
    SXMSPLSRVT________________________XMS: Description of Pipeline Services
    SXMSPMAST________________________Integration Engine: Message Queue (Master)
    SXMSPMAST2__________________XML Message Broker: Message Queue (Master)
    SXMSPMIRAW__________________Integration Engine: Performance Data Extracted from PMI
    SXMSPTRACE__________________HTTP Trace
    SXMSPVERS________________________Integration Engine: Message Version
    SXMSPVERS2________________________Integration Engine: Message Version (Switch Table)
    SXMSQUEUE_RCV__________________Mapping Queue Receiver
    SXMSQUEUE_REORG____________Storage Location for Queues That Are Being Reorganized
    SXMSQUEUESTATUS____________Queue Status During Upgrade Phase
    SXMSRECVT________________________Technical Receiver
    SXMSRTDIAG__________________Entries for Support Diagnostics
    SXMSSPDIAG________________________Objects for SXMS SUPPORT DIAGNOSTICS
    SXMSSPDIAGS__________________Objects for SXMS SUPPORT DIAGNOSTICS
    SXMSSYERR________________________XMS: System Error Error Codes
    SXMSSYERRT________________________XMS: Brief Description of System Error Codes
    SXMSTRANS_CONFIG____________Configuration Table for Message Transfer
    SXMSTRANS_HEADER____________Lookup Table for Message Transfer
    SXMSTRANS_MSG__________________Body Table for Message Transfer
    SXMSTRC_DAT__________________XMS: Trace Data
    SXMSTRC_SEL__________________XMS: Selection Criteria for Trace Start
    SXMSTSACT________________________Action Table for Integration Server Troublshooting
    SXMSTSTRIG________________________Table of Troubleshooting Trigger
    Best Regards,
    Nagesh Y R
    Edited by: Nagesh Rudhra Yellapu on Jun 17, 2008 1:43 PM

Maybe you are looking for

  • Why does itunes keep saying I don't have enough memory on my windows 8.1

    When I am trying to download new songs, import a CD or trying to watch a TV segment on I tunes on my Samsung Laptop computer for Windows 8.1 and I keep getting messages saying I don't have enough memory and I also keep receiving messages that I'm not

  • O/P ALV in edit mode

    Hi All, Can any on tell me how to get the coloumns of the O/P ALV table in eit mode. I have an alv table ready its working fine. All I know is I need to use some codes like call method l_value->if_salv_wd_table_settings~SET_READ_ONLY   EXPORTING    

  • Duplicate processing by DBAdapter when using Distributed Polling with Logical Delete Strategy

    We have DBAdapter based polling services in OSB running across two Active-Active clusters (total 20 managed service across 2 clusters), listening to the same database table. (Both clusters read from the same source DB). We want to ensure distributed

  • Acrobat Pro XI messages in wrong language

    I have uploaded Acrobat Pro XI from a CD at my office, with the serial number my coworkers have used successfully.  I select the installation language as English, and the program when it runs is in English, but all of the alert messages are in Dutch.

  • B2B Help to do following setup : Message from EBS to BPEL to B2B to TP

    I created a BPEL to send message to B2B and it works. BPEL send message to B2B. Identifies Agreement and etc. Message have to hit TP using HTTP Post. TP uses port 443. In the trading partner setup I tried different channel I get following message whe