SAP ABAP Data Element /SAPSLL/OBJTP_REPL_TXT (Description of Reference Types)
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
⤷ SLL-LEG (Application Component) Global Trade Services
⤷ /SAPSLL/CORE_LEGAL (Package) Legal Services: Core Functions
Basic Data
Data Element | /SAPSLL/OBJTP_REPL_TXT |
Short Description | Description of Reference Types |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | /SAPSLL/TEXT40 | |
Data Type | CHAR | Character String |
Length | 40 | |
Decimal Places | 0 | |
Output Length | 40 | |
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 | Ref. Type |
Medium | 15 | Reference Type |
Long | 20 | Reference Type |
Heading | 40 | Reference Type |
Documentation
Definition
Internal technical key of a business object in the Business Object Repository (BOR).
Business objects in the BOR are identified both by their object type (BUS2032, for example) and through a descriptive name (such as SalesOrder). Both designations must be unique among all object types.
External applications often use the descriptive names to address business objects. In contrast, they are usually identified by the object type internally in the BOR. Only the internal key was used originally, but due to the widespread use of business objects, the need arose to address them by a name as well. Both designations are now managed to ensure downward compatibility.
The object type can be up to 10 characters long.
Use
Dependencies
Example
Examples:
- BUS2032
- BUS6026
History
Last changed by/on | SAP | 20141106 |
SAP Release Created in | 720 |