U.01 - Impacted Used Custom Code

This workflow identifies used custom programs and transactions, and custom smart forms that depend upon SAP-authored objects with significant differences on each of the compared systems. The workflow searches for all objects that are invoked by a custom program, transaction or smart form until the first different SAP object is found, or until the dependency chain is exhausted. Significant differences include SAP authored objects that are different on each system compared, exist in one system only, or are not compared. A complexity analysis is performed for the ABAP code associated with each custom program. Custom Smart Forms from the Source system are also analyzed for their impact on the Target system. The results are stored in three Table datasets, which provide data for the Development Dashboard report and Excel spreadsheet.

This workflow requires that SAP’s where used indices are up to date on the systems being analyzed.

The Prepare Object Links Cache workflow from the Upgrade package should be run before the U.01 - Impacted Custom Code workflow is run against an RFC Destination for the first time, or to update the RFC Destination’s object links database after new support packs or transports have been applied.

Creating RFC Destinations

Before you begin, you will need to create RFC Destinations for each of the SAP systems you wish to compare, and for the system from which to extract performance history data.

In the LiveCompare hierarchy, select the RFC Destination from which to extract performance history data, and click the PHD tab. Enter a value (n) in the ‘Keep this many months of data:’ field, and click ‘Update Data’ to download the most recent <n> months of performance history data. You may also specify a schedule so that the available performance history data is downloaded at regular intervals. See the Retrieving Performance History Data help topic for details.

Preparing the Workflow

To prepare the U.01 - Impacted Custom Code workflow, log in as a LiveCompare Editor and drag its workflow template from the Templates folder into your own workspace. Then modify the workflow as follows:

To specify the Current or As-Is system:

  1. Select the System 1 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 New or To-Be system:

  1. Select the System 2 parameter and view its details in the Property Editor.

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

To specify the system from which to retrieve performance history data:

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

  2. Select the appropriate RFC Destination, then click ‘Save’.

Save the workflow using the ‘Save’ toolbar button.

Running the Workflow

To run the U.01 - Impacted Custom Code 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 any of the following Table datasets and choose ‘View Details’ from their context menus to display the table contents.

  • Impacted Used Custom Code

  • Smart Form Impact

  • Changing Objects Details

These tables are returned to the Run Complete Analysis workflow, and provide data for the Development Dashboard report and Excel spreadsheet.