A service data processing method and device, electronic equipment and storage medium

Abstract

This invention discloses a business data processing method, apparatus, electronic device, and storage medium. The method includes displaying an editing interface, which includes a component bar area and a work area. In response to a target operation command, standardized components in the component bar area are configured in the work area to determine several data tables, several fields in the data tables, and the continuity relationship between the fields. A target audit code is generated based on the several data tables, the several fields in the data tables, and the continuity relationship between the fields. This target audit code is used to perform continuity auditing on the business data corresponding to the fields to be audited. This invention eliminates the need for manual auditing by auditors, reducing labor costs and improving audit efficiency. Furthermore, this invention reduces the workload of manually writing code, effectively reducing the probability of errors and improving audit quality. It can be widely applied in the field of computer technology.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a business data processing method, apparatus, electronic device, and storage medium. Background Technology

[0002] With the development of information technology, the amount of business data generated by various industries in the process of informatization is becoming increasingly massive. In some areas, it is necessary to conduct continuous audits on special business data in order to reduce potential risks in related businesses and provide assistance for the development decisions of related businesses.

[0003] For example, a crucial field in a financial institution's business data table is a user's account balance. When a user makes a transaction, the account balance in the business data table changes. Generally, each transaction generates a new business data record based on the table's field format. According to continuity constraints, the final balance field value in the old business data record should equal the initial balance field value in the new business data record. This is the relationship between the two business data records. Therefore, the auditor's continuity audit work involves checking whether these two business data records comply with the aforementioned continuity constraints to assess whether the account balance value is incorrect.

[0004] Traditional auditing methods require auditors and business personnel to repeatedly communicate audit requirements to clarify the content of data tables and the meaning of fields for various business data. Then, auditors rely on their experience to conduct continuous audits of some data. This method is labor-intensive and prone to errors. In addition, the accuracy of this type of audit depends on the experience of the auditors, which can easily lead to audit errors and omissions. There is a potential risk of incorrect or missed audits, resulting in low audit efficiency and unreliability. Summary of the Invention

[0005] In view of this, in order to address at least one deficiency of the prior art, embodiments of the present invention provide a business data processing method, apparatus, electronic device, and storage medium to reduce labor costs and error probability, and improve the efficiency and quality of business data continuity auditing.

[0006] One aspect of the present invention provides a business data processing method, the method comprising:

[0007] The editing interface is displayed, which includes a component bar area and a job area. The component bar area includes a variety of standardized components, each of which is used to determine the business data table type, business data table field information, or the continuity relationship between fields in the business data table.

[0008] In response to the target operation command, the standardized components of the component bar area are configured in the work area to determine several data tables, several fields in the data tables, and the continuity relationship of each field in the data tables;

[0009] A target audit code is generated based on several data tables, several fields in the data tables, and the continuity relationship of each field in the data tables. The target audit code is used to perform continuity audit on the business data corresponding to the field to be audited.

[0010] Another aspect of the present invention provides a business data processing apparatus, comprising:

[0011] The first module is used to display the editing interface, which includes a component bar area and a job area. The component bar area includes a variety of standardized components, each of which is used to determine the business data table type, business data table field information, or the continuity relationship between fields in the business data table.

[0012] The second module is used to configure the standardized components of the component bar area in the work area in response to the target operation command, and to determine several data tables, several fields in the data tables, and the continuity relationship of each field in the data tables.

[0013] The third module is used to generate target audit code based on several data tables, several fields in the data tables, and the continuity relationship of each field in the data tables. The target audit code is used to perform continuity audit on the business data corresponding to the field to be audited.

[0014] Another aspect of the present invention provides an electronic device, including a processor and a memory;

[0015] The memory is used to store programs;

[0016] The processor executes the program to implement the method as described above.

[0017] This invention also discloses a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device can read the computer instructions from the computer-readable storage medium and execute the computer instructions, causing the computer device to perform the aforementioned method.

[0018] An embodiment of the present invention first displays an editing interface, which includes a component bar area and a work area. The component bar area includes various standardized components, each of which is used to determine the business data table type, business data table field information, or the continuity relationship between fields in the business data table. Next, in response to a target operation instruction, the standardized components in the component bar area are configured in the work area to determine several data tables, several fields in the data tables, and the continuity relationship between the fields in the data tables. Finally, a process is generated based on the several data tables, the several fields in the data tables, and the continuity relationship between the fields in the data tables. The target audit code is used to perform continuity auditing on the business data corresponding to the auditable field. This invention, through operations on standardized components in a visual editing interface, such as dragging and clicking, can determine the continuity relationship between auditable fields and then automatically generate target audit code to perform continuity auditing on the business data corresponding to the auditable field. The entire process eliminates the need for manual auditing by auditing personnel. The visual interface makes the business logic easy to understand for both business and auditing personnel, reducing labor costs and improving audit efficiency. Furthermore, this invention provides standardized functions for business personnel, reducing the workload of manually writing code, effectively reducing the probability of errors, and improving audit quality. Attached Figure Description

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

[0020] Figure 1 A schematic diagram illustrating the implementation environment of a business data processing method provided in this embodiment;

[0021] Figure 2 This embodiment provides a flowchart of the steps of a business data processing method.

[0022] Figure 3 This is a schematic diagram of the editing interface of the software system in this embodiment;

[0023] Figure 4 This is a schematic diagram illustrating the establishment of continuous relationships between data table fields in the work area according to this embodiment;

[0024] Figure 5 This is a schematic diagram illustrating the operation of creating a transactional data table using the first standardized component in this embodiment.

[0025] Figure 6This is a schematic diagram illustrating the operation of creating or modifying data table fields using the second standardized component in this embodiment;

[0026] Figure 7 This is a schematic diagram illustrating the operation of establishing the continuity relationship of data table fields through the third standardized component in this embodiment;

[0027] Figure 8 This is a schematic diagram illustrating the operation of establishing the continuity relationship of data table fields through connecting lines and a third standardized component in this embodiment;

[0028] Figure 9 This is a flowchart illustrating the steps of selecting candidate fields from the business data table based on continuity constraints in this embodiment.

[0029] Figure 10 This is a schematic diagram illustrating the operation of constructing continuity constraints between data table fields in this embodiment;

[0030] Figure 11 This is a schematic diagram illustrating the operation of associating or merging data tables in this embodiment;

[0031] Figure 12 A flowchart illustrating the steps of another business data processing method provided in this embodiment;

[0032] Figure 13 This is a schematic diagram of the structure of a service data device provided in this embodiment. Detailed Implementation

