Definition
Enables centralized maintenance and storage of master data, with
distribution mechanisms ensuring that master data can be delivered to
systems that need it. It differs from master data harmonization in that
master data is created centrally using a rich client. Information can
subsequently be distributed to clients as required using interactive
distribution.
Key capabilities/use case
Aimed at central data ownership resulting in substantial quality improvements
Allows companies to set own company standards in managing master data
Still allows client-specific control on master data (local completion)
PREV<<NEXT>>
Central Master Data Management – Benefits
Central Master Data Management – Benefits
From central master data management, companies gain the
following benefits:
Incorporates all benefits of master data consolidation
Enables central data ownership, resulting in substantial quality
improvements
Allows companies to set own company standards in managing master data
1) Can Mask functionality be used for determining which BP records exist in R/3?
Ans. There is no need for a mask to be generated, as Syndicator can filter records to be sent according to the Agency and remote key stored within MDM. The “suppress records without key” option needs to be set to “Yes”.
2) Can a mask be recreated automatically from a saved search selection criteria?
Ans. This is not currently supported. Records can be hidden per role using “constraints” functionality in the console.
3) Can MDM send only changed fields and data and not the whole record?
Ans : There are two possible answers to this.
1. If you are extracting changed data through the API, you can set the timestamp field to change only when your key fields change. This will allow you to select only those records whose changes need to be sent to R/3.
2. Using the Syndicator you can use the timestamp technology in calculated fields or set up the relevant search criteria in the Syndicator to select only those records that have relevant changes
