Method for capturing discrepancies in equipment ledgers that integrate business flow characteristics

Abstract

This invention discloses a method for capturing equipment ledger discrepancy nodes that integrates business flow characteristics, relating to the fields of equipment asset management and equipment operation and maintenance management. The method determines the target ledger field with business flow write verification discrepancies based on the ledger record and business flow record of the target equipment. It identifies gap-forming nodes that generate write requirements for the target ledger field, and field rewriting nodes that rewrite the same target ledger field after the write requirement is formed and enter subsequent closure judgment. After an unclosed write gap is formed at the gap-forming node, it determines whether the rewriting of the field rewriting node can close the unclosed write gap. If it cannot close, it writes the obscured rewriting information to the corresponding gap record, and captures the equipment ledger discrepancy nodes obscured by the current display value based on the gap record.

Description

Technical Field

[0001] This invention relates to the fields of equipment asset management and equipment operation and maintenance management, and more specifically, to a method for capturing equipment ledger discrepancy nodes that integrate business flow characteristics. Background Technology

[0002] Equipment asset management and equipment operation and maintenance management technologies are commonly used to record ledger fields such as equipment status, location, responsible person, user department, and lifecycle stage, and to update the equipment ledger based on business processes such as equipment receipt, requisition, transfer, repair, return, inventory, and scrapping. In this scenario, the business log records the factual changes of equipment during the business process, and the equipment ledger records the write results of these factual changes in the corresponding ledger fields; there is usually a write correspondence between the two.

[0003] Existing methods for handling discrepancies in equipment ledgers typically link ledger records and business transaction records based on equipment number, asset number, or serial number. They then combine this with the currently displayed value, historical field write records, or the chronological order of business transactions to trace the source of the discrepancy. This approach can help pinpoint write discrepancies between equipment ledgers and business transactions when a single business transaction write fails, a single field value is inconsistent, or the correspondence between ledger fields and business transactions is relatively direct.

[0004] The existing technology has the following shortcomings: On the one hand, when the same target ledger field is continuously rewritten by multiple business nodes, the field rewriting node may rewrite the target ledger field based on its own business facts, and make the current displayed value reflect the field value corresponding to the later business facts. In this case, the current displayed value can only indicate that the target ledger field has formed a subsequent write result, but cannot prove that the write requirement corresponding to the gap forming node has been successfully closed by actual writing; the consequence is that the system may easily mistake the change in the current displayed value caused by the field rewriting node as the previous gap having ended, thus obscuring the unclosed write gap during the difference tracing process.

[0005] On the other hand, existing tracing methods based on historical field write records or business transaction time sequences can usually see the changes in the field values ​​of the target ledger field at different times, but it is difficult to distinguish whether the rewriting of a field rewriting node is a closing write to the unclosed write gap corresponding to the gap formation node, or an independent rewriting based on its own business facts. The consequence is that the gap formation node may be removed from the difference attribution chain, and subsequent rewriting, verification, and capture of equipment ledger difference nodes lack stable basis; the difficulty lies in the fact that it is difficult to confirm whether the rewriting has truly closed the previous unclosed write gap by relying solely on the current displayed value change or time sequence.

[0006] To overcome the aforementioned deficiencies of the prior art, embodiments of the present invention provide a method for capturing equipment ledger difference nodes that integrate business flow characteristics, in order to solve the problems mentioned in the background art. Summary of the Invention

[0007] To achieve the above objectives, the present invention provides the following technical solution: A method for capturing discrepancies in equipment ledgers by integrating business flow characteristics, including: S101, Based on the ledger records and business transaction records of the target device, identify the target ledger fields where there are differences in business transaction write verification; identify the gap forming node that generates the write requirement for the target ledger field from the business transaction records, and identify the field rewriting node that rewrites the target ledger field after the write requirement is formed and enters the subsequent closure judgment. S102, if the corresponding business fact has been completed at the gap formation node, should be written to the target ledger field, and the corresponding write value can be determined, if the target ledger field does not form a qualified actual write that can close the write requirement within the allowed write delay, then it is determined that the gap formation node has formed an unclosed write gap. S103, determine the writing basis corresponding to the field rewriting node; when the field rewriting node rewrites the target ledger field based on its own writing basis, and the rewriting changes the current display value of the target ledger field and makes the current display value conform to its own writing basis, determine whether the rewriting can close the unclosed writing gap; wherein, the writing basis is formed by the business facts completed by the field rewriting node itself, and is not derived, supplemented or retried from the writing requirements of the gap forming node; S104, when the rewrite cannot close the unclosed write gap, the write basis, rewrite result and current display value change of the field rewrite node are written to the gap record corresponding to the gap forming node, and the gap forming node is determined as the equipment ledger difference node of the target equipment; when the unclosed write gap is closed by qualified actual writing, the attribution retention corresponding to the gap forming node is released.

[0008] In a preferred embodiment, determining the gap-forming node that generates a write requirement for a target ledger field from the business transaction records includes: filtering candidate business nodes from the business transaction records; when a candidate business node has already formed a corresponding business fact completion record, there is a field write relationship between the candidate business node and the target ledger field, and a write value can be generated according to the field mapping rules corresponding to the business fact completion record and the target ledger field, a write requirement is generated, and the candidate business node is determined as the gap-forming node; wherein, the write requirement includes a gap-forming node identifier, a target ledger field identifier, a write value, and a write requirement formation time, and the allowable write delay is determined according to the field delay parameter corresponding to the target ledger field, the node delay parameter corresponding to the candidate business node, or the ledger update cycle parameter corresponding to the target device.

[0009] In a preferred embodiment, a qualified actual write is an actual write record that satisfies the requirements of field object correspondence, write basis correspondence, write value verification, and closed record generation; field object correspondence means that the field written in the actual write record is consistent with the target ledger field; write basis correspondence means that the write basis of the actual write record corresponds to the write requirement of the gap forming node, or corresponds to the supplementary write task or retry task generated by the write requirement; write value verification means that the actual write value in the actual write record is consistent with the write value, or satisfies the equivalence verification rule corresponding to the target ledger field; closed record generation means that the actual write record generates a closed record corresponding to the write requirement, and the closed record is used to update the corresponding gap closure status after an unclosed write gap is formed.

[0010] In a preferred embodiment, determining the self-writing basis corresponding to the field rewriting node includes: when the field rewriting node has formed its own business fact completion record, the writing source of the field rewriting node points to the field rewriting node, and the rewritten value is generated by the self-business fact completion record of the field rewriting node, it is determined that the field rewriting node has its own writing basis; when the writing source, writing task, and writing value generation process of the field rewriting node do not reference the write requirement, supplementary writing task, retry task, or derived task association identifier of the gap forming node, it is determined that the self-writing basis is not derived, supplemented, or retried from the write requirement of the gap forming node.

