Hierarchy

⤷

⤷

⤷

Basic Data
Data Element | EXIT_800M |
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
Definition
In the movement table, you define which fields of the sender table, defined in activity, are to be moved to which fields of the FI-GLX receiver table, defined in ledger.
If a direct assignment sender-receiver is not possible, you can also work with a user exit. In this case, the program does not form a MOVE, it calls up this exit.
The exit must be defined as follows:
xyy with x = S (standard exit, defined by SAP),
U (user exit, defined by customer)
yy= 2-character exit number
Examples: S01, S02, U01, U02
The exit routines have to be defined in the following programs:
RGIFS000: Standard exit in table T800M
RGIFU000: User exit, defined in table T800M
RGIVSmmm: Standard exit in table T888M (mmm = client)
RGIVUmmm: User exit in table T888M (mmm = client)
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 must always specify the using parameters if the relevant fields are also filled in the table. All fields of the sender and receiver table are accessible in the user exit.
History
Last changed by/on | SAP | 19960103 |
SAP Release Created in |