When trying to create a User Defined unit, for example ‘grit’, with name or suffix the error: “Suffix already exists as a unit name.” appears but with Pounds (lb), for example, this can be added.

Reason and Prerequisites

The error you received “Suffix already exists as a unit name.” is due to the design of MDM and how it works.
What this error means is that there is already a unit of measure with
this value – in this case it is ‘grit’ under the Polish Value
dimension.
In order to get around this what you can do is use the grit value but
change its name so as not to conflict with the already existing value.
For example you can call grit (len) or grit (custom).
The reason that you cannot add grit/grit is because MDM checks that the unit name added does not exist as suffix and vice versa.
Those checks were added in order to protect the data entered by users.
The reason you do succeed to have Pounds (lb) in two dimensions is that there is no “Pounds” as suffix and there is no lb as unit name across all dimensions.
Solution

Currently this is the behavior and in the future the plan is to have UOM managing in Console, so there will be probably some changes. Therefore we can only suggest either or both of the following:
1. Create a development request according to SAP Note #1156293
2. Use a workaround more or less as already suggested above:
2.1. If you do not need the grit/grit under the existing dimension Polish Level, then you may update it to grit-name/grit-suffix (for example).
2.2. Add grit/grit or grit./grit under Length as desired (or grit#) so that at least you have either the unit name or the suffix as grit.
2.3. If you cannot afford 2.1, then you must add name/suffix under Length that none of them is exactly “grit”.

Receiving a ClassCastException exception while creating connection using MDM Java API to MDM Server.
The same API code runs fine in a standalone Java Application, but gives this error when using NetWaver Web application.
The exception says:
java.lang.ClassCastException: class
com.sap.mdm.internal.net.SimpleConnectionImpl:library:com.sap.mdm.tech.mdm4j@com.sap.engine.boot.loader.ResourceMultiParentClassLoader@6609fca @alive incompatible with interfacecom.sap.mdm.net.ConnectionAccessor:expert.no/expert~products~search@co.sap.engine.boot.loader.ResourceMultiParentClassLoader@5090ac9b@alive
Other terms

0000840655 2009, 0002473957 2009, 0000747971 2008
Reason and Prerequisites

- Using NetWeaver Web application.
- There is a class loader conflict between com.sap.mdm.tech.mdm4j library and the jar files that assembled in the deployed EAR file.
Solution

The Web or WebDynpo application should include hard reference to Java API shared library in the form:
reference-type="hard">
provider-name="sap.com"
target-type="library">com.sap.mdm.tech.mdm4j

You have created a Role and gave him permissions to Delete records (the permissions were set in the “Roles” table in the MDM 7.1 Console).
However, when logging on to the MDM Data Manager, the user that is assigned to this role is unable to remove relationships from the records.
Although no message is displayed in Data Manager, the following message
is logged in the server log file:
Returning from a function and encountering error: 0xFFAA8000
CatMgr@RemoveFromRelationship275#Relationships.cpp
Other terms

Delete, Relationship
Reason and Prerequisites

Relationship operations rights are control by rights specified at the Functions [default] level.
Solution

Give Execute access rights at the Functions [default] level and None
access rights for other operatios appropriately. This will allow the user to remove relationships.

You want to separate the individual users in an MDM system from the administrator so that they can receive different rights.
Other terms

AS/400, OS400, system i, i5OS, iSeries, IBM i
Reason and Prerequisites

Information requirements
Solution

After the installation of an MDM system, the user, who was specified and created as the MDM user during the installation, has all rights to carry out all tasks (including administrative tasks) in the MDM parts and also in the operating system.
In general, however, the users of the MDM system should work with the MDM system using the Windows-based applications only, without having the rights to carry out administrative tasks.
For information about the user concept in the MDM application, read chapter 10 of the MDM Console manual (MDM system administration). Conclusion: Essentially, the various repositories are protected by a password that is to be assigned by the owner. In addition, you can use a server password that can be freely assigned (right-click and choose the Change Password option) to protect the repositories from being changed via the MDM Console – only users who change or create repositories must know this password.
Additional recommendation for IBM i:
For the MDM users, you can initially create an additional user USER as a copy of the user ADM (WRKUSRPRF ADM). Then change the following attributes of USER:
GRPPRF(OWNER) SUPGRPPRF(R3GROUP) INLPGM(*NONE) INLMNU(*SIGNOFF) LMTCPB(*YES).
In addition, you must assign a new password for USER.
Here, it is particularly important that the entry for GRPPRF is identical for both ADM and this USER.
You can transfer this user profile to the MDM users without them being able to execute administrator functions inadvertently.

A master data management (MDM) system that is installed in SYSBAS is to be relocated to an independent Auxiliary Storage Pool (iASP).
Other terms

AS/400, OS400, system i, iSeries, i5OS, Auxiliary Storage Pool, ASP, independent ASP, IBM i
Reason and Prerequisites

Information requirements
Solution

Prerequisite:
If your MDM system is running on a kernel with SAP Release 710, you must use at least the patch ILE as of level 175 (see related notes).
We recommend the following procedure:
1. Use the MDM Console to archive all of the repositories on Windows.2. Use the MDM Console to delete all of the repositories on Windows.3. As the user ADM of your MDM system , end all running instances – also end all corresponding SAPSTRSRV jobs in QUSRWRK.4. As a user with QSECOFR authorization, remove all of the repository-specific parts from the *.ini files (mds.ini, mdis.ini, mdss.ini) in the relevant subdirectory /config – only the global part may remain.5. As a user with QSECOFR authorization, remove all of the *LIB objects that comply with the MDM naming convention from QSYS.LIB (after deleting the repositories in the previous step, such objects should no longer exist).6. As a user with QSECOFR authorization, delete the *LIB object A2I_MDMDBS.7. Call the conversion program IASPIFSCRT for the iASP:
ADDLIBLE
IASPIFSCRT SID() IASPP() VHOST() TRANS() The integrated file system (IFS) part of your
MDM system is then in the iASP; the directories /usr/sap/< SID>_bak and
/sapmnt/_bak are backup copies and can be deleted.8. Change the default profile DEFAULT.PFL of your MDM system by entering the iASP according to the following line:
dbs/db4/rdbname = 9. Then log on again as ADM and start the MDM system.10. On Windows, start the MDM Console and generate a new – empty – repository as a test. In this case, you must specify the name of your iASP as the server of the database management system (DBMS), and you must use the case shown by the WRKRDBDIRE entry (generally uppercase). When you create this repository, the system must display a message stating that this DBMS server has not yet been configured for MDM. Choose OK to confirm this dialog box. You can then delete the test repository again.11. In the MDM Console on Windows, you can then unpack the repositories you previously archived.

XML Schema based import does not ignore missing element and overwrites destination field when Null Interpretation is set to Overwrite
Other terms

configuration
Reason and Prerequisites

The way Import Manager is currently designed to work with XML files will not enable him to distinguish between an XML with the field having and a missing field. In both cases, it will use the mapping that was done to the xml schema and saved in the map, but when the field does not exist at all, you may notice that it is added to the source hierarchy and displayed in Italics in 5.5 or displayed as any other regular in 7.1.
Solution

The solution suggested is to create two different maps, one with NULL Interpretation set to Ignore for data that does not include the field/s and one with NULL Interpretation set to Overwrite when the source includes the field and you want to overwrite destination when the source field has NULL.

There is information missing required for processing your MDM message
Other terms

OSS, Master data management, MDM71, customer message, Create, Support, Syndicator, Syndication Server, MDSS

Solution

To enable SAP Support to process your MDM message effectively the following information is required:
1 Please provide us the general information according to the
note #1278148.
2 Please provide the name of the syndicator map. The map can be
either included in the archived repository or can be attached as
file using the Export Map functionality.
3 State the destination properties you selected.
4 Please attach the output file if applicable.
5 Please attach a screen shot of the error.
6 Please provide the exact date and time in GMT, when the error
occured.

Syndicator related issues
————————-
7 Please provide the Syndicator error log.
It can be found on the following path:
C:\usr\sap\MDM\MDSS02\log

Syndication Server related issues
———————————
7 Please send a copy of the mdss.ini located in:
C:\usr\sap\MDM\MDSS02\config
8 Please provide us the xml log and exception files:
e.g. on Windows:
C:\usr\sap\MDM\MDSS02\log
C:\usr\sap\MDM\MDS00\mdm\distributions\ base>\\Outbound\\\Log

C:\usr\sap\MDM\MDS00\mdm\distributions\ base>\\Outbound\\\Exception

This note contains information about changes done in SAP Netweaver MDM GDS 2.0 SP02 Patch 1

Other terms

SAP NetWeaver MDM global data synchronization, SAP GDS 2.0, SAP GDS 2.0 SP02 Patch 1

Reason and Prerequisites

Release of SAP Netweaver MDM GDS 2.0 SP02 Patch 1
Solution

SAP Netweaver MDM GDS 2.0 SP02 Patch 1 has the following changes.
1. New standard Repository with 1Sync 6.41 Version 2 GPC update.
Please check the relevant 1Sync Relese Note
2. Correction for saving the Effective Data Attribute
3. Correction in the export interface for the PackageMarksFreeFrom and Season Attributes. Please install the new PI interface patch (SP2 P1) too.
4. The picklist for hierarchy lookup fields (like ‘Global Item Classification’) contained only the root node. This is now fixed to expand to the leaf nodes.