A method, device and medium for implementing a cross-system push information interface

Abstract

The embodiment of the present application discloses a method, device and medium for implementing a cross-system information push interface. The method comprises the following steps: obtaining a preset dynamic link library file corresponding to a data transmission end system; determining the data to be pushed in the preset dynamic link library file, and generating a data configuration table based on an SQL statement and the data to be pushed; wherein the data configuration table is used to configure the push of the current push task; creating a corresponding business table structure in the data receiving end system based on the type of the data to be pushed; regularly pushing the data to be pushed to the data receiving end system through a preset ESB interface and data configuration table; calling a preset integration tool of the data receiving end system, and synchronizing the received data to be pushed to the business table structure through the preset integration tool to complete the cross-system information push. The above method improves the efficiency of cross-system information push.

Description

Technical Field

[0001] The present application relates to the field of computer application technology, and in particular to a method, device, and medium for implementing a cross-system push information interface. Background Art

[0002] As the scale of major enterprises continues to expand and the business volume grows increasingly rapidly, the business processes of enterprises are becoming more and more complex, and the need for cross-system docking is increasing.

[0003] Especially for large group enterprises, taking financial sharing as an example, many enterprises need to separate business and financial accounting. After completing the document process of the financial sharing system, business personnel hope to continue to process financial accounting for business documents in the accounting system in real time, and approval personnel also need to quickly obtain feedback on changes in document status.

[0004] However, the manual batch acquisition of business data in the existing technology makes the data docking cycle longer, resulting in the corresponding business requests being unable to obtain processing results for a long time, thereby reducing the efficiency of cross-system docking business. Summary of the Invention

[0005] The embodiments of the present application provide a method, device and medium for implementing a cross-system information push interface, which is used to solve the following technical problems: the manual batch acquisition method of business data in existing technologies makes the data docking cycle longer, resulting in the corresponding business requests being unable to obtain processing results for a long time, thereby making the efficiency of cross-system docking business low.

[0006] The embodiments of this application adopt the following technical solutions:

[0007] The present application provides an implementation method for a cross-system information push interface, comprising: obtaining a preset dynamic link library file corresponding to a data transmission end system; determining the data to be pushed in the preset dynamic link library file, and generating a data configuration table based on a SQL statement and the data to be pushed; wherein the data configuration table is used to configure the push of the current push task; based on the type of the data to be pushed, creating a corresponding business table structure in the data receiving end system; regularly pushing the data to be pushed to the data receiving end system through a preset ESB interface and the data configuration table; calling a preset integration tool of the data receiving end system, and synchronizing the received data to be pushed to the business table structure through the preset integration tool to complete the cross-system information push.

[0008] By configuring the SQL statements to be executed at each stage, the embodiment of the present application intuitively understands the events in the interface synchronization process, clearly controls the synchronization progress of the data, and explicitly tracks the flow of data in the interface, enabling developers and implementers to efficiently and agilely develop and maintain a new data interface. The embodiment of the present application pre-sets the ESB interface and the data configuration table to regularly push the data to be pushed to the data receiving end system, enabling the push of different types of data. The interface code does not need to be repeatedly developed, and the existing files can be directly deployed, making cross-system message push simpler and clearer, and improving the efficiency of cross-system message push.

[0009] In one implementation of the present application, the data configuration table includes at least one of an internal code, an interface name, a start statement, a data query statement, an end statement, a USB interface address, a business interface service, and an integration tool mapping model number.

[0010] In one implementation of the present application, after obtaining the preset dynamic link library file corresponding to the data transmission end system, the method also includes: obtaining the pushed historical data, establishing a data synchronization table based on the historical data; and detecting the pushed data based on the data synchronization table.

[0011] In one implementation of the present application, historical data that has been pushed is obtained, and a data synchronization table is established based on the historical data, specifically including: obtaining all historical data that has been pushed, and building all data synchronization tables based on all historical data; and obtaining data that has been pushed within a preset time period, and building an incremental data synchronization table based on the data that has been pushed within the preset time period; and obtaining detailed documents corresponding to the pushed data, and building a detailed data synchronization table based on the detailed documents.

