Method and system for verification and cross-system synchronization of distributed data under applet

Abstract

A method and a system for verifying and synchronizing distributed data under an applet belong to the technical field of industrial internet and production, the method is executed by a manufacturing execution system, and the method comprises the following steps: receiving production execution data verified in real time by a mobile terminal; generating a production execution report and synchronizing the production execution report to an enterprise resource planning system to generate a process report; when report data is corrected, collaborative operation is triggered according to the generation state of a process report to maintain data consistency, and the system correspondingly comprises a data acquisition and verification terminal, a manufacturing execution system platform and an enterprise resource planning system platform to realize the collaborative operation. And an intelligent cross-system collaborative correction mechanism is constructed, so that the problems that data verification is lagged, cross-system synchronization is difficult and consistency is difficult to guarantee in traditional production are effectively solved.

Description

Technical Field

[0001] This invention relates to a method and system for data verification and cross-system synchronization under a mini-program, belonging to the field of industrial internet and production technology. Background Technology

[0002] In the wave of digital transformation in manufacturing, enterprises generally adopt MES systems to manage workshop production execution and ERP systems to coordinate enterprise resource planning. However, data collection on the production floor still heavily relies on manual entry into PCs or fixed industrial terminals, which is cumbersome, lacks real-time performance, and is difficult to adapt to the needs of flexible and mobile production management.

[0003] With the popularization of mobile internet technology, lightweight applications such as mini-programs have begun to penetrate industrial sites, providing front-line operators with a convenient data entry portal. However, in the process of realizing the data flow of "mini-program data collection - MES processing - ERP integration", the following significant technical problems exist: Data validation lag: Existing solutions typically place data validation in the backend system (MES or ERP), which results in invalid, overproduction, or incorrectly formatted data still entering the system after entry and being transmitted to downstream systems along the business chain such as production reporting, cost accounting, and planning and scheduling. The cost of subsequent investigation and correction is extremely high. Cross-system synchronization maintenance is difficult: MES and ERP systems usually synchronize data through timed batch processing or simple one-way interfaces, which lacks real-time and transactional guarantees. That is, when production data (such as the quantity completed) in MES changes due to error correction, the related business documents (such as process reports and cost vouchers) generated in ERP cannot be automatically synchronized or reversed, resulting in data inconsistency between the two systems and heavy reliance on manual verification and manual adjustment. On-site operations lack real-time guidance and error correction: Traditional mobile data collection applications only realize the data reporting function and do not put business rules (such as planned quantity verification and the reason for overproduction must be filled in) in advance at the moment of operation. This makes it easy for operators to enter data without knowing the compliance requirements in time, which not only makes it easy to make mistakes, but also increases the management burden of subsequent communication and explanation. Summary of the Invention

[0004] To address the shortcomings of existing technologies, the purpose of this invention is to provide a method and system for data verification and cross-system synchronization under a mini-program, in order to solve the technical problems of lack of real-time verification of existing production data at the source of collection and difficulty in automatically maintaining data consistency during cross-system synchronization.

[0005] To achieve the above objectives, the present invention provides a method for data verification and cross-system synchronization under a mini-program, which is executed by a manufacturing execution system and includes: Receiving and Integration Steps: Receive production execution data uploaded from the mobile terminal. The production execution data is associated with and used by the mobile terminal to generate orders based on the scanned schedule card barcode. The production execution data is also verified in real time. Report generation and synchronization steps: Based on the production execution data that has passed real-time verification, generate the corresponding production execution report, and synchronize the data in the report to the enterprise resource planning system to drive it to generate the associated process report; Data correction and collaboration steps: When modifying data in existing production execution reports, the corresponding collaboration operation is triggered based on the generation status of the process report in the enterprise resource planning system.

[0006] Furthermore, the mobile terminal is a mini-program that collects production execution data by scanning or manually entering the schedule card barcode.

[0007] Furthermore, the real-time verification includes a first verification and a second verification performed sequentially; The first verification is an information consistency verification, which includes: comparing the production execution data obtained from the scheduling card barcode with the scheduling task information assigned by the current equipment. If the comparison results are inconsistent, all subsequent steps, including the second verification, will be terminated; if the comparison results are consistent, the second verification will be triggered.

[0008] Furthermore, the second verification is the overproduction legality verification, which is calculated and judged based on the quantity already produced, the planned production quantity, and the quantity of production executed in this production, obtained from the production order; If the overproduction legality verification passes, the subsequent report generation and synchronization steps are executed; if it fails, the subsequent steps are suspended or preset processing is executed based on the verification result.

