SAP ABAP Data Element USOBXTYPE (Type of Application (Transaction/RFC Function/Service))
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-SEC-AUT-PFC (Application Component) ABAP Authorization and Role Management
⤷ S_PROFGEN (Package) ABAP Role Administration (Profile Generator)
⤷ BC-SEC-AUT-PFC (Application Component) ABAP Authorization and Role Management
⤷ S_PROFGEN (Package) ABAP Role Administration (Profile Generator)
Basic Data
Data Element | USOBXTYPE |
Short Description | Type of Application (Transaction/RFC Function/Service) |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | USOBXTYPE | |
Data Type | CHAR | Character String |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 30 | |
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 | Type |
Medium | 20 | Type |
Long | 40 | Type of Application |
Heading | 55 | Type of Application (Transaction/RFC Function/Service) |
Documentation
Definition
An application in this context means an executable program object for which the authorization default data must be maintained.
The following application types exist:
- 'TR' - transaction.
- 'RF' - RFC function module.
- 'HT' - TADIR service. A service that an object catalog entry receives when it is created in the SAP system. Examples: SICF services, BSP applications.
- 'HS' - External services. External services are not directly known to the SAP backend system, since they run externally and only communicate with the SAP backend system through RFC function calls.
Use
Dependencies
Example
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 700 |