Master data management system under multi-data source scene

Abstract

The invention discloses a master data management system in a multi-data source scene, and relates to the technical field of master data management.According to the master data management system, a multi-source receiving module is arranged to collect corresponding service data from multiple service systems in real time, and a data integration unit periodically integrates the collected service data; the master data management unit generates a master data verification sequence according to the master data generated after integration; according to the method, a plurality of regular integer groups obtained by grouping main data are independently processed, for any regular integer group, the number of digits of a character 1 is counted so as to determine a derivative array of the regular integer group, a non-'0' character on the right side of a decimal point of a regular correction group is extracted to determine a conversion array, and finally the derivative array and the conversion array are combined so as to obtain a conversion result. Therefore, the verification array of each regular integer group is determined, the possibility of coupling collision in the data verification process can be effectively reduced, the credibility of the data verification result is enhanced, and the risk of data management of an enterprise is reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of master data management, and in particular to a master data management system in a multi-data source scenario. Background Art

[0002] In the operation process of modern enterprises, with the widespread application of information technology, there are usually multiple business systems with different functions within the enterprise. These systems include enterprise resource planning (ERP) systems, customer relationship management (CRM) systems, sales systems, procurement systems, production systems, financial systems, etc. Each business system continuously generates a large amount of business data in its specific business process; As businesses continue to expand and deepen, these multi-source business data are experiencing explosive growth, and the relationships between data are becoming increasingly complex. To better inform decision-making, optimize business processes, and improve operational efficiency, businesses need to integrate these business data from different systems into master data. Master data, as key data for core business entities, can provide a unified and accurate view of information. However, the process of integrating business data from multiple systems into master data and its subsequent use presents numerous challenges, particularly data consistency. Data in different business systems may be updated and modified at different times and by different operators, and each system may differ in data storage format, accuracy, and encoding. This can easily lead to inconsistencies in master data after integration. Such inconsistencies can cause serious problems across the enterprise's various business processes, such as data errors in financial report generation, inaccurate inventory information leading to stockouts or backlogs in supply chain management, and inconsistent customer information affecting service quality in customer relationship management. These issues can impact the enterprise's overall operational efficiency and the accuracy of its decisions. To address the consistency issue of master data, a message digest algorithm is currently often used to process the integrated master data. The message digest algorithm performs specific calculations on the data content to generate a fixed-length digest value. When the data remains unchanged, the digest value calculated each time is the same; however, when the data is modified, the digest value changes. In this way, data consistency can be verified to a certain extent. Currently, the MD5 algorithm is a classic and widely used message digest algorithm. The MD5 algorithm can convert data of any length into a 128-bit digest value. In the early practice of master data management, the MD5 algorithm was widely used for data consistency verification. However, with the development of technology and the increasing requirements for data security and accuracy, the MD5 algorithm has gradually exposed some problems. The MD5 algorithm has the possibility of collision, that is, different data may generate the same MD5 value. This leads to the possibility of misjudgment when using the MD5 value as the basis for data consistency verification. For example, if the master data undergoes a slight change, but the MD5 value does not change due to the collision problem, the data inconsistency cannot be accurately detected, which brings potential risks to the enterprise's data management. In order to solve the above problems, the present invention proposes a solution. Summary of the Invention

[0003] The purpose of the present invention is to provide a master data management system in a multi-data source scenario in order to solve the problems raised in the above background technology; The purpose of the present invention can be achieved through the following technical solutions: A master data management system in a multi-data source scenario includes: Multi-source receiving module, used to collect corresponding business data from several business systems in real time; Data integration unit, used for temporarily storing all received business data; The data integration unit is further configured to perform data cleaning, data conversion, data fusion and data matching operations on all business data temporarily stored in the integration period at intervals of each integration period to obtain master data of the integration period; The master data management unit is configured to generate a master data verification sequence for an integration period according to a preset generation rule after receiving the master data for the integration period.

[0004] Furthermore, the business system includes sales system, procurement system, production system and financial system.

