A master data management system and master data management method

Abstract

The application discloses a master data management system and a master data management method. The master data management system comprises a background storage system and at least one front-end business system. The background storage system receives first standardized master data of the front-end business system through an input interface, approves and stores the first standardized master data. The front-end business system uses second standardized master data in the background storage system through an output interface of the background storage system. Different front-end business systems set different personalized approval processes and personalized interactive interfaces according to business requirements. In the application, the background storage system stores master data of each front-end business system as standardized master data after approving the master data through the personalized approval process. On this basis, each front-end business system calls the standardized master data of the background storage system and realizes utilization of the standardized master data through the personalized interactive interface, thereby realizing centralized management of master data and personalized processes of business systems.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and more specifically, to a master data management system and a master data management method. Background Technology

[0002] Master data is the foundational data of an enterprise, supporting its transactional data. Master data management involves integrating core and important shared data from multiple business systems within an enterprise, centrally organizing and standardizing the data, and ultimately maintaining and managing it through a master data management system for use by all business systems.

[0003] Traditional master data systems have two implementation methods:

[0004] 1. Centralized: Master data management for all business systems is centralized in a single system, implementing functions such as master data workflow approval, unified coding, data maintenance, and data distribution. Because a unified system is used to manage master data, it's difficult for the master data system to provide personalized management for different business systems' master data application scenarios. For example, the approval process for supplier master data differs from that for user master data, but a centralized master data system struggles to implement personalized processes for different business systems.

[0005] 2. Filing-based: The generation and approval of master data are implemented in different business systems, which then send the master data to the main data center platform. This approach allows for personalized master data management in each business system, but the drawback is the difficulty in achieving unified management on the main data center platform. For example, if you want to delete or deactivate a supplier, you need to do so in the supplier management system; you cannot operate on the supplier's data in the master data management system, otherwise, data inconsistencies may occur.

[0006] In summary, the disadvantage of "centralized" master data management is that it is not easy to achieve personalization, while the disadvantage of "filing-based" master data management is that it is difficult to centrally control. This poses a challenge to enterprises in truly making good use of the master data system.

[0007] In addition, traditional master data management systems typically use relational databases, which have certain limitations in horizontal scalability. Furthermore, relational databases are not efficient enough and have slow retrieval speeds when handling recursive relation retrieval and keyword full-text matching. Summary of the Invention

[0008] This application provides a master data management system and a master data management method. The back-end storage system approves the master data of each front-end business system through a personalized approval process and stores it as standardized master data. On this basis, each front-end business system calls the standardized master data of the back-end storage system and realizes the use of the standardized master data through a personalized interactive interface. This achieves both centralized management of master data and personalized processes of business systems.

[0009] This application provides a master data management system, including a back-end storage system and at least one front-end business system;

[0010] The back-end storage system receives the first standardized master data from the front-end business system through the input interface, and approves and stores the first standardized master data.

[0011] The front-end business system uses the second standardized master data in the back-end storage system through the output interface of the back-end storage system; different front-end business systems set up different personalized approval processes and personalized interactive interfaces according to business needs.

[0012] Preferably, each front-end business system has a first process engine, which includes a personalized approval process and a personalized master data approval form. The data structure information of the master data in the master data approval form is the same as the data structure information of the same type of master data in the back-end storage system.

[0013] Preferably, the data in the backend storage system is abstracted into entity data and relational data.

[0014] Preferably, the backend storage system includes a graph database and a search engine. The graph database stores entity data and relation data, while the search engine stores entity data.

[0015] Preferably, the backend storage system further includes an original database and a database change data capture module. The original database stores the first standardized master data, and the database change data capture module listens to the original database and obtains the first change data, and writes the first change data into an internal message queue.

[0016] Front-end business systems, graph databases, and search engines update their master data based on the first change in the internal message queue.

[0017] Preferably, the master data management system also includes a general front-end system for managing multiple business systems, the general front-end system having a second process engine that uses a standard approval process;

[0018] In a general front-end system, different business systems correspond to different domains, and each domain is managed independently.

[0019] Preferably, the background storage system listens to or periodically extracts second change data from business systems outside the master data management system or receives second change data through a data write interface, and updates its own master data based on the second change data.

[0020] This application also provides a master data management method based on a front-end business system, the master data management method including:

[0021] Call at least one form data, and the data structure information of the main data of the form data is the same as the data structure information of the same type of main data in the backend storage system;

[0022] Arrange at least one form of data according to business needs to form a personalized master data approval form;

[0023] Set up the master data approval process according to business needs to form a personalized approval workflow;

[0024] Upon receiving the master data to be updated, the system inputs the master data to be updated into the personalized master data approval form and initiates an approval request to the backend storage system according to the personalized approval process.

[0025] Preferably, the master data management method further includes:

[0026] Subscribe to or listen to the internal message queue of the backend storage system;

[0027] If there is third-party change data related to its own business in the internal message queue, then the master data is updated according to the third-party change data.

[0028] Preferably, personalized master data approval forms and / or personalized approval processes are assembled by dragging and dropping.

[0029] Other features and advantages of this application will become clear from the following detailed description of exemplary embodiments with reference to the accompanying drawings. Attached Figure Description

[0030] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments of the present application and, together with their description, serve to explain the principles of the present application.

[0031] Figure 1 A schematic diagram of the master data management system provided in this application;

[0032] Figure 2 A schematic diagram of the structure of an example of the master data management system provided in this application;

[0033] Figure 3 An example of master data in the back-end storage system provided in this application;

[0034] Figure 4 A flowchart of the master data management method provided for this application. Detailed Implementation

[0035] Various exemplary embodiments of the present application will now be described in detail with reference to the accompanying drawings. It should be noted that, unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps set forth in these embodiments do not limit the scope of the present application.

[0036] The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit the scope of this application and its application or use.

[0037] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, they should be considered part of the specification.

[0038] In all the examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values.

[0039] This application provides a master data management system and a master data management method. The back-end storage system approves the master data of each front-end business system through a personalized approval process and stores it as standardized master data. On this basis, each front-end business system calls the standardized master data of the back-end storage system and realizes the use of the standardized master data through a personalized interactive interface. This achieves both centralized management of master data and personalized processes of business systems.

[0040] like Figure 1 As shown, the master data management system includes a back-end storage system 110 and at least one front-end business system 120.

[0041] The backend storage system 110 includes an input interface and an output interface. The backend storage system 110 receives the first standardized master data from the frontend business system 120 through the input interface, and approves and stores the first standardized master data.

[0042] In the backend storage system 110, each type of master data needs to have its data structure information predefined and saved. This data structure information includes field names, field types, whether null values ​​are allowed, whether the data is user-entered, the value range, and whether it is a nested field. Therefore, the data structure information for each type of master data is consistent.

[0043] As an example, the data within the backend storage system is abstracted into entity data and relational data. Please refer to [link / reference]. Figure 2As one example, the backend storage system includes a raw database, a database change data capture module, a graph database, and a search engine. The raw database stores the first standardized master data, and the database change data capture (CDC) module... Figure 2 The CDC software (shown in the image) listens to the original database and obtains the first changed data, then writes this data to an internal message queue. Front-end business systems 120, the graph database, the search engine, and external business systems update their own master data based on the first changed data in the internal message queue. For example: Please refer to... Figure 2 Data lake applications can monitor changes to master data and input the updated master data into the data lake for data quality checks.

[0044] Specifically, the graph database stores entity data and relationship data, while the search engine stores entity data. Master data is stored as "entities" in the graph database's "nodes" and in the search engine's "documents," ensuring a consistent data storage method across different business scenarios and facilitating unified maintenance and management. Relationships between master data are stored as "edges" between nodes in the graph database, enabling fast recursive relationship retrieval.

[0045] In this embodiment, both the graph database and the search engine have horizontal scalability. The graph database supports the setting and retrieval of complex relationships. Using a clustered graph database such as Nebula can ensure good performance and functional scalability, and can support billions or even tens of billions of data points. Using a search engine such as Elasticsearch can support billions or even tens of billions of document retrievals.

[0046] The front-end business system 120 directly accesses the back-end storage system 110 and uses the second standardized master data within the back-end storage system 110 through its output interface to implement its business functions. Different front-end business systems have different personalized interactive interfaces set up according to their business needs. Different front-end business systems 120 have different personalized approval processes set up according to their business needs.

[0047] Based on the data architecture of the backend storage system, each frontend business system 120 customizes a frontend application according to actual business needs. This application is only used to implement different personalized display and management needs and different frontend interaction interfaces under different business scenarios. All frontend business systems 120 use the unified data architecture of the backend storage system to store and manage master data. For example, for user-type master data, a user self-service portal is usually required. For example, users can log in to the frontend application to modify their basic information (such as phone number, education, work experience, etc.), submit departmental change applications themselves or have their organizational administrators submit them, and have the human resources department submit resignation applications, etc., to realize the input of user-type master data to be updated; for supplier-type master data, after the supplier passes the bidding process, the staff of the material procurement department need to enter the supplier's basic information. After approval, the supplier master data becomes effective. Suppliers can modify their basic information, such as company case and product range, through the self-service portal to realize the input of supplier-type master data to be updated.

[0048] After receiving the master data to be updated, the front-end business system 120 initiates an approval application to the back-end storage system 110 through a personalized approval process. After the back-end storage system 110 approves the application, it stores the master data to be updated in the back-end storage system 110.

