Schedule a background job to verify that a TBOM is up-to-date, and mark TBOMS as potentially obsolete, to generate an overview of potentially obsolete TBOMS.

A TBOM can become obsolete if, for example, a transaction changes by importing a new support package. Perform this activity manually after you have made changes.

The obsolescence check compares the changed objects in transport requests and versions with the objects in TBOMs. The system cannot identify whether a changed object actually resulted in a program flow change and actually made the TBOM obsolete, so the Obsolete status only indicates that you need to record the TBOM again during the next planned TBOM update cycle.

The TBOM status Obsolete indicates that the TBOM is potentially obsolete. The obsolescence check is based on a comparison of the changed objects in transport requests and versions of the objects in TBOMs. The system cannot identify whether a changed object actually resulted in a program flow change and made the TBOM obsolete.

The Obsolete status only indicates that you need to record the TBOM again during the next planned TBOM update cycle. 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.

See also the customizing (transaction SPRO) for SAP Solution Manager under  Capabilities Business Process Change Analyzer Schedule Check Jobs for TBOM .