Conigma™ DEVSYNC

Synchronization and collision check for parallel SAP landscapes for project development and maintenance (5-system landscape)

Functionality:

Conigma™ DEVSYNC, Conigma™ DEVSYNC, part of the Conigma™ Suite, has been developed in particular for SAP system landscapes containing parallel development and QA systems, i.e. one for project development another one for maintenance, which needs to be synchronized regularly.  

Conigma™ DEVSYNC calculates the difference between the both SAP systems, which need to be synchronized and displays the result via a graphical user interface (selection criteria such as “displaying all identical objects in the both SAP systems” can be easily defines by the user).

The innovative analysis capabilities of Conigma™ DEVSYNC not only cover ABAP but also are able to deal with Customizing recognizing synchronization issues even for single table entries.

If a customer is using Enhanced CTS (CTS+) for transporting Non-ABAP objects, also these objects will be discovered and added to the object list to be transported into the target SAP system.

To deal correctly with source system dependant SAP BI objects, Conigma™ DEVSYNC contains a special algorithm as well as the corresponding special repack methodology.

To calculate this difference, the user has several criteria, being selected via the graphical user interface – additionally when using Conigma™ CCM, the user is able to switch on powerful filters, for example, only change requests which are part of a specific release, only change requests having a specific status.

Setzt der Kunde The intuitive graphical user interface of Conigma™ DEVSYNC, which is completely integrated in SAPgui, enables a comfortable control of the synchronization process by offering i.e.

• Storing and loading different synchronization configurations – source-, target system, filter options, repack strategy, etc.
  
• Additional criteria for selecting the objects to be analyzed for synchronization needs, i.e. by time period, SAP user, task type or status.
  
• Graphical display of the status of each object after analysis and calculation.
  
• Remote comparison of objects – displaying the source code of the object from target and source system in a split-screen view, highlighting the differences.

After calculating the difference, Conigma™ DEVSYNC automatically generates transport orders for all objects, which have been changed only on one SAP system and imports those into the SAP system needing synchronization. Also collisions are reported and the user needs to decide how to deal with these moving forward.

If necessary and using Conigma™ CCM, it is also possible to automatically attach the generated transport orders to an existing change request or Conigma™ CCM creates a new change request first.

For manual intervention to change the object selection calculated by Conigma™ DEVSYNC, i.e. for adding or removing objects before importing, Conigma™ DEVSYNC provides an intuitive graphical user interface.

Benefits:

Conigma™ DEVSYNC enables a company to significantly reduce the amount of work for synchronization of parallel SAP lines, necessary always, if the company uses in parallel a project/release oriented development methodology on one SAP line and a “continuous development” methodology to do the daily maintenance development for the production line.

Typical application scenarios:

Aus der berechneten Synchronization and collision check for SAP landscapes with parallel development and QA systems

Increasingly more companies develop and maintain their SAP systems, using two different approaches in parallel and having quite often also different teams for the both approaches.

• Release- or project oriented development – a set of new functionality is developed over a longer period of time and transitions into production at a defined point in time
  
• Continuous Development – each single change request or bugfix moves into productive status immediately after completion of development

For implementation of the above approach with two different parallel development methodologies, customers are using a so called 5-system SAP landscape, which have two development systems (one for maintenance development, one for project/release development) as well as two QA systems (again one for maintenance development, one for project/release development) and one production system.

During the development of a project or a new release, Conigma™ DEVSYNC allows at any time for updating the development system for the project/release to reflect the most current status of the production system and to detect and fix problems, typically caused by changing the same objects independently in both development systems, very early in the development cycle. Otherwise these problems may show up earliest, when the project or release is going live. Establishing a development process for a SAP project/release, which guarantees, that the development system always reflect the most current status of the production system also ensures, that moving a new project/release into production(release cutover) is just a matter of a couple of hours and may happen fully automated.