Hierarchy
⤷ ICM (Application Component) Incentive and Commission Management (ICM)
⤷ CACSMAP (Package) ICM: Mapping
Basic Data
Data Element | CACSCONVEXITGRP |
Short Description | Identification of a Grouped Conversion Exit |
Data Type
Category of Dictionary Type | Direct Type Entry | |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ||
Data Type | CHAR | Character String |
Length | 4 | |
Decimal Places | 0 | |
Output Length | 4 | |
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 | ConExGrp |
Medium | 15 | ConverExitGroup |
Long | 20 | ConversionExit Group |
Heading | 8 | ConExGrp |
Documentation
Definition
The group comprises two conversion exits, whose names are taken from the name of this group, with an extra 0 for the category field and an extra 1 for the identification field. The identification field is also assigned below the basic conversion exit.
The presentation conversion (screen display, OUTPUT conversion) of the identification field is then created using the value in the category field (see the TCACS_CONVEXIT table in Customizing). If there is no layout definition in Customizing, no conversion is executed.
The database conversion (INPUT conversion) always uses the basic conversion exit (only ALPHA is allowed in this version).
Note for interface developers
For interfaces that have grouped conversion exits, the fields must always appear in pairs, with the category field first and then the identification field. You may need to adjust the processing sequences in the PAI event accordingly, to enable the category field information to be transferred to the identification field.
History
Last changed by/on | SAP | 20020219 |
SAP Release Created in | 463 |