[0011] In a preferred embodiment, determining whether the rewrite can close the unclosed write gap includes: determining whether the rewrite of the field rewrite node satisfies source closure, value closure, and record closure; source closure is the write requirement, rewrite task, or retry task of the gap formation node corresponding to the write source of the field rewrite node; value closure is the rewrite value of the field rewrite node being consistent with the write value corresponding to the unclosed write gap, or satisfying the equivalence verification rule corresponding to the target ledger field; record closure is the rewrite of the field rewrite node generating a closed record that matches the write requirement identifier corresponding to the unclosed write gap; when at least one of source closure, value closure, and record closure is not met, it is determined that the rewrite of the field rewrite node cannot close the unclosed write gap.

[0012] In a preferred embodiment, determining that the rewriting of a field rewriting node changes the current display value of a target ledger field and makes the current display value conform to its own writing basis includes: when the rewritten field of the field rewriting node corresponds to the target ledger field, and the field value before rewriting is different from the field value after rewriting, determining that the field rewriting node changes the field value of the target ledger field; when the current display value of the target ledger field is consistent with the rewritten field value of the field rewriting node, and the current display value originates from the rewriting record of the field rewriting node, determining that the rewritten field value of the field rewriting node occupies the current display value of the target ledger field; when the current display value meets the self-basis compliance condition, and the unclosed write gap is still not closed, determining that the rewriting of the field rewriting node is a masking rewriting for the unclosed write gap; wherein, the self-basis compliance condition is that the current display value is consistent with the rewritten value generated by the field rewriting node based on its own writing basis, or the current display value meets the equivalence verification rule corresponding to the target ledger field.

[0013] In a preferred embodiment, the writing basis, rewriting result, and current display value change of the field rewriting node are written into the gap record corresponding to the gap forming node. This includes: establishing a gap record using the gap forming node identifier, the target ledger field identifier, and the write requirement identifier as the main index; writing the write requirement, write value, write requirement formation time, allowed write delay, and gap closure status corresponding to the gap forming node into the gap record; when the rewriting of the field rewriting node is determined to be a masking rewriting for an unclosed write gap, the field rewriting node identifier, the writing basis of the field rewriting node, the field value before rewriting, the field value after rewriting, the current display value change, and the inability to close the gap are written into the gap record; when the gap closure status in the gap record is unclosed, and there is masking rewriting information in the gap record, the gap record is used as the capture basis for determining that the gap forming node is the equipment ledger difference node of the target device.

[0014] In a preferred embodiment, when multiple field rewrite nodes are masked and rewritten for the same unclosed write gap, the masked and rewritten information corresponding to the multiple field rewrite nodes is appended to the same gap record according to the rewrite time order of each field rewrite node.

[0015] In a preferred embodiment, when an unclosed write gap is closed by a qualified write, the attribution retention corresponding to the gap formation node is released, including: updating the gap closure status in the gap record to closed, and writing the closure record corresponding to the qualified write to the gap record; after the gap closure status is updated to closed, the occlusion rewrite information in the gap record is stopped as the basis for capturing new equipment ledger difference nodes.

[0016] In a preferred embodiment, when the same target ledger field corresponds to multiple unclosed write gaps, gap records are established using the gap forming node identifier, the target ledger field identifier, and the write requirement identifier corresponding to each unclosed write gap. For the rewriting of the same field rewriting node, it is determined whether the rewriting can close each unclosed write gap. When the rewriting cannot close at least one of the unclosed write gaps, and the rewriting is determined to be a masking rewriting for the unclosed write gap, the masking rewriting information of the field rewriting node is written to the corresponding gap record. When any gap record satisfies the condition that the gap closure state is unclosed and there is masking rewriting information, the gap forming node corresponding to the gap record is determined as the equipment ledger difference node of the target device.

[0017] The effects and advantages of the device ledger difference node capture method integrating business flow characteristics of the present invention are as follows: This invention provides a method for capturing equipment ledger discrepancy nodes that integrates business flow characteristics. By identifying target ledger fields during business flow write verification discrepancies, and establishing continuous judgment criteria around gap formation nodes, field rewriting nodes, and unclosed write gaps, this method can determine whether the rewriting has truly closed the unclosed write gap corresponding to the gap formation node, even when the current displayed value has been occupied by a field rewriting node. By writing the unclosed, obscured rewriting information into the gap record corresponding to the gap formation node, this invention can keep subsequent changes in the current displayed value and previous unclosed write gaps in the same attribution chain, supporting the stable capture of equipment ledger discrepancy nodes. Therefore, the equipment ledger discrepancy processing can shift from simply tracing based on the current displayed value or time sequence to judging by combining the write source, rewritten value, and closing record, improving the traceability and consistency of discrepancy attribution, supplementary verification, and closure processing in continuous business node rewriting scenarios. Attached Figure Description

[0018] Figure 1 This is a schematic diagram of the method flow of the present invention; Figure 2A schematic diagram illustrating the principle behind the formation of discrepancies in the equipment ledger; Figure 3 This is a schematic diagram of the S103 process of the present invention; Figure 4 This is a schematic diagram of the S104 process of the present invention. Detailed Implementation

[0019] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0020] This invention provides a method for capturing equipment ledger discrepancy nodes that integrates business flow characteristics. It is applicable to equipment asset management and equipment operation and maintenance management, targeting the field write relationships between the ledger records and business flow records of a target device, and identifying equipment ledger discrepancy nodes obscured by changes in the currently displayed value. The target ledger field is the ledger field in the target device's ledger record where there are business flow write verification discrepancies, and which this method continuously judges; the currently displayed value is the field value of the target ledger field that is currently presented externally or read by the system as its latest state.

[0021] Existing equipment ledger discrepancy handling typically links ledger records and business transaction records based on equipment number, asset number, or serial number, and then traces the source of the discrepancy based on the current displayed value, historical field write records, or the time sequence of business transactions. This method can usually pinpoint the source of the discrepancy between ledger records and business transaction records when a single business fact write fails or a single field value is inconsistent. However, when the same target ledger field is continuously rewritten by multiple business nodes, the current displayed value may already be the field value corresponding to the later business fact, making the ledger appear to have been updated.

[0022] In the aforementioned continuous rewrite scenario, the business node that completes its business transaction earlier and should be written to the target ledger field may not have formed a qualified write within the allowed write delay. This business node corresponds to a gap formation node and an unclosed write gap. Subsequently, the business node rewriting the same target ledger field may simply occupy the current display value based on its own business transaction, thus forming a field rewrite node. At this point, the change in the current display value does not necessarily mean that the unclosed write gap has been closed by a qualified write. If the system only ends the tracing based on the change in the current display value or the time sequence of the business flow, it is easy to cause the gap formation node to be removed from the difference attribution chain, thereby missing the device ledger difference nodes that are obscured by the current display value.

[0023] To this end, after identifying the target ledger field where there is a discrepancy in the business flow write verification, this invention identifies the gap forming node that generates a write requirement for the target ledger field, and identifies the field rewriting node that rewrites the same target ledger field after the write requirement is formed and enters the subsequent closure judgment; further, it determines whether the rewriting of the field rewriting node can close the unclosed write gap corresponding to the gap forming node, and if it cannot be closed, the rewriting information of the field rewriting node is written into the gap record corresponding to the gap forming node, thereby binding the subsequent changes in the current display value with the previous unclosed write gap, and capturing the device ledger difference node that is obscured by the current display value.

