Some SAP customers have a SAP client architecture requirement to distribute transports to particular system clients in the landscape, based on rules and the source client of the transport. ActiveControl includes a capability to automate this client-based transport distribution, which can be setup via the following steps.
1) Configure table /BTI/TE_IMP_CLI in the Domain Controller with the required transport distribution rules
|PATH||the ActiveControl path for which the rule is being defined.|
|SOURCE SYSTE||the source system (SID).|
|SOURCE CLIENT||the source system client.|
|TARGET||the target system in the path where the transport has/not to be imported into particular client.|
|SORT ORDER||This is used for sorting the clients in a particular target.|
|TARG CLIENT||The client of the target system.|
|SKIP||An X should be entered in this field for the rules where you want the transport to not be imported into the defined client defined in the rest of the rule.|
2) Switch on TE_EXIT_SAMPLE_0065 in /BTI/TE_EXITC table in the Domain Controller
i) the import queue is not skipped, it is during the import that the skipping occurs based on the rules defined in the configuration table
ii) the clients will be sorted based on SORTORDER
iii) if a client is not defined in the configuration it will be ignored
iiii) if no entries are found for a transport it will be imported in all the clients defined in the config
iv) the transports can still be imported using both single one-by-one or block import.
v) It is NOT possible to use this functionality during the standard Merge process into a multi-client Dev system (as Merge process will import the source transport into all configured clients of the Development target and then create the Merge TOC in one of those clients). If you really want to achieve Merge to specific client, the solution would be to configure multiple Merge targets, each with one client.