MM-SUS and EBP-SUS same client

[Former Member]

Hi experts.

SAP documentation provides information that I can configure MM-SUS and EBP-SUS in the same client, so I will have one client for SRM and another for MM-SUS and EBP-SUS, ok I have done and really works.

The problem is if I replicate vendors from SRM to SUS the system creates a vendor company in the SUS and send e-mail with user and password that must be used to create new users, and if I send the same vendor from ECC to SUS the system will create a new vendor company in the SUS, right?

So the same vendo have 2 acounts in SUS and I need just one.

Some help will be welcome.

Nilson

[Former Member · Accepted solution]

Hi Nilson,

For handling of duplicate business partners:

You should have the role SAP_EC_SUS_ADMIN_PURCHASER for transaction

bbp_sus_bp_adm and then do the following:

1. Implement the BAdI called "Extension for Duplicate Check".

2. To consolidate business partners in the SUS 1:n scenario, start

transaction bbp_sus_bp_adm.

3. Choose Business Partner -> Duplicate Check.

SAP SUS checks if the business partner already exists.

Once this check has run, the purchaser administrator can decide either

to assign the partner to an existing entry (that is, consolidate the par

tners) or to create a new business partner.

a. To consolidate existing business partners, select "Consolidate

Existing Business Partner".

b. To create a new business partner, select "New Bpartner". If you

select this indicator, you must manually replicate the business partner

in the MM procurement system.

4. Choose Save.

Hope, this will help you.

Kind Regards,

Edel.

[Former Member · Accepted solution]

Good

Thanks for helpful reply

solved problem.

[Former Member]

Hi Nilson,

We are also looking into a solution in Having both SRM SuS and MM SuS in the same client .

We are having Ex Classic 7.02 and done MM SuS but looking for the option of SRM SuS.

Can you please guide on the steps and activity on the same..

Regards

IS

[Former Member]

Hi Nilson,

In relation to SUS neither BBPUPDVD, BBPGETVD nor BBP_VENDOR_SYNC are

supported to replicate vendors from ECC backends.

Please turn off replication using those programs and only use BD14 to avoid

double BPs to be created.

I hope this helps.

Kind Regards,

Edel.

[Former Member]

Eder

BBPUPDVD, BBPGETVD are used to replicate vendors from ECC to SRM not to SUS, my problem is that if I use BD14 to replicate vendor from ECC to SUS and after I use fleg PORTAL in vendor administration in SRM and send the same vendo to SUS a new vendor company is created.

Nilson

[Former Member]

Hi Partners,

Please let me know if you have suitable Consultants for SAP SUS Techno Functional requirement.

Please Send your resumes to me.

Title: SAP SUS Techno Functional Consultant.

Location: PHX, AZ

Duration: 6 +months

Job Description for SAP SUS:

Ø Must have Techno-functional Experience in SAP SUS and ROS.

Ø Ability to Design, configure, develop custom requirements and test SUS with ECC and/or SRM Integration.

Ø Experience in Vendor On-boarding, Collaboration and Vendor Integration processes.

Ø Knowledgeable in SAP SRM, PI/XI.

Ø Knowledgeable in ABAP, BSP.

Ø Collaboratively within the team environment

Ø Interact daily with the client, project team, and senior management staff

Any SRM cons with spl on SUS will be able to do the job

Thanks

Srikanth kumar.V