Rather than distributing the complete master data information, views of the master data can be distributed (for example, material sales data, material purchase data). Each view of the master data is stored in a separate message type.
Users can specify which data elements in a master record are to be distributed.
Various distribution strategies are supported:
· Cross-system master data can be maintained centrally and then distributed. The final values are assigned locally.
· A view of the master data can be maintained locally. In this case there is always one maintenance system for each view. After the master data has been maintained it is transferred to a central SAP system and distributed from there.
· Active distribution (PUSH)
If the master data is changed (for example, new data, changes or deletions), a master data IDoc is created in the original system and is distributed by class as specified in the distribution model.
· Requests (PULL)
A request occurs when a client system needs information about master data held in the system. You can select specific information about the master data, for example, the plant data for a material.
If you want to be notified of all subsequent changes to the master data, this has to be set up “manually” between the two systems. It is not yet possible for this to be done automatically in the distribution mechanism in the original system.
A distinction is made between transferring the entire master data and transferring only changes to the master data.
If the entire master data is transferred, a master IDoc is created for the object to be distributed in response to a direct request from a system. Only the data that was actually requested is read and then sent. The customer specifies the size of the object to be distributed in a request report.
If only changes are transferred, the master IDoc is created based on the logged changes.