The documentation from version 39.5.17 of PLANTA project can be found in the new PLANTA Online Help.

DT415 Data Table

The creation, modification, and deletion of data items in data tables of the Q1B and Q2B schemas must only be carried out by PLANTA. The only exception is data table DT400, which can contain custom DIs as well.

From S 39.5.20

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

From S 39.5.13 / DB 39.5.5

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

From DB 39.5.3

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

From S 39.5.0

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

Up to S 39.5.0

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

New from S 39.5.20

Attention
  • Each data table in PLANTA must possess a UUID. This includes:
    • a UUID data item
    • the corresponding UUID column in the database

DI000265 DT

Three digit ID of the data table

Note

  • Data tables 600-799 are customer specific tables

DI001571 Data table

Name of the data table

DI000216 Variable Name

Used for databases which are addressed internally by means of SQL. Contains the names of the data tables, as defined in the database.

DI000266 DB Schema

ID of the database

DI000928 Pos.OS

Starting position of the object protection data items. It is the DB position of the Created on DI.

Note

  • If a wrong value is entered here, the object protection fields are possibly set incorrectly or not set at all when data is edited.

DI001985 DI for autom. pos.

For data tables for the records of which an internal sorting is relevant, the ID of the position DI is entered here.

Note

  • Check upon creation, if the data table has an automatic pos. number
    • In case nothing is entered in the DT in DI for autom. pos.:
      • No further check. Insertion is possible.
    • In case the _DI for autom. pos._DI does not have DB type N4:
      • Dialog message "0100". Insertion is not possible.


From DB 39.5.0

Zero value allowed

This parameter determines whether the records of the respective data table are considered valid if they have a ZERO value. This parameter determines whether in referenced data tables (i.e. data tables with a foreign key on this table) ZERO is permitted on the field of the foreign key.

Values

  • Checked: On the field of the foreign key in the referenced data table, ZERO is a valid value.
  • Unchecked: 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 = Checked. 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 = Unchecked. 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.

Up to DB 39.5.0

DI004269 Create dash record

The parameter defines whether dash records of the respective data table are considered valid.

DI056937 DTP cache

From S 39.5.5

The parameter has been deactivated. This function has been replaced by a new parameter in planta_server.conf.

From S 39.5.0

The parameter no longer has a function. This function has been replaced by a new parameter in planta_server.conf.

Up to S 39.5.0

If the parameter is activated, the data is loaded from the corresponding data tables when it is loaded into the DTP cache for the first time. Upon further access it is not used from the database but from the DTP cache.


New from S 39.5.0

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

  • Checked: The data table is activated.
  • Unchecked: 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 = Unchecked), the IE: FATAL ERROR: get_dip: DI 123456 not found error message is displayed.
      • If it is a virtual DI (virtual = Checked), the DI is not loaded, i.e. it is not displayed.

Notes

  • If a schema is deactivated (DI060096 Activated = Unchecked), all contained data tables are automatically deactivated (DI060097 Activated = Unchecked), i.e. the setting of the schema overwrites the setting of the data table.
  • If a data table is deactivated (DI060097 Activated = Unchecked), all data items contained in it are deactivated as well (DI060111 Activated = Unchecked). 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).


New from S 39.5.13

DI063257 Entity Name

A name for access to the entities (data tables) under HQL is allocated here.

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.


New from S 39.5.11

DI063234 Historization

The parameter defines whether the data items of a particular data table can be historized. In order for them to actually be historicized, the Historization parameter must be activated for each individual required data item.

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!

See also: Data Table Historization

DI061211 Universally Unique Identifier DI

In this field the ID of the UUID data item of the data table is specified.

         PLANTA project









 
  • Suche in Topic-Namen

  • Suche in Topic-Inhalten
This site is powered by the TWiki collaboration platform Powered by Perl