Smart Impact and SAP HANA Migration Assessment App Differences
The Smart Impact and SAP HANA Migration Assessment Apps (in particular the SAP HANA Migration Assessment App’s Impacted Custom Code workflow) use different algorithms to calculate the impact of change on a set of used objects. For this reason, an analysis of the same SAP systems by each App is unlikely to produce exactly the same results (although the results are likely to be of a similar order of magnitude). When comparing the Apps’ results, it is important to consider the differences in the inputs to each App:
Performance History Data
It should be possible to run the Smart Impact and SAP HANA Migration Assessment Apps with the same set of performance history data. However, there may be some differences in the available performance history data if the Apps are run at different times.
Changing Objects
The SAP HANA Migration Assessment App considers complete systems. However, the Smart Impact App uses a set of changing objects obtained from transports, ChaRM change requests or an object list. These two sets of ‘changes’ are unlikely to be the same.
The SAP HANA Migration Assessment App uses a top-down approach, starting with the used objects and then drilling down into the implementation until they find something that has changed. The Smart Impact App uses either a top-down or bottom-up approach (starting with the changing objects), depending upon the number of changing objects found by the App.
Searching for Objects
The SAP HANA Migration Assessment App stops searching for objects when it reaches the SAP layer. It never searches deeper than the first set of SAP-authored objects that are used by custom code. This means that if an SAP-authored object has not changed, the custom objects that use it will not be marked as impacted. This approach is based on the idea that in upgrades, low level changes that are significant affect the 'surface' SAP-authored objects used by custom code.
By contrast, the Smart Impact App continues searching through the network of SAP-authored objects until it reaches the end of the call chain, as determined by LiveCompare’s smart impact analysis system.
As an example, suppose you have a custom object C that depends on a standard SAP function module F, which in turn depends on a changing SAP table T. The Smart Impact App will report C as impacted, but the SAP HANA Migration Assessment App will not.
Dashboard Charts
The SAP HANA Migration Assessment and Smart Impact Apps each present different Dashboard charts for their impacted code. The SAP HANA Migration Assessment App’s Used vs. Impacted Custom chart displays the used custom objects, and the impacted custom objects (both used and unused). The Smart Impact App’s Used, Impacted & Most-at-risk chart displays the used and impacted objects (showing the number of standard and custom objects in each category). The Most-at-risk column in the chart shows the number of standard and custom objects that are recommended for testing, however this data is not available to the SAP HANA Migration Assessment App.