Synchronization Method, System, Device and Storage Medium for ERP Data

Abstract

The present invention relates to the field of data synchronization, and discloses a method, system, device and storage medium for synchronizing ERP data. The method includes: a first ERP distributed system sends an ERP data modification request; the ERP blockchain system receives the ERP data modification request and reads the request parameters corresponding to the ERP data modification request; according to the request parameters, the preset ERP data blockchain is modified to obtain a new ERP data blockchain; the second ERP distributed system reads the request time of the ERP data modification request and generates a block index request based on the request time; the ERP blockchain system receives the block index request, performs a retrieval process on the preset ERP data blockchain to obtain query modification parameters; the second ERP distributed system receives the query modification parameters and reads the request parameters of the ERP data modification request; determines whether the query modification parameters are consistent with the modification request parameters; if they are inconsistent, the ERP data modification request is placed in the preset polling queue; if they are consistent, the request parameters corresponding to the ERP data modification request are modified.

Description

Technical Field

[0001] The present invention relates to the field of data synchronization, and in particular, to a method, system, device, and storage medium for synchronizing ERP data. Background Art

[0002] As a financial processing system, ERP has been increasingly applied to the daily work of each finance department. As an efficient and convenient data system, the ERP system can quickly export various types of data and information. A data table with hundreds of thousands of records can be retrieved from the database within a few minutes.

[0003] However, the current ERP financial processing system is a distributed data system, and there is a certain delay in data modification between each ERP database. It is unlikely for the ERP database in location A to export data from the database in location B. The reason is that data corruption may occur during long-distance data transmission. The database information modified at 0:00 in location A may take several minutes to be synchronized to the database in location B. If data needs to be exported at this time, the data modified at this moment will be lost. For databases with general low timeliness requirements, it can be tolerated, but financial type databases involve major asset issues and cannot handle database latency problems.

[0004] Therefore, in view of the data synchronization delay problem caused by the current ERP distributed database during the data processing process, a new synchronization technology is needed. Summary of the Invention

[0005] The main objective of the present invention is to solve the technical problem of data synchronization delay caused by the current ERP distributed database during the data processing process.

[0006] The first aspect of the present invention provides a method for synchronizing ERP data. The method for synchronizing ERP data is applied to the ERP data synchronization system. The ERP data synchronization system includes: a first ERP distribution system, a second ERP distribution system, and an ERP blockchain system. The method for synchronizing ERP data includes:

[0007] The first ERP distribution system sends an ERP data modification request to the second ERP distribution system and the ERP blockchain system;

[0008] The ERP blockchain system receives the ERP data modification request and reads the request parameters corresponding to the ERP data modification request;

[0009] According to the request parameters, modify the pre-set ERP data blockchain to obtain a new ERP data blockchain;

[0010] The second ERP distribution system receives the ERP data modification request, reads the request time of the ERP data modification request, generates a block index request based on the request time, and sends the block index request to the ERP blockchain system;

[0011] The ERP blockchain system receives the block index request, retrieves and processes the pre-set ERP data blockchain according to the block index request to obtain query modification parameters, and sends the query modification parameters to the second ERP distribution system;

[0012] The second ERP distribution system receives the query modification parameters and reads the request parameters of the ERP data modification request;

[0013] Judge whether the query modification parameters are consistent with the modification request parameters;

[0014] If they are inconsistent, place the ERP data modification request in the pre-set polling queue;

[0015] If they are consistent, modify the request parameters corresponding to the ERP data modification request.

[0016] Optionally, in the first implementation manner of the first aspect of the present invention, the ERP blockchain system receives the ERP data modification request, and reading the request parameters corresponding to the ERP data modification request includes:

[0017] The ERP blockchain system receives the ERP data modification request and reads the ERP data subject and the subject adjustment quantity of the ERP data modification request.

[0018] Optionally, in the second implementation manner of the first aspect of the present invention, modifying the pre-set ERP data blockchain according to the request parameters to obtain a new ERP data blockchain includes:

