Dear experts,
In short; when defining a qualified table in a repository you can define one or more fields as key-fields. This only prevents you from adding a the reference twice to the pre-selection but still allows you create more than one instance of this key within the same main table record.
For instance, if you have a material repository with material as key for the main table and you define a qualified table to represent the plant level data, you can still maintain more than one record for plant X in relation to material Y.
This results in data duplication and is a serious risk when distributing the data to subscribing systems.
The issue was reported through OSS and was explained to be a feature to allow multiple telephone number. etc to be maintained. No solution was provided.
We found this issue in our MDM system (MDM 5.5 SP05). Can you help us find out whether or not this issue was encountered at other clients/projects and if there is a solution? If you have the same issue, can you please let me know what version and support pack youu2019re on?
We would appriciate any help on this.
Thanks in advance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.