A packaging method enforcing tag suffix and lot preceeding comparison

Abstract

The application relates to the technical field of semiconductor testing, and discloses a packaging method for enforcing tag tail numbers and batch pre-arrangement comparison, which comprises the following steps: firstly, obtaining the total number of work orders, the standard full-box number and the actually measured tail number; through calculation, checking whether the balance after deducting the tail number and loss can be divided by the standard full-box number, performing number logic verification and determining the integer box generation number; after the verification passes, the system dynamically generates a label code, controls printing, constructs a batch packaging data set containing all label identifiers, collects physical labels to construct an actually measured scanning data set, and performs set consistency comparison with the batch packaging data set to verify whether the two sets are subsets of each other; after the set comparison passes, the actually measured total number is further verified to be equal to the net value of the work order, and only when the two sets match, the system allows the work order to be stored and closed. Through source logic verification and bidirectional set comparison, the application realizes closed-loop management and control of the whole packaging process, and ensures the accuracy of inventory data.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of semiconductor testing, in particular to a packaging method for enforcing label tail number and batch combination comparison in advance. BACKGROUND

[0002] In the semiconductor and precision electronic component post-sealing and testing link, product packaging and warehousing is a key process connecting production and logistics. The existing manufacturing execution system usually issues packaging tasks according to the theoretical quantity of production work orders, and the workers print and paste labels according to the preset standard full box quantity.

[0003] However, in the actual production process, due to process loss, sampling consumption and non-integer multiple production factors, the actual output quantity often deviates from the theoretical quantity of work orders, and non-standard quantity tail boxes are inevitably produced. The existing packaging operation process usually lacks pre-data logical constraints and allows to print all labels in advance without confirming the actual loss and tail number details. This operation mode is easy to cause the number of generated physical labels to be greater than the actual qualified product quantity, or the nominal value of the tail number label does not match the actual product. When the workers try to correct these differences in the warehousing link, they often need to discard the old labels and reapply for printing, which not only reduces the operation efficiency, but also causes waste of label consumables and data redundancy.

[0004] In addition, in the warehousing verification stage, the existing scanning terminal technology mainly relies on the verification logic of quantity accumulation, that is, whether the total sum of all scanned labels is equal to the work order warehousing quantity. This single-dimensional verification method cannot identify the legitimacy of the specific label identity. For example, when there are multiple batch mixed operations in the operation site, if other work order labels are mistakenly mixed into the current tray, or the same label is repeatedly scanned, as long as the total value of the accumulation meets the requirements, the system may still determine that the verification is passed. This logical loophole leads to confusion of the relationship between the actual product and the account, making it difficult to trace the inventory, and cannot meet the strict requirements of high-precision manufacturing on batch management. Therefore, there is an urgent need for a packaging control method that can enforce quantity logic from the source and accurately compare the unique identity at the verification end. SUMMARY

[0005] In view of the deficiencies of the prior art, the present application provides a packaging method for enforcing label tail number and batch combination comparison in advance, which solves the problem of inventory account inconsistency caused by arbitrary tail number processing, lagging loss recording and label mismatch with actual product in the packaging link of semiconductor and precision manufacturing industry.

[0006] To achieve the above purpose, the present application is implemented by the following technical scheme: a packaging method for enforcing label tail number and batch combination comparison in advance, comprising the following steps:

[0007] obtaining a total number of work orders and a standard full case number of a current production work order, and recording a number of measured tail numbers;

[0008] performing a quantity logic verification, determining a number of integer case labels to be generated based on the total number of work orders, the number of measured tail numbers and the standard full case number, and introducing a loss number in the verification process to ensure quantity balance;

[0009] in response to passing of the quantity logic verification, generating encoding data and controlling a printing device to output to obtain physical labels according to the determined number of integer case labels to be generated, while constructing a batch packaging dataset containing unique identifiers of all integer case and tail number labels in the system;

[0010] after the physical labels and corresponding tail number labels are pasted to packaging units, collecting barcode data of the physical labels on the packaging units to construct a measured scanning dataset, and performing set consistency comparison between the measured scanning dataset and the batch packaging dataset;

[0011] after the set consistency comparison passes, determining whether to allow execution of a warehouse closing operation based on matching results of a total number of the measured scanning dataset and the total number of work orders after deducting the loss number.

[0012] The step of performing quantity logic verification and introducing loss number specifically includes:

[0013] calculating a preliminary balance of the total number of work orders after deducting the number of measured tail numbers, and determining whether the preliminary balance can be divided by the standard full case number;

[0014] if not, correcting the preliminary balance by a loss number entered by a user until the corrected balance can be divided by the standard full case number;

[0015] dividing the corrected balance by the standard full case number to obtain a quotient as the number of integer case labels to be generated.

[0016] The specific steps of the set consistency comparison are:

[0017] verifying whether the measured scanning dataset is a subset of the batch packaging dataset to confirm that all scanned labels are within the system preset range;

[0018] at the same time, verifying whether the batch packaging dataset is a subset of the measured scanning dataset to confirm that all labels preset by the system have been scanned;

[0019] only when the two datasets are subsets of each other, it is determined that the set consistency comparison passes.

[0020] The step of generating encoding data includes:

[0021] generate a public prefix combining the work order unique identifier and the product material code;

[0022] generate an incremental serial number and format it;

[0023] concatenate the public prefix, the formatted serial number and the standard full case quantity in a preset order to form a unique identifier containing an implicit quantity attribute.

[0024] The step of controlling the output of the printing device further comprises:

[0025] establish the job start time and the valid printing time window when starting the printing task;

[0026] verify whether the current time is within the valid printing time window before outputting each of the physical labels;

[0027] if the verification fails, forcibly terminate the printing task and clear the buffer data.

[0028] The step of constructing the measured scanning data set comprises:

[0029] parse the collected graphical code data to obtain the label unique identifier and the corresponding quantity attribute;

[0030] perform a local deduplication operation to discard repeatedly collected label data;

[0031] store the deduplicated label unique identifier and its parsed quantity attribute in the measured scanning data set.

[0032] The step of determining whether to allow the execution of the warehouse closing operation specifically comprises:

[0033] calculate the sum of the quantities parsed from all labels in the measured scanning data set to obtain a measured scanning total quantity;

[0034] calculate the value obtained by subtracting the loss quantity from the total quantity of work orders to obtain a theoretical warehouse net value;

[0035] compare the measured scanning total quantity with the theoretical warehouse net value, and only when they are exactly equal, generate a control signal allowing the closing.

