MDM 321 – SAP Netweaver Master Data Management

Symptom
This note contains the neccessary manual steps when upgrading from GDS 1.0 to GDS 2.0
Other terms
SAP NetWeaver MDM global data synchronization, SAP GDS 2.0, SAP GDS 1.0
Reason and Prerequisites
The repository of GDS Console 1.0 has been upgraded with the migration tool shipped with GDS 2.0.
Solution
The following manual steps have to be accomplished after finishing the repository migration:
In case you applied the note 1299944 for GDS 1.0:Open the MDM console and login to the repository of GDSUnload the repository.Select theRelationshipstable (this is a system table). On the right pane the content of the table is displayed. One entry is supposed to be there.Select the relationship with codeParentand change the value of the ‘Code’ attribute toParent1.Save the modifications and load the repository.Restart the MDM connector and GDS on the [...]

Symptom
You use SAP NetWeaver Master Data Management. You want to load master data from a SAP Remote System (R/3, ERP, CRM, SRM) into your MDM repository.You use MDM’s local extractor (transaction MDM_CLNT_EXTR) for this purpose.
Other terms
MDM, MDM_CLNT_EXTR, MDM_BATCH_EXTRACT, Inbound, Import, Master Data Extraction
Reason and Prerequisites
SAP NetWeaver MDM is currently not able to pull data from SAP systems into its storage. A SAP Remote System needs to push the data to MDM.
Solution
This note provides an overview of the local extractor (transaction MDM_CLNT_EXTR) and its handling, known and related issues, and so on.Please refer to the attached document as well as the related notes.
If neither the document nor the related notes seem to solve your issue, open an OSS message that contains the logon data [...]

Symptom
You use MDM 5.5 Support Package 4 and want to use the new extractor for customizing data for initializing the Support Package 4 repositories.
Other terms
SAP Master Data Management, MDMGX Generic Extractor
Solution
This note describes how to install the extractor in your MDM client systems. In the attachment, the note contains the required transport files and the complete documentation.
The note is updated on request. A change history is provided at the end of the note. Refer to the related notes in the attachments.
Components of the extractor and standard system
The generic extractor consists of the following components:
1. Release-independent core (package MDM_GX_CORE_RI)
As of Basis Release 6.20, the core is executable and contains the Customizing functions with all relevant objects.2. Release-independent core (package MDM_GX_CORE_RD)
The MDM_GENERIC_EXTRACTOR extraction program and the [...]

Symptom
GDS 1.0 SP06 Patch02
Other terms
GDS, GDS Console, UCCnet, Transora, 1Sync, Data Pools
Reason and Prerequisites
You want to install or upgrade GDS 1.0 SP06 Patch02
Solution
This patch contains files to upgrade GDS based on MDM 5.5 SP06 Patch04 (build version 5.5.64.71).
If you want to upgrade to this version please setup your GDS first to GDS 1.0 SP06 and upgrade afterwards with the content of this patch.
New Installation: Please install GDS 1.0 SP06 as described in the Installation Guide and Configuration Guide. Please note, the MDM Server version required for this release is: MDM 5.5 SP06 Patch04.Upgrade from GDS 1.0 SP05: Please refer to the GDS Upgrade Guide.
Update the GDS Console property reference
Please follow the steps below to update the property reference from the old 5.5.42.103 MDM Java API [...]

Symptom
GDS 1.0 SP06 Patch03 Hotfix01
Other terms
GDS, GDS Console, UCCnet, Transora, 1Sync, Data Pools
Reason and Prerequisites
Registration process were very slow in case of big packaging hierarchies. MDM connections were not properly closed in every case.
Solution
This release contains the following fixes:
Registration process were extremely slow in case of big packaging hierarchy because of multiple validation (0000651192 2009)Minor fix: MDM connections were not closed properly in certain situations

Symptom
There is information missing required for processing your MDM message
Other terms
Other terms
OSS, Master data management, MDM55, customer message, Create, Support,
webservice
Solution
To enable SAP Support to process your MDM message effectively the
following information is required:
1. The general information according to the note #915930.
2. The MDM_JAVA_API version (7.1 SP X Patch Y / digits version (7.1.xx.yy).
3. The MDM_WEB_SERVICES version (7.1 SP X Patch Y and SC counter)
4. The MDM_WEB_SERVICES_RUNTIME version (7.1 SP X Patch Y and SC counter)
5. The web service request and response.
6. An Archive repository that includes only the data needed for reproducing the issue
7. NetWeaver Java AS version (7.0 SP X)
8. Trace File or part of the trace which contains the MDM webservices exception stack trace.

Symptom
There is information missing required for processing your MDM message
Other terms
OSS, Master data management, MDM55, customer message, Create, Support, webservice
Solution
To enable SAP Support to process your MDM message effectively the
following information is required:
1. The general information according to the note #915930.
2. The MDM_JAVA_API version (5.5 SP X Patch Y and exact build version 5.5.xx.yy).
3. The MDM_WEB_SERVICES version (5.5 SP X Patch Y and exact build version 5.5.xx.yy and SC counter).
4. Which MDM web services are used: MDMSearchRecords, MDMCreateRecords, MDMUpdateRecords, MDMAddRemoteKey, MDMGetKeymapping.
5. Attach the web service request and response.
6. Please describe the MDM operation you which to perform (e.g., create a record in Table X with Fields A and B populated. Specify when you operate on lookup and or qualified fields).
7. Send us please (if not already supplied) [...]

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 [...]