SAP ABAP Data Element /BEV3/CHKEYNAME (CH: Key Name for Customizing)
Hierarchy
☛
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
⤷
SD-SLS-PLL-OBS (Application Component) Remaining Beverage - Obsolete Objects
⤷
/BEV3/CH (Package) Contract Handling
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials⤷
SD-SLS-PLL-OBS (Application Component) Remaining Beverage - Obsolete Objects⤷
/BEV3/CH (Package) Contract Handling
Basic Data
| Data Element | /BEV3/CHKEYNAME |
| Short Description | CH: Key Name for Customizing |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR15 | |
| Data Type | CHAR | Character String |
| Length | 15 | |
| Decimal Places | 0 | |
| Output Length | 15 | |
| 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 | Key |
| Medium | 15 | Key |
| Long | 20 | Key Term |
| Heading | 16 | Key Term |
Documentation
Definition
As every FM knows its assignment (application area, sub-module), it can determine its specific Customizing. The assignments are also a key component in this context and are supplemented with an additional key term.
The FM finds the individually required data under the key term (unique supplementary key) which is updated in the coding of the function modules.
As far as the parameters are based on CH agreements, 5 entries can specify them:
CH org.
CHD type
AGCl
RI
EN
To define an agreement, the characteristics of AGCl, RI, EN would be sufficient. But when they are different for each contract type, it is possible to precisely define the relevant agreement by specifying the organizational terms of CH (CH org. and CHD type).
History
| Last changed by/on | SAP | 20040116 |
| SAP Release Created in |
