User Exits are typically customer-specific requirements, delivered as custom Z code on top of an individual customer’s ActiveControl implementation.
The following matrix summaries Basis Technologies responsibilities both in writing and supporting customer-specific User Exits.
| ID | Scenario | Chargeable? | Supported by Basis Technologies during implementation? | Supported by Basis Technologies during ActiveControl Upgrades? |
|---|---|---|---|---|
| 1 | Customer writes their own Z user exit with no assistance from Basis Technologies | No | No | No |
| 2 | Customer requests help in writing a Z User Exit | Yes | No | No |
| 3 | Customer requests BTI to develop a Z User Exit – its Custom only | Yes | Yes, during initial development / implementation | No (see note 1) |
| 4 | Customer performing AC self-upgrade. Requests BTI review of existing Z User Exits | Yes | N/A | No – unless budget is in place for it. |
| 5 | Customer performing AC upgrade with BTI involvement. Requests BTI review of existing Z User Exits | Yes | N/A | Yes, if budget in place. |
| 6 | Customer implements an out-of-the-box Standard Reusable User Exit with no changes to it | No | Yes | Yes |
Notes
(1) Whilst Basis Technologies will support the initial implementation of a User Exit where we are involved as a chargeable deliverable – it will not be supported during a subsequent Upgrade of ActiveControl unless chargeable services are in place.
(2) Please refer to this section on the responsibilities for upgrading ActiveControl
Post your comment on this topic.