CN-115827628-B - Main data management system and main data management method
Abstract
The application discloses a main data management system and a main data management method, wherein the main data management system comprises a background storage system and at least one front-end service system, the background storage system receives first standardized main data of the front-end service system through an input interface, the first standardized main data is approved and stored, the front-end service system uses second standardized main data in the background storage system through an output interface of the background storage system, and different front-end service systems set different personalized approval flows and personalized interaction interfaces according to service requirements. In the application, the background storage system examines and approves the main data of each front-end service system through the personalized examination and approval process and stores the main data as the standardized main data, and on the basis, each front-end service system calls the standardized main data of the background storage system and realizes the utilization of the standardized main data through the personalized interactive interface, thereby realizing the centralized management of the main data and the personalized process of the service system.
Inventors
- LIU QIYAN
- LIU HAIEN
- TANG JUN
- YANG FAN
- LI XINMING
- YU YANG
- YANG CHUANZHEN
- WANG JIASHOU
- LI LIGANG
- TANG JUN
- TAO GANG
- GAN ZHIXIONG
- LI ZHONGTAI
Assignees
- 云南中烟工业有限责任公司
Dates
- Publication Date
- 20260508
- Application Date
- 20221130
Claims (5)
- 1. The main data management system is characterized by comprising a background storage system and at least one front-end service system; The background storage system receives first standardized main data of the front-end service system through an input interface, approves and stores the first standardized main data, wherein the background storage system further comprises an original database and a database change data grabbing module, the original database stores the first standardized main data, the database change data grabbing module listens to the original database and obtains first change data, and the first change data is written into an internal message queue; the background storage system comprises a graph database and a search engine, wherein entity data and relation data are stored in the graph database, and entity data are stored in the search engine; The front-end business system, the graph database and the search engine update own main data according to first change data in the internal message queue, each front-end business system is provided with a first flow engine, the first flow engine comprises a personalized approval flow and a personalized main data approval form, the first flow engine self-defines form data and an arrangement mode of the approval flow in a dragging mode according to the requirements of different business scenes, and realizes assembly to finally form the personalized main data approval form and/or the personalized approval flow, wherein the main data in the personalized main data approval form uses data structure information of the same type of main data in the background storage system, and the data structure information of the main data in the personalized main data approval form is the same as the data structure information of the same type of main data in the background storage system; the front-end business system uses the second standardized main data in the background storage system through the output interface of the background storage system, and different front-end business systems set different personalized approval flows and personalized interaction interfaces according to business requirements.
- 2. The primary data management system of claim 1, wherein the data within the background storage system is abstracted into entity data and relationship data.
- 3. The primary data management system of claim 1, further comprising a generic front-end system for managing a plurality of business systems, the generic front-end system having a second flow engine that uses standard approval flows; In the general front-end system, different service systems correspond to different domains and perform independent management on the different domains.
- 4. The primary data management system of claim 2, wherein the background storage system listens to or periodically extracts second change data of a service system other than the primary data management system or receives the second change data through a data writing interface, and updates its own primary data according to the second change data.
- 5. A main data management method based on the front-end service system included in the main data management system according to any one of claims 1 to 4, wherein the main data management method includes: Invoking at least one form data, wherein the data structure information of the main data of the form data is the same as the data structure information of the same kind of main data in a background storage system; arranging the at least one form data according to the service requirement to form a personalized main data approval form; Setting an approval process of main data according to business requirements to form a personalized approval process, wherein the personalized main data approval form and/or the personalized approval process are assembled in a dragging mode; responding to the received main data to be updated, inputting the main data to be updated into the personalized main data approval form, and initiating an approval request to the background storage system according to the personalized approval process, wherein, Subscribing or monitoring an internal message queue of the background storage system; if the third change data related to the self business exists in the internal message queue, the self main data is updated according to the third change data.
Description
Main data management system and main data management method Technical Field The present application relates to the field of data processing technologies, and in particular, to a main data management system and a main data management method. Background The main data is basic data of an enterprise, and plays a supporting role on transactional data of the enterprise. The main data management is to integrate the core and important shared data in a plurality of business systems in an enterprise, intensively arrange and normalize the data, and finally maintain and manage the data through a main data management system for each business system to use. There are two implementations of conventional primary data systems: 1. the main data management of each business system is centralized in the same system, namely, the functions such as main data flow approval, unified coding, data maintenance, data distribution and the like are realized in the system. Because the unified system is used for managing the main data, the main data system is difficult to perform personalized management aiming at the main data application scenes of different service systems, for example, the auditing flow of the main data of the provider is different from the auditing flow of the main data of the user, but the centralized main data system is difficult to realize the personalized flow of the different service systems. 2. And the record type is that the generation and approval of the main data are realized in different service systems, and then the service systems send the main data to a main data center platform. This approach allows personalized primary data management in each business system, but has the disadvantage that unified management is difficult to achieve on the primary data center platform. For example, if a vendor is to be deleted or deactivated, this operation needs to be performed in the vendor management system, the vendor data cannot be operated on in the master data management system, otherwise the data may be inconsistent. In summary, the disadvantage of "centralized" master data management is that personalization is not easily achieved, and the disadvantage of "docket" master data management is that centralized management is difficult, which presents challenges to the enterprise in truly functioning a live master data system. In addition, the traditional main data management system generally uses a relational database, which has a certain limitation on lateral expansibility, and has the defects of insufficient efficiency and insufficient retrieval speed in the aspects of processing recursive relation retrieval and keyword full text matching. Disclosure of Invention The application provides a main data management system and a main data management method, a background storage system examines and approves main data of each front-end service system through a personalized examination and approval process and stores the main data as standardized main data, on the basis, the front-end service system calls the standardized main data of the background storage system and realizes the utilization of the standardized main data through the personalized interactive interface, thereby realizing the centralized management of the main data and the personalized flow of the service system. The application provides a main data management system, which comprises a background storage system and at least one front-end service system; The background storage system receives first standardized main data of the front-end service system through an input interface, and approves and stores the first standardized main data; The front-end service system uses the second standardized main data in the background storage system through the output interface of the background storage system, and different front-end service systems set different personalized approval flows and personalized interaction interfaces according to service requirements. Preferably, each front-end service system is provided with a first flow engine, the first flow engine comprises a personalized approval flow and a personalized main data approval form, and the data structure information of the main data in the main data approval form is the same as the data structure information of the same kind of main data in the background storage system. Preferably, the data within the background storage system is abstracted into entity data and relationship data. Preferably, the background storage system comprises a graph database and a search engine, wherein entity data and relation data are stored in the graph database, and entity data are stored in the search engine. Preferably, the background storage system further comprises an original database and a database change data grabbing module, wherein the original database stores first standardized main data, the database change data grabbing module listens to the original database and obtains first change data, and the first change data is writte