[0024] Based on the above technical means, this invention constructs a complete process for capturing device ledger difference nodes that integrate business flow characteristics, consisting of steps S101 to S104 sequentially. (Refer to...) Figure 1 , Figure 1 This is a schematic diagram of the method flow of the present invention, which includes: Step S101 is used to identify, for the target device, target ledger fields with business flow record write verification differences based on the ledger records and business flow records of the target device, and to identify gap formation nodes that generate write requirements for the target ledger fields, as well as field rewriting nodes that rewrite the same target ledger field after the write requirement is formed and enter the subsequent closure judgment. The target ledger field is the ledger field in the target device's ledger record that has a business flow record write verification difference with the business flow record; the gap formation node is the business node that has completed the corresponding business fact and generates a write requirement for the target ledger field based on the field write relationship and field mapping rules of the target ledger field; the field rewriting node is the business node that, after the write requirement corresponding to the gap formation node is formed, rewrites the same target ledger field based on its own business fact and enters the subsequent rewriting closure judgment. Thus, step S101 associates the state of the target ledger field with the changes in business facts in the business flow record, providing an object basis for subsequently identifying unclosed write gaps and judging whether the rewriting of the field rewriting node can close the unclosed write gap.

[0025] Step S102 is used to determine whether the gap-forming node creates a write requirement for the target ledger field based on the business facts corresponding to the gap-forming node, the field write relationship corresponding to the target ledger field, and the field mapping rules. After generating the write value according to the field mapping rules, it is determined whether the target ledger field forms a qualified actual write within the allowed write delay. A qualified actual write is an actual write record used to close the write requirement corresponding to the gap-forming node. Its judgment criteria include field object correspondence, write basis correspondence, write value verification, and record closure generation. When the gap-forming node has already created a write requirement, and the target ledger field has not formed a qualified actual write within the allowed write delay, the unclosed write gap corresponding to the gap-forming node is determined, so that subsequent steps can determine whether the rewriting of the field rewriting node can close the gap based on the unclosed write gap.

[0026] Step S103 is used to determine whether the modification of the target ledger field by the field modification node can close the unclosed write gap during the existence of the unclosed write gap. This step first determines whether the field modification node has its own writing basis, and determines whether the field modification node modifies the target ledger field based on its own writing basis, and whether the current display value of the target ledger field originates from the modification of the field modification node. Further, this step determines whether the modification satisfies source closure, value closure, and record closure based on the writing source, modified value, and closing record of the field modification node; when at least one of the source closure, value closure, and record closure is not met, a non-closure judgment result is generated, which indicates that although the modification of the field modification node causes a change in the current display value, it cannot close the unclosed write gap corresponding to the gap forming node.

[0027] Step S104 is used to generate occlusion rewrite information corresponding to the rewrite when the rewrite of the field rewrite node cannot close the unclosed write gap, and write the occlusion rewrite information into the gap record corresponding to the gap forming node. The gap record uses the gap forming node identifier, the target ledger field identifier, and the write requirement identifier as the main index to carry the basic information of the unclosed write gap, the gap closure status, and the occlusion rewrite information. Therefore, when the gap closure status of the gap record is unclosed and there is occlusion rewrite information, the gap forming node corresponding to the gap record is determined as the equipment ledger difference node of the target device, thereby capturing the preceding difference node that is occluded by subsequent changes in the current displayed value.

[0028] It should be noted that when the same unclosed write gap corresponds to multiple masking rewrites, the system appends the masking rewrite information in the order of rewrite time. When the unclosed write gap is subsequently closed by a qualified write operation, the system updates the gap closure status. When the same target ledger field corresponds to multiple unclosed write gaps, the system performs separate checks on each gap.

[0029] The following describes specific embodiments and references. Figure 2 This invention explains the formation principle and subsequent processing procedure of the device ledger difference node being obscured by subsequent changes in the currently displayed value in the method of the present invention. This embodiment is used to illustrate the technical solution of the present invention. The specific device type, ledger fields, business node name, field mapping rules, allowed write delay, and equivalence verification rules can be configured according to the actual device asset management scenario.

[0030] In one embodiment, the system is used to correlate the ledger records and business transaction records of a target device during equipment asset management to capture equipment ledger discrepancy nodes that are obscured by subsequent changes in the currently displayed value. The target device is a single device object that is captured by the ledger discrepancy node. The ledger records are used to record ledger fields such as the target device's status, location, responsible person, user department, and lifecycle stage. The business transaction records are used to record changes in business facts of the target device during business processes such as warehousing, requisition, transfer, maintenance, return, inventory, and scrapping.

[0031] This embodiment uses the device location field of target device D001 as an example for explanation. The device location field is used to record the current warehouse, usage location, or maintenance location of target device D001. Before the transfer of target device D001 is completed, the current displayed value of the device location field is warehouse number one.

[0032] Reference Figure 2 , Figure 2 This diagram illustrates the formation principle of discrepancy nodes in the equipment ledger. In scenarios where continuous business flows affect the same ledger field, the current displayed value of the ledger field typically only reflects the field's status after the most recent field write. If we only rely on the current displayed value to determine whether the ledger field has been updated with business changes, we may easily overlook the write requirements of earlier business nodes that have been formed but not yet closed. In other words, the current displayed value can reflect subsequent business facts, but it does not necessarily mean that the field write obligation corresponding to the preceding business node has been closed.

[0033] In this embodiment, the allocation completion node N1 generates a write request for the device location field, with the write value being Library 2. However, this write request is not successfully written within the allowed write delay, thus creating a corresponding unclosed write gap. Subsequently, the maintenance transfer node N2 rewrites the same device location field to the maintenance area based on its own business facts, ensuring that the current displayed value of the device location field reflects the maintenance transfer business facts.

[0034] In the above situation, if only the current displayed value of the device location field (repair area) is read, it is easy to mistakenly assume that the subsequent business rewriting has been completed, thus ignoring the existence of the unclosed write gap corresponding to the transfer completion node N1. Therefore, this embodiment does not directly end the previous write requirement with the current displayed value, but further determines whether the rewriting of the maintenance transfer node N2 can close the unclosed write gap corresponding to the transfer completion node N1.

[0035] In step S101, the system reads the ledger records and business transaction records of the target device and determines the target ledger fields, gap formation nodes, and field rewriting nodes required for subsequent gap judgment and rewrite closure judgment. This step is used to establish the correspondence between the same target device, the same target ledger fields, and the preceding and following business nodes, providing an object basis for subsequent judgment of unclosed write gaps and for judging whether subsequent rewrites can close the gap.

[0036] Specifically, the system reads the corresponding ledger field from the ledger record based on the device identifier of the target device, and reads the business node record related to the target device from the business flow record. The business node record includes at least the business node identifier, business fact completion status, business completion time, field write relationship, and field mapping rule. The field write relationship can come from the ledger field configuration, business node configuration, or field rule information in the business flow record corresponding to the target device, and is used to indicate the ledger field that should be written after a certain business node is completed. The field mapping rule is used to generate the write value of the corresponding ledger field based on the business fact content in the business node, and it can include the business fact field, the target ledger field identifier, and the write value generation rule.

