Show TOC

Procedure documentationAnalyzing Business Processes Affected by Changes Locate this document in the navigation structure

 

You can use this analysis to check whether a process structure is affected by specific changes. You can precisely specify both the relevant parts of the process structure and the relevant changes. The result of the analysis is a list of the affected nodes in the process structure. You can use the result to create test plans to retest the affected scenarios, processes or process steps after the change.

Prerequisites

You have created TBOMs for all executable entities in your process structure.

You have ensured that the TBOMs are up-to-date. You only get correct and reliable analysis results if the TBOMs are up-to-date.

For more information about identifying errors or out-of-date TBOMs, see Checking Business Process Status.

You can update TBOMs in the following ways:

  • You can re-record or recalibrate TBOMs. For more information, see Checking Whether a TBOM is Up-to-Date.

  • You can schedule a background job. For more information, see the Customizing for   SAP Solution Manager under   Capabilities (Optional)   Business Process Change Analyzer  .

Analysis Results with Out-of-Date TBOMs

You can also run analyses with TBOMs that have the status Out-of-Date. This status is simply used to identify TBOMs that are potentially out-of-date (see Checking Whether a TBOM is Up-to-Date). However, the analysis results are generally accurate. An out-of-date TBOM can only produce inaccurate analysis results in the following special cases:

  • An influence is not identified although the analyzed changes do affect objects of a program flow.

    This can occur when an object contains too few objects. New objects have been added to the program flow since the TBOM was last updated. The planned change affects only these new objects.

  • An influence is identified although the analyzed changes do not affect the program flow.

    This can occur when an object contains too many objects. Objects have been removed from the program flow since the TBOM was last updated. The planned change affects only these objects that are no longer relevant.

Both of these special cases occur very rarely since a change generally affects not only the deleted or new objects, but also older objects already contained in the out-of-date TBOM.

Procedure

  1. Expand the information area Change Impact Analysis.

  2. Under 1., select the type of analysis that you want to run. There are the following scope types:

    • Support Packages/ Support Package Stacks: This option offers a basic selection of support packages. The support packages must have been installed in the managed system using the SAP Maintenance Optimizer.

    • Enhancement Packages: This option offers a basic selection of support packages and enhancement packages. The delivery transports must have been installed in the managed system using the SAP Maintenance Optimizer.

    • Planned Activation of a Business Function: You can select business functions and check which parts of business processes will be affected, before activation. You can either select the business functions directly from the managed system or use the business function scope of a project or solution as the source. Prerequisite for the use of this function is that the managed system has at least one of the following software statuses:

      • SAP NetWeaver Enhancement Package 1: Support Package Stack 06

      • SAP NetWeaver Enhancement Package 2: Support Package Stack 02

      • SAP ERP 600 Enhancement Package 4: Support Package Stack 06

      • SAP ERP 600 Enhancement Package 5: Initial delivery

      • SAP CRM 7.0 Enhancement Package 1: Initial delivery

    • Transport Requests: You can select any transport requests from a managed system.

    • Object List: You can directly enter and analyze the objects that you are planning to change.

    • Change Transaction: You can analyze the impact of change transactions from Change Request Management.

  3. Under 2., specify the system and client in which you have or plan to make the change. If you are analyzing change transactions, select the type of change transaction here.

  4. Under 3., enter details of the change that you want to analyze (for example, the number of the transport request, the number of the change request, or the names of objects).

  5. Under 4., specify which projects or solutions you want to analyze. You can use the following parameters:

    • Project: Choose this option if you want to analyze projects only. In the Project ID field, you can restrict the projects further. If you do not specify a project ID, all projects are analyzed.

    • Solution: Choose this option if you want to analyze solutions only. In the Solution ID field, you can restrict the solutions further. If you do not specify a solution ID, all solutions are analyzed.

    • Project/Solution: Choose this option if you want to analyze both projects and solutions. In the Project ID and Solution ID fields, you can restrict the selection further. If you do not specify a project ID or solution ID, all projects and solutions are analyzed.

  6. Under 5., enter a description for the analysis.

  7. Optional: To specify additional optional parameters for the analysis, choose Details under 6.. You can use the following optional parameters:

    • Location of Test Cases: You can specify in which system you manage your test cases. You have the following options:

      • If you do not manage your test cases centrally, you can select the system role of the system in which you manage the test cases. If you manage your test cases centrally, this selection has no effect.

      • If you use partner tools to manage test cases, you can select the partner tool used. If you choose Test Organizer, the system only takes into account test cases from SAP systems.

    • Filter Options for Business Process Nodes

      • Node Type: You can restrict the nodes to be analyzed to a certain level or business process hierarchy.

      • Logical Component: You can restrict the analysis to executable entities that are assigned to a specific logical component.

      • Test Cases: You can select whether you want to analyze nodes with test cases, nodes without test cases, or all nodes.

      • Extended Parameters: If you have assigned attributes to nodes in the business process hierarchy, you can use these attributes to restrict the nodes for the change analysis. See Assign and Lock Attributes for further information.

    • Filter Options for TBOMs

      • TBOM Item Criticality: You can specify whether you want to restrict the analysis to objects with a specific weighting.

      • TBOM Usage: You can select whether you want to use only dynamic TBOMs, only static TBOMs, or all TBOM types for the analysis.

    • Filter Options for Executable Units: You can specify further parameters to restrict the executable entities that are relevant for the analysis. You can use the following parameters:

      • Only in scope: You can use this checkbox to restrict the analysis to those nodes that are defined as In Scope in the Business Blueprint. For more information, see the Transactions tab.

      • You can also specify additional filter criteria for each type of executable entity.

  8. To start the analysis immediately, choose the Execute pushbutton.

  9. To start the analysis at a later time:

    1. Choose Schedule.

    2. Select the starting point and confirm your entries.

    The result ID is displayed at the top of the screen; you can find the analysis results using this ID.

  10. Refresh the results list so that you can select your analysis results.

    Scheduled analyses that have not yet been executed are also included in the results list. The scheduled start date and scheduled time of these analyses are displayed. After this time, you can access the analysis results in the same way as the other analyses.

Result

You have carried out the analysis. You can evaluate the analysis results and create test plans from the analysis results.