You can create static or semi-dynamic TBOMs for the executable entities in your SAP Solution Manager projects or solutions.
In case of static TBOMS the system analyzes the environment to determine which objects are in the executable entity.
If your system supports Usage and Procedure Logging (UPL), you can create TBOMs semi-dynamically. In addition to using the environment information the objects are filtered using the object usage data provided by the UPL function of your system. Only objects which are actually used are in the semi-dynamic TBOM.
You have created a Business Process Hierarchy.
You have assigned executable entities to the nodes.
You have created background RFC connections to the managed systems in your system landscape.
In the Test Management work center, choose
.In the Project/Solution Selection Options group box, do the following
Specify whether the TBOMs are to be created only for projects, only for solutions, or for both projects and solutions.
Specify the projects and solutions for which you want to create static or semi-dynamic TBOMs.
Note
If you leave the Project ID or Solution ID fields empty, the system creates TBOMs for all projects or solutions.
Select the system role.
To display the systems associated to the system role, choose Show systems from which TBOMS are created.
Alternatively, you can use the SOLAR02 configuration role of a project or the leading/navigation role of a solution.
Specify the scope of TBOM creation:
Only update obsolete TBOMs
Create missing TBOMs.
This option creates TBOMs for all executable entities for which there is no TBOM.
Update all static or semi-dynamic TBOMs, and create missing ones
This option creates missing static or semi-dynamic TBOMs, and updates all existing ones. If there are both dynamic and static enhancements for a TBOM, only its existing static enhancements are updated, no new static enhancements are created.
Adapt the branching level, if required.
For semi-dynamic TBOMs, use the default value 999.
For static TBOMS, begin with the default value 5. If the TBOMs are created quickly, increase the value. if the TBOM creation takes too much time, decrease it.
If your system supports Usage Procedure Logging (UPL), to achieve more precise results, do the following:
Select the Create Semi-Dynamic TBOMs checkbox.
To determine the system whose UPL data is to be used, in the UPL System Role field, in the UPL group box select the system role.
Recommendation
To achieve realistic results, use the production system.
Specify the time range for the data collection. Ensure that it contains executions of the transactions you want to record.
Example
To cover, for example, period end closing activities, specify a time span of at least two months.
To check the availability and quality of UPL data for the systems involved, choose Show systems where UPL data is retrieved.
If the gaps are too large, objects may be missing in the UPL data and therefore in the TBOMs.
If no UPL data is available, perform a BPCA self-check. For more information, see Checking the Prerequisites for Generating Semi-Dynamic TBOMs.
To reduce the runtime, you can decrease the branching level if needed.
Note
Define a branching level of at least 3. If the system does not detect UPL data on the first two branching levels, a static TBOM is created.
Run the program.
Recommendation
Schedule the program as a background job.
If errors occur during the TBOM generation, perform a BPCA self-check. For more information, see Checking the Prerequisites for Generating Semi-Dynamic TBOMs.
In the Static and Semi-Dynamic TBOM Generation Job Search group box, display the status of the job.
Static or semi-dynamic TBOMs are created or updated, for the selected projects and solutions.
The generation is logged in the SAP application log (transaction SLG1) for the object BPCA_RESULT.