[0036] After allowing the execution of the warehouse closing operation, further comprises:

[0037] start a database transaction and update the main state of the current work order to completed;

[0038] perform a write protection operation on all data records associated with the work order, set the access permission to read-only, or use a database trigger to intercept data modification instructions to prevent historical data from being tampered with.

[0039] After determining the number of integer box labels to be generated, further comprising:

[0040] Parameter setting is performed on the memory address or database record where the total number of work orders, the measured number of remainders, and the loss number are located;

[0041] During the process of printing the physical labels, the above-mentioned locked parameters are prohibited from being modified until the printing job is completed or abnormally terminated.

[0042] After determining that the warehousing closing operation is allowed to be performed, further comprising the steps of performing production data archiving and external synchronization:

[0043] The final confirmed total number of work orders, the measured number of remainders, the loss number, and the measured total number of scans are obtained and encapsulated to generate a standard message packet in a predetermined format;

[0044] The standard message packet is sent to an external enterprise resource planning system through a message queue middleware to complete the synchronization of inventory accounts and production performance.

[0045] The present application provides a packaging method for enforcing label remainder and batch comparison in advance.

[0046] 1、The present application performs number logic verification based on modulo operation before label generation, and forcibly introduces a loss correction mechanism, which is different from the traditional mode of printing first and checking later. The method blocks abnormalities caused by physical quantity non-conservation at the data source, and the system ensures that only when the balance after deducting the remainder and the loss can be evenly divided by the standard full box quantity, a printing instruction is generated, effectively avoiding the waste of invalid labels caused by number logic errors, and solving the problem of warehouse process deadlock caused by inconsistent accounts and actual performance in subsequent links.

[0047] 2、The present application uses a two-way consistency comparison algorithm based on set theory, replacing the single number accumulation verification. By constructing a preset batch packaging data set, the system not only verifies whether the total number of measured scans meets the standard, but also verifies whether the unique identifier of each physical label belongs to the current work order strictly. This mechanism can accurately identify and intercept the situation of non-batch label mixing or batch label missing, ensuring the strict correspondence between physical identity and system data, and eliminating the risk of wrong parts that may be hidden by traditional number counting methods.

[0048] 3、The application establishes a full-process data closed-loop control from work order downward to warehouse storage and case closing, after confirming that the measured data and the theoretical data are completely matched, the system automatically executes database write protection and triggers external system synchronization, realizes real-time archiving of production performance, through locking of key parameters and limitation of printing time window, the scheme prevents human tampering with data or repeated use of outdated labels during the operation process, and provides accurate account data that is traceable and irrefutable for enterprise inventory management. BRIEF DESCRIPTION OF DRAWINGS

[0049] Figure 1 It is a method flowchart of the application;

[0050] Figure 2 It is a system architecture diagram of the application. DETAILED DESCRIPTION

[0051] The technical solutions in the embodiments of the application will be clearly and completely described below with reference to the drawings in the embodiments of the application. Obviously, the described embodiments are only part of the embodiments of the application, rather than all the embodiments of the application. Based on the embodiments in the application, all other embodiments obtained by those skilled in the art without creative labor fall within the protection scope of the application.

[0052] Embodiment:

[0053] Referring to the drawings Figure 2 , Figure 2 It is a packaging system for enforcing label tail number and batch combining comparison, which is one embodiment of the application. The system comprises a central control terminal, a production execution system interface, a label comparison device, a label printing device and a quality review terminal. The above hardware components are connected through a communication network to establish a signal connection and a data exchange channel.

[0054] The central control terminal is the core logic processing unit of the system, which is configured with a processor and a storage medium, and is used to run a label generation algorithm, a logic interlocking control program and an abnormal fuse determination program. The central control terminal is bidirectionally connected with the production execution system interface, the label comparison device, the label printing device and the quality review terminal to realize data collection, calculation and instruction issuing.

[0055] The production execution system interface is used for data docking with the production management database or the MES system in the factory. The production execution system interface is responsible for extracting the production work order details of the current batch, including the total number of work orders and the preset standard full-box number, and transmitting the above basic data to the central control terminal for caching and operation.

[0056] The label comparison device is arranged at a packaging site for collecting label information adhered to a surface of a package. The label comparison device is configured as an optical scanning device or an industrial vision recognition camera and has a function of analyzing one-dimensional bar codes or two-dimensional matrix codes. The label comparison device reads a unique serial number and related coded information on the label and returns raw data read to a central control terminal in real time for index query and comparison verification.

[0057] The label printing device is communicatively connected to the central control terminal and is configured to generate visual packaging labels on a physical medium in response to a printing instruction. The label printing device is controlled by a state control signal sent by the central control terminal and has a switching function between a logical lock state and a working state. In the logical lock state, the label printing device cannot receive or execute a printing task of an integer label.

[0058] The quality review terminal is configured to provide a human-computer interaction interface for identity verification and review operations of a quality manager. The quality review terminal is configured with a permission authentication module for identifying biological features or identity keys of an operator. After receiving a review pass instruction, the quality review terminal generates a corresponding authorization signal and sends the authorization signal to the central control terminal. The authorization signal constitutes one of prerequisites for unlocking the label printing device.

[0059] The communication network adopts an industrial Ethernet, a TCP / IP protocol or a serial communication interface standard to ensure real-time and stability of instruction transmission between devices. The central control terminal monitors running states of terminal devices through the communication network and coordinates working time sequences between the devices.

[0060] Referring to the accompanying drawings Figure 1 , Figure 1 The packaging method for enforcing label tail number and batch combination pre-comparison is an embodiment of the present application. The method is cooperatively executed by the central control terminal and internal function modules thereof to realize whole-process management and control from order distribution to warehouse storage. The overall operation process mainly includes the following steps.

[0061] First, the system performs initialization and permission presetting. The production execution system interface receives a total number of orders and a standard full-box number of a current batch from an external management system. At this time, the logical interlocking control module sets a printing permission of an integer label of a secondary label in the label printing device to a prohibited state. The data generation module does not perform data operation for the secondary label in this stage and only allows generation of a printing instruction of a first label tail number or a batch combination label.

[0062] Subsequently, the first type of label processing and data anchoring stage is entered, the data anchoring module generates the first type of label containing a unique identifier, after the work personnel complete the physical packaging, the unique identifier on the packaging is read by the label comparison device, the data anchoring module indexes and extracts the measured decimal number in the database according to the unique identifier, and the number is used as the reference data for subsequent calculation.