[0049] Specifically, each front-end business system 120 has a first process engine, which includes the aforementioned personalized approval process and personalized master data approval form. The data structure information of the master data in the master data approval form is the same as the data structure information of similar master data in the back-end storage system 110. The master data in the master data approval form uses the data structure information of similar master data in the back-end storage system 110. As an example, the form data is automatically generated based on the data structure of the master data in the back-end storage system 110.

[0050] The arrangement of form data and approval processes can be customized by dragging and dropping according to the needs of different business scenarios, so as to achieve assembly and ultimately form personalized master data approval forms and / or personalized approval processes.

[0051] Front-end forms can be dynamically generated by predefined form data formats without modifying the source code. Using the workflow engine and forms, the approval process for master data can be quickly customized in a low-code manner. After the user creates master data and it is approved, the master data can be stored in the back-end storage system, improving the efficiency of customized approval processes.

[0052] In most cases, the differences in master data management between different business systems lie in the approval processes. Maintaining and managing master data for different users, suppliers, and products requires different approval processes. By using the aforementioned process engine, the configurability and customization capabilities of the processes can be enhanced. Business personnel can flexibly define approval forms and processes, significantly reducing the workload of adding new master data management processes.

[0053] Preferably, such as Figure 1 As shown, the master data management system also includes a general front-end system 130 for managing multiple business systems. The general front-end system 130 has a second process engine that uses standard approval processes. In the general front-end system 130, different business systems correspond to different domains, and different domains are managed independently.

[0054] Preferably, considering that the master data management system may not cover certain business systems, a temporary "filing-based" master data management method is used to manage these uncovered business systems. The backend storage system 110 listens for or periodically extracts second change data from business systems outside the master data management system (i.e., those not registered in the master data management system of this application), or receives second change data through a data write interface, and updates its own master data based on the second change data.

[0055] Based on the above explanation, Figure 2 and 3 One example is shown. Figure 3 This demonstrates the characteristics of master data in a backend storage system. The master data comprises four main categories: user master data (including organizational structure and users), product master data (including product categories and products), supplier master data (including supplier categories, suppliers, and supplier contracts), and store master data (including store categories, stores, and store business scope). This data is stored in the same graph database. Different types of master data can have interrelationships. For example, a user might be an administrator for a major product category, and products might belong to multiple different product categories; a supplier might have signed multiple supply contracts, and each supply contract might involve the supply of one or more products.

[0056] Figure 2The structure of the data management system in this example is illustrated. The backend storage system uses a unified graph database and search engine to store master data. The data structure information of the master data is standardized, specifying which fields each type of master data includes, their names, data types, value ranges, whether null values ​​are allowed, whether users are allowed to fill in the field, whether they are nested fields, and their parent fields. This data structure information facilitates the dynamic generation of forms on the front end and the validation of input data. User master data, product master data, supplier master data, and store master data all share the same backend data storage, namely the graph database and search engine of the backend storage system. All master data storage uses a unified "entity" and "relationship" system.

[0057] Preferably, in order to distinguish different master data types, a data type description field can be added to the nodes in the graph database and search engine to indicate the type of master data (product, user, organization, or others).

[0058] Since both graph databases and search engines support dynamically adding attribute fields to nodes or documents, other attribute fields of the master data can be added dynamically.

[0059] Graph databases can be used to efficiently retrieve data with recursive relationships. For example, retrieving all goods and all types of goods that a supplier has ever supplied through contracts can be achieved with a very simple query in a graph database.

[0060] like Figure 2 As shown, the data management system includes two custom-developed front-end business systems: "User Center" and "Product Center". These two front-end business systems embed or share a process engine, and implement customized management logic and user interface for two different business scenarios: "User Management" and "Product Management".

[0061] The User Center is used specifically for managing users and organizations. Customizations available for user-specific master data management within the User Center include: 1. A user self-service platform where users can modify their own data; modifications to certain critical information, such as the user's organizational affiliation, require administrator approval; 2. User access control, where administrators can authorize users to access certain business systems. This authorization information is pushed to a message queue for processing by the relevant business systems.

[0062] The Product Center is used to manage master data related to products. Customization options available for master data management in the Product Center include: 1. Initial Product Sales Process: Some products require an initial sales process before being added to the master data system. This includes processes such as qualification verification of manufacturers and suppliers, bank account opening, submission of approvals to relevant government departments, and filing of quality-related materials; 2. Hierarchical Product Management: For large group enterprises, different legal entities or branches may have different product management permissions, and the product management processes for different branches and with different attributes may vary.

