Data updating method and device, computer equipment, readable storage medium and program product

Abstract

The invention relates to a data updating method and device, computer equipment, a computer readable storage medium and a computer program product. The method comprises the following steps: extracting incremental data under the condition of detecting that an update identifier of a main data storage database represents that data update exists; generating an updating operation instruction corresponding to the incremental data according to the updating type of the incremental data; pushing an update operation instruction to the business system through the interface service to execute data update processing in the business system to obtain a data update result; under the condition that data updating is completed, the updating identification of the incremental data is correspondingly modified. According to the method, an incremental pushing and event driving mechanism of the main data is realized through an incremental identifier updating detection mechanism, the main data updating time delay is effectively shortened, the incremental data of the main data storage database is extracted according to the updating identifier for updating processing, the data transmission quantity in the data updating process is effectively reduced, and the updating efficiency is improved. Therefore, the data updating processing efficiency of the main data system is improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a data updating method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Technology

[0002] With the advancement of enterprise informatization and digitalization strategies, enterprise business systems have gradually evolved from early "single-function systems" to "multi-domain distributed systems" (such as ERP, CRM, SCM, etc.). Master data, as a core data asset of enterprises (such as customer data, product data, and organizational data), has also transitioned from "independent maintenance by each system" to "centralized management and control by a master data management platform." Currently, mainstream master data management platforms possess basic functions such as master data collection, cleaning, storage, and sharing, but there is still room for optimization in terms of "real-time performance" and "performance adaptability."

[0003] While existing master data management platforms offer sharing and open functionality, they are limited by the "full data retrieval on a scheduled basis" sharing model, resulting in a master data update delay of 1-24 hours. This leads to low efficiency in master data updates and fails to meet the "real-time data synchronization" requirements of enterprises in fast-paced production scenarios. Summary of the Invention

[0004] Therefore, it is necessary to provide a data update method, apparatus, computer equipment, computer-readable storage medium, and computer program product that can improve the efficiency of data update processing in response to the above-mentioned technical problems.

[0005] Firstly, this application provides a data updating method, including:

[0006] If an update identifier is detected in the main data storage database indicating that data has been updated, incremental data is extracted from the main data storage database based on the update identifier.

[0007] Generate an update operation instruction corresponding to the incremental data based on the update type of the incremental data;

[0008] The update operation instruction is pushed to the business system through the interface service, so that the data update processing corresponding to the incremental data is executed in the business system to obtain the data update result;

[0009] When the data update result indicates that the data update is complete, the update identifier of the incremental data in the main data storage database is modified accordingly.

[0010] In one embodiment, the method further includes:

[0011] Upon receiving a master data update request, obtain the master data release application information corresponding to the master data update request;

[0012] The master data release application information is reviewed and approved to obtain the review result information corresponding to the master data release application information.

[0013] If the audit result information indicates that the audit has been approved, the master data storage database is updated with incremental data based on the master data release application information.

[0014] In one embodiment, the master data update process includes master data addition processing, master data modification processing, and master data deletion processing;

[0015] The incremental data update process for the master data storage database based on the master data release application information includes:

[0016] When the master data release application information characterizes the data update processing as master data addition processing, the physical data table, version number identifier, and update identifier of the incremental data corresponding to the master data release application information are searched in the master data storage database, and the master data addition processing corresponding to the incremental data is performed according to the physical data table, the version number identifier, and the update identifier.

[0017] When the master data release application information characterizes the data update processing as master data modification processing, the version number identifier and update identifier of the incremental data corresponding to the master data storage database are searched in the master data storage database, and the master data modification processing corresponding to the incremental data is performed according to the version number identifier and the update identifier.

[0018] When the master data release application information represents data update processing as master data deletion processing, the version number identifier and update identifier of the incremental data corresponding to the master data release application information are searched in the master data storage database, and the master data deletion processing corresponding to the incremental data is performed according to the version number identifier and the update identifier.

[0019] In one embodiment, the update type includes add type, modify type and delete type, and the update operation instruction includes insert instruction, update instruction and delete instruction;

[0020] The step of generating the update operation instruction corresponding to the incremental data based on the update type of the incremental data includes:

[0021] When the update type of the incremental data is an addition type, the master data code of the incremental data is identified, and an insertion instruction is generated using the master data code as the primary key.

[0022] When the update type of the incremental data is a modification type, identify the master data code and version number of the incremental data, and generate an update instruction using the master data code and the version number as a joint primary key;

[0023] When the update type of the incremental data is a modification type, the master data code of the incremental data is identified, and a deletion instruction is generated using the master data code as the matching field.

[0024] In one embodiment, the step of pushing update operation instructions to the business system via an interface service to perform data update processing corresponding to the incremental data in the business system and obtain data update results includes:

[0025] When the update type of the incremental data is a new addition type, the insertion instruction and the master data code uniqueness verification rule are pushed to the business system through the interface service. The uniqueness verification rule of the master data code is used to perform uniqueness verification processing in the business system, and the data insertion processing corresponding to the incremental data is performed according to the verification result of the uniqueness verification processing to obtain the data update result.

[0026] When the update type of the incremental data is modification type, the update instruction is pushed to the business system through the interface service, so that the data modification processing corresponding to the incremental data is performed in the business system through the master data code and version number carried by the update instruction, and the data update result is obtained.

[0027] When the update type of the incremental data is deletion, the deletion instruction is pushed to the business system through the interface service. The business system then performs the data deletion process corresponding to the incremental data using the master data code carried by the update instruction, and obtains the data update result.

[0028] In one embodiment, it further includes:

[0029] If the data update result indicates that the data update has failed, perform the update retry process corresponding to the data update result to obtain the update retry result;

[0030] If the update retry result indicates that the update retry was successful, the number of retryes and the success time are recorded, and the update identifier of the incremental data in the main data storage database is modified accordingly.