[0063] Next, logical verification and abnormal fuse determination are performed, the permission verification module receives the review confirmation signal from the quality review terminal, after the confirmation signal is valid, the dynamic calculation engine module performs balance operation according to the total number of work orders, the standard full box number and the measured decimal number, and obtains the theoretical integer box number and the verification remainder, the abnormal fuse module determines whether the verification remainder is zero, if the verification remainder is not zero, the abnormal fuse module sends a blocking signal to the logical interlocking control module to maintain the prohibited state of the printing permission.

[0064] Only when the verification remainder is zero, the second type of label generation and unlocking stage is entered, the data generation module constructs the printing data of the second type of label in real time according to the theoretical integer box number, and embeds the unique identifier of the first type of label therein, the logical interlocking control module releases the restriction on the label printing device, and allows the label printing device to output the second type of label.

[0065] Finally, closed-loop comparison and case closing are performed, the label comparison device collects the information of all second type of labels, the central control terminal verifies the data correlation of the second type of label and the first type of label, when the comparison records of all labels are complete and logically consistent, the system determines that the batch packaging is completed and allows warehousing.

[0066] The loading and analysis process of work order data is the basis for the system to perform subsequent closed-loop control, which is mainly completed by the production execution system interface and the data anchoring module of the central control terminal, in the specific implementation, the process includes the following steps:

[0067] Establish a communication session and request data, the production execution system interface establishes a connection with the production management server of the factory through a pre-configured communication protocol, the communication protocol can use hypertext transfer protocol HTTP / HTTPS, transmission control protocol TCP / IP or database connection protocol such as ODBC, JDBC, after the connection is established, the production execution system interface sends a data request instruction to the production management server according to the batch number or job number of the current job batch, for the specific handshake process and message format of the above communication protocol, those skilled in the art can use the existing standard network communication technology to realize, which will not be described here.

[0068] The production execution system interface receives the response data packet returned by the production management server. The data format of the data packet is usually JavaScript Object Notation (JSON), Extensible Markup Language, or fixed-length string format. The central control terminal calls the pre-stored field mapping table to match and extract the key-value pairs in the response data packet with the internal variables of the system.

[0069] In the present embodiment, the following definitions are made: is the total number of work orders, representing the total number of chips or devices that need to be packaged after passing through the previous test process. The following definition is made: is the standard full box quantity, representing the maximum number of products that a single complete packaging box or tray can hold under the standard packaging specification. The central control terminal stores the parsed in the volatile memory or cache of the system as a global variable for subsequent module calls.

[0070] For the acquisition method of , in addition to directly reading the value from the data packet, the following alternative embodiments are also included: the system reads the wafer quantity in the work order and the chip output quantity of the single wafer, performs multiplication operation to obtain the calculation result and assigns it to ; or reads the total good quantity statistics value uploaded by the previous test process as . For the acquisition method of , in addition to directly reading the parameter set by the work order, the system also includes the following: accessing the local pre-stored product specification database according to the product model field in the work order to retrieve the standard packaging specification parameter corresponding to the model as . The above different acquisition paths all belong to the specific implementation form of obtaining work order data.

[0071] Data validity verification: after parsing is completed, the system performs data integrity verification logic. This verification logic is used to confirm that the obtained values meet the pre-set logical rules and production specifications, preventing abnormal calculation caused by upstream data errors. The verification rules include: confirming that is a positive integer, confirming that is a positive integer and . If the verification fails, the system generates an error log and suspends the process; if the verification passes, the system locks the above variables, preventing them from being modified arbitrarily during the job process, unless the change process is performed by the highest authority.

[0072] Through the above steps, the system completes the collection and storage of job reference data, ensuring that the subsequent dynamic calculation engine module has accurate and tamper-proof input sources.

[0073] ​After the work order data is loaded, the system immediately enters the permission control state to ensure that the packaging operation strictly follows the timing rule of decimal number first and integer second. This process is executed by the logic interlocking control module, and the specific implementation steps are as follows:

[0074] Initialize the print state variable. The central control terminal opens a register or logical address in the volatile memory for storing the print permission state, and defines the integer label print state variable. The system sets the initial value of to the logical value 0, which represents the locked state. At the same time, it defines the decimal label print state variable and sets to the logical value 1, which represents the open state. This step establishes the default security policy in the system initialization program, i.e., the system logic program refuses to execute any operation instruction for the integer label before the specific unlocking condition is met.

[0075] Function shielding of the user interaction interface. The logic interlocking control module refreshes the operation interface of the label printing device or the client interface of the production execution system in real time according to the state variable value set in step . When is detected, the system sets the function control of the integer label printing on the interface to the disabled state, including but not limited to virtual buttons, menu options, or shortcut keys. In specific implementation, the system removes the event listener of the control or sets the property of the control to read-only, so that the control presents an uninteractive visual effect and does not trigger any callback function when receiving a click operation. Through physical shielding of the user interface, the system prevents the operation personnel from mistakenly triggering the printing task.

[0076] Background instruction interception and verification. In order to prevent the operation personnel from bypassing the graphical interface and directly calling the printing function through the command line or third-party interface, the system sets the command distribution logic between the data generation module and the print driver. When the system receives any print request, the command distribution logic first parses the label type field in the request data packet. If it identifies that the request belongs to the integer label or standard box label category, the system program reads the value of . If , the system program performs a return operation or throws an exception, directly discarding the print request, not sending a physical instruction to the label printing device, and writing a illegal access record to the log system. This technical feature constitutes a redundant control measure to ensure the enforceability of the control.

[0077] Condition restriction of data generation. In addition to prohibiting the printing action, the locking logic also extends to the data generation link. In In the state of lock, even if the system background receives the operation request of generating integer label data, the dynamic calculation engine module will skip the corresponding calculation subprogram, which means that in the lock state, the specific encoding content of the integer label such as the two-dimensional code data string and the serial number is not instantiated or allocated storage space in the system memory. This design fundamentally eliminates the possibility of error printing caused by cache data leakage, and realizes strict restriction from data generation to physical output.

[0078] Through the above steps, the system constructs a time sequence controlled job environment, and forces the production resources to flow to the processing flow of the fractional label, providing a determined initial environment for subsequent dynamic calculation based on measured data.

[0079] The generation strategy of the unique identifier is the core technical means to realize data anchoring, and its purpose is to allocate an identification code that does not conflict with each other in the system job cycle for each first-class label decimal or batch label, so that the physical label can become the index entry of dynamic data in the database. The specific implementation process of this strategy includes the following steps:

