A master data encoding method, system, device and medium based on a business primary key

Abstract

The present application relates to the technical field of data asset management, in particular to a main data coding method, system, device and medium based on business primary key; the method first establishes a configuration table according to the obtained main data object, main data business primary key and business stage; then establishes a coding rule library according to the main data business primary key and the established coding meta model; finally registers the main data model to the main data system, increases the process activity configuration in the maintenance process configuration link, configures the business primary key attribute value after the verification to the coding rule, and generates the main data coding; the flexible coding of the main data object is realized, the main data coding is ensured to be associated and penetrated in each business environment of discrete manufacturing industry, and the penetration of end-to-end process is realized.

Description

Technical Field

[0001] This invention relates to the field of data asset management technology, and more specifically, to a master data encoding method, system, device, and medium based on business primary keys. Background Technology

[0002] In the field of data asset management within management information systems, master data is considered core data for enterprises, characterized by high sharing and high stability. Currently, one of the basic requirements of master data management is to achieve a one-to-one correspondence between master data objects and their codes. This coding maintains consistency across heterogeneous systems and process data while enabling end-to-end business process continuity. However, in the small-batch production model of discrete manufacturing, the diverse personalized needs of different stages of business processes make it impossible to achieve end-to-end process continuity through a fixed master data code. Therefore, a system that supports flexible definition of coding rules is needed for master data coding to adapt to the high-sharing characteristics of master data in discrete manufacturing. Summary of the Invention

[0003] This invention addresses the problem of existing encoding methods requiring repetitive encoding across multiple heterogeneous systems according to their respective scenarios. It proposes a master data encoding method, system, device, and medium based on business primary keys. First, a configuration table is established based on the acquired master data object, master data business primary key, and business stage. Then, an encoding rule base is established based on the master data business primary key and the established encoding meta-model. Finally, the master data model is registered in the master data system, and process activity configuration is added in the maintenance process configuration stage. The verified business primary key attribute values ​​are configured into the encoding rules to generate master data encoding. This achieves flexible encoding of master data objects, ensuring the consistency and interconnectivity of master data encoding across various business environments in discrete manufacturing, and realizing end-to-end process continuity.

[0004] The specific implementation details of this invention are as follows:

[0005] A master data encoding method based on business primary keys first establishes a configuration table based on the acquired master data object, master data business primary key, and business stage; then, an encoding rule base is established based on the master data business primary key and the established encoding meta-model; finally, the master data model is registered in the master data system, and process activity configuration is added in the maintenance process configuration stage to configure the verified business primary key attribute value into the encoding rules to generate master data encoding.

[0006] To better implement this invention, the master data encoding method based on the business primary key further includes the following steps:

[0007] Step S1: Based on the obtained master data object, master data business primary key, and business stage, create a configuration table;

[0008] Step S2: Establish a coding rule base based on the primary key of the main database business and the established coding meta-model;

[0009] Step S3: Based on the master data business primary key attribute set, register the identified master data model to the master data system, select the corresponding coding rule from the coding rule library, add process activities according to the business stage, configure the verified business primary key attribute values ​​into the coding rule, and generate the master data code for the corresponding stage.

[0010] To better realize the present invention, step S1 further includes the following steps:

[0011] Step S11: Obtain the data entity object containing data characteristics from the enterprise database to obtain the master data object;

[0012] Step S12: Based on the master data object and the data link of the master data object in the enterprise business process, divide the master data object into different business stages, identify the master data business primary key corresponding to different business stages, and obtain the master data business primary key attribute set.

[0013] Step S13: Based on the obtained master data object, business stage, and master data business primary key, establish a master data object-business stage-business primary key configuration table, and configure the master data object, business stage, and master data business primary key into the master data system according to the configuration table.

[0014] To better realize the present invention, step S2 further includes the following steps:

[0015] Step S21: Use the abstract analysis method to divide the coding meta-model into prefix model objects, serial code model objects, and suffix model objects;

[0016] Step S22: Based on the master data business primary key and the master data business primary key attribute set, configure the sorting order, separator, and serial number parameters of the master data business primary key attribute items, and establish an encoding rule base.

[0017] To better implement the present invention, the prefix model object and the suffix model object are further used to match the set of primary key attributes of the main data business, sort the combination of primary key attributes of the main data business, and configure the separator after the primary key attribute item of the main data business.

