CN116860779A - Accounting method, device, equipment, medium and product - Google Patents

Accounting method, device, equipment, medium and product Download PDF

Info

Publication number
CN116860779A
CN116860779A CN202310868677.6A CN202310868677A CN116860779A CN 116860779 A CN116860779 A CN 116860779A CN 202310868677 A CN202310868677 A CN 202310868677A CN 116860779 A CN116860779 A CN 116860779A
Authority
CN
China
Prior art keywords
reconciliation
field
attribute
data source
source
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202310868677.6A
Other languages
Chinese (zh)
Inventor
黄剑佳
李伟
蒋忆成
程鹏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Industrial and Commercial Bank of China Ltd ICBC
Original Assignee
Industrial and Commercial Bank of China Ltd ICBC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Industrial and Commercial Bank of China Ltd ICBC filed Critical Industrial and Commercial Bank of China Ltd ICBC
Priority to CN202310868677.6A priority Critical patent/CN116860779A/en
Publication of CN116860779A publication Critical patent/CN116860779A/en
Pending legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24—Querying
    • G06F16/242—Query formulation
    • G06F16/2433—Query languages
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/22—Indexing; Data structures therefor; Storage structures
    • G06F16/2282—Tablespace storage structures; Management thereof
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/03—Credit; Loans; Processing thereof
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/12—Accounting
    • G06Q40/125—Finance or payroll

Abstract

The disclosure provides a reconciliation method, a device, equipment, a medium and a product, relates to the distributed technical field, and can be applied to the technical field of financial science and technology, wherein the method comprises the following steps: and configuring a reconciliation definition table and a reconciliation field attribute table, wherein the reconciliation definition table is used for recording a reconciliation data source and a reconciliation matching field, and the reconciliation field attribute table is used for recording an attribute field of the reconciliation data source. And in response to the reconciliation starting instruction, invoking a reconciliation definition table and a reconciliation field attribute table to acquire a reconciliation data source, a reconciliation matching field and an attribute field of the reconciliation data source of the to-be-reconciled task. And generating a reconciliation job program corresponding to the to-be-reconciled task according to the reconciliation data source, the reconciliation matching field and the attribute field of the reconciliation data source of the to-be-reconciled task. And executing a reconciliation job program to complete the reconciliation of the target table and the source table in the task to be reconciled.

Description

