SAP ABAP Data Element UKM_PREC_OBJTYP (Object Type of Preceding Document)
Hierarchy
☛
SAP_FIN (Software Component) SAP_FIN
⤷ FIN-FSCM-CR-AD (Application Component) Adaptor
⤷ UKM_GENERAL (Package) Connection to SAP Credit Management
⤷ FIN-FSCM-CR-AD (Application Component) Adaptor
⤷ UKM_GENERAL (Package) Connection to SAP Credit Management
Basic Data
Data Element | UKM_PREC_OBJTYP |
Short Description | Object Type of Preceding Document |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | OJ_NAME | |
Data Type | CHAR | Character String |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
Value Table | TOJTB |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | OBJ | |
Default Component name | OBJTYPE | |
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | ObjectType |
Medium | 15 | Pred. Obj. Type |
Long | 20 | Obj.Type Predecessor |
Heading | 20 | Obj.Type Predecessor |
Documentation
Definition
Internal, technical key of a business object in the Business Object Repository (BOR).
Business objects in the BOR are identified by the object type (for example BUS2032) and a descriptive, English name (for example, SalesOrder). Both names must be unique across all object types.
From external applications, business objects are frequently identified by the descriptive names, whereby internally in the BOR, they are mostly identified by the object type. Originally, only the internal key was used, but due to the widespread use of business objects, names are now required for identification. For compatability reasons, both names are now used.
The object type can have a maximum of 10 characters.
Use
Dependencies
Example
Examples:
- BUS2032
- BUS6026
History
Last changed by/on | SAP | 20050705 |
SAP Release Created in | 600 |