[0018] The characteristic parameters of the serial code model object include the serial code fixed-length identifier, fixed-length, step size, initial value of the serial code, padding character, and separator.

[0019] To better realize the present invention, step S3 further includes the following steps:

[0020] Step S31: After identifying the attribute set corresponding to the primary key of the master data business and the master data attributes, register the master data model to the master data system, and set the encoding rules corresponding to the master data model in the encoding configuration stage;

[0021] Step S32: Add process activities in the master data maintenance process configuration stage to generate master data codes for the corresponding stages;

[0022] Step S33: Verify the business primary key attribute value, and pass the verified business primary key attribute to the configured coding rules to generate discrete manufacturing master data codes.

[0023] To better implement the present invention, the number of configured process activities and the order of activities are further set according to the number of business primary keys of the master data object and the scenario order of the master data object in the data link.

[0024] Based on the above-mentioned master data encoding method based on business primary keys, in order to better realize the present invention, a master data encoding system based on business primary keys is further proposed, including an initialization unit, an establishment unit, and an encoding unit.

[0025] The initialization unit is used to establish a configuration table based on the acquired master data object, master data business primary key, and business stage; the establishment unit is used to establish a coding rule base based on the master data business primary key and the established coding meta-model.

[0026] The encoding unit is used to register the master data model to the master data system, add process activity configuration in the maintenance process configuration stage, configure the verified business primary key attribute value into the encoding rules, and generate master data encoding.

[0027] Based on the aforementioned master data encoding method based on business primary keys, in order to better realize the present invention, an electronic device is further proposed, including a memory and a processor; a computer program is stored in the memory; when the computer program is executed on the processor, the aforementioned master data encoding method based on business primary keys is implemented.

[0028] Based on the aforementioned master data encoding method based on business primary keys, and to better implement this invention, a computer-readable storage medium is further proposed, wherein computer instructions are stored on the computer-readable storage medium; when the computer instructions are executed on the aforementioned electronic device, the aforementioned master data encoding method based on business primary keys is implemented.

[0029] The present invention has the following beneficial effects:

[0030] (1) By constructing a business primary key and a coding meta-model, and adding a coding step to the master data maintenance process to trigger the generation of master data codes, this invention can not only achieve flexible coding of master data objects, but also ensure that master data codes are associated and connected in various business links of discrete manufacturing.

[0031] (2) This invention establishes a configuration table between different business primary keys, master data categories and coding meta-models, and triggers the generation of multiple coding sets in the maintenance process. This not only standardizes the coding process, but also establishes a mapping relationship between different codings at different stages of the same object. This solves the problem that the method of matching one coding rule with one master data object in a discrete environment cannot connect the end-to-end business workflow, and improves the utilization rate of master data object coding. Attached Figure Description

[0032] Figure 1 A flowchart illustrating the master data encoding method based on business primary keys provided by this invention. Detailed Implementation

[0033] To more clearly illustrate the technical solutions of the embodiments of the present invention, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments, and therefore should not be regarded as a limitation on the scope of protection. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0034] In the description of this invention, it should be noted that, unless otherwise explicitly specified and limited, the terms "set up," "connected," and "linked" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0035] The technical terms and their explanations used in the embodiments of this application are as follows:

[0036] Master data: In contrast to business data, master data refers to data that is repeatedly used across multiple business departments within an enterprise and exists in multiple heterogeneous application systems. It has high business value and is used to describe the core business entities of the enterprise.

[0037] Scenario: A set of business activities performed by an enterprise to achieve its production and operation goals, including business processes and related data flows.

[0038] Business primary key: Describes unique identifiers for entity data from a business attribute perspective. The difference between a data primary key and a data primary key is that a data primary key only describes unique identifiers from a data perspective and is unrelated to specific business content; it is added when a new record is added and is typically represented as 32 or 64 bits of random data. A business primary key, on the other hand, describes unique identifiers through a combination of attributes closely related to the business entity object. For example, a business primary key for basic personnel information could be: gender, date of birth, and ID number.

