cancel
Showing results for 
Search instead for 
Did you mean: 

Clarifications on EBP-SUS and MM-SUS Scenario

sap_srm1
Explorer
0 Kudos

Hi !

We are planning to implement EBP-SUS and MM-SUS in one Client . Request you to help us on the following issues.

1. While the outbound messages will not have a problem from MM & EBP, how do we route inbound messages to MM & EBP effectively. Should be handle it in XI ?? If ues, what is the best criteria .

2. Since both the config guides for MM-SUS and EBP-SUS scenarios include transactions for transferring Vendor & Comapny Code data, how do we check duplication.For ex : if we transfer a Vendor from R/3 and subsequently try to transfer the same vendor from EBP , is there any inbuilt duplicate check ?

3. In MM-SUS, an ASN created in SUS creates an inbound delivery is created in MM. What would happen in case of EBP-SUS i.e when an ASN is created for an EBP PO ? We are on extended classic scenario ?

4.If you do a confirmation in EBP-SUS, will a GR be generated in both EBP and subsequently in MM.

Request yr help pl.

Regards

Accepted Solutions (1)

Accepted Solutions (1)

Ramki
Active Contributor
0 Kudos

Hi

Strong recommendation from me: Pl use <b>different clients for SUS and SRM</b>.

1) You need to have a condition defined in XI to route messages appropriately to MM & EBP systems. For example, ASN from SUS uses same XML for both EBP &MM. So, in the mapping, you need a condition.

2) In the std, it creates different business partners. If you want the same business partner for the same vendor, then suggest you to modify VENMAP table after replication. There are no known adverse impact of modyfing this table.

If you are using the same client for EBP & SUS, I expect problems in Org plan definition, company definition etc and to my knowledge there is no good config guide to guide this. This is because, SAP does not recommend to have single client for EBP & SUS.

3) ECS with SUS has some limitations. I hope you know them. In EBP-SUS scenario, you have confirmation (instead of ASN) which creates a confirmation in EBP.

4) It does not create GR in MM...this is, to my knowledge, one of the limitations of ECS with SUS.

Best regards

Ramki

Ramki
Active Contributor
0 Kudos

Also check note

543544 : SUS - ECS with EBP not supported

sap_srm1
Explorer
0 Kudos

Thank Atul & ramki.

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi

Welcome to world of SRM.

I guess, you must have got enough details in the SRM guides.

Anyways, better to understand the basics first,, before going in detail. I hope this will answer all your queries.

<b>Refer to these links -></b>

<u>Supplier Enablement</u>

<b>http://help.sap.com/saphelp_srm50/helpdata/en/cd/0e343e47fd6b2ee10000000a114084/frameset.htm</b>

<u>SUS-EBP Scenario</u>

<b>http://help.sap.com/saphelp_srm50/helpdata/en/06/0f343e47fd6b2ee10000000a114084/frameset.htm</b>

<u>SUS-MM Scenario</u>

<b>http://help.sap.com/saphelp_srm50/helpdata/en/39/0f343e47fd6b2ee10000000a114084/frameset.htm</b>

<u>Supplier Self-services</u>

<b>http://help.sap.com/saphelp_srm50/helpdata/en/25/99b13c48740d55e10000000a114084/frameset.htm</b>

<u>Procurement</u>

<b>http://help.sap.com/saphelp_srm50/helpdata/en/8e/e5623c046a9b67e10000000a11402f/frameset.htm</b>

<u>Users in SRM user Management</u>

<b>http://help.sap.com/saphelp_srm50/helpdata/en/cd/6313513813554e941a02a91540c29e/frameset.htm</b>

<b>Please try this SAP OSS notes as well to get System architecture details-></b>

<u>Note 982871 - Consulting services: supplier integration in SRM

963000 - Usage and release of SRM as AddOn to ECC in ERP2005

868192 - Consulting solution: SUS-MM (SUS-MMSRV) service procurement

573383 - EBP and SUS deployment variants</u>

<b>Also do read this -></b>

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

Standard SAP Single-roles

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)

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>

Do let me know.

Regards

- Atul