MM-SUS: EBP, SUS and ROS in one single client

[former_member524065]

Dear experts,

We are currently on:

SRM 7

ECC6 (EhP 4)

Classic Scenario

We are in the process of implementing SUS and ROS in the same client as EBP.

There are a few things which are not clear to me:

- Do I still need to set up a seperate Vendor Group for SUS next to the one used for EBP? Or can I use that one for both puposes?

- Is vendor replication from ECC to SUS (BD14) necessary or is the replication from ECC to EBP (BBPGETVD) enough for this?

- Should I keep the vendors used for EBP seperate from those used for SUS.

- After user registration (ROS) and acceptance do I still need to transfer the vendor to EBP taking into consideration that they are both on the same client?

Thanks for your reply

[Former Member]

Hi Djurick,

First of all it is not recommended to have EBP and SUS in the same client.

However coming to your questions

- Do I still need to set up a seperate Vendor Group for SUS next to the one used for EBP? Or can I use that one for both puposes?

You need to setup a separate group for SUS vendors.

- Is vendor replication from ECC to SUS (BD14) necessary or is the replication from ECC to EBP (BBPGETVD) enough for this?

BD14 is mandatory even if you have SUS and EBP on same client

- Should I keep the vendors used for EBP seperate from those used for SUS.

Yes

- After user registration (ROS) and acceptance do I still need to transfer the vendor to EBP taking into consideration that they are both on the same client?

Yes you need to transfer

Regards,

Nikhil