SAP ABAP Data Element RMPSE_OBJTYPE (Object Type)
Hierarchy
☛
SAP_BS_FND (Software Component) SAP Business Suite Foundation
⤷
CA-GTF-RCM (Application Component) Records and Case Management
⤷
RMPS_SOA_BE (Package) RMPS: Services Backends
SAP_BS_FND (Software Component) SAP Business Suite Foundation⤷
CA-GTF-RCM (Application Component) Records and Case Management⤷
RMPS_SOA_BE (Package) RMPS: Services Backends
Basic Data
| Data Element | RMPSE_OBJTYPE |
| Short Description | Object Type |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | CHAR | Character String |
| Length | 5 | |
| Decimal Places | 0 | |
| Output Length | 5 | |
| 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 |
| Long | 20 | Object Type |
| Heading | 14 | Object Type |
Documentation
Definition
Document Type ID for Service identification in the backend
Use
The backend functionality of RecordsManagement does only know some technical settings like RMS ID, SPS ID, GenerationRule, etc... but not Document Type. The (frontend) service knows only the Document Type but not the special technical settings of the RecordsManagement backend. So this Document Type is the connection from frontend to the backend technical setting.
Dependencies
Example
SAP delivers example entries of customizing table RMPSE_SOA_REC. The customer can use his own DocTypes definitions.
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 701 |
