Batch Input Channel

Batch Input is used mainly for bulk data transfers, for example, the one-time import of data from a legacy system into a newly installed SAP system. Another typical use is for periodic (hourly, daily...) transfers of data from external systems or legacy systems that are still in use into the SAP system, 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 system.                              

A session records transactions and data in a special format that can be interpreted by the SAP system. When the System reads a session, it uses the data in the session to simulate on-line entry of transactions and data. The System can call transactions and enter data using most of the facilities that are available to interactive users.

For more information refer to: SAP Help → SAP Netweaver 7.5 → Managing Batch Input Sessions

Technical Prerequisites

The following technical prerequisites need to be fulfilled to use this monitoring template:

  • Managed system has an SAP Basis ≥ 7.00
  • ST-A/PI 01R is installed on the managed system
  • Solution Manager 7.01 SP 23 or newer is installed on the SAP Solution Manager system

Available Monitoring Content

 

The Batch Input monitoring functionality enables an automated monitoring of the processing of batch input session. This includes the monitoring of sessions in a specific status, the monitoring of the number of errors within these sessions, the monitoring of the number of transactions processed within specific sessions and the monitoring of cancellations if background jobs processing batch input sessions.

 

Monitoring Template: Batch Input

Metric Name Description MAI Category Since SP

Number of sessions in critical status(es)

Measures the number of batch input sessions in a specified status. It is intended to be used for measuring batch input sessions in a critical status.

Exceptions

7.1 SP12

Number of sessions in uncritical status(es)

Measures the number of batch input sessions in a specified status. It is intended to be used for measuring batch input sessions in an uncritical status.

Performance

7.1 SP12

Number of errors per session

Measures the Number of errors that occurred when the queue was processed

Exceptions

7.1 SP12

Transactions processed per session

Measures the number of transactions in the defined status(es)

Performance

7.1 SP12

Number of transaction in critical status(es)

Measures the number of transactions in a specified status. It is intended to be used for transactions in a critical status.

Exceptions

7.1 SP12

Number of transaction in uncritical status(es)

Measures the number of transactions in a specified status. It is intended to be used for transactions in an uncritical status.

Performance

7.1 SP12

Canceled jobs during Batch Input processing

For every session, one background job for processing is created when background processing is chosen. If enabled, the monitor checks whether the job was canceled.

Exceptions

7.1 SP12

Configuration

The Interface and Connection Monitoring setup can be accessed via SAP Solution Manager Configuration (SOLMAN_SETUP). 

To access the Integration Monitoring setup please go to SAP Solution Manager Configuration (SOLMAN_SETUP) → Application Operations → Integration Monitoring → Interface and Connections.

Note: If you didn't perform the infrastructure configuration yet, please follow the Interface and Connection Monitoring Setup with SAP Solution Manager 7.2.

Monitoring Template: Batch Input

Navigate to the step 'Define Scope'. You can create a new scenario or use an existing one. Make sure the sender and the receiver system are part of the Interface and Connection Monitoring scenario.

Create the Interface Channel:

  1. Select the scenario and click 'Next'
  2. In step 'Preparation' perform all relevant manual activities and run all automatic activities.
  3. In step 'Configuration' click the 'Add' button.
    • Channel Name: Enter a meaning full name (max. 30 characters)
    • Type: Select 'Batch Input'
    • Monitoring Template: Select 'Batch Input'
    • Description: Enter a description for the channel
  4. Click Next.
  5. Source type:
    • Select 'Technical System'
    • If the source system is not on-premise please select 'External Service' if it is a cloud service or 'Unspecified Managed Object'.
  6. Source: Select the on premise system from the drop-down list or enter the name for the unspecified managed object
  7. Target Type:
    • Select 'Technical System'
    • If the target system is not on-premise please select 'External Service' if it is a cloud service or 'Unspecified Managed Object'.
  8. Target: Select the target system from the drop-down list or enter the name for the unspecified managed object
  9. The measuring point is selected automatically. Please note that for this template either the target or the source system must be an ABAP system! Usually the measuring point would be the target system.
  10. If more than one client are connected for the on premise system please select the correct client for the monitoring
  11. Click Next.
  12. Click Finish.

