MDM 321 – SAP Netweaver Master Data Management

Symptom

You use standard Material Repository or Product Repository of SAP MDM and want to load data into GDS-Repository GDS 2.0 from the Material Repository or Product Repository instead of loading data from backend system into GDS Repository.
Other terms

SAP Master Data Management, Material Repository, Product Repository, GDS, GDS-Repository, GDS 2.0
Reason and Prerequisites

Data is loaded from Backend System to GDS Repository for using in GDS scenario. In some cases customer extracted information from Backend System to standard SAP Material Repository or Product Repository and want to load this repository to GDS Repository for using in GDS scenario.
MDM (Standard Material Repository or Product Repository):
Standard SAP MDM Material Repository or SAP MDM Product Repository is unarchived on MDM System.Standard SAP MDM Material Repository or SAP MDM Product Repository is loaded.SAP MDM Syndicator is installed.Ports and Remote System is set up. (by default available in Standard SAP MDM Material or SAP MDM Product Repository Repository)
PI:
PI-SystemFile Adapter is set up, i.e. connected to outbound “Ready” folder of “_MATMAS05″ (in standard SAP Material Repository) or “_MDMMatmas” (in standard SAP Product Repository). For more information please refer to Port Configuration in SAP MDM Documentation.PI-Configuration to route message to GDS-Application. (Please refer to GDS 2.0 configuration guide)
MDM (GDS-Repository):
GDS-Repository is unarchived on MDM -SystemGDS Respository is loaded.

Solution

This solution describes how to load data from standard SAP Material Repository or SAP Product Repository to GDS-Repository by extracting (syndicate) Material Repository or Product Repository data from MDM.
Remark in case Custom Message Type is used (instead using IDOC_Type “MATMAS_GDS.MATMAS05″:
The steps below describes loading data from Standard Material Repository or SAP Product Repository by utilizing standard IDOC Type MATMAS_GDS.MATMAS05. But using any Custom Message Type is also a valid approach. In case using Custom Message Type please feel free to copy Message Mapping as described in step 1 below. After copying please use Custom Message Type as source Message Type (instead IDOC Type “MATMAS_GDS.MATMAS05″). Before proceeding with remaining steps described below please refer also to “Integration Engine (Routing & Mapping) in “GDS 2.0 Architecture” (attchement Architecture_Overview.zip).
1. Open “PI Integration Repository”. Choose Software Component “GDS” and Software Component Version “GDS 2.0″. Under namespace http://sap.com/xi/GDS/1Sync/64 please open “Mapping Objects”, expand “Message Mappings” and choose “MatmasGdsMatmas05_TradeItems”. Copy “MatmasGdsMatmas05_TradeItems” and name it “MaterialMigration_MatmasGdsMatmas05_TradeItems” or “ProductMigration_MatmasGdsMatmas05_TradeItems”.
2. Now open “MaterialMigration_MatmasGdsMatmas05_TradeItems” or “ProductMigration_MatmasGdsMatmas05_TradeItems” and please expand “Header” under Message Type “MT_TradeItems” and make a dummy mapping by using function “Constant” for those fields:Sender (for example value: “Constant”)Receiver (for example value: “Constant”)MessageID (for example value: “Constant”)CreationDateTime (for example value: “Constant”)
Create Interface Mapping using this message mapping.

3. Configure PI to map incoming message using the Interface Mapping to the GDS Interface “MI_TradeItems_In”. Configure PI to route message through XI Adapter to GDS Application.
4. Open SAP MDM Syndicator by clicking on “Syndicator. exe” and connect to standard SAP MDM Material Repository or SAP MDM Product Repository.
5. Choose “File” and then “Open”. Choose “MDC R/3″ (SAP MDM Material Repository) or “MDC R/3 & ERP” (SAP MDM Product Repository) as “Remote System” and choose map “MATMAS05_R3″ (SAP MDM Material Repository) or “_MDMMatmas” (SAP MDM Product Repository) under “Available maps”.

6. Choose “Syndication” and “Execute”. Now save the file to “< root> \usr\sap\MDS\MDS00\mdm\distributions\LOCALHOST_MSQL\\Outbound\\\Ready\” in case of SAP MDM Material Repository or to “< root> \usr\sap\MDS\MDS00\mdm\distributions\LOCALHOST_MSQL\\Outbound\\\Ready\” in case of SAP MDM Product Repository. If File-Adapter is set up appropriate PI will pull the Data from “Ready” folder.
Remark:
If syndication server is running and the port is configured the extraction will happen automatically. When the messages reaches PI it will send to the GDS application through XI Adapter if this is configured accordingly.
7. Update Registration and Publication status from 1Sync by using MDM Import Manager. This has to be executed after initial load into GDS Repository ONLY ONE TIME! To update Registration and Publication status from 1Sync please follow the steps described in the note 1299122. After status update with help of MDM Import Manager, GDS import module will take care of updating right statuses when using GDS application.