Posting Errors Displayed Immediately

SAP NetWeaver Exchange Infrastructure (SAP NetWeaver XI) works as a broker between SAP and non-SAP solutions, making information exchange secure. Although the component has diverse options for monitoring data exchange, it can do so only in terms of the data’s conversion and distribution. Once SAP NetWeaver XI has successfully converted data into the desired format and transmitted it to the SAP back end, it regards its task as complete – successfully and without errors.
It’s also vitally important for a business processes to know that the target system has processed the transferred information correctly. Monitoring this operation is not a native task of SAP NetWeaver XI. REALTECH BackendBooster for SAP NetWeaver XI optimally supplements the functions of the broker.

REALTECH BackendBooster
REALTECH BackendBooster

REALTECH BackendBooster provides mechanisms for differentiated process control like monitoring at the level of business flows. During operations, SAP NetWeaver XI monitors data exchange; REALTECH BackendBooster monitors the correct posting of data in SAP software. This approach guarantees seamless operation of core processes.

Data Exchange and Data Control

Interfaces that map business processes are defined in REALTECH BackendBooster. For example, the interfaces store information about who is responsible for a business process so that they can notify the appropriate user in the event of an error. The interfaces automatically generated by REALTECH BackendBooster contain the complete technical definition, such as the loading method in use. You can define which data is ultimately delivered to which interface as you wish in REALTECH BackendBooster – unlike the situation with the ALE monitor, the standard tool of IDoc monitoring in the SAP back end.
The ALE monitor has only a few filter criteria like the IDoc number, the date of creation, the partner system, or the type of message. REALTECH BackendBooster, however, uses all the useful data of the IDoc (company code, sales organization, or plant) as a differentiating characteristic. For example, if several sales organizations are managed in an SAP solution, you can use REALTECH BackendBooster to distribute the sales order data intelligently. If a posting error occurs with an IDoc from sales organization X, BackendBooster issues an alert to the user responsible. Depending on the responsibilities involved in such a case, the tool can also notify several persons from various departments. That’s how the solution supports even complex and interwoven business processes.

Within REALTECH BackendBooster, the interface monitor keeps an eye on all the defined interfaces. It analyzes the data in the SAP back end in light of criteria specified in the BackendBooster and thus monitors its posting status. REALTECH BackendBooster redirects errors in the posting process directly to the department responsible for the operation so that it can analyze and correct errors.

Error Analysis and Correction

As a rule, the data from SAP NetWeaver XI is transferred to REALTECH BackendBooster as objects – BAPIs or IDocs in this case. As far as SAP NetWeaver XI is concerned, the data has already been exchanged successfully. REALTECH BackendBooster then distributes the data to the defined interfaces responsible for the business processes. The interfaces, in turn, transmit the data as objects to the posting process and monitor it. All steps are logged and are available for analysis in REALTECH BackendBooster. If an error occurs during posting, the software informs the user responsible. REALTECH BackendBooster stores the source data of the erroneous objects in persistent tables for analysis and correction of the problem. Users who analyze errors in the monitor have the following options:

  • Reinitiate the posting. This approach makes sense when a block was present during the previous attempt at posting.
  • Correct the data and reinitiate the posting operation. This approach makes sense when the source data is incorrect – if the incorrect plant was entered, for example.
  • Reinitiate the posting operation in the event of poor data quality with an alternate loading method: call transaction. This way, the user can monitor the posting online and execute the same steps involved in a familiar, manual posting.
  • Reject the erroneous object. This approach triggers an additional process, such as issuing a notification to the person responsible for the process or issuing a confirmation to SAP NetWeaver XI.

A user can repeat these actions as often as desired until the error is corrected. The user works in the familiar SAP environment. The technology used to post the data in the back end makes no difference. It can be IDoc, BAPI, call transaction, or a customer-specific loading module. The user interface for monitoring and correcting the failure remains the same.
Whether RFC or ALE is involved, REALTECH BackendBooster offers comprehensive monitoring of the posting of SAP data over a central user interface for the first time. Up until now, RFC-based processes – the flows in SAP NetWeaver XI – or ALE-based processes in the SAP back end could only be monitored separately.

Mass Data Handling in ABAP

Complete implementation of the interface monitor in ABAP code within the SAP back end enables direct access to all SAP resources. Within the SAP back end, REALTECH BackendBooster offers its own, integrated development environment for the maintenance and service of interface programs in ABAP.
Users do not have to go to all the effort of writing the interface programs manually. They can generate the interfaces automatically in REALTECH BackendBooster with simple configuration. For developers, definition of the interfaces at the meta level is manageable and easy to maintain. Little or no programming knowledge is required. The coding can be reproduced at any time from a combination of templates.
For performance reasons, REALTECH BackendBooster consciously avoids intermediate steps that require transformation of the data into intermediate formats like XML. Mass data handling occurs within the native ABAP coding, and data is redirected directly to the loading method of the SAP solution involved. Process monitoring occurs across applications, and the software offers an open API interface to exchange status information – even with external applications.
Regardless of the loading method, REALTECH BackendBooster can recheck the data to be transmitted for errors. If the source data does not contain the information needed for correct posting, the software reads the information directly from the SAP back end and inserts it as needed. Because it is integrated with the SAP back end, no resource-intensive RDC call with SAP NetWeaver XI is needed.

Stefan Huber
Stefan Huber