Which SAP systems to use in a Pipeline
A Pipeline stores the RFC Destinations for the SAP systems that LiveCompare analyses. The systems you assign to a Pipeline’s Analysis, Comparison and Usage systems determine how much of LiveCompare's analysis you can use.
This topic explains which SAP system belongs in each Pipeline role, why that mapping works, and which configurations to avoid. It's for Administrators and Editors who create or edit Pipelines.
Pipeline system roles
A pipeline defines a pathway to production. In most SAP landscapes, that pathway runs from development, through quality assurance, to production:
DEV → QAS → PRD
Assign your SAP systems to the Pipeline roles as follows:
| Pipeline role | SAP system |
|---|---|
| Analysis System | DEV |
| Comparison System | QAS |
| Usage System | PRD |
Why this configuration works
Each Pipeline role does a different job in the analysis. The mapping above gives each one the system that holds the data it needs.
Analysis System
LiveCompare reads your changing objects from the Analysis System. It needs SAP's Where Used indexes and an Object Links Cache database created for that system.
If you point it at DEV, you’ll see the impact of a change while it's still in development - before it reaches QAS, and while there's still time to act on what you find.
Comparison System
LiveCompare compares changing objects and table data between the Analysis System and the Comparison System. Point it at QAS, the next system downstream.
The comparison then tells you what's genuinely new in DEV, relative to what you've already promoted.
Usage System
LiveCompare drives the most-at-risk ranking from a set of used objects. It gets these from the Usage System's performance history data, which comes from the SAP tables behind the ST03 transaction.
Point it at PRD. Production usage reflects what your business actually runs, so the ranking in the Smart Impact app reflects real risk.
Configurations to avoid
Don't shift the Pipeline roles downstream. For example:
| Pipeline role | SAP system |
|---|---|
| Analysis System | QAS |
| Comparison System | PRD |
| Usage System | PRD |
With this configuration, LiveCompare loses two important capabilities:
-
It can't analyze the impact of changes before they land in QAS.
-
It can't optimize impact analysis by tracking daily development.
If you've already configured a Pipeline this way, edit it in the studio or apps interface to move the Analysis and Comparison systems one system upstream.