[0080] In response to the generation request of the first-class label, when the job personnel selects the print decimal or print batch function on the interactive interface of the label printing device, the system first retrieves the current decimal label printing state variable After confirming that the logical value is 1, the data anchoring module receives the request data packet containing the current work order number, product part number and batch number. At this time, the system temporarily stores the request data and enters the identifier generation subprogram.

[0081] Generate a globally unique identifier. The system calls the internal serial number generation algorithm to create a string used to uniquely mark the physical label, defined as In order to ensure uniqueness in cross-batch and multi-terminal environment, the system uses combined encoding to generate, and in the specific implementation, The generation logic of follows the following encoding rules:

[0082] ;

[0083] Among them, represents the system internal number of the current work order; represents the system current timestamp accurate to the millisecond level; represents the random check digit generated by the hardware random number generator; represents the string concatenation operator; represents the hash operation function. Through the above operation, the system generates a fixed-length string as The generation mode combines time discreteness and randomness, ensuring that the tag IDs generated by different terminals are unique. For the specific selection of the hash operation function, a person skilled in the art can use MD5, SHA-1, or MurmurHash algorithm.

[0084] The initialization data anchor record is inserted into the tag measurement data table in the background database, and the system associates the number of measured mantissas of the record with the mantissa number field in the database, and sets the initial value of the field to null. This step has already opened a dedicated data storage space in the information system before the physical tag is printed, establishing a correspondence between the physical entity and the digital information. After the initialization data anchor record is inserted, the data anchor module immediately inserts a new record in the tag measurement data table in the background database, which takes the as the primary key, and at the same time, the system associates the number of measured mantissas of the record with the mantissa number field in the database, and sets the initial value of the field to null. This step has already opened a dedicated data storage space in the information system before the physical tag is printed, establishing a correspondence between the physical entity and the digital information.

[0085] The system retrieves the pre-stored first-type tag printing template, converts the generated into a machine-readable graphical code format, including Quick Response Matrix Code, Data Matrix Code, or 128 Code. The system embeds the graphical code data into the printing instruction stream and sends it to the tag printing device through the printer instruction language. The barcode is recorded on the printed physical tag as a voucher for data indexing in subsequent steps. For the generation and printing driver technology of the barcode, a person skilled in the art can use existing industrial printing standards to achieve it, and will not be described here. Through the above steps, each first-type tag carries an unforgeable identity, and the identity has been registered in the background database, laying a foundation for subsequent real-time data backfilling and extraction based on the identity.

[0086] After obtaining the physical tag, the work link enters the entity operation phase. At this time, the system supports asynchronous processing of physical work and data entry, i.e., generating physical carriers first and then entering business data. The process specifically includes the following steps:

[0087] Perform physical packaging and loss removal. The work personnel paste the printed first-type tag on the outer surface of the packaging container, and according to the production specification, the products to be packaged are loaded into the container. During the packaging process, the work personnel perform the appearance inspection program. If a product with appearance defects or not meeting the quality standards is found, the work personnel will remove it from the work flow and not load it into the packaging container. In this step, due to the existence of loss removal operation, the actual number of products loaded into the container is uncertain. At this time, the first-type tag pasted on the container only serves as a unique index carrier for the container, and the graphical code carried by it has not yet been associated with specific numerical information.

[0088]

[0089] ​​Determine the actual number of tail, after the physical packing action is completed, the operator counts the product in the container, the specific implementation of the counting method includes:

[0090] The artificial point counting method, using high-precision electronic counting scale for weighing conversion or using machine vision counter for automatic statistics, the counted value is assigned to the actual number of tail , which represents the total amount of remaining qualified products in the current work order that cannot be packaged as a standard full box.

[0091] Trigger data backfill request, the operator operates the label comparison device on site, scans the first type of label on the packaging container, and the label comparison device reads the unique identifier in the label , and sends a query request to the central control terminal, and the central control terminal identifies the , sends a data entry instruction to the front-end interactive device, the specific form of the front-end interactive device includes a wireless handheld terminal, an industrial tablet computer or a PC workstation connected with a scanning gun, the operator enters the value determined in the step in the input interface of the front-end interactive device, and submits an update instruction.

[0092] Perform database update operation, after the data anchor module receives the update instruction containing and , execute the database write operation, the system retrieves the corresponding record row in the database table according to as the index key, and writes the received value to the corresponding field of the record row, covering the original initial value, at this time, the physical label and the quantity data actually contained by it complete the data association. If the quantity is found to be incorrect during the subsequent review process, the operator can scan the label again and submit a new value, and the system will determine and execute the overwrite update according to the operation timestamp, and the last submitted data will be used as the final actual number of tail , this mechanism ensures the correctability of the data, and avoids the situation that the label is scrapped due to printing errors.

[0093] The data acquisition process uses the unique identifier on the physical label to call the recorded actual data from the background database, thereby avoiding errors caused by manual secondary entry, and the technical process is mainly completed by the label comparison device and the central control terminal, and includes the following steps:

[0094] The optical scanning and decoding are performed. An operator uses a label matching device to scan a first type of label attached to a packaging container. The label matching device is internally provided with an optical scanning module. The module specifically includes a laser scanning engine, a charge-coupled device image sensor, or a complementary metal-oxide-semiconductor image sensor. When the device captures an image of a barcode or a two-dimensional code on the label surface, a binarization process and a decoding algorithm are performed to parse the graphical information into a unique identifier in the form of a string. In this step, the device only reads the identifier itself, without parsing a specific quantity value from the graphical code.

[0095] The index query request is constructed. The label matching device parses the decoded The data query message is generated. The message follows a specific communication protocol, such as Modbus TCP, HTTP / JSON, or WebSocket. The message contains an explicit operation instruction field, indicating that the central control terminal performs a data retrieval operation. Subsequently, the label matching device sends the request to the data anchoring module of the central control terminal through a communication network.

[0096] Database retrieval and field extraction. After receiving the query request, the central control terminal parses The data anchoring module uses as the primary key or index key to perform a query operation in the label measurement data table of the database. In specific implementations, the system locates the unique record row matching the in the database management system interface, and reads the value of the measured mantissa quantity field stored in the record row.

[0097] Data state verification and exception handling. After extracting the value of , the system immediately performs validity verification. The verification logic checks whether it is a null value or a default initial value. If is a null value, it indicates that the physical packing data corresponding to the label has not been entered or has not been completed. The system immediately returns the corresponding error code to the front-end device and prevents the subsequent calculation process. If is a valid positive integer, the system determines that the data collection is successful, and temporarily stores the value in the input register of the calculation engine.