[0039] A business scenario includes business processes and the data entities and data supporting these processes. One characteristic of master data is its high degree of sharing, meaning it comprises entity object data across business processes, systems, and departments. Therefore, there must be a relationship between the master data objects in the scenario, the attribute combinations of the business primary keys of these master data entity objects, and other relevant factors. Furthermore, given the diverse and small-batch nature of discrete manufacturing business processes, business scenarios are often segmented. This means that the data requirements for the same master data object differ across scenarios. For example, in the process documentation stage, the business primary keys required for part master data might include drawing number, version, and technical status; in the planning stage, they might include drawing number, version, and manufacturing unit. Therefore, establishing the relationships between scenarios, master data, and business primary keys is a necessary step in streamlining end-to-end processes.

[0040] Example 1:

[0041] This embodiment proposes a master data encoding method based on business primary keys. First, a configuration table is established based on the acquired master data object, master data business primary key, and business stage. Then, an encoding rule base is established based on the master data business primary key and the established encoding meta-model. Finally, the master data model is registered in the master data system, and a process activity configuration is added in the maintenance process configuration stage. The verified business primary key attribute values ​​are configured into the encoding rules to generate master data encoding. Figure 1 As shown, the master data encoding method based on the business primary key specifically includes the following steps:

[0042] Step S1: Create a configuration table based on the obtained master data object, master data business primary key, and business stage.

[0043] Furthermore, step S1 specifically includes the following steps:

[0044] Step S11: Obtain the data entity object containing data characteristics from the enterprise database to obtain the master data object;

[0045] Step S12: Based on the master data object and the data link of the master data object in the enterprise business process, divide the master data object into different business stages, identify the master data business primary key corresponding to different business stages, and obtain the master data business primary key attribute set.

[0046] Step S13: Based on the obtained master data object, business stage, and master data business primary key, establish a master data object-business stage-business primary key configuration table, and configure the master data object, business stage, and master data business primary key into the master data system according to the configuration table.

[0047] Step S2: Establish a coding rule base based on the primary key of the main database business and the established coding meta-model.

[0048] Furthermore, step S2 specifically includes the following steps:

[0049] Step S21: Use the abstract analysis method to divide the coding meta-model into prefix model objects, serial code model objects, and suffix model objects;

[0050] Step S22: Based on the master data business primary key and the master data business primary key attribute set, configure the sorting order, separator, and serial number parameters of the master data business primary key attribute items, and establish an encoding rule base.

[0051] Furthermore, the prefix model object and the suffix model object are used to match the set of primary key attributes of the main data business, sort the combination of primary key attributes of the main data business, and configure the separator after the primary key attribute item of the main data business.

[0052] The characteristic parameters of the serial number model object include whether it is fixed length, fixed length, step size, initial value, padding character, and separator.

[0053] Step S3: Based on the master data business primary key attribute set, register the identified master data model to the master data system, select the corresponding coding rule from the coding rule library, add process activities according to the business stage, configure the verified business primary key attribute values ​​into the coding rule, and generate the master data code for the corresponding stage.

[0054] Furthermore, step S3 specifically includes the following steps:

[0055] Step S31: After identifying the attribute set corresponding to the primary key of the master data business and the master data attributes, register the master data model to the master data system, and set the encoding rules corresponding to the master data model in the encoding configuration stage;

[0056] Step S32: Add process activities in the master data maintenance process configuration stage to generate master data codes for the corresponding stages;

[0057] Step S33: Verify the business primary key attribute value, and pass the verified business primary key attribute to the configured coding rules to generate discrete manufacturing master data codes.

[0058] Furthermore, the number of configured process activities and the order of activities are set according to the number of business primary keys of the master data object and the scenario order of the master data object in the data link.

[0059] Working principle: This embodiment first establishes a configuration table based on the acquired master data object, master data business primary key, and business stage; then, it establishes a coding rule base based on the master data business primary key and the established coding meta-model; finally, it registers the master data model to the master data system and adds process activity configuration in the maintenance process configuration stage, configuring the verified business primary key attribute value into the coding rules to generate master data codes; this achieves flexible coding of master data objects, ensuring that master data codes are interconnected across various business environments in discrete manufacturing, and realizing end-to-end process connectivity.

[0060] Example 2:

[0061] This embodiment is based on the above embodiment 1, such as... Figure 1 As shown, the specific steps include:

[0062] Step S1: Retrieve the data entity object containing data characteristics from the enterprise database to obtain the master data object;

[0063] Based on the master data object and its data link in the enterprise business process, the master data object is divided into different application scenarios, and the master data business primary key under different application scenarios is identified to obtain a set of master data object application code attribute list.

[0064] The master data code is a set of data attributes used to uniquely identify a master data object. When the content of any one of these attributes changes, a new master data code needs to be generated.

[0065] When the master data object is a device master data object, the primary key of the device master data object in the procurement project initiation stage is project category + project name + device name; in the procurement stage, the primary key of the device master data object is procurement demand source + demand name + device name + device model + device specification; in the warehousing and accounting stage, the primary key of the device master data object is device name + device model + device specification + manufacturer + factory identification code; and in the asset depreciation stage, the primary key of the device master data object is asset category + device name + device model + device specification + user department + purchase time. If the maintenance of the device is the same as that in the warehousing and accounting stage due to the uniqueness requirement, it does not need to be identified as a separate scenario for business key identification.

[0066] Based on the obtained master data objects, application scenarios, and master data business primary keys, a master data object-application scenario-business primary key configuration table is established, and the master data objects, application scenarios, and master data business primary keys are configured into the master data system according to the configuration table.

[0067] In this embodiment, the corresponding business primary key is identified for each type of master data according to different business stages or scenarios; the attribute items identified as business primary keys must be included in master data management and non-null constraints are applied during master data model registration; after the business primary key identification is completed, a relationship configuration table of master data category, business scenario, and business primary key is established.

[0068] In this embodiment, the scenario is not a data query, but rather a process of encoding master data to associate different scenarios using primary key combinations with business meaning. The technical implementation does not rely on existing primary-foreign key relationships. Instead, it adds columns instead of rows to the identified master data model to include all fields related to the business primary keys for each scenario. It explicitly states that attributes identified as business primary keys must be included in master data management and are not empty. When the data items entered by the master data maintenance personnel in the maintenance process match the business primary key attribute combination data items in the master data category, scenario, and business rule configuration tables, the encoding ring is triggered to call the corresponding encoding rules to generate codes and write them to the corresponding columns in the master data model. The configuration table data items include master data category, scenario name, scenario activity set, business primary key name, business primary key attribute combination, and configured business rule name. The configuration table configuration process originates from the results of master data identification in the end-to-end process. The configuration is based on segmenting the process at the same granularity to form corresponding scenarios, business primary keys, and primary key attribute combinations.

[0069] Generating a new code for newly generated data typically involves using a sequence number or a globally unique identifier. The challenge lies in controlling the generation of new versions when backend data is modified. This embodiment focuses not on the version of the data itself, but on the unique identifier of the same data across different business processes. Furthermore, it requires pre-configured encoding rules. The difficulty lies in the segmentation of various scenarios in the end-to-end process and the implementation of business primary key encoding. For example, in personnel information, when a person's position changes, a new version of the personnel information is generated. Traditionally, this would result in a new data primary key. In this embodiment, the business primary key remains unchanged. However, in a scenario like attendance tracking, the business primary key includes: gender, date of birth, ID number, and attendance date.

[0070] Step S2: Use the abstract analysis method to divide the coding meta-model into prefix model objects, serial code model objects, and suffix model objects;

[0071] The prefix model object and suffix model object are used to match the attribute set, sorting attribute combination, and configuration attribute item separator involved in the primary key of the master data business;

[0072] The characteristic parameters of the serial number model object include a serial number fixed-length identifier, fixed-length, step size, initial value of the serial number, padding character, and separator. Among them, the serial number fixed-length identifier is 0 for variable length and 1 for fixed length; the initial value of the serial number is the first serial number, such as 0001.

[0073] This embodiment uses an abstract analysis method to divide the coding metamodel into three objects: prefix, serial code, and suffix. The prefix and suffix objects can contain zero or more attributes, and each attribute can define a delimiter. If there is no delimiter, it is not defined. If the serial code object exists, feature parameters need to be defined, such as whether it is fixed length, fixed length, step size, initial value, padding character, and delimiter. If it does not contain a serial code object, it does not need to be defined.

[0074] Based on the identified primary key of the master data business and the obtained list of primary key attributes, the sorting order, separator, and serial number parameters of the primary key attributes are configured to form an encoding rule base.