[0019] Judge whether the ERP data modification request conforms to the pre-set modification rules according to the ERP data subject and the subject adjustment quantity;

[0020] If it conforms to the modification rules, read the request time of the ERP data modification request, read the pre-set ERP data blockchain, set the request time as the block name, and perform on-chain processing on the ERP data subject and the subject adjustment quantity to obtain a new ERP data blockchain.

[0021] Optionally, in the third implementation manner of the first aspect of the present invention, judging whether the ERP data modification request conforms to the pre-set modification rules according to the ERP data subject and the subject adjustment quantity includes:

[0022] Determine whether the ERP data subject is a preset subject;

[0023] If it is not a preset subject, determine that the ERP data modification request does not conform to the preset modification rule;

[0024] If it is a preset subject, determine whether the subject adjustment quantity meets the preset constraint conditions;

[0025] If the constraint conditions are not met, determine that the ERP data modification request does not conform to the preset modification rule;

[0026] If the constraint conditions are met, determine that the ERP data modification request conforms to the preset modification rule.

[0027] Optionally, in the fourth implementation manner of the first aspect of the present invention, the extracting the data of the retrieval result to obtain query modification parameters includes:

[0028] Determine whether the data of the retrieval result is empty;

[0029] If it is empty, determine the blank data as the query modification parameter;

[0030] If it is not empty, extract the ERP data subject and the subject adjustment quantity in the retrieval result to obtain the query modification parameter.

[0031] Optionally, in the fifth implementation manner of the first aspect of the present invention, the retrieving and processing the preset ERP data blockchain according to the block index request to obtain query modification parameters includes:

[0032] Read the request time in the block index request, use the request time as the block name, and perform retrieval processing on the preset ERP data blockchain to obtain a retrieval result;

[0033] Extract the data of the retrieval result to obtain the query modification parameter.

[0034] Optionally, in the sixth implementation manner of the first aspect of the present invention, after placing the ERP data modification request in the preset polling queue, it further includes:

[0035] Analyze the polling duration of the ERP data modification request in the polling queue, and determine whether the polling duration exceeds a preset alarm threshold;

[0036] If it exceeds the preset alarm threshold, send an alarm message to the management port and remove the ERP data modification request from the polling queue.

[0037] The second aspect of the present invention provides an ERP data synchronization system, and the ERP data synchronization system includes:

[0038] The first ERP distributed system, the second ERP distributed system, and the ERP blockchain system;

[0039] The first ERP distributed system is used to send an ERP data modification request to the second ERP distributed system and the ERP blockchain system;

[0040] The ERP blockchain system is used to receive the ERP data modification request and read the request parameters corresponding to the ERP data modification request;

[0041] Modify the preset ERP data blockchain according to the request parameters to obtain a new ERP data blockchain;

[0042] The second ERP distributed system is used to receive the ERP data modification request, read the request time of the ERP data modification request, generate a block index request based on the request time, and send the block index request to the ERP blockchain system;

[0043] The ERP blockchain system is used to receive the block index request, perform a retrieval process on the preset ERP data blockchain according to the block index request to obtain query modification parameters, and send the query modification parameters to the second ERP distributed system;

[0044] The second ERP distributed system is used to receive the query modification parameters and read the request parameters of the ERP data modification request;

[0045] Determine whether the query modification parameters are consistent with the modification request parameters;

[0046] If they are inconsistent, place the ERP data modification request in a preset polling queue;

[0047] If they are consistent, modify the request parameters corresponding to the ERP data modification request.

[0048] The third aspect of the present invention provides an ERP data synchronization device, including: a memory and at least one processor, instructions are stored in the memory, and the memory and the at least one processor are interconnected by a line; the at least one processor invokes the instructions in the memory so that the ERP data synchronization device executes the above-mentioned ERP data synchronization method.

