CN117312433A - Method, device and system for transmitting service data based on direct connection port - Google Patents

Abstract

The invention discloses a business data transmission method, a device and a system based on a direct connection port, wherein the method is suitable for a data processing system integrated with a plurality of direct connection ports, and comprises the following steps: respectively acquiring interface data collected by each direct connection port, wherein the interface data are data input by an external system connected with the direct connection port; after the interface data are stored, carrying out service processing on the interface data by using an interface batch tool according to service logic of an external system corresponding to each interface data to obtain service data; and when the callback state of the direct connection port is not callback, callback the service data to a corresponding external system for the external system to call. The invention can integrate a plurality of direct connection ports connected with the external system, and carry out multi-thread communication connection with the external system by operating the plurality of integrated direct connection ports, thereby shortening the communication delay, improving the transmission efficiency and improving the stability of data transmission.

Description

A business data transmission method, device and system based on direct connection interface

Technical field

The present invention relates to the technical field of business data transmission, and in particular, to a business data transmission method, device and system based on a direct connection interface.

Background technique

With the development of science and technology, more and more enterprises have set up or built corresponding data processing systems (such as SAP ECC system). Through the data processing system, various basic data and business data are transmitted to the systems of various companies or enterprises to realize the interaction of online business and information.

In order to realize data interaction among multiple systems, most of the commonly used communication methods between data processing systems and various systems are to transmit data through asynchronous middleware such as kettle, sterling, and FTP. However, the currently commonly used methods have the following technical problems: Since the data processing system communicates asynchronously with each external system, each time data is transmitted, the timeliness is poor and the delay is long; The data transmission interfaces are different, resulting in low stability of data transmission, high failure rate, and easy data loss. Data often needs to be retransmitted after loss, further reducing the efficiency of data transmission and data processing.

Contents of the invention

The present invention proposes a business data transmission method, device and system based on direct connection interfaces. The data processing system of the method integrates multiple direct connection interfaces connected to external systems. By running multiple integrated direct connection interfaces and multiple Multi-threaded communication connections with an external system can not only shorten communication delays and improve transmission efficiency, but also improve the stability of data transmission.

The first aspect of the embodiment of the present invention provides a business data transmission method based on a direct connection interface. The method is suitable for a data processing system integrating multiple direct connection interfaces. The method includes:

Obtain the interface data collected by each direct connection interface respectively, where the interface data is data input by the external system connected to the direct connection interface;

After saving the interface data, use an interface batch tool to perform business processing on the interface data according to the business logic of the external system corresponding to each interface data to obtain business data;

When the callback status of the direct interface is not called back, the business data is called back to the corresponding external system for calling by the external system.

In a possible implementation of the first aspect, the data processing system is provided with: a data interface header object, a data interface processor, a superclass data interface processor, and a data interface factory;

The data interface factory, the superclass data interface processor, the data interface processor and the data interface header object are connected in sequence, the data interface factory is connected to a direct connection interface or an enhancement point, and the direct connection interface is connected to External system connection, the enhancement point is connected to the process node of the data processing system.

In a possible implementation of the first aspect, obtaining the interface data collected by each direct connection interface separately includes:

When the data interface factory receives the first instance acquisition request of the direct connection interface, the data interface factory is controlled to return the first super class instance data of the super class data interface processor to the direct connection interface, so that the direct connection interface The connection port sends interface data to the super-class data interface processor, wherein the first instance acquisition request is a request generated when an external system calls each direct connection port to transmit data or a request generated by triggering the enhancement point;

The data interface processor is used to transmit interface data received by the superclass data interface processor to the data interface header object.

In a possible implementation of the first aspect, saving the interface data includes:

The data interface processor calls the superclass data interface processor to obtain the next data interface number of the data interface header object;

Create an object instance in the data interface header object according to the data interface number, so that the data interface header object can use the object instance to save the data of the next transmission object;

The data interface number is used to save the interface data into the data table of the data interface object.

In a possible implementation of the first aspect, the interface batch tool is used to perform business processing on the interface data according to the business logic of the external system corresponding to each interface data to obtain business data, including:

When it is determined that there are multiple interface data that meet the processing conditions, use the interface batch tool to create a batch processing instance based on the business logic of the external system, and split the interface data according to the number of threads of the processing instance;

After the split is completed, the control interface batch tool sends a first instance acquisition request to the data interface factory, so that the interface batch tool obtains the second super class instance data of the super class data interface processor;

The interface batch tool sends the processing instance and the split interface data to the super-class data interface processor, so that the super-class data interface processor batch-processes the split interface data to obtain business data.

In a possible implementation of the first aspect, the super-class data interface processor performs batch processing on the split interface data to obtain business data, including:

Utilize the multi-thread processing method of the super-class data interface processor to filter the split interface data according to the status of the data interface processor to obtain filtered data;

The data interface processor is called to perform business processing on the filtered data in batches according to the business logic corresponding to the data interface object to obtain business data.

In a possible implementation of the first aspect, calling back the business data to the corresponding external system includes:

After using the data interface processor to receive a callback request from the callback interface of the external system, the data interface processor is controlled to receive business data from the data interface object and transmit the business data to the callback interface of the external system.

In a possible implementation of the first aspect, the data processing system is further provided with a data interface monitoring station, and the method further includes:

Use the data interface monitoring station to search and display the data interface header data that meets the query conditions according to the query conditions input by the user;

