How does TBOM obsolescence detection work, and what does 'Out-of-Date' actually mean?

Schedule a background job to flag potentially obsolete TBOMs (they go stale as the application changes, e.g. a transaction changes after a new SP). The check compares objects changed in a transport with objects in the TBOM.

Since the system can't tell whether a change really altered program flow, Out-of-Date only means re-record at the next update cycle — it's still usable. Flow-changing object types are included (CLAS/FUGR/FUNC/PROG/TABU; a table-content change only matters if the TBOM recorded a table-access key).