[0049] The fourth aspect of the present invention provides a computer-readable storage medium, instructions are stored in the computer-readable storage medium, and when it runs on a computer, it causes the computer to execute the above-mentioned ERP data synchronization method.

[0050] In an embodiment of the present invention, in order to ensure the secure transmission of information in a distributed ERP database, a blockchain is used as the standard for data synchronization. During the process of transmitting and synchronizing data, the information in the blockchain during the information transmission process can be fixed, and the request information for modifying data can be displayed in the polling queue, comprehensively managing the information transmission speed and information accuracy. This not only solves the problem of data synchronization delay caused by the current ERP distributed database during the data processing process, but also solves the problem of untimely transmission of operation information due to slow data confirmation. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] Figure 1 FIG. is a schematic diagram of an embodiment of the ERP data synchronization method in an embodiment of the present invention;

[0052] Figure 2 FIG. is a schematic diagram of an embodiment of the ERP data synchronization system in an embodiment of the present invention;

[0053] Figure 3 FIG. is a schematic diagram of another embodiment of the ERP data synchronization system in an embodiment of the present invention;

[0054] Figure 4 FIG. is a schematic diagram of an embodiment of the ERP data synchronization device in an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0055] The embodiments of the present invention provide a method, system, device, and storage medium for synchronizing ERP data.

[0056] The terms "first", "second", "third", "fourth", etc. (if any) in the specification, claims, and above-mentioned drawings of the present invention are used to distinguish similar objects and do not necessarily need to describe a specific order or sequence. It should be understood that such used data can be interchanged under appropriate circumstances so that the embodiments described herein can be implemented in an order different from that illustrated or described herein. In addition, the terms "comprising" or "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units does not necessarily need to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products, or devices.

[0057] For ease of understanding, the following describes the specific process of the embodiments of the present invention. Please refer to Figure 1 , an embodiment of the ERP data synchronization method in an embodiment of the present invention. The ERP data synchronization method is applied to an ERP data synchronization system, which includes: a first ERP distribution system, a second ERP distribution system, and an ERP blockchain system. The ERP data synchronization method includes:

[0058] 101. The first ERP distribution system sends an ERP data modification request to the second ERP distribution system and the ERP blockchain system;

[0059] 102. The ERP blockchain system receives the ERP data modification request and reads the request parameters corresponding to the ERP data modification request;

[0060] 103. According to the request parameters, modify the preset ERP data blockchain to obtain a new ERP data blockchain;

[0061] In steps 101 - 103, the first ERP distribution system simultaneously sends an ERP data modification request to the second ERP distribution system and the ERP blockchain system. In order to synchronize the request operation of modifying data in the first ERP distribution system while confirming the synchronized data to the second ERP distribution system, and avoid information isolation in operations between the two distribution systems.

[0062] The ERP blockchain system modifies the ERP data subjects and data change amounts in the ERP data blockchain according to the data modification request of the first ERP distribution system as the determined information source. However, in order to ensure that the second ERP distribution system can synchronously know the processing process of the first ERP distribution system, it will not perform data synchronization after determining the blockchain modification, but execute simultaneously.

[0063] Further, in 102, the following steps can be executed:

[0064] 1021. The ERP blockchain system receives the ERP data modification request and reads the ERP data subjects and subject adjustment quantities of the ERP data modification request.

[0065] In this embodiment, the ERP data modification request includes the time when the request is sent, the ERP data subjects, and the subject adjustment data. First, read the ERP data subjects and subject adjustment quantities. For example: for the "tax" subject, increase by 10,000 quantity units.

[0066] Further, in 103, the following steps can be executed:

[0067] 1031. According to the ERP data subjects and subject adjustment quantities, determine whether the ERP data modification request conforms to the preset modification rules;

[0068] 1032. If it conforms to the modification rules, then read the request time of the ERP data modification request, read the preset ERP data blockchain, set the request time as the block name, and perform on-chain processing on the ERP data subjects and subject adjustment quantities to obtain a new ERP data blockchain.