When the user's query request is obtained, the corresponding interface data report is searched from the data interface object according to the query request and displayed. The query request is a request input by the user after viewing the data interface header data.

A second aspect of the embodiment of the present invention provides a business data transmission device based on a direct connection interface. The device is suitable for a data processing system integrating multiple direct connection interfaces. The device includes:

A data acquisition module, configured to obtain interface data collected by each direct connection interface respectively, where the interface data is data input by an external system connected to the direct connection interface;

A business processing module, after saving the interface data, using an interface batch tool to perform business processing on the interface data according to the business logic of the external system corresponding to each of the interface data to obtain business data;

A callback processing module, configured to call back the business data to the corresponding external system for calling by the external system when the callback status of the direct interface is not called back.

In a possible implementation of the second aspect, the data processing system is provided with: a data interface header object, a data interface processor, a superclass data interface processor, and a data interface factory;

The data interface factory, the superclass data interface processor, the data interface processor and the data interface header object are connected in sequence, the data interface factory is connected to a direct connection interface or an enhancement point, and the direct connection interface is connected to External system connection, the enhancement point is connected to the process node of the data processing system.

In a possible implementation of the second aspect, obtaining the interface data collected by each direct connection interface separately includes:

When the data interface factory receives the first instance acquisition request of the direct connection interface, the data interface factory is controlled to return the first super class instance data of the super class data interface processor to the direct connection interface, so that the direct connection interface The connection port sends interface data to the super-class data interface processor, wherein the first instance acquisition request is a request generated when an external system calls each direct connection port to transmit data or a request generated by triggering the enhancement point;

The data interface processor is used to transmit interface data received by the superclass data interface processor to the data interface header object.

In a possible implementation of the second aspect, saving the interface data includes:

The data interface processor calls the superclass data interface processor to obtain the next data interface number of the data interface header object;

Create an object instance in the data interface header object according to the data interface number, so that the data interface header object can use the object instance to save the data of the next transmission object;

The data interface number is used to save the interface data into the data table of the data interface object.

In a possible implementation of the second aspect, the interface batch tool is used to perform business processing on the interface data according to the business logic of the external system corresponding to each interface data to obtain business data, including:

When it is determined that there are multiple interface data that meet the processing conditions, use the interface batch tool to create a batch processing instance based on the business logic of the external system, and split the interface data according to the number of threads of the processing instance;

After the split is completed, the control interface batch tool sends a first instance acquisition request to the data interface factory, so that the interface batch tool obtains the second super class instance data of the super class data interface processor;

The interface batch tool sends the processing instance and the split interface data to the super-class data interface processor, so that the super-class data interface processor batch-processes the split interface data to obtain business data.

In a possible implementation of the second aspect, the super-class data interface processor performs batch processing on the split interface data to obtain business data, including:

Utilize the multi-thread processing method of the super-class data interface processor to filter the split interface data according to the status of the data interface processor to obtain filtered data;

The data interface processor is called to perform business processing on the filtered data in batches according to the business logic corresponding to the data interface object to obtain business data.

In a possible implementation of the second aspect, calling back the business data to the corresponding external system includes:

After using the data interface processor to receive a callback request from the callback interface of the external system, the data interface processor is controlled to receive business data from the data interface object and transmit the business data to the callback interface of the external system.

In a possible implementation of the second aspect, the data processing system is also provided with a data interface monitoring station, and the device further includes:

A query module, used to use the data interface monitoring station to search and display the data interface header data that meets the query conditions according to the query conditions input by the user;

Display module, used to search for and display the corresponding interface data report from the data interface object according to the query request when obtaining the user's query request. The query request is input by the user after viewing the data interface header data. request.

The third aspect of the embodiment of the present invention provides a business data transmission system based on a direct connection interface. The system includes: a unified interface framework module, a master data management module, a sales management module, a financial management module and a procurement management module;

The unified interface framework module is respectively connected to the master data management module, the sales management module, the financial management module and the procurement management module.

Compared with the existing technology, the embodiments of the present invention provide a business data transmission method and device based on direct connection interfaces. The beneficial effect is that: the present invention can integrate multiple direct connection interfaces connected to external systems. By running Multiple integrated direct-connect interfaces perform multi-threaded communication connections with multiple external systems, which not only shortens communication delays and improves transmission efficiency, but also improves the stability of data transmission.

Description of drawings

Figure 1 is a schematic flow chart of a service data transmission method based on a direct connection interface provided by an embodiment of the present invention;

Figure 2 is a class diagram of a data interface framework provided by an embodiment of the present invention;

Figure 3 is a Header data structure diagram of a data interface header object provided by an embodiment of the present invention;

Figure 4 is an Object data structure diagram provided by an embodiment of the present invention;

Figure 5 is a flow chart of the saving operation of inbound interface data provided by an embodiment of the present invention;

Figure 6 is a flow chart of the saving operation of outbound interface data provided by an embodiment of the present invention;

Figure 7 is an operation flow chart of business processing provided by an embodiment of the present invention;

Figure 8 is an operation flow chart of callback processing provided by an embodiment of the present invention;

Figure 9 is an operation flow chart of monitoring processing provided by an embodiment of the present invention;

Figure 10 is a schematic structural diagram of a service data transmission device based on a direct connection interface provided by an embodiment of the present invention;