[0031] If the update retry result indicates that the update retry has failed, the data rollback operation corresponding to the update operation instruction is executed, and an alarm message corresponding to the update retry result is generated.

[0032] Secondly, this application also provides a data updating device, comprising:

[0033] The incremental data extraction module is used to extract incremental data from the main data storage database based on the update identifier when an update identifier is detected indicating that data has been updated in the main data storage database.

[0034] The instruction generation module is used to generate update operation instructions corresponding to the incremental data based on the update type of the incremental data;

[0035] The instruction push module is used to push update operation instructions to the business system through the interface service, so as to perform data update processing corresponding to the incremental data in the business system and obtain data update results.

[0036] The identifier update module is used to modify the update identifier of the incremental data in the main data storage database when the data update result indicates that the data update is complete.

[0037] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0038] If an update identifier is detected in the main data storage database indicating that data has been updated, incremental data is extracted from the main data storage database based on the update identifier.

[0039] Generate an update operation instruction corresponding to the incremental data based on the update type of the incremental data;

[0040] The update operation instruction is pushed to the business system through the interface service, so that the data update processing corresponding to the incremental data is executed in the business system to obtain the data update result;

[0041] When the data update result indicates that the data update is complete, the update identifier of the incremental data in the main data storage database is modified accordingly.

[0042] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0043] If an update identifier is detected in the main data storage database indicating that data has been updated, incremental data is extracted from the main data storage database based on the update identifier.

[0044] Generate an update operation instruction corresponding to the incremental data based on the update type of the incremental data;

[0045] The update operation instruction is pushed to the business system through the interface service, so that the data update processing corresponding to the incremental data is executed in the business system to obtain the data update result;

[0046] When the data update result indicates that the data update is complete, the update identifier of the incremental data in the main data storage database is modified accordingly.

[0047] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:

[0048] If an update identifier is detected in the main data storage database indicating that data has been updated, incremental data is extracted from the main data storage database based on the update identifier.

[0049] Generate an update operation instruction corresponding to the incremental data based on the update type of the incremental data;

[0050] The update operation instruction is pushed to the business system through the interface service, so that the data update processing corresponding to the incremental data is executed in the business system to obtain the data update result;

[0051] When the data update result indicates that the data update is complete, the update identifier of the incremental data in the main data storage database is modified accordingly.

[0052] The aforementioned data update method, apparatus, computer equipment, computer-readable storage medium, and computer program product, upon detecting an update identifier in the master data storage database indicating a data update, extract incremental data from the master data storage database based on the update identifier; generate an update operation instruction corresponding to the incremental data based on the update type of the incremental data; push the update operation instruction to the business system through an interface service, so that the business system executes the data update processing corresponding to the incremental data to obtain a data update result; and modify the update identifier of the incremental data in the master data storage database accordingly when the data update result indicates that the data update is complete. This application, through an incremental identifier update detection mechanism, implements an "incremental push + event-driven" mechanism for master data, effectively shortening the master data update latency of the system. Furthermore, by extracting incremental data from the master data storage database based on the update identifier for update processing, it effectively reduces the amount of update data transmitted during the data update process, thereby improving the data update processing efficiency of the master data system. Attached Figure Description

[0053] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0054] Figure 1 This is a diagram illustrating the application environment of a data update method in one embodiment.

[0055] Figure 2 This is a flowchart illustrating a data update method in one embodiment;

[0056] Figure 3 This is a flowchart illustrating the database update steps of the master data management platform in one embodiment.

[0057] Figure 4 This is a flowchart illustrating the steps of the master data management platform in real-time updating business system data in one embodiment;

[0058] Figure 5 This is a structural block diagram of a data update device in one embodiment;

[0059] Figure 6 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0060] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0061] The data update method provided in this application embodiment can be applied to, for example, Figure 1In the application environment shown, terminal 102 communicates with master data management server 104 via a network. Multiple business servers 106 can also communicate with master data management server 104 via a network. The master data storage database stores the master data that master data management server 104 needs to process. The master data storage database can be integrated on master data management server 104 or placed on the cloud or other network servers. Terminal 102 can update the master data on master data management server 104. When master data management server 104 detects an update identifier in the master data storage database indicating a data update, it extracts incremental data from the master data storage database based on the update identifier; generates update operation instructions corresponding to the incremental data based on the update type of the incremental data; pushes the update operation instructions to the business system through an interface service to execute the data update processing corresponding to the incremental data on the business server 106 corresponding to the business system, obtaining the data update result; and, if the data update result indicates that the data update is complete, modifies the update identifier of the incremental data in the master data storage database accordingly. The terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle systems, and projection devices. Portable wearable devices can include smartwatches, smart bracelets, and head-mounted displays. Head-mounted displays can be virtual reality (VR) devices, augmented reality (AR) devices, and smart glasses. The main data management server 104 and the business server 106 can be independent physical servers, server clusters or distributed systems composed of multiple physical servers, or cloud servers providing cloud computing services.

[0062] In one exemplary embodiment, such as Figure 2 As shown, a data update method is provided, which is applied to... Figure 1 Taking the master data management server 104 as an example, the explanation includes the following steps 201 to 207. Wherein:

[0063] Step 201: If an update identifier is detected in the main data storage database indicating that data has been updated, the incremental data of the main data storage database is extracted based on the update identifier.

[0064] The master data storage database refers to the database used to store the master data managed by the master data management server. Master data is high-value core business entity data shared across systems, departments, and business processes within an enterprise, used to uniformly describe the identity and attributes of key business objects. It serves as the "common language" of enterprise operations, typically changing slowly but frequently referenced by business systems. Examples include customer master data (customer code, customer name, contact information, etc.); supplier master data (supplier number, company name, payment method, etc.); material master data (material code, material name, specifications, unit of measurement, classification, etc.); and employee master data (employee ID, name, position, organization, employment status, etc.). Master data can be shared across systems; multiple systems (such as ERP, CRM, SCM) use the same set of customer or material information, possessing authoritative uniqueness and high citation frequency. Update flags, on the other hand, are used to indicate whether master data has been updated. Update flags are Boolean values, Y / N, corresponding to whether data has been updated or not. In the context of master data management and data synchronization, the "add, modify, and delete" operations of master data are usually considered as incremental data.