[0063] The data management system also includes a general front-end business system—the "Master Data Center." For business systems that haven't been customized, users can use the "Master Data Center" to manage master data. For example, since a "Store Center," a front-end business system customized for store management, doesn't currently exist, the "Master Data Center" can be used temporarily to manage store-related master data. Similarly, supplier-related master data can also be managed through the "Master Data Center." Supplier-related master data and store-related master data are divided into different "domains." The "Master Data Center" uses standard approval processes and standard pages for viewing and managing master data. The management of the Master Data Center is domain-based; that is, users need to switch between managing supplier and store master data, and can only manage master data from one domain at a time.

[0064] Through approval forms and workflow engines, front-end business systems such as the user center, product center, and main data center can read and modify the master data.

[0065] Based on the aforementioned data management system, this application also provides a master data management method based on a front-end business system. For example... Figure 4 As shown, the master data management methods include:

[0066] S410: Call at least one form data, the data structure information of the main data of the form data is the same as the data structure information of the same type of main data in the backend storage system.

[0067] S420: Arrange at least one form data according to business needs (e.g., by dragging and dropping) to form a personalized master data approval form.

[0068] S430: Set up the master data approval process according to business needs to form a personalized approval process.

[0069] S440: In response to receiving the master data to be updated, the master data to be updated is entered into the personalized master data approval form, and an approval request is sent to the back-end storage system according to the personalized approval process.

[0070] Preferably, the master data management method further includes:

[0071] P1: Subscribe to or listen to the internal message queue of the background storage system.

[0072] P2: If there is third-party change data related to its own business in the internal message queue, then update its own master data according to the third-party change data.

[0073] This application uses a unified data architecture (back-end storage system) to store all master data-related information, centrally storing and managing data to facilitate standardized practices. While conforming to the processes of the front-end business departments, the unified master data structure and access methods maximize the commonality of master data management, avoiding personalized customization of the back-end data storage structure, reducing the cost of back-end customization, and achieving data structure sharing, basic master data management process sharing, and unified master data storage and usage standards. This solves the problems of "centralized" master data systems struggling to achieve personalization and "registration-based" master data systems finding it difficult to achieve centralized master data management and maintenance.

[0074] While specific embodiments of this application have been described in detail by way of examples, those skilled in the art should understand that the above examples are for illustrative purposes only and are not intended to limit the scope of this application. Those skilled in the art should understand that modifications can be made to the above embodiments without departing from the scope and spirit of this application. The scope of this application is defined by the appended claims.

Claims

1. A master data management system, characterized in that, Includes a backend storage system and at least one frontend business system; The backend storage system receives the first standardized master data from the frontend business system through an input interface, approves and stores the first standardized master data. The backend storage system also includes an original database and a database change data capture module. The original database stores the first standardized master data, and the database change data capture module listens to the original database and obtains the first change data, and writes the first change data into an internal message queue. The backend storage system includes a graph database and a search engine. The graph database stores entity data and relationship data, and the search engine stores entity data. The front-end business system, the graph database, and the search engine update their own master data based on the first changed data in the internal message queue. Each front-end business system has a first process engine, which includes a personalized approval process and a personalized master data approval form. The first process engine customizes the arrangement of form data and approval process through drag-and-drop according to the needs of different business scenarios, and assembles them to finally form a personalized master data approval form and / or a personalized approval process. The master data in the personalized master data approval form uses the data structure information of the same type of master data in the back-end storage system, and the data structure information of the master data in the personalized master data approval form is the same as the data structure information of the same type of master data in the back-end storage system. The front-end business system uses the second standardized master data in the back-end storage system through the output interface of the back-end storage system; different front-end business systems set up different personalized approval processes and personalized interactive interfaces according to business needs.

2. The master data management system according to claim 1, characterized in that, The data in the backend storage system is abstracted into entity data and relational data.

3. The master data management system according to claim 1, characterized in that, It also includes a general front-end system for managing multiple business systems, the general front-end system having a second process engine that uses standard approval processes; In the general front-end system, different business systems correspond to different domains, and each domain is managed independently.

4. The master data management system according to claim 2, characterized in that, The background storage system listens to or periodically extracts second change data from business systems outside the master data management system, or receives the second change data through a data writing interface, and updates its own master data based on the second change data.

5. A master data management method, based on a front-end business system included in the master data management system according to any one of claims 1 to 4, characterized in that, The master data management method includes: Call 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 type of main data in the backend storage system; Arrange at least one form data according to business needs to form a personalized master data approval form; The approval process for master data is set up according to business needs to form a personalized approval process, wherein the personalized master data approval form and / or the personalized approval process are assembled by dragging and dropping. In response to receiving the master data to be updated, the master data to be updated is entered into the personalized master data approval form, and an approval request is initiated to the backend storage system according to the personalized approval process, wherein, Subscribe to or listen to the internal message queue of the background storage system; If there is third change data related to its own business in the internal message queue, then the master data is updated according to the third change data.

Images