SAP ABAP Data Element CNV_10020_CALLTYPE (Evaluation module type)
Hierarchy
☛
DMIS (Software Component) DMIS 2011_1
⤷
CA-GTF-BS (Application Component) Business Application Support
⤷
CNV_10020 (Package) CNV package 10020
DMIS (Software Component) DMIS 2011_1⤷
CA-GTF-BS (Application Component) Business Application Support⤷
CNV_10020 (Package) CNV package 10020
Basic Data
| Data Element | CNV_10020_CALLTYPE |
| Short Description | Evaluation module type |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CNV_10020_CALLTYPE | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | Type |
| Medium | 15 | Type |
| Long | 20 | Type |
| Heading | 5 | Type |
Documentation
Definition
The standard approach on evaluating non-transparent fields is the use of a generic function module. To speed up the evaluation it is better to generate coding. Especially for "easy" rules the generic overhead in evaluation is big.
Use
- Generic evaluation
Use the generic evaluation on complicated rules when generation does not work or results in too much coding. - Generated evaluation
Use it whenever possible to speed up things especially on large tables.
History
| Last changed by/on | SAP | 20141030 |
| SAP Release Created in | 2010_1_620 |