[0065] For example, in an enterprise system, master data is the "common language of enterprise operations." To ensure that all enterprise systems use unified, accurate, and timely basic information and avoid business errors, inefficiencies, and decision-making mistakes caused by data inconsistencies, it is necessary to synchronize the master data update status to the business systems after the master data is updated. The solution proposed in this application is suitable for timely and efficient synchronization of master data to the business systems. Therefore, the solution proposed in this application specifically uses an "event-driven + timed scanning" dual-trigger mode to process master data-related data updates. First, when the "whether to update flag" in the master data storage database changes from N to Y, incremental extraction is automatically triggered. Second, records with "whether to update flag = Y" are scanned periodically, for example, every 10 seconds, to prevent missed extractions. This effectively detects the data update status of the master data storage database and allows the extraction of incremental data from the master data storage database based on the update flag.

[0066] Step 203: Generate update operation instructions corresponding to the incremental data based on the update type of the incremental data.

[0067] For example, in master data management and data synchronization scenarios, the "add, modify, and delete" operations of master data are usually regarded as incremental data. Therefore, the update type of incremental data can specifically include three types: add, modify, and delete. Each type corresponds to an update operation instruction to synchronize the incremental data of the master data storage database to the business system and complete the data update process.

[0068] Step 205: Push update operation instructions to the business system through the interface service, so that the business system can perform the data update processing corresponding to the incremental data and obtain the data update result.

[0069] For example, when generating update operation instructions, these instructions can be pushed to the business system via an interface service to perform data update processing corresponding to the incremental data. Here, each business system has an independent API interface, with interface authentication and field mapping pre-completed. Therefore, the corresponding update operation instructions can be sent directly from the business system on business server 106 or from the business system's database interface. Upon receiving the request, the target business system (such as ERP or CRM) performs processes including verifying identity and permissions (checking token validity), verifying data integrity (required fields, coding standards, etc.), performing local operations, recording operation logs, and returning response results. Finally, it generates and returns the incremental data update result to the master data management server 104.

[0070] Step 207: If the data update result indicates that the data update is complete, modify the update flag of the incremental data in the main data storage database accordingly.

[0071] For example, when the push process returns a data update result indicating that the data update is complete, corresponding data cleanup instructions can be further executed. For instance, for incremental data of the deletion type, records with "version number = 0" can be deleted (i.e., records that have been deleted by the business system, achieving physical deletion and releasing storage resources). In addition, the "whether to update" flag of all successfully pushed records needs to be changed from Y to N to avoid repeated extraction and push during the master data update process.

[0072] The aforementioned data update method involves, upon detecting an update identifier in the master data storage database indicating a data update, extracting incremental data from the master data storage database based on the update identifier; generating an update operation instruction corresponding to the incremental data based on the update type of the incremental data; pushing the update operation instruction to the business system via an interface service, so that the business system executes the data update processing corresponding to the incremental data to obtain the data update result; and modifying the update identifier of the incremental data in the master data storage database accordingly when the data update result indicates that the data update is complete. This application, through an incremental identifier update detection mechanism, implements an "incremental push + event-driven" mechanism for master data, effectively shortening the master data update latency of the system. Furthermore, by extracting incremental data from the master data storage database based on the update identifier for update processing, it effectively reduces the amount of update data transmitted during the data update process, thereby improving the data update processing efficiency of the master data system.

[0073] In an exemplary embodiment, the method further includes: upon receiving a master data update request, obtaining master data release application information corresponding to the master data update request; performing release review processing on the master data release application information and obtaining review result information corresponding to the master data release application information; and, if the review result information indicates that the review has been passed, performing incremental master data update processing on the master data storage database based on the master data release application information.

[0074] Among them, a master data update request refers to a request to update the master data stored in the master data storage database. The master data update request includes master data release application information, which records information such as the specific update type, master data code list, and operation time. Release review processing refers to reviewing whether the master data update details in the release application (including the comparison of fields before and after addition, deletion, and modification) comply with business rules (such as whether the added customer code complies with the enterprise coding standard).

[0075] For example, users can edit the addition, modification, and deletion of master data stored in the master data storage database on the terminal, generate corresponding master data release application information, and submit master data update requests to the master data management server based on the master data release application information. The master data management server then performs the database update processing of the master data. Specifically, after completing the master data addition, deletion, and modification operations, users need to select the master data record marked "Update Flag = Y" in the master data release module, generate a unified "Master Data Release Application Form" (including update type, master data code list, operation time, etc.), and submit it to the master data management server to enter the review stage. The review stage can be implemented through machine review and manual review. Reviewers can view the master data update details in the release application form (including field comparison before and after addition, deletion, and modification) through the interface of the master data release review module. If it meets the business rules (such as the addition of customer codes conforming to the enterprise coding specifications), the review is approved; if it does not meet the rules, it is rejected and the reason for rejection is filled in (synchronously fed back to the applicant user). The review approval / rejection results are synchronized to the master data release module in real time, and the applicant user can view them in real time. Once the release application is approved, the master data storage database module automatically performs data updates and simultaneously locks the update flag information of the "update status" for that batch of records, thereby preventing duplicate releases. In this embodiment, the master data update process is reviewed and processed through master data release application information, and the master data update is completed based on the review results, thus effectively ensuring the accuracy and validity of master data updates.

[0076] In one exemplary embodiment, the master data update process includes master data addition processing, master data modification processing, and master data deletion processing.

[0077] Incremental data update processing of the master data storage database based on master data release application information includes:

[0078] When the master data release application information represents data update processing as master data addition processing, the physical data table, version number identifier, and update identifier of the incremental data corresponding to the master data release application information are searched in the master data storage database. Based on the physical data table, version number identifier, and update identifier, the master data addition processing corresponding to the incremental data is performed.

[0079] When the master data release application information represents data update processing as master data modification processing, the version number identifier and update identifier of the incremental data corresponding to the master data release application information are searched in the master data storage database, and the master data modification processing corresponding to the incremental data is performed based on the version number identifier and update identifier.

[0080] When the master data release application information represents data update processing as master data deletion processing, the version number identifier and update identifier of the incremental data corresponding to the master data release application information are searched in the master data storage database, and the master data deletion processing corresponding to the incremental data is performed based on the version number identifier and update identifier.

[0081] For example, master data update processing specifically includes three processing types: master data addition processing, master data modification processing, and master data deletion processing.

[0082] For the processing of newly added master data, based on user operations, a corresponding physical data table needs to be created in the master data storage database according to the business attributes of the newly added master data (such as customer data containing "customer code, customer name, and contact information"). The table structure must contain the fields "Master data code (string type, 32-bit length, globally unique), version number (integer type, initial value 1), update status (boolean type, value Y / N), creation time, and operator". For the import of this newly added data, there are two import methods: one supports importing standard CSV / Excel format files (with "format validation, field integrity validation, and master data code uniqueness validation" triggered before import); the other is manual entry (entered through a visual form, with real-time field format validation). After the data import is complete, the "version number" of the newly added master data record in the master data storage database is assigned a value of 1, the "update status" is assigned a value of Y, and the creation time and operator information are recorded synchronously. When the review result information indicates that the review has passed, for the processing of new master data, it is necessary to confirm and store the corresponding incremental data according to the physical data table, version number identifier, and update identifier, so as to turn this "draft record to be published" into a "valid record to be officially published" in the master data storage database.

[0083] For master data modification, only users with master data modification permissions are allowed to perform single / batch modifications on existing master data records in the visual interface of the master data asset management module (field-level modifications are supported, such as updating customer contact information). After the modification operation is submitted, the "version number" of the corresponding record in the master data storage database is incremented by 1 (e.g., if the original version number was 2, it becomes 3 after modification), the "update flag" is assigned a value of Y, and the operation time and operator information are updated synchronously. In the case where the review result information indicates that the review has been approved, for master data modification, the incremental data is modified according to the version number flag and the update flag, thus indicating that this new version number (e.g., version number = 3) has been officially adopted and will become the baseline version for all subsequent system synchronization.

[0084] For master data deletion, users with master data deletion permissions must initiate a deletion request in the master data asset management module. The system first performs logical deletion (marking the "deletion status" field as "deleted," while retaining the data record for traceability). After logical deletion, the "version number" of the corresponding record in the master data storage database is set to 0, and the "update flag" is set to Y, synchronously recording the deletion time and operator information. In the review result information indicating successful review, for master data deletion, the incremental data corresponding to the deletion is processed based on the version number flag and update flag to confirm whether the version number is set to 0.

[0085] In this embodiment, after approval, the master data storage database module performs the corresponding data update process for different master data update processes, ensuring the accuracy and efficiency of data updates.

[0086] In an exemplary embodiment, the update types include add type, modify type and delete type, and the update operation instructions include insert instruction, update instruction and delete instruction.

[0087] Step 203 includes: when the update type of incremental data is an insert type, identifying the primary data code of the incremental data and generating an insert instruction using the primary data code as the primary key; when the update type of incremental data is a modify type, identifying the primary data code and version number of the incremental data and generating an update instruction using the primary data code and version number as a composite primary key; when the update type of incremental data is a modify type, identifying the primary data code of the incremental data and generating a delete instruction using the primary data code as the matching field.

[0088] For example, master data update processing includes master data addition processing, master data modification processing, and master data deletion processing. The corresponding update types for synchronizing incremental data to the business system are addition, modification, and deletion types, and the corresponding update operation instructions are insert, update, and delete instructions. In the data update process, for the master data storage database, the extraction logic can be "filtering all records in the master data storage database with 'Update Status = Y'", and classifying them according to "update type" (add / modify / delete) to generate an incremental data set (containing core information such as master data code, version number, field values, and update type). Then, corresponding update operation instructions are generated for different types of incremental data in the incremental data set. Specifically, for "new" type records in the incremental dataset, an "insert instruction" (containing complete field values, with "master data code" as the primary key) is generated; for "modified" type records, an "update instruction" (containing master data code and new field values, with "master data code + version number" as the composite primary key) is generated; and for "deleted" type records, a "delete instruction" (containing master data code, with "master data code" as the unique matching field) is generated. These update operation instructions then complete the data update process for the business system. In this embodiment, the "master data code" unique key is used for update operations, while the composite key "master data code + version number" is used for modification operations to generate update operation instructions. This improves the matching accuracy of the business system's data update process and overcomes problems such as data matching errors and old data overwriting.

[0089] In one exemplary embodiment, step 205 includes:

[0090] When the update type of incremental data is a new addition, the interface service pushes the insertion command and master data code uniqueness verification rules to the business system. The uniqueness verification rules of the master data code are used to perform uniqueness verification processing in the business system, and the data insertion processing corresponding to the incremental data is performed according to the verification result of the uniqueness verification processing to obtain the data update result.

[0091] When the update type of incremental data is modification type, an update instruction is pushed to the business system through the interface service. The business system then performs the corresponding data modification processing of the incremental data using the master data code and version number carried in the update instruction, and obtains the data update result.

[0092] When the update type of incremental data is deletion, a deletion instruction is pushed to the business system through the interface service. The business system then executes the data deletion process corresponding to the incremental data using the master data code carried in the update instruction, and obtains the data update result.

[0093] For example, the data update processing performed by the service system for incremental data includes three processing types: data insertion processing, data modification processing, and data deletion processing.