[0009] Furthermore, the overproduction legality verification includes: calculating the sum of the quantity already produced and the quantity produced in this production run, and determining whether the sum is greater than the planned production quantity; If the result is greater than, the overproduction legality verification fails, and an integrity verification of the overproduction status and reason is triggered; if the result is not greater than, the overproduction legality verification passes.

[0010] Furthermore, the production execution report includes the quantity, weight, overproduction status marker, and reason for overproduction in this production execution, and the process report includes production identifier, operator, execution quantity, and execution time information.

[0011] Furthermore, data synchronization between the mobile terminal and the manufacturing execution system, as well as between the manufacturing execution system and the enterprise resource planning system, is achieved through API interfaces.

[0012] Furthermore, in the data correction and collaboration step, the manufacturing execution system obtains the generation status of the process report from the enterprise resource planning system through the API interface, wherein the generation status is specifically one of generated or not generated; If the generation status is "Generated", then a reverse operation is triggered for the process report, and then the data in the production execution report is modified. If the generation status is not generated, the data modification and related update in the production execution report will be executed directly.

[0013] Furthermore, the reverse operation in the data synchronization is one or more of the following: unauditing, deletion, or invalidation.

[0014] A data verification and cross-system synchronization system for mini-program deployments, characterized in that it includes: The data acquisition and verification terminal is used to collect the barcode of the scheduling card, obtain the corresponding production order based on the barcode, and perform real-time verification on the entered production execution data. The manufacturing execution system platform is communicatively connected to the mobile data acquisition and verification terminal, and is used to receive production execution data that has passed real-time verification and generate corresponding production execution reports; The Enterprise Resource Planning (ERP) system platform is communicatively connected to the data acquisition and verification terminal and the Manufacturing Execution System (MES) platform. It is used to receive synchronized data from production execution reports and generate corresponding process reports. The manufacturing execution system platform integrates a data consistency maintenance module, which is used to trigger corresponding collaborative operations based on the generation status of the corresponding process report in the enterprise resource planning system platform when modifying the production execution report.

[0015] The beneficial effects of this invention are: The core of this method lies in performing real-time verification, including order information checking and overproduction compliance judgment, at the source of data entry in the mini-program. The verified data is automatically synchronized to the Manufacturing Execution System (MES) to generate production reports, and then to the Enterprise Resource Planning System (ERP) to generate business documents. At the same time, when data needs to be corrected, the status of the ERP process report is automatically detected and reverse operations are intelligently triggered to achieve a complete closed loop of "verification-synchronization-collaborative maintenance". Thus, while ensuring the quality of the data source, the problem of automatic maintenance of data consistency across heterogeneous systems is completely solved.

[0016] This system utilizes a distributed architecture comprised of mobile data acquisition terminals (mini-programs), a Manufacturing Execution System (MES) platform, and an Enterprise Resource Planning (ERP) platform. Combined with API interfaces, it enables intelligent collaboration between systems, ensuring that data undergoes dual verification at the source and automatically driving bidirectional data synchronization between MES and ERP. This allows for intelligent coordination between the two systems to perform reverse operations when data changes occur, thus guaranteeing data consistency, business compliance, and operational traceability in a cross-system environment. This effectively addresses the pain points of traditional production data management, such as lagging verification, difficulty in synchronization, and challenges in maintaining consistency. Attached Figure Description

[0017] Other features, objects, and advantages of the present invention will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings: Figure 1 This is a schematic diagram illustrating the steps of a method for verifying and synchronizing data across systems within a mini-program according to the present invention. Figure 2 This is a flowchart illustrating a method for verifying and synchronizing data across systems within a mini-program, as described in this invention. Figure 3 This is a schematic diagram of the first verification process in Embodiment 1 of the present invention; Figure 4 This is a schematic diagram of the second verification process in Embodiment 2 of the present invention; Figure 5 This is a schematic diagram of the data modification and synchronization process in Embodiment 4 of the present invention; Figure 6 This is a schematic diagram of the structure of a mini-program-based data verification and cross-system synchronization system according to the present invention.

[0018] The reference numerals in the attached figures are as follows: 1. Data acquisition and verification terminal; 2. Manufacturing execution system platform; 3. Enterprise resource planning system platform. Detailed Implementation

