Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CTS-ORG (Application Component) Transport Organizer⤷
SCTS_OBJ (Package) CTS: Object Editing (Including Transport Objects)
Basic Data
| Data Element | OB_SUBOBJ |
| Short Description | Object: Sub-Object |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | OB_SUBOBJ | |
| Data Type | CHAR | Character String |
| Length | 10 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| Value Table | OBJSUB |
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 | Sub-Object |
| Medium | 15 | Sub-Object |
| Long | 20 | Sub-Object |
| Heading | 0 |
Documentation
Definition
Subobject of an object
Use
Subobjects of objects are defined for two reasons:
- Definition of business (sub)views of the objects.
You can define several subobjects, with 10-character subobject names, for the various views (e.g. with preselections) of an object. You could for example define subobjects per country (German, Austrian , etc.) of a view object "Wage type". They are distinguished from the higher-level object by selection of the country-specific rows.
- Assignment of maintenance transaction codes and IMG chapters to the objects.
This assignment is at subobject level. You must specify a subobject for an object. Names are not restricted. The maintenance transactions are responsible for the of the object view (row) selection logic.
Procedure
Examples
Example definition:
Name V_FILENAME
Object type V
Subobject name 0000000001
Transaction code OKUN
Help relevant X
Documentation type O
Book SIMG_PHA1
Class SIMG
Document SIMG_CFMENUOKCMOKUN
Position 1
Dependencies
History
| Last changed by/on | SAP | 19951208 |
| SAP Release Created in |