[0069] In steps 1031 and 1032, if the "tax" account decreases by 10,000 quantity units and the current amount of the "tax" account itself is 800, and a decrease of 10,000 quantity units results in a negative number, and the modification rule does not allow "tax" to be less than zero, it means that it does not conform to the modification rule and no data adjustment is performed.

[0070] If the "tax" account increases by 10,000 quantity units and meets the modification rule, then the request time of the ERP data modification request is "XXXX.01.25 00:00", the "XXXX.01.25 00:00" is determined as the block name, and the "tax" account is increased by 10,000 quantity units for on-chain processing to obtain a new ERP data blockchain.

[0071] Further, the following steps can be executed in 1031:

[0072] 10311. Determine whether the ERP data account is a preset account;

[0073] 10312. If it is not a preset account, then determine that the ERP data modification request does not conform to the preset modification rule;

[0074] 10313. If it is a preset account, then determine whether the account adjustment quantity meets the preset constraint conditions;

[0075] 10314. If the constraint conditions are not met, then determine that the ERP data modification request does not conform to the preset modification rule;

[0076] 10315. If the constraint conditions are met, then determine that the ERP data modification request conforms to the preset modification rule.

[0077] In steps 10311 - 10315, first judge whether the "tax" account is an account that can be put on the chain. If the "tax" account is not set in the on-chain accounts, then directly determine that the ERP data modification request does not conform to the preset modification rule.

[0078] If "purchase computer" is an account that can be put on the chain, then judge whether the account adjustment quantity corresponding to "purchase computer" meets the preset rule. The account adjustment quantity is "+105.7", and the constraint condition for "purchase computer" is that the account adjustment quantity cannot be a decimal and must be greater than zero, so it is determined that the ERP data modification request does not conform to the preset modification rule. However, if the account adjustment quantity is "+105" and meets the constraint conditions, then it is determined that the ERP data modification request conforms to the preset modification rule.

[0079] 104. The second ERP distribution system receives an ERP data modification request, reads the request time of the ERP data modification request, generates a block index request based on the request time, and sends the block index request to the ERP blockchain system;

[0080] 105. The ERP blockchain system receives the block index request, retrieves and processes the pre-set ERP data blockchain according to the block index request to obtain query modification parameters, and sends the query modification parameters to the second ERP distribution system;

[0081] In steps 104 and 105, the second ERP distribution system receives an ERP data modification request, needs to generate a block index request based on the request time as an index condition, and sends the block index request to the ERP blockchain system.

[0082] Further, the following steps can be executed in 105:

[0083] 1051. Read the request time in the block index request, use the request time as the block name, retrieve and process the pre-set ERP data blockchain to obtain a retrieval result;

[0084] 1052. Extract the data of the retrieval result to obtain query modification parameters.

[0085] In steps 1051 and 1052, the request time in the block index request is "XXXX.01.25 00:00". Under the block name of "XXXX.01.25 00:00", retrieve and process the ERP data blockchain. The ERP data blockchain controls the uniqueness of each block with the time as the block name. The blockchain retrieval of "XXXX.01.25 00:00" may be empty or there may be specific accounts and account modification quantities. Then, extract the data of the retrieval result to obtain query modification parameters (which may have specific quantities and accounts or may be empty).

[0086] Further, the following steps can be executed in 1052:

[0087] 10521. Determine whether the data of the retrieval result is empty;

[0088] 10522. If it is empty, determine the blank data as the query modification parameters;

[0089] 10523. If it is not empty, extract the ERP data accounts and account adjustment quantities in the retrieval result to obtain query modification parameters.

[0090] In steps 10521 - 10523, if the retrieval result is "null", the blank data is determined as the query modification parameter. If the retrieval result is not "null", it indicates that there is feedback data in the retrieval result, and the ERP data subject and the subject adjustment quantity in the retrieval result are extracted to obtain the query modification parameter.

[0091] 106. The second ERP distribution system receives the query modification parameter and reads the request parameter of the ERP data modification request;