[0033] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0034] In the field of computer technology, a software system refers to a computer software system composed of system software, support software, and application software, and is an important component of a computer system. To enable human-computer interaction and obtain user operation logic, a software system typically relies on a user interface. The user interface serves as the medium for interaction and information exchange between the system and the user, enabling the conversion of information between its internal computer form and a human-readable format. Visualization is also an essential element in human-computer interaction through the user interface. Visualization technology utilizes computer graphics and image processing techniques to convert data into graphics or images displayed on a screen and facilitate interactive processing. Visualization technology allows users to directly manipulate tangible information within a graphical interface, improving the efficiency of communication with the computer.

[0035] Auditing, as a supervisory mechanism, has evolved alongside advancements in information technology and cross-disciplinary integration. Related technologies include auditing software systems for monitoring economic data, such as verifying the continuity of business transactions. However, due to relatively low levels of informatization in auditing-related fields and excessive coupling between the business and audit sides, auditing using computer software systems can lead to high communication costs in the audit process due to a lack of standardized data between the two sides. Furthermore, audit analysis relies heavily on the individual abilities and understanding of auditors, compromising efficiency and quality, resulting in low development efficiency for dedicated auditing software systems.

[0036] To address this, this invention provides a business data processing method based on a software system's editing interface. Within this interface, the embodiment configures standardized components in the component bar within the work area according to the user's target operation instructions, determining the elements to be audited. These elements may include, but are not limited to, data tables, fields within data tables, and the continuity relationships between fields. Then, the embodiment generates target audit code based on the elements to be audited, performing continuity auditing. It should be noted that the continuity mentioned above refers to the business continuity of transaction data, such as amounts or points, and can also reflect changes in transaction data due to consumption, transactions, and other operations. This invention, through operations on standardized components in the editing interface, such as dragging and clicking, can automatically generate target audit code to perform continuity auditing on the business data within the elements to be audited, eliminating the need for manual auditing by auditors. The editable interface in this embodiment makes the business logic easy for both business and audit personnel to understand, reducing labor costs and improving audit efficiency. Furthermore, the embodiment provides standardized functions to business personnel through standardized functional encapsulated components, reducing the workload of manual coding, simplifying the process, effectively reducing the probability of errors, and improving audit quality.

[0037] Figure 1 This is a structural schematic diagram of an implementation environment provided by the present invention. For example... Figure 1As shown, this implementation environment includes a terminal 101 and a server 102. The terminal 101 is equipped with a business data processing software system capable of auditing the continuity relationships of business data tables. The software system's editing interface is a visual user interface, which divides the operation area, including but not limited to a component bar area and a job area. The component bar area contains several standardized components representing continuity relationships. Responding to a target operation command, the software system configures standardized components in the job area and generates target audit codes based on the continuity relationships represented by the configured standardized components, performing continuity audits on the business data to be audited. In this implementation environment, the terminal 101 can be any electronic product that allows human-computer interaction via one or more methods such as a keyboard, touchpad, touchscreen, remote control, voice interaction, or handwriting device. This electronic product can receive the user's target operation command through its visual operation interface and display the results of the operation command in real time. For example, as... Figure 1 As shown, the terminal 101 can be a personal computer (PC), mobile phone, smartphone 1011, personal digital assistant (PDA), wearable device, handheld computer (PPC), tablet computer, etc.

[0038] In addition, Figure 1 In the illustrated implementation environment, terminal 101 can establish a communication connection with server 102 via a network protocol. Server 102 stores a large amount of business data in its database. This business data can be unaudited data, audited business data, or intermediate business data temporarily stored during the auditing process. Server 102 can push various types of data to terminal 101 according to different retrieval commands sent by terminal 101. Target audit code is stored in server 102 for continuous auditing. In this implementation environment, the server can be a standalone server, a server cluster consisting of several servers, or a cloud computing service center. The form of the server is not limited to the examples described above. It is understood that the server also has data storage capabilities, which can be implemented using a local database or a cloud-based database.

[0039] Taking a specific audit process as an example, in Figure 1In the implementation environment shown, the complete business data processing process is as follows: On the editing interface of terminal 101, i.e., the visual user interface, the business data to be audited is first obtained from server 102 through data acquisition controls or instructions, and then displayed on the editing interface. In this embodiment, the business data to be audited can be displayed visually in the form of a data table. This interface includes at least a component bar area and a work area. The component bar area contains various standardized components, which can be used to determine the business data table type, business data table field information, or the continuity relationship between fields in the business data table. For example, a connection line component can be used to represent the continuity relationship between fields in the table; another example is that a function component can be used to represent the content of the continuity relationship. The embodiment obtains user click, drag, and connect operation instructions on the editing interface, and responds to these instructions by configuring the operation target, i.e., various elements placed in the work area, to determine several data tables, several fields in the data tables, and the continuity relationship between the fields in the data tables. After the configuration is completed, based on the target audit code generated by server 102, the business data in the data table to be audited in the work area of ​​terminal 101 is continuously audited, and the audit results are visualized.

[0040] It should be understood that the embodiments of the present invention are only by way of Figure 1 This example illustrates one possible implementation environment and outcome: a user sends a data retrieval request through terminal 101, and server 102 packages the corresponding data based on the request and sends it back to terminal 101 for visualization. In other application scenarios of this invention, the business data processing method can also be implemented solely by terminal 101 equipped with business data processing software. For example, after terminal 101 disconnects from server 102, the user can perform offline operations based on cached data in the terminal, obtain target audit code using the target audit code generation program built into terminal 101, and perform continuity auditing. After reconnecting to server 102, the business data cached locally on terminal 101 and related continuity relationships are uploaded and updated to server 102 for data storage and updating. This invention does not limit specific application scenarios; the above... Figure 1 The application scenarios described are merely illustrative examples.

[0041] It is understood that the business data processing method provided in this embodiment of the invention can also use a blockchain for data storage in its implementation environment. During implementation, business data to be audited uploaded by other blockchain nodes can be obtained from existing blocks in the blockchain, downloaded to terminal 101 which is also a blockchain node, and visualized in the editing interface of terminal 101. Based on the continuity relationship between business data, continuous auditing of business data is performed through the generated target audit code. In addition, the audit results and related data can be packaged into a new block and uploaded to the blockchain through terminal 101. Through the decentralized data storage method of blockchain, business data is more open and secure, and malicious data tampering is also avoided.

[0042] like Figure 2 As shown, this embodiment of the invention provides a business data processing method, which can be applied to... Figure 1 This method can be implemented using terminal 101; alternatively, it can also be executed on any other device or equipment with data processing capabilities. (See reference...) Figure 2 The method specifically includes, but is not limited to, steps S100-S300:

[0043] S100, Display editing interface;

[0044] The editing interface in this embodiment may include, but is not limited to, a component bar area and a task area. The component bar area provides various types of component tools, while the task area displays various auditable elements, including but not limited to data tables, fields within data tables, and the continuity relationships between fields. In this embodiment, the component bar area includes multiple standardized components. Each standardized component can carry business data or be used to determine the type of business data table, field information of the business data table, or the continuity relationships between fields in the business data table.