[0005] Furthermore, it is characterized in that the generation rule of the master data verification sequence for one integration cycle is as follows: S11: performing binary conversion on the master data, and marking the converted binary data as data to be regularized; S12: From left to right, take every four characters as a regular integer group, and obtain a plurality of regular integer groups from the data to be regularized. According to the position of each regular integer group in the data to be regularized, mark all the regular integer groups in sequence from left to right as A1, A2, ..., Aa, where a ≥ 1; S13: Concatenate the regular integer group A1 and the character string "0." to obtain a regular correction group B1, wherein the character string "0." is concatenated at the leftmost end. For example, if the regular integer group A1 is 0001, the regular correction group B1 is 0.0001; S14: generating a derivative array D1 of the regularized correction group B1 according to a preset derivative rule; S15: Obtain the decimal number of the derivative array D1 of the regularization and correction group B1 to obtain the derivative number E1 of the regularization and correction group B1; S16: Generate a conversion array of the regularization correction group B1 according to a preset cutting generation rule; S17: performing an AND operation on the start identifier of the regularization and correction group B1 and the derived array D1 to obtain a check array of the regularization and correction group B1; S18: Obtain regularized and modified groups B2, B3, ..., Ba in sequence according to S13, and obtain parity check arrays of regularized and modified groups B2, B3, ..., Ba in sequence according to S14 to S17; S19: According to the order of the regularized correction groups B1, B2, ..., Ba, the corresponding check arrays are spliced to obtain the main data check sequence of the integration period.

[0006] Furthermore, after generating a master data verification sequence for an integration period, the master data management unit stores the master data for the integration period and the master data verification sequence thereof.

[0007] Beneficial effects of the present invention: The present invention provides a multi-source receiving module to collect corresponding business data from multiple business systems in real time, and provides a data integration unit that periodically integrates and processes the collected business data to obtain corresponding master data. In addition, a master data management unit is provided to generate a corresponding master data verification sequence based on the master data generated after integration. In the process of generating the main data verification sequence, the present invention independently processes several regular integer groups obtained from the main data grouping. For any regular integer group, its regular correction group is first analyzed. Specifically, the number of bits that are "1" characters is counted to determine its derivative array, and the non-"0" characters to the right of the decimal point of the regular correction group are extracted to determine the conversion array. Finally, the derivative array and the conversion array are combined to determine the verification array of each regular integer group. In this way, the possibility of coupling collision in the data verification process can be effectively reduced, the credibility of the data verification results can be enhanced, and the risk of enterprise data management can be reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] The present invention will be further described below with reference to the accompanying drawings.

[0009] Figure 1 It is a system block diagram of the present invention. DETAILED DESCRIPTION

[0010] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making any creative efforts shall fall within the scope of protection of the present invention.

