Skip to end of metadata
Go to start of metadata

FAQ, tipps and tricks related to the SAP predefined Business Content

MDM Content: Frequently Asked Questions


MDM Content Documentation

How can I login into a MDM Repository?

MDM Repositories contain a common user and (usually) a password. The valid logon credentials depend on your MDM Versions. All SAP MDM Repositories for MDM 5.5 include the user Admin without a password. All SAP MDM Repositories for MDM 7.1 include the user Admin with password sapmdm. Further information about users and passwords is available within the SAP Content Notes.

Back to top

How can I use the predefined MDM Content?

MDM Content is delivered as a template for supporting the generic MDM scenarios. As soon as the content is installed and correctly configured within a heterogeneous environment it is ready to use. This gives you a head start for implementing MDM scenarios in your specific projects. Due to its template character the content can be modified and/or enhanced to exactly fulfill the your project requirements. Using the pre-defined sample data that is part of the delivery, the content can be used for demo and/or training purposes, too.

Back to top

Where can I find SAP Notes about the repositories?

SAP Notes are generally available on SAP Service Market Place. The list below links directly to the SAP Note.

Back to top

Where can I find SAP Notes about the MDM processes?

SAP Notes are generally available on SAP Service Market Place. The list below links directly to the SAP Note.

Back to top


MDM Content Development

What is MDM Content?

MDM Content consists of two parts.

The first one is content for the SAP NetWeaver MDM Server. This includes MDM related development artifacts (e.g. repositories, table and field definitions, workflows, Import and Syndication maps, Portal Content, and so on). The server content enables the storage and maintenance as well as import and export of master data in MDM.

The second part is content for MDM connectivity. This includes all artifacts needed to connect the MDM server to its remote systems (e.g. PI Content, extractors for customizing and master data, and so on). The connectivity content enables the extraction and distribution of master data from and to remote systems as well as the related monitoring and supportability of the processes.

MDM Content is always specific for a master data object type (e.g. Customer, Material, Vendor, and so on).

Further information is available in the MDM Content Presentation.

Back to top

How can I copy a Remote System in a Repository?

There is no feature in MDM Console that does a Remote System copy automatically. If you are running MDM 7.1, you can use the Transport feature in MDM Console and some manual actions.

  1. Create a backup archive of your repository. 
  2. Export the Repository Schema using the Transport feature in MDM Console.
  3. Open the resulting XML in any (XML) editor
  4. Locate the Remote System that you want to copy.
  5. Copy and paste (add) your new Remote System to the Schema XML
  6. Within the new Remote System element, you have to adjust all occurences of the old Remote System Code and Name to your desired new values. If your editor supports a Find and Replace feature, you can use it. Ensure to check the XML elements:
    1. RemoteSystem: the attribute code must be changed to a new value. This new code value is used in various other elements as mentioned below.
    2. Name: the actual name displayed in MDM Console, Import Manager, and so on
    3. InboundPort: the attribute importMap consists of the Remote System Code and the Import Map Name. Adjust the code accordingly.
    4. InboundPort -> Name: the SAP standard Repositories use the Remote System Type (e.g. ERP) as part of the Port Name. Adjust this value as the Port Name must be unique.
    5. OutboundPort: attribute syndicatorMap consists of the Remote System Code and the Syndicator Map name. Adjust the code accordingly.
    6. OutboundPort -> Name: the SAP standard Repositories use the Remote System Type (e.g. ERP) as part of the port name. Adjust this value as the Port Name must be unique!
    7. SyndicatorMap -> Map -> RemoteSystems -> Item: attribute agency_code contains the Remote System Code. Adjust the code accordingly.
  7. Locate the portSequence attribute of the Repository element. Add your new ports accordingly.
  8. Save the XML.
  9. Import the schema XML to your repository using the Transport feature in MDM Console. You will see your new Remote System including all items (maps, ports). Check the import result carefully and accept the changes.
  10. You need to unmount and mount the Repository to create the port folders on your harddisk.

 MDM Quick Starters

What are MDM Quick Starters?

MDM Quick Starters (QS) extend the successful MDM Business Content approach. QS are preconfigured business packages that enable SAP NetWeaver Master Data Management (MDM) customers to rapidly deploy and implement a self-contained, directly applicable master data management scenario on top of SAP NetWeaver MDM and in some cases, in conjunction with SAP NetWeaver Business Process Management (BPM). Currently available quick starters are:

  1. Collaborative Material Master Data Creation
  2. Aggregate Physician Spend

  Back to top