This document provides an overview and agenda for a webinar on REALTECH's SmartChange solution for automated DevOps for SAP S/4HANA projects. REALTECH is introduced as an expert in SAP migrations and transport automation tools. The SmartChange suite is described as providing change process management, transport management, and synchronization management capabilities to automate SAP development processes. Key features of the transport management and synchronization management modules are highlighted. A demo of the SmartChange solution is included on the agenda.
12. “When our development environments get out of sync, it takes hours to find and fix all the
discrepancies. There must be a better way!”
“I have a transport with 1,000 lines of code. I need a quick way to see the difference
between Production Support and Project Dev. “
“When retrofitting a bug fix to my development environment, I overwrote weeks worth of
work and now my release is late.”
8/26/2019
SmartChange Suite – Synchronization Management
Main pain points with manual synchronizations!
13. Workbench and Customizing changes
Compares in real time
Tracks the status of all objects and versions
View differences in a split screen
Automatically retrofit changes
Record retrofit activity for audit and reporting
Synchronization Management Module
8/26/2019
SmartChange Suite – Synchronization Management
14. Why Synchronization Management?
• 5 box model
Synchronization needed between DEV N and DEV N+1, because
• Re-applying bug fixes ensures that bugs will not become alive again after release roll out
• Re-applying all other object changes allows developers on DEV N+1 to operate on the most recent objects and thus
becoming aware of e.g. interface changes as soon as possible
Development
Quality Assurance
Production
DEV N+1
QAS
DEV N
QAS
PRD
Bugfixing &
Optimization
Bugfixing &
Optimization
Sync
November 20, 2013
8/26/2019
16. Details
Export
Analysis
Categorization
Recommendation
1
2
3
4
Every transport request that is exported from N (or imported into)
DEV N, will be recognied automatically and queued for further
processing …
The objects of the queued transport requests will be analyzed with
regard to wether they were also changed on DEV N+1 or not …
Based on the analysis result, each object will be catgorized into
critical / not critical …
The final result is a recommendation for how to synchronize an
object – via transport request from DEV N or manually …
If all objects of a DEV N request can be synchronized via transport,
this DEV N request can be applied to DEV N+1 with just 3 clicks.
If only some of the objects of a DEV N request can be synchronized
via transport, Synchronization Management allows to create a new
transport request on DEV N, that only contains the „non-critical“
objects. Direct navigation for all objects into delta view & split
screen illustration is also provided.
8/26/2019
17. What objects are covered?
Workbench Objects
•Full functionality for all versionable object
types
(A list of all versionable objects can be
generated through report RSVCDI00)
•For non versionable objects, we can check
if the object only exist on one of the 2 DEV
Systems. Currently, we cannot provide
information about equalness…
Customizing
•Tables, Views, View Clusters and logical
Objects are compared by adapting SAP‘s
cross customizing viewer technology. This
allows high performance comparision of
mass data.
•Comparision is done on table record level.
8/26/2019
1) Export
Keine Prozessänderung für die Entwickler von der Objektänderung bis zum Export
2) Automatische Analyse aller Workbench- und Customizing-Änderungen
Die zuletzt exportierte Version auf DEV wird mit der aktiven Version auf DEV‘ verglichen.
3) Automatische Kategorisierung
Jedes Objekt erhält einen Status, z.B. Objekt existiert nich auf DEV‘, Objekt wurde nur auf DEV geändert, Objekt wurde auf beiden Systemen geändert.
4) Empfehlung der optimalen Synchronisationsmethode
Das Ergebnis der Kategorisierung ist eine Empfehlung, ob ein Objekt per Transport abgeglichen werden darf oder manuell abgeglichen werden sollte.