[0092] 107. Determine whether the query modification parameter is consistent with the modification request parameter;

[0093] 108. If they are not consistent, place the ERP data modification request in the preset polling queue;

[0094] 109. If they are consistent, modify the request parameter corresponding to the ERP data modification request.

[0095] In steps 106 - 109, if there is an IP address substitution and the false first ERP distribution system sends the modification request parameter, it will cause the query modification parameter to be inconsistent with the modification request parameter. It may also be that the ERP blockchain system has not completed the on-chain process. At this time, there is a certain time delay. Place the ERP data modification request in the polling queue and poll every 5 minutes to check whether the on-chain process has been completed. If the on-chain process is completed, the query modification parameter is consistent with the modification request parameter, and the request parameter corresponding to the ERP data modification request is modified.

[0096] However, if the query modification parameter is consistent with the modification request parameter, it indicates that the ERP data modification request has been on-chain and is an accurate data, then modify the ERP data related to the database in the second ERP distribution system.

[0097] Furthermore, after step 108, the following steps can also be executed:

[0098] 1081. Analyze the polling duration of the ERP data modification request in the polling queue and determine whether the polling duration exceeds the preset alarm threshold;

[0099] 1082. If it exceeds the preset alarm threshold, send an alarm message to the management port and remove the ERP data modification request from the polling queue.

[0100] In steps 1081 - 1082, the polling duration of the ERP data modification request can be set to not exceed 50 minutes. If it exceeds 50 minutes, it is considered that the ERP data modification request has not been successfully on-chain and is an unqualified data, then stop polling to check the on-chain situation of the blockchain. Remove the ERP data modification request from the polling queue and it can be added to the abnormal adjustment data log for data security personnel to repair the data.

[0101] In the embodiment of the present invention, in order to ensure the secure transmission of information in the distributed ERP database, the blockchain is used as the standard for data synchronization. During the process of transmitting and synchronizing data, the information in the blockchain during the information transmission process can be fixed and the request information for modifying data can be displayed in the polling queue, so as to comprehensively manage the information transmission speed and information accuracy, which not only solves the data synchronization delay caused by the current ERP distributed database during the data processing process, but also solves the problem that the operation information transmission is not timely due to the slow data confirmation.

[0102] The above describes the ERP data synchronization method in the embodiment of the present invention. Next, the ERP data synchronization system in the embodiment of the present invention will be described. Please refer to Figure 2 An embodiment of the ERP data synchronization system in the embodiment of the present invention. The ERP data synchronization system includes:

[0103] The first ERP distribution system 201, the second ERP distribution system 202, and the ERP blockchain system 203;

[0104] The first ERP distribution system 201 is used to send an ERP data modification request to the second ERP distribution system and the ERP blockchain system;

[0105] The ERP blockchain system 203 is used to receive the ERP data modification request and read the request parameters corresponding to the ERP data modification request;

[0106] According to the request parameters, modify the preset ERP data blockchain to obtain a new ERP data blockchain;

[0107] The second ERP distribution system 202 is used to receive the ERP data modification request, read the request time of the ERP data modification request, generate a block index request based on the request time, and send the block index request to the ERP blockchain system;

[0108] The ERP blockchain system 203 is used to receive the block index request, perform a retrieval process on the preset ERP data blockchain according to the block index request to obtain query modification parameters, and send the query modification parameters to the second ERP distribution system;

[0109] The second ERP distribution system 202 is used to receive the query modification parameters and read the request parameters of the ERP data modification request;

[0110] Judge whether the query modification parameters are consistent with the modification request parameters;

[0111] If they are inconsistent, place the ERP data modification request in a preset polling queue;

[0112] If they are consistent, modify the request parameters corresponding to the ERP data modification request.

