User Exit (Transport Form [Group] Mismatching)

An optional User Exit was created for a Basis Technologies customer where there Transport Form Groups did not match the corresponding field values in ChaRM. The reason for the Group mismatch was that this customer had subdivided their Transport Form groups out per module, one for customising and one for workbench to facilitate more granular approvals within ActiveControl.

Eg FI – Customising, FI – Workbench

To overcome such mismatching, the following steps can be undertaken:

1) Switch on user exit 0960 in table /BTI/TE_EXITC table in the Domain Controller

2) Populate the matching values in /BTI/TE_TVARV, using variable TE_CHARM_CU_GROUPS and TE_CHARM_WB_GROUPS

[Variable Name] = TE_CHARM_CU_GROUPS
[Number] = Sequential number: 1,2,3, etc
[Selection Value Low] = 1,2,3,4,5 (the numerical value from CRMD_CUSTOMER_H)
[INCL/EXCL] = I
[Option] = EQ
[Selection Value High] = GUID value from /BTI/TE_GROUPS

[Variable Name] = TE_CHARM_WB_GROUPS
[Number] = Sequential number: 1,2,3, etc
[Selection Value Low] = 1,2,3,4,5 (the numerical value from CRMD_CUSTOMER_H)
[INCL/EXCL] = I
[Option] = EQ
[Selection Value High] = GUID value from /BTI/TE_GROUPS

Example Customer Configuration

The below illustrates some example configuration of /BTI/TE_TVARV table at a customer implementation of the ActiveControl ChaRM integration.

Figure: Example customer configuration of /BTI/TE_TVARV