System data transmission verification method, device, equipment and medium

Abstract

The invention discloses a system data transmission verification method, device, equipment and medium, and the method comprises the steps: under the condition that data transmission occurs between at least two business systems, according to a business scene corresponding to a data transmission process between the at least two business systems, verifying the data transmission process between the at least two business systems; determining a target verification mechanism corresponding to the data transmission process from the plurality of verification mechanisms to be selected; verifying the interaction data information corresponding to the data transmission process according to the target verification mechanism to obtain an inter-system verification result; and under the condition that the cost accounting system in the at least two service systems receives the interactive data information, verifying the data logic relationship of each module in the cost accounting system in the process of processing the corresponding interactive data information, and obtaining a verification result in the system. Therefore, the abnormal condition of data transmission can be quickly found through multiple verification mechanisms, and the cost accounting accuracy is improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of information processing, and in particular to a system data transmission verification method and device, equipment and a medium. BACKGROUND

[0002] Production and sales integration is an important mode for modern enterprises to realize efficient resource allocation and business process collaboration, and data is transmitted between multiple business systems to support enterprise operation decision-making.

[0003] However, due to the complexity of data interaction between systems, abnormal situations such as data loss cannot be found in time during cross-system transmission, resulting in a decrease in the accuracy of cost accounting. Therefore, how to find abnormal situations in the data transmission process in time is a technical problem that needs to be solved at present. SUMMARY

[0004] The embodiments of the present application provide a system data transmission verification method, device, equipment and medium, which solve the technical problem that abnormal situations in data transmission cannot be found in time in the prior art, and achieve the technical effect of finding abnormal situations in data transmission in time.

[0005] In a first aspect, the present application provides a system data transmission verification method, comprising:

[0006] In the case of data transmission between at least two business systems, a target verification mechanism corresponding to the data transmission process is determined from a plurality of candidate verification mechanisms according to the business scenario corresponding to the data transmission process between the at least two business systems;

[0007] According to the target verification mechanism, the interaction data information corresponding to the data transmission process is verified to obtain an inter-system verification result, which is used to indicate whether an abnormality occurs in the inter-system data transmission process;

[0008] In the case that the cost accounting system in the at least two business systems receives the interaction data information, the data logic relationship in the process of processing the corresponding interaction data information by each module in the cost accounting system is verified to obtain an intra-system verification result, which is used to indicate whether an abnormality occurs in the data processing process in the cost accounting system.

[0009] In some embodiments of the present application, based on the foregoing scheme, before determining the target verification mechanism corresponding to the data transmission process from the plurality of candidate verification mechanisms according to the business scenario corresponding to the data transmission process between the at least two business systems, the method further comprises:

[0010] determining whether the number of interaction data information exceeds a preset information quantity to obtain a first determination result;

[0011] determine whether the number of the accompanying fields of each piece of interaction data information exceeds the preset number of fields, to obtain a second determination result;

[0012] determine whether the data transmission occurs between two business systems, to obtain a third determination result;

[0013] determine the business scenario according to the first determination result, the second determination result and the third determination result.

[0014] In some embodiments of the present application, based on the foregoing scheme, in the business scenario where the number of interaction data information exceeds the preset number of information and the number of accompanying fields of each piece of interaction data information exceeds the preset number of fields, the interaction data information corresponding to the data transmission process is verified according to a target verification mechanism, including:

[0015] verify whether the number of sending data information of the sending business system matches the number of receiving data information of the receiving business system; the sending business system is a business system that sends data in the at least two business systems, and the receiving business system is a business system that receives data in the at least two business systems;

[0016] verify whether the inventory data in the sending business system matches the inventory data in the receiving business system;

[0017] select target interaction data information from the interaction data information, and verify whether the accompanying fields of the target interaction data information sent by the sending business system match the accompanying fields of the target interaction data information received by the receiving business system.

[0018] In some embodiments of the present application, based on the foregoing scheme, in the business scenario where the number of interaction data information does not exceed the preset number of information, the number of accompanying fields of each piece of interaction data information does not exceed the preset number of fields, and the data transmission occurs between two business systems, the interaction data information corresponding to the data transmission process is verified according to a target verification mechanism, including:

[0019] verify whether the number of sending data information of the sending business system matches the number of receiving data information of the receiving business system; the sending business system is a business system that sends data in the at least two business systems, and the receiving business system is a business system that receives data in the at least two business systems;

[0020] classify the interaction data information according to business categories, determine the category information that needs to be verified in the interaction data information of each category of business categories, and verify the category information according to the preset verification manner corresponding to each category of business categories.

