Show TOC

Procedure documentationCreating TBOMs Locate this document in the navigation structure


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.

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.


  1. In the Business Process Hierarchy, open the attributes for 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 the project or solution you require.

      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:

      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 WebClient 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 accoutn 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.
    • 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 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.

  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: Schließen Sie den Modus oder den Browser. This ensures that all objects are captured.

  12. Choose Start Recording.

    The 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.