Hierarchy

⤷

⤷

Basic Data
Data Element | MDG_OBJ_CORRELATION |
Short Description | Key Harmonization |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | MDG_OBJ_CORRELATION | |
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 | Key Harm. |
Medium | 15 | Key Harmonizat. |
Long | 20 | Key Harmonization |
Heading | 35 | Key Harmonization |
Documentation
Definition
Indicates whether keys are harmonized for a combination of business system, business object type, and communication channel or if key mapping needs to be carried out. If keys are harmonized, target system keys match sender system keys.
Use
Dependencies
The setting is only evaluated by certain outbound implementations. If you set this value for a business system that acts as a target system for a replication model, you can only activate the replication model if the relevant outbound implementation supports the evaluation of this setting.
Example
The I_MAT outbound implementation for material evaluates this setting during data replication. Therefore, you can configure harmonized keys or key mapping, depending on whether or not the target system has harmonized keys.
The 986_3 outbound implementation for business partner does not evaluate this setting during data replication. Therefore you must leave this field empty. For this outbound implementation, key mapping is always read and written.
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 702 |