DT412 Data Item

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

Caution

• 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 Tools → Restart PLANTA service menu item must be executed 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).
  • 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.

DI000242 Index

Here, the index number is specified for data items which are associated with a unique index.

Examples

• Project ID in the Project data table
  • Project ID in the Task data table
  • Project ID in the Project text data table contains the index number of the Index from the Project data table.
• Usually, Index is used to automatically fill IDs that do not exist as data fields themselves.
  • In DT463 Task, Project occurs twice. Once as a path to DT461 Project and once as part of the task number. In both data items, Index = 461_ is entered. In a module which has Project and Task areas, none of both project data items must exist as a data field in the task area, because both project data items in the task record are automatically filled with the content of Project from the corresponding project record via the index.
• Another aspect of Index is that it scans N:1 relationships "reversely".
  • Usually, one project is specified and all of its corresponding tasks are found.
  • Conversely, this N:1 relationship between Project and Task can also be used to find the corresponding project when specifying a task. To do so, index 461 Project must be specified in the Project DI of DT463 Task.

Warning

• Incorrect use will result in unpredictable results.

DI000238 DI

ID number of the data item. Automatically incrementing number which is formed of the license number and a continuous counter.

DI002058 Data item

Name of the data item (incarnation)

DI001591 Name

Name of the data item

DI000239 DT

Data table of the data item

DI023581 Data table

Name of the data table

DI041035 DI Python ID

Identifier of a data item. It is used in connection with Python to identify the data item.

Note

• Names must be usable as Python literals. They must not contain blanks, umlauts, special characters, etc.
• The DI Python ID must be unique in the data table.
  • It can be overwritten in the DF Python ID in the data field.
• The Python IDs of standard IDs are allocated by PLANTA.
• Individual Python IDs must start with an L and the license number.
  • Example: L011_request
• The Python IDs of standard data items must not be changed.

DI027351 DB Schema

In this data field, the data base schema to which the data table belongs is displayed.

DI000215 SQL ID

Here, the SQL column names of (real) data items are stored as they have been defined in the data base.

Note

• SQL ID must be unique. Exception: parallel DIs with SQL = 2 or 4
• Via the Set column name button, the SQL ID can be set automatically.
• Reserved key words of the used DBMS must not be used as an SQL ID.

DI040835 Fetch exit DI

In this data field, the ID of the associated fetch exit data item can be entered for the DI.

DI040836 Incarnation DI

• In this data field, the ID number of the corresponding ID field can be stored for incarnation DIs. This number is set automatically when creating incarnations.
• For DIs with only one incarnation, the DI number of the corresponding incarnation can be stored here.

DI040837 Data item for adjustment source

In this data field, the data source for adjustment between two tables can be stored.

Example

• When creating a status report, the data fields of DT823 Status report are adjusted with those of DT461 Project. For this purpose, the corresponding data source is stored in the data items of DT823. In the Planned effort field, e.g., the ID number of the Planned effort DI from DT461 is stored.

DI000275 Virtual

This parameter determines whether the data item is a real or a virtual data item.

Values

• : Real data item which is available in the database.
• : Virtual data item which is not available in the database, but is detected from data at runtime, e.g. by a value range.

Note

• Virtual data items have no DB pos.

DI000241 DB pos.

This field is necessary for sorting and must not be empty in real data items.

Details

• When creating new real data items (virtual is deactivated), it is reasonable to allocate the DB pos. in ascending manner.
• Virtual data items (virtual is activated) have no DB pos.

Note

• Occupied DB positions may not be used.
• Within compound table IDs which consist of several data items, the distance between the allocated DB pos. must correspond to the DB length.
  • Example DT462
    • ID from DI001049 to DI001092
    • DI001049 does not possess DB pos. = 19 and DB length = 18.
    • The next DI in the data table (here DI001080) may therefore only begin at DB pos. = 37.

DI041365 Column type

Type of the data item in the database (written out). It determines DB type, DF type, and PPMS type of the data item which are automatically set in the selection of the column type.

DI000254 DB length

Database length of the data item. It depends on DB type (Column type).

Values

Note

• For data items with class = 15 (I-text), the DB length can be extended to a maximum of 80 at any time. The space technically required for this purpose is always 4, regardless of the value contained in DB length.

DI000246 DF length

Possible input length in the data field which corresponds to the selected data item

Details

• In alpha numeric data items: Length of the input field in number of characters, the DB length as a maximum

Note

• When defining the DF length, the format must be considered.
• It is possible to write in a field via Python entries that are longer than the defined DF length. However, they are cut to the permitted length when you first click on them.

DI000253 DB type

Type of the data item in the database in the PLANTA syntax (as a code for column type)

Note

• The DB type is set automatically when you select the column type.

Values

DI000244 DF type

Type of the datafield which corresponds to the data item

Note

• The DF type is set automatically when you select the column type.

Values

