If the client is already using MDM to create the Material Master, can we use that MDM as a catalog for SRM or do we need to instal SRM-MDM in addition?
You should not have to install the MDM server again, but as mentioned above, the versions need to be of the same support pack. So far, the main patches of SRM-MDM1.0 released have a corresponding patch/pack for MDM5.5 (with OSS notes).
You should need to put in the SRM-MDM repository and deploy the UI for SRMMDM. The pre-delivered repository contains a main catalog table from which the default OCI mappings are setup. So, I think if you're going to use the delivered catalog repository, the items have to be imported to this table.
Then again, there may be other flexible ways of doing this correctly.
SRM-MDM is one of the Business Scenarios the MDM Suite covers.
It is called like that to differentiate between pure MDM processes (purpose Master Data Management) and SRM-MDM (purpose Catalog Management processes). Catalogs are master data like normal materials, just Content, why SAP also consolidated everything related to Master Data into the product MDM.
They also needed a selling point for making MDM a bit more popular and give it some excitement; with catalogs the argumentation is easy and provides clients an easy entry into the overall Master Data Management arena.
The SAP SRM-MDM Catalog 1.0 Business Scenario as well SRM-MDM consists out of these four technical blocks:
- Server
SAP MDM Import Server
SAP MDM Server
- Database
SAP MDM Database
- Clients
SAP MDM Console
SAP MDM Data Manager
SAP MDM Import Manager
SAP MDM Workflow
- Web Application Server
SRM-MDM Catalog Search
For set up look into IT Scenario Configuration Guide for SAP NetWeaver MDM 5.5
(Document Version 2.00 – September 2006) available on the SAP Service Marketplace via quick link operationw04 → SAP MDM → SAP MDM 5.5 Documentation Center → MDM
Product replication, your are asking for, is needed in the case the materials are not there, as clients implement MDM for using catalogs only as well. They are the heart of the whole system & process. From there the master catalog can be created, which then can be integrated into catalog driven scenarios like SRM as well CRM via OCI. In case of SRM only (6.0) the config guide refers to the SRM-MDM Catalog Scenario (also, because the XI Content is specific for this scenario).
The SRM-MDM Business Scenario is mandatory starting with SRM 6.0. In case of a lower SRM release you have the choice between CCM and MDM.
Maintenance for CCM is currently scheduled to end in 2013. Long time for water to run down the whole river.
few weeks ago, we are in same situation and due to version project consolidations, we have decided to install SRM-MDM catalog on to separate landscape. We will consolidated this to MDM landscape in next year.
The details of installation:
SRM-MDM Catalog:
MDM SP 5.5, NW04SR2; We are using same database for both MDM and NW04S. if you are going to use portal component then it is better to have 2 databases to manage loads/performance.
More Details:
Please know that SRM-MDM Catalog software is part of SRM 6.0 but we still need to manage SRM-MDM as separate installation from SRM landscape. but you cna combine with existing MDM if you have one landscape.
The following SRM 6.0 landscape explains the landscape details very well.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.