[0019] To make the technical means, creative features, objectives and effects of this invention easier to understand, the invention will be further described below in conjunction with specific embodiments. Specific implementation method one: Reference Figure 1 and Figure 2 As shown in the figure, this specific embodiment provides a method for data verification and cross-system synchronization under a mini-program. This method is executed by a manufacturing execution system and includes: Receiving and Integration Steps: Receive production execution data uploaded from the mobile terminal. The production execution data is associated with and used by the mobile terminal to generate orders based on the scanned schedule card barcode. The production execution data is also verified in real time. Report generation and synchronization steps: Based on the production execution data that has passed real-time verification, generate the corresponding production execution report, and synchronize the data in the report to the enterprise resource planning system to drive it to generate the associated process report; Data correction and collaboration steps: When modifying data in existing production execution reports, the corresponding collaboration operation is triggered based on the generation status of the process report in the enterprise resource planning system.

[0021] Example 1: Reference Figure 3 As shown, this embodiment details the implementation of the first stage of real-time verification in this invention, namely, information consistency verification. This step aims to ensure the accuracy of production task identification from the source of data entry, preventing all subsequent data from becoming invalid due to operator misscanning or system assignment errors. It mainly includes the following steps: S1. Operation Initiation and Data Collection: Operators at the production site use the barcode scanning entry on their mobile terminal (i.e., the mini-program) and the terminal camera to scan the barcode on the physical card attached to the production schedule. The mini-program captures the original data of the barcode (such as one-dimensional or two-dimensional barcode information) through the device interface. As an alternative, manual input of the barcode number is also supported. S2. Background Information Association Acquisition: The mini program will capture barcode data and send a request to the enterprise's backend system through a pre-integrated API interface. It will then query the enterprise resource planning system (ERP system). The ERP system will retrieve and return the key production order information associated with the barcode from its database. This information typically includes: production order number, product color, size specification, planned production quantity, etc. The mini program receives this information and temporarily stores it locally or in the session. S3. Information Consistency Verification: After receiving the production order information returned by the ERP system, the system immediately performs the first verification, comparing the production execution data parsed from the barcode of the scheduling card with the scheduling task information assigned to the current equipment. For example, the production order number corresponding to the barcode of the scheduling card is precisely matched with the order number in the scheduling task list. S4. Verification Result Response: The system executes different control strategies based on the comparison results. When the comparison results match, the interface automatically fills in the order information obtained from the ERP (such as displaying the production order number, quantity produced, color, machine number, etc.) and unlocks or jumps to the next data entry interface (used to fill in the quantity, weight, etc. of this production execution). When the comparison results are inconsistent, the mini program immediately pops up a prominent warning pop-up on the front-end interface, indicating "card information is inconsistent with the current task". At the same time, the entire real-time verification process is suspended, that is, all subsequent data entry fields (including the quantity of fabric laid, overproduction information, etc.) are locked or hidden, making the operation unable to continue. It is necessary to wait for the operator to rescan the correct card and successfully pass this consistency verification before it can be restored.

[0022] This embodiment transforms the traditional, manual verification process into an automated, real-time feedback verification process. It intercepts data errors caused by inconsistencies in the entire data chain at the source of data generation, providing reliable data support for subsequent accurate production statistics and overproduction analysis.

[0023] Example 2: Reference Figure 4 As shown, this embodiment details the implementation of the second stage of real-time verification in this invention, namely, the verification of overproduction legality. This step is executed after the information consistency verification in Embodiment 1 is passed. Its core lies in triggering mandatory data integrity verification when potential overproduction is detected through automated verification logic of real-time quantity calculation. It mainly includes the following steps: S1. Data Entry: After successfully passing the information consistency verification in Example 1, the mini-program interface will automatically unlock or jump to the next data entry interface. This area obtains and displays two key baseline data from the ERP system: planned production quantity (e.g., 1000 pieces) and current production quantity (e.g., 800 pieces). At the same time, the interface provides fields such as "Quantity of this Production Execution" and "Weight" for operators to enter. S2. Real-time calculation and overproduction judgment: When the operator enters a value (e.g., 250 pieces) in the "Quantity of this production execution" field, the system monitors the changes in this field in real time and immediately triggers the background verification logic when the input is completed or the focus is removed: calculate the sum of the quantity produced and the quantity of this production execution, and determine whether the sum is greater than the planned production quantity. For example: Current output (800) + current production execution (250) = cumulative estimated output (1050), and compare the cumulative estimated output (1050) with the planned production quantity (1000): If the comparison result is no overproduction, the process continues: At this time, the "overproduction" checkbox in the interface remains optional and unchecked, the "reason for overproduction" input box remains hidden or disabled, and the submit button (such as "confirm report") is available. Users can submit data at any time, and the process will smoothly enter the subsequent cross-system synchronization steps. If the comparison result indicates overproduction, a mandatory verification is triggered: the system automatically checks the "Overproduction" checkbox on the interface and immediately sets the interactive state of the checkbox to an uneditable state (locked). The system automatically pops up or highlights the "Reason for Overproduction" input box and sets its field attribute to required. Only after the user enters the required text information in the "Reason for Overproduction" input box will the system unlock the submit button in real time, allowing the operation to continue and proceed to the subsequent report generation and synchronization steps.

