MDM 321 – SAP Netweaver Master Data Management

MDM Change tracker (Web UI) tuple limitations in 7.1 SP00/01

July 15, 2009 at 2:00 am

[Change] [iView] [MDM] [media tracker] [mobile tracker] [Portal] [python tuple] [tracker] [tuple] [UI;] [Web]

1. MDM Tuple fields in iviews do not enforce required fieldsSymptom Saving a record with MDM Item Details iView does not enforce Required property on Tuple fields Other terms Tuples, Required, iViews, MDM Reason and Prerequisites A field marked as a Required...
2. Dates and numbers formatting – MDM standard iViewsSymptom Date and numbers format do not match the user regional setting Other terms Date, Currency, Real, MDM, Portal, iView Reason and Prerequisites MDM Standard Portal iViews formatting of dates and numbers...
3. MDM 5.5 & 7.1 Portal Standard iViews notes summarySymptom Relevent SAP Note for portal iViews is not found Other terms MDM-FN-TC; Portal; Web UI; Reason and Prerequisites Solution Following is a summary of MDM iViews related SAP Notes grouped by...
4. Inability to open images and Pop-up windows – MDM iViewsSymptom There are 3 possible symptoms to this issue: 1. MDM Portal iViews image fields are not displaying image. Instead of the linked image, a red “X” is displayed. In addition, Portal...
5. MDM Item Details iView – “Record is protected” messageSymptom When trying to edit a record via MDM Portal Item Details iView you see a message that “Record is protected, record is checked out” and you can not edit it. Trying...
6. Numbers after decimal point displayed differently- MDM iViewSymptom Formatting of MDM Real, Measurement or Currency field types with 1 or more digits after the decimal point appear to be different when comparing these fields in Item Details Edit mode...
7. “Illegal value for parameter” error when uploading PDF/ImageSymptom You are trying to upload a new PDF/Image file to the MDM PDF/Image Table using the MDM Portal iViews but receiving a “com.sap.mdm.internal.protocol.manual.ServerException: Illegal value for parameter” error. Other terms MDM,...

Symptom

When using MDM 7.1 SP00/SP01, after making changes to the tuple field for a specific
record, The permanent ids within the change history table are populated
inconsistently. This results in the tuple changes not being found when searching utilizing the
main table record permanent id. This also occurs when working with the MDM Change tracker in the Portal in conjunction with a
Result Set iView, i.e. The change tracking log entries for the selected record will not display the tuples that changed
Other terms

Change tracker, MDM, Portal, iView, Web UI
Reason and Prerequisites

The issue occurred due to a limitation of how tuple changes were
recorded in the change tracking table (it did not save the change with
the Main table record permanent ID).
Solution

Changes to tuple values and tuple member fields may only be found by selecting the tuple table in the “Table” dropdown of the Change Tracker.
This limitation was removed in MDM 7.1 SP02.

Permalink