[0021] In some embodiments of this application, based on the aforementioned scheme, in business scenarios where the number of interactive data messages does not exceed a preset number of messages, the number of attached fields in each interactive data message does not exceed a preset number of fields, and data transmission occurs between at least three business systems, the interactive data messages corresponding to the data transmission process are verified according to a target verification mechanism, including:

[0022] The interactive data information is classified according to business categories, and the categories of interactive data information that need to be verified in each business category are determined.

[0023] The category information is verified based on the transmission relationship of interactive data information between business systems.

[0024] In some embodiments of this application, based on the foregoing scheme, the method further includes:

[0025] When code and data conversion occurs in the interactive data information, the interface tables of the various business systems connected to the verification and cost accounting system reflect the data logic relationships of the interactive data information.

[0026] In some embodiments of this application, based on the foregoing scheme, the data logic relationships of each module within the cost accounting system are verified during the processing of corresponding interactive data information, including:

[0027] Verify the data logic relationships in the process of processing corresponding interactive data information in the product module, raw material module, energy module, in-plant logistics module, and deferred cost module within the cost accounting system;

[0028] After the product module, raw material module, energy module, in-plant logistics module and deferred payment module are verified, the data logic relationship in the process of processing and storing data in the cost accounting system is verified through the accounting module in the cost accounting system. The stored data is a collection of interactive data information within a preset time period.

[0029] Secondly, this application also provides a system data transmission verification device, the device comprising:

[0030] The target verification mechanism determination module is used to determine the target verification mechanism corresponding to the data transfer process from multiple candidate verification mechanisms, based on the business scenario corresponding to the data transfer process between at least two business systems, when data transfer occurs between at least two business systems.

[0031] The inter-system verification module is used to verify the interactive data information corresponding to the data transmission process according to the target verification mechanism, and obtain the inter-system verification result. The inter-system verification result is used to indicate whether an anomaly has occurred during the inter-system data transmission process.

[0032] The system kernel verification module is used to verify the data logic relationship of each module in the cost accounting system during the processing of the corresponding interactive data information when the cost accounting system receives interactive data information from at least two business systems, and to obtain the system kernel verification result. The system kernel verification result is used to indicate whether any abnormality has occurred during the data processing in the cost accounting system.

[0033] Thirdly, this application also provides an electronic device, including:

[0034] processor;

[0035] Memory used to store processor-executable instructions;

[0036] The processor is configured to execute a system data transfer verification method as provided in the first aspect.

[0037] Fourthly, this application also provides a non-transitory computer-readable storage medium, which, when the instructions in the storage medium are executed by the processor of an electronic device, enables the electronic device to execute a system data transfer verification method as provided in the first aspect.

[0038] One or more technical solutions provided in the embodiments of this application have at least the following technical effects or advantages:

[0039] This application provides a system data transmission verification method, comprising: when data transmission occurs between at least two business systems, determining a target verification mechanism corresponding to the data transmission process from multiple candidate verification mechanisms based on the business scenario corresponding to the data transmission process between the at least two business systems; verifying the interactive data information corresponding to the data transmission process according to the target verification mechanism to obtain an inter-system verification result, which is used to indicate whether an anomaly occurred during the inter-system data transmission process; and when the cost accounting system in at least two business systems receives the interactive data information, verifying the data logic relationship of each module in the cost accounting system during the processing of the corresponding interactive data information to obtain an internal verification result, which is used to indicate whether an anomaly occurred during the data processing within the cost accounting system. It is evident that this application, by using a verification mechanism adapted to the business scenario to verify the interactive data information between systems, significantly improves verification efficiency, can quickly detect abnormal data, avoids the lag of traditional manual verification, and effectively shortens the problem handling cycle. At the same time, the cost accounting system is used to calculate data within the system. While ensuring data consistency across systems, it further strengthens the internal data logic self-consistency and improves the accuracy of cost accounting. Attached Figure Description

[0040] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0041] Figure 1 A flowchart illustrating a system data transmission verification method provided in an embodiment of this application;

[0042] Figure 2 This application provides a schematic diagram of a system data transmission process.

[0043] Figure 3 A schematic diagram of the structure of a system data transmission verification device provided in an embodiment of this application;

[0044] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0045] This application provides a system data transmission verification method, which solves the technical problem in the prior art that it is impossible to detect abnormal situations in data transmission in a timely manner.

[0046] The technical solution of this application embodiment is to solve the above-mentioned technical problems, and the general idea is as follows:

[0047] This application provides a system data transmission verification method, comprising: when data transmission occurs between at least two business systems, determining a target verification mechanism corresponding to the data transmission process from multiple candidate verification mechanisms based on the business scenario corresponding to the data transmission process between the at least two business systems; verifying the interactive data information corresponding to the data transmission process according to the target verification mechanism to obtain an inter-system verification result, which is used to indicate whether an anomaly occurred during the inter-system data transmission process; and when the cost accounting system in at least two business systems receives the interactive data information, verifying the data logic relationship of each module in the cost accounting system during the processing of the corresponding interactive data information to obtain an internal verification result, which is used to indicate whether an anomaly occurred during the data processing within the cost accounting system. It is evident that this application, by using a verification mechanism adapted to the business scenario to verify the interactive data information between systems, significantly improves verification efficiency, can quickly detect abnormal data, avoids the lag of traditional manual verification, and effectively shortens the problem handling cycle. At the same time, the cost accounting system is used to calculate data within the system. While ensuring data consistency across systems, it further strengthens the internal data logic self-consistency and improves the accuracy of cost accounting.

[0048] To better understand the above technical solutions, the following will provide a detailed explanation of the technical solutions in conjunction with the accompanying drawings and specific implementation methods.

[0049] First, it should be clarified that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0050] Integrated production and sales, as a crucial model for modern enterprises to achieve efficient resource allocation and business process collaboration, involves the deep integration of multiple core business systems, including procurement supply chain systems, manufacturing management systems, in-plant logistics systems, energy management systems, sales logistics systems, sales management systems, cost accounting systems, financial management systems, various production execution systems, equipment systems, and engineering project systems. These systems cover the entire value chain from raw material procurement, production and manufacturing, warehousing and logistics to sales and services, and the real-time interaction and accurate transmission of their data are the core foundation supporting enterprise operational decisions.

[0051] However, due to the independent functions of each system, inconsistent data standards, and complex interaction scenarios, data transfer between systems is prone to problems such as format misalignment, logical contradictions, or information loss, directly affecting the accuracy of cost accounting and the reliability of financial statements. For example, if production data between the manufacturing management system and the cost accounting system fails to synchronize in real time or is converted incorrectly, it will lead to deviations in cost allocation; data gaps between the sales and logistics system and the financial management system may cause delays or errors in accounting reconciliation.

[0052] To address the aforementioned problems, embodiments of this application provide a system data transmission verification method. For example... Figure 1 The diagram shown is a flowchart of a system data transmission verification method provided in an embodiment of this application, including steps S1-S3.

[0053] Step S1: In the case of data transfer between at least two business systems, determine the target verification mechanism corresponding to the data transfer process from multiple candidate verification mechanisms based on the business scenario corresponding to the data transfer process between at least two business systems.

[0054] Step S2: Verify the interactive data information corresponding to the data transmission process according to the target verification mechanism to obtain the inter-system verification result. The inter-system verification result is used to indicate whether an abnormality has occurred during the inter-system data transmission process.

[0055] Step S3: When the cost accounting system in at least two business systems receives interactive data information, verify the data logic relationship of each module in the cost accounting system during the process of processing the corresponding interactive data information, and obtain the system verification result. The system verification result is used to indicate whether any abnormality has occurred during the data processing in the cost accounting system.

[0056] Regarding step S1, when data transfer occurs between at least two business systems, the target verification mechanism corresponding to the data transfer process is determined from multiple candidate verification mechanisms based on the business scenario corresponding to the data transfer process between the at least two business systems.

[0057] A business system refers to an enterprise's internal information systems responsible for different business functions. Each business system focuses on processing specific business areas and needs to share data with other business systems (e.g., the procurement system needs to transmit procurement amounts to the finance system). Examples of business systems include: procurement supply chain systems, manufacturing management systems, in-plant logistics systems, energy management systems, sales logistics systems, sales management systems, cost accounting systems, financial management systems, equipment systems, and engineering project systems.

[0058] Business scenarios refer to the specific context of data transfer between systems, including: the number of data entries transferred, the number of fields, and the transfer relationships. The number of data entries transferred can be high-frequency (e.g., thousands per hour) or low-frequency (e.g., hundreds per day). The number of fields can be complex (e.g., 30 fields per entry) or simple (e.g., 5 fields per entry). Transfer relationships can be unidirectional (e.g., A→B) or bidirectional (e.g., ...). ) and multiple systems (such as A→C and A→B→C).

[0059] Before determining the target verification mechanism for data transmission from multiple candidate verification mechanisms based on the business scenario of data transmission, the method also includes steps S11-S14.

[0060] Step S11: Determine whether the amount of interactive data information exceeds the preset amount of information, and obtain the first determination result;

[0061] Step S12: Determine whether the number of attached fields for each piece of interactive data exceeds the preset number of fields, and obtain the second determination result;

[0062] Step S13: Determine whether data transmission occurs between two business systems to obtain the third determination result;

[0063] Step S14: Determine the business scenario based on the first judgment result, the second judgment result, and the third judgment result.