[0113] In the embodiments of the present invention, in order to ensure the secure transmission of information in the distributed ERP database, the blockchain is used as the standard for data synchronization. During the process of transmitting and synchronizing data, the information in the blockchain during the information transmission process can be fixed and the request information for modifying data can be displayed in the polling queue, and comprehensive management can be carried out on the information transmission speed and information accuracy, which not only solves the problem of data synchronization delay caused by the current ERP distributed database during the data processing process, but also solves the problem of untimely transmission of operation information caused by slow data confirmation.

[0114] Please refer to Figure 4 , another embodiment of the ERP data synchronization system in the embodiments of the present invention, the ERP data synchronization system includes:

[0115] The first ERP distribution system 201, the second ERP distribution system 202, and the ERP blockchain system 203;

[0116] The first ERP distribution system 201 is used to send an ERP data modification request to the second ERP distribution system and the ERP blockchain system;

[0117] The ERP blockchain system 203 is used to receive the ERP data modification request and read the request parameters corresponding to the ERP data modification request;

[0118] According to the request parameters, modify the preset ERP data blockchain to obtain a new ERP data blockchain;

[0119] The second ERP distribution system 202 is used to receive the ERP data modification request, read the request time of the ERP data modification request, generate a block index request based on the request time, and send the block index request to the ERP blockchain system;

[0120] The ERP blockchain system 203 is used to receive the block index request, perform a retrieval process on the preset ERP data blockchain according to the block index request to obtain query modification parameters, and send the query modification parameters to the second ERP distribution system;

[0121] The second ERP distribution system 202 is used to receive the query modification parameters and read the request parameters of the ERP data modification request;

[0122] Judge whether the query modification parameters are consistent with the modification request parameters;

[0123] If they are inconsistent, place the ERP data modification request in a preset polling queue;

[0124] If they are consistent, modify the request parameters corresponding to the ERP data modification request.

[0125] Among them, the ERP blockchain system 203 is specifically used for:

[0126] The ERP blockchain system receives the ERP data modification request and reads the ERP data subject and the subject adjustment quantity of the ERP data modification request.

[0127] Among them, the ERP blockchain system 203 is also specifically used for:

[0128] According to the ERP data subject and the subject adjustment quantity, determine whether the ERP data modification request conforms to a preset modification rule;

[0129] If it conforms to the modification rule, read the request time of the ERP data modification request, read the preset ERP data blockchain, set the request time as the block name, and perform an on-chain process on the ERP data subject and the subject adjustment quantity to obtain a new ERP data blockchain.

[0130] Among them, the ERP blockchain system 203 is also specifically used for:

[0131] Judge whether the ERP data subject is a preset subject;

[0132] If it is not a preset subject, determine that the ERP data modification request does not conform to the preset modification rule;

[0133] If it is a preset subject, judge whether the subject adjustment quantity meets the preset constraint conditions;

[0134] If the constraint conditions are not met, determine that the ERP data modification request does not conform to the preset modification rule;

[0135] If the constraint conditions are met, determine that the ERP data modification request conforms to the preset modification rule.

[0136] Among them, the ERP blockchain system 203 is also specifically used for:

[0137] Read the request time in the block index request, use the request time as the block name, and perform a retrieval process on the preset ERP data blockchain to obtain a retrieval result;

[0138] Extract the data of the retrieval result to obtain query modification parameters.

[0139] Among them, the ERP blockchain system 203 is further specifically configured to:

[0140] Determine whether the data in the retrieval result is empty;

[0141] If it is empty, determine the blank data as the query modification parameter;

[0142] If it is not empty, extract the ERP data subject and the subject adjustment quantity in the retrieval result to obtain the query modification parameter.

[0143] The ERP data synchronization system further includes a removal module 204, and the removal module 204 is specifically configured to:

[0144] Analyze the polling duration of the ERP data modification request in the polling queue, and determine whether the polling duration exceeds a preset alarm threshold;

[0145] If it exceeds the preset alarm threshold, send an alarm message to the management port and remove the ERP data modification request from the polling queue.

