SAP ABAP Data Element CNV_10020_OBART (Object type)
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_OBART |
Short Description | Object type |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CNV_10020_OBART | |
Data Type | CHAR | Character String |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
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 | Obj. type |
Medium | 15 | Object type |
Long | 20 | Object type |
Heading | 10 | Obj. type |
Documentation
Definition
The object type makes up the first two characters of the general object number, which is a unique identifier for an object (order, cost center, project) at client level.
Objects with different master tables (such as orders and projects) have different object types, while objects with the same master tables (such as CO orders, production orders, and networks) have the same object type.
Notes
- It is possible for a package to have multiple paths with the same source and target determination objects. In this case, you need an identifier, which is stored in the object type field. This makes it possible for the system to uniquely assign data from the object tables to the corresponding path it uses to find the data.
- If there is an elementary relationship that uses the source determination object OBJNR, the object type field must contain the object type found by the elementary relationship.
History
Last changed by/on | SAP | 20141030 |
SAP Release Created in |