[0037] The system determines whether a business node has formed a business fact completion record based on the business fact completion status in the business node record; it determines whether the business node should be written to the corresponding ledger field after completion based on the field write relationship; and it extracts the corresponding business fact field from the business fact completion record according to the field mapping rules to generate the write value of the target ledger field. When the field write relationship is missing, or the field mapping rule cannot generate a unique write value, the system does not identify the business node as a gap formation node and temporarily prevents the business node from entering the subsequent gap formation judgment.

[0038] Business transaction record write verification discrepancy refers to a situation where a business transaction record has completed the record based on business facts, field write relationships, and field mapping rules to form the expected value of a target ledger field, but the current displayed value or most recently written value of that target ledger field in the ledger record does not match the expected value, and the field write discrepancy does not satisfy the equivalence verification rules corresponding to the target ledger field. When a business transaction record shows that a certain business node has formed a business fact completion record, and that business node should write to a certain ledger field, but the current displayed value or most recently written value of that ledger field does not match the corresponding expected value, the system identifies that ledger field as the target ledger field.

[0039] In this embodiment, the target device is device D001. The system reads the ledger record of device D001 and determines that the current displayed value of the device location field is warehouse number one. The system reads the business transaction record of device D001 and identifies that the transfer completion node N1 corresponding to the transfer transaction DB20260501 has formed a business fact completion record. This business fact indicates that device D001 has been transferred from warehouse number one to warehouse number two. According to the field writing relationship corresponding to the device location field, the device location field should be written after the transfer completion node N1 is completed. According to the field mapping rules, the target warehouse field in the transfer transaction is mapped to the write value of the device location field as warehouse number two. Since the current displayed value of the device location field is still warehouse number one, while the write value corresponding to the transfer completion node N1 is warehouse number two, the system determines the device location field as the target ledger field.

[0040] The system further identifies business nodes that generate write requirements for the target ledger field from the business transaction records. When a business node has formed a business fact completion record, points to the target ledger field through the field write relationship, and can generate the write value for the target ledger field according to the field mapping rules, the system identifies this business node as a gap-forming node. In this embodiment, the transfer completion node N1 has formed a business fact completion record, can point to the equipment location field, and can generate the write value database 2. Therefore, the system identifies the transfer completion node N1 as a gap-forming node.

[0041] The system also reads business nodes located after the gap formation node according to the business completion time and determines whether the business node rewrites the same target ledger field based on its own business facts. When the business node has already formed its own business fact completion record, the rewriting time is later than the writing requirement formation time corresponding to the gap formation node, and its rewriting record points to the same target ledger field, the system considers the business node as a candidate field rewriting node. For business nodes that rewrite other ledger fields, or business nodes that involve the target ledger field but cannot form a target ledger field rewriting record, the system does not consider them as field rewriting nodes for this unclosed write gap.

[0042] Furthermore, the system combines the source record of the current displayed value of the target ledger field to determine whether the candidate field rewriting node should enter the subsequent rewriting closure judgment. When the rewriting record of the candidate field rewriting node can serve as a candidate source of the source record of the current displayed value of the target ledger field, or when the rewriting record has already changed the current displayed value of the target ledger field, the system determines the candidate field rewriting node as a field rewriting node to enter the subsequent closure judgment. Thus, subsequent steps only perform closure judgment on field rewriting nodes that may affect the current displayed value and may obscure the previous unclosed write gap.

[0043] In this embodiment, the maintenance transfer node N2 corresponding to the maintenance transfer flow has formed a business fact completion record, which indicates that device D001 has been transferred to the maintenance area. The business completion time of maintenance transfer node N2 is later than the write request formation time corresponding to transfer completion node N1, and it rewrites the device location field to maintenance area according to its own business fact. Therefore, the system determines maintenance transfer node N2 as a field rewriting node. Whether this field rewriting node is in the period of unclosed write gap existence is jointly determined by the unclosed write gap status output in step S102 and the rewrite closure judgment in step S103.

[0044] In step S102, based on the target ledger field and gap formation node output in step S101, the system determines whether the gap formation node has formed a write requirement for the target ledger field, and whether the write requirement has been successfully closed by actual writing within the allowed write delay. This step is used to determine whether the preceding business node has formed an unclosed write gap, providing a target gap for the rewrite closure judgment of subsequent field rewrite nodes.

[0045] Specifically, the system reads the business fact completion record corresponding to the gap forming node, the field writing relationship corresponding to the target ledger field, and the field mapping rule. When the gap forming node has formed a business fact completion record, and the field writing relationship points to the target ledger field, and can generate the write value according to the field mapping rule, the system determines that the gap forming node has a write requirement for the target ledger field. In this embodiment, the transfer completion node N1 has formed a business fact completion record of equipment D001 being transferred from warehouse 1 to warehouse 2. The field writing relationship corresponding to the equipment location field points to the ledger field, and the field mapping rule maps the target warehouse field in the transfer flow to warehouse 2. Therefore, the system determines that the transfer completion node N1 has a write requirement for the equipment location field and determines warehouse 2 as the write value.

[0046] After determining the write requirement, the system reads the allowable write delay corresponding to the target ledger field. The allowable write delay represents the time range within which the target ledger field is allowed to be delayed in forming a valid write operation from the time the write requirement is generated. Its time unit can be determined according to the unified time unit of the ledger system where the target device is located. The system prioritizes reading the field delay parameter corresponding to the target ledger field; if the field delay parameter is not configured, it reads the node delay parameter corresponding to the gap formation node; if neither is configured, it reads the ledger update cycle parameter corresponding to the target device. When the time units of different parameters are inconsistent, the system first converts them to the unified time unit of the ledger system before determining whether the allowable write delay has been exceeded. When the time of the write requirement cannot be determined, or when none of the above parameters are configured, the system does not directly determine an unclosed write gap and temporarily does not proceed to subsequent rewrite closure judgment based on this write requirement.

[0047] In this embodiment, the system reads the field delay parameter corresponding to the device location field, and uses the time when the allocation completion node N1 forms a write request for the device location field as the starting point to determine the allowable write delay corresponding to the write request.

[0048] Before the allowed write delay expires, the system continuously reads the actual write records of the device location field, either continuously or according to a preset detection cycle. The actual write record is the actual write record of the target ledger field, and includes at least the written field, the writing basis, the actual write value, and the write time. The preset detection cycle can be determined by the detection cycle parameter corresponding to the target ledger field or the ledger update cycle parameter corresponding to the target device. The system determines whether the actual write record constitutes a qualified write record. A qualified write record is one that can close the gap forming node and meet the write requirements. The determination includes field object correspondence, writing basis correspondence, write value verification, and record closure generation.