[0146] In the embodiment of the present invention, in order to ensure the secure transmission of information in the distributed ERP database, the blockchain is used as the standard for data synchronization. During the process of transmitting and synchronizing data, the information in the blockchain during the information transmission process can be fixed and the request information of the modified data can be displayed in the polling queue, so as to comprehensively manage the information transmission speed and information accuracy. It not only solves the problem of data synchronization delay caused by the current ERP distributed database during the data processing process, but also solves the problem of slow data confirmation resulting in untimely transmission of operation information.

[0147] Above Figure 2 And Figure 3 The synchronization system of the ERP data in the embodiment of the present invention is described in detail from the perspective of modular functional entities. Next, the synchronization device of the ERP data in the embodiment of the present invention will be described in detail from the perspective of hardware processing.

[0148] Figure 4FIG. 0 is a schematic structural diagram of an ERP data synchronization device provided by an embodiment of the present invention. The ERP data synchronization device 400 may vary greatly due to different configurations or performances, and may include one or more processors (central processing units, CPUs) 410 (for example, one or more processors) and a memory 420, and one or more storage media 430 for storing application programs 433 or data 432 (for example, one or more mass storage devices). Among them, the memory 420 and the storage media 430 may be transient storage or persistent storage. The program stored in the storage media 430 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations on the ERP data synchronization device 400. Further, the processor 410 may be configured to communicate with the storage media 430 and execute a series of instruction operations in the storage media 430 on the ERP data synchronization device 400.

[0149] Based on the ERP data synchronization device 400 may further include one or more power supplies 440, one or more wired or wireless network interfaces 450, one or more input / output interfaces 460, and / or, one or more operating systems 431, such as Windows Serve, Mac OS X, Unix, Linux, FreeBSD, and so on. Those skilled in the art can understand that Figure 4 The shown structure of the ERP data synchronization device does not constitute a limitation on the ERP data synchronization device, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0150] The present invention also provides a computer-readable storage medium. The computer-readable storage medium may be a non-volatile computer-readable storage medium, and the computer-readable storage medium may also be a volatile computer-readable storage medium. Instructions are stored in the computer-readable storage medium. When the instructions are run on a computer, the computer is caused to execute the steps of the ERP data synchronization method.

[0151] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the above-described system or system and unit can refer to the corresponding processes in the foregoing method embodiments, and will not be described herein again.

[0152] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical discs that can store program codes.

[0153] As described above, the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions described in the foregoing embodiments or perform equivalent replacements for some of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the various embodiments of the present invention.

Claims

1. A method for synchronizing ERP data, characterized in that, The synchronization method of the ERP data is applied to an ERP data synchronization system, which includes: a first ERP distributed system, a second ERP distributed system, and an ERP blockchain system. The synchronization method of the ERP data includes: The first ERP distributed system sends an ERP data modification request to the second ERP distributed system and the ERP blockchain system; The ERP blockchain system receives the ERP data modification request and reads the request parameters corresponding to the ERP data modification request; According to the request parameters, modify the pre-set ERP data blockchain to obtain a new ERP data blockchain; The second ERP distributed system receives the ERP data modification request, reads the request time of the ERP data modification request, generates a block index request based on the request time, and sends the block index request to the ERP blockchain system; The ERP blockchain system receives the block index request, performs a retrieval process on the pre-set ERP data blockchain according to the block index request to obtain query modification parameters, and sends the query modification parameters to the second ERP distributed system; The second ERP distributed system receives the query modification parameters and reads the request parameters of the ERP data modification request; Judge whether the query modification parameters are consistent with the modification request parameters; If they are inconsistent, place the ERP data modification request in the pre-set polling queue; If they are consistent, modify the request parameters corresponding to the ERP data modification request.

2. The method for synchronizing ERP data according to claim 1, characterized in that, The ERP blockchain system receives the ERP data modification request, and reading the request parameters corresponding to the ERP data modification request includes: The ERP blockchain system receives the ERP data modification request and reads the ERP data subject and the subject adjustment quantity of the ERP data modification request.

