The entity type is used to manage all type relations of the application. While the logical definition is done in the entity data form in connection with the related entities, the type tables can be created in the database here. Additionally, links from and to type tables can be created and managed.
Table Fields |
Link-1/Link-2 |
Type | name the type shaping fir the entity |
Table | name of the database table for the type shaping |
Object Title | title ofthe object |
Default List | name of the default list for the type shaping |
Default Form | name of the default form for the type shaping |
Comment | comment on the type record |
Create Table/View | creates the type table in the database |
Delete Table/View | deletes the type table in the database |
Create List | creates the default type list for the type shaping. |
Create Form | creates the default type form for the type shaping |
Access to Type | opens the type access form |
attribute | master attribute for type (T_ENT_TYP) |
type, entry | string, entry required |
max. no. of characters | 20 |
selection tool | no |
multilingual field | no |
The Name is the entity`s type unique ID in the application's data model.
The type name can be modified after the record has been saved, but not if the database tables or the default list or form have already been created. In this case, these objects must be deleted first.
Table
After editing the type record, you create the table fields for the type attributes. then you can physically create the table in the database.
Object-Title
attribute
master attribute for type (T_ENT_TYP)
type, entry
string, entry optional
max. no. of characters
20
selection tool
no
multilingual field
yes
The title is used in error messages.
Note!
You should always give your objects a title. If you don't, error messages will only contain the object's key, and you won't be able to find the object in a Search mask.
Default List
The default list can only be created when you already have a table for the type in the database. The list contains all significant entity's master attribute fields and all additional attribut fields. The default list record and its field assignment can then be found in the Mask Data form, and can be used as a template for other lists.
Note!
Once a default list has been created, it cannot be overwritten. You first need to delete it from the Mask Data form. The Field Selection menu displays all the lists and forms which already exist.
Default Form
The default form can only be created when you already have a table for the type in the database. The form contains all entity's master attribute fields and all additional attribute fields in a standard layout. The default form record and its field assignment can then be found in the Mask Data form, and can be used as a template for other lists.
Note!
Once a default list has been created, it cannot be overwritten. You first need to delete it from the Mask Data form. The Field Selection menu displays all the lists and forms which already exist.
Comment
attribute
master attribute for type (T_ENT_TYP)
type, entry
string, entry optional
max. no. of characters
255
selection tool
no
multilingual field
no
Create Table/View
Before creating the master table or view, you first need to create the table fields for master attribute or view fields in the Table Fields sublist.
Attention! Do not use Create Table/View while the application is running. Always ensure that no other users are using the tables first.
DataView automatically checks to see if this table exists, and creates one if necessary. If it exists, DataView will adjust it, either directly in the database (for minor modifications) or by starting an Export/Import with the binary loader (for major modifications). Before starting the loader, it makes a security check.
If the loader is used, DataView automatically does the following (you can follow the process in the Messages Console):
If DataView is unable to create the new table because of definition errors, the loader file remains in the tmp folder. After correcting the definitions, the function can be called again.
Note! When altering (setting) the Non-Zero flag (to zero), ensure that there are entries for every possible user record in the modified table column. Otherwise DataView will be unable to load the loader file into the new table.
Note! DataView always uses the binary loader, even if the ASCII loader is selected in the LOADER default.
If you modify definitions for views as opposed to tables, Create Table/View will not modify the view in the database, but delete it completely and create a new view.
More information:
-> Deleting or modifying model objects
Delete Table/View
Attention! Do not use Delete Table/View while the application is running. Always ensure that no other users are using the tables first.
When a type`s table is deleted, the repository retains all the type`s descriptive data.
More information:
-> Deleting or modifying model objects
Create List
You can create the default list as soon as the type relation has table in the database (use Create Table in the Entity Type form).
The default list holds the entity's significant master attribute fields and the additional attribute fields. The default list record and its field assignment can be found in the Mask Data form, and can be used as a template for other lists.
Once a default list has been created, it cannot be overwritten by creating a new one. You first need to delete it from the Mask Data form.
Create Form
You can create the default form as soon as the type relation has table in the database (use Create Table in the Entity Type form).
The default form holds the entity's significant master attribute fields and the additional attribute fields in a default layout. The default form record and its field assignment can be found in the Mask Data form, and can be used as a template for other lists.
Once a default form has been created, it cannot be overwritten by creating a new one. You first need to delete it from the Mask Data form.
Type Access (menu only)
This function extends the scope of the standard Access function. Access privileges apply not only to the type relation object, but also to all lists and forms which refer to it (i.e. every mask which the application calls with userexits such as iwf_lis_typ, iwf_frm_typ,...). For example, users with access to the masks may only edit records in them if they have also been granted access to the type relation object.
More information:
-> Access to records