[0049] Field object correspondence means that the fields written in the actual record are consistent with the target ledger fields; writing basis correspondence means that the writing basis of the actual record corresponds to the writing requirement of the gap forming node, or corresponds to the supplementary writing task or retry task generated by the writing requirement; writing value verification means that the actual value is consistent with the writing value, or meets the equivalence verification rules corresponding to the target ledger fields; closed record generation means that the actual record generates a closed record corresponding to the writing requirement identifier, and the closed record records the writing requirement identifier, the actual record identifier, the actual writing time, and the closure result. When all the above judgments are true, the system determines that the actual record is a qualified actual record that can close the writing requirement.

[0050] When the write request has not yet formed an unclosed write gap, a closing record is used to indicate that the write request has been closed by the corresponding write record; when the write request has formed an unclosed write gap, a closing record is used to update the gap closure status in the corresponding gap record to closed. If either judgment is not true, the system will not determine the write record as a qualified write of the write request.

[0051] In some implementations, the equivalence verification rules corresponding to the equipment location field can be provided by the equivalence representation configuration table corresponding to the target ledger field. For example, Warehouse No. 2 can be configured as an equivalent location representation with Warehouse No. 2, Warehouse 2, or Warehouse No. K02; if the maintenance area is not configured as an equivalent location representation of Warehouse No. 2, the equivalence verification rules corresponding to Warehouse No. 2 are not satisfied. When the target ledger field is not configured with an equivalence representation configuration table, the system uses the direct consistency between the actual written value and the expected written value as the basis for verification of the written value; when the same actual written value corresponds to multiple candidate equivalent representations and cannot be uniquely determined, the system determines that the written value verification is invalid, or temporarily does not confirm that the written value verification is valid.

[0052] In this embodiment, when the write delay expires, the current displayed value of the device location field is still library number one. The system has not read a qualified write operation for the transfer completion node N1, nor has it read a closed record corresponding to the write request identifier of the transfer completion node N1. Therefore, the system determines that the write request formed by the transfer completion node N1 for the device location field has not been closed by a qualified write operation, and an unclosed write gap is formed corresponding to the transfer completion node N1.

[0053] The system generates the unclosed write gap status information corresponding to the allocation completion node N1, and uses this status information as input for step S103. This status information includes the gap formation node identifier, target ledger field identifier, write requirement identifier, write value, write requirement formation time, allowed write delay, and gap closure status. The write requirement identifier can be generated based on the gap formation node identifier, target ledger field identifier, and business facts, or it can be read from business transaction records or field write task records.

[0054] It should be noted that the business flow write verification difference in step S101 is used to filter the target ledger fields that need to be judged by this method from the ledger field level, and the unclosed write gap in step S102 is used to confirm whether the write requirement corresponding to the specific gap forming node under the target ledger field has exceeded the allowed write delay and has not been closed by qualified actual write. The former determines the field-level entry point, and the latter determines the node-level gap object. The subsequent rewrite closure judgment uses the unclosed write gap status information formed in step S102 as the judgment object.

[0055] In this embodiment, the gap formation node is identified as the transfer completion node N1, the target ledger field is identified as the equipment location field, the write value is warehouse number two, and the gap closure status is unclosed. Therefore, subsequent steps do not directly end the write request based on the latest current display value of the target ledger field, but instead use this unclosed write gap as the object for rewrite closure judgment. Step S102 does not determine whether the rewrite of the maintenance transfer node N2 constitutes an occlusion rewrite; this judgment is completed in step S103.

[0056] Reference Figure 3 In step S103, the system determines whether the field rewriting node can close the unclosed write gap by modifying the target ledger field based on the field rewriting node output in step S101 and the unclosed write gap output in step S102. This step is used to distinguish between the field rewriting generated by subsequent business nodes based on their own business facts and the closing write performed on the previous unclosed write gap.

[0057] Specifically, the system reads the business fact completion record, write source, write value generation process and rewrite record of the field rewrite node, and reads the write requirement, write value, supplementary write task, retry task and unclosed write gap status corresponding to the gap formation node; the rewrite record is the record generated after the field rewrite node performs rewrite on the target ledger field, which includes at least the rewritten field, the field value before rewrite, the field value after rewrite, the write source and the rewrite time.

[0058] The current display value source record indicates the most recent write source corresponding to the current display value of the target ledger field. It can be determined by the most recent write record of the ledger field, the field rewrite record, or the current value source identifier. The system determines whether the current display value originates from the rewrite record of the field rewrite node based on the write record identifier in the most recent write record of the ledger field, the rewrite record identifier in the field rewrite record, and the current value source identifier. When the above records can point to the same field rewrite node, and the current display value is consistent with the rewritten field value of that field rewrite node, the system determines that the current display value originates from the rewrite record of that field rewrite node.

[0059] A supplementary write task is a task derived from the write requirements of a gap-forming node. A retry task is a write task executed again after a previous write failure or incomplete closure. The system can determine whether a task corresponds to the write requirements of a gap-forming node based on the write requirement identifier, gap-forming node identifier, supplementary write task identifier, or retry task identifier in the task record. When the most recently written record, field modification record, and current value source identifier of a ledger field cannot correspond to each other, or the source of the current displayed value cannot be uniquely determined, the system will not directly determine the modification of the field modification node as the source of the current displayed value and will generate a source pending verification mark.

[0060] The system first determines whether a field rewriting node has its own writing basis. The writing basis refers to the writing basis formed by the field rewriting node based on its own business facts, and this writing basis is not associated with the writing requirements, supplementary writing tasks, or retry tasks of the gap-forming node. When the writing source, writing task, or writing value generation process of a field rewriting node is missing, making it impossible to determine whether the rewriting references the writing requirements, supplementary writing tasks, or retry tasks of the gap-forming node, the system generates a source pending verification flag and temporarily does not determine that the field rewriting node has its own writing basis. The source pending verification flag is used to record the reason why the field rewriting node cannot enter the masked rewriting judgment. Its recorded content includes the field rewriting node identifier, the target ledger field identifier, the current displayed value source candidate record, and the reason for pending verification. While the source pending verification mark exists, the system will not write the rewrite of the field rewrite node into the gap record, nor will it write the rewrite as a qualified real write closure unclosed into the gap; when the current displayed value source record, field rewrite record or closure record is completed, the system will re-determine whether the rewrite satisfies the source closure, value closure and record closure based on the completed record.

[0061] In this embodiment, the field rewriting node is the maintenance transfer node N2; the system reads the maintenance transfer log and determines that the maintenance transfer node N2 has formed a business fact completion record, and its writing source points to the maintenance transfer business itself. The written value maintenance area is generated by the target maintenance location field in the maintenance transfer log; the writing source does not carry the write requirement identifier, rewrite task identifier or retry task identifier of the transfer completion node N1, so the system determines that the maintenance transfer node N2 has its own writing basis.