[0098] Data aggregation and calculation. The system integrates the collected with the global variables of the current work order, including the total quantity of work orders and the standard full-box quantity to form a complete set of operation inputs. At this time, the central control terminal has completed the conversion from physical indexes to digital calculation parameters, and has prepared the data for the subsequent dynamic balance calculation.

[0099] Through the above-mentioned index-based collection method, the system ensures that the mantissa quantity participating in the core calculation is strictly derived from the physical field measurement results.

[0100] The multi-level confirmation mechanism is an independent verification step set by the system before performing logical verification. By introducing a review process independent of the operator, it ensures that the basic data entered into the system is consistent with the physical reality. This mechanism is led by the permission verification module and is jointly executed by the front-end interactive device and the quality review terminal. The specific implementation process includes the following steps:

[0101] Job submission and state locking, after the operator submits the measured mantissa quantity through the front-end interactive device , the system does not immediately mark this data as valid for subsequent calculations. At this time, the system establishes a temporary transaction session in the database and defines a review state variable, with its initial value set to a logical value of 0 representing pending review. At the same time, the front-end interactive device disables the current entry interface and displays a waiting prompt, preventing the operator from making secondary modifications or withdrawing the submitted data until the review process is complete.

[0102] Review task routing and on-site checking, the system uses a message queue or polling mechanism to send a review request containing a unique identifier and to the quality review terminal. The quality review terminal is a handheld or fixed computing device specifically for quality assurance (QA) personnel. QA personnel scan the physical labels on the packaging site based on the data displayed on the terminal, and physically count or sample the products in the container. This step realizes the check of the correspondence between data records and physical entities.

[0103] Identity authentication and operation confirmation, after confirming the consistency between the physical object and the data, the QA personnel need to perform a confirmation operation on the quality review terminal. The system enforces identity authentication logic at this link, and the specific authentication methods include: reading the user identification code in the QA personnel's radio frequency identification card, collecting biometric data and performing feature vector comparison, or inputting an authorized key. The quality review terminal encrypts the confirmation instruction based on the collected identity information, generates a confirmation data packet containing a digital signature, and sends it to the central control terminal.

[0104] Permission matching and state updating, after receiving the confirmation data packet, the permission verification module parses and retrieves the user's permission level in the system's permission management database. The system performs the following logical judgments:

[0105] ;

[0106] wherein, represents the minimum authority threshold of quality review preset by the system; represents the digital signature validity flag, whose value is True when the system verifies that the digital signature is legal; represents the logical AND operation.

[0107] Logical release, if and only if is updated to 1, the system releases the lock state of the data, and determines as valid data, and triggers the subsequent dynamic calculation engine module, if the weighting fails or the QA personnel performs a rejection operation, the system will maintain 0, and return a rejection instruction to the front-end interactive device, forcing the operator to re-count and enter data.

[0108] Through the above steps, the system completes the verification of the data through permission control and manual review before the data enters the core calculation logic, preventing source data errors caused by negligence of the front-line operators.

[0109] After completing the manual review and permission confirmation, the system enters the automatic logical verification stage, which uses computer programs to verify and calculate the remaining work quantity based on the anchored measured data to ensure that the data meets the preset quantity relationship, and this process is performed by the dynamic calculation engine module, including the following steps:

[0110] Load verification parameters, when the review state variable is updated to 1, the dynamic calculation engine automatically triggers the verification thread, and the system simultaneously retrieves three core variables from the memory or database: the total number of work orders , the standard full box quantity , and the measured tail number just passed the review At this time, the system will perform a pre-check on these three variables to ensure that they are all non-negative integers and meet the condition to prevent negative numbers from appearing in the calculation results due to input errors.

[0111] Perform the remainder verification operation, the system aims to verify whether the remaining product quantity after removing the measured tail number can be divided by the standard packaging specification, this logic is based on the packaging operation rule: in the operation mode of first tail number and then integer, if the tail number statistics are accurate and there is no additional loss, the remaining products must be composed of several complete standard boxes, the system performs the following remainder verification formula:

[0112] ;

[0113] wherein, is defined as the remainder verification value; represents a modulo operation for calculating the remainder after division.

[0114] The system determines whether the calculated is zero, and executes different control strategies according to the determination result:

[0115] ;

[0116] wherein, is defined as a logical check status bit.

[0117] If , it indicates that the remaining quantity cannot be divided by the standard box, i.e. is not an integer multiple of , which usually means that there is unrecorded loss, extra good products, or entry error in the previous step, at this time, the system triggers an exception handling program, sends an error prompt pop-up window to the front-end interactive device, and marks the system state field of the current work order as abnormal lock, suspending the subsequent operation permission until the management personnel corrects the data or resets the entry process through an authorized account.

[0118] If , it indicates that the data meets the preset logic, the system determines that the check is passed, and automatically enters the yield calculation of the next step.

[0119] The number of integer box labels to be generated is calculated, and after confirming that the logic is correct, the system continues to perform division operation to determine the specific number of integer labels to be printed in the following step, and the operation formula is as follows:

[0120] ;

[0121] wherein, is defined as the number of integer box labels to be generated, and since the remainder check has been passed, the calculated here must be a positive integer. The system stores in a loop counter variable as a count threshold for controlling the number of subsequent printing loops.

[0122] Unlock the integer printing permission, as the final output of the check process, the system modifies the value of the integer label printing state variable , and the system updates from logical value 0 to logical value 1. This state update operation removes the interactive shielding and instruction interception described in the step, and formally opens the generation and printing function of the integer label.

[0123] ​​Through the above steps, the system uses mathematical logic to perform a secondary verification of the physics homework results, ensuring that the batch printing permission is only released under the premise that the data logic is strictly self-consistent, thereby avoiding label waste or discrepancies between accounts and actual quantities due to quantity mismatch.

[0124] An exception handling mechanism refers to a control strategy that forcibly suspends the current workflow and introduces high-privilege intervention to correct data deviations when the system detects a logical verification failure. This mechanism prevents erroneous data from being carried over into subsequent calculations. The specific implementation process includes the following steps:

[0125] Interrupt triggering and context locking occurs when the dynamic calculation engine calculates the remainder check value. When the value is not zero, the system immediately activates the exception handling procedure. The central control terminal sends a work pause command to the front-end interactive device and the label printing device. Upon receiving the command, the front-end interactive device overlays a modal dialog box on the current interface to display the specific difference value and locks all input controls except for the exception reporting function. At the same time, the system updates the system status field of the current work order to the suspended state and rejects all subsequent write operation requests related to the work order at the database level until the exception is resolved.