[0012] In one implementation of the present application, the pushed data is detected based on the data synchronization table, specifically including: comparing all data synchronization tables with the detailed data synchronization table; and comparing the incremental data synchronization table with the detailed data synchronization table; if the comparison results are consistent, it is determined that the pushed data is correct.

[0013] In one implementation of the present application, the data to be pushed is pushed to the data receiving end system at a regular interval through a preset ESB interface and a data configuration table, specifically including: creating an assembly method component corresponding to a preset dynamic link library file; and creating a single task corresponding to the assembly method component; when the single task is executed, the data to be pushed is pushed to the data receiving end system through the preset ESB interface and the data configuration table.

[0014] In one implementation of the present application, a preset integration tool of the data receiving end system is called, and the received data to be pushed is synchronized to the business table structure through the preset integration tool to complete the cross-system push of information, specifically including: configuring the field mapping of the integration tool to parse the push data sent by the data transmission end system; synchronizing the parsed data to the business table structure, and storing the parsed data in the database to complete the cross-system push of information.

[0015] In one implementation of the present application, after obtaining the preset dynamic link library file corresponding to the data transmission end system, the method also includes: constructing a first voucher information table in the data transmission end system; and constructing a second voucher information table in the data receiving end system; wherein the first voucher information table and the second voucher information table respectively include at least one of the internal code, voucher code, voucher internal code and voucher year.

[0016] An embodiment of the present application provides an implementation device for a cross-system information push interface, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so as to enable the at least one processor to: obtain a preset dynamic link library file corresponding to a data transmission end system; determine data to be pushed in the preset dynamic link library file, and generate a data configuration table based on an SQL statement and the data to be pushed; wherein the data configuration table is used to push configuration for a current push task; based on the type of data to be pushed, create a corresponding business table structure in a data receiving end system; push the data to be pushed to the data receiving end system at regular intervals through a preset ESB interface and a data configuration table; call a preset integration tool of the data receiving end system, and synchronize the received data to be pushed to the business table structure through the preset integration tool to complete the cross-system information push.

[0017] A non-volatile computer storage medium provided by an embodiment of the present application stores computer-executable instructions, wherein the computer-executable instructions are configured to: obtain a preset dynamic link library file corresponding to a data transmission end system; determine data to be pushed in the preset dynamic link library file, and generate a data configuration table based on a SQL statement and the data to be pushed; wherein the data configuration table is used to push configuration for a current push task; based on the type of data to be pushed, create a corresponding business table structure in a data receiving end system; push the data to be pushed to the data receiving end system at regular intervals through a preset ESB interface and the data configuration table; call a preset integration tool of the data receiving end system, and synchronize the received data to be pushed to the business table structure through the preset integration tool to complete cross-system information push.

[0018] At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects: By configuring the SQL statements to be executed at each stage, the embodiments of the present application can intuitively understand the events in the interface synchronization process, clearly control the progress of data synchronization, and clearly track the flow of data in the interface, so that developers and implementers can efficiently and agilely implement the development and maintenance of a new data interface. The embodiments of the present application pre-set the ESB interface and data configuration table to regularly push the data to be pushed to the data receiving end system, which can realize the push of different types of data. The interface code does not need to be repeatedly developed, and the existing files can be directly deployed, making cross-system message push simpler and clearer, and improving the efficiency of cross-system message push. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments described in the present application. For those skilled in the art, other drawings can be obtained based on these drawings without inventive work. In the drawings:

[0020] Figure 1 A flowchart of a method for implementing a cross-system push information interface provided in an embodiment of the present application;

[0021] Figure 2 A schematic diagram of the structure of a device for implementing a cross-system push information interface provided in an embodiment of the present application. DETAILED DESCRIPTION

[0022] The embodiments of the present application provide a method, device, and medium for implementing a cross-system push information interface.