Accounting method, device, equipment, medium and product
Technical Field
The disclosure relates to the field of distributed technology, and may be applied to the technical field of financial science and technology, in particular to a reconciliation method, device, equipment, medium and product.
Background
In credit business, a perfect reconciliation mechanism is a key factor for ensuring the normal operation of a credit system. At present, the checking of a credit system mainly depends on batch checking at night of a host computer, and for scenes with higher timeliness requirements, the batch checking at night often cannot meet the timeliness requirements. In addition, in the newly added account checking scene, new batch program support is required, repeated development is caused, and the account checking realization efficiency is seriously affected.
Disclosure of Invention
In view of this, the main purpose of the present disclosure is to provide a checking method, device, equipment, medium and product, which aims at least partially solving the technical problems of low timeliness, repeated development of batch programs and the like in the existing checking method.
To achieve the above object, a first aspect of an embodiment of the present disclosure provides a reconciliation method, including: configuring a reconciliation definition table and a reconciliation field attribute table, wherein the reconciliation definition table is used for recording a reconciliation data source and a reconciliation matching field, and the reconciliation field attribute table is used for recording an attribute field of the reconciliation data source; responding to a reconciliation starting instruction, and calling the reconciliation definition table and a reconciliation field attribute table to acquire a reconciliation data source, a reconciliation matching field and an attribute field of the reconciliation data source of a to-be-reconciled task; generating a reconciliation job program corresponding to the to-be-reconciled task according to the reconciliation data source, the reconciliation matching field and the attribute field of the reconciliation data source of the to-be-reconciled task; and executing the reconciliation job program to finish reconciliation of the target table and the source table in the task to be reconciled.
According to an embodiment of the disclosure, the generating the reconciliation job program corresponding to the to-be-reconciled task according to the reconciliation data source, the reconciliation matching field, and the attribute field of the reconciliation data source includes: and splicing the reconciliation data source, the reconciliation matching field and the attribute field of the reconciliation data source to generate an HQL query statement as the reconciliation job program.
According to an embodiment of the present disclosure, the stitching the reconciliation data source, the reconciliation matching field, and the attribute field of the reconciliation data source, generating the HQL query statement as the reconciliation job program includes: and under the condition that the number of the single-side accounts in the source table is larger than that of the single-side accounts in the target table, splicing the reconciliation data source, the reconciliation matching field and the attribute field to generate the HQL query statement by using a left connection condition of a primary key field of the source table and a primary key field of the target table in the attribute field and a driving table of the target table.
According to an embodiment of the present disclosure, the stitching the reconciliation data source, the reconciliation matching field, and the attribute field of the reconciliation data source, generating the HQL query statement as the reconciliation job program further includes: and under the condition that the number of the single-side accounts in the source table is smaller than that of the single-side accounts in the target table, splicing the reconciliation data source, the reconciliation matching field and the attribute field to generate the HQL query statement by using a left connection condition of a primary key field of the source table and a primary key field of the target table in the attribute field and a driving table of the source table.
According to an embodiment of the present disclosure, the stitching the reconciliation data source, the reconciliation matching field, and the attribute field of the reconciliation data source, generating the HQL query statement as the reconciliation job program further includes: and under the condition that the data of the source table and the data of the target table are inconsistent, splicing the reconciliation data source, the reconciliation matching field and the attribute field by using the primary key field of the source table and the primary key field of the target table in the attribute field as an interconnection condition to generate the HQL query statement.
According to an embodiment of the disclosure, the executing the reconciliation job program to complete the reconciliation of the target table and the source table in the task to be reconciled includes: and calling an application program interface of spark to execute the HQL query statement to finish the reconciliation of the target table and the source table in the task to be reconciled.
According to an embodiment of the disclosure, the reconciliation matching field includes a source type flag and a target type flag; before generating the reconciliation job program corresponding to the to-be-reconciled task according to the reconciliation data source, the reconciliation matching field, and the attribute field of the reconciliation data source of the to-be-reconciled task, the method further comprises: determining whether the source type flag and the target type flag are HQL sentences; under the condition that the source type mark and the target type mark are not HQL sentences, generating the reconciliation job program directly based on the reconciliation definition table and the reconciliation field attribute table; and under the condition that the source type mark and the target type mark are HQL sentences, creating a view according to the reconciliation definition table and the reconciliation field attribute table, and generating the reconciliation job program according to the view.
According to an embodiment of the present disclosure, the method further comprises: obtaining a reconciliation result obtained by executing the reconciliation job program; analyzing the account checking result, and determining a difference record between the target table and the source table; and splicing the difference records according to the attribute fields.
According to an embodiment of the disclosure, the reconciliation matching field includes a job number, a reconciliation name, a source table name, a target table name, and a reconciliation date field; the attribute fields include source field names, destination field names, result field aliases, field sequence numbers, primary key fields, source field functions, source field function parameter values, destination field functions, destination field function parameter values.
A second aspect of an embodiment of the present disclosure provides a reconciliation apparatus, comprising: the configuration module is used for configuring a reconciliation definition table and a reconciliation field attribute table, wherein the reconciliation definition table is used for recording a reconciliation data source and a reconciliation matching field, and the reconciliation field attribute table is used for recording an attribute field of the reconciliation data source; the first acquisition module is used for responding to the reconciliation starting instruction, calling the reconciliation definition table and the reconciliation field attribute table to acquire a reconciliation data source, a reconciliation matching field and an attribute field of the reconciliation data source of the to-be-reconciled task; the first generation module is used for generating a reconciliation job program corresponding to the to-be-reconciled task according to the reconciliation data source, the reconciliation matching field and the attribute field of the reconciliation data source of the to-be-reconciled task; and the execution module is used for executing the reconciliation job program to finish reconciliation of the target table and the source table in the task to be reconciled.
A third aspect of an embodiment of the present disclosure provides an electronic device, including: one or more processors; and a storage means for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform a reconciliation method in accordance with the foregoing.
A fourth aspect of the disclosed embodiments provides a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform a reconciliation method according to the above.
A fifth aspect of the disclosed embodiments provides a computer program product comprising a computer program which, when executed by a processor, implements a reconciliation method according to the above.
According to the account checking method, the device, the equipment, the medium and the product provided by the embodiment of the disclosure, the account checking method at least has the following beneficial effects:
because the reconciliation definition table is pre-configured to record the reconciliation data source and the reconciliation matching field, the attribute field of the reconciliation field attribute table discipline reconciliation data source is pre-configured, and the reconciliation definition table and the reconciliation field attribute table are directly called to generate the reconciliation job program for reconciliation when the reconciliation is required, the access efficiency of reconciliation can be effectively improved, and the timeliness of reconciliation is improved. When the account is newly added, the account can be newly added only by configuring the corresponding data in the account checking definition table and the account checking field attribute, repeated development is not needed, the development cost is saved, and the account checking efficiency is improved. Because multiple sets of accounts can be configured in the account checking definition table and the account checking field attribute, corresponding account checking operation programs can be generated based on the account checking data sources, the account checking matching fields and the account checking data sources of different accounts, and therefore, multiple sets of accounts can be accessed simultaneously, and batch account checking can be achieved more efficiently. The reusability is high.
By generating the HQL query statement as the reconciliation job program, the HQL query statement is used for object-oriented encapsulation of query conditions and has rich and flexible query characteristics, so that the reconciliation information can be efficiently and accurately queried under the condition of being applied to batch reconciliation and simultaneous access of multiple sets of reconciliation, and efficient and accurate reconciliation is realized.
As the corresponding HQL query sentences are generated for checking account for different data in the source table and the target table, the checking account of different account conditions can be satisfied, and thus the flexibility and the efficiency of checking account are improved.
Because spark can provide distributed queries and can optimize the workload of iterations, batch reconciliation can be better achieved and the workload of the reconciliation device reduced by invoking the application program interface of spark to execute HQL query statements to complete the reconciliation.
Because the source type mark and the target type mark are pre-configured to distinguish whether the HQL is supported or not, and different forms of generation of the reconciliation job program are adopted for the two allocations of supporting the HQL and not supporting the HQL, the reconciliation of different reconciliation scenes can be satisfied, and the reconciliation flexibility is further improved.
Because the difference records are spliced and stored based on the attribute fields, the follow-up backtracking of the difference accounting information can be facilitated.
Drawings
In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present disclosure, and other drawings may be obtained from the structures shown in these drawings without inventive effort to those of ordinary skill in the art.
FIG. 1 schematically illustrates a system architecture 100 of a reconciliation method and apparatus in accordance with an embodiment of the disclosure;
FIG. 2 schematically illustrates a flow diagram of a reconciliation method in accordance with an embodiment of the disclosure;
fig. 3 schematically illustrates a flowchart of generating a reconciliation job program corresponding to a task to be reconciled in operation S203 in accordance with an embodiment of the disclosure;
FIG. 4 schematically illustrates a flow diagram of generating an HQL query statement in operation S301 according to an embodiment of the disclosure;
FIG. 5 schematically illustrates a flow chart of generating an HQL query statement in operation S301 according to another embodiment of the disclosure;
FIG. 6 schematically illustrates a flow chart of generating an HQL query statement in operation S301 according to yet another embodiment of the disclosure;
FIG. 7 schematically illustrates a flow chart of a reconciliation method in accordance with another embodiment of the disclosure;
FIG. 8 schematically illustrates a flow chart of a reconciliation method in accordance with yet another embodiment of the disclosure;
FIG. 9 schematically illustrates a block diagram of a reconciliation apparatus in accordance with an embodiment of the disclosure;
FIG. 10 schematically illustrates a block diagram of a reconciliation apparatus in accordance with another embodiment of the disclosure;
FIG. 11 schematically illustrates a block diagram of a reconciliation apparatus in accordance with another embodiment of the disclosure;
fig. 12 schematically shows a block diagram of an electronic device adapted to implement the method described above, according to an embodiment of the disclosure.
Detailed Description
Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is only exemplary and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the present disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the concepts of the present disclosure.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and/or the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It should be noted that the terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly formal manner.
Where expressions like at least one of "A, B and C, etc. are used, the expressions should generally be interpreted in accordance with the meaning as commonly understood by those skilled in the art (e.g.," a system having at least one of A, B and C "shall include, but not be limited to, a system having a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a formulation similar to at least one of "A, B or C, etc." is used, in general such a formulation should be interpreted in accordance with the ordinary understanding of one skilled in the art (e.g. "a system with at least one of A, B or C" would include but not be limited to systems with a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).
Some of the block diagrams and/or flowchart illustrations are shown in the figures. It will be understood that some blocks of the block diagrams and/or flowchart illustrations, or combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data consistency restoration apparatus, such that the instructions, when executed by the processor, create means for implementing the functions/acts specified in the block diagrams and/or flowchart. The techniques of this disclosure may be implemented in hardware and/or software (including firmware, microcode, etc.). Additionally, the techniques of this disclosure may take the form of a computer program product on a computer-readable storage medium having instructions stored thereon, the computer program product being for use by or in connection with an instruction execution system.
In the technical scheme of the disclosure, the related information is collected, stored, used, processed, transmitted, provided, disclosed, applied and the like, which all conform to the regulations of related laws and regulations, necessary security measures are taken, and the public order harmony is not violated.
In the technical scheme of the disclosure, if the personal information of the user needs to be acquired, the authorization or the consent of the user is acquired before the personal information of the user is acquired or acquired.
Aiming at the technical problems in the related art, the embodiment of the disclosure provides a reconciliation method, which comprises the following steps: and configuring a reconciliation definition table and a reconciliation field attribute table, wherein the reconciliation definition table is used for recording a reconciliation data source and a reconciliation matching field, and the reconciliation field attribute table is used for recording an attribute field of the reconciliation data source. And in response to the reconciliation starting instruction, invoking a reconciliation definition table and a reconciliation field attribute table to acquire a reconciliation data source, a reconciliation matching field and an attribute field of the reconciliation data source of the to-be-reconciled task. And generating a reconciliation job program corresponding to the to-be-reconciled task according to the reconciliation data source, the reconciliation matching field and the attribute field of the reconciliation data source of the to-be-reconciled task. And executing a reconciliation job program to complete the reconciliation of the target table and the source table in the task to be reconciled.
Fig. 1 schematically illustrates a system architecture 100 of a reconciliation method and apparatus in accordance with an embodiment of the disclosure. It should be noted that fig. 1 is only an example of a system architecture to which embodiments of the present disclosure may be applied to assist those skilled in the art in understanding the technical content of the present disclosure, but does not mean that embodiments of the present disclosure may not be used in other devices, systems, environments, or scenarios.
As shown in fig. 1, a system architecture 100 according to this embodiment may include a database 101, a network 102, and a server 103. The database 101 communicates with the server 103 via the network 102.
The database 101 may store a pre-configured reconciliation definition table and a reconciliation field attribute table. The reconciliation definition table is used for recording a reconciliation data source and a reconciliation matching field, and the reconciliation field attribute table is used for recording an attribute field of the reconciliation data source.
Network 102 may include various connection types such as wired, wireless communication links, or fiber optic cables, among others. The wired mode can be, for example, connection by adopting any one of the following interfaces: the wireless mode may be, for example, a wireless mode connection, where the wireless mode may be, for example, any one of a plurality of wireless technology standards such as bluetooth, wi-Fi, infrared, zigBee, etc.
The server 103 may be a server that provides various services, such as a background management server (for example only) that performs reconciliation. In response to the reconciliation start instruction, the background management server invokes the reconciliation definition table and the reconciliation field attribute table from the database 101 through the network 102 to obtain a reconciliation data source, a reconciliation match field, and an attribute field of the reconciliation data source for the reconciliation task, generates a reconciliation job procedure corresponding to the reconciliation task according to the reconciliation data source, the reconciliation match field, and the attribute field of the reconciliation data source for the reconciliation task, and executes the reconciliation job procedure to complete reconciliation of the target table and the source table in the reconciliation task.
It should be noted that, the reconciliation method provided by the embodiments of the present disclosure may be performed by the server 103. Accordingly, the reconciliation device provided by the embodiments of the present disclosure may be provided in the server 103. Alternatively, the reconciliation method provided by the embodiments of the present disclosure may also be performed by a server or cluster of servers other than server 103 and capable of local communication with database 101 and/or server 103. Accordingly, the reconciliation device provided by the embodiments of the present disclosure may also be provided in a server or server cluster that is different from the server 103 and is capable of local communication with the database 101 and/or the transfer server 103. Alternatively, the reconciliation method provided by the embodiments of the present disclosure may be performed in part by the server 103 and in part by the database 101. Accordingly, the reconciliation device provided in the embodiments of the present disclosure may be partially disposed in the server 103 and partially disposed in the database 101.
It should be understood that the number of databases, networks, servers in fig. 1 is merely illustrative. There may be any number of databases, networks, servers, as desired for implementation.
The account checking method provided by the embodiment of the disclosure can be applied to the field of financial science and technology. For example, with increasing material culture demands, people demand loans increasingly. Therefore, more and more financial institutions develop credit businesses in which a perfect reconciliation mechanism is a key factor in ensuring proper operation of credit systems. However, the existing reconciliation mechanism mainly relies on batch reconciliation at night by a host computer, timeliness of the reconciliation cannot be met, and in the case of newly added reconciliation, repeated development exists.
It should be understood that the reconciliation method provided by the embodiments of the present disclosure is not limited to application in the field of financial science and technology, but may be applied to any field other than the financial field. The above description is merely exemplary, and the reconciliation method of the embodiments of the present disclosure may be applied to any field having reconciliation, such as e-commerce, logistics, and other technical fields.
The reconciliation method of the embodiments of the present disclosure will be described in detail below with reference to fig. 2 to 8, based on the context of fig. 1.
Fig. 2 schematically illustrates a flow chart of a reconciliation method in accordance with an embodiment of the disclosure.
As shown in fig. 2, the reconciliation method may include, for example, operations S201 through S204.
In operation S201, a reconciliation definition table and a reconciliation field attribute table are configured.
In operation S202, in response to the reconciliation start instruction, the reconciliation definition table and the reconciliation field attribute table are invoked to obtain a reconciliation data source, a reconciliation match field, and an attribute field of the reconciliation data source for the task to be reconciled.
In operation S203, a reconciliation job program corresponding to the task to be reconciled is generated from the reconciliation data source, the reconciliation match field, and the attribute field of the reconciliation data source for the task to be reconciled.
In operation S204, a reconciliation job procedure is performed to complete reconciliation of the target table and the source table in the task to be reconciled.
In the embodiment of the disclosure, definition configuration is performed by configuring a reconciliation definition table and a reconciliation field attribute table to complete definition of different business reconciliation requirements so as to support the reconciliation requirements related to single-table reconciliation and HQL (Hibernate Query Language) statement reconciliation.
The reconciliation definition table defines a data source and a reconciliation matching field of the reconciliation, and specifically includes a job number, a reconciliation name, table names of a reconciliation source table and a target table, a reconciliation date field, a reconciliation data source (support table and SQL statement), a reconciliation result saving type, and the like. The reconciliation field attribute table defines specific fields of the reconciliation data source, and specifically includes a source field name, a destination field name, a comparison result field alias, a field sequence number, whether a primary key field, a source field function parameter value, a destination field function parameter value, and the like.
In embodiments of the present disclosure, parameters of the reconciliation initiation instruction may include, for example, the number of reconciliation job tasks, the reconciliation job queue version, the partition field value, and the job number. The job number is used for matching with the job number configured in the reconciliation definition table, and relevant reconciliation data under the matched job number is obtained for reconciliation. The partition field value can be understood as a limiting condition of the data range, and when the partition field value is empty, the server time is taken, and the partition value date format is determined.
It should be understood that, related data of multiple sets of tasks to be checked can be configured in the checking definition table and the checking field attribute table at the same time, and can be distinguished and queried by using the job number as an index.
According to the embodiment of the disclosure, the reconciliation data source and the reconciliation matching field are recorded through the pre-configured reconciliation definition table, the attribute field of the reconciliation field attribute table discipline reconciliation data source is pre-configured, and when the reconciliation is needed, the reconciliation definition table and the reconciliation field attribute table are directly called to generate the reconciliation operation program for reconciliation, so that the access efficiency of reconciliation can be effectively improved, and the timeliness of reconciliation is improved. When the account is newly added, the account can be newly added only by configuring the corresponding data in the account checking definition table and the account checking field attribute, repeated development is not needed, the development cost is saved, and the account checking efficiency is improved. Because multiple sets of accounts can be configured in the account checking definition table and the account checking field attribute, corresponding account checking operation programs can be generated based on the account checking data sources, the account checking matching fields and the account checking data sources of different accounts, so that multiple sets of accounts can be accessed simultaneously, batch account checking can be realized more efficiently, and the reusability is high.
Fig. 3 schematically illustrates a flowchart of generating a reconciliation job program corresponding to a task to be reconciled in operation S203 in accordance with an embodiment of the disclosure.
As shown in fig. 3, generating a reconciliation job program corresponding to the to-be-reconciled task in operation S203 may include, for example, operation S301.
In operation S301, the reconciliation data source, the reconciliation matching field, and the attribute field of the reconciliation data source are spliced to generate an HQL query statement as a reconciliation job program.
In an embodiment of the disclosure, the reconciliation job program may be obtained by splicing HQL of the reconciliation definition configuration according to parameters in the reconciliation start instruction. And searching a reconciliation definition table and a reconciliation field attribute table according to the job number in the reconciliation starting instruction, and acquiring a reconciliation data source, a reconciliation matching field and an attribute field of the reconciliation data source of the to-be-reconciled task to perform HQL splicing to obtain an HQL query statement. For example, the job number of the job to be checked out is a, the check definition table and the check field attribute table may store the job number of the job to be checked out of 1, 2, 3, 4, and the check data source, the check matching field, and the attribute field of the check data source of the job number of 1 may be acquired from the check definition table and the check field attribute table. And according to the reconciliation data source with the job number of 1, the reconciliation matching field and the attribute field of the reconciliation data source, the HQL query statement of the to-be-reconciled task with the job number of 1 can be spliced.
According to the embodiment of the disclosure, the HQL query statement is generated as the reconciliation job program, and the HQL query statement is used for object-oriented encapsulation of query conditions and has rich and flexible query characteristics, so that the reconciliation information can be efficiently and accurately queried under the condition of being applied to batch reconciliation and simultaneous access of multiple sets of reconciliation, and efficient and accurate reconciliation is realized.
Fig. 4 schematically illustrates a flowchart of generating an HQL query statement in operation S301 according to an embodiment of the present disclosure.
As shown in fig. 4, generating the HQL query statement in operation S301 may include, for example, operation S401.
In operation S401, in the case where the number of one-side accounts in the source table is greater than the number of one-side accounts in the target table, the reconciliation data source, the reconciliation matching field, and the attribute field are spliced to generate the HQL query statement using the left connection condition of the primary key field of the source table and the primary key field of the target table and the drive table of the target table in the attribute field.
For example, the source table is denoted by a, the target table is denoted by B, and when the number of single-side accounts of the source table a is greater than the number of single-side accounts of the target table B, the HQL query statement is spliced by traversing the reconciliation definition table and the reconciliation field attribute table, and can be denoted as an HQL query statement of a-B, using the primary key field as a left connection condition:
select a. Source table field result field name.
from Source Table name a
left join target table name b on a. source table field (primary key) =b. target table field (primary key) and.
Source table date partition field = b target partition field
where b. target table field (primary key) is null
Source table date partition field = partition value.
Fig. 5 schematically illustrates a flowchart of generating an HQL query statement in operation S301 according to another embodiment of the present disclosure.
As shown in fig. 5, generating the HQL query statement in operation S301 may include, for example, operation S501.
In operation S501, in a case where the number of one-side accounts in the source table is smaller than the number of one-side accounts in the target table, the reconciliation data source, the reconciliation matching field, and the attribute field are spliced to generate the HQL query statement using the left connection condition of the primary key field of the source table and the primary key field of the target table in the attribute field and the source table as the drive table.
For example, the source table is denoted by ase:Sub>A, the target table is denoted by B, and when the number of single-side accounts of the source table ase:Sub>A is smaller than the number of single-side accounts of the target table B, the HQL query statement is spliced by traversing the reconciliation definition table and the reconciliation field attribute table, and can be denoted as the HQL query statement of B-ase:Sub>A, using the primary key field as the left connection condition:
select b.
from target table name b
left join source table name a on a source table field (primary key) =b target table field (primary key) and.
Source table date partition field = b target partition field
where a source list field (primary key) is null
Target table date partition field = partition value.
Fig. 6 schematically illustrates a flowchart of generating an HQL query statement in operation S301 according to yet another embodiment of the present disclosure.
As shown in fig. 6, generating the HQL query statement in operation S301 may include, for example, operation S601.
In operation S601, in case that the data of the source table and the target table are not identical, the reconciliation data source, the reconciliation matching field, and the attribute field are spliced to generate an HQL query statement using the primary key field of the source table and the primary key field of the target table in the attribute field as the interconnection condition.
For example, the source table is denoted by a, the target table is denoted by B, and when the number of single-side accounts of the source table a is smaller than the number of single-side accounts of the target table B, the HQL query statement is spliced by traversing the reconciliation definition table and the reconciliation field attribute table, and can be denoted as the HQL query statement of AB, and the primary key field is used as the connection condition:
select a. Source table field result field name.
b. Target table field b result field name.
from Source Table name a
Inner join target table name b on a. Source table field (Main Key) =b. Target table field (Main Key)
and.......
Source table date partition field = b target partition field
where a source table date partition field = partition value.
According to the embodiment of the disclosure, as the corresponding HQL query sentences are generated for checking the different data in the source table and the target table, the checking of different account conditions can be satisfied, and thus the flexibility and the efficiency of checking are improved.
Further, executing the reconciliation job program to complete the reconciliation of the target table and the source table in the task to be reconciled in operation S204 may comprise: and calling an application program interface of spark to execute the HQL query statement to finish the reconciliation of the target table and the source table in the task to be reconciled.
Spark can be understood as an open source clustered computing environment similar to Hadoop, but there are some differences between them that make Spark perform better in terms of some workloads, in other words, spark enables memory distribution datasets that optimize iterative workloads in addition to being able to provide interactive queries.
According to the embodiment of the disclosure, since spark can provide distributed query and can optimize the iterative workload, batch reconciliation can be better realized and the workload of the reconciliation device can be reduced by calling the application program interface of spark to execute the HQL query statement to complete the reconciliation.
Fig. 7 schematically illustrates a flow chart of a reconciliation method in accordance with another embodiment of the disclosure.
As shown in fig. 7, the reconciliation match field may also include a source type flag and a target type flag. The reconciliation method may also be operated, for example, from operation S701 to operation S703 before executing the reconciliation job procedure corresponding to the to-be-reconciled task according to the reconciliation data source, the reconciliation match field, and the attribute field of the reconciliation data source of the to-be-reconciled task of operation S203.
In operation S701, it is determined whether the source type flag and the target type flag are HQL statements.
In operation S702, in the case where the source type flag and the target type flag are not HQL statements, the reconciliation job program is generated directly based on the reconciliation definition table and the reconciliation field attribute table.
In operation S703, in the case where the source type flag and the target type flag are HQL statements, a view is created from the reconciliation definition table and the reconciliation field attribute table, and then a reconciliation job program is generated from the view.
For example, in the case where a temporary view needs to be created, a sentence may be used: hivecontext sql ("hql statement"), creatorrepoplaceTempView ("view name") creates a view and returns the view name.
According to the embodiment of the disclosure, since the source type mark and the target type mark are preconfigured to distinguish whether the HQL is supported or not, and different forms of generation of the reconciliation job program are adopted for the two allocations of supporting the HQL and not supporting the HQL, the reconciliation of different reconciliation scenes can be satisfied, and the flexibility of the reconciliation is further improved.
Fig. 8 schematically illustrates a flow chart of a reconciliation method in accordance with yet another embodiment of the disclosure.
As shown in fig. 8, the reconciliation method may further include operations S801 to S803, for example.
In operation S801, a reconciliation result obtained by executing the reconciliation job program is obtained.
In operation S802, the accounting result is analyzed to determine a difference record between the target table and the source table.
In operation S803, the difference records are spliced according to the attribute fields.
For example, the result set obtained by executing the above three HQL query sentences is analyzed:
in the case where the HQL query statement execution result of a-B is not null, the result set per row record may be, for example: 2-A single account is more.
In the case where the HQL query statement execution result of B-ase:Sub>A is not null, the result set per row record may be, for example: 3-B single side account is more.
Traversing the execution result of the HQL query sentence of the AB, and comparing the elements recorded in each row, wherein the comparison result can be as follows:
the elements are identical: 1-unifying;
element inconsistency: 4-element inconsistencies (AB all but with differences, which fields need to be described as different);
and if the HQL query statement execution result of A-B and the HQL query statement execution result of B-A are both null and no record with inconsistent elements exists in the HQL query statement execution result of AB, the total table of comparison results (reconciliation result table) is 1-consistent.
After the comparison result is obtained, the comparison result is stored in a result table (detail table). The difference records can be spliced according to the field sequence configured by the reconciliation field attribute table, the interval is used, when the record elements are inconsistent in all AB, only one record is saved, and the record A is stored in the result one field; b records are stored in a result two field; the element differences are stored in the diff value field.
After the comparison result is saved, the result file can be processed. The export of the comparison result can be configured to be completed by the processing operation, and the naming of the file can be as follows: the table name yyyymmdd. Txt of the reconciliation list may have the file content of: each line of data consists of field values of "reconciliation result detail table" spliced using char=27 intervals.
After the comparison result is finished, whether a task to be checked exists or not is also required to be judged, and if the task to be checked exists, the operation S202 is returned, the configuration data is read based on the job number of the current task to be checked, and the checking operation is continuously executed; in the case where there is no task to be reconciled, the reconciliation operation is ended.
According to the embodiment of the disclosure, since the difference records are spliced and stored based on the attribute fields, the subsequent backtracking of the difference accounting information can be facilitated.
In summary, the reconciliation method provided by the embodiments of the present disclosure supports multiple sets of reconciliation jobs with only one set of reconciliation logic through the configurable reconciliation device. The configured account checking definition table and account checking field attribute table support multiple sets of account checking access, and account checking scenes can be newly added only by configuring data of the two tables. Near zero-cost butt joint, the access efficiency is effectively improved, and the development cost is saved. And the independent concurrent scheduling of multiple jobs is supported, and efficient reconciliation can be carried out. In addition, the reconciliation method is low in maintenance cost and high in reusability.
Based on the reconciliation method shown in fig. 2 to 8, the embodiment of the disclosure further provides a reconciliation device, and the reconciliation device of the embodiment of the disclosure will be described below with reference to fig. 9 to 11 based on the scenario described in fig. 1.
Fig. 9 schematically illustrates a block diagram of a reconciliation apparatus in accordance with an embodiment of the disclosure.
As shown in fig. 9, reconciliation apparatus 900 may include a configuration module 910, a first acquisition module 920, a first generation module 930, and an execution module 940.
The configuration module 910 is configured to configure a reconciliation definition table and a reconciliation field attribute table, where the reconciliation definition table is used for recording a reconciliation data source and a reconciliation match field, and the reconciliation field attribute table is used for recording an attribute field of the reconciliation data source. The configuration module 910 may be configured to perform the operation S201 described above, which is not described herein.
The first obtaining module 920 is configured to, in response to the reconciliation start instruction, call the reconciliation definition table and the reconciliation field attribute table to obtain a reconciliation data source, a reconciliation match field, and an attribute field of the reconciliation data source for the reconciliation task. The obtaining module 920 may be configured to perform the operation S202 described above, which is not described herein.
The first generating module 930 is configured to generate a reconciliation job program corresponding to the to-be-reconciled task according to the reconciliation data source, the reconciliation matching field, and the attribute field of the reconciliation data source of the to-be-reconciled task. The generating module 930 may be configured to perform the operation S203 described above, which is not described herein.
And the execution module 940 is configured to execute a reconciliation job procedure to complete reconciliation of the target table and the source table in the task to be reconciled. The execution module 940 may be configured to execute the operation S204 described above, which is not described herein.
Fig. 10 schematically illustrates a block diagram of a reconciliation apparatus in accordance with another embodiment of the disclosure.
As shown in fig. 10, reconciliation apparatus 900 may further include a determination module 950, a second generation module 960, and a third generation module 970, for example.
The first determining module 950 is configured to determine whether the source type flag and the target type flag are HQL statements. The determining module 950 may be configured to perform the operation S701 described above, which is not described herein.
The second generation module 960 is configured to generate, directly based on the reconciliation definition table and the reconciliation field attribute table, a reconciliation job procedure if the source type flag and the target type flag are not HQL statements. The second generation module 960 may be used to perform the operation S702 described above, and will not be described herein.
A third generating module 970 is configured to create a view according to the reconciliation definition table and the reconciliation field attribute table, and generate a reconciliation job procedure according to the view when the source type flag and the target type flag are HQL statements. The third generating module 970 may be configured to perform the operation S703 described above, which is not described herein.
Fig. 11 schematically illustrates a block diagram of a reconciliation apparatus in accordance with another embodiment of the disclosure.
As shown in fig. 11, the reconciliation apparatus 900 may further include, for example, a second acquisition module 980, a second determination module 990, and a stitching module 9100.
A second obtaining module 980, configured to obtain a reconciliation result obtained by executing the reconciliation job procedure. The second acquisition module 980 may be configured to perform the operation S801 described above, which is not described herein.
A second determining module 990, configured to analyze the accounting result and determine a difference record between the target table and the source table. The second determining module 990 may be used to perform the operation S802 described above, which is not described herein.
And a splicing module 9100, configured to splice the difference records according to the attribute field. The splicing module 9100 may be used to perform operation S803 described above, and will not be described herein.
Any number of modules, sub-modules, units, sub-units, or at least some of the functionality of any number of the sub-units according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented as split into multiple modules. Any one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be implemented at least in part as a hardware circuit, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system-on-chip, a system-on-substrate, a system-on-package, an Application Specific Integrated Circuit (ASIC), or in any other reasonable manner of hardware or firmware that integrates or encapsulates the circuit, or in any one of or a suitable combination of three of software, hardware, and firmware. Alternatively, one or more of the modules, sub-modules, units, sub-units according to embodiments of the present disclosure may be at least partially implemented as computer program modules, which when executed, may perform the corresponding functions.
For example, any of the configuration module 910, the first acquisition module 920, the first generation module 930, the execution module 940, the determination module 950, the second generation module 960, the third generation module 970, the second acquisition module 980, the second determination module 990, and the stitching module 9100 may be combined in one module/unit/sub-unit or any of the modules/units/sub-units may be split into multiple modules/units/sub-units. Alternatively, at least some of the functionality of one or more of these modules/units/sub-units may be combined with at least some of the functionality of other modules/units/sub-units and implemented in one module/unit/sub-unit. According to embodiments of the present disclosure, at least one of the configuration module 910, the first acquisition module 920, the first generation module 930, the execution module 940, the determination module 950, the second generation module 960, the third generation module 970, the second acquisition module 980, the second determination module 990, and the stitching module 9100 may be implemented at least in part as hardware circuitry, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or any other reasonable manner of integrating or packaging a circuit, or any other hardware or firmware, or any one of or any suitable combination of three of software, hardware, and firmware. Alternatively, at least one of the configuration module 910, the first acquisition module 920, the first generation module 930, the execution module 940, the determination module 950, the second generation module 960, the third generation module 970, the second acquisition module 980, the second determination module 990, and the stitching module 9100 may be at least partially implemented as a computer program module, which, when executed, may perform the corresponding functions.
It should be noted that, the accounting device part in the embodiment of the present disclosure corresponds to the accounting method part in the embodiment of the present disclosure, and specific implementation details and technical effects thereof are the same, which are not described herein again.
Fig. 12 schematically shows a block diagram of an electronic device adapted to implement the method described above, according to an embodiment of the disclosure. The electronic device shown in fig. 12 is merely an example and should not be construed to limit the functionality and scope of use of the disclosed embodiments.
As shown in fig. 12, an electronic device 1200 according to an embodiment of the present disclosure includes a processor 1201, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 1202 or a program loaded from a storage section 1208 into a Random Access Memory (RAM) 1203. The processor 1201 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or an associated chipset and/or special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. Processor 1201 may also include on-board memory for caching purposes. The processor 1201 may include a single processing unit or multiple processing units for performing the different actions of the method flows according to embodiments of the disclosure.
In the RAM1203, various programs and data required for the operation of the electronic apparatus 1200 are stored. The processor 1201, the ROM1202, and the RAM1203 are connected to each other through a bus 1204. The processor 1201 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM1202 and/or RAM 1203. Note that the program may be stored in one or more memories other than the ROM1202 and the RAM 1203. The processor 1201 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in the one or more memories.
According to an embodiment of the disclosure, the electronic device 1200 may also include an input/output (I/O) interface 1205, the input/output (I/O) interface 1205 also being connected to the bus 1204. The electronic device 1200 may also include one or more of the following components connected to the I/O interface 1205: an input section 1206 including a keyboard, a mouse, and the like; an output portion 1207 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, a speaker, and the like; a storage section 1208 including a hard disk or the like; and a communication section 1209 including a network interface card such as a LAN card, a modem, or the like. The communication section 1209 performs communication processing via a network such as the internet. The drive 1210 is also connected to the I/O interface 1205 as needed. A removable medium 1211 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed as needed on the drive 1210 so that a computer program read out therefrom is installed into the storage section 1208 as needed.
According to embodiments of the present disclosure, the method flow according to embodiments of the present disclosure may be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program can be downloaded and installed from a network via the communication portion 1209, and/or installed from the removable media 1211. The above-described functions defined in the system of the embodiments of the present disclosure are performed when the computer program is executed by the processor 1201. The systems, devices, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.
The present disclosure also provides a computer-readable storage medium that may be embodied in the apparatus/device/system described in the above embodiments; or may exist alone without being assembled into the apparatus/device/system. The computer-readable storage medium carries one or more programs which, when executed, implement methods in accordance with embodiments of the present disclosure.
According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium. Examples may include, but are not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
For example, according to embodiments of the present disclosure, the computer-readable storage medium may include the ROM1202 and/or the RAM 1203 and/or one or more memories other than the ROM1202 and the RAM 1203 described above.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. Those skilled in the art will appreciate that the features recited in the various embodiments of the disclosure and/or in the claims may be combined in various combinations and/or combinations, even if such combinations or combinations are not explicitly recited in the disclosure. In particular, the features recited in the various embodiments of the present disclosure and/or the claims may be variously combined and/or combined without departing from the spirit and teachings of the present disclosure. All such combinations and/or combinations fall within the scope of the present disclosure.

