DT415 Data Table

• If system customizing changes are made to data tables or data items (e.g. new data items are created, data item parameters are changed), the NEW Tools Restart PLANTA service menu item must be carried out in order to make the changes visible.
  • Note: If you click on the menu item, all open client connections (sessions) are closed. During restart, new client connections are not possible. This does not apply to changes made to I-texts, e.g. changes to the DI name or adjustment of value ranges (also of the VR type).
  • NEW Before restarting the service, the target directory must be deleted so it can be created anew upon server restart in order to make sure that the POJO classes contained in it, which are responsible for the meta data of the data dictionary, are generated anew.

• If system customizing changes have been made to data tables or data items (e.g. new data items have been created, data item parameters have been changed), the Reload system customizing button must be clicked on, or the Tools Reload system customizing menu item must be carried out in the Data Dictionary or Data Items modules to make the changes visible.
  • This does not apply to changes to I-texts, e.g. changes made to the DI name or adjustment of value ranges (also of the VR type).

• If system customizing changes have been made to data tables or data items (e.g. new data items have been created, data item parameters have been changed), the NEW Reload system customizing button, or the menu item of the same name, must be clicked on in the Data Dictionary or Data Items modules to make the changes visible.
  • This does not apply to changes made to I-texts, e.g. changes made to the DI name or adjustment of value ranges (also of the VR type).

• If system customizing changes have been made to data tables or data items (e.g. new data items have been created, data item parameters have been changed), the NEW Restart server button, or the menu item of the same name, must be clicked on in the Data Dictionary or Data Items modules to make the changes visible.
  • This does not apply to changes made to I-texts, e.g. changes made to the DI name or adjustment of value ranges (also of the VR type).

• If system customizing changes have been made to data tables or data items (e.g. new data items have been created, data item parameters have been changed), the Reload forking server button, or the menu item of the same name, must be clicked on in the Data Dictionary or Data Items modules to make the changes visible.
  • This does not apply to changes made to I-texts, e.g. changes made to the DI name or adjustment of value ranges (also of the VR type).

• Each data table in PLANTA must possess a UUID. This includes:
  • a UUID data item
    • The ID of the UUID data item must furthermore be stored in the Universally Unique Identifier DI field.
  • the corresponding UUID column in the database

Zero value allowed

Values

• : On the field of the foreign key in the referenced data table, ZERO is a valid value.
• : On the field of the foreign key in the referenced data table, ZERO is an invalid value.

Example

• For data table 441 Language, Zero value permitted = . In data table 462 Project note there is a foreign key for data table 441.
  • Result: In DT 462 Project note a record can be created in which the Language code field is empty or in which database is ZERO.
• For data table 467 Resource, Zero value permitted = . In data table 466 Resource assignment there is a foreign key for data table 467.
  • Result: In DT 466 Resource assignment no record can be created in which the Resource field is empty or in which database is ZERO.

DI004269 Create dash record

DI060097 Activated

Defines whether a data table is deactivated. If a data table is deactivated, all DIs contained are automatically deactivated. Data tables which are to be deleted can be deactivated in a first step, e.g., for tests, and finally be deleted in a second step.

Values

• : The data table is activated.
• : The data table is deactivated. This means, that the data table does not exist in the Data Dictionary of the server. The following applies to all DIs of a deactivated Data table:
  • If a deactivated DI is used in a module, it is still displayed in the customizing.
  • If a module is started with a deactivated DI, the behavior differs according to the DI.
    • If it is a real DI (virtual = ), the IE: FATAL ERROR: get_dip: DI 123456 not found error message is displayed.
    • If it is a virtual DI (virtual = ), the DI is not loaded, i.e. it is not displayed.

Notes

• If a schema is deactivated (DI060096 Activated = ), all contained data tables are automatically deactivated (DI060097 Activated = ), i.e. the setting of the schema overwrites the setting of the data table.
• If a data table is deactivated (DI060097 Activated = ), all data items contained in it are deactivated as well (DI060111 Activated = ). The opposite, however, is not true. It is possible to deactivate individual data items in an active data table.
• As soon as the value is changed and saved in one of the three parameters mentioned (DI060111, DI060096, or DI060097), a script is created in the work directory and a message is displayed at the same time: Due to your changes to DT412, your database must be adjusted. Please select the appropriate ./22_*.sql file (depending on the database system) and run the content on your database.
  • The message is only displayed once in a session, i.e. only upon the first change to DI060111 or DI060097 or DI060096.
• After changes to DI060111, DI060096, or DI060097, the System Customizing must be updated (e.g. via the respective menu item in the Tools menu).

DI063257 Entity Name

Notes

• The entity name must be unique.
• The entity name must not be empty.
• In the standard, English entity names are allocated.
• The entity name must comply with the Java class name conventions.

DI063234 Historization

Note

• If you try to activate the Historization parameter for a data item without activating the Historization parameter on the data table, the following message is displayed: Historization not possible, historization is disabled for DT!