Daily FOL

LiveCompare’s smart impact apps and workflows use a tree of SAP object dependencies to help determine which objects are most at risk on an Analysis System and therefore recommended for testing. LiveCompare stores the dependencies for each Analysis System in a database on the LiveCompare server.

The Daily FOL workflow updates an Analysis System’s dependencies database to include dependencies for objects from transports that have changed in the last specified number of days. (excluding SAP-delivered transports). The dependencies database allows LiveCompare’s smart impact apps and workflows to run in Express or Standard mode, based on whether their changing objects are already in the dependencies database.

For example, the Smart Impact app works like this:

  • If the app’s changing objects are all in the dependencies database, the app runs in Express mode. Its Find Object Links (Read Only) action reads the dependencies database directly and doesn’t need to connect to SAP to find any object dependencies.

  • If the app’s changing objects aren’t all in the dependencies database, the app runs in Standard mode. Its Find Object Links (Read Only) action connects to SAP to find the missing dependencies.

The Find Object Links (Read Only) action typically runs much faster in Express mode.

To keep an Analysis System’s dependencies database up-to-date, schedule the Daily FOL workflow to run each night.

Prerequisites

The Daily FOL workflow uses a pipeline to identify the SAP Analysis and Usage systems. The workflow uses the Analysis System to create or maintain a dependencies database, and the Usage System to provide used objects to the Find Object Links action.

To set up the Daily FOL workflow, you need to prepare the following things:

  • Create a pipeline for use by the Daily FOL workflow, specifying an Analysis System and a Usage System.

  • Make sure performance history data is available for the pipeline’s Usage System in its PHD tab.

  • Run the Create Object Links Cache workflow from the Prerequisites templates folder using the pipeline.

Prepare the workflow

To prepare the Daily FOL workflow, follow these steps:

  1. Drag its workflow template from the Templates > Impact Analysis folder into your own workspace.

  2. In the workflow, set the Pipeline parameter to the pipeline you created in the Prerequisites section.

  3. Set the Number of days parameter to search for transports that users have changed over the specified number of days. The default value is 7.

  4. Select Save tool button. to save the workflow.

Run the workflow

To run the Daily FOL workflow, select the Run tool button. toolbar button or Run Now from the diagram’s context menu, or select F5. LiveCompare marks the current action with an animated display.

Check the results

Once the workflow has finished, you can check its results. The workflow’s Detailed Tree of Links dataset contains a set of object links, and its Result dataset contains a set of changing objects and the objects that reference them, either directly or indirectly. The workflow also creates or updates the dependencies database for the pipeline’s Analysis System with objects from transports that users have changed in the last specified number of days.

Schedule the workflow

We recommend that you schedule the workflow to run each night. This keeps the Analysis System’s dependencies database up-to-date with dependencies for objects from transports that users have changed in the last specified number of days.. To do so, follow these steps:

  1. Right-click the Daily FOL workflow in the Workflows hierarchy and select Schedule Run from the context menu.

  2. Specify a daily schedule in the Run Workflow screen. Set the workflow to run after office hours.

  3. Select Schedule Run.