[0064] Regarding steps S11-S13, the preset information quantity refers to the system's pre-set threshold for the number of data entries (e.g., 100,000 entries per month), used to distinguish between high-frequency and low-frequency data transmission scenarios. The preset field quantity refers to the system's pre-set threshold for the number of fields per data entry (e.g., 30 fields per entry), used to distinguish between complex and simple data structures.

[0065] The first judgment result includes: the number of interactive data messages exceeds the preset number of messages, and the number of interactive data messages does not exceed the preset number of messages. The second judgment result includes: the number of attached fields in each interactive data message exceeds the preset number of fields, and the number of attached fields in each interactive data message does not exceed the preset number of fields. The third judgment result includes: data transmission occurs between two business systems, and data transmission occurs between at least three business systems.

[0066] Regarding step S14, the business scenario is determined based on the first judgment result, the second judgment result, and the third judgment result.

[0067] Specifically, the candidate verification mechanisms include a first verification mechanism, a second verification mechanism, and a third verification mechanism.

[0068] In business scenarios where the amount of interactive data exceeds a preset limit and the number of fields attached to each piece of interactive data exceeds a preset limit, the first candidate verification mechanism will be selected as the target verification mechanism. For example, the amount of interactive data exceeds 100,000 pieces per month, and each piece of interactive data has more than 30 fields attached.

[0069] In business scenarios where the number of interactive data messages does not exceed the preset number of messages, the number of accompanying fields in each interactive data message does not exceed the preset number of fields, and the data transmission occurs between two business systems, the second candidate verification mechanism will be selected as the target verification mechanism. For example, if the number of interactive data messages is less than 100,000 per month, and the number of accompanying fields in each interactive data message is less than 30, and the transaction only involves the sending and receiving of information between two business systems.

[0070] In business scenarios where the number of interactive data messages does not exceed a preset number, the number of accompanying fields for each interactive data message does not exceed a preset number of fields, and data transmission occurs between at least three business systems, the third alternative verification mechanism will be selected as the target verification mechanism. For example, this applies to scenarios where the number of interactive data messages is less than 100,000 per month, each interactive data message has fewer than 30 accompanying fields, and some systems receive information from multiple systems and aggregate it according to the dimensions required by the business.

[0071] Regarding step S2, the interactive data information corresponding to the data transmission process is verified according to the target verification mechanism to obtain the inter-system verification result. The inter-system verification result is used to indicate whether an anomaly has occurred during the inter-system data transmission process.

[0072] The verification steps are explained below when the target verification mechanisms are the first candidate verification mechanism, the second candidate verification mechanism, and the third candidate verification mechanism.

[0073] If the first candidate verification mechanism is determined as the target verification mechanism, the process includes steps S211-S213.

[0074] Step S211: Verify whether the number of data messages sent by the sending service system matches the number of data messages received by the receiving service system; the sending service system is a service system that sends data from at least two service systems, and the receiving service system is a service system that receives data from at least two service systems.

[0075] Step S212: Verify whether the inventory data in the sending business system matches the inventory data in the receiving business system;

[0076] Step S213: Select target interactive data information from the interactive data information, and verify whether the attached fields of the target interactive data information sent by the sending business system match the attached fields of the target interactive data information received by the receiving business system.

[0077] For example, a manufacturing management system and a cost accounting system will be used as examples for illustration (e.g.) Figure 2 The data transfer relationship is shown by the arrow within the blue dashed box. The manufacturing management system and the cost accounting system can transfer data to each other. The following explanation only assumes that the manufacturing management system is the sending business system and the cost accounting system is the receiving business system.

[0078] Regarding step S211, obtain the total number of data entries uploaded by the manufacturing management system within a preset time period (e.g., one hour) and the total number of data entries received by the cost accounting system within the same preset time period. If the two numbers match (e.g., the total number of data entries uploaded is 1000 and the total number of data entries received is 1000), continue with subsequent verification steps. If they do not match (e.g., the total number of data entries uploaded is 1000 and the total number of data entries received is 990), send a verification mismatch signal to the mobile terminal.

[0079] Regarding step S212, the manufacturing management system and the cost accounting system each calculate their respective inventory data. Inventory calculation can be performed daily. The cost accounting system sends the daily inventory data to the manufacturing management system, which then verifies the inventory data for matching using the inventory verification module. If a mismatch is found, a verification mismatch signal is sent to the mobile terminal.

[0080] Regarding step S213, for example, for each piece of interactive data uploaded by the manufacturing management system, select it as the target interactive data for verification. For the target interactive data, verify whether the attached fields (such as product number, production quantity, production line code) sent by the manufacturing management system match the attached fields received by the cost accounting system (such as the field content, format, and type being the same).