[0024] This embodiment transforms the quantitative relationship between "planned production quantity - produced quantity - current production execution quantity" into real-time calculation and directly maps the calculation results to mandatory control of user interface controls. This not only provides real-time warnings of overproduction risks, but more importantly, through the linkage mechanism of "locking checkboxes" and "mandatory overproduction reason", it forcibly ensures the integrity and traceability of abnormal data, greatly improving the quality and compliance level of production reporting data.

[0025] Example 3: This embodiment serves as an extension and supplement to Embodiment 2. This application not only supports the core judgment rule described in Embodiment 2 (i.e., the cumulative output estimate is greater than the planned production quantity), but its verification logic can also be extended according to specific production management strategies to achieve more refined process control and early warning. For example, to avoid the risk of material stockpiling caused by the company's production capacity at the last minute, managers want to require on-site personnel to confirm the situation and record the reasons when the output reaches a certain high percentage of the planned amount, even if there is no actual overproduction. In the above scenario, system administrators can configure extended overproduction warning conditions for specific production order types or the entire system through the management backend, such as setting a warning threshold ratio (e.g., 95%). That is, after performing the core calculation of Example 2 (cumulative output estimate = quantity already produced + quantity deployed this time), the system will then make the following judgment: If the cumulative output estimate is greater than the planned production quantity: then proceed as in Example 2; if the cumulative output estimate is less than the planned production quantity, then further determine the relationship between the cumulative output estimate and the ratio of planned production quantity × warning threshold. If the cumulative output estimate is greater than the ratio of planned production quantity to the warning threshold, the system will also determine that the overproduction legality verification has failed and will implement the same steps as in Example 2: the system will automatically check and lock the "overproduction" checkbox, force the filling in of "reason for overproduction", disable the submission function before the reason is filled in, and prompt the operator "The planned output is about to be reached. Please confirm and explain the current situation".

[0026] This embodiment demonstrates the adaptability and scalability of the verification logic of the present invention by introducing configurable and threshold-based extended judgment conditions. Through the configurable interface, enterprises can flexibly set different early warning thresholds according to different product lines, order priorities or production stages, so that the system can adapt to complex management needs.

