purchase order doesn't create in srm sus

[Former Member]

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 Alessio

[Ramki · Accepted solution]

Hi

Use Txn BBP_SUS_BP_ADM and using Business Partner as company code option download the company codes from backend. This will create a node in PPOMA_BBP.

Then try

Best regards

Ramki

[Former Member · Accepted solution]

Excuse me can you explain better your solution,i do the download from r/3 system,but i haven't a new node in ppoma_bbp

Thanks for your attention

[Ramki · Accepted solution]

Are you sure ?

Did you receive any error messages while downloading ?

Click on the 'Companies' option in PPOSA_BBP and see.

[Former Member · Accepted solution]

Thanks a lot for your help,as you suggest i found a new node in ppoma_bbp. The purchase order has been created,i found an insert in table CRMD_ORDERADM_H,but i cannot see it in web page of sus system.Have you any ideas?

Best regards

[Former Member · Accepted solution]

Hi

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

[Former Member · Accepted solution]

Dear RAM..

I am facing similar type of problem. in SRM server ... I have copied my SRM data of existing server & installed in new server . we have connected this new server with XI Development & Re test server.

All the setting relevent to proxy & logical & all are completed by the XI consulatant...

Now my Data are flowing from SRM to R/3 test properly but .. From R/3 to SRM server Idoc is coming to SRM Server in XML form but giving error as mentioned below.

XML :1

Error in SXMB_ moni is as mentioned below.

StandardMessageFault

An error occured within an XI interface: Exception occurredE:BBP_PD:147 -Enter a country for partner 0000000054 with type 'Sold-to Party' E:BS:002 -"Create" is not allowed (SUS Purchase Order 9401356434 ) Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57

No further information available

XML:2

StandardMessageFault

An error occured within an XI interface: Exception occurredE:BBP_PD:147 -Enter a country for partner 0000000044 with type 'Sold-to Party' E:BBP_PD:147 -Enter a country for partner DF002 with type 'Vendor' W:BBP_PD:649 -Delvery date is in the past; check the entry E:BS:002 -"Create" is not allowed (SUS Purchase Order 9401356443 ) Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57

No further information available;

XML: 3

StandardMessageFault

An error occured within an XI interface: Exception occurredE:BBP_PD:147 -Enter a country for partner 0000000054 with type 'Sold-to Party' W:BBP_PD:649 -Delvery date is in the past; check the entry W:BBP_PD:649 -Delvery date is in the past; check the entry W:BBP_PD:649 -Delvery date is in the past; check the entry W:BBP_PD:649 -Delvery date is in the past; check the entry W:BBP_PD:649 -Delvery date is in the past; check the entry W:BBP_PD:649 -Delvery date is in the past; check the entry W:BBP_PD:649 -Delvery date is in the past; check the entry W:BBP_PD:649 -Delvery date is in the past; check the entry W:BBP_PD:649 -Delvery date is in the past; check the entry E:BS:002 -"Create" is not allowed (SUS Purchase Order 9401356430 ) Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57

No further information available

If you can help...

I will be very much thankful to you..

[Former Member · Accepted solution]

Hi Atul,

     I am facing the same issue, but only for a newly created company code.

In other cases MM-SUS scenario is working fine.

We are using SRM 7.0.

If you can help, I would be very thankful to you. I am new to SRM.

Regards,

Nikhil