[0081] If the second candidate verification mechanism is selected as the target verification mechanism, the process includes steps S221-S222.

[0082] Step S221: Verify whether the number of data messages sent by the sending service system matches the number of data messages received by the receiving service system; the sending service system is a service system that sends data in at least two service systems, and the receiving service system is a service system that receives data in at least two service systems.

[0083] Step S222: Classify the interactive data information according to business categories, determine the category information that needs to be verified in the interactive data information of each business category, and verify the category information according to the preset verification method corresponding to each business category.

[0084] For example, a cost accounting system and a financial management system will be used as examples for illustration (e.g., Figure 2 The data transfer relationship is shown by the arrow within the red dashed box. The cost accounting system and the financial management system can transfer data to each other, including two scenarios: one where the cost accounting system acts as the sending system and the financial management system acts as the receiving system; and the other where the financial management system acts as the sending system and the cost accounting system acts as the receiving system.

[0085] Regarding step S221, verification is performed when the cost accounting system acts as the sending business system and the financial management system acts as the receiving business system, and when the financial management system acts as the sending business system and the cost accounting system acts as the receiving business system. The verification process can be found in the above explanation regarding step S211.

[0086] Step S222: In the cost accounting system and financial management system, the interactive data information can be divided into at least the following three categories according to business type:

[0087] Procurement settlement data: Settlement information related to material procurement (such as material code, quantity, and amount).

[0088] Accounting data: Accounting information involving costs and finance (such as product code, quantity issued, amount).

[0089] Cost data: Details involving cost allocation (such as cost center code, account code, and amount).

[0090] For procurement settlement data, the categories of information that need to be verified include: material code (or product code), cost receipt quantity, cost receipt amount, financial accounting quantity, and financial accounting amount. Verification of these categories of information, based on the preset verification methods corresponding to the procurement settlement data, includes: verifying whether the material codes are consistent, and verifying whether the cost quantity and amount match those in the financial records.

[0091] For accounting data, the categories of information that need to be verified include: material code (or product code), cost issuance quantity, cost issuance amount, financial accounting quantity, and financial accounting amount. Verification of these categories of information, based on the preset verification methods corresponding to the accounting data, includes: verifying whether the material codes are consistent and whether the cost issuance amount matches the financial accounting amount.

[0092] For expense data, the categories of information that need to be verified include: cost center code, account code, cost issuance amount, and financial receipt amount. Verification of this category information is performed according to the preset verification method corresponding to the expense data, including: whether the cost center code and account code match, and whether the cost issuance amount and financial receipt amount are consistent.

[0093] When the third candidate verification mechanism is selected as the target verification mechanism, steps S231-S232 are included.

[0094] Step S231: Classify the interactive data information according to business categories, and determine the category information that needs to be verified in the interactive data information of each business category;

[0095] Step S232: Verify the category information according to the transmission relationship of interactive data information between business systems.

[0096] For example, cost accounting systems, sales logistics systems, and manufacturing management systems will be used as examples for illustration (e.g., Figure 2 The data transfer relationship is shown by the arrow pointing to the green dashed box.

[0097] Regarding step S231, in the cost accounting system, sales logistics system, and manufacturing management system, the interactive data information can be divided into two business categories according to product weight type: "Theoretical weight + weight difference" and "Actual weight". The categories of information requiring verification for "Theoretical weight + weight difference" include: material number, product code, theoretical weight (theoretical weight), weight difference value, and allowable shipment quantity. The categories of information requiring verification for "Actual weight" include: material number, product code, actual weight (actual weight), and allowable shipment quantity.

[0098] Regarding step S232, in the "Theoretical Weight + Weighing Difference" business category, the manufacturing management system simultaneously sends product theoretical weight information (interactive data information) to both the cost accounting system and the sales logistics system. The cost accounting system receives the product theoretical weight information, converts it into a product code, and then sends it to the sales logistics system. When the product is weighed before leaving the factory and the weighing difference information is obtained, it is sent back to the cost accounting system through the sales logistics system. Finally, the cost accounting system and the sales logistics system sum the theoretical weight and the weighing difference, respectively, and verify the material number, product code, the approved issuance quantity in the cost accounting system, and the approved issuance quantity in the sales logistics system daily.

[0099] In the "Actual Weight" business category, the manufacturing management system simultaneously sends product actual weight information (interactive data information) to both the cost accounting system and the sales logistics system. The cost accounting system receives the product actual weight information, converts it into a product code, and then sends it to the sales logistics system. The cost accounting system and the sales logistics system can directly verify the material number, product code, actual weight, and approved shipment quantity daily.

[0100] Regarding step S3, when the cost accounting system in at least two business systems receives interactive data information, the data logic relationship of each module within the cost accounting system is verified during the processing of the corresponding interactive data information. A system-level verification result is obtained, which indicates whether any anomalies have occurred during data processing within the cost accounting system. This includes steps S31-S32.

[0101] Step S31: Verify the data logic relationships in the process of processing the corresponding interactive data information by the product module, raw material module, energy module, in-plant logistics module, and deferred cost module within the cost accounting system;

[0102] Step S32: After the verification of the product module, raw material module, energy module, in-plant logistics module and deferred payment module is completed, the data logic relationship in the process of processing and storing data in the cost accounting system is verified through the accounting module in the cost accounting system. The stored data is a collection of interactive data information within a preset time period.

[0103] The verification process within the cost accounting system needs to be executed in modules and sequentially. First, the product module is verified (during which the energy module, in-plant logistics module, and deferred cost module can be verified simultaneously). Next, the raw materials and fuels module is verified. After the verification of the product, raw materials and fuels, energy, in-plant logistics, and deferred cost modules is completed, the data logic relationships of the data stored within the cost accounting system (within preset time periods such as 1 hour or 1 day) are verified through the accounting module within the cost accounting system to improve the accuracy of cost accounting.

[0104] Furthermore, due to the different frequencies of data exchange between various business systems (such as "triggered when the front-end system has new business data", "hourly", and "daily"), the cost accounting system can execute the accounting step S3 multiple times a day.

[0105] For example, the data logic relationship verification steps corresponding to each module in the cost accounting system are shown in Table 1.

[0106] Table 1 Verification Form for Modules within the Cost Accounting System

[0107]

[0108]

[0109] Furthermore, the method also includes the following steps before performing step S3:

[0110] When code and data conversion occurs in the interactive data information, the interface tables of the various business systems connected to the verification and cost accounting system reflect the data logic relationships of the interactive data information.

[0111] Specifically, in cross-system data transfer, different systems may use their own encoding rules (such as product names, cost center codes, etc.). To ensure data consistency in the cost accounting system, code conversion is required and the logical relationships after conversion must be verified.

[0112] It should be noted that after verifying the data logic relationship between the interface tables of the various business systems connected to the cost accounting system and the interactive data information, the accounting steps of each module within the cost accounting system are then executed.

[0113] The interface table serves as an "intermediate bridge" for data transfer between systems. The interface tables of the various business systems connected to the verification and cost accounting system handle the logical relationships of the interactive data information, including: whether the relationship between input product codes and output product codes is correct; whether the relationship between input product codes and cost center codes is correct; whether the relationship between output product codes and cost center codes is correct; whether the relationship between product codes and accounting objects is correct; whether the relationship between product categories and unit codes is correct; whether the relationship between account sets and unit codes is correct; whether the product disposal rules are correct; and whether there is corresponding product output information for the consumed materials in the current month.

[0114] Furthermore, the method also includes sending the inter-system verification results and the intra-system verification results to the mobile terminal. The mobile terminal is used to provide a human-computer interaction interface so that business personnel can check the data transmission status and promptly detect data transmission anomalies for subsequent processing.

[0115] In summary, this application provides a system data transmission verification method, comprising: when data transmission occurs between at least two business systems, determining a target verification mechanism corresponding to the data transmission process from multiple candidate verification mechanisms based on the business scenario corresponding to the data transmission process between the at least two business systems; verifying the interactive data information corresponding to the data transmission process according to the target verification mechanism to obtain an inter-system verification result, which is used to indicate whether an anomaly occurred during the inter-system data transmission process; and when the cost accounting system in at least two business systems receives the interactive data information, verifying the data logic relationship of each module in the cost accounting system during the processing of the corresponding interactive data information to obtain an internal verification result, which is used to indicate whether an anomaly occurred during the data processing within the cost accounting system. It is evident that this application significantly improves verification efficiency by using a verification mechanism adapted to the business scenario to verify the interactive data information between systems, enabling rapid detection of abnormal data, avoiding the lag of traditional manual verification, and effectively shortening the problem handling cycle. At the same time, the cost accounting system is used to calculate data within the system. While ensuring data consistency across systems, it further strengthens the internal data logic self-consistency and improves the accuracy of cost accounting.

[0116] Based on the same inventive concept, embodiments of this application also provide, as follows: Figure 3 An apparatus is shown, the apparatus comprising:

[0117] The target verification mechanism determination module 31 is used to determine the target verification mechanism corresponding to the data transmission process from multiple candidate verification mechanisms when data transmission occurs between at least two business systems, based on the business scenario corresponding to the data transmission process between at least two business systems.

[0118] The inter-system verification module 32 is used to verify the interactive data information corresponding to the data transmission process according to the target verification mechanism, and obtain the inter-system verification result. The inter-system verification result is used to indicate whether an abnormality has occurred during the inter-system data transmission process.

[0119] The system kernel verification module 33 is used to verify the data logic relationship of each module in the cost accounting system during the process of processing the corresponding interactive data information when the cost accounting system in at least two business systems receives interactive data information, and to obtain the system kernel verification result. The system kernel verification result is used to indicate whether an abnormality has occurred during the data processing in the cost accounting system.

[0120] Furthermore, the device also includes a business scenario determination module, used for:

[0121] Determine whether the amount of interactive data exceeds the preset amount of information, and obtain the first determination result;

[0122] Determine whether the number of attached fields in each piece of interactive data exceeds the preset number of fields to obtain a second judgment result;

[0123] Determine whether data transfer occurs between two business systems to obtain a third judgment result;

[0124] Based on the first, second, and third judgment results, the business scenario is determined.

[0125] Furthermore, the device also includes a first execution module for:

[0126] Verify whether the amount of data sent by the sending business system matches the amount of data received by the receiving business system; the sending business system is a business system that sends data from at least two business systems, and the receiving business system is a business system that receives data from at least two business systems.

[0127] Verify whether the inventory data in the sending business system matches the inventory data in the receiving business system;

[0128] Select the target interactive data information from the interactive data information and verify whether the attached fields of the target interactive data information sent by the sending business system match the attached fields of the target interactive data information received by the receiving business system.

[0129] Furthermore, the device also includes a second execution module for:

[0130] Verify whether the amount of data sent by the sending business system matches the amount of data received by the receiving business system; the sending business system is a business system that sends data from at least two business systems, and the receiving business system is a business system that receives data from at least two business systems.

[0131] The interactive data information is classified according to business categories. The category information that needs to be verified in the interactive data information of each business category is determined, and the category information is verified according to the preset verification method corresponding to each business category.

[0132] Furthermore, the device also includes a third execution module for:

[0133] The interactive data information is classified according to business categories, and the categories of interactive data information that need to be verified in each business category are determined.

[0134] The category information is verified based on the transmission relationship of interactive data information between business systems.

[0135] Furthermore, the device also includes a data logic relationship verification module, used for:

[0136] When code and data conversion occurs in the interactive data information, the interface tables of the various business systems connected to the verification and cost accounting system reflect the data logic relationships of the interactive data information.

[0137] Furthermore, the device also includes an execution module within the cost accounting system, used for:

[0138] Verify the data logic relationships in the process of processing corresponding interactive data information in the product module, raw material module, energy module, in-plant logistics module, and deferred cost module within the cost accounting system;

[0139] After the product module, raw material module, energy module, in-plant logistics module and deferred payment module are verified, the data logic relationship in the process of processing and storing data in the cost accounting system is verified through the accounting module in the cost accounting system. The stored data is a collection of interactive data information within a preset time period.

[0140] Based on the same inventive concept, embodiments of this application also provide, as follows: Figure 4 An electronic device shown includes:

[0141] Processor 41;

[0142] Memory 42 is used to store executable instructions of processor 41;

[0143] The processor 41 is configured to execute a system data transfer verification method as described above.

[0144] Based on the same inventive concept, this application also provides a non-transitory computer-readable storage medium, which, when the instructions in the storage medium are executed by the processor 41 of an electronic device, enables the electronic device to execute a system data transmission verification method as described above.

[0145] Since the electronic device described in this embodiment is an electronic device used to implement the information processing method in the embodiments of this application, those skilled in the art can understand the specific implementation methods and various variations of the electronic device in this embodiment based on the information processing method described in the embodiments of this application. Therefore, how the electronic device implements the method in the embodiments of this application will not be described in detail here. Any electronic device used by those skilled in the art to implement the information processing method in the embodiments of this application falls within the scope of protection of this application.

[0146] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0147] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0148] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0149] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1The steps of the function specified in one or more boxes.

