Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-GTF-EEW-SRV (Application Component) EEW Services⤷
OXT_TASK (Package) Task Handler for OXT Tool
Basic Data
| Data Element | OXT_SYSGROUP |
| Short Description | System Group |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | OXT_OBJNAME | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| 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 | Group |
| Medium | 15 | Group |
| Long | 20 | System Group |
| Heading | 30 | System Group |
Documentation
Definition
To identify the group assignment of the development system, test system, productive system and Customizing client in the Easy Enhancement Workbench, you can describe this system with an identical system group.
Use
You need only maintain the system group if you want to maintain multiple systems per system type, that is, you want to generate extensions in multiple R/3 systems that are connected to a CRM system.
Even in this case, you need only maintain the system group if multiple system roles (for example, development-, or test systems) exist for each system. If you want to maintain development systems exclusively, and these are also to generate the client-dependent Customizing, then you need not maintain the system groups.
You can freely define the description of the system groups.
Dependencies
Example
History
| Last changed by/on | SAP | 20041216 |
| SAP Release Created in | 640 |
