SRM MDM with Multiple Repositories and required S&A.

[Former Member]

Hello everyone,

We are in the planning process to migrate from CCM to MDM. Our current environment has two separate customers running on two separate SAP clients in SRM 5.0 using the internal CCM (one SAP SRM instance, 2 separate SAP clients).

In MDM it seems the concept of SAP client does not exist but the concept of an MDM Repository. I was thinking that by creating two dfifferent repositories (one for each customer) it would substitue the concept of the internal CCM on each SAP client.

Can we have one MDM system with two separate repositories one for each of the existing customers with the required S&A?

That is, customer A will logon to MDM to maintain only A's repository. Customer A must not be allowed to access B's repository and viceversa.

Also, Repository A would be published only for users using SRM system under SAP Client A, and Repository B would be published only for users using SRM system under SAP Client B.

The intention is that each customer will have their own electronic catalog.

Thank you.

Martin

[former_member544585 · Accepted solution]

Hi Martin,

The answer to your question is yes, it is possible to have one MDM system with two separate repositories one for each of the existing customers (that intend to have different electronic catalogs).

In fact, I think this would be the best way to separate: 1. data sets, 2. access.

1. Each MDM repository carries its own data set (like SAP client)

2. Each MDM repository has its own security (users/passwords, roles, etc.)

Another consideration (relates to point 1) is bringing data from SAP client (e.g. product master, contracts). Since you have two different SAP clients, managing replicated data from both of them in one MDM repository would be a form of suicide.

You can have multiple repositories on one MDM server. A common case is when you have a staging (master) repository, and a production (slave) repository. The slave repository is what you show to searching end users; the master repository is for data loads. You synchronize the slave repository with any changes from the master at such time when you're sure the master is good to publish.

Hope this helps.

Cheers,

Serguei

[Former Member]

Hi Martin,

You can create a new field "Client" in the catalog and use the same repository. The field Client can be filled using the BADI BBP_CCM_CHAR_MAINT. You can config a "constraint" in the role to "filter" by client.

Evandro

[Former Member]

Hi Evandro,

Thank you for your reply.

I think your suggestion will work but do you think that separate repositories will also work? Are there any implications to this?

The reason we have two separate SAP clients (one for each customer) is because that is the only way SAP will guarantee data isolation between customers.

Do you think this guarantee will exist by adding a "Client" field?

Thanks.

Martin