Parallel Import capability in ActiveControl enables Approvers to initiate an additional transport import, even when an existing import is in progress.
Check Parallel Import Possible (0070) will run automatically during the ‘Approve and Import’ parallel import process , to confirm that that the parallel deployment is technically feasible – and more importantly – safe to do so alongside the Import that is already running. This new 0070 analyser will essentially perform the following checks:
1) that the Target is configured for parallel imports
2) that the Target is not a Merge Target
3) That there are no object overtake/regression warnings
4) That DDIC objects are not contained in both the i) transports already being imported, and ii) the transports on which the ‘Approve and Import’ is being performed.
If any of these checks fail, then the Parallel import will not be allowed to proceed. Instead, the Transports will solely be approved and moved into the Import Queue for import as part of the next automated or manual import once the current running import finishes, and a message will be presented to the User to tell them that the parallel import has started.
Please note that 0070 does NOT need to be configured. It runs automatically as part of the General Analysis process during the ‘Approve and Import’ process.
|KEY_NO_RELATED_VIEWS||By default, when transporting table entries, views that use the same table in key fields will be considered a conflict. This behaviour can be turned off with this flag.|
|KEY_NO_WILDCARDS||If this flag is set, wildcards are not considered when searching for conflicting table entries.|
|RISKGROUP||If you want to exclude certain Objects from being able to be included in Parallel Imports, you should configure these via a new and distinct Risk Group (using the usual /BTI/TE_RISKG, /BTI/TE_RISKGOB and /BTI/TE_RISKGOBT configuration) and configure against this RISKGROUP parameter.|