SAP ABAP Data Element MDG_GET_KM_FROM_CENTRAL_REG (Get Key Mapping Information from Central Registry)
Hierarchy
☛
SAP_BS_FND (Software Component) SAP Business Suite Foundation
⤷
CA-MDG-KM (Application Component) Key Mapping
⤷
MDG_BS_ID_MATCHING_CDDIC (Package) MDG Key Mapping: DDIC
⤷
⤷
Basic Data
| Data Element | MDG_GET_KM_FROM_CENTRAL_REG |
| Short Description | Get Key Mapping Information from Central Registry |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | BOOLE | |
| 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 | KM C Reg |
| Medium | 15 | KM from CtrlReg |
| Long | 20 | KM from Central Reg. |
| Heading | 37 | Get Key Mapping from Central Registry |
Documentation
Definition
Specifies whether or not key mapping data is read directly from the central registry.
This setting can be useful if a process on a client system needs complete key mapping content for an object and this content is not allowed to belong to the local registry.
&USE&
To ensure key mapping data is read directly from the central registry, pass the parameter value 'X' to the key mapping API.
Dependencies
You must have defined a central registry for each business object type. You can do this in the Customizing activity Customize Business Objects for Key Mapping.
Example
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 702 |