Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-CTS-ORG (Application Component) Transport Organizer⤷
SCTS_CAT (Package) CTS: Object Directory & Packages
Basic Data
| Data Element | GENFLAG |
| Short Description | Generation flag |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | GENFLAG | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | Gen. Flag |
| Medium | 15 | Generation Flag |
| Long | 23 | Generation Flag |
| Heading | 4 | Gen. |
Documentation
Definition
This flag indicates whether an object of the ABAP Workbench is generated automatically.
- Generated (GENFLAG <> " ")
- Not generated (GENFLAG = " ")
Use
Generation programs for Repository objects create an entry in the object directory (TADIR) for the generated objects using the function module TR_TADIR_INTERFACE. By setting the parameter WI_SET_GENFLAG, you can flag an object as a generated object in the object directory. Depending on how you want the objects to be handled during the upgrade, set one of the following values:
- X Generated, is retained during the upgrade
- T Generated, can be deleted during the upgrade
The following rules apply for handling objects classified with these values during the upgrade and in the Transport Organizer:
SPACE
The objects have not been generated or they are not flagged as generated objects because they should be treated as non-generated objects regarding correction, transport, and delivery: New objects created at SAP or SAP partners or modified object versions must be delivered using the normal transport routes. Objects created in the customer system must be in the customer namespace and are protected against overwriting or deletion during the upgrade due to this assignment. It may be possible to make manual modifications to these objects using ABAP Development Workbench editors depending on the system change option and original system. Objects not contained in $* or T* packages are included in the global object directory (GTADIR) at SAP.
T
The objects are lost during the upgrade (repository switch) because SAP imports the new Repository and deletes the old customer Repository. Generated objects flagged with this value may be deleted during the upgrade since they can be regenerated at any time if this is necessary. (If it improves performance, these objects are deleted.) Objects with GENFLAG T are not included in the global directory (GTADIR).
X
The objects are saved during the upgrade (repository switch) because they are copied to the new version after the new SAP Repository has been imported and before the old customer Repository is deleted. Generated objects flagged with this value are retained during the upgrade.
Exception:
If an object is delivered by SAP with the same name, the object generated in the customer system is overwritten.
Objects with GENFLAG X are not included in the global object directory (GTADIR).
The following also applies generally:
- If generated objects belong to a $* package, they are only valid locally and are not transportable.
If the generated objects are not in $* or T* packages, they are transportable. However, name collisions or overwriting may occur because objects with GENFLAG are not included in the global object directory (GTADIR). It is therefore possible for various objects to exist under the same name in different systems. - If you need to ensure that the customer's objects are not overwritten during the upgrade by objects delivered by SAP with the same name, then you must reserve the used naming convention for generated objects and lock the creation of objects with the ABAP Workbench. (with PROTART F). This reservation is made by the CTS administrator, with an entry in the maintenance view V_TRESN with reservation type F (SAP-internal, by the department System Logistics).
- If you want to maintain generated objects with an editor, an I message is sent. This message indicates that the object is generated, but can be modified.
- If there is a reservation of the naming convention (maintenance view V_TRESN) with PROTART = F and MSGSEV = E for objects flagged as generated in the object directory (for MSGSEV = W, only a warning for change access), then manual changes to these objects are rejected in the ABAP Workbench.
- If Repository objects, the names of which are defined according to a naming convention reserved for generated objects (with TRESN-PROTART "F" and TRESN-MSGSEV "W": repairs are possible) are created manually using the ABAP Workbench, the TADIR-GENFLAG is set to "X". In this way the object has been flagged as "generated". (Other values are not given for selection, since the correct GENFLAG value is generally only known to the development team of the generator.)
Examples
Dependencies
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in |
