DT420 DB Schema

• 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).

DI060096 Activated

Defines whether a schema is (de)activated. If a schema is deactivated, all data tables or DIs contained in it are automatically deactivated. Schemas that are to be deleted can be deactivated in a first step, e.g., for test purposes, and finally be deleted in a second step.

Values

• : The schema is activated.
• : The schema is deactivated. This means, that the schema does not exist in the Data Dictionary of the server. The following applies to all DIs of all data tables of a deactivated schema:
  • 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 data tables contained in it and the data items contained in the data tables are automatically deactivated (DI060097 Activated = and DI060111 Activated = ), i.e. the setting of the schema overwrites the setting of the data table and the data items.
• 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).

DI060099 Generated NEW

Values

• : When saving changes that require a schema update, the respective file is generated for the update.
• : When saving changes that require a schema update, no file is generated for the update.

Note

• The same applies to the following Python functions for generating the respective SQL commands:
  • db_schema_create
  • db_custom_schema_create
  • db_custom_lines_create

DI060099

Values

• : When saving changes that require a schema update, the respective file is generated for the update.
• : When saving changes that require a schema update, no file is generated for the update.

Note

• The same applies to the following Python functions for generating the respective SQL commands:
  • db_schema_create
  • db_custom_schema_create
  • db_custom_lines_create

• 1: Check I-texts
  
• 2: Check and write I-texts
  
• 3: Check hyperlinks
  
• 4: Check and write hyperlinks
  
• 5: Check I-texts and hyperlinks
  
• 6: Check and write I-texts and hyperlinks
  
• 7: Check relations
  
• 8: Check object protection
  
• 9: NEW Check dash records
  
• 10: NEW Check and write dash records
  
• 11: NEW Check everything (I-texts, hyperlinks, relation, object protection, dash records)
  

• 1: Check I-texts
  
• 2: Check and write I-texts
  
• 3: Check hyperlinks
  
• 4: Check and write hyperlinks
  
• 5: Check I-texts and hyperlinks
  
• 6: Check and write I-texts and hyperlinks
  
• 7: Check relations
  
• 8: Check object protection
  
• 9: Check everything (I-texts, hyperlinks, relation, object protection)