MDM Tuple fields in iviews do not enforce required fields

[] [] [] [] [] [] [] []

Symptom
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 Field in the MDM Console appears with an asterisk in the Item Details iView. When populating fields in the Item Details iView, if values are not entered for those fields marked with the asterisk, a validation error occurs. (This functionality is only enforced on standard MDM iViews).
In the case of a Tuple field, an asterisk will be visible in the portal UI, however on saving the record, the validation on the field is not triggered.
Solution
Consider adding in a Data Manager a validation for enforcing Required property (see SAP Note 1259076 on how to apply such a [...]

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

[] [] [] [] [] [] [] [] [] [] []

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 [...]

Tracking Tuple changes in MDM Change Tracking application

[] [] [] [] []

Symptom
Change tracking report on main table records, lists only a single log entry when tracking tuple modifications. Changes to tuple details (values or tuple member values) are not displayed in the change tracking application report.
Other terms
iViews, MDM, Change Tracking, Tuple A2I_CM_HISTORY
Reason and Prerequisites
Tracking log entries in A2I_CM_HISTORY table, associates tuple changes as belonging to the tuple value and it does not directly link these changes as belonging to the main table to which these tuples relate.
The result is that when searching for all changes for a specific main table, the change tracking application will not include in its report tuples changes, apart from the record stating that a tuple field was modified.
Solution
To report on the relevent tuple details changes, a separate new [...]