Leading system
A system in a system group is referred to as a leading system and the other systems are based on its information.
The term leading system is widely used in software systems integration , but it can also be used in other areas of integration . For this it is not absolutely necessary that these systems are technically interconnected. They can also be organizationally linked, for example one system for invoicing and one system for shipping processing. A system can also be a filing system, for example paper shipping instructions with addresses. The core idea is that the relevant information, in the above examples the address details (invoice and shipping), is required by several systems. The information can then be redundant (in copy) or as a reference (for example "see invoice XY"). However, only the information from the system responsible for this information is assumed to be correct.
The term only makes sense if several systems are considered in which the same information is used (e.g. address data) or information is derived (e.g. shipping only possible when invoice has been issued or prepayment has been made).
Depending on the information, there can be several leading systems in a system group, that is, one system can be leading for information A while another system can be leading for information B. Conversely, however, usually only one system is in charge of information.
The concept of the leading system arose from the problem of determining the source of information in system networks in which information is present or required more than once, which information can be assumed to be correct or original, for example.
Example: A customer places an order by specifying his address in a web shop (system A). The information is stored in the database A. In the order processing system (system B) these data are generated as an order in the database B. An employee in order processing recognizes an error in the address, checks the address and corrects it in system A. There is a difference between the data in database A and database B here. Another system can be used for dispatch (system C). At this point it must already be clarified which system (A or B or C) is leading. Does C get its data from A or B?
"Leading system" is the most frequently used procedure for master data distribution in practice: One of the existing systems is defined as the leading system for a master data class and is therefore the starting point for the distribution to the other systems, which are asynchronous either in push or pull -Procedure can be done. The initial creation of the master data takes place in the leading system with the attributes available there.
Application example
In the specific case of Customer Relation Management (CRM) at SAP , it is the system in a mySAP.com system landscape that always contains the latest document, application and customizing information. When data is exchanged in a CRM system landscape with CRM Mobile, CRM Online and SAP R / 3, CRM Online is the leading system and has master data sovereignty.
literature
- Loser, Cornel, Legner, Christine, Gizanis, Dimitrios: Master Data Management for Collaborative Service Processes . In: Chen, Jian (Ed.): International Conference on Service Systems and Service Management 2004 . Tsinghua University Beijing, 2004.
Individual evidence
- ↑ Master data management . joint script by Dr. Christine Legner, HEC Lausanne, and Dr. Boris Otto, TU Dortmund ( Memento of the original from October 21, 2014 in the Internet Archive ) Info: The archive link was inserted automatically and has not yet been checked. Please check the original and archive link according to the instructions and then remove this notice.
- ^ Glossary of the SAP library at the University of Heidelberg