[0023] In order to enable those skilled in the art to better understand the technical solutions in this application, the following will clearly and completely describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.

[0024] As the scale of major enterprises continues to expand and the business volume grows increasingly rapidly, the business processes of enterprises are becoming more and more complex, and the need for cross-system docking is increasing.

[0025] Especially for large group enterprises, taking financial sharing as an example, many enterprises need to separate business and financial accounting. After completing the document process of the financial sharing system, business personnel hope to continue to process financial accounting for business documents in the accounting system in real time, and approval personnel also need to quickly obtain feedback on changes in document status.

[0026] However, the manual batch acquisition of business data in the existing technology makes the data docking cycle longer, resulting in the corresponding business requests being unable to obtain processing results for a long time, thereby reducing the efficiency of cross-system docking business.

[0027] In order to solve the above problems, the embodiments of the present application provide a method, device and medium for implementing a cross-system push information interface. By configuring the SQL statements to be executed at each stage, the events in the interface synchronization process can be intuitively understood, the synchronization progress of the data can be clearly controlled, and the flow of data in the interface can be clearly tracked, so that developers and implementers can efficiently and agilely implement the development and maintenance of a new data interface. The embodiments of the present application pre-set the ESB interface and the data configuration table to regularly push the data to be pushed to the data receiving end system, which can realize the pushing of different types of data. The interface code does not need to be repeatedly developed, and the existing files can be directly deployed, making cross-system message push more simple and clear, and improving the efficiency of cross-system message push.

[0028] The technical solutions proposed in the embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0029] Figure 1 This is a flow chart of a method for implementing a cross-system push information interface provided in an embodiment of the present application. Figure 1 As shown, the implementation method of the cross-system push information interface includes the following steps:

[0030] S101: Obtain a preset dynamic link library file corresponding to the data transmission end system.

[0031] In one embodiment of the present application, a data transmission end system deploys a pre-prepared dynamic link library file according to demand. The deployed dynamic link library file can be used to obtain and push information that needs to be pushed across systems.

[0032] S102: Determine the data to be pushed in the preset dynamic link library file, and generate a data configuration table based on the SQL statement and the data to be pushed; wherein the data configuration table is used to perform push configuration for the current push task.

[0033] In one embodiment of this application, the information to be pushed is organized into SQL statements through configuration, which are then deployed and executed on both the data transmission and data reception ends. Developers can develop and maintain a new interface by configuring the SQL statements for pushing data, achieving agile and efficient development. This configuration method stores information about data synchronization progress in a table, allowing users to maintain the interface by retrieving push records, making troubleshooting easier and clearer.

[0034] In one embodiment of the present application, during the cross-system data push process, the pushed historical data is obtained, a data synchronization table is established based on the historical data, and the pushed data is detected based on the data synchronization table.

[0035] Specifically, all pushed historical data is obtained and a full data synchronization table is constructed based on all historical data. Furthermore, data pushed within a preset time period is obtained and an incremental data synchronization table is constructed based on the data pushed within the preset time period. Furthermore, detailed documents corresponding to the pushed data are obtained and a detailed data synchronization table is constructed based on the detailed documents.

[0036] Specifically, all data synchronization tables established in the embodiment of the present application include at least field numbers, field names, and field types. All data synchronization tables are used to record all data that has been pushed. The incremental data synchronization tables established in the embodiment of the present application include at least field numbers, field names, and field types. The incremental data synchronization tables are used to record data that has been pushed within a preset time period. For example, data that has been successfully pushed within an hour can be recorded, and data that has been successfully pushed within a day can also be recorded.

[0037] Furthermore, the detailed data synchronization table established in the embodiment of the present application includes at least the field number, field name, and field type. Through this detailed data synchronization table, the sub-form information corresponding to the pushed data can be recorded. Different data corresponds to a main form and a sub-form respectively. The detailed data synchronization table can record the detailed data corresponding to the sub-form, thereby recording the pushed data in more detail. By searching the push record maintenance interface, troubleshooting is simpler and clearer.