[0062] The system further determines whether the field rewriting node rewrites the target ledger field based on its own writing basis, and whether the current displayed value of the target ledger field originates from the rewriting record of the field rewriting node. In this embodiment, the rewriting record of maintenance transfer node N2 points to the equipment location field, and the rewritten field value is maintenance area. The system reads the ledger record of equipment D001 and determines that the current displayed value of the equipment location field has changed from warehouse number one to maintenance area, and the source record of the current displayed value points to the rewriting record of maintenance transfer node N2. This current displayed value is consistent with the rewriting value generated by maintenance transfer node N2 based on its own business facts, and can reflect the subsequent business facts corresponding to maintenance transfer node N2.

[0063] The current displayed value reflects the subsequent business facts corresponding to the maintenance transfer node N2, but only indicates that the equipment location field has been rewritten and occupied by subsequent business. It does not prove that the write requirement corresponding to the transfer completion node N1 has formed a qualified write closure. Therefore, the system continues to determine whether the rewrite can close the unclosed write gap corresponding to the transfer completion node N1.

[0064] This judgment includes source closure, value closure, and record closure. Source closure is used to confirm whether the rewrite addresses a preceding gap. Source closure is determined when the write request identifier, gap formation node identifier, fill task identifier, or retry task identifier carried in the write source of the field rewrite node matches the corresponding identifier in the unclosed write gap status information. Value closure is used to confirm whether the rewritten value satisfies the preceding write value. Record closure is used to confirm whether the rewrite has a closure record basis corresponding to the write request identifier.

[0065] In this embodiment, the write source of maintenance transfer node N2 does not correspond to the write request identifier of transfer completion node N1, nor does it correspond to the rewrite task or retry task of transfer completion node N1; therefore, source closure is not established. The rewritten value of maintenance transfer node N2 is in the maintenance area, which does not belong to the write value library 2 or its equivalent position expression; therefore, value closure is not established. The system did not read the closed record corresponding to the write request identifier of transfer completion node N1; therefore, record closure is not established.

[0066] When source closure, value closure, and record closure are all true, the system determines that the rewrite can close the corresponding unclosed write gap and uses the closure result to update the closure status of subsequent gaps. When at least one of source closure, value closure, and record closure is false, the system generates a non-closure judgment result. In this embodiment, although the rewrite of the maintenance transfer node N2 changes the current displayed value of the equipment location field to the maintenance area, it cannot close the unclosed write gap corresponding to the transfer completion node N1. Therefore, the system generates a non-closure judgment result. This non-closure judgment result proceeds to step S104 to trigger the masking rewrite information to be written to the gap record.

[0067] Reference Figure 4 In step S104, the system determines whether the current rewrite of the field rewrite node constitutes a masking rewrite based on the unclosed write gap output in step S102 and the non-closing judgment result output in step S103. If a masking rewrite is constituted, the masking rewrite information corresponding to the current rewrite is written into the gap record corresponding to the gap forming node. This step is used to bind the previous unclosed write gap and the subsequent masking rewrite information to the same gap record, and to determine the equipment ledger difference node accordingly.

[0068] Specifically, the system reads the unclosed write gap status information corresponding to the gap forming node, the rewrite record of the field rewriting node, the current display value source record, and the inability to close the gap judgment result. When a field rewriting node rewrites a target ledger field based on its own writing basis, and the current display value of the target ledger field comes from the rewrite of this field rewriting node, and this rewrite cannot close the unclosed write gap corresponding to the gap forming node, the system determines this rewrite of the field rewriting node as a masked rewrite. A masked rewrite is used to indicate that this rewrite forms and occupies the current display value of the target ledger field, but cannot close the corresponding unclosed write gap.

[0069] In this embodiment, the write value formed by the allocation completion node N1 for the device location field is Library No. 2, and this write request is not closed by a qualified actual write within the allowed write delay. The maintenance transfer node N2 rewrites the device location field to the maintenance area based on the maintenance transfer pipeline, and changes the current displayed value of the device location field to the maintenance area. Step S103 has generated a non-closure judgment result, indicating that this rewrite by the maintenance transfer node N2 cannot close the unclosed write gap corresponding to the allocation completion node N1. Therefore, the system determines this rewrite by the maintenance transfer node N2 as a masked rewrite.

[0070] After determining the occlusion rewrite, the system generates occlusion rewrite information. This information includes the field rewrite node identifier, its own writing basis, the field value before rewrite, the field value after rewrite, the change in the current displayed value, and the non-closure judgment result. In this embodiment, the field rewrite node identifier is maintenance transfer node N2, and its own writing basis is the maintenance transfer log; the field value before rewrite is the current displayed value of the equipment location field before the rewrite record is generated, which in this embodiment is library number one; the field value after rewrite is the maintenance area; the change in the current displayed value is that the equipment location field changes from library number one to the maintenance area; the non-closure judgment result indicates that this rewrite cannot close the unclosed write gap corresponding to the transfer completion node N1.

[0071] The system establishes a gap record G1 based on the unclosed write gap status information corresponding to the allocation completion node N1. This gap record G1 corresponds to the unclosed write gap status information output in step S102. Gap record G1 uses the node identifier of allocation completion node N1, the equipment location field identifier, and the write requirement identifier formed by allocation completion node N1 for the equipment location field as its primary index. It also records the write requirement corresponding to allocation completion node N1, the write value database, the write requirement formation time, the allowed write delay, and the gap closure status. The gap record uses the gap formation node, the target ledger field, and the write requirement as its index, rather than the latest currently displayed value of the target ledger field. Therefore, it can retain the attribution object of the previous gap even after subsequent changes in the current displayed value.

[0072] In some implementations, the gap record also records the target device identifier, gap record identifier, field rewrite node identifier, self-writing basis identifier, field value before rewrite, field value after rewrite, current display value change, inability to close judgment result, time of writing obscured rewrite information, closing record identifier, and closing time. Specifically, the target device identifier, gap formation node identifier, target ledger field identifier, and required writing identifier are used to determine the preceding unclosed write gap corresponding to the gap record; the field rewrite node identifier, self-writing basis identifier, field value before rewrite, field value after rewrite, current display value change, and inability to close judgment result are used to record the occupancy of the current display value by subsequent rewrites and the judgment result of the inability to close the preceding gap; the closing record identifier and closing time are used to update the gap closure status when a qualified actual write is subsequently formed.

[0073] When the missing node identifier, target ledger field identifier, or required write identifier makes it impossible to uniquely establish a missing record, the system will not temporarily establish the corresponding missing record and will not output the device ledger difference node based on the information of this record.

[0074] The system writes the occlusion rewrite information corresponding to the maintenance transfer node N2 into the gap record G1. After writing, the gap record G1 simultaneously inherits the unclosed write gap basic information of the transfer completion node N1 and the occlusion rewrite information of the maintenance transfer node N2, so that the preceding gap corresponding to the transfer completion node N1 and the subsequent current display value change corresponding to the maintenance transfer node N2 are associated under the same gap record.

[0075] When a gap record's gap closure status is unclosed, and the gap record contains occlusion rewrite information, the system identifies the gap forming node corresponding to the gap record as an equipment ledger difference node and outputs the corresponding equipment ledger difference node result. This equipment ledger difference node result includes the target equipment identifier, target ledger field identifier, gap forming node identifier, write requirement identifier, write value, gap record identifier, gap closure status, and corresponding occlusion rewrite information identifier. This indicates that the difference node originates from the unclosed write gap corresponding to the gap forming node, rather than from a change in the current displayed value formed by a field rewrite node.