[0045] For example, such as Figure 3As shown, in this embodiment, the component bar area can provide component tools for representing various continuous relationships. For example, the component tools for system components provide entity components and transaction components. The entity component can be used to represent the specific hardware devices or data-level storage structures involved in the audit process. During the audit process, the business data or associated business data tables related to the entity component can be obtained from the server's database. The transaction component can be used to represent the specific transactions involved in the audit process. The business data acquisition method of the transaction component is the same as that of the entity component. Both the transaction component and the entity component load or record business data in the form of data tables. In addition, since the business data in this embodiment is mainly displayed in the form of data tables, the component bar area also provides a data table component tool: the Tencent Distributed Data Warehouse (TDW) Table-Field Information Component (hereinafter referred to as the Table-Field Information Component). The Table-Field Information Component can be used to build or adjust the data tables of system components. Various business data, such as account ID, version number, and balance, can be recorded in the data table. Furthermore, during the process of constructing a new table using the table-field information component, the field names and data types of the business data can be set. For example, a field name can be changed to "Account ID," and the "Account ID" can be set to integer data; another field name can be changed to "Balance," and the "Balance" can be set to floating-point data. Understandably, in this embodiment, to create a new element or table component, the user first selects the target component in the component bar area, clicks it, and then drags and drops the component to the work area. The corresponding element or table component will then be displayed in the work area, showing a preview of the business data. Clicking on the component allows for data modification. It should be noted that the business data of the components in the work area can be modified. Modification can be done by direct input from the operator or by retrieving the corresponding business data from the server through the business data retrieval space.

[0046] S200: In response to the target operation command, configure the standardized components in the component bar in the work area to determine several data tables, several fields in the data tables, and the continuity relationship between the fields in the data tables.

[0047] The target operation instruction refers to the user's operation on the component in the work area of ​​the editing interface. This operation is captured and triggered by the work area. The operation includes, but is not limited to, moving, clicking, or connecting a field within a component to other fields. In this embodiment, continuity refers to the logical continuity of data during the audit process. Taking account balances in financial data as an example, continuity means that changes in account amounts, balances, and points due to transactions are logically continuous, rather than sudden jumps. More specifically, if user A's initial account balance is 100 yuan, and after a transaction of 50 yuan, user A's balance remains 50 yuan, then the business data in this transaction process can be considered continuous. In this embodiment, the continuity relationship refers to the correspondence that business data needs to maintain before and after transactions. For business data that needs to maintain continuity, it is verified whether this correspondence is satisfied. If so, a continuity relationship exists between the business data; otherwise, no continuity relationship exists. In this embodiment, the specific continuity relationships between business data can be represented in the editing interface using graphics or functions. For example, connecting lines can be used to indicate a continuity relationship between fields in a data table, and function elements can be used to represent the specific content of the continuity relationship. It should be noted that the continuity relationships determined in step S200 are all continuity relationships to be audited, not necessarily correct continuity relationships between business data. The correctness of the continuity relationship can be determined through auditing in subsequent steps.

[0048] For example, such as Figure 4 As shown, the user selects the Table-Field Information component in the component bar area to create two business data tables. Table A represents the information of account A in a transaction, including account ID, version number, initial balance, transaction amount, and termination balance. Table B represents the information of account B in a transaction, identical to Table A, including account ID, version number, initial balance, transaction amount, and termination balance. Since the operation is a transfer, to establish a continuity between the initial balance in Table A and the termination balance in Table B, the user can right-click the initial balance field in Table A in the work area and connect it to the termination balance field in Table B with a line. After connecting, the user can associate the connection with a function element. Thus, this embodiment establishes a continuity between the initial balance of account A and the termination balance of account B.

[0049] S300. Generate target audit code based on several data tables, several fields in the data tables, and the continuity relationship between the fields in the data tables;

[0050] This target audit code can be used to perform continuity audits on the business data corresponding to the field to be audited. Continuity auditing verifies the continuity relationship between business data in two table fields that have established a continuity relationship. It verifies whether the business data at both ends of the connection line satisfy the functional relationship in the function element. If they satisfy, the audit passes; otherwise, it indicates data anomalies and the audit fails. The audit results can be visualized in the work area, including but not limited to warning icons and text reminders.

[0051] For example, in the embodiment, the process of generating the target audit code may include, but is not limited to, steps S310-S340:

[0052] S310, Define consistency audit syntax rules, and construct syntax tree roots, define syntax entities, etc.

[0053] S320. According to the consistency audit syntax rules, the embodiment further defines the domain-specific language (DSL) of the consistency audit items. For example, after defining the basic entity of merchant multi-institution account application form, the data structure of the entity may include merchant multi-institution application form ID, non-multi-institution application form ID, and institution type, etc., and when auditing the entity, the field data of merchant multi-institution application form ID, non-multi-institution application form ID, and institution type are selected as audit items.

[0054] S330. The embodiment will perform lexical analysis on the consistency audit item DSL; for example, the embodiment can convert the defined consistency audit item DSL text into a string of tokens, where the token is a data type containing two main attributes: type and content.

[0055] S340. Perform syntax analysis on the consistency audit item DSL; according to the consistency audit syntax rules defined in step S310 of the embodiment, construct an abstract syntax tree from the token obtained in step S330; traverse the abstract syntax tree and combine it with the pre-set code template to generate the consistency target audit code.

[0056] In some alternative embodiments, the step S200, which involves configuring standardized components of the component bar in the work area in response to a target operation instruction, and determining several data tables, several fields in the data tables, and the continuity relationship between the fields in the data tables, may vary depending on the standardized components being configured. When a user needs to create a data table in the work area, step S200 in this embodiment may include, but is not limited to, step S210:

[0057] S210. In response to the first operation command on the first standardized component in the component bar area, a data table is created in the work area;

[0058] The first standardized component is a control component in the component bar area used to create a new data table in the work area; the first operation instruction is the operation performed by the user on the first standardized component in the component bar area or work area of ​​the editing interface. The operation is captured and triggered by the editing interface. It can be understood that the operation that triggers the first operation instruction includes, but is not limited to, clicking the control component to create a new data table and long-pressing the newly created table to drag it.

[0059] For example, such as Figure 5 As shown in the embodiment illustrated, the first standardized component is system element component 501. The user first clicks on this component in the component bar area of ​​the editing interface, triggering a control command to create a new data table. This generates a legend 503 for the data table in the editing interface and displays the movement trajectory 502 of the legend 503. The user can move the data table to any position in the work area by long-pressing and dragging the legend. It is understood that in this embodiment, other operation commands can also be used to fill or modify the business data in the data table. For example, target business data can be retrieved from the server using a data acquisition control and filled into the data table; or the name of the data table can be modified. Furthermore, the data table legend in this embodiment can display the field information contained in the data table and the specific business data corresponding to the field information, such as Account ID: 1001; Version Number: 2; Balance: 1000.