[0038] Specifically, the all data synchronization table is compared with the detailed data synchronization table; and the incremental data synchronization table is compared with the detailed data synchronization table. If the comparison results are consistent, it is determined that the pushed data is correct.

[0039] Furthermore, when checking pushed data, the data in the All Data Synchronization Table can be compared with the data in the Detailed Data Synchronization Table. If a mismatch is detected between the data in the Detailed Data Synchronization Table and the All Data Synchronization Table, the mismatched data can be identified as suspected erroneous data. Furthermore, the data in the Incremental Data Synchronization Table can be compared with the data in the Detailed Data Synchronization Table. If a mismatch is detected between the data in the Detailed Data Synchronization Table and the Incremental Data Synchronization Table, the mismatched data can be identified as suspected erroneous data.

[0040] Furthermore, the pushed data is checked based on the determined suspected erroneous data to determine the erroneous pushed data.

[0041] Furthermore, when the data in all data synchronization tables is consistent with the data in the detailed data synchronization table, and the data in the incremental data synchronization table is consistent with the data in the detailed data synchronization table, it is determined that the pushed data is correct data.

[0042] In one embodiment of the present application, the data configuration table includes at least one of the data to be pushed, interface name, start statement, data query statement, end statement, USB interface address, business interface service and integration tool mapping model number.

[0043] Specifically, Table 1 is a data configuration table provided in an embodiment of the present application. As shown in Table 1, the data configuration table includes at least field numbers, field names, and field types. The field names include at least internal code, interface name, start statement, data query statement, end statement, USB interface address, business interface service, sender, last interface return number, last interface return data, and integration tool mapping model number:

[0044]

[0045] Table 1

[0046] S103: Based on the type of data to be pushed, a corresponding business table structure is created in the data receiving end system.

[0047] In one embodiment of the present application, the data receiving end system creates a table structure identical to the document pushed by the data transmission end system. For example, if the data transmission end system sends a financial table, the data receiving end system creates a table structure corresponding to the financial table.

[0048] S104: Push the data to be pushed to the data receiving end system at regular intervals through the preset ESB interface and data configuration table.

[0049] In one embodiment of the present application, an assembly method component corresponding to a preset dynamic link library file is created; and a single task corresponding to the assembly method component is created. When the single task is executed, the data to be pushed is pushed to the data receiving end system through the preset ESB interface and data configuration table.

[0050] Specifically, an assembly method component corresponding to the dynamic link library file is created, and a single task is created. Executing the task pushes data to the receiving system. Data transmission utilizes the company's internal ESB interface and Web Services, ensuring secure data transmission.

[0051] S105: Call the preset integration tool of the data receiving end system, and synchronize the received data to be pushed to the business table structure through the preset integration tool to complete the cross-system information push.

[0052] In one embodiment of the present application, the field mapping of the integration tool is configured to parse the push data sent by the data transmission end system, synchronize the parsed data to the business table structure, and store the parsed data in the database to complete the cross-system information push.

[0053] Specifically, configure the field mapping of the integration tool, parse the data pushed by the data transmission end system, fill the parsed data into the corresponding business table structure, and the data receiving end system can obtain the corresponding push information and store the obtained push information in the database.

[0054] In one embodiment of the present application, a first voucher information table is constructed on the data transmission end system, and a second voucher information table is constructed on the data receiving end system. The first voucher information table and the second voucher information table each include at least one of the following: an internal code, a voucher code, a voucher internal code, and a voucher year.

[0055] Specifically, the embodiment of the present application constructs a first voucher information table in the data transmission end system, and the first voucher information table is provided with field numbers, field names, and field types. Among them, the field names include at least information such as the internal code, voucher code, voucher internal code, and certification year. Through the first voucher information, it is used to store voucher records for the data in the data input end system. The embodiment of the present application constructs a second voucher information table in the data transmission end system, and the second voucher information table is provided with field numbers, field names, and field types. Among them, the field names include at least information such as the internal code, voucher code, voucher internal code, and certification year. Through the second voucher information, it is used to store voucher records for the data in the data output end system.

