Match
This workflow identifies standard SAP programs on the specified Source system that match used custom executables retrieved from a system containing performance history data. A match between two objects is determined by the similarity of their code and their links to common child objects.
The report produced by the workflow shows standard SAP programs that have more than a given percentage of common children on the Source and Performance History Data systems. The default percentage is 50%, however this may be changed by adjusting the value of the workflow’s Match Percentage Threshold parameter.
The results are displayed in a Dashboard report which includes a link to an associated Excel report.
Prerequisites
The Create Object Links Cache workflow from the Prerequisites templates folder should be run for the Source system to create a cache of object links, or to update the RFC Destination’s object links database after new support packs or transports have been applied. See the workflow’s associated help file for details.
Creating RFC Destinations
Before you begin, you will need to create RFC Destinations for the Source SAP system, and for the Performance History system from which usage data for executables is obtained.
In the LiveCompare hierarchy, select the RFC Destination from which to retrieve 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 Match workflow, drag its workflow template from the Templates folder into your own workspace, and modify the workflow as follows:
To specify the Source system to analyze:
-
Select the Source System parameter and choose ‘Edit RFC Destination’ from its context menu to display the RFC Destination dialog.
-
Select the RFC Destination for the system to analyze, then click ‘Save’.
To specify the system from which to retrieve performance history data:
-
Select the System 1 parameter and choose ‘Edit RFC Destination’ from its context menu to display the RFC Destination dialog.
-
Select the RFC Destination which to retrieve performance history data, then click ‘Save’.
Save the workflow using the ‘Save’ toolbar button.
Running the Workflow
To run the Match 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.
Dashboard Report
The Dashboard report generated by the Match workflow includes a column chart which shows the number of similar objects found for each matching program. By default, a program is considered to match on the Source and Performance History system if it has at least 50% of its child objects in common.
Additional Resources
The Additional Resources section of the Dashboard report includes links to the following report:
FindSimilarObjects
This CSV report includes the following columns.
| Column | Description |
|---|---|
| TYPE | This column is set to PROG. |
| NAME | The name of a used custom program with at least the specified percentage of common objects on the Source and Performance History systems. |
| FOUND_TYPE | The type of a similar standard SAP object. |
| FOUND_NAME | The name of a similar standard SAP object. |
| UW_COUNT | A count of the program’s used objects. |
| UW_SAME | The number of used objects that are the same on the Source and Performance History systems. |
| NAME_LENGTH | The number of characters in the program name. |
| FOUND_NAME_LENGTH | The number of matching characters in the program name and similar object name. |
| NAME_IN1 | The number of characters in the program name only. |
| NAME_IN2 | The number of characters in the similar object name only. |
| CODE | The number of code lines that are common to the custom program and the similar object. This column is left blank if UW_SAME is less than one half of UW_COUNT. |
| FOUND_CODE | The number of code lines that are common to the custom program and the similar object. This column is left blank if UW_SAME is less than one half of UW_COUNT. |
| IN1 | The number of code lines in the custom program that are not in the candidate similar object. This column is left blank if UW_SAME is less than one half of UW_COUNT. |
| IN2 | The number of code lines in the similar object that are not in the custom program. This column is left blank if UW_SAME is less than one half of UW_COUNT. |
| UW_PERCENTAGE | The number of used objects common to the custom program and similar object, as a percentage of the number of used objects in the custom program. |
| CODE_PERCENTAGE | The number of code lines common to the custom program and similar object, as a percentage of the number of code lines in the custom program. |
Analysis Input Data
This Excel report contains a copy of the input parameters used to produce the workflow’s Dashboard report. The value of each input parameter is stored in a separate worksheet, which is named after the parameter whose value it contains.