Many SAP customers have multiple clients within at least some of their SAP systems. In some cases, this multi-client strategy is limited to the Development system (eg 100 main client, 200 unit test client) – but in other cases, multiple clients can also be seen in Test and sometimes even Production SAP systems.
In some cases, the client distribution is based on the original source client of the Transport. This scenario can be handled in ActiveControl via long-standing client distribution capability described in this online Change Note.
In other cases, customers may want to specific the client(s) in a system to which individual Transport Forms should be deployed, based on a user choosing on the Transport Form. This scenario can be achieved using Rules Engine consumer for client selection/import.
/BTI/TE_RE_CLISE
Table /BTI/TE_RE_CLISE is the consumer table for the Client Selection import rules.
| Field | Description |
|---|---|
| FILTER | (optional) Please refer to Filter section. |
| SYSTEM_TYPE | If you want the rules to be applicable for all systems defined in /BTI/TE_RE_SYSTP – instead of a specific system. |
| TARGET | Define the Target against which the client import rule is running against. |
| TARCLIENT | Define the Target client against which the client import rule is running against. |
| STEP | As per what is configured in /BTI/TE_RE_STEP. |
| PRIORITY | Number sequence (1,2,3 etc). This is the order in which the rules will be processed. |
| DEF_ON_EXCEPTION | “Defer on Exception” is an optional setting. If switched on, then if there is an exception, then the action set for the rule will be carried out, but a system error will also be logged. |
Post your comment on this topic.