Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
FI-SL-SL (Application Component) Basic Functions⤷
GBRU (Package) FI-SL rollup
Basic Data
| Data Element | USEREXIT |
| Short Description | User Exit (S..: Standard Exits, U..: User Exits) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | EXIT_NR | |
| Data Type | CHAR | Character String |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Exit |
| Medium | 15 | User Exit |
| Long | 20 | User Exit |
| Heading | 4 | Exit |
Documentation
Definition
Rollup user exits can be used in the following four cases:
- Exit in rollup header
The exit is accessed after you have filled in the internal tables which are needed for the rollup execution. At this point, you can carry out general validations, for example, to check the period interval you have entered.
- Exit 1 in the field movement header table
The system checks that a read summary record appears in the sender set and that any existing selection conditions are met. If this check is successful, the exit is accessed. It is only used for a subsequent selection that is not possible using either a set or a selection formula. The receiver record is not yet filled at this point.
- Exit for field movements
The exit is accessed when key fields are moved from the sender to the receiver. The key of the receiver record is already partially filled - the field movement is carried out in alphabetical order of receiver field names. The data part is not filled in at all. You can perform substitutions for particular key fields of the coding block using this exit. You can define this exit both direct in the field movement (unconditional exit) and in a substitution activity (possible in conjunction with a condition). If several fields in an exit are accessed or changed, you have to enter this exit for each of these fields.
- EXit 2 in the field movement header table
The exit is accessed once the receiver record has been generated completely. If necessary, you can also make substitutions (rounding-off) in the amount fields at this point.
The exit name must have the following structure:
- Sxx: standard exit delivered by SAP, valid for all clients
- Uxx: user exit, may be defined by the user
where xx is a two-digit exit number.
The exit routines are defined in the following programs:
- Standard exits
Program RGLVS000
- User exits:
Compare entry to 'Rollup: User-exits' in table T80D (can be maintained in FI-SL Customizing with transaction GCX2).
Caution: The delivered T80D entry for rollup user exits is only an example. If you want to use user exits, enter an exit program at this point that is within the customer name range (like ZGLVUmm) and assign a corresponding customer development class to the program.
The form routines in the program must have the following structures, where xx is the exit number:
- FORM Axx_USER_EXIT for exit in the rollup header. The results of this exist are checked via the return code. SY-SUBRC = 0 means, that processing should be continued, SY-SUBRC > 0 means, that the processing should be terminated.
- FORM Bxx_USER_EXIT for exit 1 in the field movement header table. The result of the subsequent selection exit 1 is checked via the return code. SY-SUBRC = 0 means that the record is valid, SY-SUBRC > 0 means that it is invalid.
- FORM Cxx_USER_EXIT for exits during the field movement. Here, the field(s) to be changed can be accessed via the structure GLU1.
- FORM Dxx_USER_EXIT for exit 2 in the field movement header table. Here, the data fields to be changed can be accessed via the structure GLU2.
In each exit routine, the contents of the field SY-SUBRC must be set to a value >= 0, so that the system can recognize the routine in the existence check.
In the user exit, all the key fields are accessed via the structure GLU1, all data fields via the structure GLU2.
History
| Last changed by/on | SAP | 19950403 |
| SAP Release Created in |