Maintain the Interface:

  1. Select the interface channel you created
  2. On the 'Interfaces' tab click the 'Add' button.
  3. Provide the following information
    • Interface Name: The name of the interface
    • Session Name (mandatory): Enter the name of the session or the group of the sessions that should be monitored (the information required can be found in transaction SM35 of the monitored system). You can also use the input help to maintain this field.
    • Creating Program: Name of the program that created the session (information about the creating program can also be found in transaction SM35).
    • Created by: Enter the name of the user who created the session.
    • Max. Session Age (integer in days): Define the age of sessions to be taken into account when data is collected. Via this parameter you can avoid the alerting on old batch input session.
    • Max. Alert Age (integer in days): Define how long the data collection history should be kept for the managed object. If not set or set to more than 14 days it is automatically restricted to 14 days.

Select Metrics:

  1. On the tab 'Metrics' select the metrics you want to monitor. Please note that the selected metrics are collected for each interface destination entered above.

  2. Enter Metric Parameters:

    • Metric: Number of errors per session
      • Parameter set name: You can enter a name for the parameter set to distinguish it if you have more than one
      • Unit (mandatory): Define whether the total number of sessions or the percentage of sessions should be monitored.
        • Number (N): The number of sessions matching the selection criteria is taken into account for rating the alert.
        • Percentage (%): The percentage in comparison to all found sessions is taken into account.
    • Metric: Number of sessions in critical / uncritical status(es)
      • Parameter set name: You can enter a name for the parameter set to distinguish it if you have more than one
      • Status(es) (mandatory): This parameter has to be set for all metrics that measure status related key figures. Use the input help to select a status.
      • Collector Mode (mandatory): Define how the data collector should evaluate the data
        • ALL: This collector type evaluates the total number of all batch input sessions listed in SM35 that fulfill the configured selection criteria, regardless of whether a session has already been alerted on or not. How far into the past sessions are monitored is determined by the configuration of parameter 'Maximum Session Age' on interface level.
        • DELTA: This collector type keeps a data collection history to determine whether a session has already been alerted on. Only sessions that have not yet been alerted on are considered during the data collection. The length of the history of the data collection is restricted by parameter ‘Maximum Alert Age' on interface level.
      • Unit (mandatory): Define whether the total number of sessions or the percentage of sessions should be monitored.
    • Metric: Number of transaction in critical / uncritical status(es)
      • Parameter set name: You can enter a name for the parameter set to distinguish it if you have more than one
      • Status(es) (mandatory): This parameter has to be set for all metrics that measure status related key figures. Use the input help to select a status.
      • Collector Mode (mandatory): Define how the data collector should evaluate the data.
      • Unit (mandatory): Define whether the total number of sessions or the percentage of sessions should be monitored.

 

Critical vs. uncritical Status Metrics

Note that technically metrics for critical and uncritical statuses produce the same result if configured identically. However, metrics for critical statuses are supposed to be used for measuring transactions in an error state only, whereas metrics for uncritical statuses can be used for throughput measurements, too. Consequently in the Interface Channel Monitoring application the metrics are categorized as “Exceptions” and “Performance”, respectively.

You can maintain attributes as described in the Interface and Connection Monitoring Setup with SAP Solution Manager 7.2 on the tab 'Attributes'.

Thresholds and the collection schedule are maintained in the next step of the guided procedure. Once you have maintained all your channels, click 'Next' in the main guided procedure to move to the step 'Activation'.

 

Maintain Thresholds and Schedule:

  1. Select the Alert for the channel (the alert is the line with the red flash icon next to it)
    • On alert level you can maintain notification and incident message creation
  2. Select the Metrics
    • You can adjust the thresholds on the tab Thresholds. The recommended rating strategies for this metric are “Info Only”, “Numeric Threshold (Green/Yellow/Red)” and “Range Threshold”. 
    • Do not change the data collector type or data collector name on the tab 'Data Collection' as the monitor will not work anymore if this is changed.
    • Only change the collection interval if you know what you do or if advised to do this by SAP.
  3. Click 'Apply and Activate' → <Choose one option> to activate the monitoring