- SAP Community
- Products and Technology
- Spend Management
- Spend Management Q&A
- PO R3-SUS send error XI
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
PO R3-SUS send error XI
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 04-09-2008 11:31 PM
Hello
We have SRM 5.0 extended scenario with ECC 6.0.
When I create a PO in SRM and it send to SUS, the PO are Ok.
The problem I have it in the PO of R3 to SUS. Idoc is sent correctly, but SUS it receives it with error in XI.
An error occured within an XI interface: Exception occurredE:BBP_PD:147 -Enter a country for partner 0000000126 with type 'Sold-to Party' E:BBP_PD:147 -Enter a country for partner 0001000022 with type 'Vendor' E:BS:002 -"Create" is not allowed (SUS Purchase Order 3300000096 ) Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57
I have read some threads that handle some solutions like updating via trx BBP_SUS_BP_ADM the partners.
However the partners were updated of SRM to HIS by transactions BBP_SP_SUPP_INI and BBP_SP_COMP_INI for vendors and companies and are complete in their data.
I need the advice of you.
- SAP Managed Tags:
- SAP Supplier Relationship Management
Accepted Solutions (1)
Accepted Solutions (1)
masa_139
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
Please check the note 702787 Message "Enter a country".
[https://service.sap.com/sap/support/notes/702787|https://service.sap.com/sap/support/notes/702787]
Regards,
Masa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Answers (5)
Answers (5)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
We are facing th below issue in srm while transferring the invoices from mm to sus
<?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>
Trace:
<?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 = SRM</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = SC2354</Trace>
<Trace level="1" type="Timestamp">2008-08-25T07:26:51Z INDIA</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 = 48B266CC39E920E8E10000000AC83195</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 InvoiceRequest_In*</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/SRM/SupplierEnablement/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 = SRM</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = SC2354</Trace>
<Trace level="1" type="Timestamp">2008-08-25T07:26:52Z INDIA</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="#o188" />
</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="o188">
- <CX_ROOT>
<TEXTID>1F09B73915F6B645E10000000A11447B</TEXTID>
<PREVIOUS href="#o187" />
<KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID>
- <INTERNAL_SOURCE_POS>
<PROGID>325</PROGID>
<CONTID>3133</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="o187">
- <CX_ROOT>
<TEXTID>65B8FEB5F43CC949B7CD662AB888ED34</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>325</PROGID>
<CONTID>3369</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_PD:147 -Enter a country for partner with type 'Sold-to Party' E:BBP_PD:428 -Enter exactly one partner of type Sold-to Party I:R5:553 -'Different country' field contents deleted because identical to 'Country' E:BS:013 -System status INCM is active (SUS Invoice 5000000731) 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" />
- <!--
-->
<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 = SRM</Trace>
<Trace level="1" type="T">client = 100</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = DEV04</Trace>
<Trace level="1" type="Timestamp">2008-08-25T08:23:20Z INDIA</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="#o191" />
</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="o191">
- <CX_ROOT>
<TEXTID>1F09B73915F6B645E10000000A11447B</TEXTID>
<PREVIOUS href="#o190" />
<KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID>
- <INTERNAL_SOURCE_POS>
<PROGID>320</PROGID>
<CONTID>3133</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="o190">
- <CX_ROOT>
<TEXTID>65B8FEB5F43CC949B7CD662AB888ED34</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>320</PROGID>
<CONTID>3369</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_PD:147 -Enter a country for partner with type 'Sold-to Party' E:BBP_PD:428 -Enter exactly one partner of type Sold-to Party I:R5:553 -'Different country' field contents deleted because identical to 'Country' E:BS:013 -System status INCM is active (SUS Invoice 5000000732) 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" />
- <!--
-->
<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="3" type="T">Manual Restart: increase Tracelevel to 3</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!--
-->
<Trace level="3" type="T">Persisting message Status = 016</Trace>
<Trace level="3" type="T">Message version 004</Trace>
<Trace level="3" type="T">Pipeline RECEIVER</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="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">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="3" type="T">system-ID = SRM</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = DEV04</Trace>
<Trace level="1" type="Timestamp">2008-08-25T08:23:31Z INDIA</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="3" type="T">External PLID = RECEIVER</Trace>
<Trace level="3" type="T">Internal PLID = SAP_RECEIVER</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_RECEIVER</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">PLSRVID = PLSRV_CALL_INBOUND_PROXY</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2008-08-25T08:23:31Z INDIA Begin of pipeline processing PLSRVID = RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- <!--
-->
<Trace level="1" type="Timestamp">2008-08-25T08:23:31Z INDIA Start of pipeline service processing PLSRVID= PLSRV_CALL_INBOUND_PROXY</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_INBOUND_PROXY</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_INBOUND_PROXY</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_PROXY_FRAMEWORK</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="Inbound Framework" />
- <!--
-->
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
- <asx:values>
<CX_ERROR href="#o191" />
</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="o191">
- <CX_ROOT>
<TEXTID>1F09B73915F6B645E10000000A11447B</TEXTID>
<PREVIOUS href="#o190" />
<KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID>
- <INTERNAL_SOURCE_POS>
<PROGID>320</PROGID>
<CONTID>3133</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="o190">
- <CX_ROOT>
<TEXTID>65B8FEB5F43CC949B7CD662AB888ED34</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>320</PROGID>
<CONTID>3369</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_PD:147 -Enter a country for partner with type 'Sold-to Party' E:BBP_PD:428 -Enter exactly one partner of type Sold-to Party I:R5:553 -'Different country' field contents deleted because identical to 'Country' E:BS:013 -System status INCM is active (SUS Invoice 5000000733) 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="3" type="T">No persisting of message after plsrv call, because of config</Trace>
</Trace>
<Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!--
-->
<Trace level="3" type="T">Persisting message Status = 014</Trace>
<Trace level="3" type="T">Message version 005</Trace>
<Trace level="3" type="T">Pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- <!--
-->
<Trace level="3" type="T">Trace object available again now. OK.</Trace>
<Trace level="3" type="T">manual Restart Flag X</Trace>
<Trace level="3" type="T">Message Guid 48B266CC39E920E8E10000000AC83195</Trace>
<Trace level="3" type="T">Version 000</Trace>
<Trace level="3" type="T">Pipeline ID RECEIVER</Trace>
<Trace level="3" type="T">EOIO Force I</Trace>
<Trace level="3" type="T">Restart Trace X</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="T">Error of the prevous version:</Trace>
<Trace level="3" type="T">Area ABAP</Trace>
<Trace level="3" type="T">Error ID DYNAMIC_CALL_FAILURE</Trace>
<Trace level="3" type="T">Restart of Queue?</Trace>
<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="3" type="T">Call qRFC .... MsgGuid = 48B266CC39E920E8E10000000AC83195</Trace>
<Trace level="3" type="T">Call qRFC .... Pipeline = RECEIVER</Trace>
<Trace level="3" type="T">OK.</Trace>
<Trace level="3" type="T">Manual Restart: increase Tracelevel to 3</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!--
-->
<Trace level="3" type="T">Persisting message Status = 016</Trace>
<Trace level="3" type="T">Message version 006</Trace>
<Trace level="3" type="T">Pipeline RECEIVER</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="3" type="T">message version successfully read from persist version= 006</Trace>
<Trace level="2" type="T">Increment log sequence to 007</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- <!--
-->
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="3" type="T">system-ID = SRM</Trace>
<Trace level="3" type="T">client = 100</Trace>
<Trace level="3" type="T">language = E</Trace>
<Trace level="3" type="T">user = DEV04</Trace>
<Trace level="1" type="Timestamp">2008-08-25T08:27:55Z INDIA</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="3" type="T">External PLID = RECEIVER</Trace>
<Trace level="3" type="T">Internal PLID = SAP_RECEIVER</Trace>
</Trace>
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="3" type="T" />
<Trace level="3" type="T">Pipeline attributes</Trace>
<Trace level="3" type="T">PID = SAP_RECEIVER</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">PLSRVID = PLSRV_CALL_INBOUND_PROXY</Trace>
<Trace level="3" type="T" />
<Trace level="1" type="Timestamp">2008-08-25T08:27:55Z INDIA Begin of pipeline processing PLSRVID = RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- <!--
-->
<Trace level="1" type="Timestamp">2008-08-25T08:27:55Z INDIA Start of pipeline service processing PLSRVID= PLSRV_CALL_INBOUND_PROXY</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_CALL_INBOUND_PROXY</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_INBOUND_PROXY</Trace>
<Trace level="3" type="T">PLSRVTYPE =</Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_PROXY_FRAMEWORK</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="Inbound Framework" />
- <!--
-->
- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
- <asx:values>
<CX_ERROR href="#o191" />
</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="o191">
- <CX_ROOT>
<TEXTID>1F09B73915F6B645E10000000A11447B</TEXTID>
<PREVIOUS href="#o190" />
<KERNEL_ERRID>UNCAUGHT_EXCEPTION</KERNEL_ERRID>
- <INTERNAL_SOURCE_POS>
<PROGID>320</PROGID>
<CONTID>3133</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="o190">
- <CX_ROOT>
<TEXTID>65B8FEB5F43CC949B7CD662AB888ED34</TEXTID>
<PREVIOUS />
<KERNEL_ERRID />
- <INTERNAL_SOURCE_POS>
<PROGID>320</PROGID>
<CONTID>3369</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_PD:147 -Enter a country for partner with type 'Sold-to Party' E:BBP_PD:428 -Enter exactly one partner of type Sold-to Party I:R5:553 -'Different country' field contents deleted because identical to 'Country' E:BS:013 -System status INCM is active (SUS Invoice 5000000734) 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="3" type="T">No persisting of message after plsrv call, because of config</Trace>
</Trace>
<Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!--
-->
<Trace level="3" type="T">Persisting message Status = 014</Trace>
<Trace level="3" type="T">Message version 007</Trace>
<Trace level="3" type="T">Pipeline RECEIVER</Trace>
</SAP:Trace>
Any idea as to waht can be done to redolve the same.
Thanks and Regards,
Manu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Yes, the problem was solved.
Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
any idea?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Raul,
We implemented the notes you listed but didn't solve the issue.
Then we configured the points Khan's listed and it solved our issue ( Issue was exact same as yours)
Assign Role: SAP_EC_SUS_ADMIN_PURCHASER then run the transaction BBP_SUS_BP_ADM.
Verify the Business Partner creation using BP transaction.
Thanks for all the inputs,
mathew
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Masa/Khan, thanks for its answers.
I applied notes 987569, 940490 and 705541, but the problem persists.
Another suggestion?.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
please go through the following help file -->
http://help.sap.com/saphelp_srm50/helpdata/en/18/76591cd00f4a5a91807a4d13e53f86/frameset.htm
on the left hand side --> click on the link
Business Partner Maintenance in SAP Supplier Self-Services
On the right hand side --> details are shown > here you need to follow the section->
-
>
Creation of business partners in the Plan-Driven Procurement with Supplier Integration business scenario
-
>
below Transactions are for the ---> SUS-EBP scenario
BBP_SP_SUPP_INI.
BBP_SP_COMP_INI.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- SAP Ariba 2405 Release Key Innovations Preview in Spend Management Blogs by SAP
- SAP Ariba Source to Contract 2405 Release Key Innovations in Spend Management Blogs by SAP
- Workflow Email notification in CP in Spend Management Q&A
- Regarding Bills of Material MM Module in Spend Management Q&A
- Error in a service of application MMPUR Function not possible for a contract in Spend Management Q&A
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.