October 28, 2009 at 3:38 am
Symptom
When trying to mount a repository with a db-user and password that does not correspond to the one based on which the original creation or unarchive process for the repository was performed the repository will not load.
Other terms
853526 2009
Reason and Prerequisites
This is the correct behavior of MDM. You can only load a repository with the user and password in which the repository was originally created.
When the repository is first created it stores the user and password
that was used when it was created. Once you have changed the user or
password you will need to modify the password for each repository that
was created using the old password and well as the A2i_Xcat_dbs table.
Solution
Please see the attached screenshots showing were the passwords need to
be changed.
NOTE: Since you are [...]
October 28, 2009 at 3:37 am
Symptom
A record was created in MDM using the option “Add Master” and is flagged as Master. No variants were created for this record and still the “Delete” option is disabled (grayed out) for this record.
Other terms
966478 2009
Solution
The Data Manager only has support for adding master records, but not for modifying or deleting them. In order to do that, you need the SAP for Retail application. See the “MDM 5.5 IT Scenario Process Guide” for more information.
October 28, 2009 at 3:37 am
Symptom
Trying to modify records for a specific table in the Data Manger causes the MDM Server, MDS, to crash.
Other terms
874377 2009
Reason and Prerequisites
The issue is that a specific field, “Y” in a table, “X” has is an invalid option (no value was selected) that was set for the “Sort Index” property of this field (valid options should be Case Sensitive, Case Insensitive or Numeric only).
Solution
To fix this go to the Console, and then the table “X”. Go to the field “Y” and in the field detail, the “Sort Type” property should not be empty. Change it to “Case Insensitive” and you should be able to load the repository and add records into this table from Data Manager without MDS crashing.
October 28, 2009 at 3:36 am
Symptom
When trying to log into the standard Business Content (for example, VENDOR or CUSTOMER, etc.) with the user Admin and no password the log-in fails.
Other terms
942655 2009
Solution
The password should be “sapmdm” (all in lower case).
October 26, 2009 at 5:32 am
Symptom
Since MDM 5.5, it is possible to monitor MDM servers using CCMS heartbeat functionality. This allows to check the MDM server availability and health and let the central CCMS system (CEN) send alerts when an MDM server crashes.
MDM more often is now installed within Hardware clusters (e.g. Microsoft MSCS) to increase system availability and to lower failover times when a server crashes.
The cluster behavior is not mapped to the CCMS heartbeat monitoring as of today.
Today’s CCMS heartbeat of a MDM cluster:
Each physical host has its own CCMS installation reporting to the central CCMS system (CEN). So each MDM server is reporting
an own Monitoring Tree Element called: \MDM_HOST_\Availability \Master Data Server for each cluster host.
If only one MDM installation in the cluster is active and the others [...]
October 26, 2009 at 5:32 am
Symptom
There is information missing required for processing your MDM message
Other terms
OSS, Master data management, MDM7.1, customer message, Create, Support, ABAP API
Solution
To enable SAP Support to process your MDM message effectively the following information is required:
1 MDM version, Service package, Patch and build
e.g. MDM 7.1 SPnn Patch X 7.1.yy.zz
To find the build of all MDM client components please look at client
menu item: Help / About component
To find the build of MDM servers please go to installation directory
(e.g. Windows: C:\usr\sap\MDM\MDS00\exe), click on version
tab in the properties of the executable. Click on “File Version”
among the Item names and check the Value.
2 Which operating system(s) are your MDM application components
running on? What is the version?
3 Which database system is your MDM running on? What is the version?
4 Give a [...]
October 25, 2009 at 10:14 pm
Symptom
Since MDM 5.5, it is possible to monitor MDM servers using CCMS heartbeat functionality. This allows to check the MDM server availability and health and let the central CCMS system (CEN) send alerts when an MDM server crashes.
MDM more often is now installed within Hardware clusters (e.g. Microsoft MSCS) to increase system availability and to lower failover times when a server crashes.
The cluster behavior is not mapped to the CCMS heartbeat monitoring as of today.
Today’s CCMS heartbeat of a MDM cluster:
Each physical host has its own CCMS installation reporting to the central CCMS system (CEN). So each MDM server is reporting
an own Monitoring Tree Element called: \MDM_HOST_\Availability \Master Data Server for each cluster host.
If only one MDM installation in the cluster is active and the others [...]
October 23, 2009 at 5:55 am
Symptom
Out of memory error during import of Material master records (iDoc MATMAS05) into MDM 7.1 Material repository.
The error occurs when using MDM import manager or import server.
Other terms
SAP MDM, Master Data Management, MDIS, MDM 7.1 SP03 Material Content
Reason and Prerequisites
Prerequisites:
The problem only occurs if the material iDoc contains multiple sub-segments with many occurrences for plants (E1MARCM) or unit of measures (E1MARMM) or valuation segments (E1MBEW) or sales organisations (E1MVKEM).
Reason:
MDM import manager (and import server) tries to bring multiple occurrences of sub-segments into a flat structure which consumes main memory. If too many occurrences need to be flattened the process runs out of memory
Solution
Until a fix in MDM import manager / MDIS is available you may apply the following workaround: Use separate import maps [...]