SAP ABAP Data Element DRP_OBJECT (DEV Reporting: Object type)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-SRV-DRT (Application Component) Development Reporting Tools
⤷
S_DEVREPORTING (Package) - INTERNAL, no reuse - SAP internal Dev. Reporting

⤷

⤷

Basic Data
Data Element | DRP_OBJECT |
Short Description | DEV Reporting: Object type |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | OBJECT | |
Data Type | CHAR | Character String |
Length | 4 | |
Decimal Places | 0 | |
Output Length | 4 | |
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 | 4 | Obj. |
Documentation
Definition
An object is uniquely identified by its program ID (PGMID), object type and object name.
The SAP System differentiates between complete objects and their component subobjects.
- Complete objects usually have an object directory entry, and can include subobjects that can be transported separately. Complete objects are indicated by the PGMID R3TR.
- Subobjects do not have their own object directory entry. Subobjects have the PGMID LIMU.
Example
The complete object R3TR PROG includes the following subobjects, among others:
- LIMU REPS
- LIMU REPT
- LIMU DYNP
Use the F4 Help to display examples of types of complete objects and subobjects.
History
Last changed by/on | SAP | 20130604 |
SAP Release Created in | 711 |