Show TOC

Procedure documentationChecking Whether a TBOM is Up-to-Date


A TBOM contains a list of all objects that are used in a specific executable entity. If you change objects in the TBOM, the TBOM may potentially contain outdated information.

The obsolescence check compares the objects listed in the TBOM with the objects that actually exist in the system affected. The system affected is the system in which you executed the executable entity in order to record the TBOM. All object types that can change the program flow for an executable entity are taken into account. The following object types are included:

  • CINC: Class include (ABAP objects)

  • CLAS: Class (ABAP objects)

  • CLSD: Class definition (ABAP objects)

  • CPRI: Private header (ABAP objects)

  • CPRO: Protected header (ABAP objects)

  • CPUB: Public header (ABAP objects)

  • DIAL: Dialog module

  • ENHO: Enhancement implementation

  • ENHS: Enhancement spot

  • FUGR: Function group

  • FUNC: Function module

  • METH: Method (ABAP objects)

  • PROG: Program

  • REPS: Report source

  • SHLP: Search help

  • TABU: Table contents

    Changing table contents only results in an out-of-date TBOM if a table access key was recorded in the TBOM. For more information, see Displaying TBOM Contents.

  • WAPA: BSP (Business Server Page) application

  • WAPP: Page/controller for a BSP application

  • WDYC: Controller (Web Dynpro)

  • WDYN: Web Dynpro components

  • WDYV: View (Web Dynpro)

  • SQLT: Pool/cluster table

  • TABL: Table

  • TTYP: Table type

  • VIEW: View

You can either run the check directly for an individual TBOM, or use report AGS_BPCA_TBOM_OUTDATE_CHECKER2. We recommend scheduling a job that executes this report daily. You define the background job for the TBOM obsolescence check in Customizing for SAP Solution Manager under Start of the navigation path Capabilities Next navigation step Business Process Change Analyzer Next navigation step Schedule Check Jobs for TBOM End of the navigation path.


Checking Whether a Specific TBOM is Up-to-Date
  1. Open the attributes of the executable entity whose TBOM you wish to check.

  2. Choose the TBOM tab.

  3. Choose Up-to-Date Check.

  4. Specify the required options for the obsolescence check:

    • The default value for the date is derived from the TBOM creation date, the last changed date of the TBOM, and the last obsolescence check for this TBOM. If you only want to include changes made after a specific date in the system affected, you can specify a later date.

      Note Note

      If you specify a later date, the TBOM may be flagged as Updated although relevant changes were made in the affected system on an earlier date.

      End of the note.
    • Choose the source that the system is to use to determine changed objects:

      • Transport Requests: The obsolescence check takes into account all transport requests in the affected system as well as transport requests that were imported into or exported out of the system. The period for the transport requests checked is derived either from the date of the last obsolescence check or from the data specified by the user.

      • Versions: The obsolescence check can take into account new versions of development objects in the affected system.

        New versions of development objects are generated when transport requests are imported or exported. Objects determined in this way are therefore always a subset of the objects determined based on the transport requests. You can use this option, for example, if you develop customer objects and want to restrict the check to objects with versions.

  5. Start the obsolescence check.

    You can either execute the obsolescence check immediately or start it as a background job.

    Note Note

    We recommend starting any obsolescence checks that span longer periods as background jobs. The system notifies you when the check has completed.

    End of the note.
Checking Whether a TBOM is Up-to-Date Using Report AGS_BPCA_TBOM_OUTDATE_CHECKER2
  1. Call the TBOM Obsolescence Check report (AGS_BPCA_TBOM_OUTDATE_CHECKER2).

    1. In the Test Management work center, choose the Administration view.

    2. Choose TBOM Utilities.

    3. Choose TBOM Obsolescence Check.

  2. Specify whether you want to check all TBOMs or just those for specific objects or solutions.

    To check the TBOMs for specific objects or solutions only, select the relevant checkbox and specify the relevant projects or solutions.

  3. Specify the source to be used to determine changed objects.

    You can use transport requests or versions to check whether data is up-to-date.

  4. Choose the execution options.

    • When you choose the details for all TBOMs, the relevant short text for each out-of-date TBOM is displayed.

    • When you update the database, the system saves the status information determined and changes the date of the last obsolescence check for all TBOMs checked. If you only want to execute a test run, deselect the checkbox.

  5. Optional: Select the special check options.

    • If you specify a date as of which changes are to be taken into account, the system checks only those transport requests that were imported or exported after this date. Any transport requests from before this date are not considered relevant by the system. If you do not specify a date, the system automatically sets the period for which transport requests are checked.

      Note Note

      If you specify a date, the TBOM may be flagged as Updated although relevant changes were made in the affected system on an earlier date.

      End of the note.
    • You can repeat the check for TBOMs already flagged as Out-of-Date.

      Repeating the check with a specific change date allows out-of-date TBOMs to be assigned the Up-to-Date status once more. Note that executing the check again for out-of-date TBOMs can take some time.

    • You can check all changes made since the last TBOM change.

      The system saves the date of the last obsolescence check for each TBOM. To accelerate the check, by default, the system checks only those transport requests that have been added since the last check. This option allows you to specify the scope of the transport requests to be checked rather than using the date of the last TBOM change. When you choose this option, the obsolescence check is equivalent to the first obsolescence check executed. It therefore may take some time to execute.

    • You can recalibrate all out-of-date TBOMs.

      When you choose this option, out-of-date TBOMs are assigned the Up-to-Date status once more. However, the contents of the TBOMs are not changed. For more information, see Recalibrating TBOMs.

  6. Execute the report.

    You can execute the report immediately or schedule it as a job.

    Note Note

    We recommend starting obsolescence checks that span longer periods or include out-of-date TBOMs as background jobs. Only execute obsolescence checks for short change periods immediately.

    End of the note.


The system has checked the objects in the TBOM. The system has assigned the overall status Out-of-Date to the TBOM under the following conditions:

  • If you selected the Transport Requests option: In the transport requests checked, the obsolescence check found at least one object that is also in the TBOM.

  • If you selected the Versions option: The obsolescence check found an object version in the affected system that was generated during the period being checked.

The TBOM status Out-of-Date indicates that the TBOM is potentially obsolete. The obsolescence check is based on the comparison of the changed objects in transport requests and versions with the objects in TBOMs. However, the system cannot identify whether a changed object actually resulted in a program flow change and actually outdated the TBOM.

The Out-of-Date status therefore simply indicates that you need to record the TBOM again during the next planned TBOM update cycle. However, you can continue to use the TBOM for analyses. For more information about analysis results for out-of-date TBOMs, see the Prerequisites section in Analyzing Business Processes Affected by Changes.