[0060] After constructing the data tables, in order to improve the operability of the embodiment and the richness of the visualization content, in response to the target operation command, the embodiment of the present invention configures the standardized components of the component bar in the work area, and determines several data tables, several fields in the data tables, and the continuity relationship of each field in the data tables. This step S200 may further include step S220:

[0061] S220, In response to a second operation instruction on a second standardized component in the component bar area, configure several fields in a data table in the work area;

[0062] The second standardized component is a control component in the component bar area used to modify, add, delete, and update fields in existing data tables in the work area. The second operation instruction is an operation performed by the user on the second standardized component in the component bar area or work area of ​​the editing interface. The operation is captured and triggered by the editing interface. It can be understood that the operation that triggers the second operation instruction includes, but is not limited to, clicking the control component to create a new data table field, adding or deleting a field in the data table, and modifying the name and data attributes of a field in the data table.

[0063] For example, such as Figure 6 As shown in the embodiment illustrated, the second standardized component is a table-field information component. This component displays a preview of the data table information currently in the work area. The preview content 601 includes the fields contained in the data table, the data types of each field, and the specific data values. To modify the field attributes in the data table, the user can click on the preview content in the component bar area or click on the field content of the data table in the work area to modify the data table field attributes, field names, or field data. For example, in this embodiment, using the plus sign control 6011 in the preview area 601 of the TWD table, two new fields named "Transaction Amount" and "Termination Balance" are added to the data table named "Account Balance" in the work area; the attributes of the two fields are set to integer type in the preview area, and the business data values ​​of "Transaction Amount" and "Termination Balance" in the data table are retrieved from the server's database using the data update control.

[0064] After adjusting and modifying the field content of the data table, the user can set the continuity relationship of the fields. In some alternative embodiments, in response to the target operation instruction, the standardized components of the component bar are configured in the work area to determine several data tables, several fields in the data tables, and the continuity relationship of the fields in the data tables. This step S200 may also include step S230 or step S240:

[0065] S230, In response to a third operation command on a third standardized component in the component bar area, configure the continuity relationship of each field in the data table in the work area;

[0066] The third standardized component is a control component used in the component bar area to establish continuous relationships between fields in an existing data table in the work area. For example, a function component is a control component that can represent continuous relationships between fields through function relationships. The third operation instruction is an operation performed by the user on the third standardized component in the component bar area or work area of ​​the editing interface. The operation is captured by the editing interface and triggered by the instruction. It can be understood that the operation that triggers the third operation instruction includes, but is not limited to, clicking in the component bar area to establish a new continuous relationship, or moving or modifying an existing continuous relationship in the work area.

[0067] For example, such as Figure 7 As shown, in order to establish a continuity relationship between the "Initial Balance" field in data table A and the "Termination Balance" field in data table B, the user first expands the preview interface 701 of the function relationship (i.e., continuity relationship) by clicking the function element, selects the common function control, and enters "Initial Balance of Table A" in object A of the common function control "fx=="; and enters "Termination Balance of Table B" in the corresponding B. At this point, the continuity relationship between the "Initial Balance" field in data table A and the "Termination Balance" field in data table B is established through the function element, and the constraint of the continuity relationship between the two fields is that their data values ​​are equal.

[0068] S240. In response to the fourth operation instruction, connect the fields in the data table with lines or arrowed lines in the work area, and select the third standardized component in the component bar area to configure the continuity relationship of the fields in the data table.

[0069] The third operation instruction refers to the user's operation on the field content of the data table in the work area of ​​the editing interface. This operation is captured and triggered by the editing interface. The corresponding operation is to select a data table field and connect it to another data table field using a line or an arrow. It should be noted that when establishing a continuity relationship between fields, the two selected fields can originate from the same data table or different data tables.

[0070] For example, such as Figure 8As shown, to establish a continuity relationship between the "Initial Balance" field 801 in data table A and the "Termination Balance" field 802 in data table B, the user first right-clicks the "Initial Balance" field in data table A to draw a connection line 803, and then connects the connection line to the "Termination Balance" field in data table B. This establishes a continuity relationship between the two fields. Then, the user can select the connection line and choose the common function control "fx==" from the function controls in the component bar area. This completes the continuity relationship between the "Initial Balance" field in data table A and the "Termination Balance" field in data table B, and determines the constraint of the continuity relationship between the two fields as whether they are equal.

[0071] In the foregoing embodiments, the third standardized component includes, but is not limited to, relational operators, arithmetic operators, and logical operators. Corresponding to the operators, the continuity relationship includes, but is not limited to, numerical magnitude relationships, arithmetic relationships, and logical relationships. In some alternative embodiments, the step S230 of selecting the continuity relationship of each field in the configuration data table for the third standardized component in the component bar area may include at least one of steps S231-S233:

[0072] S231. In response to the fifth operation instruction of selecting the relational operator in the component bar area, the continuity relationship of each field in the data table is determined as a numerical size relationship.

[0073] The fifth operation instruction is triggered by the user's operation of selecting the function control of the relational operator in the component bar area. In the embodiment, the values ​​used to represent numerical relationships include, but are not limited to, greater than, less than, equal to, and unequal to. For example, the user selects two data table fields in the editing interface that need to establish a numerical relationship, namely the "initial balance" field in data table A and the "terminating balance" field in data table B. After determining the fields, the user selects the common function control "fx>" in the function control in the component bar area. The common function control "fx>" is used to represent that the continuity relationship established between the "initial balance" field in data table A and the "terminating balance" field in data table B is that the data value of the "initial balance" field in data table A is greater than the data value of the "terminating balance" field in data table B.

[0074] S232. In response to the sixth operation instruction of selecting an arithmetic operator in the component bar area, the continuity relationship of each field in the data table is determined as an arithmetic relationship;

[0075] Specifically, the sixth operation instruction is triggered by the user's selection of the arithmetic operator function control in the component bar area; in the embodiment, the arithmetic relationship is used to represent operations including but not limited to addition, subtraction, multiplication, and division. Similar to step S231, the user can select the common function control "fx+" in the function control to represent adding the data values ​​in two selected data table fields and assigning the result to a third data table field. It should be understood that the third data table field can be a new data table field or either of the two selected data table fields.

[0076] S233. In response to the seventh operation instruction of selecting a logical operator in the component bar area, the continuity relationship of each field in the data table is determined as a logical relationship.

[0077] Specifically, the seventh operation instruction is the instruction triggered by the user's operation of selecting a function control of a logical operator in the component bar area; in the embodiment, the logical relationship is used to represent, but is not limited to, inclusion and being included.

[0078] In some alternative embodiments, in order to audit complex relationships expressed by combinations of fields from multiple (more than two) data tables, the business data processing method provided in the embodiments may further include steps S500-S600:

[0079] S500: Select a field in the data table as a candidate field;

[0080] Specifically, all fields from the data tables created by the user in the work area are used as candidate fields.

[0081] S600. When a candidate field is the same as a pre-configured field, and the continuity relationship of the candidate field meets the pre-configured continuity constraints, the candidate field is determined as a field to be audited.

[0082] The pre-configured fields are the filtering range determined by the user based on the data table fields to be audited before the audit is performed. It can be understood that the filtering range should include several data table fields, and the fields to be audited determined in the steps can also be various combinations of any number of data table fields from the filtering range. Furthermore, in this embodiment, to determine whether a candidate field is an audit field, its continuity relationship needs to be verified. If it is determined that the candidate field meets the continuity constraint conditions obtained by combining the continuity relationships between data table fields in the filtering range, then the candidate field is determined as a field to be audited.

[0083] To improve the accuracy of the fields to be audited obtained through screening, in some optional embodiments, the process of selecting fields in the data table as candidate fields in step S600 may include, but is not limited to, steps S610-S620:

[0084] S610, Obtain the pre-configured continuity constraints;

[0085] The continuity constraint is used to characterize the constraint relationship between several fields in a business data table. For example, in a certain consumption operation record, the continuity constraint between table A1 before the operation and table A2 after the operation should be: the version number field of table A2 should be obtained by adding one to the data value of the version number field of table A1; and the value of the ending balance field of table A1 should be the same as the value of the initial balance of table A2; furthermore, the ending balance of table A2 should be the sum of the transaction amount of table A2 and the initial balance of table A2. The data table fields that satisfy this continuity constraint are then considered candidate fields.

[0086] S620. Based on the continuity constraint, select candidate fields from the business data table;

[0087] For example, after obtaining server data, the embodiment obtains Table A1 and Table A2. If the version number field and the termination balance field of Table A1, and the version number field, transaction amount field, and termination balance field of Table A2 satisfy the continuity constraint condition in step S610, they are candidate fields.

[0088] In some alternative embodiments, to make the obtained candidate fields more accurate, the continuity constraints in the embodiments may include, but are not limited to, audit formulas for business data table formats, version number fields, initial balances, and final balances; furthermore, such as Figure 9 As shown, step S620, selecting candidate fields from the business data table based on continuity constraints, may include, but is not limited to, steps S621-S625:

[0089] S621. Based on the audit formula for the business data table format, determine several target business data tables to be audited that belong to the same business data table format.

[0090] Among them, the business data table format audit formula can identify the number of fields and field attributes contained in the business data table. When the number of fields and field attributes of the business data table are the same, it can be determined that the business data table being compared belongs to the target business data table to be audited with the same format.

[0091] For example, such as Figure 10 After obtaining the server business data, the example obtains data table A1 and data table A2. According to the table format audit formula, the number of fields and field attributes of table A1 and table A2 are compared. It is determined that the number of fields and field attributes of the two data tables are the same. The fields of the data tables are the same: account ID, version number, initial balance and termination balance.

[0092] S622. Based on the audit formula for the version number field, select the version number field as the first field from the target business data table;

[0093] The version number field audit formula is used to audit the relationship between two adjacent business data tables, where the version number of the later business data table is equal to the version number of the earlier business data table plus one. Taking data tables A1 and A2 in step S621 as an example, the value of the version number field recorded in table A2 is 3, and the value of the version number field in table A1 is 2; therefore, the version number fields of both tables A1 and A2 satisfy the version number field audit formula, and thus the version number fields in data tables A1 and A2 are determined as the first field.

[0094] S623. Select the initial balance field as the second field from the target business data table according to the initial balance audit formula;

[0095] The initial balance audit formula is used to audit the relationship between two adjacent business data tables, where the initial balance of the latter business data table equals the termination balance of the former business data table. Similarly, taking data tables A1 and A2 in step S621 as an example, the value of the termination balance field in table A1 is 1000; the value of the initial balance field in table A2 is 1000. Therefore, the termination balance field of table A1 and the initial balance field of table A2 satisfy the initial balance audit formula, and thus the termination balance field of table A1 and the initial balance field in table A2 are determined as the second field.

[0096] S624. Based on the termination balance audit formula, select the termination balance field as the third field from the target business data table;

[0097] The termination balance audit formula is used to audit any business data table. The termination balance is equal to the sum of the initial balance and the transaction amount. Similarly, taking the data table A2 obtained in step S621 as an example, the value of the termination balance field in table A2 is 1500, the value of the transaction amount field in table A2 is 500, and the value of the initial balance field in table A2 is 1000. Therefore, the termination balance field, transaction amount field, and initial balance field in table A2 are all third fields.

[0098] S625. Determine the candidate fields based on the first field, the second field, and the third field.

[0099] For example, in the field selection of data tables A1 and A2 according to steps S621-S624 of this embodiment of the invention, the determined candidate fields include: the version number field and the termination balance field of table A1, and the version number field, the transaction amount field, and the termination balance field of table A2. The above fields satisfy the continuity constraint conditions formed by S621-S624, and therefore can be determined as candidate fields under the continuity constraint conditions.

[0100] To reduce data processing volume and improve the readability of data tables visualized in the work area, in some alternative embodiments, step S621, determining several target business data tables to be audited that belong to the same business data table format according to the business data table format audit formula, may include at least one of steps S621a and S621b:

[0101] S621a, In response to the eighth operation instruction on several target business data tables, determine the association relationship between the several target business data tables;

[0102] Specifically, such as Figure 11 As shown, the eighth operation instruction is triggered by a user querying the relationships between several target business data tables in the work area. For example, the user first selects several business data tables 1001 that need to be merged, and then extracts the relationships between the tables by clicking the relationship query control 1002 in the editing interface. These relationships are then visualized in the work area. The relationships include, but are not limited to, the existence of identical or similar fields, or a clear distribution trend in the same field across several business data tables. By determining and extracting these relationships, this embodiment allows users to focus more on data with existing relationships, reducing the amount of data processed and improving processing efficiency.

[0103] S621b, in response to the ninth operation instruction on several target business data tables, merges the several target business data tables.

[0104] Specifically, the ninth operation instruction is triggered by the user merging several target business data tables within the work area. For example, as shown... Figure 11 The user first selects several business data tables 1001 that need to be merged. By clicking the table merge control 1003 in the editing interface, the user-selected business data tables are merged. The merging methods include, but are not limited to, full joins and inner joins. The example displays the merged master table visually in the work area to reduce the number of data tables displayed and to make the visualization more readable.

[0105] In some alternative embodiments, the step S100 of displaying the editing interface includes, but is not limited to, steps S110-S150:

[0106] S110, Configure the set of business data table types, the set of business data table fields, and the set of continuous relationships;

[0107] Specifically, after logging into the business data processing software system on the terminal and passing user authentication, the system retrieves the elements to be audited from the server's database or cloud database. These elements may include, but are not limited to, data tables of business data, fields contained in the data tables, and the continuity relationships between fields. To facilitate user organization and retrieval of data tables, the software system in this embodiment categorizes the data tables retrieved from the database into several business data table type sets based on their different types. This allows users to retrieve and extract data from the corresponding sets according to the needs of different data table types, reducing redundant data processing steps and improving audit efficiency. To facilitate user modification of data table field content and attributes, the software system in this embodiment integrates the field content of various types of data tables to obtain a business data table field set. Users can directly retrieve the complete field names and attributes from this business data table field set as needed and add them to the target data table, thereby saving operational steps and further improving audit efficiency. In addition, to facilitate users in constructing continuous relationships between data table fields, the software system in this embodiment integrates all continuous relationships that appear in historical data to obtain a continuous relationship set. Users can also select template components that have encapsulated relevant function expressions or formulas from this continuous relationship set according to specific needs to construct continuous relationships between target data table fields.

[0108] S120. Display the component bar area and the work area in the editing interface;

[0109] The editing interface includes a component bar area with various standardized components. Each standardized component can carry business data or be used to determine the type of business data table, field information, or the continuity relationship between fields in the business data table. The work area is used to visualize the standardized components selected by the user from the component bar area. It is understood that the work area in this embodiment can also visualize the user's actual operation process and the final audit results.

[0110] S130. Display the first standardized component in the component bar area according to the data table type set;

[0111] The first standardized component is used to determine the type of business data table. For example, in one embodiment, the first standardized component is a system element that includes an entity component and a transaction component. Both components can represent the specific hardware devices or data-level storage structures involved in the audit process, and the data tables derived from these two components are of the same type; for example, the entity component mainly stores specific monetary values ​​in user accounts, while the transaction component mainly stores information data related to the transaction. Therefore, in the software system of this embodiment, the user can select the corresponding component according to the required business data table type.

[0112] S140. Display the second standardized component in the component bar area according to the data table field set;

[0113] The second standardized component is used to determine the field composition of the business data table. Specifically, the second standardized component can be a field component template that integrates and encapsulates all the fields included in the data table stored in the database by the software system of the embodiment. Users can select a field component template according to specific needs and add it to the data table by dragging and dropping. Entering specific data values ​​in the field template completes the addition of the field content.

[0114] S150. Based on the set of continuous relationships, display the third standardized component in the component bar area;

[0115] The third standardization component is used to determine the continuity relationship between fields. Specifically, the third standardization component can be a component module in the embodiment software system that integrates the continuity relationships between all data table fields stored in the database and encapsulates the relational expression function or formula to obtain the continuity relationship. For example, relational operators, arithmetic operators, and logical operators are encapsulated into function elements. Users can select a component of a certain continuity relationship according to specific needs and establish the continuity relationship between data table fields by connecting them.

[0116] In some alternative embodiments, to improve the accuracy of audit results, the business data processing method may further include step S700:

[0117] S700: Display the number of business data tables in the editing interface; when the number of business data tables is less than the target number of business data tables, display the missing auditable fields in the editing interface.

[0118] Specifically, before conducting an audit, the embodiment can preset an audit template for the target business data table. This audit template includes, but is not limited to, the number of data tables to be audited, the fields to be audited, and the types of field data. The audit template is stored in the software system's backend and can serve as the basis for quality control of the user-created business data tables to be audited. For example, if the number of data tables created by the user using the annotation components is less than the number of audit templates, the software system will provide a visual reminder; for example, by displaying the missing fields to be audited in the work area, or by displaying the missing field components in the component bar area.

[0119] In some alternative embodiments, to improve resilience and security, the business data processing method may further include step S800:

[0120] S800: Obtain the business data table and audit results for continuous auditing; distribute the business data table in the database cluster and distribute the audit results in the server cluster.

[0121] In this context, a server cluster refers to a group of servers working together to provide the same service, while the client perceives only one server. For example, the embodiment can encapsulate standardized functional components and continuous relational formulas using C++, and perform structured and modular processing of data tables, making it easier for the software system to automate processes. The software system service can be deployed in a distributed manner, with multiple copies of the service maintained to improve availability. Data storage in the embodiment can also utilize a MySQL relational database management system, and Redis can be used as a cache to ensure system performance. Furthermore, the database cluster in the embodiment can be deployed separately from the service cluster to reduce the coupling between services and data, providing database disaster recovery capabilities.

[0122] Based on the above-described business data processing method, taking the auditing process of business data in the financial field as an example, the business data processing process of this embodiment of the invention will be described in detail with reference to the accompanying drawings:

[0123] For example, in a transaction scenario in the financial field, a user's account balance data is stored in a database table, and changes to the balance in the data table need to comply with certain continuity constraints. For example... Figure 4As shown, in the editing interface of the software system in this embodiment, Table A is used to represent the data table for user account balances. The fields in Table A represent data table fields, such as version number, initial balance, final balance, and transaction amount. In the editing interface of the software system in this embodiment, the visualized data table displays the data stored by the audited entity in the work area at a database granularity. In this embodiment, the component bar area is equipped with various types of components used to determine the type of business data table, business data table field information, or the continuity relationship between fields in the business data table; for example, lines represent continuity constraints between data table fields, and function elements represent specific continuity constraints such as equality or addition. Furthermore, the system components in the editing interface can also add multiple specific data tables, determining the continuity relationship between fields in each data table or more complex continuity constraints based on the actual situation; for example, Table A, Table B, and Table C can be added, with continuity constraints between fields in Table A and Table B, and also between fields in Table B and Table C.

[0124] like Figure 12 As shown, the operation flow in the editing interface of this embodiment consists of three steps. First, the data table to be filtered is displayed in the editing interface. Then, the data in the data table is filtered through standardized functional components. Finally, continuity constraints are described using continuity fruits. Specifically, the user determines the data tables to be added (the number of data tables can be arbitrary), and then selects a system element from the component bar area, such as an entity or transaction, to load the added data tables into the system element; a table diagram is formed in the work area. Then, according to the continuity constraint requirements between different data tables, the fields between different tables are connected with lines to express that the two fields have a continuity constraint relationship. In addition, the user can also add specific function components to the lines from the component bar area to express the specific content of the continuity constraint relationship, such as two fields being equal, the value of the previous field being added by one to obtain the value of the next field, etc. The final result is as follows. Figure 4 As shown, there is a continuity constraint between the two data tables. The specific fields are the initial balance and the ending balance. The continuity constraint between the two fields is whether they are equal.

[0125] Finally, based on the continuity constraints between the two data tables expressed in the work area, the software system of the embodiment can automatically generate relevant code to audit the relevant data in the database. That is, it audits whether the beginning balance and ending balance of the two tables meet the above-mentioned continuity constraint relationship. If they do, the audit is passed; if they do not, it means that there is a problem with the data and the audit is not passed.

