Blog template Banner

IntelliCorp Blog

3 Ways to Prevent Production Failure Using LiveCompare

3 Ways to Prevent Production Failure Using LiveCompare


Hello and welcome to the IntelliCorp blog. Today we discuss three ways to prevent production failure by using LiveCompare to ensure systems are kept in synch.

 

LiveCompare helps you ensure business continuity and zero defects when promoting changes to production SAP instances.


Defects, rework and hyper-care periods are eliminated, so you can give that time back to the business.


So how can we use LiveCompare exactly? And which apps should we run?


1. Run LiveCompare Before You Start A Project

 

Run LiveCompare before you start a project to ensure your project stream is a complete copy of production. There must be no differences between the two environments. Simply connect your Business as Usual (BAU) and project streams, and hit run to automatically compare the following:

 

  • Compare Objects and Compare Objects Advanced - These workflows compare a selection of objects (or use the Compare Objects App).
  • Compare IMG Configurations - This workflow identifies differences in IMG configurations on the two systems (or use the Compare IMG App).
  • Destination to Source Object Transport Comparison – This is a transport comparison workflow. For a set of objects, this workflow finds the transports that contain the objects on the source system (Development) and the target system (Production). It helps you to keep the transports synchronized by identifying:
    • The transport objects that are in synch on the two systems.
    • The transport objects that are newer on the Development system.
    • The transport objects that are newer on the Production system.
    • The latest transports that include the objects on the Development system.
    • The latest transports that include the objects on the Production system.
    • Each of the transports that include the objects on the Development system.
    • Each of the transports that include the objects on the Production system.

 

run LiveCompare Before You Start A Project

2. Run LiveCompare When You Implement Emergency Business Requirements


Run LiveCompare when you implement emergency business requirements.

 

Once these move through DEV and QAS in your BAU stream, run LiveCompare to identify any differences in objects and configuration before they are promoted to PRD.


This is easy to do in LiveCompare using the transport comparison app. This app will automatically identify all differences between project and BAU environments.

 

Run LiveCompare When You Implement Emergency Business Requirements image1

Also use LiveCompare’s Impact App to identify impacted objects, comparing them on the Development and QA systems.

 

Run LiveCompare When You Implement Emergency Business Requirements image 2

 

Run LiveCompare When You Implement Emergency Business Requirements image 3

3. Run LiveCompare one Final Time Before Promoting Change


To ensure zero defects at go-live, run LiveCompare a final time before promoting change to your project PRD system. This will ensure that there will be no transport overwrites. The Release Assurance App is used here to find any objects that are missing from the Production system, and objects that have changed between the QA and Production systems.

 

Run LiveCompare one Final Time Before Promoting Change image 1

Release Assurance generates the following reports:


ChildObjects


This report lists all the objects that the source objects depend on and which are:

 

  • Different between QAS and PRD
  • Not included in the source transports


Promoting the source transports to production will at best halt the release (import errors) and worse result in production defects.

ParentObjects


This report lists all the objects that depend on the source objects and which are:

 

  • Different between QAS and PRD
  • Not included in the source transports


As with the different child objects, promoting the source transports to PRD will at best halt the release and at worse result in production defects.


Compared Child Objects


This report includes comparison details for the child objects.

 

Run LiveCompare one Final Time Before Promoting Change image 2

Compared Parent Objects


This report includes comparison details for the parent objects.


Case Study Example


A customer we work with has eliminated the need for an N+1 landscape. That’s correct, they use just one stream and every change takes place in their main path to production. They are able to maintain this landscape because they use LiveCompare to proactively analyze the impact of SAP application change. LiveCompare tells them what to test, why and what will break. They can fix problems fast, before go-live. LiveCompare enables them to adopt an agile approach to SAP application change management and increase release frequency by 40%. They have ZERO DEFECTS when they go live with change to support business innovation.

 

eliminate n1 instances using livecompare


Want to find out more about using LiveCompare for dual maintenance? Contact us today to book a demo.


SHARE THIS STORY | |