The primary assumption in MDMS is that data flow is managed only from the headquarters to a local company, not vice versa.
It is not permitted to create a data item locally even if it is urgent. The request from a subsidiary to create a data item should be submitted to the headquarters. Despite the time pressure, this rule should be observed.
The process of creating a new data item at the headquarters involves also scanning for changes and replicating new data items in the incremental mode to local companies. This definitely takes longer than just opening a card and creating a data item locally. However, the benefit is data consistency.
As recently many improvements have been implemented for faster scanning for changes, the creation and replication of new data items has been shortened to 5-10 minutes, which is a good result. To speed up the process, it is possible to develop an extra solution using Web services.
Indeed, to respond to users’ claims about time pressure and more flexible flow of data, a global/group organisation should focus on developing policies that prevent situations when it becomes critical to create urgently a data item at a local level. If proper procedures are implemented, creating data solely at the headquarter level, taking into account the time needed, becomes the best practise which is accepted and applied across the entire organisation.