• A: alphanumeric string
  • Further letters may be appended in order to specify additional type properties:
    • L: set left aligned
    • R: set right aligned
    • G: convert to uppercase letters
    • M: e-mail address
    • P: phone number
  • Order: ALG
• I: UUID field
• N: number
• C: currency
• D: date
  • Stored internally as the number of days since 01/01/70.
• U time
• Y: yes/no
• P: type of relationship for links (SS, SF, FS, FF)
• O: Object protection
  • Stored in the database as a number
  • Displayed on the GUI as a three digit character string:
    • r: reading of record permitted
    • w: writing (changing) permitted
    • d: deletion permitted
    • r, w, and d may only occur once
    • the order is arbitrary
    • Only values which are to take effect must be specified (e.g. rw for read + write
    • the spelling used under LINUX, with "-" for not in effect is allowed (e.g. rw- for read + write)
• W: calculation procedure in DT 467

DI003141 PPMS Type

Note

• The PPMS type is set automatically when you select the column type.

Values

• A: alphanumeric string
  • Further letters may be appended in order to specify additional type properties:
    • L: set left aligned
    • R: set right aligned
    • G: convert to uppercase letters
    • M: e-mail address
    • P: phone number
  • Order: ALG
• B: binary (internal only)
• BL: BLOB continuous text
• BLOB: binary large object
• C: currency
• CLOB: character large object
• D: Date
• IT: text
• ITG: text, large
• L: link
• N2: number with no decimal fraction digits, up to 4 digits
• N4: number with no decimal fraction digits, up to 9 digits
• N8: number with decimal fraction digits
• O: Object protection
• D: date
• UUID: Universally Unique Identifier
• W: calculation procedure in DT 467
• Y: yes/no

DI001990 Link type

Value range type

There are three groups of value range types:

• Px: check on input fields
• Cx: calculation for input/output fields (but usually output fields)
• PY: Python value range

Details

• Customizing of value ranges

DI027352 Value range

Here, the formula for the data item value range is entered/displayed

Details

• Customizing of value ranges
• Python value range functions
• Python api

DI000252 EXIT

ID of the data item exit

Note

• Exits are created, edited, and deleted in the Exits module.

Details

• Customizing of exits

DI000248 Summarization type

Summarization type of the data item. The value is used as a default preset for the respective data field if the data field does not possess any summarization type. If a deviating value is entered in the data field, this value takes effect, except 5 Never summarize, always calculate (see below).

Values

• 0: no summarization (for DFs "Summ. type" from DI)
• 1: sum
• 2: maximum
• 3: minimum
• 4: mean (average)
• 5: never summarize, always calculate

Note

• The Never summarize, always calculate summarization type on a data item prevents any summarization and does not allow deviating summarization types in the data field. For fields with relative values, e.g. percentage specifications, summarization basically does not make any sense. The Never summarize, always calculate summarization type on the data item provides the customizer with a means to prohibit this effectively.
• If, e.g., no summarization type has been stored in a grouped area, the following default summarization types are used.
  • Alpha numeric fields: maximum
  • Numeric fields: sum
  • Date fields: maximum
  • The values of the checkbox fields are not summarized, the checkboxes are always displayed as deactivated

DI001701 Symbol ID

ID of the data item symbol

Example

• DIs with DB type = N, T, U, Y, A, AL, or ALG receive font symbols.
• DIs which are bars receive bar symbols.

Note

• The symbol defined here
  • overwrites possible symbol definitions in the skin (DT030, Symb. input field, Symb. output field and Symb. hyperlink
  • are overridden by the symbol directly in the data field (DT411, Symbol ID parameter).

DI002033 Symbol

Preview of the symbol which is defined for the selected data item via the symbol ID parameter

DI000257 Format ID

ID of the format for date or currency which is saved in the selected data item

Note

• This format
  • overrides a deviating format which has possibly been specified on other levels:
    • on skin level: the formats specified in the Date format, Currency format, or Number format parameters
    • on user level: the formats specified in the Date format, Currency format, or Number format parameters
  • and can itself be overridden by the possibly existing deviating format on data field level of the respective data field (Format ID parameter).
    • Exception: Projection values. Here, the format does not have any effect on the data field.

DI002075 Format

Preview of the format which has been specified for the selected data field in the Format ID parameter.

DI001700 Class

Values

• 0: Data
• 1: Date bar
• 2: Histogram bar
• 3: Time scale
  • For these two DIs, you have to specify the following:
    • Type: T
    • Format: 2 = day, 3 = CW, 4 = month, 5 = quarter, 6 = year
    • Length: output length of the values, e.g. 8 for day
• 4: Incarnation
• 5: RGB color output
• 8: Linkage
• 9: Data items which do not represent values in the database, and which cannot be assigned to any "real" data table. This type of data item is required, for example, as building blocks for complex objects or fields in print areas.
• 10: Area frame dominance symbol
• 11: Projection value
• 12: Histogram scale
• 13: OLE objects
• 15: I-text
• 16: Hyperlink/documents
• 17: Variable object (continuous text)
• 18: Exchange rate dependent on the date (only for C fields)
• 19: CLOB

DI000967 Status

Used as a selection criterion for the customizer's DI selection lists.

Values

• 0: status unknown, visible in the data dictionary
• 1: normal data item, visible in the data dictionary
• 2: complex data items, visible in the data dictionary
• 3: free criterion
• 4: free criterion
• 5: free criterion
• 6: object protection, technical IDs
• 7: PLANTA internal
• 8: reserve data item, not active
• 9: designated for deletion

DI000151 UF DF

Frequency of use in data field. Shows how often the data item appears as a data field in data areas.

Note

• Using the link on this field you can check the usage of this data item in the Data Areas module.

DI000152 UF DDI

Frequency of use of determining data items. This shows how often the data item appears in data areas as a determining data item (DDI).

Note

• Using the link on this field you can check the usage of this data item in the Data Areas module.

DI001561 UF UDI

Frequency of use of child data items. This shows, how often the data item appears as a child data item in DI structures.

Note

• Using the link on this field you can check the usage of this data item in the Data Items module.

DI057664 UF traffic light

Use frequency of traffic lights. Shows how often the data item is used as a traffic light in data areas.

Note

• Using the link on this field you can check the usage of this data item in the Data Areas module.

DI026678 Multiline

This parameter controls whether line breaks are possible in the data field corresponding to the data item.

DI001165 DI note

Controls the display of the notes in the Data Field Information.

Values

• 1: standard only
• 2: standard and customer-specific
• 3: individual only

DI002461 SQL

Information for generating SQL schema files

Values

• 0: data item appears in the generated schema file
• 1: data item has the specification NOT NULL in the schema
• 2: data item does not appear in the schema file which is generated because it is a parallel relationship data item
  • Note
    • Parallel DIs can differ in the data item parameter configuration. For this purpose, the SQL ID of the parallel data items must be identical.
    • DIs with SQL = 2 are required since relations can only be defined via Ident of DI, and Ident up to DI.
• 4: The data item is not displayed in the generated schema file because it is a parallel DB-pos-data item.
  • Parallel DIs can differ in the data item parameter configuration. For this purpose, the DB pos. and the SQL ID of the parallel data items must be identical. Parallel DIs are no longer required from release 39 since relations can now intersect in their DIs.
• Values 0, 1, 2, 4 are combined dually.

Note

• In case a date field in the SQL parameter is marked as NOT ZERO, all ZERO values in date fields are treated as if their default value was 0 (which equates to 1/1/1970).

DI026799 SQL default value

Default value of the data item for the SQL database

Caution! This value is currently not unloaded during schema export.

DI028175 Scheduling

DI066579 Data item configuration

This parameter can be used to configure tooltip modules

DI001867 Created by

When a record is created, the ID (code) of the logged-on user is automatically entered in this field. The creating user is also the owner of a record.

DI000407 Created on

When a record is created, the time of creation is automatically entered here.

DI001868 Changed by

When a record is modified, the ID (code) of the logged-on user is automatically entered in this field.

DI000408 Changed on

When a record is created, the time of creation is automatically entered here.

DI001869 Owner license

DI003037 Date of currency conversion

DI060111 Activated

Defines whether a data item is (de)activated. Data items 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. For this purpose, a schema update file is generated, which can be executed manually if necessary and does not delete the DI.

Values

• : The DI is activated.
• : The DI is deactivated. This means, that the DI does not exist in the data dictionary of the server.

  • If a deactivated DI is used in a module, it will still be displayed in the customizing.

    • If a module is started with a deactivated DI, the behavior will differ according to the DI.
      • If it is a real DI ( virtual = ), the IE: FATAL ERROR: get_dip: DI 123456 not found error message will be displayed.
      • If it is a virtual DI ( virtual = ), the DI will not be loaded, i.e. it will not be displayed.

Note

• If a DI is deactivated, it is displayed grayed-out in the Data Dictionary and in the listbox on the DI field in the Data Areas module.
• If a schema (060096 Activated = ) or a data table (060097Aktiviert = ) is deactivated, all contained DIs are automatically deactivated, i.e., the data table or schema settings overwrite the setting of the DI.

• 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 will only be displayed once in a session, i.e. only upon the first change made to DI060111 or DI060097 or DI060096.
  • After making changes to DI060111, DI060096, or DI060097, the System Customizing must be updated (e.g. via the respective menu item in the Tools menu).

DI062333 HTML template for value range

Stores a template (written in HTML) that enables syntax highlighting in the Python code

DI063233 Historization

The parameter determines whether the selected data item is to be historized or not.

Note

• The parameter only takes effect if the Historization parameter is activated as well.
• Historization is always done record wise. I.e. if changes are made to a DI with activated Historization parameter, an entry for the entire record is created in the history data table. If changes are made to a DI with deactivated Historization parameter, no entry is created in the history data table.