SAP ABAP Data Element /SAPSLL/OBJTP_REPL (Object Type of Reference Document)
Hierarchy
☛
SLL-LEG (Software Component) SLL-LEG 901: Add-On Installation
⤷
SLL-LEG (Application Component) Global Trade Services
⤷
/SAPSLL/CORE_LEGAL (Package) Legal Services: Core Functions

⤷

⤷

Basic Data
Data Element | /SAPSLL/OBJTP_REPL |
Short Description | Object Type of Reference Document |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | /SAPSLL/OBJTP_REPL | |
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 | ObjectType |
Medium | 15 | Object Type GTS |
Long | 20 | Object Type for GTS |
Heading | 8 | Obj.Type |
Documentation
Definition
Internal, technical business object key in the Business Object Repository (BOR).
Business objects in the BOR are are identified by the object type (for example, BUS2032) or by a descriptive name in English (for example, SalesOrder. Both names must be unique among all object types.
From external applications, business objects are mostly referred to by their name, while internally in the BOR they are identified usually by their object type. Originally, only the internal key was used, but due to the use of business objects spreading, it became necessary to refer to them by name. For compatability reasons, both names are supported.
The object type can have a maximum of 10 characters.
Use
Dependencies
Example
Examples:
- BUS2032
- BUS6026
History
Last changed by/on | SAP | 20141106 |
SAP Release Created in | 100 |