[0126] It should be added that the front-end code of the example software is implemented based on the Vue open-source framework and the Element UI open-source components, encapsulating independent standardized functions and standardized components with standardized descriptions. For example, in Figure 4 The function element encapsulates function expressions or formulas for describing various continuity relationships. When establishing continuity relationships or complex continuity constraints, these relationships can be completed through simple interactive commands such as clicking and dragging. In addition, the standardized functions encapsulated in this embodiment may also include data table association and merging operations, thereby reducing the data processing workload for business personnel and resulting in fewer table fields displayed on the interface, enhancing readability. The standardized functions encapsulated in this embodiment may also include functions for expressing complex continuity constraints; for example, in one embodiment, the fields used to establish continuity constraints in the data must all satisfy the following four formulas:

[0127] 1. Two identical data tables (data tables updated after a transaction of the same type or the same object) are designated as Table A and Table B, respectively.

[0128] 2. The value of the version number field in table A plus one equals the value of the version number in table B; where the version number indicates the number of times the data in the table has been changed, and the version number increments by one for each change;

[0129] 3. The data value of the initial balance field in table A is equal to the data value of the termination balance field in table B;

[0130] 4. In Table B, the data value of the Termination Balance field should be equal to the sum of the data value of the Initial Balance field and the data value of the Transaction Amount field in Table B.

[0131] Taking a user's account balance information record as an example, before a transaction, the account balance is: current balance 100 yuan. During the transaction, the user incurred a expense of 10 yuan. After the transaction is completed, a new account balance information record is generated in the database: current balance 90 yuan. Applying the aforementioned four formulas to this transaction scenario, the account balance information record before the transaction corresponds to data table A; the account balance information record after the transaction corresponds to data table B. In table A, the data recorded in the "Terminal Balance" field is 100; in table B, the data recorded in the "Initial Balance" field is 100, the data recorded in the "Transaction Amount" field is 10, and the data recorded in the "Terminal Balance" field is 90. Furthermore, if the value recorded in the "Version Number" field of table A is 1, then the value recorded in the "Version Number" field of table B is 2.

[0132] In summary, this embodiment can be briefly described as follows: The user constructs a system based on all possible continuous relational components (i.e., function elements) and content components (i.e., system elements), such as... Figure 4 The user interface shows how users can select the data tables to be audited within the corresponding system components, clearly indicating which fields in each data table require auditing. For example, which fields need to be audited can be determined based on pre-defined continuity constraints. After configuration in the work area, the system automatically generates audit codes based on the continuity relationships between fields, auditing all actual data. This process eliminates the need for manual auditing or verification by auditors, thus improving audit efficiency.

[0133] like Figure 13 As shown, this embodiment of the invention also provides a business data processing device, which includes a first module 1301, a second module 1302 and a third module 1303;

[0134] The first module 1301 is used to display the editing interface, which includes a component bar area and a work area. The component bar area includes a variety of standardized components, each of which is used to determine the business data table type, business data table field information, or the continuity relationship between fields in the business data table.

[0135] The second module 1302 is used to respond to the target operation command, configure the standardized components in the component bar in the work area, and determine several data tables, several fields in the data tables, and the continuity relationship between the fields in the data tables.

[0136] The third module 1303 is used to generate target audit codes based on several data tables, several fields in the data tables, and the continuity relationship between the fields in the data tables. The target audit codes are used to perform continuity audits on the business data corresponding to the fields to be audited.

[0137] For example, with the collaboration of the first, second, and third modules in the device, the embodiment device can implement any of the aforementioned business data processing methods. Specifically, based on the user's target operation instructions, standardized components in the component bar are configured in the work area to determine the elements to be audited. These elements may include, but are not limited to, data tables, fields within data tables, and the continuity relationships between fields. Then, the embodiment generates target audit code based on the elements to be audited and performs continuity auditing. By encapsulating standardized functions into components, standardized functions are provided to business personnel, reducing the workload of manually writing code, simplifying the process, effectively reducing the probability of errors, and improving audit quality.

[0138] This invention also provides an electronic device, which includes a processor and a memory;

[0139] The memory stores the program;

[0140] The processor executes a program to perform the aforementioned business data processing method; the electronic device has the function of carrying and running the business data processing software system provided in the embodiments of the present invention, such as a personal computer (PC), mobile phone, smartphone, personal digital assistant (PDA), wearable device, handheld computer (PPC), tablet computer, etc.

[0141] This invention also provides a computer-readable storage medium storing a program that is executed by a processor to implement the business data processing method described above.

[0142] In some alternative embodiments, the functions / operations mentioned in the block diagrams may not occur in the order shown in the operation diagrams. For example, depending on the functions / operations involved, two consecutively shown blocks may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order. Furthermore, the embodiments presented and described in the flowcharts of this invention are provided by way of example to provide a more comprehensive understanding of the technology. The disclosed methods are not limited to the operations and logic flows presented herein. Alternative embodiments are contemplated in which the order of various operations is altered and sub-operations described as part of a larger operation are executed independently.

[0143] This invention also discloses a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device can read the computer instructions from the computer-readable storage medium and execute the computer instructions, causing the computer device to perform the aforementioned business data processing method.

[0144] Furthermore, although the invention has been described in the context of functional modules, it should be understood that, unless otherwise stated, one or more of the described functions and / or features may be integrated into a single physical device and / or software module, or one or more functions and / or features may be implemented in a separate physical device or software module. It is also understood that a detailed discussion of the actual implementation of each module is unnecessary for understanding the invention. Rather, given the properties, functions, and internal relationships of the various functional modules in the apparatus disclosed herein, the actual implementation of the module will be understood within the scope of conventional skill of an engineer. Therefore, those skilled in the art can implement the invention as set forth in the claims using ordinary techniques without excessive experimentation. It is also understood that the specific concepts disclosed are merely illustrative and not intended to limit the scope of the invention, which is determined by the full scope of the appended claims and their equivalents.

[0145] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0146] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-included system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device.

[0147] More specific examples of computer-readable media (a non-exhaustive list) include: electrical connections (electronic devices) having one or more wires, portable computer disk drives (magnetic devices), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Furthermore, computer-readable media can even be paper or other suitable media on which the program can be printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, interpreting, or otherwise processing as necessary, and then stored in computer memory.

[0148] It should be understood that various parts of the present invention can be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0149] In the description of this specification, references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0150] Although embodiments of the invention have been shown and described, those skilled in the art will understand that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the claims and their equivalents.

[0151] The above is a detailed description of the preferred embodiments of the present invention, but the present invention is not limited to the embodiments described. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of the present invention, and these equivalent modifications or substitutions are all included within the scope defined by the claims of this application.

Claims

1. A business data processing method, characterized in that, include: The editing interface includes a component bar area and a job area. The component bar area includes a variety of standardized components. Each standardized component is used to determine the business data table type, business data table field information, or the auditable continuity relationship between fields in the business data table. The continuity relationship refers to the correspondence that the business data in the business data table before the business operation and the business data table after the business operation need to maintain. In response to the target operation command, the standardized components in the component bar area are configured in the work area to establish several data tables, several fields in the data tables, and auditable continuity relationships between the fields in the data tables; wherein, the continuity relationship is identified by the connection between the fields of different business data tables in the work area; A target audit code is generated based on several data tables, several fields in the data tables, and the continuity relationship to be audited between the fields in the data tables. The target audit code is used to perform continuity audit on the business data corresponding to the fields.

2. The business data processing method according to claim 1, characterized in that, In response to a target operation command, the standardized components of the component bar area are configured in the work area, and several data tables, several fields in the data tables, and auditable continuity relationships between the fields in the data tables are established, including: In response to a first operation instruction on a first standardized component in the component bar area, the data table is created in the work area.

3. The business data processing method according to claim 2, characterized in that, In response to a target operation command, the standardized components of the component bar area are configured in the work area, and several data tables, several fields in the data tables, and auditable continuity relationships between the fields in the data tables are established, including: In response to a second operation instruction on a second standardized component in the component bar area, several fields in the data table are configured in the work area.

4. The business data processing method according to claim 3, characterized in that, In response to a target operation command, the standardized components of the component bar area are configured in the work area, and several data tables, several fields in the data tables, and auditable continuity relationships between the fields in the data tables are established, including: In response to a third operation instruction on a third standardized component in the component bar area, the continuity relationship of each field in the data table is configured in the work area; Alternatively, in response to a fourth operation instruction, the fields in the data table are connected in the work area with lines or arrowed lines, and a third standardized component is selected in the component bar area to configure the continuity relationship of the fields in the data table.

5. The business data processing method according to claim 4, characterized in that, The third standardized component includes relational operators, arithmetic operators, and logical operators; the continuous relation includes numerical magnitude relations, arithmetic relations, and logical relations. The step of configuring the continuity relationship of each field in the data table by selecting the third standardized component in the component bar area includes: In response to a fifth operation instruction that selects the relational operator in the component bar area, the continuity relationship of each field in the data table is determined as a numerical size relationship; Alternatively, in response to a sixth operation instruction that selects the arithmetic operator in the component bar area, the continuity relationship of each of the fields in the data table is determined as an arithmetic relationship; Alternatively, in response to a seventh operation instruction that selects the logical operator in the component bar area, the continuity relationship of the fields in the data table is determined as a logical relationship.

6. The business data processing method according to claim 1, characterized in that, The method further includes: The field in the data table is selected as the candidate field; When the candidate field is the same as the pre-configured field, and the continuity relationship of the candidate field meets the pre-configured continuity constraints, the candidate field is determined as the field to be audited.

7. The business data processing method according to claim 6, characterized in that, The selection of the fields in the data table as candidate fields includes: Obtain pre-configured continuity constraints; the continuity constraints are used to characterize the constraint relationships between several fields in the business data table; Candidate fields are selected from the business data table based on the continuity constraints.

8. The business data processing method according to claim 7, characterized in that, The continuity constraints include audit formulas for business data table formats, version number fields, initial balances, and final balances; The step of selecting candidate fields from the business data table based on the continuity constraint includes: Based on the audit formula for the business data table format, identify several target business data tables to be audited that belong to the same business data table format. According to the version number field audit formula, the version number field is selected as the first field from the target business data table; wherein, the version number field audit formula is used to audit the relationship between two adjacent business data tables, and the version number of the latter business data table is equal to the version number of the former business data table plus one. The initial balance field is selected as the second field from the target business data table according to the initial balance audit formula; wherein, the initial balance audit formula is used to audit the relationship between two adjacent business data tables, where the initial balance of the latter business data table is equal to the termination balance of the former business data table; According to the termination balance audit formula, the termination balance field is selected as the third field from the target business data table; wherein, the termination balance audit formula is used to audit any business data table, and the termination balance is equal to the sum of the initial balance and the transaction amount; The candidate fields are determined based on the first field, the second field, and the third field.

9. The business data processing method according to claim 8, characterized in that, After the step of determining several target business data tables to be audited under the same business data table format according to the audit formula of the business data table format, it also includes at least one of the following: In response to the eighth operation instruction on the plurality of target business data tables, the association relationship between the plurality of target business data tables is determined; Alternatively, in response to the ninth operation instruction on the plurality of target business data tables, the plurality of target business data tables are merged.

10. A business data processing method according to claim 1, characterized in that, The display editing interface includes: Configure the set of business data table types, the set of business data table fields, and the set of continuous relationships; The component bar area and the job area are displayed in the editing interface; Based on the set of data table types, a first standardized component is displayed in the component bar area. The first standardized component is used to determine the type of the business data table. Based on the data table field set, a second standardized component is displayed in the component bar area. The second standardized component is used to determine the field composition of the business data table. Based on the set of continuity relationships, a third standardized component is displayed in the component bar area. The third standardized component is used to determine the continuity relationships between fields.

11. The business data processing method according to any one of claims 1-10, characterized in that, The method further includes: The number of business data tables is displayed in the editing interface; When the number of business data tables is less than the number of target business data tables, the missing auditable fields are displayed in the editing interface.

12. The business data processing method according to any one of claims 1-10, characterized in that, The method further includes: Obtain the business data table for the continuity audit and the audit results for the continuity audit; The business data tables are distributed and stored in the database cluster, and the audit results are distributed and stored in the server cluster.

13. A business data processing device, characterized in that, include: The first module is used to display the editing interface, which includes a component bar area and a job area. The component bar area includes a variety of standardized components. Each standardized component is used to determine the business data table type, business data table field information, or the auditable continuity relationship between fields in the business data table. The continuity relationship refers to the correspondence that the fields in the business data table before the business operation and the business data table after the business operation need to maintain. The second module is used to configure the standardized components of the component bar area in the work area in response to the target operation command, and to establish several data tables, several fields in the data tables, and the auditable continuity relationship between the fields in the data tables; wherein, the continuity relationship is identified by the connection between the fields of different business data tables in the work area. The third module is used to generate target audit code based on several data tables, several fields in the data tables, and the continuity relationship to be audited between the fields in the data tables. The target audit code is used to perform continuity audit on the business data corresponding to the fields.

14. An electronic device, characterized in that, Including the processor and memory; The memory is used to store programs; The processor executes the program to implement the method as described in any one of claims 1-12.

15. A computer-readable storage medium, characterized in that, The storage medium stores a program that is executed by a processor to implement the method as described in any one of claims 1-12.

16. A computer program product, characterized in that, The computer program product includes computer instructions that are executed by a processor to implement the method as described in any one of claims 1-12.

Images