Show TOC

Procedure documentationRecording Batch TBOMs Locate this document in the navigation structure

 

You can also create TBOM extensions for executable units that call one or more background jobs.

Prerequisites

  • The RFC connection to the managed system does not require manual logon.

    For more information about recording a batch TBOM without an RFC connection, see Checking the Status of a Batch TBOM.

  • See SAP Note 1684704 for further requirements.

Procedure

  1. Follow the instructions for recording a TBOM. For more information, see Create TBOM.

  2. Create a dynamic TBOM.

  3. To create a TBOM, start a transaction or another executable unit that schedules background jobs.

    The system creates a TBOM extension with the objects that are used directly by the executable unit.

    Next, the system plans a background job for the TBOM collector in the SAP Solution Manager system. The system specifies the time of the first execution as two minutes after the first background job starts in the managed system.

    The TBOM collector checks whether the scheduled background jobs have already been executed in the managed system. When a background job is finished, the TBOM collector creates a separate TBOM extension for the objects that were affected by the background job in question. Until all the jobs have been completed, the system schedules the TBOM collector again five minutes later.

    If all the jobs on the managed system are complete and errors occur when the TBOM collector is executed, the system attempts to execute the TBOM collector two more times. After a total of three failed attempts, the system deallocates the TBOM collector. Failed attempts can occur if, for example, manual logon is necessary for the RFC connection.

    The following graphic illustrates this process.

    This graphic is explained in the accompanying text.

    Flow Chart for Creating a Batch TBOM