This sets the transport target for merge requests created by ActiveControl, allowing merge transports to be handled via a different transport route if required. If not set the default value from TMS will be used.
Select whether you want one merge transport for every originating transport (1:1), a big one with everything (Consolidated) or one per import run (By Import Run)
Select which path the Transport Forms for the merges will be created. Leave it blank if you want to create them manually.
Select which Type you want Merge Transport Form to be allocated to. If not set, the merge will get the type of the first transport merged.
Select which Group you want for the Merge Transport Form to be allocated to. If not set, the merge will get the group of the first transport merged.
Stop on BW post-processing error
This option controls whether Merge process will stop or continue when BW postprocessing fails
Select which Task the Transport Form should be associated with. If not set, the merge will get the task of every transport merged.
Controls whether ActiveControl Merge should stop, continue or skip any other errors encountered during the Merge process.
For 1:1 merges automatically copy over Transport Form manual step details
Check if you want Manual Steps to be added in the Merge Transport Form in 1:1 merge scenario; it not relevant to the Consolidated Merge scenario.
For 1:1 merges make the merge transport form owner the same as the original owner
The default behaviour of ActiveControl is to assign Merge TOCs to the AC_RFC user. If this configuration option is switched on, then the Merge TOC will be assigned to the owner of the original source transport in the 1:1 Merge scenario.
These options allow you to apply various unconditional modes to all transport requests imported into this target system.
Pre-import logical command
ActiveControl supports transporting between SAP systems that do not share common underlying transport directories.
Before importing a transport request, ActiveControl checks whether the required transport files are available and, if not, automatically copies the files to the target transport directory. If further import pre-processing is required, you may use this option to invoke an SAP logical command (transaction SM69) to call your own script before the import is performed. You can choose whether the script is invoked on the domain controller or the target SAP system.
Post-import logical command
This option is similar to the previous option. It allows for a logical command to be called after a transport request has been imported into a target system. This option might be used for copying transport logs that were created by the import process back to the transport directories of the source SAP development system.