[0027] Example 4: Reference Figure 5 As shown, this embodiment details how the system ensures data consistency with the Enterprise Resource Planning (ERP) system through intelligent synchronization mechanisms and collaborative operations when production execution data changes in the Manufacturing Execution System (MES), thereby forming a closed-loop, reliable data management process. The specific steps are as follows: In the production execution report interface of the MES system platform, when managers find that there is an anomaly in the data of a certain "fabricating record" (such as incorrect quantity, weight or status information), they can initiate a data correction process by clicking the corresponding modification button of the record. Before responding to any modification operation, the system will perform a synchronization status awareness. That is, the MES system will proactively check and confirm whether the data of the "fabric details" record to be modified has been successfully synchronized to the ERP system through the interface and whether a corresponding "process report" has been generated. Based on the above synchronization status judgment result, different processing paths will be automatically executed to ensure the integrity and consistency of cross-system data logic. When data has not yet been synchronized to the ERP system (i.e., there is no corresponding valid work report in the ERP), the modification process is relatively simplified. After the operator completes the data correction and saves it directly in the MES interface, the system automatically triggers a related update. This update not only applies to the current record but also links to correct all logically related business data. Once the data has been synchronized to the ERP system (i.e., the corresponding work report already exists in the ERP system), this system will initiate a cross-system collaborative processing flow to prevent data discrepancies. S1. Initiate a reverse operation command: The MES system sends a "cancel synchronization" business command to the ERP system by calling the API interface; S2. ERP side performs reverse operation: After receiving the instruction, the ERP system performs the standard reverse business processing flow on the corresponding "process report sheet" that has been generated. This flow usually includes: first, performing a reverse audit operation on the document to remove it from the confirmed state, and then performing a deletion operation to remove the document from the current valid business records. S3. MES-side correction and resynchronization: Only after the MES system receives confirmation feedback from the ERP side that the reverse operation has been successful can the operator be allowed to modify the data on the MES interface. After the data on the MES side is corrected and saved, and the internal related data is automatically updated, the system will automatically re-trigger the standard data synchronization process to resynchronize the corrected data to the ERP and generate a new and accurate "process report". Specific Implementation Method Two: Reference Figure 6 As shown in the illustration, this specific embodiment describes in detail a system architecture for implementing the method of the present invention, which includes the following core components and modules: 1. Data Acquisition and Verification Terminal 1: Used to collect the barcode of the scheduling unit card, obtain the corresponding production order based on the barcode, and perform real-time verification on the entered production execution data, including: 1. Data acquisition module, which combines the mobile device camera or receives manual input to obtain the schedule card barcode; 2. Data communication module: This module communicates with MES / ERP via the API port and is responsible for request sending and response processing. 3. Real-time verification engine module, which includes two sub-modules for first verification and second verification: Information consistency verification submodule: compares the production execution data obtained by scanning with the current scheduled task list assigned by the system. If they are inconsistent, the process is immediately blocked at the front end. Overproduction legality verification submodule: Based on the planned production quantity and the quantity already produced obtained from the ERP, and the quantity of production executed in this operation entered by the operator on site, it performs real-time calculations and dynamically controls the input interface according to the calculation results and preset rules.

[0029] 2. Manufacturing Execution System Platform 2: Communicatively connected to the mobile data acquisition and verification terminal 1, used to receive production execution data that has passed real-time verification, and generate corresponding production execution reports, which include; 1. Data Receiving and Parsing Module: Securely receives and parses data from the mobile terminal; 2. Production Execution Report Generation Module: Based on the persistent parsed data, automatically generate or update production execution reports (such as fabric details) within the system. 3. Synchronization Engine Module: After the report is generated, it automatically calls the business document generation interface provided by the ERP system to push key data; and monitors the result of each synchronization operation in real time (success / failure / error code), and provides visual status feedback and manual synchronization entry in the management interface.

[0030] 4. Data Consistency Maintenance Module: When a modification instruction for an existing report is received, the module automatically checks the status of the corresponding process report in the ERP system through a query interface and makes intelligent decisions based on the status awareness results to maintain data consistency.

[0031] 3. Enterprise Resource Planning System Platform 3: Communicatively connected to the data acquisition and verification terminal 1 and the manufacturing execution system platform 2, used to receive synchronous data from production execution reports and generate corresponding process report sheets; 1. Data Query Module: Provides the mini-program with an accurate interface for querying production order data; 2. Process Report Generation Module: Receives synchronized data pushed by MES and automatically generates the associated process report.

[0032] 3. Reverse Operation Module: This module is only invoked by the MES system when collaborative data correction is required, ensuring that any data cleanup operation complies with ERP processes and requirements.

[0033] In summary, this system utilizes a distributed architecture comprised of a mobile data acquisition terminal (mini-program), Manufacturing Execution System Platform 2 (MES), and Enterprise Resource Planning System Platform 3 (ERP). Combined with API interfaces, it enables intelligent collaboration between systems, ensuring that data undergoes dual verification at the source and automatically driving bidirectional data synchronization between MES and ERP. This allows for intelligent coordination between the two systems to perform reverse operations when data changes occur, thus guaranteeing data consistency, business compliance, and operational traceability in a cross-system environment. This effectively addresses the pain points of traditional production data management, such as lagging verification, difficulty in synchronization, and challenges in maintaining consistency.

[0034] The foregoing has shown and described the basic principles, main features, and advantages of the present invention. It will be apparent to those skilled in the art that the present invention is not limited to the details of the exemplary embodiments described above, and that the invention can be implemented in other specific forms without departing from its spirit or essential characteristics. Therefore, the embodiments should be considered illustrative and non-limiting in all respects, and the scope of the invention is defined by the appended claims rather than the foregoing description. Thus, all variations falling within the meaning and scope of equivalents of the claims are intended to be included within the present invention. No reference numerals in the claims should be construed as limiting the scope of the claims.