[0076] In this embodiment, the gap closure status of gap record G1 is unclosed, and the occlusion rewrite information of maintenance transfer node N2 has been written. Therefore, the system identifies the transfer completion node N1 as the equipment ledger difference node for equipment D001, and outputs the equipment ledger difference node result containing equipment D001, the equipment location field, the transfer completion node N1, the gap record G1, and the occlusion rewrite information identifier corresponding to the maintenance transfer node N2. Thus, even if the current displayed value of the equipment location field has changed to the maintenance area, the system can still capture the preceding unclosed write gap corresponding to the transfer completion node N1 based on the gap record.

[0077] In some implementations, when multiple field rewrite nodes are obscured by the same unclosed write gap, the system writes the obscured rewrite information into the same gap record according to the rewrite time order of each field rewrite node. Specifically, after determining that the rewrite of a certain field rewrite node constitutes an obscured rewrite, the system determines the corresponding gap record based on the gap forming node identifier, target ledger field identifier, and write requirement identifier corresponding to the obscured rewrite. When the gap closure status of the gap record is still unclosed, the system writes the obscured rewrite information corresponding to the field rewrite node into the gap record and saves each obscured rewrite information in the rewrite time order.

[0078] In the extended example of this embodiment, after the maintenance transfer node N2 rewrites the equipment location field to the maintenance area, if the target equipment D001 is returned to the completion node N3, and the completion node N3 rewrites the equipment location field to the usage location A based on its own business facts, then the system, according to the rewrite closure judgment method in step S103, determines whether the rewrite by the completion node N3 can close the unclosed write gap corresponding to the transfer completion node N1. When the rewrite by the completion node N3 cannot close the unclosed write gap, the system writes the occlusion rewrite information corresponding to the completion node N3 into the gap record G1 in the order of rewrite time.

[0079] In some implementations, when an unclosed write gap is subsequently closed by a valid write operation, the system updates the gap closure status in the corresponding gap record and removes the attribution retention corresponding to the gap formation node. Attribution retention is indicated by the attribution retention status field in the gap record, which records whether the gap record continues to be used as the basis for capturing equipment ledger difference nodes. When the gap closure status is unclosed and there is occlusion rewrite information in the gap record, the attribution retention status field is "retained"; when the gap closure status is updated to "closed," the attribution retention status field is updated to "removed." After removing attribution retention, the system stops using the occlusion rewrite information in the gap record as the basis for capturing new equipment ledger difference nodes, but retains the already written occlusion rewrite information as part of the gap record's historical processing.

[0080] Specifically, when the system detects that a new written record has been formed in the target ledger field, it determines whether the written record constitutes a qualified written record that meets the writing requirements corresponding to the gap formation node, based on the field object correspondence, the writing basis correspondence, the written value verification, and the closed record generation. When the written record constitutes a qualified written record, the system updates the gap closure status in the corresponding gap record from unclosed to closed, and writes the written record identifier, closure time, and closure record corresponding to the qualified written record into the gap record.

[0081] In the extended example of this embodiment, if the system subsequently receives a write task for the transfer completion node N1, and writes the device location field into the second database or its equivalent location representation through the write task, while simultaneously generating a closed record that meets the write requirements for the transfer completion node N1, then the system determines that the actual write record corresponding to the write task constitutes a qualified actual write. The system updates the gap closure status of the gap record G1 to closed, and retains the masking rewrite information corresponding to the maintenance transfer node N2 or return completion node N3 already written in the gap record G1 as a historical masking process.

[0082] In some implementations, when multiple unclosed write gaps correspond to the same target ledger field, the system establishes separate gap records, determines whether the rewriting of the field rewriting node can close each unclosed write gap, and determines the corresponding equipment ledger difference node. Specifically, the system reads the unclosed write gap status information corresponding to multiple gap forming nodes for the same target ledger field, and establishes gap records respectively with the corresponding gap forming node identifier, target ledger field identifier, and write requirement identifier. The gap records are not merged because the target ledger field is the same; instead, rewriting closure judgment is performed separately based on their respective gap forming node identifier and write requirement identifier. The closure result of one gap record does not change the judgment result of other gap records. Each gap record determines whether to output a new equipment ledger difference node based on its own gap closure status and occlusion rewriting information.

[0083] In the extended example of this embodiment, if there is another gap-forming node N0 in the same equipment location field, and gap-forming node N0 and transfer completion node N1 form different unclosed write gaps, then the system establishes gap record G0 corresponding to N0 and gap record G1 corresponding to N1 respectively. After maintenance transfer node N2 rewrites the equipment location field to maintenance area, the system determines whether the rewrite can close the unclosed write gap corresponding to G0 and the unclosed write gap corresponding to G1 respectively; for gap records whose determination result is that they cannot be closed, the system determines the gap-forming node corresponding to the gap record as the equipment ledger difference node; for gap records whose gap closure status has been updated to closed, the system stops using the occlusion rewrite information in the gap record as the basis for capturing new equipment ledger difference nodes.

[0084] Through the above extended processing, the system can maintain the correspondence between the preceding write gap, the subsequent occlusion rewrite, and the gap closure status around the gap record when there are continuous subsequent rewrites, subsequent supplementary write closures, and multiple preceding unclosed write gaps in the same target ledger field, so that the capture results of the equipment ledger difference node correspond to each preceding gap respectively.

[0085] The above embodiments can be implemented by software, hardware, firmware, or a combination thereof. When implemented in software, the program instructions for implementing the above steps can be stored in a computer-readable storage medium and read and executed by a processor to complete the corresponding processing procedures in the embodiments of the present invention.

[0086] Those skilled in the art can make conventional adjustments to the implementation of data reading, rule configuration, status recording, and result output based on the actual deployment method of the equipment asset management system. As long as they do not deviate from the technical concept of capturing equipment ledger difference nodes around gap formation nodes, field rewriting nodes, and gap records, they should all fall within the protection scope of this invention.

Claims

1. A method for capturing discrepancies in equipment ledgers that integrates business flow characteristics, characterized in that, include: S101, Based on the ledger records and business transaction records of the target device, determine the target ledger fields where there are differences in business transaction write verification; Identify the gap formation node that generates the writing requirement for the target ledger field from the business transaction records, and identify the field rewriting node that rewrites the target ledger field after the writing requirement is formed and enters the subsequent closure judgment. S102, if the corresponding business fact has been completed at the gap formation node, should be written to the target ledger field, and the corresponding write value can be determined, if the target ledger field does not form a qualified actual write that can close the write requirement within the allowed write delay, then it is determined that the gap formation node has formed an unclosed write gap. S103, determine the basis for writing the field to the node corresponding to the field modification; When a field rewriting node rewrites a target ledger field based on its own writing basis, and the rewriting changes the current display value of the target ledger field and makes the current display value conform to its own writing basis, it is determined whether the rewriting can close the unclosed writing gap; wherein, the writing basis is formed by the business facts completed by the field rewriting node itself, and is not derived, supplemented or retried from the write requirements of the gap forming node. S104, when the rewrite cannot close the unclosed write gap, the write basis, rewrite result and current display value change of the field rewrite node are written to the gap record corresponding to the gap forming node, and the gap forming node is determined as the equipment ledger difference node of the target equipment; when the unclosed write gap is closed by qualified actual writing, the attribution retention corresponding to the gap forming node is released.