[0056] By configuring the SQL statements to be executed at each stage, the embodiment of the present application intuitively understands the events in the interface synchronization process, clearly controls the synchronization progress of the data, and explicitly tracks the flow of data in the interface, so that developers and implementers can efficiently and agilely develop and maintain a new data interface. The embodiment of the present application pre-sets the ESB interface and the data configuration table to regularly push the data to be pushed to the data receiving end system, which can push different types of data. The interface code does not need to be repeatedly developed, and the existing files can be directly deployed, making cross-system message push simpler and clearer, and improving the efficiency of cross-system message push.

[0057] Figure 2 This is a schematic diagram of a device for implementing a cross-system push information interface provided in an embodiment of the present application. Figure 2 As shown, the implementation device of the cross-system push information interface includes:

[0058] at least one processor; and,

[0059] a memory communicatively connected to the at least one processor; wherein,

[0060] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

[0061] Obtain the preset dynamic link library file corresponding to the data transmission end system;

[0062] Determine the data to be pushed in the preset dynamic link library file, and generate a data configuration table based on the SQL statement and the data to be pushed; wherein the data configuration table is used to push configuration for the current push task;

[0063] Based on the type of the data to be pushed, a corresponding business table structure is created in the data receiving end system;

[0064] Pushing the data to be pushed to the data receiving end system regularly through the preset ESB interface and the data configuration table;

[0065] The preset integration tool of the data receiving end system is called, and the received data to be pushed is synchronized to the business table structure through the preset integration tool to complete the cross-system information push.

[0066] An embodiment of the present application also provides a non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured to: obtain a preset dynamic link library file corresponding to a data transmission end system; determine the data to be pushed in the preset dynamic link library file, and generate a data configuration table based on a SQL statement and the data to be pushed; wherein the data configuration table is used to push configuration for the current push task; based on the type of the data to be pushed, create a corresponding business table structure in the data receiving end system; regularly push the data to be pushed to the data receiving end system through a preset ESB interface and the data configuration table; call a preset integration tool of the data receiving end system, and synchronize the received data to be pushed to the business table structure through the preset integration tool to complete the cross-system information push.

[0067] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems, or computer program products. Therefore, the embodiments of this specification may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the embodiments of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0068] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0069] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0070] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0071] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0072] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0073] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0074] The various embodiments in this application are described in a progressive manner. Similar portions between the various embodiments can be referenced to each other, and each embodiment focuses on the differences from the other embodiments. In particular, the device, apparatus, and non-volatile computer storage medium embodiments are generally similar to the method embodiments, so their descriptions are relatively simple. For relevant portions, refer to the descriptions of the method embodiments.

[0075] The foregoing is merely an embodiment of the present application and is not intended to limit the present application. It will be apparent to those skilled in the art that various modifications and variations may be made to the embodiments of the present application. However, such modifications or substitutions do not deviate from the spirit and scope of the technical solutions of the various embodiments of the present application.

Claims

1. A method for implementing a cross-system push information interface, characterized in that: The method comprises: Obtain the preset dynamic link library file corresponding to the data transmission end system; Determine the data to be pushed in the preset dynamic link library file, and generate a data configuration table based on the SQL statement and the data to be pushed; wherein the data configuration table is used to push configuration for the current push task; Based on the type of the data to be pushed, a corresponding business table structure is created in the data receiving end system; Pushing the data to be pushed to the data receiving end system regularly through the preset ESB interface and the data configuration table; Calling a preset integration tool of the data receiving end system, and synchronizing the received data to be pushed to the business table structure through the preset integration tool to complete cross-system information push; The method of regularly pushing the data to be pushed to the data receiving end system through the preset ESB interface and the data configuration table specifically includes: Creating an assembly method component corresponding to the preset dynamic link library file; and Creating a single task corresponding to the assembly method component; When the single task is executed, the data to be pushed is pushed to the data receiving end system through the preset ESB interface and the data configuration table.

