ActiveControl includes an ‘Inline Conflict’ capability to notify Transport creators – at the point of assigning their object change to a transport in the SAPGUI- if the change conflicts with another change already made to the same content in another development system. This covers both workbench and customizing objects.
When a conflict is detected, the conflicting transports are displayed and the team member is given the opportunity not to save their changes.
When this Inline Conflict Analysis is performed, ActiveControl connects from the current SAP development system to the ActiveControl domain controller, which in turn connects to the other configured SAP development systems to check for conflicting changes. A target SAP system is deemed to be a development system if the target attribute “Show transport requests created in this SAP system within ActiveControl” is enabled.
Inline Conflict Analysis is switched on for the relevant Development systems within table /BTI/TE_ACTIVE in the ActiveControl domain controller.
In order to restrict the systems that ActiveControl checks during the analysis, the relevant entries need to be maintained in table /BTI/TE_INLINE. For example, this could be used to check from the ECC project development system (field SYSID) to the ECC BAU development system only (field CHECK_SYSID). The INACTIVE flag allows specific systems checks to be switched off if required.
In addition to the /BTI/TE_ACTIVE and /BTI/TE_INLINE table configuration, the client to check when connecting to the relevant development system must be specified in the Conflict Analysis Options section of the Conflict/Merge Options target configuration Import Options tab in field “Client to be used during conflict analysis”. This must be done in the target system that is being connected to for the conflict analysis.
(1) Please note that although Inline Conflict Analysis does cover customising objects, it does not cover role changes made via PFCG at the current time.