ActiveControl Merge works according to the following high-level process:

1) The original transport(s) are imported to the target development system.

2) A Merge transport (Transport of Copies) is created (not imported) in the target development system.

3) All of the objects in the original transports are put into the new Merge TOC

4) That new merge transport is then released and moved down the target landscape.


When should we Merge in the process?

ActiveControl flexibility allows customers to Merge at any point in the development lifecycle. This could be after Development, after QA, after Production etc.

In most cases, Basis Technologies’ customers choose to Merge to the project development stream after they have been imported into the Production system, otherwise there is a risk that the project will introduce changes that the business is either not ready for or do not want, when it goes live.

To this end, it is necessary to add the target for the project development system to the transport path for the Production Support development stream. The project development system must appear as a child of the Production system. Once changes are applied to the Production system, they will flow to the import queue of the project development system and will be automatically analysed to determine whether the changes can be applied automatically (as described further on the next page).


Configuration Steps

Detailed information on how to configure ActiveControl Merge can be found in this online FAQ article

There are many different options (eg 1:1 Merge versus Consolidated Merge, Merging to original Business Task versus a single central Business Task etc) that are best discussed with a Basis Technologies consultant.

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment