Ansicht
Dokumentation

BOOKCEXITS - BOOKCEXITS

Function exits allow the customer to implement additional logic in a transaction. The SAP applications developer determines the points in a transaction at which function exits are called, and which data is to be transfered. He creates the appropriate function modules with short text, interface and documentation. The functionality provided for a function exit is described in the accompanying SAP documentation.
Example coding created by SAP can exist for function exits, and can be copied (and changed) if required. Furthermore, the function groups can contain subroutines that can be called if required. These subroutines cannot be changed.

The customer creates the coding of the function modules, and (if necessary) the screens, text elements, his own Includes (...) for the function group.

Responsibility for function groups containing function exits is split between SAP and the customer, and therefore not everything allowed in the customer's own function groups is allowed in these groups. The customer is not allowed to change the components created by SAP. In particular, the customer is not allowed to copy, delete, rename or reassign function modules, and likewise the interface, management and documentation of the function modules may not be changed.

The ABAP/4 coding only runs when the customer activates the project, which contains the function exit as a component. Prior to this, the function exits have no effect in the transaction.