2. A method for implementing a cross-system push information interface according to claim 1, characterized in that: The data configuration table includes at least one of an internal code, an interface name, a start statement, a data query statement, an end statement, a USB interface address, a business interface service, and an integration tool mapping model number.

3. The method for implementing a cross-system push information interface according to claim 1, characterized in that: After obtaining the preset dynamic link library file corresponding to the data transmission end system, the method further includes: Acquire the pushed historical data and create a data synchronization table based on the historical data; The pushed data is detected based on the data synchronization table.

4. A method for implementing a cross-system push information interface according to claim 3, characterized in that: The acquiring of pushed historical data and establishing a data synchronization table based on the historical data specifically includes: Obtaining all pushed historical data and building all data synchronization tables based on all the historical data; and Acquire the data pushed within a preset time period, and construct an incremental data synchronization table based on the data pushed within the preset time period; and Obtain the detailed documents corresponding to the pushed data, and build a detailed data synchronization table based on the detailed documents.

5. A method for implementing a cross-system push information interface according to claim 4, characterized in that: The detecting of the pushed data based on the data synchronization table specifically includes: Comparing the all data synchronization table with the detailed data synchronization table; and Comparing the incremental data synchronization table with the detailed data synchronization table; If the comparison results are consistent, it is determined that the pushed data is correct.

6. A method for implementing a cross-system push information interface according to claim 1, characterized in that: The calling of the preset integration tool of the data receiving end system and synchronizing the received data to be pushed to the business table structure through the preset integration tool to complete the cross-system information push specifically includes: Configuring field mapping of the integration tool to parse the push data sent by the data transmission end system; The parsed data is synchronized to the business table structure, and the parsed data is stored in the database to complete the cross-system push of information.

7. The method for implementing a cross-system push information interface according to claim 1, characterized in that: After obtaining the preset dynamic link library file corresponding to the data transmission end system, the method further includes: Constructing a first credential information table in the data transmission end system; and Constructing a second credential information table in the data receiving end system; The first voucher information table and the second voucher information table respectively include at least one of the internal code, voucher code, voucher internal code and voucher year.

8. A device for implementing a cross-system push information interface, comprising: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to: Obtain the preset dynamic link library file corresponding to the data transmission end system; Determine the data to be pushed in the preset dynamic link library file, and generate a data configuration table based on the SQL statement and the data to be pushed; wherein the data configuration table is used to push configuration for the current push task; Based on the type of the data to be pushed, a corresponding business table structure is created in the data receiving end system; Pushing the data to be pushed to the data receiving end system regularly through the preset ESB interface and the data configuration table; Calling a preset integration tool of the data receiving end system, and synchronizing the received data to be pushed to the business table structure through the preset integration tool to complete cross-system information push; The method of regularly pushing the data to be pushed to the data receiving end system through the preset ESB interface and the data configuration table specifically includes: Creating an assembly method component corresponding to the preset dynamic link library file; and Creating a single task corresponding to the assembly method component; When the single task is executed, the data to be pushed is pushed to the data receiving end system through the preset ESB interface and the data configuration table.

9. A non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured to: Obtain the preset dynamic link library file corresponding to the data transmission end system; Determine the data to be pushed in the preset dynamic link library file, and generate a data configuration table based on the SQL statement and the data to be pushed; wherein, The data configuration table is used to push configuration for the current push task; Based on the type of the data to be pushed, a corresponding business table structure is created in the data receiving end system; Pushing the data to be pushed to the data receiving end system regularly through the preset ESB interface and the data configuration table; Calling a preset integration tool of the data receiving end system, and synchronizing the received data to be pushed to the business table structure through the preset integration tool to complete cross-system information push; The method of regularly pushing the data to be pushed to the data receiving end system through the preset ESB interface and the data configuration table specifically includes: Creating an assembly method component corresponding to the preset dynamic link library file; and Creating a single task corresponding to the assembly method component; When the single task is executed, the data to be pushed is pushed to the data receiving end system through the preset ESB interface and the data configuration table.

Images