[0150] Although preferred embodiments of the invention have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including both the preferred embodiments and all changes and modifications falling within the scope of the invention.

[0151] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Therefore, if these modifications and variations fall within the scope of the claims of this invention and their equivalents, this invention also intends to include these modifications and variations.

Claims

1. A system data transmission verification method, characterized in that, include: In the case of data transfer between at least two business systems, the target verification mechanism corresponding to the data transfer process is determined from multiple candidate verification mechanisms based on the business scenario corresponding to the data transfer process between the at least two business systems. The interactive data information corresponding to the data transmission process is verified according to the target verification mechanism to obtain the inter-system verification result. The inter-system verification result is used to indicate whether an abnormality has occurred during the inter-system data transmission process. When the cost accounting system in at least two business systems receives the interactive data information, the data logic relationship of each module in the cost accounting system in the process of processing the corresponding interactive data information is verified to obtain the system verification result. The system verification result is used to indicate whether an abnormality has occurred in the data processing process in the cost accounting system.

2. The system data transmission verification method as described in claim 1, characterized in that, Before determining the target verification mechanism corresponding to the data transfer process from multiple candidate verification mechanisms based on the business scenario corresponding to the data transfer process between at least two of the business systems, the method further includes: Determine whether the amount of the interactive data information exceeds a preset amount of information to obtain a first determination result; Determine whether the number of attached fields in each piece of interactive data information exceeds a preset number of fields to obtain a second determination result; Determine whether the data transfer occurs between the two business systems to obtain a third determination result; The business scenario is determined based on the first judgment result, the second judgment result, and the third judgment result.

