Quick Distributed Development
SAP systems are often mission critical. They support ongoing core operations of the companies that rely on them.These companies need to be able to support their production systems at all times, which includes addressing critical bugs and urgent enhancements in a timely manner.Stopping the process of production support for any extended period of time is usually not an option.Unfortunately many those same companies have a need to perform major transformations and upgrades of these SAP systems as they need to ensure that their systems keep up with the ever changing and accelerating pace of business. This includes SAP software upgrades to the latest available versions of the software like Suite on HANA or S/4. These upgrades and transformations are usually major projects that require many months to conduct, test, and deploy successfully.
While these transformation projects are ongoing the companies need to continue to support their production environments. They implement bug fixes and enhancements in a separate environment and release them directly to their production systems as needed.Unfortunately this creates a problem, as the bug fixes and critical enhancement do not automatically appear in the project environment. Unless they are recreated within the project these changes would get lost once the project goes life.
In response to this most SAP customers try to minimize the number of large, longer running projects they conduct, and they implement a manual process of tracking and re-implementing the production changes during the course of the project.This manual process, sometimes referred to as “retrofitting”, is laborious and prone to human error.What if there was a way to automate this process and ensure that 100% of the bug fixes get correctly applied to the project environment without human intervention?
Software changes are done in one system and will be transported to the system landscape which is linked to this system. But sometimes it is necessary to implement these changes into another system landscape without using the import function of the transport requests. Imagine you want to implement a new functionality. You will use a second development system to work on this new implementation, because you don’twantto disturb the maintenance of the system being done in the original development system.
Retrofit is used to synch transports across landscapes, maintain transport dependencies and automate import of transports into landscapes. It reduces testing risk, timelines and defect cycles by ensuring dual maintenance changes are consistently applied to your landscape.
smartRetrofitsupports dual maintenance using an automated solution that can be run as a stand-alone or as an add-on to SAP Retrofit. Each change request implemented in the source (or upper) landscape is synchronized with the target (or lower) landscape with automated merges. The solution automatically merges the code and supports auto-import of the changes during standard Retrofit processby eliminating conflicts due to technical changes. It also provides Web-UI based smart comparison and merge features for developers to handle the actual “conflicts” by remediation.
What are the steps to be taken in the retrofit process? First aconflict analysis is performed by comparing source and target custom objects to classify objects asequal code, non-equal code, existing only in source system or existing only in target system. Then the solution handles various retrofit categories, re-defines the conflict status and converts every transport into auto-importable transports.smartShift’s Retrofit solution eliminates the manual work involved in dual maintenance. It mitigates the risk of development environments getting inconsistent, especially during a long running project requiring multiple parallel development releases.The solution is unique in its capability to support heterogeneous development environments, for example, performing retrofit between non-HANA and HANA environment.
While dividing development tasks improvesefficiency and maintaining multiple systems reduces production risk, it becomes a complex undertaking to merge these changes. Resolving any inconsistencies between systems in a risk free manner by using automated tools can help ensure a quick and efficient process.