Figure 11 is a schematic structural diagram of a service data transmission system based on a direct connection interface provided by an embodiment of the present invention.

Detailed ways

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without making creative efforts fall within the scope of protection of the present invention.

In order to solve the above problems, a direct-connect interface-based service data transmission method provided by the embodiments of the present application will be introduced and explained in detail below through the following specific embodiments.

Referring to FIG. 1 , a schematic flowchart of a service data transmission method based on a direct connection interface provided by an embodiment of the present invention is shown.

In one embodiment, the method is applicable to a data processing system. The data processing system can have a unified framework for data interfaces, and all data interfaces between the data processing system and peripheral systems or external systems can be managed in a unified framework.

Through the data interface framework, the general functions of the data interface between the data processing system and the peripheral system are realized, such as: process management and status control of interface data, display and problem monitoring of interface data, and task management and scheduling of interface data processing.

These common functions no longer need to be implemented separately in various data interfaces, so that developers of various data interfaces can focus on the business and system logic of the respective interface data itself.

In one embodiment, various objects included in the data interface framework can be abstracted into the classes listed below.

Referring to Figure 2, a class diagram of a data interface framework provided by an embodiment of the present invention is shown.

In an optional embodiment, the data processing system may be provided with: a data interface header object, a data interface processor, a superclass data interface processor, and a data interface factory.

Wherein, the data interface factory, the super-class data interface processor, the data interface processor and the data interface header object are connected in sequence, the data interface factory is connected to a direct connection interface or an enhancement point, and the direct connection The port is connected to the external system, and the enhancement point is connected to the process node of the data processing system.

In one implementation, the data interface processor is a processor (ZCL_DI_PROC) that contains the core logic of interface data storage, processing, and callback. The processor can also contain that each data interface object should inherit from this class and implement its own special logic. .

In an implementation manner, the superclass data interface processor may correspond to the superclass of the data interface processor in the above list, and may be a processor (ZCL_DI_PROC_xxx) used to redefine and implement their own special logic. This part of the logic requires subclasses that each data interface object inherits from the data interface processor (ZCL_DI_PROC), such as ZCL_DI_PROC_MAT (material master data), ZCL_DI_PROC_SO (sales order data), etc.

In one implementation, the data interface factory may be the data interface factory class (ZCL_DI_FACTORY) in the above list, specifically producing data interface Header objects and processors.

In one implementation, the data interface header object may be an object of a single data interface header (ZCL_DI_HEADER) in the above list, or may be an object of multiple data interface headers in the above list (ZCL_DI_HEADERS).

Referring to Figure 3, a Header data structure diagram of a data interface header object provided by an embodiment of the present invention is shown.

In one embodiment, the present invention constructs a Header data structure based on the Header data of the data interface header object, as shown in Figure 3.

The data interface header object can be used to store data transmitted by the interface of an external system, such as serial number, object, keyword, status, time, message and other general information. For this purpose, a Header data table can be constructed as the common main table for all interface data. The storage tables for various interface data are related to the Header data table by foreign keys. Taking the material master data Material and sales order data Order as an example, Figure 3 shows the relationship between each of their tables and the common Header data table.

Specifically, the Header data table can be as follows:

In order to distinguish the above data interface processing status, in one embodiment, the value of the field of the data interface processing status may be as shown in the following table:

area describe ZDISTS Data interface processing status value describe 00 Pending 01 Processing 02 Processing failed 03 Processed successfully 09 abandoned

Similarly, in order to distinguish the above data interface callback status, in one embodiment, the value of the field of the data interface callback status can be as shown in the following table:

area describe ZDIRTS Data interface callback status value describe 00 No callback required 01 Awaiting callback 02 callback failed 03 Callback successful 09 abandoned

Referring to Figure 4, an Object data structure diagram provided by an embodiment of the present invention is shown.

Since the abstraction and unified management of data interface objects are the basis of the entire data interface framework, the present invention sets two setting tables for Object, namely the ZDIOBJSET setting table and the ZDIOBJTAB setting table.

In one embodiment, the ZDIOBJSET setting table can be as follows:

The ZDIOBJTAB settings table can look like this:

In the basic settings, the number segment of the data interface object is used to generate the number of the interface data. Each data interface object can have different number segments for easy differentiation; the processing class of the data interface object is the core of the data interface framework. Here The setting facilitates the data interface factory to find the processing class corresponding to each data interface object.

Each data interface object can have multiple data storage tables, of which one table needs to be designated as the main table. This main data table needs to be related to the data interface Header table with foreign keys, and other data tables need to be related to this main table with foreign keys. data sheet. This data interface object storage setting can help the data interface framework find the data storage table of each data interface object and display the data.

As an example, the service data transmission method based on direct connection interface may include:

S11. Obtain interface data collected by each direct connection interface respectively, where the interface data is data input by an external system connected to the direct connection interface.

For data input to the data processing system, the data processing system can define the coordinates of the direct port connected to the external system to receive data according to the agreement with the external system. It can also define the SAP end as the interface for receiving data. Generally, you can use Receive data in the form of RFC.

When the port receives data input from the external system, the data can be obtained directly from the port, thereby obtaining the interface data.

Among them, as an example, step S11 may include the following sub-steps:

S111. When the data interface factory receives the first instance acquisition request of the direct connection interface, control the data interface factory to return the first super class instance data of the super class data interface processor to the direct connection interface to Cause the direct connection interface to send interface data to the super-class data interface processor, wherein the first instance acquisition request is a request generated when an external system calls each direct connection interface to transmit data or is triggered by the enhancement point ask.

S112. Use the data interface processor to transmit the interface data received by the super-type data interface processor to the data interface header object.

In an implementation, the SAP data interface can be used as a direct interface. Specifically, the operation method of receiving data can be as follows:

The external system can call the SAP data interface and send the first instance acquisition request to the interface, so that the interface can obtain the first instance acquisition request. Then the SAP data interface can request the data interface factory (ZCL_DI_FACTORY) according to the first instance acquisition request. The data interface factory returns the first superclass instance data of the superclass data interface processor to the interface, thereby obtaining the data interface processing corresponding to the data interface object. Instance of the controller (ZCL_DI_PROC_XXX).

Subsequently, the SAP data interface can directly transmit the interface data to the super-class data interface processor. The super-class data interface processor directly transmits the data to the data interface processor. Finally, the data interface processor can transmit the data to the data interface. The header object is used for processing such as calling, saving or analyzing to achieve fast direct transmission of data.

S12. After saving the interface data, use an interface batch tool to perform business processing on the interface data according to the business logic of the external system corresponding to each interface data to obtain business data.

In one embodiment, after the data interface header object receives the data, the data can be saved first, and after the saving is completed, subsequent business processing can be performed on it to avoid data loss.

Since there are multiple connected external systems and multiple data may be received, in order to process multiple data in a unified manner, you can first determine the business logic of the external system connected to each interface, and then use the interface batch tool to determine the corresponding data for each interface. The business logic performs corresponding business processing on the data to achieve batch processing and improve the efficiency of data processing.

In an optional embodiment, the operation of saving the interface data may include the following sub-steps:

S121: Call the super-class data interface processor through the data interface processor to obtain the next data interface number of the data interface header object.

S122. Create an object instance in the data interface header object according to the data interface number, so that the data interface header object can use the object instance to save the data of the next transmission object.

S123. Use the data interface number to save the interface data into the data table of the data interface object.

Combined with the above example, using the SAP data interface as a direct interface, the operation of using the SAP data interface to call the NEW_DATA method of the processor to save the received interface data can be as follows:

First, the data interface processor can first call the NEW_HEADER method of the parent class ZCL_DI_PROC to first obtain the next data interface number of the current data interface object, and then the data interface header object creates an instance of the data interface HeaderZCL_DI_HEADER and saves the Header data.

The data interface header object then uses this data interface number to save the received interface data to the main data table and other data tables of the current data interface object.

It should be noted that the NEW_HEADER method can be called when the interface data is saved, calling GET_NEXT_NUM to obtain the new data interface number and save the data interface Header. In this embodiment, other unfinished interface data with the same data interface keyword can be set to discard at the same time, thereby ensuring that only the latest interface data will be processed.

Some steps of the data interface processor need to be managed uniformly by the interface framework. This part of the logic is directly implemented by the super class ZCL_DI_PROC itself; other steps should be implemented by each data interface object separately. This part of the logic requires each data interface object. Subclasses inherited from the super class ZCL_DI_PROC, such as ZCL_DI_PROC_MAT (material master data), ZCL_DI_PROC_SO (sales order data), etc., to redefine and implement their own special logic. Specifically, part of the logic of the data interface processor is as shown in the following table:

To further explain, the state in which an external system inputs data to the data processing system for data processing by the data processing system can be regarded as the "inbound" state.

Referring to FIG. 5 , a flow chart of the saving operation of inbound interface data provided by an embodiment of the present invention is shown.

Specifically, the data saving operation may include the following steps:

In the first step, the external system calls the SAP data interface.

In the second step, the SAP data interface requests the data interface factory ZCL_DI_FACTORY to obtain the instance of the data interface processor ZCL_DI_PROC_XXX corresponding to the data interface object.

In the third step, the SAP data interface calls the NEW_DATA method of the data interface processor to save the received interface data. The way in which the data interface processor saves the data can be performed according to the above-mentioned operations of steps S121-S123.

In another application scenario, the external system may only transmit data to the data processing system, and let the data processing system serve as a transfer station to forward the data to another external data. In this scenario, data may be output via a direct interface. To avoid data loss, the data output from the direct-connect interface also needs to be saved.

For ease of understanding, the state in which an external system inputs data to the data processing system and the data processing system outputs data to other external systems can be regarded as an "outbound" state.

Referring to FIG. 6 , a flow chart of saving outbound interface data provided by an embodiment of the present invention is shown.

For outbound interface data, the interface data is usually saved directly into the data interface framework at the corresponding system process node, such as some enhancement points or enhanced nodes.

Referring to Figure 6, the process of saving outbound interface data is the same as that of inbound interface data. The operation may include the following steps:

In the first step, the external system calls the enhancement point or enhancement node.

In the second step, the enhancement point or enhancement node requests the data interface factory ZCL_DI_FACTORY to obtain the instance of the data interface processor ZCL_DI_PROC_XXX corresponding to the data interface object.

In the third step, the enhancement point or enhancement node calls the NEW_DATA method of the data interface processor to save the received interface data. The way in which the data interface processor saves the data can also be performed according to the above-mentioned operations of steps S121-S123.