3. The system data transmission verification method as described in claim 1, characterized in that, In a business scenario where the number of interactive data messages exceeds a preset number of messages and the number of attached fields for each piece of interactive data message exceeds a preset number of fields, the step of verifying the interactive data messages corresponding to the data transmission process according to the target verification mechanism includes: Verify whether the amount of data sent by the sending service system matches the amount of data received by the receiving service system; the sending service system refers to the service system that sends data in at least two service systems, and the receiving service system refers to the service system that receives data in at least two service systems. Verify whether the inventory data in the sending service system matches the inventory data in the receiving service system; Select target interactive data information from the interactive data information, and verify whether the attached fields of the target interactive data information sent by the sending business system match the attached fields of the target interactive data information received by the receiving business system.

4. The system data transmission verification method as described in claim 1, characterized in that, In the business scenario where the number of interactive data messages does not exceed a preset number of messages, the number of attached fields in each interactive data message does not exceed a preset number of fields, and the data transmission occurs between two business systems, the verification of the interactive data messages corresponding to the data transmission process according to the target verification mechanism includes: Verify whether the amount of data sent by the sending service system matches the amount of data received by the receiving service system; the sending service system refers to the service system that sends data in at least two service systems, and the receiving service system refers to the service system that receives data in at least two service systems. The interactive data information is classified according to business categories. The category information that needs to be verified in the interactive data information of each business category is determined, and the category information is verified according to the preset verification method corresponding to each business category.

