Show TOC

Procedure documentationChoosing the TBOMs Types

 

A TBOM (Technical Bill of Materials) contains all the objects in an executable entity. The business process change analyzer (BPCA) uses TBOMs to determine whether an executable entity is affected by a change. To be able to use the BPCA, create a TBOM for each executable entity in your solution documentation.

To create a TBOM, you have the following options, in descending order of precision:

  • Dynamic:

    Dynamic TBOMs are the most precise, but cannot be generated automatically. Use them for business-critical transactions, for example.

    Record, for example, a transaction while it runs. The associated executable entity is called with the corresponding RFC user in the managed system. You must be authorized to execute the executable entity in the managed system. Enter the data required for the executable entity there.

    All objects in the executable entity are captured in the background, and copied to the TBOM once the executable entity has run. The dynamic creation also includes RFC connections and branched GUI user procedures within the same (primary) system, and RFC connections to other (secondary) systems. In these cases, so-called enhancements are created. Further RFC connections to third-party systems are also recorded, but branched GUI processes in secondary or third-party systems are no longer recorded.

    Enhancements are also created if an executable entity schedules background jobs. The system creates a separate TBOM enhancement for each background job with the objects involved.

    Note Note

    Running the executable entities creates new data records in the managed system. Take this into account when you create TBOMs in a production system.

    End of the note.

    Note Note

    When you record a dynamic TBOM, all actions performed by the same user are recorded in the managed system. Ensure that this user does not perform any actions during the TBOM recording which should not be recorded.

    End of the note.

  • Semi-Dynamic

    Semi-dynamic TBOMs are mass-generated and are more precise than static TBOMs. As with the generation of a static TBOM, the system analyzes the environment to determine which objects are in the executable entity. Only objects which are actually used are in the TBOM.

    From Solution Manager 7.2 SPS 3, semi-dynamic TBOMs can also be based on the ABAP Call Monitor (transaction SCMON). In addition to UPL, SCMON also records the entry point, for example the transaction, from which an object is used. This enables a better connection of used objects to executable units. In addition semi-dynamic TBOMs based on SCMON can capture also dynamically called objects.

    Semi-dynamic TBOMs can also use the Usage and Procedure Logging (UPL). Semi-dynamic TBOMs based on UPL are less exact than TBOMs from SCMON. Objects are filtered using the object usage data that is provided by the UPL function of your system.

  • Static:

    In static (as with semi-dynamic) mass-generation, the executable entity is not called. The system analyzes the environment to determine which objects are in the executable entity, so you therefore do not require authorization in the managed system. Dynamic calls or generated objects are not detected, so they are not in the TBOM. The result is not as precise as dynamic or semi-dynamic generation.

Note Note

Static and semi-dynamic TBOMs do not support SAP Web Link (SAP_LONG_URL) applications (the URL of a portal, for example, via which an SAP application in an ABAP application server is started). In this case, create dynamic TBOMs.

End of the note.

Prerequisites

  • You have created a solution documentation. You have assigned test cases and executable entities to the nodes.

  • To create TBOMs semi-dynamically with SCMON, you have ensured the following:

    • SAP Solution Manager 7.2 SPS 1 (ST 720 SP03)

    • Managed system:

      • SAP_BASIS 750 or SAP_BASIS 740 SP14 and SAP_KERNEL 742 Patch Level 310

      • ST-PI 2008_1 SP14 or ST-PI 740 SP04

    For more information about the requirements of Usage and Procedure Logging (UPL), see SAP Note 1828848Information published on SAP site.

    To check whether UPL is set up correctly, perform a BPCA self-check. For more information, see Checking the Prerequisites for Generating Semi-Dynamic TBOMs.

  • To create TBOMs semi-dynamically with UPL, you have ensured the following:

    • SAP Solution Manager 7.2 SPS 1 (ST 720 SP01) or higher

    • Managed system:

      • SAP_BASIS 701 SP10 and Kernel 720 Patch 94, SAP_BASIS 702 SP09 and Kernel 720 Patch 94, SAP_BASIS 703 SP03

      • ST-PI 2008_1_xx_SP12

    For more information about the requirements of Usage and Procedure Logging (UPL), see SAP Note 1828848Information published on SAP site.

    To check whether UPL is set up correctly, perform a BPCA self-check. For more information, see Checking the Prerequisites for Generating Semi-Dynamic TBOMs.

  • You have identified the following special cases and created their requirements. For more information, see Satisfying the Prerequisites for Special Cases of TBOM Recording.

Procedure

  1. To cover the complete executables library, mass-generate static or semi-dynamic TBOMs. For more information, see, Creating Static or Semi-Dynamic TBOMs.

  2. Identify executables which require more precise dynamic TBOMs because they

    • are in business-critical business processes, for example

    • use SAP Web Links, which are not supported by semi-dynamic or static TBOMs

    For more information, see Checking the TBOM Coverage and Status.

  3. Depending on the effort you want to expend, or if no static or semi-dynamic TBOM is supported, create dynamic TBOMs. For more information, see