Symptom
When you are logged on to EP as anonymous user, any popup windows that is triggered from the underlying MDM iView requires the user to enter user and password.
Other terms
iViews
Solution
This bevaior is by-design. If possible, set Item Details fields as drop-down and not as popups to avoid such issues.
Symptom
You would like the MDM UWL iView to allow launching of a Portal page or iView, dependent on an MDM workflow step ID.
Other terms
UWL
Solution
In Portal UWL UI, when a portal user will click on the UWL button “Show Record Details” it is possible to launch a popup window depending on the workflow step name. In other words, the same button “Show Record Details” can launch portalPage1 for WFStepID1 and portalPage2 for WFStepID2 depending on the current step of the workflow.
Details of this option are attached to this note as an attachment “UWL_MdmIViewLauncher_Step_name.pdf” and also xml sample “UWLsteppage.zip”.
Symptom
Comparing records using Compare Records or Compare with Original commands result different values while values are actually the same.
Other terms
Compare Records, Compare with Original
Solution
The Compare Records and Compare with Original commands provide a convenient way to visually compare multiple records.
When multivalued fields such as qualified, tuples, multi valued measurement, or multi valued lookups are part of the records to be compared, the order of values is significant. If same values appear in the records but in a different order, the comparison will indicate that the records are not the same.
Symptom
Not all fields are displayed and compared while using Compare Records or Compare with Original commands.
Other terms
tuples, qualified lookups, Compare Records, Compare with Original
Solution
The Compare Records and Compare with Original commands provide a convenient way to visually compare multiple records.
However in some cases not all fields are compared and displayed.
When tuple fields are involved in the comparison, only the tuple members which are display fields are compared.
Furthermore, if all display fields are similar but the other fields are not similar, the color coding will indicate that the records are the same.
Symptom
After upgrading the Portal Business Package from MDM 7.1 SP02 to MDM 7.1 SP03 some of the functions and usability have changed
Other terms
Tuple, iViews
Solution
The attached presentation describes some of the major enhancements that
have been implemented in MDM 7.1 SP03 (build 7.1.03.xx).
Note: The presentation shows a comparison between the features in MDM
7.1 SP02 and MDM 7.1 SP03 and does not reflect changes from earlier releases.
Symptom
In a Presentation Hierarchy, a Publication Family (node) became grayed out and is invalid.
Other terms
Disconnected family, Publication, Publisher, Publishing
Reason and Prerequisites
A publication Family usually becomes invalid (and noted with the gray sign) when it belongs to a publication, and afterwards the partitioning
has changed and all the records no longer belong to this family.
This situation can be easily tested by trying and execute the Set Record Mode Search (right click on the Publication Hierarchy Family), if this is the case it will be grayed out as there are no records to find.
Also, if you will try and filter the records in Data Manager by the
partition path, you will see that there are no such records.
Solution
The solution is to Synchronize Publication Children
(right click on the parent node [...]
Symptom
You want to use the Material repository delivered with SAP NetWeaver MDM 7.1.
This note provides a detailed documentation of the Material repository and the related content for Material Master Data Consolidation and Harmonization scenarios.
Other terms
MATMAS, MATMAS05, CLFMAS, CLFMAS02, MDC, MDH, MDMGX, MDM_CLNT_EXTR
Reason and Prerequisites
SAP NetWeaver MDM 7.1 SP03 and higher
Solution
The Material content delivered with MDM 7.1 SP3 features the new MDM 7.1 modelling capabilities. Tuples are used to replace the Qualified Lookup Tables (e.g. for Plant Data, …). Furthermore the new MDM Material data model was extended to support R/3 and ERP classification data (Classes and Characteristics).
Matching Content, Workflows and Validations have been reworked and enhanced. The content includes a small set of sample data (customizing and master records) that can be used [...]
Symptom
When trying to Activate a MDM service in a cluster you get an error message in the Application event windows:
“Unable to open trace file sapstartsrv.log. (Error 13 EACCES*:
Permission denied OR: The data is invalid.) [ntservsserver.cpp 2164]” and the service is not started.
Other terms
MDM, Cluster, 807136, Error 13 EACCES
Reason and Prerequisites
During update MDM does not update the SAPINSTANCE_FWK version.
This error is shown when the SAPINSTANCE_FWK is not compatible (too old) with the MDM version you are using.
Solution
In order to have a new version of the SAPINSTANCE_FWK you need to
uninstall MDM and install it again with new versions of MDM, MDM_IM and
SAPINSTANCE_FWK which can be downloaded from the SMP.
Please note – re-installing MDM will NOT cause any data loss in the
repository.