ShiftLeft: Conflict Analysis (0005) analyser has long been a popular ActiveControl analyser for helping SAP customers with parallel development tracks identify conflicts, ie where Developments in one development track are making changes to the same objects as the parallel development track(s).
Figure: Conflict Analysis in a Merge scenario (#1) and in a non-Merge cutover scenario (#2).
Regardless of a customer’s ActiveControl setup (ie if they are using 1-way merge or 2-way merge), prior to ActiveControl 9.10, the existing Conflict Analysis (0005) could only be run at the point of either merging or deploying into the target Development system. In recent years, growing numbers of Basis Technologies customers’ have requested the ability to run 0005 Conflict Analysis in a non Development target.
The most common use-case is for customers using 1-way Merge that deploy original project transports into their target Production Support (Business As Usual) landscape – instead of using ActiveControl Merge. In many instances, these customers do not cutover their Projects into the Development target, but instead into a shared pre-production system – or indeed the Production system itself. In those scenarios, the customers could not fully benefit from ShiftLeft: Conflict Analysis (0005) since it did not fully identify conflicts in the Pre-Production system or Production system.
ActiveControl 9.10 introduces an enhanced Conflict Analysis (0005) so it is now possible to run the Analyser in a non-Development target. This means customers can identify conflicts in the scenario where they cutover to Production or Pre-Production, and do not first deploy to Development.
Figure: Example of 0005 being run in a non-Dev target – in this case a Production Inbox – to highlight Conflicts with transports containing same objects in parallel Development track.
Please refer to this online Change Note for details on the configuration of this new capability as part of the existing ShiftLeft: Conflict Analysis (0005) analyser.