In one embodiment, when multiple pieces of data are received, it needs to be run in batches in the background, and because some data interface objects need to process a very large amount of data on a daily basis, the background tasks of the data interface need to be able to support multi-threading and parallel processing.

In order to cope with multiple large-capacity data, in this embodiment, a data interface batch tool (ZCL_DI_BATCH) is designed in the data interface framework of the data processing system. The data interface batch tool meets the needs of background batching and multi-threading.

Among them, the description of the data interface batch tool (ZCL_DI_BATCH) can be shown in the following table:

In one implementation, using the interface batch tool to perform business processing on the interface data according to the business logic of the external system corresponding to each interface data, and obtaining the business data may include the following sub-steps:

S124. When it is determined that there are multiple interface data that meet the processing conditions, use the interface batch tool to create a batch processing instance according to the business logic of the external system, and split the interface data according to the number of threads of the processing instance.

S125. After the split is completed, the control interface batch tool sends a first instance acquisition request to the data interface factory, so that the interface batch tool obtains the second super class instance data of the super class data interface processor.

S126. The interface batch tool sends the processing instance and the split interface data to the super-class data interface processor, so that the super-class data interface processor performs batch processing on the split interface data to obtain business data.

In a specific implementation manner, the business logic of the external system connected to each interface can be determined first, and then corresponding business processing is performed on the data according to the business logic corresponding to each interface. It can be judged whether the business logic is preset business logic. If the business logic cannot be executed by the data processing system, it means that the processing conditions are not met; conversely, if the business logic can be executed by the data processing system, it means that the processing conditions are met. At this time, you can determine the amount of interface data currently received. If there is multiple interface data, you can directly use the interface batch tool to create a batch processing instance based on the business logic of the external system, and split it into multiple instances according to the number of threads processing the instance. interface data. If the interface data is small, the split method can be that one interface data corresponds to one processing instance. If the interface data is large, the interface data can be split according to the amount of data that the processing instance can run. For example, if the processing instance can process 1 MB of data and the interface data is 3.5 MB, the interface data can be split into 4 processing instances.

After the split is completed, the interface batch tool can be controlled to send a first instance acquisition request to the data interface factory, so that the interface batch tool can obtain the second superclass instance data of the superclass data interface processor.

Then, the interface batch tool can directly send the processing instance and the split interface data to the super-class data interface processor, so that the super-class data interface processor batch-processes the split interface data to obtain business data.

In a specific embodiment, the super-class data interface processor performs batch processing on the split interface data to obtain business data, which may include the following sub-steps:

S1261. Use the multi-thread processing method of the super-class data interface processor to filter the split interface data according to the status of the data interface processor to obtain filtered data.

S1262. Call the data interface processor to perform business processing on the filtered data in batches according to the business logic corresponding to the data interface object to obtain business data.

Specifically, the multi-thread processing method of the super-class data interface processor is used, and the split interface data is filtered according to the status of the data interface processor, thereby obtaining the filtered data.

Then, the data interface processor is called to perform business processing on the filtered data in batches according to the business logic corresponding to the data interface object to obtain business data.

Data filtering can effectively reduce the amount of data processed to improve data processing efficiency.

In one of the optional embodiments, the business processing of the data and the saving of the data can be performed asynchronously. The data can be saved first and then the business processing is performed, or the business processing can be performed first and then the data is saved.

Referring to FIG. 7 , an operation flow chart of business processing provided by an embodiment of the present invention is shown.

Specifically, the steps for business processing of interface data in the background may include the following steps:

The first step is to read all interface data that needs to be processed that meet the conditions according to the preset conditions.

In the second step, an instance of the data interface batch tool ZCL_DI_BATCH is then created.

Among them, if multi-threading is preset, the data interface batch tool will first split the interface data that needs to be processed according to the number of threads, and then arrange a new background task for each piece of data. Each new background task itself is single-threaded and will be triggered immediately, starting from the first step.

In the third step, the data interface batch tool requests the data interface factory ZCL_DI_FACTORY to obtain the instance of the data interface processor ZCL_DI_PROC_XXX corresponding to the data interface object.

In the fourth step, the data interface batch tool calls the method PROCESS_MULTI of the data interface processor to start batch processing of interface data.

Among them, you can first call the PROCESS_MULTI method of the super class ZCL_DI_PROC to filter the interface data according to the data interface processing status, and update the processing status of Not Processing. Then call your own PROCESS_DATA_MULTI method to batch process these interface data according to the corresponding logic of the data interface object. Finally, according to the processing result, the processing status of the interface data is updated to be successful or failed, and the corresponding information is recorded.

S13. When the callback status of the direct interface is not called back, call back the business data to the corresponding external system for calling by the external system.

In one embodiment, after the external system transmits data to the data processing system for business processing, the data processing system needs to return the data processing results to the external system for further processing or application by the external system.

In one implementation, the value of the field of the data interface callback status has been preset, and the value can be queried to determine whether the callback is completed.

It should be noted that according to the previous description, the data processing system in the "outbound" state does not perform business processing on the data and does not need to perform callback processing.

If the interface data in the "outbound" state is also called back, the callback can be triggered by the external system. This process is initiated by the external system and does not need to be managed in the SAP data interface framework.

In one of the embodiments, step S13 may include the following sub-steps:

S131. After using the data interface processor to receive a callback request from the callback interface of the external system, control the data interface processor to receive business data from the data interface object and transmit the business data to the callback interface of the external system. .

