Skip to Content
0
Former Member
May 28, 2011 at 05:53 AM

Idoc to Proxy Scenario

176 Views

Hi,

I am working on a Idoc (ECC) to proxy (SRM) scenario , I am triggering the Idoc message from RWB, when I am trying so, message is getting pushed and it shows a success message in PI Moni. But it failes in the SRM system and the error message is as follows, Please provide me with some inputs. Also the Idoc message is not directly getting posted from ECC system.

Note: Logical system already exists in PI, ECC and also in SRM systems, Let me know should I check anything else.

Error Message:

==================

http://sap.com/xi/XI/Message/30" xmlns:SOAP=" http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand=""> XIProxy DYNAMIC_CALL_FAILURE UNCAUGHT_EXCEPTION CL_BBPX_TRADING_PARTNER_SUS_IN EXECUTE_ASYNCHRONOUS 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>

Trace message is:

============================

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?><!-- Call Inbound Proxy > http://sap.com/xi/XI/Message/30"> level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST"> ************************************ -->

<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>

<Trace level="1" type="T">Work Process ID: 782464</Trace>

<Trace level="1" type="T">COMMIT is done by XMB ! </Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS"></Trace><!-- ************************************ -->

<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE"></Trace><!-- ************************************ -->

<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE">

</Trace>

<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV">

</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="1" type="T">system-ID = SND</Trace>

<Trace level="1" type="T">client = 200</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = PISUPER</Trace>

<Trace level="1" type="Timestamp">2011-05-28T04:49:46Z 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><!-- ************************************ -->

<Trace level="1" type="T">Message-GUID = F506D1E488E811E0AF6B0000089A81FE</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><!-- ************************************ -->

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

<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><!-- ************************************ -->

<Trace level="1" type="T">--start determination of sender interface action </Trace>

<Trace level="1" type="T">select interface </Trace>

<Trace level="1" type="T">select interface namespace </Trace>

<Trace level="1" type="T">--start determination of receiver interface action </Trace>

<Trace level="1" type="T">Loop 0000000001 </Trace>

<Trace level="1" type="T">select interface SupplierPortalTradingPartner_CreateOrChange_In </Trace>

select interface namespace http://sap.com/xi/SRM/SupplierEnablement

<Trace level="1" type="T">--no interface action for sender or receiver 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>

<Trace level="1" type="T">Work Process ID: 786562</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><!-- ************************************ -->

<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 = SND</Trace>

<Trace level="1" type="T">client = 200</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = PISUPER</Trace>

<Trace level="1" type="Timestamp">2011-05-28T04:55:09Z CET </Trace>

<Trace level="1" type="T">----


</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC"></Trace><!-- ************************************ -->

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

<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>

<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY"></Trace><!-- ************************************ -->

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace><!-- ************************************ -->

<Trace level="1" type="B" name="Inbound Framework"></Trace><!-- ************************************ -->

<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0"><asx:values><CX_ERROR href="#o93"/></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="o93"><CX_ROOT><TEXTID>1F09B73915F6B645E10000000A11447B</TEXTID><PREVIOUS href="#o92"/><KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID><INTERNAL_SOURCE_POS><PROGID>339</PROGID><CONTID>1580</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="o92"><CX_ROOT><TEXTID>65B8FEB5F43CC949B7CD662AB888ED34</TEXTID><PREVIOUS/><KERNEL_ERRID/><INTERNAL_SOURCE_POS><PROGID>339</PROGID><CONTID>1754</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>Error in an XI interface:

Exception occurredE:BBP_BUPA_SUPPLIER:089 -Unable to determine logical system of sender; check your data

Program: 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... =&gt; ROLLBACK WORK</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">

</Trace>

<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><!-- ************************************ -->

</SAP:Trace>

Regards,

Nithiyanandam

Edited by: Nithiyanandam A.U. on May 28, 2011 8:08 AM