• Upgrading and Moving to a New LiveCompare Server

    An in-place upgrade to a new version of LiveCompare is straight forward: Uninstall the old version. Install the new version The uninstall preserves all userdata and the new version will take care of any necessary upgrades to the userdata, such...
  • SAP Upgrade: User Tcode Analysis

    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...
  • SAP Upgrade: Unused Custom Code

    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...
  • SAP Upgrade: Impacted Used Custom Code

    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...
  • Using the Make Hierarchy Action

    Here are a couple of example workflows that have been modified to include the 'Make Hierarchy' action allowing users to be able to drill down through their results. The modified workflows are the U.01 Impacted Used Custom Code (Upgrade Template...
  • Capture Now, Compare Later

    Author's Note: Since this post was originally written, LiveCompare 2.5.1 has been released. This new version of LiveCompare uses an internal database engine rather than SQL Server, and it also contains a new feature called Data Stores. So while the...
  • Managing "U1 - Impacted Used Custom Code" Results

    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...