[0011] like Figure 1 As shown, a master data management system in a multi-data source scenario includes a multi-source receiving module and a master data control module; The multi-source receiving module is used to collect corresponding business data from several business systems and transmit it to the master data management and control module. In this application, the business systems include the sales system, procurement system, production system and financial system. In this application, the business data of the sales system includes but is not limited to order data of sales products, customer information data, sales product data, salesperson data, promotion and discount data, etc. The business data of the procurement system includes but is not limited to supplier data, purchase order data, inventory data, cost data, and purchase contract data; the business data of the production system includes but is not limited to production plan data, production equipment data, production personnel data, and product quality inspection data; the business data of the financial system includes but is not limited to financial statement data, financial budget data, cost accounting data, and asset management data; A master data control module is used to integrate and securely manage a number of business data. The master data control module includes a data integration unit and a master data management unit. After receiving a number of business data, the master data control module transmits it to the data integration unit. After receiving the transmitted business data, the data integration unit temporarily stores the business data, and performs data cleaning, data conversion, data fusion, and data matching operations on all business data stored in the integration cycle at intervals of each integration cycle to obtain master data of the integration cycle, and transmits the master data to the master data management unit. In this application, the process of performing data cleaning, data conversion, data fusion, and data matching operations on the business data to obtain master data uses a data integration processing algorithm; After receiving the transmitted master data of the integration period, the master data management unit generates the master data verification sequence of the integration period according to the preset generation rules. The generation rules are as follows: S11: performing binary conversion on the master data, and marking the converted binary data as data to be regularized; S12: From left to right, take every four characters as a regular integer group, and obtain a plurality of regular integer groups from the data to be regularized. According to the position of each regular integer group in the data to be regularized, mark all the regular integer groups in sequence from left to right as A1, A2, ..., Aa, where a ≥ 1; S13: Concatenate the regular integer group A1 and the character string "0." to obtain a regular correction group B1, wherein the character string "0." is concatenated at the leftmost end. For example, if the regular integer group A1 is 0001, the regular correction group B1 is 0.0001; S14: Generate a derivative array D1 of the regularized correction group B1 according to a preset derivative rule. The derivative rule is as follows: S141: Obtain the number of digits of the first character that is "1" from the regular integer group A1 in order from right to left, and use the number of digits as the carry identifier C1 of the regularization and correction group B1. It should be noted that if all characters in the regular integer group A1 are "0", the carry identifier C1 of the regularization and correction group B1 is 2; In this application, for all characters constituting any regular integer group, from left to right, the number of digits of the characters is 1, 2, 3, and 4 respectively; S142: According to the carry C1 of the regularization correction group B1, obtain the character D1 located at the C1-1 position from the regularization correction group B1, and perform a non-zero judgment on D1. If the character D1 is 1, then all the characters after C1 in the regularization correction group B1 are removed to obtain the derivative array D1 of the regularization correction group B1. Otherwise, the character located at C1-1 in the regularization correction group B1 is modified to "1", and the character located at C1 in the regularization correction group B1 is modified to "0" to obtain the derivative array D1 of the regularization correction group B1. In this application, the number of digits of the characters to the right of the decimal point in the regularization correction group is 1, 2, 3, and 4 from left to right. S15: Obtain the decimal number of the derivative array D1 of the regularization and correction group B1 to obtain the derivative number E1 of the regularization and correction group B1; S16: Generate a conversion array of the regularized correction group B1 according to a preset cutting generation rule. The cutting generation rule is as follows: S161: Remove "0." from the derived base number E1 of the regularization and correction group B1, then traverse the remaining data, obtain the first character that is not 0 from left to right, and use the character as the starting identifier of the regularization and correction group B1; S162: extracting all characters after the start identifier of the regularization and correction group B1 from the derived base number E1 of the regularization and correction group B1, and concatenating all the extracted characters in the order of extraction to obtain a positive identifier sequence of the regularization and correction group B1; S163: performing binary conversion on the positive identification sequence of the regularized and modified group B1 to obtain a conversion array of the regularized and modified group B1; It should be noted here that the starting identifier of the regularization and correction group B1 is included in the extraction process, and the starting identifier of the regularization and correction group B1 is extracted first; S17: performing an AND operation on the start identifier of the regularization and correction group B1 and the derived array D1 to obtain a check array of the regularization and correction group B1; S18: Obtain regularized and modified groups B2, B3, ..., Ba in sequence according to S13, and obtain parity check arrays of regularized and modified groups B2, B3, ..., Ba in sequence according to S14 to S17; S19: in the order of the regularized correction groups B1, B2, ..., Ba, the corresponding check arrays are spliced to obtain the master data check sequence of the integration period; The master data management unit stores the master data and master data verification sequence of the integration period to facilitate subsequent verification and comparison; Throughout the specification, references to terms such as "one embodiment," "example," or "specific example" indicate that the specific features, structures, materials, or characteristics described in conjunction with that embodiment or example are included in at least one embodiment or example of the present invention. In this specification, schematic representations of these terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

[0012] The above contents are merely examples and explanations of the present invention. Those skilled in the art may make various modifications or additions to the described specific embodiments or replace them in similar ways. As long as they do not deviate from the invention or exceed the scope defined by the claims, they should all fall within the scope of protection of the present invention.

[0013] The above is a detailed description of an embodiment of the present invention. However, the content described is only a preferred embodiment of the present invention and should not be considered to limit the scope of the present invention. All equivalent changes and improvements made within the scope of the present invention should still fall within the scope of the patent coverage of the present invention.

Claims

1. A master data management system in a multi-data source scenario, characterized by: include: Multi-source receiving module, used to collect corresponding business data from several business systems in real time; Data integration unit, used for temporarily storing all received business data; The data integration unit is further configured to perform data cleaning, data conversion, data fusion and data matching operations on all business data temporarily stored in the integration period at intervals of each integration period to obtain master data of the integration period; The master data management unit is configured to generate a master data verification sequence for an integration period according to a preset generation rule after receiving the master data for the integration period.

2. A master data management system in a multi-data source scenario according to claim 1, characterized in that: Business systems include sales systems, procurement systems, production systems and financial systems.

3. The master data management system in a multi-data source scenario according to claim 1, characterized in that: The rules for generating a master data verification sequence for an integration cycle are as follows: S11: performing binary conversion on the master data, and marking the converted binary data as data to be regularized; S12: From left to right, take every four characters as a regular integer group, and obtain a plurality of regular integer groups from the data to be regularized. According to the position of each regular integer group in the data to be regularized, mark all the regular integer groups in sequence from left to right as A1, A2, ..., Aa, where a ≥ 1; S13: Concatenate the regular integer group A1 and the character string "0." to obtain the regular correction group B1, wherein the character string "0." is concatenated at the leftmost end. For example, if the regular integer group A1 is 0001, the regular correction group B1 is 0.0001; S14: generating a derivative array D1 of the regularized correction group B1 according to a preset derivative rule; S15: Obtain the decimal number of the derivative array D1 of the regularization and correction group B1 to obtain the derivative number E1 of the regularization and correction group B1; S16: Generate a conversion array of the regularization correction group B1 according to a preset cutting generation rule; S17: performing an AND operation on the start identifier of the regularization and correction group B1 and the derived array D1 to obtain a check array of the regularization and correction group B1; S18: Obtain regularized and modified groups B2, B3, ..., Ba in sequence according to S13, and obtain parity check arrays of regularized and modified groups B2, B3, ..., Ba in sequence according to S14 to S17; S19: According to the order of the regularized correction groups B1, B2, ..., Ba, the corresponding check arrays are spliced to obtain the main data check sequence of the integration period.

4. The master data management system in a multi-data source scenario according to claim 3, characterized in that: The derivation rules for generating the derived array D1 of the regularized modified group B1 are as follows: S141: Obtain the number of digits of the first character "1" from the regular integer group A1 in order from right to left, and use the number of digits as the carry identifier C1 of the regularization and correction group B1. If all characters in the regular integer group A1 are "0", the carry identifier C1 of the regularization and correction group B1 is 2; S142: According to the carry identifier C1 of the regular correction group B1, obtain the character D1 located at C1-1 from the regular correction group B1, and make a non-zero judgment on D1. If the character D1 is 1, all the characters after C1 in the regular correction group B1 are removed to obtain the derivative array D1 of the regular correction group B1. Otherwise, the character located at C1-1 in the regular correction group B1 is modified to "1", and the character located at C1 in the regular correction group B1 is modified to "0" to obtain the derivative array D1 of the regular correction group B1.

5. The master data management system in a multi-data source scenario according to claim 4, characterized in that: In S141, for all characters constituting any regular integer group, the number of digits of the characters from left to right is 1, 2, 3, and 4, respectively.

6. The master data management system in a multi-data source scenario according to claim 3, characterized in that: In S16, the cutting generation rule for generating the conversion array of the regularized correction group B1 is as follows: S161: Remove "0." from the derived base number E1 of the regularization and correction group B1, then traverse the remaining data, obtain the first character that is not 0 from left to right, and use the character as the starting identifier of the regularization and correction group B1; S162: extracting all characters after the start identifier of the regularization and correction group B1 from the derived base number E1 of the regularization and correction group B1, and concatenating all the extracted characters in the order of extraction to obtain a positive identifier sequence of the regularization and correction group B1; S163: performing binary conversion on the positive identification sequence of the regularized and modified group B1 to obtain a conversion array of the regularized and modified group B1, wherein the starting identifier of the regularized and modified group B1 is included in the extraction process, and the starting identifier of the regularized and modified group B1 is extracted first.

7. The master data management system in a multi-data source scenario according to claim 1, characterized in that: After generating a master data verification sequence for an integration period, the master data management unit stores the master data of the integration period and the master data verification sequence thereof.

Images