5. The system data transmission verification method as described in claim 1, characterized in that, In the business scenario where the number of interactive data messages does not exceed a preset number of messages, the number of attached fields in each interactive data message does not exceed a preset number of fields, and the data transmission occurs between at least three business systems, the verification of the interactive data messages corresponding to the data transmission process according to the target verification mechanism includes: The interactive data information is classified according to business categories, and the category information that needs to be verified in the interactive data information of each business category is determined. The category information is verified according to the transmission relationship of the interactive data information between the business systems.

6. The system data transmission verification method as described in claim 1, characterized in that, The method further includes: When the interactive data information undergoes code and data conversion, the interface tables of each of the business systems connected to the cost accounting system are verified to verify the data logic relationship of the interactive data information.

7. The system data transmission verification method as described in claim 1, characterized in that, The verification of the data logic relationships of each module within the cost accounting system during the processing of the corresponding interactive data information includes: Verify the data logic relationships in the process of processing the corresponding interactive data information by the product module, raw material module, energy module, in-plant logistics module, and deferred cost module within the cost accounting system; After the verification of the product module, the raw material module, the energy module, the in-plant logistics module, and the deferred payment module is completed, the data logic relationship in the process of the cost accounting system processing and storing data is verified by the accounting module in the cost accounting system. The stored data is a collection of interactive data information within a preset time period.

8. A system data transmission verification device, characterized in that, The device includes: The target verification mechanism determination module is used to determine the target verification mechanism corresponding to the data transmission process from multiple candidate verification mechanisms, based on the business scenario corresponding to the data transmission process between at least two business systems, when data transmission occurs between at least two business systems. The inter-system verification module is used to verify the interactive data information corresponding to the data transmission process according to the target verification mechanism, and obtain the inter-system verification result. The inter-system verification result is used to indicate whether an abnormality has occurred during the inter-system data transmission process. The system kernel verification module is used to verify the data logic relationship of each module in the cost accounting system during the process of processing the corresponding interactive data information when the cost accounting system in at least two business systems receives the interactive data information, and to obtain the system kernel verification result. The system kernel verification result is used to indicate whether an abnormality has occurred during the data processing in the cost accounting system.

9. An electronic device, characterized in that, include: processor; Memory used to store the processor's executable instructions; The processor is configured to execute a system data transfer verification method as described in any one of claims 1-7.

10. A non-transitory computer-readable storage medium, characterized in that, When the instructions in the storage medium are executed by the processor of the electronic device, the electronic device is able to perform a system data transfer verification method as described in any one of claims 1-7.

Images