Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
GBAS (Package) FI-SL Customizing / integration / Basis
Basic Data
| Data Element | EXIT_NR |
| Short Description | Exit no. (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 no. |
| Medium | 15 | Exit no. |
| Long | 20 | Exit number |
| Heading | 4 | Exit |
Documentation
Description
This exit is used when performing the field movement.
Supplementary Documentation - EXIT_NR 1000
Definition
The fields of the sender table (defined in the activity) to be transferred to the fields of the FI-SL receiver table (defined in the ledger) are defined in the movement table.
If a direct assignment sender - receiver is not possible, you can also use a user exit. In this case, the program does not generate a MOVE, but calls this exit.
You define the exit as follows:
xyy with x = S (standard exit, defined by SAP),
U (user exit, defined at the customer site)
yy= two-digit exit number
Examples: S01, S02, U01, U02
You define the exit routines in the following programs:
- Standard exits for fixed field transfers: RGIFS000
- User exits for fixed field transfers: Exit program entered for the application area GIMF when maintaining cross-client user exits (Transaction GCX1). The exit program should observe customer naming conventions.
- Standard exits for variable field transfers: RGIVS000
- User exits for variable field transfers: Exit program entered for the applicaiton area GIMV when maintaining client-specific user exits (Transaction GCX2). The exit program should observe customer naming conventions.
The FORM routines in the program must have the following format:
FORM Eyy_MVC USING FROM_FIELD TO_FIELD.
Here, yy again represents the exit number. You always have to define the using parameters if the corresponding fields in the table contain values. In the user exit, you can access all fields of the sender and receiver table.
Supplementary Documentation - EXIT_NR 2000
Definition
You can use rollup user exits at the following four places:
- Exit in the rollup header
You access the exit after making entries in the internal tables that are important for the rollup execution. At that time, you can carry out general validations, for example, to check the period interval entered.
- Exit 1 in the field movement header table
The exit is accessed after a check has been successfully completed to see whether a read summary record both occurs in the sender set and fulfills a selection condition that may exist. It is only used as a subsequent selection that is not possible using a set or a selection formula. At that time, the receiver record has not yet been filled.
- Exit with field movements
The exit is accessed when transferring key fields from the sender to the receiver. The key of the receiver record is already partially filled - the transfer takes place in alphabetical order by receiver field names -, the data portion has not yet been filled. Using this exit, you can carry out substitutions for specific key fields of the coding block. You can define this exit both directly during the field movement (unconditional exit) and also in a substitution activity (possible in conjunction with a condition). If you want to access/change several fields in an exit, you have to enter this exit for each of these fields.
- Exit 2 in the field movement header table
The exit is accessed if the receiver record is completely created. At that time, you can, if necessary, carry out substitutions in the amount fields.
The name of the exit must be structured as follows:
- Sxx: standard exit delivered by SAP and cannot be changed by user
- Uxx: user exit, created by the user
xx represents a two-digit exit number.
The exit routines are defined in the following programs:
- Standard exits
Program RGLVS000
These exits are always cross-client and may not be changed.
- User exits
Compare entry to 'Rollup: User exit' in table T80D (can be maintained in FI-SL customizing)
Caution: The T80D entry delivered for rollup user exits (exit program RGLVUmmm) is only an example. When you use user exits, you should enter an exit program here that corresponds to customer naming conventions (e.g. ZGLVUmmm) and assign a corresponding customer development class to it.
The form routines in the program must have the following form, whereby xx again represents the exit number:
- FORM Axx_USER_EXIT for exit in the rollup header. The return code displays the result of this exit. SY-SUBRC = 0 means that processing is to be continued, SY-SUBRC > 0 means that processing is to be terminated.
- FORM Bxx_USER_EXIT for exit 1 in the field movement header table. The return code displays the result of the subsequent selection exit 1. SY-SUBRC = 0 means that the record is valid, SY-SUBRC > 0 means that the record is invalid.
- FORM Cxx_USER_EXIT USING Bxx_FIELD for exits during the field movement. Here, you can access the field(s) to be changed using the structure GLU1.
- FORM Dxx_USER_EXIT for exit 2 in the field movement header table. Here, you can access the data fields to be changed using the structure GLU2.
In each exit routine the contents of field SY-SUBRC must be set to a value >= 0, so that the routine can be recognized in the existence check.
In the user exit, you can access all key fields using the structure GLU1, and all data fields using the structure GLU2.
Some of the SAP delivered user exit examples are contained in program RGLVU000.
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in |