2. The method for capturing equipment ledger discrepancy nodes based on integrated business flow characteristics according to claim 1, characterized in that, Identifying gap-forming nodes that generate write requirements for target ledger fields from business transaction records includes: screening candidate business nodes from business transaction records; when a candidate business node has already formed a corresponding business fact completion record, there is a field write relationship between the candidate business node and the target ledger field, and a write value can be generated according to the field mapping rules corresponding to the business fact completion record and the target ledger field, a write requirement is generated, and the candidate business node is identified as a gap-forming node; wherein, the write requirement includes a gap-forming node identifier, a target ledger field identifier, a write value, and a write requirement formation time, and the allowed write delay is determined according to the field delay parameter corresponding to the target ledger field, the node delay parameter corresponding to the candidate business node, or the ledger update cycle parameter corresponding to the target device.

3. The method for capturing equipment ledger discrepancy nodes based on the integrated business flow characteristics according to claim 1 or 2, characterized in that, A qualified actual record is an actual record generated that satisfies the requirements of field object correspondence, writing basis correspondence, written value verification, and record closure; field object correspondence means that the fields written in the actual record are consistent with the target ledger fields; writing basis correspondence means that the writing basis of the actual record corresponds to the writing requirements of the gap forming node, or corresponds to the supplementary writing task or retry task generated by the writing requirements; The write value verification is that the actual write value in the actual write record is consistent with the write value, or meets the equivalence verification rules corresponding to the target ledger field; the closed record generation is to generate a closed record corresponding to the write requirement in the actual write record. This closed record is used to update the corresponding gap closure status after an unclosed write gap is formed.

4. The method for capturing equipment ledger discrepancy nodes based on integrated business flow characteristics according to claim 1, characterized in that, Determining the basis for writing a field rewriting node includes: when a field rewriting node has already formed its own business fact completion record, the writing source of the field rewriting node points to the field rewriting node, and the rewritten value is generated by the field rewriting node's own business fact completion record, the field rewriting node is determined to have its own writing basis; when the writing source, writing task, and writing value generation process of the field rewriting node do not reference the write requirements, supplementary writing tasks, retry tasks, or derived task association identifiers of the gap forming node, the self-writing basis is determined not to be derived, supplemented, or retried from the write requirements of the gap forming node.

5. The method for capturing equipment ledger discrepancy nodes based on integrated business flow characteristics according to claim 4, characterized in that, Determining whether the rewrite can close the unclosed write gap includes: determining whether the rewrite of the field rewrite node satisfies source closure, value closure, and record closure; source closure is the write requirement, rewrite task, or retry task of the gap formation node corresponding to the write source of the field rewrite node; value closure is that the rewritten value of the field rewrite node is consistent with the write value corresponding to the unclosed write gap, or satisfies the equivalence verification rule corresponding to the target ledger field; record closure is that the rewrite of the field rewrite node generates a closed record that matches the write requirement identifier corresponding to the unclosed write gap; when at least one of source closure, value closure, and record closure is not met, it is determined that the rewrite of the field rewrite node cannot close the unclosed write gap.

6. The method for capturing equipment ledger discrepancy nodes based on the integrated business flow characteristics according to claim 5, characterized in that, Determining whether a field rewriting node alters the current displayed value of a target ledger field and makes the current displayed value conform to its own writing basis includes: when the rewritten field of a field rewriting node corresponds to a target ledger field, and the field value before rewriting is different from the field value after rewriting, determining that the field rewriting node changes the field value of the target ledger field; when the current displayed value of the target ledger field is consistent with the rewritten field value of the field rewriting node, and the current displayed value originates from the rewritten record of the field rewriting node, determining that the rewritten field value of the field rewriting node occupies the current displayed value of the target ledger field; when the current displayed value meets the self-basis compliance condition, and the unclosed write gap is still not closed, determining that the rewriting of the field rewriting node is a masking rewriting for the unclosed write gap; wherein, the self-basis compliance condition is that the current displayed value is consistent with the rewritten value generated by the field rewriting node based on its own writing basis, or the current displayed value meets the equivalence verification rule corresponding to the target ledger field.

7. The method for capturing equipment ledger discrepancy nodes based on integrated business flow characteristics according to claim 6, characterized in that, The write basis, write result, and current display value change of the field rewriting node are written to the gap record corresponding to the gap forming node. This includes: establishing a gap record with the gap forming node identifier, target ledger field identifier, and write requirement identifier as the main index; writing the write requirement, write value, write requirement formation time, allowable write delay, and gap closure status corresponding to the gap forming node into the gap record; when the rewriting of the field rewriting node is determined to be a masking rewriting for an unclosed write gap, the field rewriting node identifier, the write basis of the field rewriting node, the field value before rewriting, the field value after rewriting, the current display value change, and the non-closure judgment result are written to the gap record; when the gap closure status in the gap record is unclosed, and there is masking rewriting information in the gap record, the gap record is used as the capture basis for determining that the gap forming node is the equipment ledger difference node of the target device.

8. The method for capturing equipment ledger discrepancy nodes based on the integrated business flow characteristics according to claim 7, characterized in that, When multiple field rewrite nodes corresponding to the same unclosed write gap are masked and rewritten, the masked and rewritten information corresponding to the multiple field rewrite nodes is appended to the same gap record according to the rewrite time order of each field rewrite node.

9. The method for capturing equipment ledger discrepancy nodes based on integrated business flow characteristics according to claim 7, characterized in that, When an unclosed write gap is closed by a qualified write, the attribution retention corresponding to the gap formation node is released, including: updating the gap closure status in the gap record to closed, and writing the closure record corresponding to the qualified write to the gap record; after the gap closure status is updated to closed, the occlusion rewrite information in the gap record is stopped as the basis for capturing new equipment ledger difference nodes.

10. The method for capturing equipment ledger discrepancy nodes based on the integrated business flow characteristics according to claim 7, characterized in that, When the same target ledger field corresponds to multiple unclosed write gaps, gap records are established with the gap formation node identifier, target ledger field identifier, and write requirement identifier corresponding to each unclosed write gap; for the rewriting of the same field rewriting node, it is determined whether the rewriting can close each unclosed write gap. When the rewrite cannot close at least one of the unclosed write gaps, and the rewrite is determined to be a masking rewrite for the unclosed write gap, the masking rewrite information of the field rewrite node is written to the corresponding gap record; when any gap record satisfies the gap closure status as unclosed and has masking rewrite information, the gap forming node corresponding to the gap record is determined as the equipment ledger difference node of the target device.

Images