Show TOC

Procedure documentationCreating TBOMs


A TBOM (Technical Bill of Materials) contains all the objects in an executable entity. The Business Process Change Analyzer uses TBOMs to determine whether an executable entity is affected by a change. To be able to use the Business Process Change Analyzer, create a TBOM for each executable entity in your scenarios, processes and process steps.

To create a TBOM, you have the following options, which are sorted in descending order by their precision:

  • Dynamic:

    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 is complete. The dynamic creation also includes RFC connections and branched GUI user procedures within the same (primary) system, and RFC connections to other (secondary) systems. Further RFC connections to third-party systems are also recorded, but branched GUI processes in secondary or third-party systems are no longer recorded.

    If an executable entity schedules background jobs, the system creates a separate TBOM enhancement for each background job with the objects involved.

    You can create dynamic TBOM enhancements for the following types of executable entities:

    • BSP application

    • CRM Web Client application

    • ABAP Web Dynpro application

    • SAP application URL (SAP_LONG_URL)

    • Program

    • SAP CRM people-centric UI application

    • Transaction

    Note Note

    Generally, completing the executable entities results in 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 which are 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 do not belong to the recorded executable entity.

    End of the note.
  • Semi-Dynamic

    Use Usage and Procedure Logging (UPL) to create a TBOM. As with the generation of a static TBOM, the system analyzes the environment to determine which objects are in the executable entity. They are filtered using the object usage data provided by the UPL function of your system. Only objects which are actually used, are in the TBOM.

    Under UPL Options, the system shows whether UPL data is available for a system.

  • Static:

    Note Note

    You can only create static TBOMs if the user parameter AGS_TBOM_EXPERT for your user has at least the value 3.

    End of the note.

    In static generation, the executable entity is not called. The system analyzes the environment to determine which objects are in the executable entity. You therefore do not require any authorizations in the managed system. Dynamic calls or generated objects are not found, so they are not in the TBOM. The result is not as precise as with dynamic or semi-dynamic generation.

    You can create static TBOM enhancements for the following types of executable entities:

    • BSP application

    • Program

    • Transaction

    If your user parameter AGS_BPCA_TBOM_EXPERT has a value of at least 3, you can specify the branching level during static generation. By default, the branching level is set to 3. Values from 1 to 4 are possible.

Alternatively, send TBOM recording tasks to the business process expert , who creates the TBOMs.


  • You have created a Business Process Hierarchy. You have assigned executable entities to the nodes.

  • Creating TBOMs semi-dynamically, requires the following:

    • SAP Solution Manager 7.1 SP09

    • Managed system:

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

      • ST-PI 2008_1_xx_SP08

    For more information about the requirements for 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.


  1. In the Business Process Hierarchy, open the attributes of the executable entities for which you want to create a TBOM.

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

    2. Under Test Preparation Views, select whether to process projects or solutions.

    3. Select a project or solution.

      The Business Process Hierarchy opens.

    4. Under the business scenario, choose the node whose executable entities you want to process.

    5. On the Transactions tab, select the executable entity to process.

    6. Choose Attributes.

  2. Choose the TBOM tab.

    Note Note

    If the user parameter AGS_BPCA_TBOM_EXPERT has at least the value 1, the TBOM tab page is selected when you open the attribute dialog.

    End of the note.
  3. Check the managed system

  4. You can now either create a TBOM or request one to be created for you.

  5. Choose Create TBOM.

  6. Enter a description.

    By default, the description consists of the following information:

    [Project or solution ID]-[node text]-[component]-[type]-[executable entity name]

    You can change the name.

  7. Choose how to create your TBOM: dynamic, semi-dynamic or static.

    To create a semi-dynamic TBOM, do the following:

    1. Activate UPL in the system. For more information, choose (Info).

    2. To determine the system whose UPL data is to be used, in the UPL System Role field, select the system role.

      Recommendation Recommendation

      To achieve realistic results, use the production system.

      End of the recommendation.
    3. Specify the time range for the data collection. Ensure that it contains the transactions you want to record.

      Example Example

      To cover, for example, period end closing activities, specify a time span of at least two months.

      End of the example.
    4. To reduce the runtime, you can decrease the branching level if needed.

      Note Note

      Define at least three branching levels. If the system does not detect UPL data on the first two branching levels, a static TBOM is created.

      End of the note.
  8. Confirm your entries.

    If you record a static TBOM, the creation of the TBOM is confirmed.

  9. If you record a dynamic TBOM: A dialog with the user name and the name of the executable entity is displayed. Choose Start Recording.

    The executable entity is opened in a new session or browser window.

  10. Perform the required activities in the managed system.

  11. When you have completed the activities, exit the function or close the browser. This ensures that all objects are captured.

  12. Choose Start Recording.

    SAP Solution Manager collects all objects used from the system or systems and then creates a TBOM. After you create the TBOM, a confirmation message appears.


A current TBOM is now assigned to the executable entity.

You can enhance the TBOM.