[0094] In cases where the incremental data update type is "new", an insert command can be sent to the database interface of the business system via the interface service, carrying a "master data code uniqueness verification" rule. The business system will then perform uniqueness verification processing based on the master data code uniqueness verification rule, and perform the corresponding data insertion processing based on the verification result to obtain the data update result. If a record with the same master data code already exists in the business system, the command is skipped (to avoid duplicate insertion), and the skipped record is logged; otherwise, the insertion operation is performed.

[0095] When the incremental data update type is modification, the interface service sends an update command to the business system. The business system then performs the corresponding data modification processing based on the master data code and version number carried in the update command, resulting in a data update. Upon receiving the command, the business system first compares the version number recorded locally with the version number in the command: if the local version number is lower than the command version number (e.g., local version is 2, command version is 3), the update operation is executed; if the local version number is equal to or higher than the command version number, the process is skipped (to avoid old data overwriting new data), and a skip log is recorded.

[0096] When the update type of incremental data is deletion, the interface service sends a deletion command to the business system. The business system then uses the master data code carried in the update command to perform the corresponding data deletion process, obtaining the data update result. Upon receiving the command, the business system matches the local record based on the master data code, performs logical deletion (marking the "deletion status" as "deleted"), and records the deletion in the log.

[0097] In this embodiment, to address the issue of severe performance degradation in the business system during data updates, data updates are performed through update operation commands. The business system does not need to handle full data comparison; it only needs to perform precise operations based on the "master data encoding / composite primary key." This reduces database IO utilization by more than 60% and CPU load by 40%-70%, effectively ensuring the response speed of the business system.

[0098] In an exemplary embodiment, the method further includes: if the data update result indicates that the data update has failed, performing update retry processing corresponding to the data update result to obtain an update retry result; if the update retry result indicates that the update retry has succeeded, recording the number of retryes and the success time, and modifying the update identifier of the incremental data in the main data storage database accordingly; if the update retry result indicates that the update retry has failed, performing a data rollback operation corresponding to the update operation instruction, and generating alarm information corresponding to the update retry result.

[0099] For example, the solution of this application can also perform process monitoring on the data update process, monitor the interface push process in real time, record information such as "command sending status (success / failure), business system response status (success / failure), and execution time", and generate real-time monitoring logs (supporting visual viewing). If the push fails due to network jitter, business system interface failure, or other reasons, resulting in a data update failure, the system automatically triggers a retry mechanism. For example, the retry interval can be set to 5 seconds, with a total of 3 retries. Then, by executing the update retry processing corresponding to the data update result, the update retry result is obtained. If the retry is successful, the number of retryes and the success time can be directly recorded, and the subsequent process can continue to be executed, modifying the update identifier of the incremental data in the main data storage database accordingly. If the update retry result indicates that the update retry failed, the data rollback mechanism will be automatically triggered. This means that the operations already executed by the batch of instructions in the business system (such as deleting inserted records or rolling back updated records to the original version) will be undone. At the same time, an alarm message (such as SMS / email, including the failed master data code and the reason for failure) will be generated and sent to the master data administrator to promptly inform them of the update status of the master data. In this embodiment, the "version number verification + retry rollback" mechanism ensures that the data between the master data management platform and the business system is consistent, avoiding cross-system data conflicts.

[0100] In one embodiment, this application specifically uses a master data management platform to handle master data updates and business system synchronization updates. The data management platform includes five core modules: master data asset management module, master data publishing module, master data publishing review module, master data sharing, opening and monitoring module, and master data storage database module. The functions and collaboration mechanisms of each module are as follows:

[0101] Master data asset management module: Supports adding, deleting, and modifying master data resources, and provides a visual display interface to realize basic management of master data throughout its entire lifecycle;

[0102] Master data publishing module: Receives updated data output from the master data asset management module, generates master data publishing applications, and provides a data entry point for subsequent review processes;

[0103] Master data release review module: Operated by business personnel with review authority, this module verifies the compliance and accuracy of master data updates (additions, deletions, and modifications) in release requests and outputs the review approval / rejection results.

[0104] Master data sharing, opening and monitoring module: responsible for the dynamic management of shared service APIs (automatically creating APIs when adding master data, and dynamically updating API data content when modifying / deleting master data), implementing real-time push of API services based on configuration, and monitoring the execution results of the sharing process, including exception retry and rollback mechanisms;

[0105] Master data storage database module: Adopting a relational database architecture, it stores the master data provided to the outside world. It is designed with a two-field marking mechanism of "version number + update status" to realize unified storage, incremental identification and consistency management of master data.

[0106] By leveraging inter-module collaboration and incremental update mechanisms, the existing master data management platform addresses issues such as "update delays, large data volumes, and high performance overhead," enabling real-time sharing of master data with business systems and providing data support for efficient business collaboration.

[0107] The database update flowchart for master data in the master data management platform can be referenced. Figure 3 As shown, through the collaboration of the master data asset management module, master data publishing module, master data publishing review module, and master data storage database module, the recording and marking of master data addition, deletion, and modification operations are completed. The core steps of this process include:

[0108] 1. Master data addition operation

[0109] Physical model creation: In the master data storage database, create a corresponding physical data table based on the business attributes of the newly added master data (such as customer data containing "customer code, customer name, contact information"). The table structure must contain the fields "master data code (string type, length 32 characters, globally unique), version number (integer type, initial value 1), update status (boolean type, value Y / N), creation time, operator".

[0110] Data import: The master data management platform provides two import methods: one is to support the import of standard CSV / Excel format files (with "format verification, field integrity verification, and master data code uniqueness verification" triggered before import) and the other is manual entry (entry through a visual form, with real-time field format verification).

[0111] Field marking: After the data import is complete, the "Version Number" of the newly added master data record in the master data storage database is set to 1, and the "Update Status" is set to Y, and the creation time and operator information are recorded synchronously.

[0112] 2. Master data modification operations

[0113] Operation trigger: Only users with master data modification permissions are allowed to modify existing master data records individually or in batches in the visualization interface of the master data asset management module (field-level modification is supported, such as updating customer contact information).

