Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CTS-ORG (Application Component) Transport Organizer⤷
SCTS_REQ (Package) CTS: Request Editing
Basic Data
| Data Element | TRCATEG |
| Short Description | Request or task category |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | TRCATEG | |
| 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 | 6 | Categ. |
| Medium | 15 | Category |
| Long | 20 | Category |
| Heading | 0 |
Documentation
Definition
The category of a request or task refers to the area that its objects belong to (object category). The following categories are available:
- CUST: Client-specific customizing
- SYST: Repository and Customizing for all clients
Requests/tasks of the category CUST, only contain objects belonging to the category CUST. These are client-specific Customizing objects from the source client.
Requests/tasks of the category SYST contain objects belonging to the category SYST. These are Repository objects and Customizing objects for all clients. Furthermore, for requests/tasks belonging to category SYST combinations are allowed i.e. they may also contain objects of the category CUST.
The category of a change request is determined by the context (ABAP Workbench or Customizing), when it is created. The category of a task is always the same as the category of the request it belongs to.
When you automatically enter changes in the ABAP Workbench or Customizing, the changed objects are included in requests with the appropriate object category.
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in |
