Benefit from SAP NetWeaver MDM global data synchronization - GDS 2.1

SAP NetWeaver Master Data Management (MDM) global data synchronization - GDS 2.1 has successfully completed the Ramp-Up phase, and is now generally available for customers:

Highlights of the new release include:

  • Additional connection to SA2Worldsync data pool
  • Ability to exchange price in the GS1 format
  • Enable the exchange of catalogue selections via peer-to-peer
  • Automated initial publication of trade items
  • Display of images assigned to trade items
  • Propagate data through a hierarchy based upon material number
  • Limit user visibility by target market
  • Create trade items for multiple target markets

For more information about global data synchronization, see the SAP NetWeaver MDM global data synchronization site.

An Eye Opener for Transporting MDM Repositories

Its been a long time since i have not written a new blog in SAP MDM. Being SAP MDM as part of EIM, I was busy working in SAP BW and some other person reasons. Today, i am gonna talk about transport of MDM objects especially MDM repositories in different Environments like (Development, Quality and Production).
Once a developer done with the repository design, maps and all other stuffs and then need to transport it to Quality/Production Environment. What is the right approach.
I would always suggest you should move the repository schema with no records or Export/Import schema to quality environment and then finally to Production.
Its strange to know that some guys keep asking about how to move values of all LUT (look-up Table) to new environment without Main table records. So what they usually do..? They take the archive .a2a file of Developement repository and then unarchive it in Quality environment where they keep the LUT records and delete manually Main table data for this repository which sometimes causes lot of issues.

Issues Threat:

1). Since you have kept the same archive file of development repository with all records. After deleting main table records using MDM Data Manager, it may be still possible that these records are available in Database as Database also keep track of these MDM records using Internal ID key. So though you have even deleted records from MDM Data Manager but because of Database there might probablilty that you might face some issues while creating records in Data Manager like The Requested Record could not be found. So after deleting main table records one should ideally load repsoitory with Update Indices to refresh the linking of records in database too but still after doing it there may be probablilty that you can still face some other issues.
2). In order to keep LUT table values while transporting, you usually forget to integrate ECC system with MDM for populating Refrence table values which is not correct. In future, if you increase some values for look up tables in particular environemnt of ECC, same would not be reflected in MDM as you took these LUT values from ECC Development Environemnt only not from Quality, similarly it could be one of the biggest threat if you dont stick to basics and forget the same thing for Production Environment. You might configure MDMGX extraction for each of Environments for populating reference table values in MDM from ECC for smooth business operations.
3). Since in each environment your Remote System might be with different name and can have different LUT key value, so sometimes it may not allow to save main table records along with LUT Values.
For Example: For LUT table Countries, Country India has Key as IND in ECC Dev Env with remote System ECC DEV. It may or may not be different in ECC Quality Env. If India country Key maintianed as IN in Quality ECC so while importing it will lead to Data discrepancies. So sometimes you can face issues like Error 5611520 - Error Saving Key Mapping and Key mapping value must be unique. You cannot overwrite key.
4). If you are having Auto ID field maintianed in Main table of Repository so you have to make some alternative to count Auto ID starts again from 0 (Zero) since if you deleted exisiting records from MDM repository which you took as complete .a2a file from Development Environment it does not start from 0 (Zero) automatically.
There might be some other issues as well you can face. So I would suggest always move repository transport from one environment to different environment with no records just schema of .a2a file or with help of Export/Import Repository Schema in order to achieve smooth implemenation. One should not bothered about tranporting all Lookup table values from one environment to another using MDM repositories as it can lead to data discrepancies.
Note: All above are my personal views, there is nothing as such strong evidences i can furnish to support above and what other issues you can face, if you transport MDM repository.a2a file from one environment to another with complete main as well as lookup table records and then later deleting main table records to work on MDM repository.

Update on MDM Info Collector

MDM Info Collector Updates

After the initial version of MDM Info Collector (Klaus David blogged about it) that proved pretty successful in message handling by delivering required contextual information for thorough analysis and streamlined processing, the tool now comes with additional features.

The MDM Info Collector creates a comprehensive snapshot (zip file) of MDM system info that can be used later by SAP Support for offline failure analysis. This accelerates the analysis and resolution of the reported failure.

What's New in Version 2.0 of MDM Info Collector

New features include:

  • Remote execution of the MDM Info Collector tool by "SAP MMC" (uses "Server Snapshot" functionality)
    When you do not have access to MDM Server on machine (e.g. the machine is managed by the IT department) but you still need to provide the MDM system info to SAP support, then you would like to use the remote execution.
    From your local Windows PC, run SAP MMC to collect info from a remote UNIX/Windows MDM machine, then download snapshot (containing info package) to your local machine (requires new SAP-Framework (720-path90) and updated MDM profile (available in MDM7.1 SP7 Patch7).
  • Supports also Master Data Import Server (MDIS) and Master Data Syndication Server (MDSS), in addition to the Master Data Server (MDS)
  • Collects much more information than before
    This additional information accelerates the analysis time of customer messages by SAP Support
  • Supports SSL
    As of MDM7.1 SP7

For more info, see the how-to information (PDF) that is attached to SAP Note  1522125.

Hope this info is useful for you.

SAP Developer Network Latest Updates