[0126] For management access and loss entry, on-site management personnel or authorized QA personnel must unlock the system through a preset authentication interface. After successful authentication, the system renders a data correction interface on the front-end interactive device. This interface includes a loss type selection control and a loss quantity input box. Based on the actual situation found on-site, such as scrap during production, sampling loss, or incoming material shortage, management personnel enter the specific loss quantity on this interface. If the on-site investigation confirms that the actual number of remnants is correct... If an error occurs, administrators can trigger a reset input command at this step, causing the process to revert to the step that triggers a data backfill request.

[0127] Perform a lossy secondary verification when the system receives... Subsequently, the dynamic calculation engine introduces this variable for correction calculation. The system aims to verify whether the remaining quantity after deducting losses satisfies the divisibility relationship of the standard bin. The corrected verification logic is as follows:

[0128] ;

[0129] in, Defined as the corrected remainder check value; Represents the total number of work orders; This represents the standard full box quantity, which is introduced here. This represents the number of unavailable products identified during the revision process.

[0130] The system generates a corrected number of tags. If the number of the loss is not equal to the number of the remaining total number, the system prompts the user to input the loss number again, and refuses to release the suspended state, if , the system indicates that the job logic has met the quantity conservation condition by introducing the loss data, and then calculates the final number of the integer box label to be generated according to the modified data

[0131]

[0132] , wherein represents the number of integer box labels to be generated; represents the total number of work orders; represents the number of the measured mantissa; represents the loss number, if the current work order has not input the loss, the value of the variable is 0; represents the standard full box number, and through the formula, the system determines the total number of tasks entering the printing queue.

[0133] It is ensured that the total amount of integer labels in the final printing instruction issued by the system has accurately excluded the mantissa part and the production loss part, and the consistency between the system data and the physical object is realized.

[0134] After calculating the effective , the system automatically generates an exception handling log, records the time of triggering the interruption, the reason type causing the difference, the modifier ID and the modified value, and then updates the integer label printing state variable to the logical value 1, and closes the modal dialog box of the front-end device to restore the normal job interface. For the storage of log data, those skilled in the art can use the transaction log table of the relational database or a special audit log system to realize, which will not be described here.

[0135] Through the above steps, the system includes the inevitable loss and abnormal conditions in the production process into the digital control category, and uses the logical interruption mechanism to ensure that only when the data relationship is verified to be consistent, the production process can continue to flow down.

[0136] After the logical verification is passed and the printing permission is released, the system enters the batch data processing stage, and the task of this stage is to convert the numerical calculation result into a printer executable instruction queue to ensure that the number of generated physical labels is consistent with the system logical calculation value. The process is executed by the print control module, including the following steps:

[0137] State monitoring and process activation, the print control module runs in the background to monitor the integer label printing state variable ​​​the value of the number of integer boxes to be printed, when the monitoring value When the value changes from 0 to 1, the system activates the print job generation thread immediately, in order to prevent concurrent modification during the generation of print data, the system applies database row-level locks or enables optimistic lock version control mechanism to the relevant source data records including the total number of work orders and the measured number of decimal places, ensuring that the data read remains static and consistent during processing.

[0138] Performing global quantity final calculation, the print control module reads the latest variable value from the database before generating the final instruction for calculation, to ensure that the data covers the possible loss correction.

[0139] Building a print data stream, the system generates the corresponding size of the data structure in memory for storing the label data to be printed, the system uses a loop logic to generate the unique code of each integer box label, for the first integer box label (where ), the system combines the work order number, product material number and the current sequence index by string concatenation algorithm to generate the corresponding integer box unique identifier At this time, the system encapsulates independent print task data as a complete batch print job.

[0140] Print buffer and instruction issuing, the generated batch print job is sent to the print spooling subsystem, which is responsible for managing the memory buffer of the printer, and through the printer driver, the general print data is converted into the page description language supported by the specific printer hardware, including ZPL, TSPL or CPCL instruction set, the system controls the number of times of sending instructions according to the value of , and sends the instructions to the physical printer through the universal serial bus, Ethernet or serial communication interface. During the instruction sending process, the system counter records the number of instructions sent in real time, ensuring that the total number of print instructions sent is strictly equal to , ensuring the consistency of system output and physical action.

[0141] Through the above steps, the system converts the quantity from the logical calculation level to the action times of the physical device, realizing the mapping from data to physical object.

[0142] In the process of generating batch integer box labels, in order to ensure that each independent packaging unit can be accurately traced to the production batch it belongs to, the system uses a combination of encoding logic to embed the upper layer attributes into the data structure of the lower layer label, which realizes data analysis in a non-networked environment, the specific implementation process includes the following steps:

[0143] The upper-level anchoring parameters are extracted. The print control module extracts key attributes of the upper-level object from the current memory context. In this embodiment, the upper-level object is defined as the current production work order or production batch. The system obtains the unique identifier of the work order. and product material codes These two parameters constitute the common attribute data for all integer box labels, used to identify the consistency of products in the same batch.

