The SAP HANA Migration Assessment App analyzes the data extracted from an As-Is and To-Be SAP system and reports on the following.
- Impacted Used Custom Code
- Custom Code Quality
- Unused Custom Code
- Used Obsolete Transactions
- Impacted Used Standard Code
- Object Usage
- Impacted Custom and Standard IDOCs
- Impacted Profiles and Authorizations
- SPDD and SPAU Objects
The SAP HANA Migration Assessment App support SAP Business Suite on HANA and SAP S/4 HANA. It also supports SAP kernel releases 620 and above, running on any SAP BASIS or Windows Application Server product from release 620 to 74x.
If LiveCompare is installed at your premises on a server that has access to your As-Is and To-Be SAP systems, an SAP HANA migration assessment may also be performed using the workflow templates installed to the ‘Data/Templates/Upgrade’ hierarchy folder.
Development, Testing, Operations.
Before running the app, follow the steps outlined in the Performing an SAP HANA Migration Assessment topic to load and run the Data Extract program on your As-Is and To-Be systems, and to upload the results into LiveCompare to create LUXes for the As-Is and To-Be systems.
Running the App
To run the SAP HANA Migration Assessment App, select the App from the Apps screen and create an App variant. Set the As-Is LUX field to the LUX uploaded for your As-Is system, and the To-Be LUX field to the LUX uploaded for your To-Be system. Edit the ‘AAQ Select List’ parameter if required to specify the quality scenarios, categories and rules to be used in the analysis. The ‘Upgrade’ scenario is selected by default.
Click ‘Run’. When the variant has completed, its results may be accessed from the App Cockpit screen.
The SAP HANA Migration Assessment App generates a Dashboard report named Upgrade Project, which includes charts relating to the following upgrade activities. Each chart has an associated Dashboard report.
Click any of the following charts to display the Development Dashboard Report.
- The Used Standard vs. Used Custom pie chart displays a usage summary for the used standard and custom code objects on the As-Is system.
- The Used vs. Impacted Custom column chart summarizes the used and impacted custom code objects.
- The Used vs. Unused Custom pie chart displays a usage summary for the used and unused custom code objects on the As-Is system.
- The SPDD & SPAU column chart provides a summary of the SPDD and SPAU objects that may need to be adjusted following a migration.
- The Good, Bad & Ugly pie chart provides a summary of the custom code on the As-Is system, grouped by code quality.
- The Custom Code Quality column chart provides a summary of the quality rule violations in the custom code, grouped by rule type. The number of objects with quality rule violations in each rule category is reported.
- The Application Area Impact column chart provides a summary of the impacted standard and custom code objects, grouped by Application Area. Click this chart to display the Testing Dashboard Report.
- The Impacted Interfaces column chart provides a summary of the impacted standard and custom IDOCs, showing the number of segments that are added in the As-Is system, deleted in the To-Be system, and different in each of the systems. Click this chart to display the Integration Dashboard Report.
- The Impacted Roles column chart displays the number of roles impacted by the migration. These roles have authorization objects that have been either added or removed on the To-Be system. Click this chart to display the Security Dashboard Report.
The Used Obsolete Transactions pie chart summarizes the used obsolete transactions on the To-Be systems, indicating the number of transactions that are obsolete (without a replacement), and the number of transactions for which a replacement transaction is available on the To-Be system. Click this chart to display the Training Dashboard Report.
The Dashboard report also includes links to the following Excel reports.
Analysis Input Data
This Excel report contains a copy of the input parameters used to produce the App’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.