[0114] Field Update: After the modification operation is submitted, the "Version Number" of the corresponding record in the master data storage database is increased by 1 based on the original value (e.g., if the original version number is 2, it becomes 3 after modification), the "Update Flag" is assigned the value Y, and the operation time and operator information are updated synchronously.

[0115] 3. Master data deletion operation

[0116] Logical deletion trigger: When a user with master data deletion permissions initiates a master data deletion request in the master data asset management module, the system first performs logical deletion (i.e., marks the "deletion status" field as "deleted" while retaining the data record for traceability).

[0117] Field marking: After logical deletion is completed, the "Version Number" of the corresponding record in the main data storage database is assigned a value of 0, and the "Update Status" is assigned a value of Y, and the deletion time and operator information are recorded synchronously.

[0118] 4. Master data publishing operation

[0119] After completing the operations of adding, deleting, or modifying master data, users need to select the master data record marked with "Update ID = Y" in the master data publishing module, generate a unified "Master Data Publishing Application Form" (including update type, master data code list, operation time, etc.), and submit it to the review stage.

[0120] 5. Master data release review process

[0121] Review access control: Only business personnel with "master data review permissions" (such as data administrators) in the master data management platform can receive and publish application forms;

[0122] Review logic: Reviewers view the master data update details (including comparison of fields before and after addition, deletion, and modification) in the release application form through the master data release review module interface. If it meets the business rules (such as the addition of a customer code conforming to the enterprise coding standard), the review is approved; if it does not meet the rules, it is rejected and the reason for rejection is filled in (and simultaneously fed back to the applicant user).

[0123] Review result feedback: The results of the review being approved or rejected are synchronized to the master data publishing module in real time, and the applicant can view them in real time.

[0124] 6. Main data storage database data update

[0125] Once the application is approved, the main data storage database module automatically performs data updates: new records are confirmed to be stored, modified records are confirmed to have their version number updated, and deleted records are confirmed to have their version number set to 0. At the same time, the "update status flag" of the batch of records is locked (to prevent duplicate publication).

[0126] The flowchart for real-time updates of business system data by the master data management platform can be found by referring to... Figure 4 As shown, through the master data sharing, opening, and monitoring module, incremental data with "Update ID = Y" in the master data storage database is pushed to the business system in real time. The core steps are as follows:

[0127] 1. Incremental data extraction from the master data sharing open module

[0128] Triggering mechanism: A dual triggering mode of "event-driven + timed scanning" is adopted. First, when the "whether to update flag" in the main data storage database changes from N to Y, incremental extraction is automatically triggered. Second, records with "whether to update flag = Y" are scanned every 10 seconds to prevent missed extraction.

[0129] Data filtering: The extraction logic is to "filter all records in the master data storage database with 'whether to update flag = Y'", and classify them by "update type" (add / modify / delete) to generate an incremental data set (containing core information such as master data code, version number, field value, and update type).

[0130] 2. Incremental data is pushed to the business system.

[0131] The master data sharing and open module generates corresponding operation instructions based on the preset API service configuration (each business system has an independent API interface, and interface authentication and field mapping have been completed in advance), and pushes them to the business systems according to the update type.

[0132] (1) Add master data push

[0133] Instruction generation: For "new" type records in the incremental data set, generate an "insert instruction" (containing complete field values, with "master data code" as the primary key);

[0134] Push logic: The API service sends an insert command to the database interface of the business system, along with a "master data code uniqueness verification" rule; if a record with the same master data code already exists in the business system, the command is skipped (to avoid duplicate insertion), and the skipped record is logged; if the record does not exist, the insert operation is performed.

[0135] (2) Modify master data push

[0136] Command generation: For records of type "modification", generate an "update command" (including master data code, new field value, and "master data code + version number" as a composite primary key);

[0137] Push logic: The API service sends an update command to the business system. After receiving the command, the business system first compares the version number recorded locally with the version number in the command. If the local version number is lower than the command version number (e.g., the local version is 2 and the command version is 3), the update operation is performed. If the local version number is equal to or higher than the command version number, the operation is skipped (to avoid old data overwriting new data), and the skip log is recorded.

[0138] (3) Delete master data push

[0139] Command generation: For records of type "delete", generate a "delete command" (including master data code, with "master data code" as the unique matching field);

[0140] Push logic: The API service sends a deletion command to the business system. After receiving the command, the business system matches the local record with the master data code, performs logical deletion (marks the "deletion status" as "deleted"), and records the deletion log.

[0141] 3. Master data sharing, open monitoring, and data cleanup operations.

[0142] (1) Real-time monitoring

[0143] Process monitoring: The master data sharing and monitoring module monitors the API push process in real time, recording information such as "command sending status (success / failure), business system response status (success / failure), and execution time", and generating real-time monitoring logs (supporting visual viewing);

[0144] Error handling: If the push fails due to network jitter, business system interface failure, or other reasons, the system will automatically trigger a retry mechanism: the retry interval is set to 5 seconds, and a total of 3 retries will be made;

[0145] Successful retry: Record the number of retries and the time of success, and continue with the subsequent process;

[0146] Retry failure: Automatically triggers the rollback mechanism, which undoes the operations already executed by the batch of instructions in the business system (such as deleting inserted records or rolling back updated records to the original version), and sends an alarm message to the master data administrator (such as SMS / email, including the failed master data code and the reason for failure).

[0147] (2) Data cleanup of the main data storage database

[0148] After the push process retry is successful or succeeds on the first try, the master data sharing, access, and monitoring module sends a "data cleanup command" to the master data storage database module:

[0149] Delete records with "Version Number = 0" (i.e., records that have been deleted and pushed by the business system, achieving physical deletion and releasing storage resources);

[0150] Change the "Update Flag" setting for all successfully pushed records from Y to N (to avoid duplicate extraction and push).

[0151] The interaction logic between various modules on the platform specifically includes:

[0152] Signal / Information Transmission: Data interaction between modules is achieved through RESTful API interfaces, with HTTPS as the transmission protocol (to ensure data security) and JSON as the data format;

[0153] Data consistency assurance: Critical operations (such as approval and successful push) adopt a "transaction mechanism", that is, if a step fails, the preceding steps are automatically rolled back to prevent data inconsistency;

[0154] Log management: All operations (add, delete, modify, publish, approve, push) generate detailed logs, which are stored in an independent log database and retained for no less than 1 year (for problem tracing).

[0155] This invention is applicable to various enterprises with multiple business systems, and is particularly suitable for the following scenarios:

[0156] Enterprises that update their master data frequently (such as retail companies that add a large amount of customer data every day, and manufacturing companies that update product inventory data every day).

[0157] For enterprises with high requirements for master data consistency (such as financial enterprises for customer information synchronization, and e-commerce enterprises for order and inventory data linkage).

[0158] Large enterprises with a large number of business systems (such as group enterprises with more than 10 business systems such as ERP, CRM, and supply chain systems).

[0159] In these practical application scenarios, this application can be used to precisely solve the following four core technical problems:

[0160] Solving the "master data update latency" problem: By using an "incremental push + event-driven" mechanism, the master data update latency is reduced from the "hours" of existing technologies to the "seconds" (≤5 seconds), meeting the needs of real-time business scenarios;

[0161] Solving the problem of "high data transmission cost": Only push incremental data with "whether to update identifier = Y", reducing the data transmission volume to 5%-10% of the existing technology, and significantly reducing network bandwidth usage;

[0162] Solving the problem of "severe performance loss in business systems": Business systems no longer need to handle full data comparison, but only need to perform precise operations based on "master data encoding / composite primary key", database IO utilization rate is reduced by more than 60%, CPU load is reduced by 40%-70%, and business system response speed is guaranteed;

[0163] To address the issue of "insufficient data consistency assurance": a "version number verification + retry rollback" mechanism is used to ensure data consistency between the master data management platform and business systems, avoiding cross-system data conflicts.

[0164] This application solves the problem of full data transmission by designing a dual-field marking mechanism of "version number + update status identifier": the version number enables control over the order of master data updates (avoiding the overwriting of old data), and the update status identifier enables accurate extraction of incremental data.

[0165] By constructing an update mode of "incremental push + composite primary key matching": new data uses the master data code as the unique key, and modified data uses "master data code + version number" as the composite key, accurate operation of business systems is achieved and performance loss is reduced;

[0166] By developing a "retry-rollback-data cleanup" linkage mechanism: retries resolve network anomalies, rollbacks ensure data consistency, and data cleanup releases storage resources, forming a complete closed loop for anomaly handling;

[0167] By implementing a multi-module collaborative process—seamlessly connecting master data asset management, publishing, review, and sharing open modules—the entire process of master data updates, from initiation to push, is controllable and traceable.

[0168] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0169] Based on the same inventive concept, this application also provides a data update apparatus for implementing the data update method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more data update apparatus embodiments provided below can be found in the limitations of the data update method described above, and will not be repeated here.

[0170] In one exemplary embodiment, such as Figure 5 As shown, a data update device is provided, comprising:

[0171] The incremental data extraction module 502 is used to extract incremental data from the main data storage database based on the update identifier when an update identifier is detected indicating that data has been updated in the main data storage database.

[0172] The instruction generation module 504 is used to generate update operation instructions corresponding to the incremental data based on the update type of the incremental data.

[0173] The instruction push module 506 is used to push update operation instructions to the business system through the interface service, so that the business system can perform data update processing corresponding to the incremental data and obtain the data update result.

[0174] The identifier update module 508 is used to modify the update identifier of incremental data in the main data storage database when the data update result indicates that the data update is complete.

[0175] In one embodiment, the system further includes a master data update module, configured to: upon receiving a master data update request, obtain master data release application information corresponding to the master data update request; perform release review processing on the master data release application information and obtain review result information corresponding to the master data release application information; and, if the review result information indicates that the review has been passed, perform incremental master data update processing on the master data storage database based on the master data release application information.

[0176] In one embodiment, master data update processing includes master data addition processing, master data modification processing, and master data deletion processing.

[0177] The master data update module is specifically used for:

[0178] When the master data release application information represents data update processing as master data addition processing, the physical data table, version number identifier, and update identifier of the incremental data corresponding to the master data release application information are searched in the master data storage database. Based on the physical data table, version number identifier, and update identifier, the master data addition processing corresponding to the incremental data is performed.

[0179] When the master data release application information represents data update processing as master data modification processing, the version number identifier and update identifier of the incremental data corresponding to the master data release application information are searched in the master data storage database, and the master data modification processing corresponding to the incremental data is performed based on the version number identifier and update identifier.

[0180] When the master data release application information represents data update processing as master data deletion processing, the version number identifier and update identifier of the incremental data corresponding to the master data release application information are searched in the master data storage database, and the master data deletion processing corresponding to the incremental data is performed based on the version number identifier and update identifier.

[0181] In one embodiment, the update types include add type, modify type and delete type, and the update operation instructions include insert instruction, update instruction and delete instruction.

[0182] The instruction generation module 504 is specifically used for: when the update type of incremental data is an insert type, identifying the primary data code of the incremental data and generating an insert instruction using the primary data code as the primary key; when the update type of incremental data is a modification type, identifying the primary data code and version number of the incremental data and generating an update instruction using the primary data code and version number as the combined primary key; and when the update type of incremental data is a modification type, identifying the primary data code of the incremental data and generating a delete instruction using the primary data code as the matching field.

[0183] In one embodiment, the instruction push module 506 is specifically used for:

[0184] When the update type of incremental data is a new addition, the interface service pushes the insertion command and master data code uniqueness verification rules to the business system. The uniqueness verification rules of the master data code are used to perform uniqueness verification processing in the business system, and the data insertion processing corresponding to the incremental data is performed according to the verification result of the uniqueness verification processing to obtain the data update result.

