Hierarchy
SAP_BS_FND (Software Component) SAP Business Suite Foundation⤷
CA-MDG-KM (Application Component) Key Mapping⤷
MDG_BS_CC_OBJ_IDENT_TYPE_CODE (Package) MDG: Object Identifier Type Code
Basic Data
| Data Element | MDG_OBJECT_NODE_TYPE_CODE |
| Short Description | Object Node Type |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | MDG_OBJECT_NODE_TYPE_CODE | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| 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 | Ob Node Ty |
| Medium | 15 | Obj. Node Type |
| Long | 20 | Object Node Type |
| Heading | 21 | Object Node Type |
Documentation
Definition
Defines which of the object ID types that already belong to the same business object are permitted to belong to the same mapping group.
Use
You can create a mapping group by assigning the same object node type to more than one object ID types. To prevent object ID types from belonging to the same mapping group, you can specify different object node types.
When implementing key mapping for subnodes of business objects, you must prevent the root node of one business object from belonging to the same mapping group as the sub node of another business object. To do this, you must specify different object node types for the respective object ID types.
Dependencies
Ensure that any object node type you assign to an object ID type within a business object is already assigned to the business object.
Example
The following business objects belong to the object type 899, which is a chart of accounts within financial accounting. Objects 1 and 2 have the same object node type, and can therefore belong to the same mapping group.
Object Type: 899
Object 1 - Financial Accounting Chart of Account
- Object ID Type: 900 (Financial Accounting Chart of Account ID)
- Object ID: 12345
- Object Node Type: S180
Object 2 - Financial Accounting Chart of Account
- Object ID Type: 900 (Financial Accounting Chart of Account ID)
- Object ID: 67890
- Object Node Type: S180
Object 3 - Financial Accounting Chart of Account Item
- Object ID Type: 909 (Financial Accounting Chart of Account Item ID)
- Object ID: 12345
- Object Node Type: S189
Objects 1 and 2 have an Object ID Type of 900 representing Financial Accounting Chart of Account ID. In contrast, object 3 has anObject ID Type of 909 representing the Account Item ID, which is a sub-node of a chart of accounts within financial accounting. Therefore, object 3 must only be mapped with another Account Item ID, but not with a whole chart of accounts. To ensure this is the case, the Object Node Type for Object ID Type 900 (Financial Accounting Chart of Account ID) is different to the Object Node Type for Object ID Type 909 (Financial Accounting Chart of Account Item ID).
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 702 |