Claims (13)

1. A reconciliation method comprising:
configuring a reconciliation definition table and a reconciliation field attribute table, wherein the reconciliation definition table is used for recording a reconciliation data source and a reconciliation matching field, and the reconciliation field attribute table is used for recording an attribute field of the reconciliation data source;
responding to a reconciliation starting instruction, and calling the reconciliation definition table and a reconciliation field attribute table to acquire a reconciliation data source, a reconciliation matching field and an attribute field of the reconciliation data source of a to-be-reconciled task;
generating a reconciliation job program corresponding to the to-be-reconciled task according to the reconciliation data source, the reconciliation matching field and the attribute field of the reconciliation data source of the to-be-reconciled task;
and executing the reconciliation job program to finish reconciliation of the target table and the source table in the task to be reconciled.
2. The reconciliation method of claim 1, wherein the generating a reconciliation job program corresponding to the to-be-reconciled task from the reconciliation data source, the reconciliation match field, and the attribute field of the reconciliation data source of the to-be-reconciled task comprises:
and splicing the reconciliation data source, the reconciliation matching field and the attribute field of the reconciliation data source to generate an HQL query statement as the reconciliation job program.
3. The reconciliation method of claim 2, wherein the concatenating the reconciliation data source, the reconciliation match field, and the attribute field of the reconciliation data source, generating an HQL query statement as the reconciliation job program comprises:
and under the condition that the number of the single-side accounts in the source table is larger than that of the single-side accounts in the target table, splicing the reconciliation data source, the reconciliation matching field and the attribute field to generate the HQL query statement by using a left connection condition of a primary key field of the source table and a primary key field of the target table in the attribute field and a driving table of the target table.
4. The reconciliation method of claim 2, wherein the concatenating the reconciliation data source, the reconciliation match field, and the attribute field of the reconciliation data source, generating an HQL query statement as the reconciliation job program further comprises:
and under the condition that the number of the single-side accounts in the source table is smaller than that of the single-side accounts in the target table, splicing the reconciliation data source, the reconciliation matching field and the attribute field to generate the HQL query statement by using a left connection condition of a primary key field of the source table and a primary key field of the target table in the attribute field and a driving table of the source table.
5. The reconciliation method of claim 2, wherein the concatenating the reconciliation data source, the reconciliation match field, and the attribute field of the reconciliation data source, generating an HQL query statement as the reconciliation job program further comprises:
and under the condition that the data of the source table and the data of the target table are inconsistent, splicing the reconciliation data source, the reconciliation matching field and the attribute field by using the primary key field of the source table and the primary key field of the target table in the attribute field as an interconnection condition to generate the HQL query statement.
6. The reconciliation method of any one of claims 2-5, wherein the executing the reconciliation job program to complete the reconciliation of the target table and the source table in the task to be reconciled comprises:
and calling an application program interface of spark to execute the HQL query statement to finish the reconciliation of the target table and the source table in the task to be reconciled.
7. The reconciliation method of any one of claims 1-5, the reconciliation match field comprising a source type flag and a target type flag; before generating the reconciliation job program corresponding to the to-be-reconciled task according to the reconciliation data source, the reconciliation matching field, and the attribute field of the reconciliation data source of the to-be-reconciled task, the method further comprises:
Determining whether the source type flag and the target type flag are HQL sentences;
under the condition that the source type mark and the target type mark are not HQL sentences, generating the reconciliation job program directly based on the reconciliation definition table and the reconciliation field attribute table;
and under the condition that the source type mark and the target type mark are HQL sentences, creating a view according to the reconciliation definition table and the reconciliation field attribute table, and generating the reconciliation job program according to the view.
8. The reconciliation method of claim 1, the method further comprising:
obtaining a reconciliation result obtained by executing the reconciliation job program;
analyzing the account checking result, and determining a difference record between the target table and the source table;
and splicing the difference records according to the attribute fields.
9. The reconciliation method of claim 1, wherein the reconciliation match field comprises a job number, a reconciliation name, a source table name, a target table name, and a reconciliation date field;
the attribute fields include source field names, destination field names, result field aliases, field sequence numbers, primary key fields, source field functions, source field function parameter values, destination field functions, destination field function parameter values.
10. A reconciliation apparatus comprising:
the configuration module is used for configuring a reconciliation definition table and a reconciliation field attribute table, wherein the reconciliation definition table is used for recording a reconciliation data source and a reconciliation matching field, and the reconciliation field attribute table is used for recording an attribute field of the reconciliation data source;
the first acquisition module is used for responding to the reconciliation starting instruction, calling the reconciliation definition table and the reconciliation field attribute table to acquire a reconciliation data source, a reconciliation matching field and an attribute field of the reconciliation data source of the to-be-reconciled task;
the first generation module is used for generating a reconciliation job program corresponding to the to-be-reconciled task according to the reconciliation data source, the reconciliation matching field and the attribute field of the reconciliation data source of the to-be-reconciled task;
and the execution module is used for executing the reconciliation job program to finish reconciliation of the target table and the source table in the task to be reconciled.
11. An electronic device, comprising:
one or more processors;
storage means for storing one or more programs,
wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method of any of claims 1-9.
12. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method according to any of claims 1 to 9.
13. A computer program product comprising a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 9.
CN202310868677.6A 2023-07-14 2023-07-14 Accounting method, device, equipment, medium and product Pending CN116860779A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310868677.6A CN116860779A (en) 2023-07-14 2023-07-14 Accounting method, device, equipment, medium and product

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310868677.6A CN116860779A (en) 2023-07-14 2023-07-14 Accounting method, device, equipment, medium and product