When it is determined that the data that has completed business processing has not been called back to the external system, the external system can call back the request to the data interface processor through its callback interface. After the data interface processor receives the callback request, the data interface processor can call back the data interface object from the data interface object. After collecting the business data that has completed business processing, the data interface processor then transmits the business data to the callback interface of the external system, and the callback interface returns it to the external system.

Since the callback data does not involve data processing within the system, you can directly call the callback interface of the external system instead of using the direct connection interface to avoid occupying the bandwidth of the direct connection interface. Since callbacks are often relatively simple, after completing the callback, you can directly change the status of the data from pending callback to callback success or callback failure, and there will be no status in the callback.

Referring to FIG. 8 , an operation flow chart of callback processing provided by an embodiment of the present invention is shown. In one operation mode, the callback process of interface data is generally similar to the processing process of interface data. Specifically, callback processing may include the following steps:

The first step is to filter all data that has not been called back after receiving the callback request.

In the second step, you can call the interface batch tool to extract multiple uncallbacked data, and then transfer the uncallbacked data to the callback interface of the external system.

It should be noted that the saving, processing and callback of interface data by the data interface framework can be asynchronous, that is, the data received by the interface can be saved first, then processed separately, and then called back separately. Each data interface object can decide whether to process synchronously or asynchronously. Since the saving of interface data is often relatively simple, processing may be time-consuming. For data interface objects with a large amount of daily data, you can choose an asynchronous method, giving priority to ensuring that the interface data can be successfully saved, and then perform background processing afterwards. This can avoid high concurrency and timeout of the interface.

In another optional embodiment, during the process of data transmission, data processing and data callback, data transmission and processing errors may occur. If there is a lack of monitoring, it may cause serious consequences, and it is difficult to monitor the system. Make adjustments and troubleshoot problems, making modifications and adjustments inconvenient.

To do this, each of the above processes needs to be monitored. It should be noted that monitoring can be executed after obtaining the interface data, after saving the interface data, during business processing, or during callback. The details can be adjusted according to actual needs.

For data monitoring, it is not only necessary to check the status and error information of the data interface, but also often check the specific interface data for further troubleshooting and analysis. However, different data interface objects have completely different data structures. If you want to view data in the foreground, you usually need to write its own data viewer for each data interface object.

Correspondingly, a dynamic data interface monitoring platform can be designed in the data interface framework. The data interface monitoring platform can include an interface data monitor and an interface data viewer (ZCL_DI_DATA_TABLE). Among them, the interface data monitor is used to monitor each data in each process, and the interface data viewer is used to view the monitored data.

In one operation mode, all data tables of each data interface object can be configured in advance and the main table can be specified. The interface data viewer can be completely based on this configuration, drill down from the data interface header to the main data of the corresponding data interface object, and then Drill down to other relevant data.

Specifically, the description of the key attributes of the interface data viewer is as shown in the following table:

Combined with the above interface data viewer, in an embodiment, the method may also include the following steps:

S21. Use the data interface monitoring station to search and display the data interface header data that meets the query conditions according to the query conditions input by the user.

S22. When obtaining the user's query request, search and display the corresponding interface data report from the data interface object according to the query request. The query request is a request input by the user after viewing the data interface header data.

You can use the data interface monitoring station to search for data interface header data that meets the query conditions according to the query conditions entered by the user, and then display the data interface header data that meets the query conditions.

Specifically, you can use the interface data monitor to find the data interface header data that meets the query conditions, read the data interface header data that meets the query conditions through the interface data viewer, and then display it.

Users can view the data interface header data that meets the query conditions. If the user needs to take a closer look at the data, they can enter a query request. After obtaining the user query request, you can search for the corresponding interface data report from the data interface object according to the query request, and then display the interface data report for the user to take a closer look.

Referring to FIG. 9 , an operation flow chart of monitoring processing provided by an embodiment of the present invention is shown.

Specifically, the operations of monitoring and viewing interface data may include the following steps:

In the first step, the data interface monitoring station reads the data interface Header data that meets the conditions according to the query conditions entered by the user.

In the second step, the data interface monitoring console creates an instance of the data interface monitor ZCL_DI_MONITOR.

In the third step, the data interface monitoring station calls the DISPLAY method of the data interface monitor to display these Header data, as well as buttons for processing, callback, and viewing data.

In the fourth step, when the user clicks the View Data button and wants to view the specific data of the data interface object, the data interface monitoring station will call the DISPLAY_DATA method of the data interface monitor.

In the fifth step, the data interface monitor will submit an interface data report.

In the sixth step, the interface data report will first read the data of the corresponding data interface object main table, and then create an instance of the interface data viewer ZCL_DI_DATA_TABLE.

In the seventh step, the interface data report calls the DISPLAY of the interface data viewer to display these main table data and buttons to view the data of each other table.

Step 8: When the user clicks the button to view data from another table, the interface data viewer will submit a new data interface report to read and display the corresponding data from other tables.

The invention can support a variety of data interface objects, manage multiple data interface objects through a data interface framework, greatly improve the efficiency and stability of the data interface between SAP and external systems, solve many long-standing problems, and greatly increase functions. performance, flexibility and ease of use.