[0144] The system constructs a structured encoded string. For each integer bin label to be generated, it constructs a string containing hierarchical relationships. For the first bin label in the sequence... Integer boxes ( The system introduces a standard full-box quantity. As a quantity attribute included in the encoding, the system performs the following encoding concatenation operation:

[0145] ;

[0146] in, Defined as the first Encoded strings for integer bins; The number of integer box labels to be generated; Represents a unique identifier for the work order; Represents the product material code; Represents the standard full box quantity; Represents string concatenation operation; This represents the preset delimiter, which can be either a group delimiter in ASCII code or a specific special character, and this character is not contained in the business data itself; This represents a serial number formatting function that performs left-padding with zeros to format an integer. Convert to fixed length A string of numbers.

[0147] The system generates check bits and image transcoding. To prevent data loss or errors during transmission or printing, the system performs check bit generation and image transcoding. Execute a data digest algorithm or verification algorithm, including MD5, SHA-256, or CRC-32, to generate a data check bit. This is then appended to the end of the encoded string. The encoding library then converts the final string, including the check digit, into a two-dimensional graphic matrix. The specific format of this graphic matrix includes DataMatrix, QRCode, or PDF417. The data is directly encoded in the graphic data payload. When scanning in the warehouse or logistics process, the scanning device can directly parse the standard quantity in the package without connecting to the backend database through the network, thus realizing the offline data parsing capability.

[0148] Establish a logical index mapping, while generating the graphic code, the system creates a hierarchical index record in the associated table of the database, the system performs a database insertion operation, binds the generated child identifier with the parent identifier, for the tail number label, the system also performs an association operation, but records the number field as the measured tail number quantity The system describes all the packaging units in this batch through the following relationship set:

[0149] ;

[0150] Wherein, is defined as a batch packaging data set; represents a unique identifier, which specifically refers to the tail number label identifier that has been anchored in the previous step; represents the integer box unique identifier generated by , which explicitly shows the parallel relationship between the tail number box and the integer box in the logical level under the same work order and the quantity attribute carried by each.

[0151] Through the above combination of encoding and association, the system ensures that each physical label is both an independent quantity carrier and part of the overall work order, thereby supporting full-link anti-counterfeiting traceability and inventory management.

[0152] In order to prevent security risks caused by long-term idle of printing permissions, or data obsolescence caused by job interruption, the system introduces a dynamic control mechanism based on time validity period, which takes effect after logical verification, ensuring that the printing instruction is only executed within the preset valid period. The specific implementation process is performed by the timing monitoring program of the print control module, including the following steps:

[0153] Initialize the time window parameter, when the integer label print state variable is updated to 1, the system starts the countdown logic at the same time, the system first calls the system call interface of the operating system to read the current system timestamp , which is marked as the job start time. At the same time, the system reads the valid printing time window from the configuration file (such as JSON or XML format file) stored in the local disk or remote configuration center, which is a preset time length such as 300 seconds, and its value is set by the administrator according to the standard production cycle of the production line.

[0154] Real-time timeliness judgment, during the execution of the printing task, that is, before sending the printing instruction of each label to the printer, the system will perform a timeliness check, the system obtains the current real-time timestamp , and performs the following logical judgment formula in combination with the above parameter:

[0155] ;

[0156] wherein, is defined as the print job active flag at the current time; represents the job start time; represents the valid print time window. The formula is used to determine whether the current time is still within the time range that allows the job, in order to ensure the accuracy of the time reference, the system preferentially uses the hardware real-time clock or the system clock calibrated through the network time protocol as the time source.

[0157] Timeout termination and queue clearing, if the calculation result shows that the current job has timed out, at this time, regardless of whether the batch print job is completed, the system immediately triggers the forced termination program, the system will forcibly reset to a logical value of 0, and send a cancel job instruction to the print spooler subsystem, the specific form of the instruction includes an immediate cancel instruction sent to the physical printer or calling the print management API of the operating system to withdraw all print tasks that have not been transmitted to the physical printer, at the same time, the front-end interactive device displays a timeout prompt, requiring the job personnel to re-verify the identity or apply for a time extension, thereby preventing expired data from being misprinted.

[0158] Print completion and permission recovery, if all labels are printed within the time window, the system performs the normal end process, the system compares the printed count with the integer box label generation quantity , when the two are equal, the system automatically updates to 0, and marks the work order as printed in the database, at this time, the system releases the lock on the total number of work orders and the measured tail number , allowing the next work order to be processed.

[0159] Through the above steps, the system combines time verification on the basis of quantity verification, further limiting the action range of the printer, ensuring that each label output is generated under the condition of logical and time dual validity.

[0160] After completing label printing and physical pasting, the system enters the final verification stage before warehousing, which verifies the consistency of the data by collecting the data of the physical label and verifying its consistency with the system pre-stored generated data, thereby verifying the data consistency, the process is performed by the warehousing management terminal or the handheld data collector, and specifically includes the following steps:

[0161] Physical label data collection, the operation personnel use the scanning terminal with wireless communication function to scan all the product boxes which have completed packaging and pasted labels, the scanning terminal includes handheld personal digital assistant with two-dimensional scanning engine, industrial tablet computer or fixed scanning frame, the system reads the two-dimensional code on each packaging box and decodes it into string format, in this process, the system does not limit the scanning order, and stores all the collected data in local temporary storage area or memory buffer, at the same time, the system performs local deduplication operation, if it is detected that the same label is scanned repeatedly, a prompt is issued and the repeated data is discarded to prevent false high count.

[0162] Constructing the measured data set, the system parses the data in the buffer area and extracts the key fields therein. The system identifies the unique identifier in each label, for the integer box label, the system extracts the integer box unique identifier ; for the fractional box label, the system extracts the unique identifier , i.e. the aforementioned fractional label identifier, the system aggregates these identifiers obtained through physical scanning into a new set, defined as the measured scanning data set .

[0163] Set consistency comparison, the system retrieves the batch packaging data set generated in step from the database, this data set represents the label set that the system logically believes should exist, the system uses hash algorithm or set difference algorithm to perform comparison operation, verifies whether the measured set and the preset set are completely equal, the comparison formula is as follows:

[0164] ;

[0165] Among them, is defined as the association verification state bit; represents the subset relationship operation, the technical meaning of this formula is: all scanned labels must exist in the system record to prevent mixing in non-batch labels; and all labels in the system record must be scanned to prevent missing scanning or physical loss. Only when the two sets are subsets of each other, i.e. the two sets are completely equal, the verification is passed.

[0166] Total quantity value review, on the basis of passing the set comparison, the system performs the second quantity value verification to ensure that the total quantity of physical objects is consistent with the work order requirements, the system traverses each element in , parses the quantity attribute contained therein, for the integer box, takes the standard full box quantity ; for the fractional box, takes the measured fractional quantity , the system performs the following cumulative verification formula:

[0167] ;

[0168] ;

[0169] wherein, is defined as the total number of measured scanning; represents the total number of elements in the measured scanning data set ; represents the number of scanning objects parsed out by the th scanning object; is defined as the final settlement state bit; represents the total number of work orders; represents the loss quantity.

[0170] The verification result output and abnormal interception, the system executes the subsequent operation according to the value of , if , the system outputs the verification pass signal on the display terminal, and automatically generates the warehouse entry document through the application programming interface or middleware data bridging, and pushes the data to the warehouse management system, if or , the system drives the buzzer and indicator light to issue an alarm, and highlights the difference list on the interface, that is, displays the missing label ID or the redundant label ID, and forcibly intercepts the entry operation until the job personnel finds out the reason and supplements or removes the relevant physical objects.

[0171] Through the above steps, the system uses the dual mechanisms of set consistency verification and total quantity value verification to ensure the accuracy of the entry data and realizes the complete management from the production plan to the physical entry.

[0172] After the entry physical verification is passed, the system needs to lock the state of the work order process to prevent subsequent invalid data modification. This process is realized by comprehensive judgment of the state bit of the whole process, which is executed by the central control module, including the following steps:

[0173] Whole process state logic operation, the system calls the state variables of each key node stored in the memory and database, executes logical and operation, to confirm that the preset conditions for completing the work order have been fully met, and the system executes the following completion judgment formula:

[0174] ;

[0175] wherein, is defined as the completion judgment result of the work order; represents the review state variable, that is, the QA review pass state confirmed in step; is defined as the print completion state variable, which is set to 1 after confirming that the print quantity is consistent in step; represents the associated verification state bit; representing the final settlement state bit; representing logical and operation, this formula ensures that each link from manual review, machine printing to physical storage has returned a success signal.

[0176] Execute database transaction commit, the system executes database operation according to the calculation result. If , it indicates that there is no exception in the whole link, the system opens the database transaction, updates the main state field of the current work order to completed, and at the same time, the system executes write protection lock on all data records associated with the work order, including work order attribute table, tail record table, printing log table and warehousing scanning record table. The specific implementation method is: set the access control list permission of the corresponding database row record to read-only, or migrate the data to read-only database view, and use the trigger of the database to intercept and refuse any UPDATE or DELETE instruction for this work order ID, so as to ensure the immutability of historical data.

[0177] Data archiving and ERP feedback, after the local database state is updated successfully, the system triggers the data synchronization service, the system encapsulates the final confirmed work order total number , the actual measurement tail number , the loss number and the final warehousing actual measurement scanning total number into JSON or XML format standard message packet, and sends the packet to the enterprise's resource planning system or manufacturing execution system through message queue middleware such as RabbitMQ or Kafka or RESTful API interface based on HTTPS protocol, completes the synchronization of financial settlement and inventory account, and for long-term storage of archived data, those skilled in the art can adopt optical disc library or cloud storage strategy of writing once and reading multiple times, which will not be described here.

[0178] Through the above steps, the system takes Boolean logic operation as the judgment core and database transaction characteristics as the execution guarantee, realizes the state termination of work order processing flow, and ensures the consistency of archived data and physical operation results.

Claims

1. A packaging method that enforces comparison of label last digits and batch numbers, characterized in that, Includes the following steps: Get the total number of work orders and the standard full box quantity of the current production work order, and receive the actual measured quantity of the remaining items. Perform quantity logic verification, determine the number of integer box labels to be generated based on the total number of work orders, the actual number of tails, and the standard full box quantity, and introduce the loss quantity during the verification process to ensure quantity balance; In response to the successful quantity logic verification, based on the determined number of integer box labels to be generated, coded data is generated and the printing device is controlled to output to obtain physical labels. At the same time, a batch packaging dataset containing unique identifiers for all integer boxes and last digit labels is constructed in the system. After the physical label and the corresponding last digit label are pasted onto the packaging unit, the graphic code data of the physical label on the packaging unit is collected to construct a measured scan dataset, and the measured scan dataset is compared with the batch packaging dataset for set consistency. After the set consistency comparison is passed, based on the matching result between the total number of the measured scan dataset and the total number of work orders after deducting the loss, it is determined whether the warehousing and case closure operation is allowed. The steps of performing quantity logic verification and introducing loss quantity specifically include: Calculate the preliminary balance after deducting the actual measured quantity from the total quantity of the work orders, and determine whether the preliminary balance is divisible by the standard full box quantity; If it is not divisible, the initial balance is corrected by the loss quantity entered by the user until the corrected balance is divisible by the standard full box quantity. Divide the corrected balance by the standard full box quantity, and the quotient is the number of box labels to be generated as the integer. The specific steps for the set consistency comparison are as follows: Verify whether the measured scan dataset is a subset of the batch packaging dataset to confirm that all scanned labels are within the system's preset range; Simultaneously verify whether the batch packaging dataset is a subset of the actual scan dataset to confirm that all preset labels in the system have been scanned; The set consistency comparison is considered successful only when the two datasets are subsets of each other; The steps for constructing the measured scan dataset include: Parse the collected graphic code data to obtain the unique identifier of the tag and the corresponding quantity attribute; Perform local deduplication to discard duplicate tag data; The unique identifiers of the deduplicated labels and their parsed quantity attributes are stored in the actual scan dataset.

2. The packaging method for forcibly comparing the last digit of the label and the batch number according to claim 1, characterized in that, The steps for generating encoded data include: A common prefix is ​​generated by combining the work order's unique identifier and the product's material code; Generate an incrementing sequence number and format it; The common prefix, the formatted serial number, and the standard full box quantity are concatenated in a preset order to form a unique identifier that includes an implicit quantity attribute.

3. The packaging method for forcibly comparing the last digit of the label and the batch number according to claim 1, characterized in that, The steps for controlling the output of the printing device also include: When initiating a print job, set the job start time and the effective print time window; Before outputting each physical label, verify whether the current time is within the valid printing time window; If the verification fails, the print job will be forcibly terminated and the buffer data will be cleared.

4. The packaging method for forcibly comparing the last digit of the label and the batch number according to claim 1, characterized in that, The steps for determining whether to allow the data entry and closure operation are specifically included: Calculate the sum of the number of labels parsed from all labels in the actual scan dataset to obtain the total number of actual scans; The theoretical net value of inventory is obtained by subtracting the amount of loss from the total number of work orders. The measured total number of scans is compared with the theoretical net value of the database. A control signal is generated to allow the case to be closed only when the two are completely equal.

5. The packaging method for forcibly comparing the last two digits of the label and the batch number according to claim 1, characterized in that, After allowing the entry and closure operation to be performed, the following is also included: Start a database transaction and update the master status of the current work order to "completed"; Perform write protection on all data records associated with the work order, set access permissions to read-only, or use database triggers to intercept data modification commands to prevent historical data from being tampered with.

6. The packaging method for forcibly comparing the last digit of the label and the batch number according to claim 1, characterized in that, After determining the required number of integer box labels to be generated, the following also includes: Parameters are set for the total number of work orders, the actual number of tails, and the memory address or database record where the loss quantity is located; During the printing of the physical label, it is forbidden to modify the locked parameters until the printing job is completed or terminated abnormally.

7. The packaging method for forcibly comparing the last two digits of the label and the batch number according to claim 1, characterized in that, After determining that the data entry and closure operation is permitted, the process also includes steps such as archiving production data and synchronizing it externally. Obtain and encapsulate the final confirmed total number of work orders, the actual number of tails, the number of losses, and the actual total number of scans, and generate a standard message message that conforms to a preset format; The standard message messages are sent to an external enterprise resource planning system via a message queue middleware to synchronize inventory records with production performance.

Images