SAP MDM Architecture

[Former Member]

Need some help to locate best resources for

1) SAP MDM Architecture diagram for different environments - Sandbox/dev, QA, Prod with considerations on clustering, load balancing, scalabiligy, performance etc.

2) Sizing Information

3) Repository creation strategy

[Former Member · Accepted solution]

Hi Subingeorge,

For point 1 this should help you:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70b0caa1-92e5-2c10-c687-a8d05e778...

For point 2:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10c4cd5f-6893-2a10-a2b0-f9cb3cd38...

Please detail what do you mean in point 3.

Thanks,

Ravi

[Former Member · Accepted solution]

Thanks a lot Ravi.

For point 3, i am looking more info around the best practices for repository creation. like for example if i have multiple master data domain like customer, vendor, product etc. what are the key factors to decide if it should be configured in single repository or multiple repository....is it the volume a critical factor to decide if it has to be multiple repository. Similarly, what other considerations i need to take on repository. Our DB is DB2, OS is AIX.

[Former Member · Accepted solution]

Hi Subin,

I came across some very good information and I am detailing it below.

The challenge is to decide about having one repository for each Master Data Domain or combining several master data domains into one repository.A classic example for having two main tables in a repository would be products and vendors/suppliers. Both of them are stored in their own main table while the supplier part number can act as a link between the two objects.

You should consider having several main tables in a repository, when-

Each main table is an entity of its own (like vendor, customer, material, etc.). The object types in each main table can be clearly differentiated from each other.

Multiple main tables are related with each other for business reasons or that they share the same commonly used data from lookup tables, e.g. Plant codes, Countries etc.

In order to make the right decision three different areas need to be considered.

These are the Console, Read/Write operations and scenarios.

Considerations in the Console

A downtime (e.g. repository maintenance) will impact all main tables. Since several domains are in one and the same repository, all these domains would be affected when the repository is unloaded.

Performance impact (like load time of the repository). The more records and tables you have in your repository the more time it takes to load it. Similar impact would be when it comes to updating or inserting new records into the repository. Indexes need to be rebuild etc.

Considerations for Data Entry (CRUD operations)

Increase of the number of users working with multiple main tables in one repository. More domains in a repository typically means also more concurrent users working in the repository. In repositories where users have Read/Write authorizations, this could lead to potentially more locking issues.

Scalability for large number of records in repository. The more records there are in your repository and the more users are working concurrently with your repository, the more powerful your machine has to be.

Consider impact of imports, syndications and synchronizations for repositories having multiple domains u2013 this would probably mean more or more often performing these operations

Considerations from a Scenario perspective

Separation of operations: If thereu2019s one domain with read/write access required and another domain only with read access required, these two domains should go into separate repositories

Keep Business scenarios is separate repositories: e.g. CMDM (Central Master Data Management) and MDM-GDS (Global Data Synchronization) both should their own repository.

Above list provides a good starting point when it comes to making the decisions of single domain repositories vs. multi domain repositories. Often it will be also required to develop a prototype to see whether all requirements can be handled with the one or the other strategy.

For AIX OS please refer SAP Note: 1342611,SAP Note 1282668.

Thanks,

Ravi

[Former Member]

Hi,

You can get all guides related to SAP MDM at the following link - https://websmp205.sap-ag.de/installmdm71

Repository Creation Strategy depends on your data modeling.

Refer these guides for more information -

Data Modeling using SAP MDM -

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d0d8aa53-b11d-2a10-aca2-ff2bd42a8...

MDM Console Reference guide - http://help.sap.com/saphelp_nwmdm71/helpdata/en/4b/71608566ae3260e10000000a42189b/MDMConsole71.pdf

SAP NetWeaver MDM Business Content -

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0429acf-2742-2c10-f18a-e6212ff02...

Thanks,

Shambhu.