SAP ABAP Data Element CNV_10020_GENER_STYLE (Generation style)
Hierarchy
☛
DMIS (Software Component) DMIS 2011_1
⤷ CA-GTF-BS (Application Component) Business Application Support
⤷ CNV_10020 (Package) CNV package 10020
⤷ CA-GTF-BS (Application Component) Business Application Support
⤷ CNV_10020 (Package) CNV package 10020
Basic Data
Data Element | CNV_10020_GENER_STYLE |
Short Description | Generation style |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CNV_10020_GENER_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 | Style |
Medium | 15 | Gener. style |
Long | 20 | Generation style |
Heading | 5 | Style |
Documentation
Definition
When all possible source values are known in advance, it is possible to generate coding that contains the relationship between the source value and the resulting offset. This indicator allows you to specify how the coding should be generated.
- Case structure
Each possible source value is listed as a new case item with the resulting offset. - Internal table
The first time the action is performed, an internal table is created by determining the offset for all possible source values.
Use
- Case structure
+ The determination of the offsets is done on generation. At runtime no additional evaluation time is required.
+ The generated coding is easy to understand. Missing relationships can be detected.
- The determination of the offsets is done on generation. Changes on the action definition always require a new generation.
- Having a huge amount of possible source values, the generated coding for the case structure can become too big. - Internal table
+ The determination of the offsets is done at runtime. Some changes on the action do not require a new generation.
+ The amount of generated coding is always the same. It is independent of the amount of possible source values.
- The determination of the offsets is done once at runtime. For this additional runtime is required.
- Because you cannot look into the internal table after generation, missing relationships are hard to detect.
When creating a new action, the case structure is good for testing. Afterwards the internal table is advisable because it keeps the coding small and some changes on the action do not require a new generation. The additional time for processing at runtime can be neglected.
History
Last changed by/on | SAP | 20141030 |
SAP Release Created in | 2010_1_46C |