-
A certain customer was upgrading from 4.0b to ECC6, and wanted to check data integrity. That is, check to make sure that certain critical configuration and master data tables have exactly the same records before and after the upgrade. Normally that's a simple problem for LiveCompare, you just use the...
-
Upgrades are a great time to look again at security provisioning. Natural expansion of authorizations since the last major project or first implementation will likely mean that there is quite a difference between what users have the potential to run and what they actually use or should be using. LiveCompare...
-
I wrote here about using LiveCompare to fully understand the impact of significant SAP changes as part of an upgrade and mentioned that LiveCompare includes a template to identify unused custom code. It’s called U.03 – Unused Custom Code and you’ll find it in the Upgrade Analysis folder...
-
With SAP systems running approximately 30% [1] custom code, it's vital that in preparing for an upgrade consideration is given to how the new version will impact our customizations. LiveCompare includes a dedicated template for analyzing used custom code automatically. It's called: U.01 - Impacted Used...
-
One of the most important concerns of a technical upgrade is how your custom executables are going to behave in the upgraded environment. Custom programs that invoke changed or missing SAP standard objects in the target box can cause runtime failures. Identifying these issues in the early phases of an...