Publications (1)

Publication Number Publication Date
CN116860779A true CN116860779A (en) 2023-10-10

Family

ID=88233829

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310868677.6A Pending CN116860779A (en) 2023-07-14 2023-07-14 Accounting method, device, equipment, medium and product

Country Status (1)

Country Link
CN (1) CN116860779A (en)

Similar Documents

Publication Publication Date Title
US10120930B2 (en) Identifying entity mappings across data assets
US20230401187A1 (en) Method and system for migrating content between enterprise content management systems
US8515898B2 (en) Column based data transfer in extract transform and load (ETL) systems
US11455410B2 (en) Data privacy pipeline providing collaborative intelligence and constraint computing
US10291704B2 (en) Networked solutions integration using a cloud business object broker
US11403299B2 (en) Constraint manager for collaborative intelligence and constraint computing
US8630969B2 (en) Systems and methods for implementing business rules designed with cloud computing
US11409897B2 (en) Constraint querying for collaborative intelligence and constraint computing
US11106820B2 (en) Data anonymization
CN111917587B (en) Method for network service management by using service system and service system
CN111427971B (en) Business modeling method, device, system and medium for computer system
CN110716714B (en) Component creation method, device, computer system and computer readable storage medium
US11755457B2 (en) Selective tracking of requests through enterprise systems by multiple vendors with a single tracking token scheme
CN114281803A (en) Data migration method, device, equipment, medium and program product
CN111177089B (en) Log processing code generation method and device, computer system and storage medium
CN114640614B (en) RPC interface automatic test method, system, electronic equipment, medium and product
CN116860779A (en) Accounting method, device, equipment, medium and product
CN115757356A (en) Data migration method, device, system, electronic equipment and storage medium
CN114677114A (en) Approval process generation method and device based on graph dragging
US9542246B2 (en) Sharing a partitioned data set across parallel applications
Ramuka Data analytics with Google Cloud platform
CN113392002A (en) Test system construction method, device, equipment and storage medium
US11573960B2 (en) Application-based query transformations
CN115484149B (en) Network switching method, network switching device, electronic equipment and storage medium
US20230153457A1 (en) Privacy data management in distributed computing systems

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination