Error in SXMB_MONI for HTML to Webservice Scenario

Hi Experts,
I am facing following error Error in SXMB_MONI for HTML to Webservice Scenario
"Runtime exception occurred during application mapping com/sap/xi/tf/_MM_EmailRequest_To_ValidateEmail_; com.sap.aii.utilxi.misc.api.BaseRuntimeException:Content is not allowed in prolog."
Only one field is used i.e. email address and mapped properly in IR but still the error is persisting, Please suggest some way out.
Regards,
Nitin

Hi,
Mapping internall follows the SAX parser. Please check if you are trying to process the data of large size.
generally while parsing the large data this exception get raised. Even though there is just one field, what is the data size you are trying to pass.
Thanks
Swarup

Similar Messages

  • Getting  Error  IN sxmb_moni   for FILE TO FILE SCENARIO

    Hi  ,
        I  did  File to file scenario by using Content conversion ..(that is  from  .TXT format to .XML format)  for a single  record it was  working fine.. if i put  0: Unbounded in my source structure means i'm getting  this following error ..
    my source structure is  like this :
    SENDOR_DT  
         STUDENT
              DETAILS
                    NAME
                    NO
                    ADRESS
                    BRANCH
    SO, I PUT   Details as 0: Unbounded.. if i did't put as unbounded means it's working fine for a single record.. but if i put Unbounded means immediately i'm getting the following error ...
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Request Message Mapping
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>Application</SAP:Category>
      <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
      <SAP:P1>com/sap/xi/tf/_TRNG_TEST_1_MM_</SAP:P1>
      <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
      <SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>During the application mapping com/sap/xi/tf/_TRNG_TEST_1_MM_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    plz provide me the solution..
    Thanks
    Babu

    Hi Babu
    please check whether the occurence of the target structure in multiple times or not. if it is 1..1 then change it to 0..unbounded.
    case2: take the payload from the sxmb_moni and put tha payload in the message mapping you will come to know where is the error.
    if still have the problem please reply back
    Thanks
    Rinku
    Hi babu
    check whether the occurence for the target node is 0..unbounded.
    Thanks
    Rinku
    Message was edited by:
            Rinku Gangwani

  • Error  in SXMB_MONI for Idoc to File Scenario (missing of field plant

    Hi SapAll.
    here i have got a tricky situation where in a Idoc(Matmas.Matmas05) to file Interface thorugh XI there is an error message raising in sxmb_moni.
    to get the conclusion for this error i just copied the message from Sxmb_moni and tried with  Message mapping in Design by just pasting there,after all this process iam getting the error message as below
    Cannot produce target element /MT_FCI_MATERIAL/fcidataimport/objects/object/extensions/collection[3]/row/fields/PLANTEXT. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
    When i go the mapping program it is defined as
    if Matmas.matmas05WERKS(sender) exists then map werks to plant tex(reciver MType)t else map constant with(null value) to reciever(MType).
    and the important thing is the here the occurance of field plant text is 1.1.
    so iam not sure on why the error was raised in message mapping as every thing is fine.
    can any body help in slolving this.
    regards.
    Varma

    if Matmas.matmas05WERKS(sender) exists then map werks to plant tex(reciver MType)t else map constant with(null value) to reciever(MType).
    When WERKS's is absent the IF doesn't have a value and hence the whole context gets suppressed which returns the error. What you have configured would work fine if WERKS is there but with no value. Here the case is a bit different. WERKS itself is not coming. Your logic doesn't handle that. Hope you got what I intend to convey.
    Correct me if I am wrong but the logic is you need to pass WERKS value to PLANTTEXT if value comes else map a blank constant...right??
    If so, why not just use mapWithDefault
    WERKS -> mapWithDefault(blank contant) -> PLANTTEXT
    This way if WERKS comes teh value would be passed, if comes with blank value blank value would eb passed if doesn't come atall, even then a blank value would be passed.
    Regards
    Soumen...

  • The page cannot be displayed: ITS error: SAP GUI for HTML

    Hello,
    I have created an iView that connects with a ECC system. When I clic on System Administration --> Support --> SAP Application --> SAP Transaction :
    System: ECC
    Transaction: su01
    SAP GUI Type: SAP GUI for HTML
    It shows: The page cannot be displayed.
    It's manadory to use SAP GUI for HTML. Please, Do you have any idea??
    Thank you
    Best,

    Hello Virginia Rodríguez,
    1)Kindly check that System ECC in Portal is Up and Running under System Administration.
    2) if u r done with first step then can try SAP GUI for Window in creation of Iview
    it will Work.
    Regards.
    Soni Vinit

  • Need steps required for http to webservice scenario

    Hi All
    I need the IR and ID steps for my below scenario.
    Request will come as HTTP request from a web site and web service will get the request and same time it will send the response back to HTTP.basically this will be synch process.Need help urgently.
    Girish

    Hi,
    The following are needed for idoc to file scenario...
    In R3...
    RFC dest to XI (sm59)
    Logical system (bd54)
    Port to XI (we21)
    Partner profile for the logical system (we20)
    In XI...
    RFC dest to R3 (sm59)
    Port to R3 (idx1)
    create metadata for the idoc (idx2)
    In sld...
    create business system for R3.
    Regards,
    Uma

  • Error in AE for File to File scenario

    Hello,
    i created a scenario for file to file. My file is picking up, but when i see sxmb_moni, i am seeing below error. Is there anything to configure for AE.
    <b>no_messaging_url_found: Unable to find URL for Adapter Engine</b>
    Please advice,
    Srinivas

    Hi,
    Under SLD check if you have maintained  Pipeline URL for XI Bsuiness system. Under tab "Integration" you will find parameter "Pipeline URL" and shd have value something like "http://dev server:port /sap/xi/engine?type=entry...
    If this entry is correct then try to refresh Adapter Cache using TC : SXI_CACHE..
    MenuGoto>Adapter Engine cache ( Click on refresh button)..
    Hope this will help.
    Nilesh

  • Error in TRFC for IDoc to File scenario while sending IDoc

    Hi,
    Configured of 'IDoc to file' scenario is completed. Executed a stand alone program to post IDocs to XXI system using a RFC destination with required previleges.
    Outbound IDoc has status successful, but it is blocked in the source system and can be viewed in TCode: SM58 (Transaction RFC). The error status is set as ':00'.
    When I tried menu item 'Edit>>Execute LUW', I got the status message as 'Function module does not exist or EXCEPTION raised'.
    For your information, User used in RFC destination is communication user with SAP_ALL profile(in XXI system).
    Can anybody help me out in resoving the error?
    Regards,
    Suraj Kumar

    Hi,
    Thanks for your reply.
    It is successfully tested and FYI as the user specified in RFC Destination is a communication user in destination system (XI), it does not have remote logon.
    Hope I am clear.
    Please let me know, if you need any further information.
    Regards,
    Suraj

  • Error in SXMB_MONI of SOAP to JDBC scenario

    <Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:MT_Soap_response. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:352) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:60) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:94) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:67) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor356.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy153.processFunction(Unknown Source) at sun.reflect.GeneratedMethodAccessor371.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7650) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2275) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1614) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8009) at com.sap.mw.jco.JCO$Server.work(JCO.java:8129) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8076) at com.sap.mw.jco.JCO$Server.run(JCO.java:7992) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns0:MT_Soap_response. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:212) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:347) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:60) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:94) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:67) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor356.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy153.processFunction(Unknown Source) at sun.reflect.GeneratedMethodAccessor371.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7650) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2275) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1614) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8009) at com.sap.mw.jco.JCO$Server.work(JCO.java:8129) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8076) at com.sap.mw.jco.JCO$Server.run(JCO.java:7992) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</Trace>
      <Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_Jdbc_Response_Soap_Response_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:MT_Soap_response. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd</Trace>
      <Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_Jdbc_Response_Soap_Response_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:MT_Soap_response. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:94) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:67) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor356.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy153.processFunction(Unknown Source) at sun.reflect.GeneratedMethodAccessor371.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7650) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2275) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1614) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8009) at com.sap.mw.jco.JCO$Server.work(JCO.java:8129) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8076) at com.sap.mw.jco.JCO$Server.run(JCO.java:7992) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:MT_Soap_response. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:352) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:60) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:94) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:67) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor356.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy153.processFunction(Unknown Source) at sun.reflect.GeneratedMethodAccessor371.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7650) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2275) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1614) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8009) at com.sap.mw.jco.JCO$Server.work(JCO.java:8129) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8076) at com.sap.mw.jco.JCO$Server.run(JCO.java:7992) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.mappingtool.tf3.IllegalInstanceException: Cannot produce target element /ns0:MT_Soap_response. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd at com.sap.aii.mappingtool.tf3.AMappingProgram.processNode(AMappingProgram.java:212) at com.sap.aii.mappingtool.tf3.AMappingProgram.start(AMappingProgram.java:347) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:60) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:91) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:94) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:67) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0.processFunction(MappingServiceObjectImpl0.java:131) at sun.reflect.GeneratedMethodAccessor356.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy153.processFunction(Unknown Source) at sun.reflect.GeneratedMethodAccessor371.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:169) at com.sap.engine.services.rfcengine.RFCJCOServer.handleRequest(RFCJCOServer.java:156) at com.sap.mw.jco.JCO$Server.dispatchRequest(JCO.java:7650) at com.sap.mw.jco.MiddlewareJRfc$Server.dispatchRequest(MiddlewareJRfc.java:2275) at com.sap.mw.jco.MiddlewareJRfc$Server.listen(MiddlewareJRfc.java:1614) at com.sap.mw.jco.JCO$Server.listen(JCO.java:8009) at com.sap.mw.jco.JCO$Server.work(JCO.java:8129) at com.sap.mw.jco.JCO$Server.loop(JCO.java:8076) at com.sap.mw.jco.JCO$Server.run(JCO.java:7992) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)</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_TO_PERSIST">
      <Trace level="3" type="T">Persisting message Status = 023</Trace>
      <Trace level="3" type="T">Message version 001</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
      </Trace>
      </Trace>
      <Trace level="1" type="T">SystemError message generated. Guid: 77F087459C16DB10E1000000C0A8641B</Trace>
      <Trace level="1" type="T">Error during execution of message : 6733E5718FF711DB97EE00132026BD95</Trace>
      <Trace level="1" type="T">ApplicationMessage was (=RefToMsgId): 659AF5F08FF711DB85C800132026BD95</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="3" type="T">Persisting message Status = 023</Trace>
      <Trace level="3" type="T">Message version 000</Trace>
      <Trace level="3" type="T">Pipeline CENTRAL</Trace>
    This is the error showing in SXMB_MONI, can u please tell where i went wrong...
    I did Transforormation correctly data is entered into JDBC but it doesn't picking up the response into SOAP message.
    Can u please find out the error..
    Regards,
    Pushparaju.B

    This is my JDBC Request structure...
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_Jdbc_request xmlns:ns0="http://soaptojdbcsync.com/demo"><STATEMENTNAME><TEST1 action="INSERT"><TABLE>TEST1</TABLE><access><BPID>1</BPID><REQ_CUST_NUM>234</REQ_CUST_NUM><MATERIAL_NUMBER>1067</MATERIAL_NUMBER><QTY>234</QTY><SUPP_CUST_NUM>456</SUPP_CUST_NUM></access></TEST1></STATEMENTNAME></ns0:MT_Jdbc_request>
    This is my JDBC Response Structure....
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:MT_Jdbc_request_response xmlns:ns0="http://soaptojdbcsync.com/demo">
       <STATEMENTNAME>
          <TEST1 action="">
             <TABLE/>
             <access>
                <BPID/>
                <REQ_CUST_NUM/>
                <MATERIAL_NUMBER/>
                <QTY/>
                <SUPP_CUST_NUM/>
             </access>
          </TEST1>
       </STATEMENTNAME>
    </ns0:MT_Jdbc_request_response>
    can u see the structure if i went wrong with it

  • Application error in SXMB_MONI in Proxy to webservice

    Hi all
    I've constructed an proxy -> XI -> External web service scenario.
    In the sxmb_moni transaction i got two response message, I got two different error message. One is
    "com.sap.security.core.server.ws.service.WSSecurityException". Another is "Unable to determine name of mapping
    program".I think I made no mistake during the design and configuration process.All this makes me confused. I still
    and soap response payload is
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
      <ns1:com.sap.security.core.server.ws.service.WSSecurityException xmlns:ns1="http://sap-j2ee-engine/error">000D60A85C830071000000330000391C0004400D9EC1282E : Found 0 operation definitions using keys: Key name:'first-body-element-ns' key value:'urn:TestServiceBeanWsd/TestServiceBeanVi/rpc'; Key name:'first-body-element-name' key value:'sayHelloIn';</ns1:com.sap.security.core.server.ws.service.WSSecurityException>
    haven't found a way to resolve this.
    Thanks!

    Hi all,
    <b>what is soap action must i give in this wsdl</b>
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:TestServiceBeanWsd/TestServiceBeanVi/rpc">
         <wsdl:types>
              <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="urn:za.co.lonmin.webservicebean" targetNamespace="urn:za.co.lonmin.webservicebean" elementFormDefault="qualified">
                   <xsd:complexType name="ReturnType">
                        <xsd:sequence>
                             <xsd:element name="resultCode" type="xsd:int" />
                             <xsd:element name="transactionOK" type="xsd:string" minOccurs="0" nillable="true" />
                        </xsd:sequence>
                   </xsd:complexType>
                   <xsd:complexType name="EmployeeData">
                        <xsd:sequence>
                             <xsd:element name="dateOfEngagement" type="xsd:dateTime" minOccurs="0" nillable="true" />
                             <xsd:element name="dateOfTermination" type="xsd:dateTime" minOccurs="0" nillable="true" />
                             <xsd:element name="employeeNumber" type="xsd:string" minOccurs="0" nillable="true" />
                             <xsd:element name="firstname" type="xsd:string" minOccurs="0" nillable="true" />
                             <xsd:element name="lastname" type="xsd:string" minOccurs="0" nillable="true" />
                             <xsd:element name="occupationCategoryCode" type="xsd:int" />
                        </xsd:sequence>
                   </xsd:complexType>
                   <xsd:complexType name="ArrayOfEmployeeData">
                        <xsd:sequence>
                             <xsd:element name="EmployeeData" type="EmployeeData" minOccurs="0" maxOccurs="unbounded" nillable="true" />
                        </xsd:sequence>
                   </xsd:complexType>
              </xsd:schema>
              <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                   <xsd:complexType xmlns:ns1="urn:za.co.lonmin.webservicebean" name="sayHelloIn">
                        <xsd:sequence>
                             <xsd:element name="action" type="xsd:string" />
                             <xsd:element name="message" type="ns1:ArrayOfEmployeeData" />
                        </xsd:sequence>
                   </xsd:complexType>
              </xsd:schema>
         </wsdl:types>
         <wsdl:message name="sayHelloIn">
              <wsdl:part name="sayHelloIn" type="sayHelloIn" />
         </wsdl:message>
         <wsdl:message name="sayHelloOut">
              <wsdl:part xmlns:generateduniqueprefix0="urn:za.co.lonmin.webservicebean" name="Response" type="generateduniqueprefix0:ReturnType" />
         </wsdl:message>
    </wsdl:definitions>
    Thanks
    kiran

  • Error in Protocol for Generation of Integration Scenario Configuration

    Hi,
    If I try to generate my Integration Scenario in simulation or real mode I get the follwoing error allways in the "Generation Statistics" section (last entry):
    <b>
    Error when creating or changing configuration objects  0</b>
    If I save it and check it - no errors could be found. Any ideas?
    Regards,
    Christian

    Hi Christian,
    you working with SAP software
    > Error when creating or changing configuration objects 0
    means:
    zero errors...
    Regards,
    Udo

  • Error in Synchronus File to Webservice Scenario

    Hi Friends,
    Following is my Scenario,
    I am trying to Send a file from SWC(Software Componebt) A(System) to SWC B(Web Service) and want to have response from Web Service.
    When I am trying the Scenario for QOS Exactly Once than Request is going to Web Service Successfully but when I am changing the QOS to Best Effort (For Synchronus scenario) in Sender Communication Channel then Communication Component B to A triggers first and then A to B rather it should happen in reverse way I suppose. Following is the Error which I am getting in SXMB_MONI for the Scenario for Sender as B and Reciever as A.
    " <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.IOException: invalid content type for SOAP: TEXT/HTML; HTTP 404 Not Found</SAP:AdditionalText>"
    Your any input will be highly appreciated.
    Regards,
    Nitin Patil

    Hi,
    your file to web service req msg scenario worked as you said from system A to system B.
    now your msg interface for web service will be synchronous having req and response.
    now make another interface for receiving response from system B and make it asnychronous.
    so when system B will send a response msg, then you will map it to above msg. then you will send this response msg by a receiver file adapter by configuring in ID.
    Regards,
    Rajeev Gupta

  • Send Alerts(e-mail) for errors in SXMB_MONI(message mapping exceptions)

    Good afternoon !
            I´m configuring SAP Netweaver PI 7.0(SP13) to use Alert Framework to send Alerts when errors occurs in the interfaces processing.
            I just achieved configure to send alerts when errors ocurrs in the Adapter Framework but, I can´t configure correctly to send alerts when errors ocurred only in SXMB_MONI(for example, message mapping exception in asyncronous interface).
            I just followed the instructions at Michal Krawczyk
    weblog(/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step) and, initially, this was not sufficient to start to send alert when errors occurs only on SXMB_MONI, so, I researched and found some configurations to do in CCMS(started from here: http://help.sap.com/saphelp_nw70/helpdata/en/e3/bf3b7a8ccb8040b638ff732c551aeb/content.htm), jobs to start events collectors, etc, and after this, I could see a mail for an message mapping exception. BUT, this message, sent from CCMS to ALM, doesn´t carry out all the message parameters, like message Id, sender(service, interface), receiver(service, interface), that is very important to help to find the message with errors to be solved.
            There is somebody here that already done the Alert configuration to send messages for errors found only in SXMB_MONI(Monitor for processed XML Messages) ?
            There is a better way to achieve this ?
            Thank you for your attention,
            Wilson Rodrigo dos Santos
            SAP Netweaver XI/PI Consultant

    Hi
    Go through these links and follow it.
    ALERTS CONFIG AND STUFF
    http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm
    XI: Alerts - Step by step
    /people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
    http://help.sap.com/saphelp_nw04s/helpdata/en/d0/d4b54020c6792ae10000000a155106/frameset.htm
    Triggering by Calling a Function Module Directly.
    /people/bhavesh.kantilal/blog/2006/07/25/triggering-xi-alerts-from-a-user-defined-function
    Alerts with variables from the messages payload (XI) u2013 UPDATED
    /people/michal.krawczyk2/blog/2005/03/13/alerts-with-variables-from-the-messages-payload-xi--updated
    Simple Steps to Get Descriptive Alerts from BPM in XI
    /people/community.user/blog/2006/10/16/simple-steps-to-get-descriptive-alerts-from-bpm-in-xi
    Triggering XI Alerts from a User Defined Function
    /people/bhavesh.kantilal/blog/2006/07/25/triggering-xi-alerts-from-a-user-defined-function
    Throwing Smart Exceptions in XI Graphical Mapping
    /people/alessandro.guarneri/blog/2006/01/26/throwing-smart-exceptions-in-xi-graphical-mapping
    /people/sukumar.natarajan/blog/2007/01/07/how-to-raise-alerts-from-abap-proxy
    /people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide
    /people/sravya.talanki2/blog/2006/11/22/error-handling-framework-xiout-of-the-box-episode-1
    /people/ginger.gatling/blog/2005/06/16/integrating-alerts-into-uwl--its-no-problem
    /people/aravindh.prasanna/blog/2006/02/20/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-3
    /people/aravindh.prasanna/blog/2005/12/24/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part-2
    /people/aravindh.prasanna/blog/2005/12/23/configuring-scenario-specific-e-mail-alerts-in-xi-ccms-part--1
    http://help.sap.com/saphelp_nw2004s/helpdata/en/56/d5b54020c6792ae10000000a155106/content.ht
    http://help.sap.com/saphelp_nw04/helpdata/en/2c/abb2e7ff6311d194c000a0c93033f7/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/frameset.htm
    /people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step
    check this links.
    https://www.sdn.sap.com/irj/sdn/forums
    Trouble shooting Alert configuration:
    /people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide
    /people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
    Alert Inbox
    http://help.sap.com/saphelp_nw04/helpdata/en/80/942f3ffed33d67e10000000a114084/frameset.htm
    Alert Notification Step-by-Step
    http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm
    Defining Alert Classifications
    http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm
    Triggering Alerts
    http://help.sap.com/saphelp_nw04/helpdata/en/49/cbfb40f17af66fe10000000a1550b0/frameset.htm
    Setting up alerts
    Setting up alerts in RZ20
    Alert Management
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e04141e8-0f11-2a10-adaa-9d97b062c2df
    Alert Notification
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/90f449a8-a6db-2910-a386-d2b5999f5751
    /people/matt.kangas/blog/2006/06/27/personalized-alert-delivery
    Thanks
    Saiyog

  • XI Contents : Error Handling : Syncronous Proxy - WebService Scenario

    Hi,
    I am working on Syncronous : Proxy <-> XI <-> WebService Scenario.
    I am using Standard XI Contents from XI and SAP side.
    Meaning : All the design objects like Message Interface / Message Types / Data Types etc are NOT created by me, but I am using from Standard XI Contents EA-HR 600. I did all the Configuration of the Scenario by using these Design objects.
    In short , I can not change any of the Design object as it belongs to SAP.
    Now, the scenario works fine. But I need to cater for Error handling.
    Any suggestion.
    I can not create fault messages as it is SAP's objects.
    Thanks.
    Dk

    Thanks for suggestions.
    Now my comment on these suggestions:
    Option1 by Bhavesh. Copy Contents to my namespsce :  I can do that, but here I need to tell you something. I have used Contents (Design Objects) and I didnt have to even create or activate any proxy ( I was amzed to see that ). Now, coping all the contents to my namespace will give me flexibility to add Fault Message (which is currently not avilable in standard content). but..but..I will have to create and generate / activate the proxy. ( Am I right?). Then where should I use this proxy? How my application will talk to this proxy? (I am not sure if I made my point clear). Currently I dont have to worry about communication between this HR application with standard Proxy ( which belongs to standard contents).
    Option2 by Jai. Webservice changes : Webservice is not developed by me. I am consuming it. but I can ask this vendor who is WebService owner to change his webservice to suit my needs. But it wont solve the problem as I do not have Fault message at XI side.
    I can consider Option1 by Bhavesh, if the proxy problem is solved.
    Thanks,
    DK

  • How to disable the option of Resart for application error in SXMB_moni

    Hi Experts,
    I have a scenario of JDBC to 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 made coding for generating application error in inbound proxy code.Looking for a quick reply.
    Thanks
    Deepak

    Hi Mayank,
    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.
    Thanks
    Deepak
    Edited by: deepak jaiswal on Mar 2, 2010 5:19 PM

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

Maybe you are looking for

  • How do i remove the hard drive?,

    HI HOW DO I GET TO THE HARD DRIVE OF MACHINE? IT WONT START SINCE WE SPILT SOME WINE ON THE KEYBOARD. CAN YOU EMAIL ME at [email protected] as I can't get to my emails please. it is an HP PAVILION  NOTEBOOK PRODUCT NO. LE936EA#ABU WINDOWS 7 INSTALLED

  • Virtual infoobjects: technical name in source and target systems

    Hello Everybody, actually I got a problem: I´ve created a virtual characteristic which is working fine on development system. However after transporting to target system the BADI implementation containing the virtual infoobject dumps: assign componen

  • Can you max out a library?

    I want to know how many images you can successfully manage in Aperture before performance gets too slow to deal with. I'm at 55K+ in my library and I think I might be better off breaking it up into a couple of different libraries. Any advice or exper

  • Anyone else having trouble with shipping?

    My order was supposed to ship on the 24th. Every time i check its status online it says it is processing. Everytime i call no one gives me any help or will even tell me if it has shipped or if it is shipping to the correct address. Verizon wireless n

  • Track pad on macbook pro 2010 can click but no response

    Hi. I have a macbook pro late 2010 model. Suddenly the mouce tracp won't work. I does everything I ask it to and even click. But when I click nothing happens. Anyone know how to fix this? I have tried screw thing behind the battery trick but that onl