ROS & EBP one client: Unable to trf accepted supplier from ROS to EBP

[Former Member]

Hi Guru,

We are working on SRM 7 with ROS and EBP being implemented on same client.

I am unable to transfer the accepted supplier from ROS to EBP with suppliers directory, system says the business partner already exists.

When potentail supplier registers themselves in ROS, a BP number is generated in SRM system. Purchaser accepts the potential supplier in Pre-screen and then trys to transfer the same from ROS to EBP. System issues an error messase BP number already exisits.

Is there any configuration I am missing?

Regards,

Sandeep Parab

[summer_wang · Accepted solution]

Hi Sadeep ,

If you have a one client scenario, then the value in the table BBP_BACKEND_DEST should have been as below:

For example :

CLIENT LOG_SYS DEST SYS_TYPE

300 ERDCLNT300 ERDCLNT300 EBP_SUS <--

This setting could solve the problem.

Best regards

Summer

[Former Member · Accepted solution]

Thanks Muthu,

Summer - a quick question

We would like to go for ROS without SUS in one client for supplier registration process, and in EBP we have following business scenario to configure in classic scenario, shopping cart with MDM catalogue, Sourcing, Transfer External Requirement (ERP requisition), Bidding, and Contract management.

Please correct my understanding.

We would be able to achieve all above business requirements by defining the SRM system as EBP_SUS rather than LOCAL.

We are having one SRM and one ERP system defined in table BBP_BACKEND_DEST.

Does it means that we do not need to define the SRM system as LOCAL anymore if we go for ROS without SUS in one client?

Sandeep

[summer_wang · Accepted solution]

Hi Sandeep,

There are different implementation scenarios.

The below can be in the same servers

1. ROS, SUS in Same Client and SRM in different client

2. ROS, SUS, SRM all in One client.

3. ROS, SUS, SRM all in different clients

In Different Servers.

1. ROS, SUS on one Server in same client.

SRM on different Server

2. ROS, SUS and SRM on different Servers

So in your case it is ROS and SRM in the same client. Ideally SUS is

also the major functionality that is implemented with ROS which caters

lot of additional functionalities. There are very rare cases where ROS

is being implemented but without SUS implementation.

But even in this scenario it is required that you maintain the

SYS_TYPE as EBP_SUS as it is a single client.

It does not bother any other functionalities.

best regards

Summer

[Former Member · Accepted solution]

Thanks Summer,

I shall try and let you know.

Sandeep

[Former Member · Accepted solution]

Thanks summer,

Problem is resolved with EBP_SUS config.

May I request you to help me with related question on ROS business partner status unable to change to RELEASED.

ROS (without SUS) and EBP has been deployed on the same client.

Regards,

Sandeep Parab

[Former Member · Accepted solution]

HI

i've the same issue. EBP and ROS (without SUS) into same client.

I modified via SM30 table BBP_BACKEND_DEST with type system= EBP_SUS and not flagged any other field.

But:

Could not create business partner (see error messages)

Business partner could not be created

Partner data not transferred from catalog. Inform system admin.

How can i do?

Am i missing something?

regards

andrea

[former_member183819]

SOME INFORMATION FOR YOU ..

Note 1302947 - Error on saving Vendor transferred from ROS in BBPMAININT

Note 1134978 - Implementation of ROS without SUS in a SRM system

Special exception:

The exception of XI implementaton would be allowed in the ROS implementation without SUS only in the one client one server scenario of the EBP and ROS. It means that the EBP and ROS is installed in the same client. Ideally, XI implementation is required but ROS implementation is possible even without the XI since the vendor Business Partner number is the same in the EBP and ROS system. But again, please refer to the note 573383 which speaks about the limitations of the single client scenario for EBP and SUS/ROS.