3. The method for synchronizing ERP data according to claim 2, characterized in that, The step of modifying the pre-set ERP data blockchain according to the request parameters to obtain a new ERP data blockchain includes: According to the ERP data subject and the subject adjustment quantity, judge whether the ERP data modification request conforms to the pre-set modification rules; If it conforms to the modification rules, read the request time of the ERP data modification request, read the pre-set ERP data blockchain, set the request time as the block name, and perform an on-chain process on the ERP data subject and the subject adjustment quantity to obtain a new ERP data blockchain.

4. The method for synchronizing ERP data according to claim 3, characterized in that, The step of judging whether the ERP data modification request conforms to the pre-set modification rules according to the ERP data subject and the subject adjustment quantity includes: Judge whether the ERP data subject is a preset subject; If it is not a preset subject, determine that the ERP data modification request does not conform to the pre-set modification rules; If it is a preset subject, judge whether the subject adjustment quantity meets the preset constraint conditions; If it does not meet the constraint conditions, determine that the ERP data modification request does not conform to the pre-set modification rules; If it meets the constraint conditions, determine that the ERP data modification request conforms to the pre-set modification rules.

5. The method for synchronizing ERP data according to claim 4, characterized in that, Performing a retrieval process on the preset ERP data blockchain according to the block index request to obtain query modification parameters, including: Reading the request time in the block index request, using the request time as the block name, performing a retrieval process on the preset ERP data blockchain to obtain a retrieval result; Extracting the data of the retrieval result to obtain query modification parameters.

6. The method for synchronizing ERP data according to claim 5, characterized in that, The extracting the data of the retrieval result to obtain query modification parameters includes: Determining whether the data of the retrieval result is empty; If it is empty, determining the blank data as the query modification parameter; If it is not empty, extracting the ERP data subject and the subject adjustment quantity in the retrieval result to obtain query modification parameters.

7. The method for synchronizing ERP data according to claim 1, characterized in that, After placing the ERP data modification request in the preset polling queue, it further includes: Analyzing the polling duration of the ERP data modification request in the polling queue and determining whether the polling duration exceeds a preset alarm threshold; If it exceeds the preset alarm threshold, sending an alarm message to the management port and removing the ERP data modification request from the polling queue.

8. A synchronization system for ERP data, characterized in that, The ERP data synchronization system includes: A first ERP distribution system, a second ERP distribution system, and an ERP blockchain system; The first ERP distribution system is used to send an ERP data modification request to the second ERP distribution system and the ERP blockchain system; The ERP blockchain system is used to receive the ERP data modification request and read the request parameters corresponding to the ERP data modification request; Modifying the preset ERP data blockchain according to the request parameters to obtain a new ERP data blockchain; The second ERP distribution system is used to receive the ERP data modification request, read the request time of the ERP data modification request, generate a block index request based on the request time, and send the block index request to the ERP blockchain system; The ERP blockchain system is used to receive the block index request, perform a retrieval process on the preset ERP data blockchain according to the block index request to obtain query modification parameters, and send the query modification parameters to the second ERP distribution system; The second ERP distribution system is used to receive the query modification parameters and read the request parameters of the ERP data modification request; Determining whether the query modification parameters are consistent with the modification request parameters; If they are not consistent, placing the ERP data modification request in the preset polling queue; If they are consistent, modifying the request parameters corresponding to the ERP data modification request.

9. A synchronization device for ERP data, characterized in that, The synchronization device for ERP data includes: a memory and at least one processor, wherein instructions are stored in the memory, and the memory and the at least one processor are interconnected by a line; The at least one processor calls the instructions in the memory so that the synchronization device for ERP data executes the ERP data synchronization method according to any one of claims 1-7.

10. A computer-readable storage medium, on which a computer program is stored, characterized in that, The computer program, when executed by a processor, implements the ERP data synchronization method according to any one of claims 1-7.

Images