[0035] Furthermore, it should be understood that although this specification describes embodiments, not every embodiment contains only one independent technical solution. This narrative style is merely for clarity. Those skilled in the art should consider the specification as a whole, and the technical solutions in each embodiment can also be appropriately combined to form other embodiments that can be understood by those skilled in the art.

Claims

1. A method for data verification and cross-system synchronization under a mini-program, wherein the method is executed by a manufacturing execution system, characterized in that: It includes: Receiving and Integration Steps: Receive production execution data uploaded from the mobile terminal. The production execution data is associated with and used by the mobile terminal to generate orders based on the scanned schedule card barcode. The production execution data is also verified in real time. Report generation and synchronization steps: Based on the production execution data that has passed real-time verification, generate the corresponding production execution report, and synchronize the data in the report to the enterprise resource planning system to drive it to generate the associated process report; Data correction and collaboration steps: When modifying data in existing production execution reports, the corresponding collaboration operation is triggered based on the generation status of the process report in the enterprise resource planning system.

2. The method for verifying and synchronizing mini-program deployment data across systems according to claim 1, characterized in that: The mobile terminal is a mini-program that collects production execution data by scanning or manually entering the schedule card barcode.

3. The method for verifying and synchronizing mini-program deployment data across systems according to claim 2, characterized in that: The real-time verification includes a first verification and a second verification performed sequentially. The first verification is an information consistency verification, which includes: comparing the production execution data obtained from the scheduling card barcode with the scheduling task information assigned by the current equipment. If the comparison results are inconsistent, all subsequent steps, including the second verification, will be terminated; if the comparison results are consistent, the second verification will be triggered.

4. The method for verifying and synchronizing mini-program deployment data across systems according to claim 3, characterized in that: The second verification is the overproduction legality verification, which is calculated and judged based on the quantity already produced, the planned production quantity, and the quantity of production executed in this production, obtained from the production order; If the overproduction legality verification passes, the subsequent report generation and synchronization steps are executed; if it fails, the subsequent steps are suspended or preset processing is executed based on the verification result.

5. The method for verifying and synchronizing mini-program deployment data across systems according to claim 4, characterized in that: The verification of the legality of overproduction includes: calculating the sum of the quantity already produced and the quantity produced in this production run, and determining whether the sum is greater than the planned production quantity; If the result is greater than, the overproduction legality verification fails, and an integrity verification of the overproduction status and reason is triggered; if the result is not greater than, the overproduction legality verification passes.

6. The method for verifying and synchronizing mini-program deployment data across systems according to claim 1, characterized in that: The production execution report includes the quantity, weight, overproduction status marker, and reason for overproduction in this production execution. The process report includes production identifier, operator, execution quantity, and execution time information.

7. The method for verifying and synchronizing mini-program deployment data across systems according to claim 1, characterized in that: Data synchronization between the mobile terminal and the manufacturing execution system, as well as between the manufacturing execution system and the enterprise resource planning system, is achieved through API interfaces.

8. The method for verifying and synchronizing mini-program deployment data across systems according to claim 7, characterized in that: In the data correction and collaboration step, the manufacturing execution system obtains the generation status of the process report from the enterprise resource planning system through the API interface. The generation status is specifically one of "generated" or "not generated". If the generation status is "Generated", then a reverse operation is triggered for the process report, and then the data in the production execution report is modified. If the generation status is not generated, the data modification and related update in the production execution report will be executed directly.

9. The method for verifying and synchronizing mini-program deployment data across systems according to claim 8, characterized in that: The reverse operation in the data synchronization is one or more of the following: unauditing, deletion, or invalidation.

10. A system for verifying and synchronizing mini-program deployment data across systems, employing the method for verifying and synchronizing mini-program deployment data across systems as described in any one of claims 1-9, characterized in that: It includes: The data acquisition and verification terminal (1) is used to collect the barcode of the scheduling card, obtain the corresponding production order based on the barcode, and perform real-time verification on the entered production execution data. The manufacturing execution system platform (2) is connected to the mobile data acquisition and verification terminal (1) for receiving production execution data that has passed real-time verification and generating corresponding production execution reports; The Enterprise Resource Planning (ERP) system platform (3) is connected to the data acquisition and verification terminal (1) and the Manufacturing Execution System (MES) platform (2) to receive synchronous data from the production execution report and generate the corresponding process report. The manufacturing execution system platform (2) is equipped with a data consistency maintenance module, which is used to trigger corresponding collaborative operations based on the generation status of the corresponding process report in the enterprise resource planning system platform (3) when modifying the production execution report.

Images