Symptom
Transport operations end with a error message stating that Import or Syndicator maps need to be upgraded.
Solution
Per the SAP Product Availability Matrix (PAM), Oracle 9 is not supported with MDM 7.1
Upgrade your DBMS from Oracle 9 to Oracle 10.
Symptom
When trying to delete an existing user from the Repository, the error
message pops up saying “Socket error on Receive” and when trying to delete it a second time, the mds server stops.
Restarted the system and again server stops when the same function is
repeated.
Other terms
872244 2008
Solution
This issue might be caused by a trailing space in the Users table in the DB.
Please perform the following steps:
Connect to Oracle DBMS directly and remove the trailing space in
USERNAME column of A2I_CM_USERS table for the user you mentioned.
Symptom
You would like to extend SAP Netweaver Global Data Syncronization 2.0 solution and have some problem or questions.
Other terms
SAP Netweaver MDM GDS, GDS 2.0, GDSCORE, GDSUI
Reason and Prerequisites
Extending SAP GDS 2.0 solution
Solution
Please follow below mentioned steps to extend SAP MDM GDS 2.0 solution.
1. Create the additional field in GDS repository in MDM. Field name should start with Z_.
2. In order to to get these field imported into GDS from external system, please do addition mapping to pass those fields in following segment /ns0:MT_TradeItems/Payload/Item/TargetMarketData/CustomFields of interface name MI_TradeItems_In namespace http://sap.com/xi/GDS/1Sync/64
3. Enhance the UI configuration to include these fields in a new tab.
Please see following help link
http://help.sap.com/saphelp_gds20/helpdata/EN/E2/F0F933057B43D3B96E608E45B78F2C/frameset.htm
4. All the Z_ fields maintained in GDS repository will get extracted into GDS export interface name MI_TradeItemExport_Out namespace [...]
Symptom
SAP NetWeaver MDM 7.1 SP03 Release Note
Other terms
MDM, Master Data Management, SAP NetWeaver MDM, Service pack 3, Service Pack 03, SP3, MDM 71,
Solution
Enhancements & Bugfixes coming with SAP NetWeaver MDM 7.1 SP03
Note: the number after every correction is an internal reference for
SAP Customer Support.
Note: If there are more than 400 named searches in the MDM repository, MDM will only show the first 400 in the menus. Neither the Data Manager or MDM Server do anything to limit the number of named searches that can be created.
Please see related note: 1373911
MDS enhancements and Fixes:Enhanced: With MDM 7.1 SP03 we ship a build for AIX which is optimized for performance. This is based on an updated C++ run time library shipped by IBM, and the customer [...]
Symptom
After loading data with the Import Manager with the default Remote System called MDM, this key mapping can not be seen of modified in the Data Manager.
Other terms
3044088
Solution
This is by design. The default ‘MDM’ remote system is not meant to be edited manually via Data Manager and there are no remote keys created if you will connect with Import manager.
Symptom
Enrichment controller moves forward the Enrichment Controller Workflow steps before syndication or import is done and time out exception is thrown, although these processes complete successfully on time.
Enrichment Controller status field indicates an error, although enrichment process completed successfully.
Other terms
Clustered WAS
Reason and Prerequisites
Your SAP WAS which Enrichment Controller is deployed on, divided to J2ee clusters. The Enrichment Controller for MDM 5.5 and 7.1 does not support deployment on clustering j2ee. When Enrichment Controller is deployed on clustered architecture, each Enrichment Controller instance “competes” the other and conflicts are created.
Solution
* Avoid deployment of MDM Enrichment Controller on clustered WAS.
Symptom
Un-able to Unarchive\Duplicate repository on MAXDB
Reason and Prerequisites
MDM is limited to 17 languages on MAXDB
Solution
While using MAXDB – Use no more than 17 languages.
If you are working with a repository/archive that already has over 17 languages, please use another DB (Such SQL server or Oracle) to open your repository. Delete the unnecessary languages and create a new archive. That archive could be used safely with Max DB.
When adding a new language please keep in mind this limitation.
Symptom
MDSS does not syndicate files.
Reason and Prerequisites
According to the design of MDM 7.1 the Remote System called MDM is a
default remote system and as such you can not syndicate remote keys
from that system. This also holds true for the Import Manager in that
you can not generate or edit it’s remote keys (MDM) and you can not
import remote keys into the MDM remote system.
Solution
In order for this map to work you need to remove the remote key called
MDM from the ‘Remote Key Override’ in the Map Properties tab.