In this embodiment, the embodiment of the present invention provides a business data transmission method based on direct connection interfaces. The beneficial effect is that: the present invention can integrate multiple direct connection interfaces connected to external systems. By running multiple integrated The direct connection interface performs multi-threaded communication connections with multiple external systems, which not only shortens the communication delay and improves the transmission efficiency, but also improves the stability of data transmission.

An embodiment of the present invention also provides a service data transmission device based on a direct connection interface. Refer to FIG. 10 , which shows a schematic structural diagram of a service data transmission device based on a direct connection interface provided by an embodiment of the present invention.

The device is suitable for a data processing system that integrates multiple direct connection interfaces. As an example, the business data transmission device based on direct connection interfaces may include:

The data acquisition module 101 is used to obtain the interface data collected by each direct connection interface respectively, where the interface data is data input by the external system connected to the direct connection interface;

The business processing module 102 is configured to, after saving the interface data, use an interface batch tool to perform business processing on the interface data according to the business logic of the external system corresponding to each of the interface data to obtain business data;

The callback processing module 103 is configured to call back the business data to the corresponding external system for calling by the external system when the callback status of the direct interface is not called back.

Optionally, the data processing system is provided with: data interface header object, data interface processor, super class data interface processor, and data interface factory;

The data interface factory, the superclass data interface processor, the data interface processor and the data interface header object are connected in sequence, the data interface factory is connected to a direct connection interface or an enhancement point, and the direct connection interface is connected to External system connection, the enhancement point is connected to the process node of the data processing system.

Optionally, obtaining the interface data collected by each direct connection interface separately includes:

When the data interface factory receives the first instance acquisition request of the direct connection interface, the data interface factory is controlled to return the first super class instance data of the super class data interface processor to the direct connection interface, so that the direct connection interface The connection port sends interface data to the super-class data interface processor, wherein the first instance acquisition request is a request generated when an external system calls each direct connection port to transmit data or a request generated by triggering the enhancement point;

The data interface processor is used to transmit interface data received by the superclass data interface processor to the data interface header object.

Optionally, saving the interface data includes:

The data interface processor calls the superclass data interface processor to obtain the next data interface number of the data interface header object;

Create an object instance in the data interface header object according to the data interface number, so that the data interface header object can use the object instance to save the data of the next transmission object;

The data interface number is used to save the interface data into the data table of the data interface object.

Optionally, the interface batch tool is used to perform business processing on the interface data according to the business logic of the external system corresponding to each interface data to obtain business data, including:

When it is determined that there are multiple interface data that meet the processing conditions, use the interface batch tool to create a batch processing instance based on the business logic of the external system, and split the interface data according to the number of threads of the processing instance;

After the split is completed, the control interface batch tool sends a first instance acquisition request to the data interface factory, so that the interface batch tool obtains the second super class instance data of the super class data interface processor;

The interface batch tool sends the processing instance and the split interface data to the super-class data interface processor, so that the super-class data interface processor batch-processes the split interface data to obtain business data.

Optionally, the super-type data interface processor performs batch processing on the split interface data to obtain business data, including:

Utilize the multi-thread processing method of the super-class data interface processor to filter the split interface data according to the status of the data interface processor to obtain filtered data;

The data interface processor is called to perform business processing on the filtered data in batches according to the business logic corresponding to the data interface object to obtain business data.

Optionally, calling back the business data to the corresponding external system includes:

After using the data interface processor to receive a callback request from the callback interface of the external system, the data interface processor is controlled to receive business data from the data interface object and transmit the business data to the callback interface of the external system.

Optionally, the data processing system is also provided with a data interface monitoring station, and the device further includes:

A query module, used to use the data interface monitoring station to search and display the data interface header data that meets the query conditions according to the query conditions input by the user;

Display module, used to search for and display the corresponding interface data report from the data interface object according to the query request when obtaining the user's query request. The query request is input by the user after viewing the data interface header data. request.

An embodiment of the present invention also provides a service data transmission system based on a direct connection interface. Refer to Figure 11, which shows a schematic structural diagram of a service data transmission system based on a direct connection interface provided by an embodiment of the present invention.

Wherein, as an example, the business data transmission system based on direct connection interface may include: unified interface framework module, master data management module, sales management module, financial management module and procurement management module;

The unified interface framework module is respectively connected to the master data management module, the sales management module, the financial management module and the procurement management module.

Among them, the unified interface framework module is used to uniformly manage each directly connected interface.

The master data management module is used to manage system data and data-related processing.

The sales management module is used to manage sales-related data.

The financial management module is used to manage financial-related data.

The procurement management module is used to manage data related to procurement projects.

Those skilled in the art can clearly understand that for convenience of description and simplicity, the specific working process of the device described above can be referred to the corresponding process in the foregoing method embodiment, and will not be described again here.

Furthermore, embodiments of the present application also provide an electronic device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, the above implementation is implemented. The business data transmission method based on direct connection interface described in the example.

Further, embodiments of the present application also provide a computer-readable storage medium that stores a computer-executable program, and the computer-executable program is used to cause the computer to execute the steps described in the above-mentioned embodiments. Business data transmission method based on direct interface.

