RFUI Impact Analysis

This workflow performs an impact analysis that supports the /SCWM/RFUI transaction. The workflow is provided with a set of transports on the Analysis system, and finds an optimal (most-at-risk) set of executables which when tested will execute each of the transport objects. The analysis is driven by performance history data which is obtained as follows.

1. SCWM functions are extracted from the /SCWM/TSTEP_FLOW and /SCWM/TVALID_PRF tables on the Analysis system.

2. SCWM screens are extracted from the /SCWM/TSTEP_SCR table on the Analysis system.

3. Usage data for the SCWM functions and screens is obtained from UPL data extracted from the Performance History system.

Additionally, step data for functions is obtained from the /SCWM/TSTEP_FLOW table on the Analysis system, and step descriptions are obtained from the /SCWM/TSTEP_CATT table.

The workflow produces a report listing all the functions and screens impacted by the transport objects, and a report listing custom functions found in the transport objects. Objects from this last report are candidates for testing regardless of whether they are used or recommended. The workflow produces a Dashboard report and an associated Excel report.

The RFUI Impact Analysis workflow calls:

• The Get Changing Objects by Transports workflow to retrieve the transport objects to analyze.

• The Get Used Objects from UPL workflow to retrieve used objects from UPL data.

• The Analyze Impact workflow to find a set of Most-at-Risk executables.

• The Summarize RFUI Results workflow to prepare the Dashboard and Excel reports.

• The Get System Info shared template workflow to retrieve system information for each of the analyzed SAP systems.

Before You Begin

Before running the RFUI Impact Analysis workflow, please note the following:

If a support pack or transport has not been applied to the Analysis system. It must be disassembled before it can be analyzed by the RFUI Impact Analysis workflow. This can be done in SAP by running the SAINT transaction and selecting ‘Disassemble OCS Package’ from the Utilities menu. Alternatively, the support pack or transport may be disassembled using the Package Disassembler App.

The RFUI Impact Analysis workflow requires that SAP’s Where Used indexes are up to date on the Analysis system. For further details, see the Step 1 (As-Is) - Checking the Integrity of the Where Used Indexes help topic.

The Create Object Links Cache workflow in the Prerequisites templates folder should be run for the Analysis system to create a cache of object links. See the workflow’s associated help file for details.

Creating RFC Destinations

Before you begin, you will need to create RFC Destinations for the Analysis and Performance History systems. You will also need to make sure UPL data has been obtained for the Performance History system’s RFC Destination. See the Retrieving UPL Data help topic for details.

Preparing the Workflow

To prepare the RFUI Impact Analysis workflow, drag its workflow template from the Templates folder into your own workspace, and modify the workflow as follows:

To specify the system to analyze:

1. Select the Analysis System parameter and choose ‘Edit RFC Destination’ from its context menu to display the RFC Destination dialog.

2. Select the RFC Destination for the system to analyze, then click ‘Save’.

To specify the Performance History system, from which to extract UPL data:

1. Select the Performance History System parameter and choose ‘Edit RFC Destination’ from its context menu to display the RFC Destination dialog.

2. Select the RFC Destination for the system to analyze, then click ‘Save’.

To specify which transports to analyze:

1. Select the Transports parameter and choose ‘Edit Table’ from its context menu to display the Table Editor dialog.

2. Enter one or more transport names from the Analysis system, or paste in a selection of transport names from an Excel spreadsheet, then click ‘Save’.

Save the workflow using the ‘Save’ toolbar button.

Overriding Step Descriptions

To overwrite the step descriptions retrieved from the /SCWM/TSTEP_CATT table in the workflow results, edit the Step Description Overrides Table parameter, and complete the STEP and TEXT columns as appropriate. Alternatively, steps and their replacement descriptions may be provided in an External Data Source that should be read into a Step Descriptions Overrides Table dataset using the Read External Data Source action.

Running the Workflow

To run the RFUI Impact Analysis workflow, click the ‘Run’ toolbar button, choose ‘Run Now’ from the diagram’s context menu, or press F5. The currently running workflow action is marked with an animated display. When the workflow execution has completed, select the Report URL dataset and choose ‘View Details’ from the context menu to access the generated report.

Excel Report

The Excel report generated by the RFUI Impact Analysis workflow includes the following spreadsheets:

SystemInfo

This spreadsheet includes SAP system information for the Analysis and Performance History systems.

Distinct

This spreadsheet includes a distinct list of the most-at-risk objects, including each object’s usage count and its associated transport.

Impacted

This spreadsheet contains a distinct list of the impacted executables, ordered by their usage counts. The IMPACT column is set to:

• R if the object is a most-at-risk executable to test.

• C if this executable is impacted by the transport objects but covered by a most-at-risk executable.

UsageDataSummary

This spreadsheet provides a summary of the usage data obtained by the workflow, showing the usage count for each used object. The IMPACT column is set to:

• R if the object is a most-at-risk executable to test.

• C if this executable is impacted by the transport objects but covered by a most-at-risk executable.

• U if the executable is not impacted by the transport objects.

MostAtRisk

This spreadsheet lists the most-at-risk executables and screens; these are recommended for testing. For transaction codes that have screens, the DYNP_PROG column in this spreadsheet contains the transaction’s associated program name, and the DYNP_NUM column contains the associated screen number. The most-at-risk objects include any new custom functions, and any new functions that are contained in custom transports, along with usage data for the functions if any is found in the retrieved UPL data. The MostAtRisk spreadsheet also includes the following columns:

Column	Description
DATE	The source object’s last modification date.
CHANGES	The number of transports on the analysis system that contain the changing object. This column is set to 0 if a child object is a table used in a view, and only the view is included in the analyzed transports.
FANIN	The source object’s fan-in value. The fan-in value of an object is the number of other objects that are referencing it. Multiple references from the same object are counted as one access.
FANOUT	The source object’s fan-out value. The fan-out value of an object is the number of other objects that are referenced in it. Multiple references to the same object are counted as one access.

MAR_Steps

This spreadsheet lists the most-at-risk executables, including their associated step and step description details.

Extra

This spreadsheet lists any new custom functions, and any new functions that are contained in custom transports, along with usage data for the functions if any is found in the retrieved UPL data.