Exception occurredE:BBP_PD:058 -Enter a currency E:BS:002
Hi All,
We are using MM-SUS scenario with SRM 5.0 and ECC 6.0 as the backend.
We have an issue while sending the purchase order from the MM to the SUS system.
The PO reaches the SUS system and our SXMB_MONI shows the following error message :
An error occured within an XI interface: Exception occurredE:BBP_PD:058 -Enter a currency E:BS:002 -"Create" is not allowed (SUS Confirmation XXXXXXX ) Programm:
This is happening for some POs and DS's(SA), the reason for which we are not able to find.
There is a OSS note Note 817380 - You cannot create a scheduling agreement release in SUS, with the same error text but these corrections already exist in our system.
Can anyone faced the same issue?
Can anyone give any links/suggestions/OSS for this particular issue?
Best regards,
Sridhar
Hi,
Please look at the below link. Shd solve your problem.
Error in SUS PO creation
Rgds,
RRK
Do reward points
Similar Messages
-
An error occured within an XI interface: Exception occurredS:BBP_CF:037
Hi
I am getting an error as described below in XI . The error is while calling inbound proxy . This is a PurchaseOrderConfirmation in SRM system. has any one faced a similar exception ....how to debug this ...is it an error in abap code
An error occured within an XI interface: Exception occurredS:BBP_CF:037 -No confirmations could be entered for purchase order 4100007164 Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line:
<?xml version="1.0" encoding="utf-8" ?>
- <nr1:StandardMessageFault xmlns:nr1="http://sap.com/xi/SRM/Basis/Global">
- <standard>
<faultText>An error occured within an XI interface: Exception occurredS:BBP_CF:037 -No confirmations could be entered for purchase order 4100007164 Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</faultText>
</standard>
</nr1:StandardMessageFault>
<?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/SRM/Basis/Global">StandardMessageFault</SAP:ApplicationFaultMessage>
<SAP:Stack>The application triggered an exception</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
thanks
PrashanthHi Prashanth,
Check these..
R/3(MM) -XI- SUS Scenario Error
PurchaseOrderConfirmation in SRM 4.0
cheers,
Prashanth
P.S Please mark helpful answers -
Error Code :-5002 Error Message :Enter valid currency , '51100000-01-001-0
Hi all,
I have found a error "Error Code :-5002 Error Message :Enter valid currency , '51100000-01-001-01'" while adding the DELIVERY document.
I have made a customer and assign then "EURO" currency and add delivery document then it prompts error.
Could anyone solve this problem. is there any setting which i am missing..??
Regards
SandeshHI Sandesh,
Check Sap note :1252328
and also check below thread of similar issue:
Re: 'Invalid Currency' error when attempting to deliver order
Hope this will solve your issue.
Thanks,
Neetu -
Error message: "Enter valid currency [Message 173-57]" during Deposit transaction
Hi All,
Is there a specific reason why can't I deposit from a "Multi-currency" cash account to a "specific (i.e., USD)" cash account using the Banking> Deposits> Deposit module.
I have already read below threads related to this issue.
Error message "Enter valid currency [Message 173-57]" during cash deposit
Can't Create Cash Deposit of Journal Entry due to "Invalid Currency" Error
Transfer Between bank accounts in different currencies
GL Postings between different currency accounts
foreign currency transactions
SAP Business One Note: 1260658 - Transfer monies between different monocurrency accounts
I have posted successfully e cash transfer from multicurrency to monocurrency cash account thru Journal Entry, However, I wanted to know the reason why it is not possible to post this transaction thru the Banking> Deposit module.
Appreciate your feedback on this matter.
Thanks!Hi,
Same error message is appeared in 8.81 PL10. So this is not due to PL. If you select other than local currency at deposit currency, this error appears.
Let me check and update.
Thanks & Regards,
Nagarajan -
How to enter the currency value Flex mobile
Hi, friends, I type from Brazil
how to enter the currency value in textinput
format BR ( Brazil )?:
Thank'sHello Ashok,
Using the same BAPI , set the field R_3_USER of the tables parameter TELEFONDATA to 3 to save the mobile number.
Hope it helps.
Thanks,
Sriram S -
Message no. M8584 ''Enter a currency key'' in MIRO
Hi Gurus,
Infact I am facing a warning message while doing MIRO. Just after inputing MIRO header like Doc date, Posting date, Reference and lastly amount field when I press the enter, I get the above cited warning error. Can you please tell me how to remove this warning error message.
Thanks
BABAHI,
It sounds like your system is operating according to design. System behaviour changed with note 982645.
The message always comes if you enter header data into miro BEFORE entering PO number and hitting ENTER. It comes even then if you enter header data and PO but press ENTER only afterwards! This is because the check of existence of currency key in the coding happens before the determination of the currency key from the PO. At the time the data are not determined from the PO, the system cannot know whether there will be a PO entry as in MIRO you can post also without a PO reference.
To eliminate the message is to enter the PO first then all other relevant data.
To get rid of this behaviour please implement SAP Note 1001420. This note just deletes new coding.
Please assign points if it useful.
Regards
Ravinagh Boni -
Hi All,
After entering Sold to Party in Service Order, system throws an error as shown below.
I have maintained the Sales Area, Currency and Cust. pricing procedure in BP but still the error exists.
Could you please help me how to fix this.
Regards,Hi Ajay,
Thank you for your response.
Yes,the Currency field has been maintained in Sales Org level.
But Currency field is not available in Service Org level, but I do not think it causes the error. Correct
me if I am wrong.
Currency field is maintained in sales org level but error exists in transaction level. Please help me with your inputs.
Regards, -
Raise exception when the user entered value is not present
Hello Abap experts,
To raise an exception in the function module when the imported variable value is not presnt in the table.
import variable: cust_name.
how to define a exception for this raise it in the code. any examples and suggestions.
Thanks,
BWerHere is the F1 help on RAISE.
<i>
RAISE
Basic form 1
RAISE except.
Effect
This statement is only effective in function modules and methods.
It triggers the exception except.
If the exception is to be handled by the caller of the function module or method ( CALL FUNCTION or CALL METHOD ), the system passes control straight back to the caller. EXPORT parameters of a function module or method are not filled. The EXPORTING, CHANGING, and RETURNING parameters of a function module or method are only filled with the current values if they were defined to be passed by reference. reference).If they are defined to be passed by value, they are not filled.
If the exception is not handled by the caller, the program terminates with an appropriate error message.
Example
Let there be a function module STRING_SPLIT containing the following code (see also the example in the documentation of the CALL FUNCTION statement):</i>
<b>FUNCTION-POOL CSTR.
FUNCTION STRING_SPLIT.
IF STRING NA DELIMITER.
RAISE NOT_FOUND.
ENDIF.
ENDFUNCTION.</b>
The calling program might then contain the following:
<b>PROGRAM EXAMPLE.
CALL FUNCTION 'STRING_SPLIT'
EXCEPTIONS
NOT_FOUND = 7.
IF SY-SUBRC = 7.
WRITE / 'There is a problem.'.
ELSE.
ENDIF.</b>
<i>
If the NOT_FOUND exception is raised in a RAISE statement in the function module STRING_SPLIT, the system exits the function module and returns control to the calling program. The return code, which you should evaluate directly after the CALL FUNCTION statement, now contains the value 7.
Note
Runtime errors:
RAISE_EXCEPTION: The caller did not handle the exception that was triggered.
Related
MESSAGE ... RAISING
Additional help
Creating Function Modules
</i>
Regards,
Rich Heilman -
Enter a country for partner with type 'Sold-to Party'
Hi
when we try to send Delivery Scheduld to SUS from R/3 thro
Idoc "DELINS" we are getting the following error on the SRM side
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:002 -"Create" is not allowed (SUS Purchase Order
7500000062 ) Programm: CX_BBP_BD_ERROR===============CP; Include:
CX_BBP_BD_ERROR===============CM002; Line: 57
we also tried referring the note 987569, we are on SP as follows
SAP_BASIS SAPKB70010
SRM_PLUS 550 SAPKIBK007
SRM_SERVER 550 SAPKIBKT07
regards,
AnandHi
<u>We have faced a similar problem in our previous Implementation.
This is happening in some cases, where the configuartion settingas are not correctly done.</u>
<b>After several tentatives, I managed to solve it activing on the Customizing for Multicompany in one client.
I have accessed to table BBPC_MARKETSET (Status of selection in a market set system) through SM30 and I have just removed the flag "Configure Market Set Procurement".</b>
<u>Also, another option,
check your Enhancements (customer specific) because this is a clear logical error.
The same partner function is added twice, hence it must be deleted programmatically in the enhancement logic.
FYI.. I usually encountered same type of issues in almost every implementation.</u>
Hope this will help.
Please reward suitable points, incase it suits your requirements.
Regards
- Atul -
Error during proxy processing An exception with the type CX_BBPX1_STD_MESSA
Hello,everyone!
My PI version is 7.11,SRM SUS version is 7.0,ECC version is 6.0 ,When I import XI SRM CONTEN,sending IDOC in ECC,there is a error some of the mesages:
<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_SUSPO_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>
Detialed error from SXMB_MONI,
Error in XI interface: Exception occurredE:BBP_PD:147 -Enter a country for partner 0015111411 with type 'Vendor' I:R5:553 -'Different country' field contents deleted because identical to 'Country' E:BS:002 -"Create" is not allowed (SUS Purchase Order 7100076527 ) Program: CX_BBP_BD_ERROR===============CP; include: CX_BBP_BD_ERROR===============CM002; Line:
This issue only ocuured for partner 0015111411, but we tried with other partner ID and those messages are processed sucessfully and PO is created.
I have a doubt that, is there functionality in proxy to compare the country with partner in SRM system. Could please anyone help me one the same.
Regards,
Baskaran KHI,
This is a standard proxy. I'm not sure how to debug the proxy with payload. Could you please tell me the steps.
We have one more error message
<FAULT_TEXT>Error in XI interface: Exception occurredE:BBP_PD:147 -Enter a country for partner XY91 with type 'Sold-to Party' E:BS:002 -"Create" is not allowed (SUS Purchase Order 7100076526 ) Program: CX_BBP_BD_ERROR===============CP; include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT>
Is there any table to check these details like Sold-to Part, Vendor etc in SRM system?
Regards,
Baskaran K -
Hi,
While posting invoice from MM TO SUS THRU XI the following error messgae is dispalyed in SRM(SXMB_MONI--TRACE)
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.
Please help in this regard.
Thanks,
ManuHi
Please refer this note
Note 987569 - SRM 5.0: ASN and SUSPO mapping corrections
E: 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 002: Create" is not allowed
regards
Muthu -
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.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> -
Purchase order doesn't create in srm sus
Dear customizer,
i have implemented a plan driven procurement with sus (r/3-sus) scenario,we have a problem when we transfer idoc from r/3 to sus.In sus sistem give me this error message
"An error occured within an XI interface: Exception occurredE:BBP_PD:147 -Enter a country for partner AER1 with type 'Sold-to Party' E:BS:002 -"Create" is not allowed (SUS Purchase Order 4500000005 ) Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT>"
I hope in your answer.Thank best regards.
Pernasetti AlessioHi
Please try this ->
Check whether the roles delivered by SAP meet your requirements. If not, you can create new roles and assign transactions to them. We recommend that you copy standard roles and tailor them to your requirements.
All users assigned to a respective role are then allowed to carry out the transactions. If required, you can refine the authorization check on the tab page Authorizations.
<u>Standard SAP Single-roles</u>
SAP_EC_SUS_ADMIN_PURCHASER (for purchasing administrators - SAP Supplier Self-Services)
SAP_EC_SUS_BIDDER (for bidders - SAP Supplier Self-Services)
SAP_EC_SUS_DISPATCHER (for dispatchers - SAP Supplier Self-Services)
SAP_EC_SUS_INVOICER (for invoicers - SAP Supplier Self-Services)
SAP_EC_SUS_ORDER_PROCESSOR (for order processors - SAP Supplier Self-Services)
SAP_EC_SUS_MANAGER (for managers - SAP Supplier Self-Services)
SAP_EC_SUS_SERVICE_AGENT (for service agents - SAP Supplier Self-Services)
<u>
If you want to use SAP Supplier Self-Services, proceed as follows:
1. Select one of the following single roles:
SAP_EC_SUS_ADMIN_PURCHASER
SAP_EC_SUS_ADMIN_VENDOR
SAP_EC_SUS_BIDDER
SAP_EC_SUS_DISPATCHER
SAP_EC_SUS_INVOICER
SAP_EC_SUS_MANAGER
SAP_EC_SUS_ORDER_PROCESSOR
SAP_EC_SUS_PRODUCT_MANAGER
SAP_EC_SUS_SAR_PROCESSOR
SAP_EC_SUS_SERVICE_AGENT
SAP_EC_SUS_SERVICE_MANAGER
2. Choose Change Roles.
3. Choose the Personalization tab page.
Note: The personalization applies to all roles, meaning the user can also create his own roles, for example copying the delivered SAP SUS roles. He can tailor these roles to his requirements by changing the SUS-specific attributes (BBP_SUS_ROLE_ATTRIBUTES).
1. Select the entry BBP_SUS_ROLE_ATTRIBUTES (SUS-specific role attributes).
2. Choose Change values.
A dialog box for maintaining SUS-specific roles appears.
3. If required, perform the following steps:
If the role should be displayed in the SUS User Management (UM) and should be able to be assigned to the relevant user by the supplier administrator, set the indicator to display the role in SUS UM.
If the user should be displayed as a service agent for the purchaser, set the Service agent indicator.
If you want to define the user as an SRM administrator, set the SRM administrator indicator. The user is then authorized to change all supplier data.
If want to assign the role SUS administrator automatically to the user during registration, set the SUS administratorindicator.
Sets the relevant indicators if you want users to receive the following notifications: Notification If Purchase Order Not Opened, Notification If Purchase Order Response Is Missing, Notification If ASN Is Missing, Notification If ConfirmationIs Missing, Notification If Invoice Is Missing,</u>
Regards
- Atul -
Hello Everyone,
I am reviewing our failed integration in SUS and have noticed that most of the purchase orders not transmitted to SUS has encountered the following errors:
a)
Error in an XI interface: Exception occurredE:AM:219 -Enter a postal code E:BBP_PD:147 -Enter a country for partner 8000000001 with type 'Supplier' E:AM:219 -Enter a postal code E:BS:002 -"Create" is not allowed (SUS Purchase Order 4010022754 ) Program: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57
b)
Error in an XI interface: Exception occurredE:BBP_PD:147 -Enter a country for partner 8000000194 with type 'Supplier' W:BBP_PD:097 -No delivery date exists for item; check whether this is necessary W:BBP_PD:097 -No delivery date exists for item; check whether this is necessary W:BBP_PD:097 -No delivery date exists for item; check whether this is necessary W:BBP_PD:097 -No delivery date exists for item; check whether this is necessary E:BS:002 -"Create" is not allowed (SUS Purchase Order 4010021989 ) Program: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57
I have checked postal code and country of the suppliers, it has been setup properly. How can we resolve this?
Thanks.Pipsquik,
In MM SUS this kind of an error occurs when company data is not present in the XML PO sent out. Not sure about SRM-SUS.
Meanwhile could you share your views on this thread. PO is not getting released from SRM
Since you already are able to generate XML POs, I think you are the best person to help him out.
Regards,
Nikhil -
Hi..
we are trying to post Purchase Order from SRM to SUS through XI using Proxy structure.
on SRM side the msg is processed.In xi also the msg got processed.But in SUS inbound the
msg is failing with the following err:
An error occured within an XI interface: Exception occurredE:BBP_PD:147 -Enter a country for partner 0000000001 with type 'Sold-to Party' E:BBP_PD:147 -Enter a country for partner VENDOR1 with type 'Vendor' E:BS:002 -"Create" is not allowed (SUS Purchase Order 1000000567 ) Programm:
Can anyone please help us in this?Hi
Just check this thread same is discussed here
SRM-XI-SUS
also check the SAP Note Note 982822 - PO Inbound in SUS with error BBP_PD 147
Note 804317 - SRM40/SUS/PO: PO inbound with error BBP_PD 147
Note 956072 - SUS: Not possible to create ERS invoice in SUS
Regards
Abhishek
Edited by: Abhishek Agrahari on Jan 14, 2009 11:59 AM
Maybe you are looking for
-
Structure field and Table field
Hi All, How is using a field from a global structure different from using a field in a table? Moderator Message: Please search before posting. Edited by: Suhas Saha on Sep 13, 2011 12:48 PM
-
Secondly, if my iphone had passcode...can someone still access the phone?
-
Having trouble accessign my HTML Resource files. I'm doing exactly the same thing I did in our last magazine. I triple checked my naming conventions for all files. Im trying to link a button to a pdf file as a "Go to URL" command. I've accurately typ
-
[solved] creating video dvd iso from existing folders
I used dvdbackup with the -M option to copy a complete video dvd to my harddisk. How can I create a video dvd iso image from the existing folders? I used k3b till now (new video dvd, only create iso file).. Last edited by SiD (2008-07-26 18:18:13)
-
Java 5.0u10 or mustang release date
Does anyone know when will java 5.0 update 10 be available? Or when will mustang(1.6) be released?