Workbench Organizer
The Data Modeler is linked to the Workbench Organizer. This means that changes to modeling objects are logged and can be transported to other systems. The Workbench Organizer ensures that there is only one original version of an object. Only this original version of an object can be changed (in the system where it is located).
Interfaces to the Workbench Organizer when creating or changing objects
When you create a new object, a dialog box appears in which you are requested to assign an object to a package. Then choose Save. A further dialog box is displayed. You can now select one of your existing requests or create a new request.
A dialog box also appears if you change an existing object and want to save it. With this dialog box, you can select your own requests or create a new request.
If the new object is a test object, select Local Object. Local objects of this type are not assigned to any request and cannot be transported.
Program IDs and object types in the Data Modeler
The program ID and the object type define how an object is locked or transported. The table below gives an overview of the program IDs and object types of relevance for the Data Modeler.
Program IDs
|
ID |
Object type |
Meaning |
|---|---|---|
|
R3TR |
UENO |
Entity type |
|
R3TR |
UDMO |
Data Model |
An entity type is always locked and transported together with the following subobjects:
-
Documentation (short text, definition, comment, example, aliases)
-
Ingoing relationships
-
Specializations
-
Generalizations
-
Attributes
-
Table assignment and view assignment
A data model is always locked and transported together with the following subobjects:
-
Documentation (short text, definition)
-
Direct successor in the hierarchy
-
Graphics positions of the direct successors
You will find a detailed description of the Workbench Organizer in the documentation Workbench Organizer.