[0075] In this embodiment, the encoding meta-model does not reflect business meaning; it only serves as a unique identifier for computer recognition. Technically, it requires an encoding rule table to support encoding generation, i.e., the encoding meta-model needs to be implemented through code, and different encoding services need to be published. Implementing the encoding meta-model in advance can adapt to more complex encoding scenarios, such as whether the encoding reflects business attributes or not, supporting prefix and suffix replacement, and supporting multiple different scenarios such as pure numbers, numbers and letters, and Chinese characters.

[0076] Step S3: After identifying the attribute set corresponding to the primary key of the master data business and other master data attributes, register the master data model to the master data system, and set the coding rules corresponding to the master data model in the coding configuration stage; add process activities in the master data maintenance process configuration stage to generate master data codes for the corresponding stages;

[0077] The configuration number and activity order of the process activities are set according to the number of business primary keys of the master data objects and the scenario order of the master data objects in the data link.

[0078] Verify the business primary key attribute value, and pass the verified business primary key attribute to the configured coding rules to generate the master data code for discrete manufacturing industry.

[0079] This embodiment adds a process activity to the maintenance process configuration stage. After each type of master data model is registered, a maintenance process needs to be configured to realize the maintenance and review of master data. The traditional approach is to fix an activity as a coding step in the process, that is, there is a fixed coding step in the process activity table that is associated with the master data coding process master table. This approach is mainly suitable for scenarios where the business process is unified and standardized, and a single code can achieve seamless integration, which is not consistent with the discrete scenario in this embodiment.

[0080] In this embodiment, the order of activities within the coded process is not fixed. Therefore, when each activity submits data, it associates the master data category, scenario, and business primary key configuration table with the submitted process activity name and data item. If a matching business primary key combination is found, and the business primary key field in the current master data does not contain valid data, the process activity calls the corresponding coding rule in the configuration table; otherwise, it proceeds to the next activity or ends the process. The advantage of this embodiment is that it does not rely on fixed processes and processes. Coding steps can be flexibly added at each stage of adding or changing processes to generate corresponding codes based on actual business rules. Without adding process activities, the master data coding cannot adapt to various processes, cannot generate corresponding codes according to different scenarios, and cannot meet the master data coding requirements of discrete manufacturing processes.

[0081] Working principle: This embodiment constructs business primary keys and coding meta-models, and adds a coding step to the master data maintenance process to trigger master data coding generation. This not only enables flexible coding of master data objects, but also ensures that master data coding is interconnected across various business processes in discrete manufacturing. By establishing a configuration table between different business primary keys, master data categories, and coding meta-models, and triggering the centralized generation of multiple codes during the maintenance process, this embodiment standardizes the coding process and establishes a mapping relationship between different codes at different stages of the same object. This solves the problem that the method of assigning one coding rule to one master data object in a discrete environment cannot connect the end-to-end business workflow, thus improving the utilization rate of master data object coding.

[0082] This embodiment encodes based on the business primary keys of each stage of the discrete manufacturing process, which can ensure that the final generated code covers the business process and supports the association between the front-end and back-end processes. It can be used in different business scenarios, realizing the end-to-end process connection. From a technical point of view, it realizes the demand for unified coding in discrete manufacturing, without having to repeatedly code according to their respective scenarios in multiple heterogeneous systems.

[0083] The other parts of this embodiment are the same as those in Embodiment 1 above, so they will not be described again.

[0084] Example 3:

[0085] Based on any one of Embodiments 1-2 above, this embodiment proposes a master data encoding system based on business primary keys, including an initialization unit, an establishment unit, and an encoding unit;

[0086] The initialization unit is used to establish a configuration table based on the acquired master data object, master data business primary key, and business stage; the establishment unit is used to establish a coding rule base based on the master data business primary key and the established coding meta-model.

[0087] The encoding unit is used to register the master data model to the master data system, add process activity configuration in the maintenance process configuration stage, configure the verified business primary key attribute value into the encoding rules, and generate master data encoding.

[0088] This embodiment also proposes an electronic device, including a memory and a processor; a computer program is stored in the memory; when the computer program is executed on the processor, the above-mentioned master data encoding method based on the business primary key is implemented.

