Hierarchy
⤷ 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_TGUMS |
Short Description | Exit number for exit routines in the FI-SL conversion |
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
User exits allow you to modify fields during the conversion (for example, accounts are summarized to account groups during the conversion). You can also use user exits to group together different source fields in one target field and thus, for example, fill a new field from two old fields.
For more information on this, refer to the online documentation for the field SEQNR (S.).
Note
User exits are defined in program RGUUX000 and must have as many FROM-using parameters as the number of source fields assigned to the target field (see the examples in RGUUX000).
If this is not the case, the system cancels processing with a runtime error before the conversion.
Warning
When using user exits, you should take into account that all modifications to fields are made during the conversion of the transaction data, but these changes are not taken into account in the individual application areas. For example, a summarization of accounts (for example, field 'RACCT') to account groups (for example, field 'RACCTGRP') using a user exit would take place when converting the transaction data, but an automatic conversion of the sets for the field 'RACCT' would not take place. You would have to maintain these sets manually.
In case of a problem (that is, if the field 'RACCT' was not defined in target table), all sets for the field 'RACCT' would be omitted during the conversion.
History
Last changed by/on | SAP | 20100310 |
SAP Release Created in |