Those skilled in the art will understand that embodiments of the present application may also provide computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment that combines software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), apparatuses and computer program products according to embodiments of the application. It will be understood that each process and/or block in the flowchart illustrations and/or block diagrams, and combinations of processes and/or blocks in the flowchart illustrations and/or block diagrams, 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, embedded processor, or other programmable data processing device to produce a machine, such that the instructions executed by the processor of the computer or other programmable data processing device produce a use A device for implementing the functions specified in one process or processes of the flowchart and/or one block or blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory that causes a computer or other programmable data processing apparatus to operate in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction means, the instructions The device implements the functions specified in a process or processes of the flowchart and/or a block or blocks of the block diagram.

These computer program instructions may also be loaded onto a computer or other programmable data processing device, causing a series of operating steps to be performed on the computer or other programmable device to produce computer-implemented processing, thereby executing on the computer or other programmable device. Instructions provide steps for implementing the functions specified in a process or processes of a flowchart diagram and/or a block or blocks of a block diagram.

The above are only preferred embodiments of the present invention. It should be noted that those of ordinary skill in the art can also make several improvements and modifications without departing from the technical principles of the present invention. These improvements and modifications It should also be regarded as the protection scope of the present invention.

Claims (10)

1. A business data transmission method based on direct connection interfaces, characterized in that the method is suitable for data processing systems integrating multiple direct connection interfaces, and the method includes: Obtain the interface data collected by each direct connection interface respectively, where the interface data is data input by the external system connected to the direct connection interface; After saving the interface data, use an interface batch tool to perform business processing on the interface data according to the business logic of the external system corresponding to each interface data to obtain business data; When the callback status of the direct interface is not called back, the business data is called back to the corresponding external system for calling by the external system. 2. The business data transmission method based on direct connection interface according to claim 1, characterized in that the data processing system is provided with: data interface header object, data interface processor, super class data interface processor, Data interface factory; The data interface factory, the superclass data interface processor, the data interface processor and the data interface header object are connected in sequence, the data interface factory is connected to a direct connection interface or an enhancement point, and the direct connection interface is connected to External system connection, the enhancement point is connected to the process node of the data processing system. 3. The business data transmission method based on direct connection interfaces according to claim 2, characterized in that the separately obtaining the interface data collected by each direct connection interface includes: When the data interface factory receives the first instance acquisition request of the direct connection interface, the data interface factory is controlled to return the first super class instance data of the super class data interface processor to the direct connection interface, so that the direct connection interface The connection port sends interface data to the super-class data interface processor, wherein the first instance acquisition request is a request generated when an external system calls each direct connection port to transmit data or a request generated by triggering the enhancement point; The data interface processor is used to transmit interface data received by the superclass data interface processor to the data interface header object. 4. The business data transmission method based on direct connection interface according to claim 2, characterized in that said saving the interface data includes: The data interface processor calls the superclass data interface processor to obtain the next data interface number of the data interface header object; Create an object instance in the data interface header object according to the data interface number, so that the data interface header object can use the object instance to save the data of the next transmission object; The data interface number is used to save the interface data into the data table of the data interface object. 5. The business data transmission method based on direct connection interface according to claim 2, characterized in that the use of interface batch tools performs business on the interface data according to the business logic of the external system corresponding to each of the interface data. Process and obtain business data, including: When it is determined that there are multiple interface data that meet the processing conditions, use the interface batch tool to create a batch processing instance based on the business logic of the external system, and split the interface data according to the number of threads of the processing instance; After the split is completed, the control interface batch tool sends a first instance acquisition request to the data interface factory, so that the interface batch tool obtains the second super class instance data of the super class data interface processor; The interface batch tool sends the processing instance and the split interface data to the super-class data interface processor, so that the super-class data interface processor batch-processes the split interface data to obtain business data. 6. The business data transmission method based on direct connection interface according to claim 5, characterized in that the super-class data interface processor performs batch processing on the split interface data to obtain business data, including: Utilize the multi-thread processing method of the super-class data interface processor to filter the split interface data according to the status of the data interface processor to obtain filtered data; The data interface processor is called to perform business processing on the filtered data in batches according to the business logic corresponding to the data interface object to obtain business data. 7. The business data transmission method based on direct connection interface according to claim 2, characterized in that the callback of the business data to the corresponding external system includes: After using the data interface processor to receive a callback request from the callback interface of the external system, the data interface processor is controlled to receive business data from the data interface object and transmit the business data to the callback interface of the external system. 8. The business data transmission method based on direct connection interface according to any one of claims 2 to 6, characterized in that the data processing system is also provided with a data interface monitoring station, and the method further includes: Use the data interface monitoring station to search and display the data interface header data that meets the query conditions according to the query conditions input by the user; When the user's query request is obtained, the corresponding interface data report is searched from the data interface object according to the query request and displayed. The query request is a request input by the user after viewing the data interface header data. 9. A business data transmission device based on a direct connection interface, characterized in that the device is suitable for a data processing system integrating multiple direct connection interfaces, and the device includes: A data acquisition module, configured to obtain interface data collected by each direct connection interface respectively, where the interface data is data input by an external system connected to the direct connection interface; A business processing module, after saving the interface data, using an interface batch tool to perform business processing on the interface data according to the business logic of the external system corresponding to each of the interface data to obtain business data; A callback processing module, configured to call back the business data to the corresponding external system for calling by the external system when the callback status of the direct interface is not called back. 10. A business data transmission system based on direct connection interface, characterized in that the system includes: a unified interface framework module, a master data management module, a sales management module, a financial management module and a procurement management module; The unified interface framework module is respectively connected to the master data management module, the sales management module, the financial management module and the procurement management module.