[0089] This embodiment also proposes a computer-readable storage medium storing computer instructions; when the computer instructions are executed on the aforementioned electronic device, the aforementioned master data encoding method based on the business primary key is implemented.

[0090] The other parts of this embodiment are the same as any one of the above embodiments 1-2, so they will not be described again.

[0091] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention in any way. Any simple modifications or equivalent changes made to the above embodiments based on the technical essence of the present invention shall fall within the protection scope of the present invention.

Claims

1. A master data encoding method based on business primary keys, characterized in that, First, a configuration table is created based on the acquired master data object, master data business primary key, and business stage. Then, a coding rule base is created based on the master data business primary key and the created coding meta-model. Finally, the master data model is registered in the master data system, and a process activity configuration is added in the maintenance process configuration stage. The verified business primary key attribute value is configured into the coding rule to generate master data coding. The master data encoding method based on business primary keys specifically includes the following steps: Step S1: Based on the obtained master data object, master data business primary key, and business stage, create a configuration table; Step S2: Establish a coding rule base based on the primary key of the main database business and the established coding meta-model; Step S3: Based on the master data business primary key attribute set, register the identified master data model to the master data system, select the corresponding coding rule from the coding rule library, add process activities according to the business stage, configure the verified business primary key attribute values ​​into the coding rule, and generate the master data code for the corresponding stage. Step S2 specifically includes the following steps: Step S21: Use the abstract analysis method to divide the coding meta-model into prefix model objects, serial code model objects, and suffix model objects; Step S22: Based on the master data business primary key and the master data business primary key attribute set, configure the sorting order, separator, and serial number parameters of the attribute items of the master data business primary key, and establish an encoding rule base; The prefix model object and suffix model object are used to match the set of primary key attributes of the main data business, sort the combination of primary key attributes of the main data business, and configure the separator after the primary key attribute item of the main data business. The characteristic parameters of the serial code model object include the serial code fixed-length identifier, fixed-length, step size, initial value of the serial code, padding character, and separator.

2. The master data encoding method based on business primary keys according to claim 1, characterized in that, Step S1 specifically includes the following steps: Step S11: Obtain the data entity object containing data characteristics from the enterprise database to obtain the master data object; Step S12: Based on the master data object and the data link of the master data object in the enterprise business process, divide the master data object into different business stages, identify the master data business primary key corresponding to different business stages, and obtain the master data business primary key attribute set. Step S13: Based on the obtained master data object, business stage, and master data business primary key, establish a master data object-business stage-business primary key configuration table, and configure the master data object, business stage, and master data business primary key into the master data system according to the configuration table.

3. The master data encoding method based on business primary keys according to claim 1, characterized in that, Step S3 specifically includes the following steps: Step S31: After identifying the attribute set corresponding to the primary key of the master data business and the master data attributes, register the master data model to the master data system, and set the encoding rules corresponding to the master data model in the encoding configuration stage; Step S32: Add process activities in the master data maintenance process configuration stage to generate master data codes for the corresponding stages; Step S33: Verify the business primary key attribute value, and pass the verified business primary key attribute to the configured coding rules to generate discrete manufacturing master data codes.

4. The master data encoding method based on business primary keys according to claim 3, characterized in that, The number of configured activities and the order of activities are set according to the number of business primary keys of the master data object and the scenario order of the master data object in the data link.

5. A master data encoding system based on a business primary key, used to execute the master data encoding method based on a business primary key as described in claim 1; characterized in that, Includes initialization unit, setup unit, and encoding unit; The initialization unit is used to establish a configuration table based on the acquired master data object, master data business primary key, and business stage; the establishment unit is used to establish a coding rule base based on the master data business primary key and the established coding meta-model. The encoding unit is used to register the master data model to the master data system, add process activity configuration in the maintenance process configuration stage, configure the verified business primary key attribute value into the encoding rules, and generate master data encoding.

6. An electronic device, characterized in that, It includes a memory and a processor; a computer program is stored in the memory; when the computer program is executed on the processor, it implements the master data encoding method based on the business primary key as described in any one of claims 1-4.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions; when the computer instructions are executed on the electronic device as described in claim 6, they implement the master data encoding method based on the business primary key as described in any one of claims 1-3.

Images