Call Inbound Proxy error

PI settings help
I am trying to transfer PR from ERP6.0 EHP4 to SRM7.0 using CPPR scenario.
I configured ERP/SRM and PI configuration in Integration directory.
But i get Reciever determination error in XML at ERP/SRM AND PI
RCVR_DETERMINATION">NO_RECEIVER_CASE_BE
Error Text: No receiver could be determined
In SRM, Inbound Message(reciever) is green but Call Inbound Proxy is giving below error.
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing! <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
I tested configuration in Integration directory.
Sender aggreeemnt is green
Reciever determination is red and giving below error.
Internal Error : You do not have sufficient authorization for this operation.
I have done below setting in Integration directory.
Business system setting.
1.Selected Business System BC_MM_MXX_594
2.Create communication channel(Gen_Rec_xi) as Receiver
  for above Business system BC_MM_MXX_594.
  -Use adapter type XI, http://sap.com/xi/XI/System SAP Basis7.xx and RFC MXX_Integration,
1.Selected Business System BC_SRM_SXX_300
2.Create communication channel(Gen_Rec_xi) as Receiver
  for above Business system BC_SRM_SXX_300.
  -Use adapter type XI, http://sap.com/xi/XI/System SAP Basis7.xx and RFC SXX_Integration.
-->>one doubt here? Should i have to create Comm channel for sender type also from ERP and SRM? pls confirm.
I created object in Integration directory as follows.
Create Object by selecting Business System BC_MM_MXX_594.
1)Selected Internal communication
2)Reciever Determination : BC_MM_MXX_594 PurchaseRequestERPSourcingRequest_Out
3)Specified Interface determination : BC_MM_MXX_594 PurchaseRequestERPSourcingRequest_Out BC_SRM_SXX_300.
4)Specified Reciever agreement BC_MM_MXX_594 BC_SRM_SXX_300 PurchaseRequestERPSourcingRequest_in(communication channel selected is Gen_Rec_xi)
5)Generated Objects and saved as CPPR_scenario.
6)Activated all objects created in CPPR_Scenario.
Pls suggest something wrong with Reciever determination?
How to find where the problem is located? at ERP or PI or SRM?.
Also onething i noted is Integrated configuration is empty in Integration directory.
Any configuration should be done for IOC.? pls confirm.
Regards
Chandra

Also i noticed below
In ERP xml ->Inbound message(SENDER).
Does this error indicate problem while sending from ERP to SRM or SRM to ERP.
because i can see sender service and interface is empty and SAP reciever is having ERP service.
however reciever does not fetched the corresponding(purchaseRequestxxxxxxx) interface names.
- <SAP:Sender>
  <SAP:Service />
  <SAP:Interface namespace="" />
  </SAP:Sender>
- <SAP:Receiver>
  <SAP:Party agency="" scheme="" />
  <SAP:Service>BC_MM_MXX_594</SAP:Service>
  <SAP:Interface namespace="http://sap.com/xi/APPL">QueryCodeList</SAP:Interface>
  </SAP:Receiver>
  <SAP:Interface namespace="http://sap.com/xi/APPL">QueryCodeList</SAP:Interface>
SOAP:mustUnderstand="1">
  <SAP:Category>XIServer</SAP:Category>
  <SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE</SAP:Code>
  <SAP:P1 />
  <SAP:P2 />
  <SAP:P3 />
  <SAP:P4 />
  <SAP:AdditionalText />
  <SAP:ApplicationFaultMessage namespace="" />
  <SAP:Stack>No receiver could be determined</SAP:Stack>
  <SAP:Retry>M</SAP:Retry>
Regards
Chandra

Similar Messages

  • ABAP Inbound Proxy Error !

    Hi ,
    I am forwarding Vendor Data from SRM EBP to SUS with the predifined proxies given by SAP, bu t i get below error when it reaches SUS System.Message processing both in SAP EBP and SAP XI is fine.
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Inbound Proxy
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIProxy</SAP:Category>
      <SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
      <SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>
      <SAP:P2>CL_BBPX_TRADING_PARTNER_IN</SAP:P2>
      <SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error during proxy processing An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause Application Error</SAP:Stack>   <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Error during proxy processing An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause Application

    Hi attached trace, kindly update wat could be the problem in case of EBP SUS Vendor replication
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Inbound Proxy
      -->
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <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=receiver</Trace>
      <Trace level="1" type="T">COMMIT is done by XMB !</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">XMB entry processing</Trace>
      <Trace level="1" type="T">system-ID = SSR</Trace>
      <Trace level="1" type="T">client = 100</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = WIP-SRINUS</Trace>
      <Trace level="1" type="Timestamp">2008-04-25T04:58:21Z CET</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = DD128437FD4A75F193690017A4F3435A</Trace>
      <Trace level="1" type="T">PLNAME = RECEIVER</Trace>
      <Trace level="1" type="T">QOS = EO</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
      <Trace level="1" type="T">Queue name : XBTR0001</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTR0001</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Going to persist message</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">--start sender interface action determination</Trace>
      <Trace level="1" type="T">select interface *</Trace>
      <Trace level="1" type="T">select interface namespace</Trace>
      <Trace level="1" type="T">no interface found</Trace>
      <Trace level="1" type="T">--start receiver interface action determination</Trace>
      <Trace level="1" type="T">Loop 0000000001</Trace>
      <Trace level="1" type="T">select interface SupplierPortalTradingPartner_CreateOrChange_In*</Trace>
      <Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/SupplierEnablement</Trace>
      <Trace level="1" type="T">no interface found</Trace>
      <Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
      <Trace level="1" type="T">Hence set action to DEL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
      <Trace level="1" type="T">system-ID = SSR</Trace>
      <Trace level="1" type="T">client = 100</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = WIP-SRINUS</Trace>
      <Trace level="1" type="Timestamp">2008-04-25T04:58:24Z CET</Trace>
      <Trace level="1" type="T">----
    </Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
      <Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="Inbound Framework" />
    - <!--  ************************************
      -->
    - <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
    - <asx:values>
      <CX_ERROR href="#o97" />
      </asx:values>
    - <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">
    - <cls:CX_SY_NO_HANDLER id="o97">
    - <CX_ROOT>
      <TEXTID>1F09B73915F6B645E10000000A11447B</TEXTID>
      <PREVIOUS href="#o96" />
      <KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID>
    - <INTERNAL_SOURCE_POS>
      <PROGID>297</PROGID>
      <CONTID>1564</CONTID>
      </INTERNAL_SOURCE_POS>
      </CX_ROOT>
      <CX_NO_CHECK />
    - <CX_SY_NO_HANDLER>
      <CLASSNAME>CX_BBPX1_STD_MESSAGE_FAULT</CLASSNAME>
      </CX_SY_NO_HANDLER>
      </cls:CX_SY_NO_HANDLER>
    - <cls:CX_BBPX1_STD_MESSAGE_FAULT id="o96">
    - <CX_ROOT>
      <TEXTID>65B8FEB5F43CC949B7CD662AB888ED34</TEXTID>
      <PREVIOUS />
      <KERNEL_ERRID />
    - <INTERNAL_SOURCE_POS>
      <PROGID>297</PROGID>
      <CONTID>1738</CONTID>
      </INTERNAL_SOURCE_POS>
      </CX_ROOT>
      <CX_DYNAMIC_CHECK />
      <CX_AI_APPLICATION_FAULT />
    - <CX_BBPX1_STD_MESSAGE_FAULT>
      <AUTOMATIC_RETRY />
      <CONTROLLER />
      <NO_RETRY />
    - <STANDARD>
      <CONTROLLER />
      *<FAULT_TEXT>An error occured within an XI interface: Exception occurredE:BBP_BUPA:034 -Organizational unit 00000008 does not exist; check entries Programm:* CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT>
      <FAULT_URL />
      <FAULT_DETAIL />
      </STANDARD>
      </CX_BBPX1_STD_MESSAGE_FAULT>
      </cls:CX_BBPX1_STD_MESSAGE_FAULT>
      </asx:heap>
      </asx:abap>
      </Trace>
      <Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      </SAP:Trace>

  • Inbound Proxy Error - JDBC to PROXY Scenario

    Hi experts,
    I am getting the following error while activating Inbound Proxy.
    Error when creating service node. [unknown]You are not authorized to use function Netzwerkadministration
    Exception of class CX_SRT_WSP_ICF
    Regards,
    Sudheer

    Hi Experts,
    Thank you for your replys.....Problem got solved......:)
    Some authorisation was missing...Now it was fine and I can activate Inbound proxy......:)
    Once again Thank you for your replys.....:)
    Regards,
    Sudheer

  • Inbound Proxy Error in Target System

    Hi
    My scenario ís MQ>XI>SAp R/3. I am successfully able to pick file from MQ and I see the success flag in SXMB_MONI(XI) and XI sends to SAP R/3 via Inbound proxy.
    But on recieving system (R/3) via proxy the data is not recieved correctly.
    I see Failure message with error in R/3 SXMB_MONI and the error is as follows.
    I guess my Mapping is correct as it passes trhough XI successfully. Is something wrong with the Inbound proxy?
    Kindly let me know your views on the same going through the error message I am unable to interpret anything. As the date format which I am recieving is correct.
    ++
    Best Regards
    Swetank

    Hi,
    When u define ur Data type (Messageinterface) dataelement as xsd:Date it is of the format CCYY-MM-DD. (ex 2003-12-31). So yyyyMMdd is not compatable with the ABAP data type that has been generated at the proxy end.
    Make sure dats-8 and xsd:Date use the same Date format.This might be the error that i can see.
    xsd:date format
    http://help.sap.com/saphelp_nw04/helpdata/en/fe/26da4105aa3f5de10000000a1550b0/content.htm
    Hope this helps
    Cheers,
    Siva Maranani.

  • SAP Inbound Proxy Error

    Hi Experts,
    I am facing an issue when executing inbound proxy message. After the message completed, the message status end up with Error. The error says below details.
    "Information about the method parameters is missing
    for the interface INTERFACE_NAME
    (ABAP interface, request message MT_Fault, request
    message namespace....)"
    I am also raising Fault messages from ABAP Proxy message programming. In SXMB_MONI while expanding all the messages I can able to see the application message but also i am seeing the above mention errors.
    Any Idea why this error appears?
    Thank you
    Magesh.

    Hi Diptendu - I don't think it's an issue with URL.
    Did  you register the service?
    http://<host>:<port>/ProxyServer/register?ns=http://sap.com/xi/XI/System&interface=ValueMappingReplicati
    onOutSynchronous&bean=localejbs/sap.com/com.sap.xi.services/ValueMappingApplicationSynchronous&m
    ethod=ValueMappingReplicationOutSynchronous
    Reference :
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e07dd2ae-f783-2c10-9aa6-ca69f67dd20f?QuickLink=index&…
    what is your receiver channel?

  • Error when calling inbound proxy

    Hi all,
    I´m facing the following problem in the R/3 monitoring:
    <SAP:Code p1="Request Message" p2="CX_XSLT_RUNTIME_ERROR" p3="/1SAI/XS00000000000000000035: 0000000000" p4="Error Text: No valid source context supplied Kernel ErrorId: CX_XSLT_RUNTIME_ERROR">APPLICATIONCALL.PARSE_APPLICATION_DATA</SAP:Code>
      <SAP:Text language="EN">Error when handling Request Message; XSLT error: CX_XSLT_RUNTIME_ERROR: XSLT program and source line: /1SAI/XS00000000000000000035: 0000000000; Error Text: No valid source context supplied Kernel ErrorId: CX_XSLT_RUNTIME_ERROR</SAP:Text>
      </SAP:ErrorHeader>
    I'm pulling a file from an external server and I pass the data to R/3 thru ABAP proxies. The point is that I am splitting the message in different parts, using the parameter Recordsets per Message, and mostly all of them are processed correctly, but in a few of them i´ve got that error. And if I process that parts of the file, that have caused the error, separately, they surprisingly work fine..
    I really do not know what happens and i really need help because I do not know what else to try or what could be the reason of this error.
    Thanks a lot!!

    the problem is INbound Message and the proxy genereted are not compatiable, can u check the field "S00000000000000000035: 0000000000;" whch field is atking this value from file, while passing to the R/3 check the lengths of this field....you will not c this error in MM, but you have to chcek the length of each field in proxy with data coming.......
    copy the payload from SXMB_MONI and directly try to send the data from SPROXY you will get the error detail....
    U can refer to the following thread where they has the same exception APPLICATIONCALL.PARSE_APPLICATION_DATA( b'cos of improper date formats...)So urs should also be a simlilar problem i guess..
    https://www.sdn.sap.com/sdn/collaboration.sdn?contenttype=url&content=https%3A//forums.sdn.sap.com/thread.jspa%3FforumID%3D44%26threadID%3D45455

  • Inbound proxy error

    Hi
    I tested with empty data, i.e no proxy data . It should actually through error, but it is going inside the else part.
    why it s happening like that.
    example :
    it_data = input-table-line.
    IF  it_data is empty.   
       display   Error.
    else.
        post the data from proxy to a table.
    end if.

    Hi,
    Controller is a generated add on mainmly used
    to influence the XML conversion and generation.
    It allows you to suppress generating XML for empty parts of the
    message. I am sorry i didnt find the links for the documentation.
    Anyway it is not easy to use it as the PI or other message broker
    as well as the bank end might refuse an xml you influenced using the controller
    e.g. because it does no longer match the public xsd´s.
    Regards,
    Marcel

  • Urgent: Error in Inbound Proxy in SCM system

    Hi All
    Please give your inputs to solve following problem I am facing. I am working on XI first time so please help me out to solve the following problem. Please let me know if you need any more info.
    Thanks a lot for your help guys.
    I am sending ORDERS.ORDER05 from R/3(ECC6.0) to SCM (5.0) through XI. I am using standard message interface ReplenishmentOrderNotification_In to send data to ICH configured on SAP SCM System.
    I am using XI adapter at receiver end. My message successfully going to SCM. SXMB_MONI, its giving error. After clicking on error flag it displays a table with 3 entries, please find them below.
    1. Start of inbound processing: ReplenishmentOrderNotification (ID 0000000000202027) 032(/SCMB/ORDER)
    2. TST 20080429202851 (type MessageCreationDateTime) was transferred as local time, interpretation as UTC 022(/SCMB/BIF_MI)
    3. Partner key(s) not found 042(/SCMB/MDL_BASIC)
    Please find the XML message from ERROR node from Inbound Proxy
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Inbound Proxy
      -->
    - <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="ABAP">APPLICATION_ERROR</SAP:Code>
      <SAP:P1 />
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="http://sap.com/xi/SCMBasis/Global">ReplenishmentOrderNotificationFault</SAP:ApplicationFaultMessage>
      <SAP:Stack>Application has thrown an exception</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Please find contents of Trace XML message from Inbound proxy
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Inbound Proxy
      -->
    - <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
      <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=receiver</Trace>
      <Trace level="1" type="T">COMMIT is done by XMB !</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
      <Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">XMB entry processing</Trace>
      <Trace level="1" type="T">system-ID = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = AMOL</Trace>
      <Trace level="1" type="Timestamp">2008-04-30T01:31:18Z CET</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">* *</Trace>
      <Trace level="1" type="T">****************************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Message-GUID = 48165647672B03B5E10080000A0C640C</Trace>
      <Trace level="1" type="T">PLNAME = RECEIVER</Trace>
      <Trace level="1" type="T">QOS = EO</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
      <Trace level="1" type="T">Queue name : XBTR0003</Trace>
      <Trace level="1" type="T">Generated prefixed queue name = XBTR0003</Trace>
      <Trace level="1" type="T">Schedule message in qRFC environment</Trace>
      <Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
      <Trace level="1" type="T">-----------------------------------------------------</Trace>
      <Trace level="1" type="T">Going to persist message</Trace>
      <Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
      <Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
      <Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
      <Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
      <Trace level="1" type="T">-----------------------------------------------------</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">--start sender interface action determination</Trace>
      <Trace level="1" type="T">select interface *</Trace>
      <Trace level="1" type="T">select interface namespace</Trace>
      <Trace level="1" type="T">no interface found</Trace>
      <Trace level="1" type="T">--start receiver interface action determination</Trace>
      <Trace level="1" type="T">Loop 0000000001</Trace>
      <Trace level="1" type="T">select interface ReplenishmentOrderNotification_In*</Trace>
      <Trace level="1" type="T">select interface namespace http://sap.com/xi/SCMBasis/Global</Trace>
      <Trace level="1" type="T">no interface found</Trace>
      <Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
      <Trace level="1" type="T">Hence set action to DEL</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">-----------------------------------------------------</Trace>
      <Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
      <Trace level="1" type="T">system-ID = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = AMOL</Trace>
      <Trace level="1" type="Timestamp">2008-04-30T16:19:34Z CET</Trace>
      <Trace level="1" type="T">-----------------------------------------------------</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
      <Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="Inbound Framework" />
      </Trace>
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Persisting message with status ManualRestart, version: 000</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">-----------------------------------------------------</Trace>
      <Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
      <Trace level="1" type="T">system-ID = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = AMOL</Trace>
      <Trace level="1" type="Timestamp">2008-04-30T20:52:28Z CET</Trace>
      <Trace level="1" type="T">-----------------------------------------------------</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
      <Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="Inbound Framework" />
      </Trace>
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Persisting message with status ManualRestart, version: 002</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">-----------------------------------------------------</Trace>
      <Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
      <Trace level="1" type="T">system-ID = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = RAJARANGA</Trace>
      <Trace level="1" type="Timestamp">2008-04-30T22:34:19Z CET</Trace>
      <Trace level="1" type="T">-----------------------------------------------------</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
      <Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="Inbound Framework" />
      </Trace>
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Persisting message with status ManualRestart, version: 004</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">-----------------------------------------------------</Trace>
      <Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
      <Trace level="1" type="T">system-ID = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = RAJARANGA</Trace>
      <Trace level="1" type="Timestamp">2008-04-30T22:35:19Z CET</Trace>
      <Trace level="1" type="T">-----------------------------------------------------</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
      <Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="Inbound Framework" />
      </Trace>
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Persisting message with status ManualRestart, version: 006</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">-----------------------------------------------------</Trace>
      <Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
      <Trace level="1" type="T">system-ID = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = RAJARANGA</Trace>
      <Trace level="1" type="Timestamp">2008-04-30T22:41:24Z CET</Trace>
      <Trace level="1" type="T">-----------------------------------------------------</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
      <Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="Inbound Framework" />
      </Trace>
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Persisting message with status ManualRestart, version: 008</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">-----------------------------------------------------</Trace>
      <Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
      <Trace level="1" type="T">system-ID = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = AMOL</Trace>
      <Trace level="1" type="Timestamp">2008-05-01T00:07:18Z CET</Trace>
      <Trace level="1" type="T">-----------------------------------------------------</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
      <Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="Inbound Framework" />
      </Trace>
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Persisting message with status ManualRestart, version: 010</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">-----------------------------------------------------</Trace>
      <Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
      <Trace level="1" type="T">system-ID = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = AMOL</Trace>
      <Trace level="1" type="Timestamp">2008-05-01T00:30:07Z CET</Trace>
      <Trace level="1" type="T">-----------------------------------------------------</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
      <Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Persisting message with status ManualRestart, version: 012</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">-----------------------------------------------------</Trace>
      <Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
      <Trace level="1" type="T">system-ID = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = AMOL</Trace>
      <Trace level="1" type="Timestamp">2008-05-01T00:53:39Z CET</Trace>
      <Trace level="1" type="T">-----------------------------------------------------</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
      <Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="Inbound Framework" />
      </Trace>
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Persisting message with status ManualRestart, version: 014</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
      <Trace level="1" type="T">***************************************</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
      <Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
      <Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">-----------------------------------------------------</Trace>
      <Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
      <Trace level="1" type="T">system-ID = SCS</Trace>
      <Trace level="1" type="T">client = 001</Trace>
      <Trace level="1" type="T">language = E</Trace>
      <Trace level="1" type="T">user = AMOL</Trace>
      <Trace level="1" type="Timestamp">2008-05-01T01:04:22Z CET</Trace>
      <Trace level="1" type="T">-----------------------------------------------------</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
    - <!--  ************************************
      -->
      <Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
      <Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
      <Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
    - <!--  ************************************
      -->
    - <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
      <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
    - <!--  ************************************
      -->
      <Trace level="1" type="B" name="Inbound Framework" />
      </Trace>
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
      <Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
      <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
    - <!--  ************************************
      -->
      </SAP:Trace>
    Regards
    Amol

    Hi All
    Thanks for your inputs, we are a step ahead now. We applied few notes I will be posting details soon. At the moment we stuck at one poin, its giving a configuration related error.  Please find the process log from SXMB_MONI from SCM system. It is saying Buyer missing in fact we have configured BP01 in SCM system and same we are getting from ECC system.
    Hope to hear from you soon. Thanks a lot for your inputs.
    ReplenishmentOrderNotificationFault
    Proxy Class (Generated)
    Detailed Information
    Start of inbound processing: ReplenishmentOrderNotification (ID 0000000000202043) 032(/SCMB/ORDER)
    The active implementation of BAdI '/SCMB/BIF_I_REPLORD' 'BEFORE_CONVERSION' has been run  080(/SCMB/BIF_COMMON)
    TST 20080508141414 (type MessageCreationDateTime) was transferred as local time, interpretation as UTC 022(/SCMB/BIF_MI)
    The active implementation of BAdI '/SCMB/BIF_MI_PARTYID' 'BEFORE_MASTER_DATA_ACCESS' has been run  080(/SCMB/BIF_COMMON)
    Start generic process type determination 000(/SCMB/BIF_CU)
    Process type could not be determined - search for standard process type 002(/SCMB/BIF_CU)
    Standard process type (ICH) determined successfully 013(/SCMB/BIF_CU)
    Start action determination for addresses 070(/SCMB/BIF_CU)
    No Customizing found; standard action is 'map all addresses' 072(/SCMB/BIF_CU)
    End of action determination for addresses 071(/SCMB/BIF_CU)
    Start partner role determination 060(/SCMB/BIF_CU)
    Partner role is 'buyer (sold-to party)' 063(/SCMB/BIF_CU)
    Partner role determination completed successfully 061(/SCMB/BIF_CU)
    TST 20080508000000 (type CreationDateTime) was transferred as local time, interpretation as UTC 022(/SCMB/BIF_MI)
    The active implementation of BAdI '/SCMB/BIF_MI_ITMBPRT' 'BEFORE_MASTER_DATA_ACCESS' has been run  080(/SCMB/BIF_COMMON)
    The active implementation of BAdI '/SCMB/BIF_MI_PRODID' 'BEFORE_MASTER_DATA_ACCESS' has been run  080(/SCMB/BIF_COMMON)
    TST 20081027000000 (type DeliveryPeriodStartDateTime, item 00010, sched. line 1) is local, interpret. as UTC 024(/SCMB/BIF_MI)
    Order 4500000105 item 00010: 'DeliveryPeriodEndDateTime' missing in schedule line 1 090(/SCMB/ORDER)
    The active implementation of BAdI '/SCMB/BIF_I_REPLORD' 'AFTER_CONVERSION' has been run  080(/SCMB/BIF_COMMON)
    BOL processing started for object /SCA/CL_SVORDER process name REPLORDER 006(/SCMB/DM_BOL)
    Start: read ODM order 250(/SCMB/ORDER)
    End: read ODM order 251(/SCMB/ORDER)
    Start: validation framework 254(/SCMB/ORDER)
    Validation started for validation profile POC1 (ICH - REPLORDER - HEADER) 606(/SCMB/DM_BOL)
    Business partner 'buyer' is missing in order 4500000105 021(/SCMB/ORDER)
    Validation for val. prof. POC1 (ICH, REPLORDER, HEADER) ended with errors and warnings 608(/SCMB/DM_BOL)
    End: validation framework 255(/SCMB/ORDER)
    Start alert notification for application ALEN - time 08.05.2008 19:15:18 - process mode F 504(/SCMB/ANOT)
    End of alert notification for application ALEN - time 08.05.2008 19:15:18 - process mode F 525(/SCMB/ANOT)
    Start: write ODM order 252(/SCMB/ORDER)
    End: write ODM order 253(/SCMB/ORDER)
    BOL processing ended for object /SCA/CL_SVORDER process name REPLORDER 007(/SCMB/DM_BOL)
    End inb. proc.: ReplenishmentOrderNotification (ReplenishmentOrder ID ) 033(/SCMB/ORDER)

  • Abap Proxy Errors

    Hi Experts,
    My scenario R/3->XI(ABAP Proxy)--->SUS Systems
    Getting the following error in SUS system.XI system it doesn't throw any error in moni.
    I am new to proxy concepts.Also please let me know any related blogs or suggestions in this regards.
    <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    <!--  Call Inbound Proxy
      -->
      <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIProxy</SAP:Category>
      <SAP:Code area="ABAP">DYNAMIC_CALL_FAILURE</SAP:Code>
      <SAP:P1>UNCAUGHT_EXCEPTION</SAP:P1>
      <SAP:P2>CL_BBPX1_SUSIV_IN</SAP:P2>
      <SAP:P3>EXECUTE_ASYNCHRONOUS</SAP:P3>
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error during proxy processing An exception with the type CX_BBPX1_STD_MESSAGE_FAULT occurred, but was neither handled locally, nor declared in a RAISING clause Application Error</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    Thanks,
    Sudhansu

    Hi Behera,
    Can you debug your proxy using this blog:
    /people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation
    https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/502a7f0e-e5d9-2910-5aa2-976a8ed8384f&overridelayout=true
    Also please check few solutions given in this threads for the same issue:
    Re: Messages waiting in SUS Moni
    Re: ABAP Inbound Proxy Error !
    Regards,
    ---Satish

  • ABAP provider proxy error using Fault Message Type

    Hello experts,
    I'm using a provider ABAP proxy with a fault message type in the inbound service interface.
    In the ABAP code on the backend system, I need to fill a database table.
    in case the record exist --> fault + message back to SAP PI to be alerted.
    I do this with a RAISE EXCEPTION TYPE.
    I generated all necessary proxies.
    The error I got on the backend system (SXMB_MONI) is this:
    Application Error - Call Inbound Proxy
    SAP:Category>Application</SAP:Category>
      <SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="xxxxx">FMT_xxxxxx</SAP:ApplicationFaultMessage>
      <SAP:Stack>The application triggered an exception</SAP:Stack>
      <SAP:Retry>N</SAP:Retry>
    Can it be that I need to use something else instead of the RAISE EXCEPTION TYPE. to get something back to SAP PI?
    Now the error is logged in SXMB_MONI on the backend system.
    Please advice.
    Thanks a lot
    Dimitri

    Hi Dimitri,
    Check out these links -
    1. /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
    2. http://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/frameset.htm
    Regards,
    Sunil Chandra

  • Upload data from abap program to abap inbound proxy

    Hi,
    I have requirement to upload flat file data to an internal table and call Inbound proxy abap class and pass all the internal table data to tha proxy clas method structure.
    So could any one help me how to send/pass data to class, Please give some e.g.
    thanks
    bobby
    Edited by: Bobby G on Nov 18, 2009 4:35 AM

    hi;
    you may follow the following ways
    1. create a report and by using GUI_upload, give the path as default , you can convert the flat file's data into internal table.
    2. call that report in proxy method by returning parameter as a table, this table can use further in the proxy.
    Another way, you have
    1.  Create a transparent table and by using the GUI_Upload in report,  you may  store the data.
    2.  from step 1, you may use data in the proxy.
    Regards
    Shashi

  • Calling error/application logs in CRM inbound proxy

    Hi All,
    In inbound proxy of CRM, I have to call Error/Application logs (for eg:SLG1) whenever an integration process throws some error. Has anyone worked on this kind of scenario to call different application logs in CRM or R3 side inbound proxy.
    If so, please give some ideas on this.
    Thanks
    Deno

    Hi Deno,
    did you have a look at my blog in which I describe it ?
    /people/michal.krawczyk2/blog/2006/09/20/xi-abap-mapping-logs--more-standard-better-visibility
    Regards,
    michal

  • Call transaction in ABAP Inbound proxy

    Hi All,
    I am processing transaction KKPAN in inbound proxy. As per my knowledge, there is no BAPI or other way of processing this transaction. I have recorded a BDC, and I am calling this BDC using Call Transaction in my Inbound proxy.
    The problem is, control never returns back to the proxy after I call this BDC using Call Transaction.  However, interestingly, If there is an error in BDC, the control comes back to the proxy. Any ideas, why it does not successfully update data using BDC in inbound proxy?
    Your inputs are appreciated.
    Thanks,
    Navdeep

    Thanks for you response Akshay !
    However, It didn't solve my problem. In my case, the inbound proxy class is being called successfully. The problem comes, when I use Call Transaction in the class. The call transaction works and returns error message, if there is some error in the processing; however, for when there is no error in the BDC data, the control never comes back after call transaction.
    However, if I use SPROXY to test this interface, by copying the payload of the message and using the same user (As in Comm Channel), I am able to call Call Transaction without any problem. The data gets created successfully.
    Now this is getting really tricky.
    Still looking for ideas
    Regards,
    Navdeep
    Message was edited by:
            Navdeep Singla

  • Sync Async using proxies ( Calling Outbound proxy from Inbound proxy )

    I'm trying to generate Asynchronous Outbound message from the Synchronous Inbound message message  due to a requirement. My question is : is it really possible to develop such a scenario?. I'm getting weird error such as Kernal exception etc. Please let me know if you have developed such scenario and what should we do dfifferently in such scenarios?. Thank you for any suggestions.

    Hi,
    This error has has nothing to do with Calling Outbound Proxy from from Inbound Proxy. The scenario which you are telling is very much possible.
    It looks like there is some problem in your proxy code while calling RFC from within there or something like that. Try catching the exception and see what is the exact error or put in debug mode and see the step where exactly your code is failing.
    Use the following links for Catching Exception in Proxy
    Inbound ABAP Proxy Trace and error handling
    Handling Exceptions
    ABAP Server Proxies - Fault Handling
    Exception handling in integration processes
    ABAP Proxy and fault messages
    /people/bhanu.thirumala/blog/2006/02/07/abap-proxy--xml-to-abap-transformation
    Thanks
    Amit
    Reward point if answer is helpful

  • Error In Inbound Proxy

    Hi
    I have SRM Scenario were I am sending a Z_CREAMAS_SUSMM  IDOC from ECC 6.0 to SRM 5.5 SUS via PI 7.0 . There are no errors on the XI side and the sxmb_moni of the SRM side .The message shows a successful flag on the XI as well as the SRM side . But however the functionality of the idoc does not work ie the vendor is not created in SRM SUS.
    When we try to test the inbound proxy from sproxy by copying the payload from sxmb_moni of SRM and then testing it we get a short dump with the following contents .
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
         caught in
        procedure "SET_METHOD" "(METHOD)", nor was it propagated by a RAISING clause.
        Since the caller of the procedure could not have anticipated that the
        exception would occur, the current program is terminated.
        The reason for the exception is:
        You attempted to use a 'NULL' object reference (points to 'nothing')
        access a component.
        An object reference must point to an object (an instance of a class)
        before it can be used to access components.
        Either the reference was never set or it was set to 'NULL' using the
        CLEAR statement.
    How to correct the error
        Probably the only way to eliminate the error is to correct the program.
        If the error occures in a non-modified SAP program, you may be able to
        find an interim solution in an SAP Note.
        If you have access to SAP Notes, carry out a search with the following
        keywords:
        "OBJECTS_OBJREF_NOT_ASSIGNED_NO" "CX_SY_REF_IS_INITIAL"
        "CL_PROXY_INBOUND_ADAPTER======CP" or "CL_PROXY_INBOUND_ADAPTER======CM00I"
        "SET_METHOD"
    Can any one please tell me what the error could be .
    regards
    Nilesh Taunk

    Hi,
      You program raise an exception as''CX_SY_REF_IS_INITIAL'.
      this is due to null value passing to the object.
      i hope, u r using intialization event in the custom ABAP code.
    please try to change it.
    warm regards
    mahesh.

Maybe you are looking for