eG Monitoring
 

Measures reported by AsAbapBatchTest

Batch input is one of the primary ways in which data can be transferred into the SAP ABAP System. Batch input is used for bulk data transfers and not for near real-time data transfers.

Typical uses of batch input include the one-time import of data from a legacy system into a newly installed SAP ABAP System. Another typical use is for periodic (hourly, daily...) transfers of data from external systems or legacy systems that are still in use into SAP ABAP, where all enterprise data is consolidated.

A batch input session is a set of one or more calls to transactions along with the data to be processed by the transactions. The system normally executes the transactions in a session non-interactively, allowing rapid entry of bulk data into an SAP ABAP System.

Administrators should periodically check whether/not the batch input sessions have completed successfully. If bulk transfers into the SAP ABAP system via these sessions is interrupted, then administrators should be able to promptly capture the errors in sessions, instantly initiate error analysis, and rapidly correct the problem. The AsAbapBatchTest test enables administrators to perform all this and more!

This test monitors the batch input sessions, promptly detects errors in sessions, and accurately points administrators to those sessions where errors have occurred. In addition, the test periodically measures the load on the SAP ABAP system by reporting the number of created and running sessions, and in the process, warns administrators of probable overload conditions.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
NumberOfErrSessions Indicates the current number of batch input sessions with errors. Number Ideally, the value of this measure should be 0. A non-zero value indicates that transactions in one/more sessions ended in errors. A transaction contains an error if it issues a message of type E (error) or type A (abnormal termination). In such situations, the system administrator must analyze the error.

Most errors fall into one of two categories:

  • Required data is missing from the batch-input session or invalid data has been included in the session. Possible external causes of this type of problem include errors in the data conversion program or the presence of unexpected types of data or incorrect data in the legacy database. Causes for this type of problem within R/3 include incorrect or incomplete customizing in an application. For example, a legacy data type may not have been foreseen in the check table entries made in application customizing.
  • Technical/programming problems. A batch input session enters data by running R/3 transactions non-interactively. A typical technical or programming problem is therefore incorrect identification of one of the data fields in a transaction. Or the conversion program may not fill a required data field or may have provided invalid values.
You can use the detailed diagnosis of this measure to know which batch input sessions encountered what type of errors.

To correct transactions with errors, the system administrator or the responsible department can interactively correct and reprocess the transactions.
NumberOfBGSessions Indicates the current number of batch input sessions running in the background. Number The data in a batch input session can be processed in one of the three modes:

  • Process/foreground: Runs the session in the foreground, displaying every screen and field. If you change a screen in this option, the process halts.
  • Display errors only: Runs the session in the foreground, displaying only errors.
  • Background: Runs the session in the background.
The NumberOfBGSessions measure reports the number of sessions currently running in the background mode. Since sessions are typically run in this mode to execute the data transfer or test its performance, you can use the NumberOfBGSessions measure as an indicator of the number of data transfer sessions the SAP ABAP system can handle at a given point in time.
NumInProcSessions Indicates the number of batch input sessions that are currently running. Number This is a good indicator of the current batch input session load on the SAP ABAP system.
NumNewSessions Indicates the number of batch input sessions being created. Number  
NumFinishedSessions Indicates the number of batch input sessions that were finished already. Number