[0185] When the update type of incremental data is modification type, an update instruction is pushed to the business system through the interface service. The business system then performs the corresponding data modification processing of the incremental data using the master data code and version number carried in the update instruction, and obtains the data update result.

[0186] When the update type of incremental data is deletion, a deletion instruction is pushed to the business system through the interface service. The business system then executes the data deletion process corresponding to the incremental data using the master data code carried in the update instruction, and obtains the data update result.

[0187] In one embodiment, the system further includes an update retry module, configured to: if the data update result indicates that the data update has failed, perform update retry processing corresponding to the data update result to obtain an update retry result; if the update retry result indicates that the update retry has succeeded, record the number of retryes and the success time, and modify the update identifier of the incremental data in the main data storage database accordingly; if the update retry result indicates that the update retry has failed, perform a data rollback operation corresponding to the update operation instruction, and generate alarm information corresponding to the update retry result.

[0188] Each module in the aforementioned data update device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0189] In one exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 6 As shown, this computer device includes a processor, memory, input / output interfaces (I / O), and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores XX data. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When the computer program is executed by the processor, it implements a data update method.

[0190] Those skilled in the art will understand that Figure 6The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0191] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0192] In one embodiment, a computer-readable storage medium is provided storing a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0193] In one embodiment, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and executes the computer instructions, causing the computer device to perform the steps in the above method embodiments.

[0194] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0195] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0196] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0197] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A data update method, characterized in that, The method includes: If an update identifier is detected in the main data storage database indicating that data has been updated, incremental data is extracted from the main data storage database based on the update identifier. Generate an update operation instruction corresponding to the incremental data based on the update type of the incremental data; The update operation instruction is pushed to the business system through the interface service, so that the data update processing corresponding to the incremental data is executed in the business system to obtain the data update result; When the data update result indicates that the data update is complete, the update identifier of the incremental data in the main data storage database is modified accordingly.

2. The method according to claim 1, characterized in that, The method further includes: Upon receiving a master data update request, obtain the master data release application information corresponding to the master data update request; The master data release application information is reviewed and approved to obtain the review result information corresponding to the master data release application information. If the audit result information indicates that the audit has been approved, the master data storage database is updated with incremental data based on the master data release application information.

3. The method according to claim 2, characterized in that, The master data update process includes master data addition processing, master data modification processing, and master data deletion processing; The incremental data update process for the master data storage database based on the master data release application information includes: When the master data release application information characterizes the data update processing as master data addition processing, the physical data table, version number identifier, and update identifier of the incremental data corresponding to the master data release application information are searched in the master data storage database, and the master data addition processing corresponding to the incremental data is performed according to the physical data table, the version number identifier, and the update identifier. When the master data release application information characterizes the data update processing as master data modification processing, the version number identifier and update identifier of the incremental data corresponding to the master data storage database are searched in the master data storage database, and the master data modification processing corresponding to the incremental data is performed according to the version number identifier and the update identifier. When the master data release application information represents data update processing as master data deletion processing, the version number identifier and update identifier of the incremental data corresponding to the master data release application information are searched in the master data storage database, and the master data deletion processing corresponding to the incremental data is performed according to the version number identifier and the update identifier.

4. The method according to claim 3, characterized in that, The update types include add type, modify type and delete type, and the update operation instructions include insert instruction, update instruction and delete instruction; The step of generating the update operation instruction corresponding to the incremental data based on the update type of the incremental data includes: When the update type of the incremental data is an addition type, the master data code of the incremental data is identified, and an insertion instruction is generated using the master data code as the primary key. When the update type of the incremental data is a modification type, identify the master data code and version number of the incremental data, and generate an update instruction using the master data code and the version number as a joint primary key; When the update type of the incremental data is a modification type, the master data code of the incremental data is identified, and a deletion instruction is generated using the master data code as the matching field.

5. The method according to claim 4, characterized in that, The step of pushing update operation instructions to the business system through the interface service, so that the business system can perform data update processing corresponding to the incremental data, and obtain data update results include: When the update type of the incremental data is a new addition type, the insertion instruction and the master data code uniqueness verification rule are pushed to the business system through the interface service. The uniqueness verification rule of the master data code is used to perform uniqueness verification processing in the business system, and the data insertion processing corresponding to the incremental data is performed according to the verification result of the uniqueness verification processing to obtain the data update result. When the update type of the incremental data is modification type, the update instruction is pushed to the business system through the interface service, so that the data modification processing corresponding to the incremental data is performed in the business system through the master data code and version number carried by the update instruction, and the data update result is obtained. When the update type of the incremental data is deletion, the deletion instruction is pushed to the business system through the interface service. The business system then performs the data deletion process corresponding to the incremental data using the master data code carried by the update instruction, and obtains the data update result.

6. The method according to any one of claims 1 to 5, characterized in that, Also includes: If the data update result indicates that the data update has failed, perform the update retry process corresponding to the data update result to obtain the update retry result; If the update retry result indicates that the update retry was successful, the number of retryes and the success time are recorded, and the update identifier of the incremental data in the main data storage database is modified accordingly. If the update retry result indicates that the update retry has failed, the data rollback operation corresponding to the update operation instruction is executed, and an alarm message corresponding to the update retry result is generated.

7. A data update device, characterized in that, The device includes: The incremental data extraction module is used to extract incremental data from the main data storage database based on the update identifier when an update identifier is detected indicating that data has been updated in the main data storage database. The instruction generation module is used to generate update operation instructions corresponding to the incremental data based on the update type of the incremental data; The instruction push module is used to push update operation instructions to the business system through the interface service, so as to perform data update processing corresponding to the incremental data in the business system and obtain data update results. The identifier update module is used to modify the update identifier of the incremental data in the main data storage database when the data update result indicates that the data update is complete.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images