SAP ABAP Data Element CNV_10030_EVAL_STYLE (Evaluation style)
Hierarchy
☛
DMIS (Software Component) DMIS 2011_1
⤷
CA-GTF-BS (Application Component) Business Application Support
⤷
CNV_10030 (Package) CNV package 10030
DMIS (Software Component) DMIS 2011_1⤷
CA-GTF-BS (Application Component) Business Application Support⤷
CNV_10030 (Package) CNV package 10030
Basic Data
| Data Element | CNV_10030_EVAL_STYLE |
| Short Description | Evaluation style |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CNV_10030_EVAL_STYLE | |
| 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 | Eval. |
| Medium | 15 | Eval. style |
| Long | 20 | Evaluation style |
| Heading | 5 | Eval. |
Documentation
Definition
The standard approach for org determination and evaluation of non-transparent fields is the use of a generic function module. To speed things up it is better to generate coding. Especially for "easy" stuff the generic overhead is big.
Notes
Be aware that due to complexity coding generation is not always possible.
For org determination it can only be used for direct determination but not for path determination.
For the evaluation of non-transparent fields you should always check in advance if the generated coding works they way the generic approach does.
History
| Last changed by/on | SAP | 20141030 |
| SAP Release Created in | 2010_1_620 |
