Development > Data and parameters > Tables > Data types 

This function is used to define the data types that can be used in all the dictionaries where the data is defined : screen fields, table fields, report parameters...

A certain number of characteristics(internal type, length, actions...) are attached to a type to be automatically assigned to the fields using this type. It is not however necessary to define all the characteristics of a type. Indeed, the non-defined characteristics at the type level will be requested at the definition of the screen, which makes it possible to define the generic types. ADONIX delivers a certain number of data types containing only the internal type, that is to say the field storage type. These data types cannot be modified. Here is the list :

Type code

Definition

A

Alphanumeric string

ABB

Blob

ACB

Clob

C

Short integer

D

Date

DCB

Decimal amount

L

Long integer

M

Local menu

MM

Local menu with the possibility to filter the elements

 

  M or MM corresponding to a local menu where the number is given by the contents of the Menu column in the table or screen dictionary. A local menu is a title table, entered either in the form of a combi box or in the form of radio buttons in the form of a check box (if it is local menu 1, which contains the values Yes/No). In the database only the choice number is stored in the list (0 if the field is not assigned, 1 if the first title in the list is selected and so on).

In the table shown below are displayed the data types corresponding to the supervisor technical elements :

Type code

Definition

ABS

Variable at the bottom of the grid

 AT

Field indicating the blob type

 AX1

Translated text (length 12)

 AX2

Translated text (length 20)

 AX3

Translated text (length 30)

W

Filler

  ABSidentifies the screen field at the bottom of the grid. This field is mandatory for all the grid section defined in a screen. If the grid will accept entries, this field will be in entry mode; if the grid is hidden, this field will be in hidden mode.

  W identifies a filler. This data type placed in a screen field will leave a space between the previous field and the next field, if theses two fields are on the same line. It is however preferable to use, to this end, the column section in the screen dictionary and to only use the fields with the data type W as a last resort.

  AX1, AX2, AX3 identify the translated texts. In fact, this field is not created in the database. Its field name serves to identify the translated text that will be stored in the dedicated table ATEXTRA.

Displayed in the table below is a list of the functional type that are particularly important (this list is not exhaustive):

Type code

Definition

MD1 to MD4

Formats for the amounts depending on the currency (which must be on-line) : the 4 corresponding formats are defined in the currency table.

MC1 to MC4

Formats for the amounts depending on the currency : These are the same types as above, but they are optimised for use in a scrolling grid in which a column is entered with a currency that does not depend on the current line.

MS1 to MS4

Amounts in the site currency

ADI

Code stored in a miscellaneous table (where the number is given in the table dictionary, by the link expression).

HM

Hour : minute

QTY

Quantity

QT1 to QT5

Optimised quantity for the grid section (same notes as above : the format of a column must not depend on the current line)

    Prerequisite

    SEEREFERTTO Refer to documentation Implementation

    Screen management

    Header

    Fields

    The following fields are present on this tab :

     

    • Title (field ZINTITTYP)

     

    Close

     

    Entry screen

    Fields

    The following fields are present on this tab :

    Object

    Used to indicate if necessary, the object associated with the data type. The linked table managed by the object is displayed.

    The presence of an object code automatically starts:

    • The existence control
    • The selection and advanced selection windows
    • The possibility of a tunnel to the object management
    • The possibility to display the current entry properties of the object.

     

    Format

    • Grid format (field OPTTAB)

    Used to optimize the display of the large grids. This is reserved for the data type of the standard, because it requires a particular process in the supervisor.

    • Parameter : represents the parameter code to enter in the screen management for the data type.
    • Variable : represents the field that will be initialised by the parameter value in the before_entry action of the bottom of grid variable.

     

    • field W1

     

    • Variable (field VARTAB)

    Used to optimize the display of the large grids. This is reserved for the data type of the standard, because it requires a particular process in the supervisor.

    • Parameter : represents the parameter code to enter in the screen management for the data type.
    • Variable : represents the field that will be initialised by the parameter value in the before_entry action of the bottom of grid variable.
    • Default value (field VALDEF)

    Ce champ permet de saisir une formule de calcul pour attribuer une valeur par défaut aux zones de ce type.

    An example can be seen in the CRY type, which defines the country code : the GPAYS variable, which defines the local country, is proposed as the default value for all the fields of this type. This default value is automatically proposed in the screen fields using this type of data. However, if a field using this data type has its own default value in the screen, it's this that will be used; in this case, the default value for the data type is ignored.

    Table Actions

    • Type (field ACTTYP)

    This grid is used to declare the actions catalogued in the actions dictionary. The objective is that for all fields having this data type, the actions defined here will be systematically executed.

    If a single action is defined is defined for both the data type and the screen field, the actions will be executed consecutively and in the following order : it is the data type then the field. There is a particular case for the "selection" and "button" actions, for which only the screen field action will be executed.

    This grid makes it possible to define the particular actions associated with the field. The possible action types are :

    • Before-field : Action before all entry or display of the field. It can be used, for example, to define the format of the field.
    • Init_button : used to define the button names in the contextual contextual.
    • Init: Used to initialize a field.
    • Before_entry : Action carried out before each entry. For example it can be used to position mkstat and so not enter it.
    • Control : Makes it possible to test the validity of the field.
    • After-field : Carried out after the control if this is valid. Makes it possible for example to assign or to display other fields.
    • After-modif : Ditto but is not started unless the field has been modified.
    • Selection : Started by the F12 key.
    • Button 1 : Triggered by the F9 key (reserved for the tunnels)
    • Button 2 to 20 : The F4 key makes it possible to have a list of contextual menus.
    • Before_line : Uniquely for the scrolling menus, making it possible to so something each time line modification is started.
    • After_line : Uniquely for the scrolling grids, making it possible to do something after each line entry.
    • Click : Only for the icon fields

    Indicate the actions to be carried out in a systematic manner on the type of data.
    The actions STD, SPE or SPV that are linked to a particular function will not be entered at this level.
    It is possible to enter several actions for the same action type except for the "button" or "icon" or "selection" actions

    • Execution (field EXEACT)

    This field is used to define the context of the action execution :

    • Interactive : on-line entry.
    • Import / Web service : loading of the record web service or import mode. The execution of the actions on the fields is carried out when all the fields are entered.
    • Always : in all cases.

    Close

     

    Tab Convergence

    Fields

    The following fields are present on this tab :

    Object

    Used to indicate if necessary, the object associated with the data type. The linked table managed by the object is displayed.

    The presence of an object code automatically starts:

    • The existence control
    • The selection and advanced selection windows
    • The possibility of a tunnel to the object management
    • The possibility to display the current entry properties of the object.

     

    Format

    • Grid format (field OPTTAB)

    Used to optimize the display of the large grids. This is reserved for the data type of the standard, because it requires a particular process in the supervisor.

    • Parameter : represents the parameter code to enter in the screen management for the data type.
    • Variable : represents the field that will be initialised by the parameter value in the before_entry action of the bottom of grid variable.

     

    • field W1

     

    • Variable (field VARTAB)

    Used to optimize the display of the large grids. This is reserved for the data type of the standard, because it requires a particular process in the supervisor.

    • Parameter : represents the parameter code to enter in the screen management for the data type.
    • Variable : represents the field that will be initialised by the parameter value in the before_entry action of the bottom of grid variable.
    • Default value (field VALDEF)

    Ce champ permet de saisir une formule de calcul pour attribuer une valeur par défaut aux zones de ce type.

    An example can be seen in the CRY type, which defines the country code : the GPAYS variable, which defines the local country, is proposed as the default value for all the fields of this type. This default value is automatically proposed in the screen fields using this type of data. However, if a field using this data type has its own default value in the screen, it's this that will be used; in this case, the default value for the data type is ignored.

    Table Actions

    • Type (field ACTTYP)

    This grid is used to declare the actions catalogued in the actions dictionary. The objective is that for all fields having this data type, the actions defined here will be systematically executed.

    If a single action is defined is defined for both the data type and the screen field, the actions will be executed consecutively and in the following order : it is the data type then the field. There is a particular case for the "selection" and "button" actions, for which only the screen field action will be executed.

    This grid makes it possible to define the particular actions associated with the field. The possible action types are :

    • Before-field : Action before all entry or display of the field. It can be used, for example, to define the format of the field.
    • Init_button : used to define the button names in the contextual contextual.
    • Init: Used to initialize a field.
    • Before_entry : Action carried out before each entry. For example it can be used to position mkstat and so not enter it.
    • Control : Makes it possible to test the validity of the field.
    • After-field : Carried out after the control if this is valid. Makes it possible for example to assign or to display other fields.
    • After-modif : Ditto but is not started unless the field has been modified.
    • Selection : Started by the F12 key.
    • Button 1 : Triggered by the F9 key (reserved for the tunnels)
    • Button 2 to 20 : The F4 key makes it possible to have a list of contextual menus.
    • Before_line : Uniquely for the scrolling menus, making it possible to so something each time line modification is started.
    • After_line : Uniquely for the scrolling grids, making it possible to do something after each line entry.
    • Click : Only for the icon fields

    Indicate the actions to be carried out in a systematic manner on the type of data.
    The actions STD, SPE or SPV that are linked to a particular function will not be entered at this level.
    It is possible to enter several actions for the same action type except for the "button" or "icon" or "selection" actions

    • Execution (field EXEACT)

    This field is used to define the context of the action execution :

    • Interactive : on-line entry.
    • Import / Web service : loading of the record web service or import mode. The execution of the actions on the fields is carried out when all the fields are entered.
    • Always : in all cases.

    Close

     

    Tab Class

    Fields

    The following fields are present on this tab :

    Type

    • Type (field TYPSELSYR)

     

    Details

     

    • Title (field PROTYP)

     

    • Supervisor mgmt (field SUPFLG)

     

    • Special format (field FMTPROSYR)

     

     

    Default representations

     

     

     

    Table Rules

    • Type (field TYPRUL)

     

    • Script (field TRTRUL)

     

    • Sub-program (field PRGRUL)

     

    • Sequence (field ORDRUL)

     

     

    • Active (field ENARUL)

     

    Table Parameter definition

    • Code (field PARCOD)

     

    • Title (field ZPARTIT)

     

    • Key (field PARCLE)

     

    • Type (field PARTYP)

     

     

    • Dim. (field PARDIM)

     

    • Method (field PARMOD)

     

    Close

     

    Functions accessed by right click on the grid

    Reference control addition
    Update parameters

     

    Fermer

     

    Tab Links

    Fields

    The following fields are present on this tab :

    Table Links

    • Link type (field TYPLNK)

     

     

    • Sequence (field ORDLNK)

     

     

    Close

     

    Reports

    By default, the following reports are associated to the function :

     ATYPE : Data type

    This can be changed by a different setup.

    Specific Buttons

    This button is used to update and compile the WWGLOBLON process. In this process, for each alphanumeric data type a global variable of the shortint type contains the entry length for the data type. These variables are named GLONxxx ( xxx = data type). These variables will be used during the definition of the work variables linked to a data type in the process. This is used to alleviate the problems linked to a modification of a data type length.

    Example of the use of these variables :
    # work variable for the Product reference
    Local Char WITEM (GLONITM)
    WITEM = [F:ITM]ITMREF  

    The following fields are present on the window opened through this button :

    Block number 1

    • field OBJET

     

    • field CLES

     

    Block number 2

    • From folder (field DOSORG)

    This field is used to define the folder from which the record is going be copied. The possible syntaxes are described in the dedicated appendix.

    • All folders (field TOUDOS)

    This option is used to copy the record to all the folders defined in the dictionary (ADOSSIER table from the current solution).

    • To folder (field DOSDES)

    This field used to define the folder in which the record is going be copied. The possible syntaxes are described in the dedicated appendix.

    Close

    This button is used to copy the data type definition to another folder.

    Menu Bar

    Documentation / Paragraphs

    This function is used to access the documentation management on the first paragraph of the documentation (if there is one) associated to the current record.

    Documentation / Links

    This function is used to access the links management. It is used to define the links between the current and other records (for example the links between functions and setups). These links are specific to the documentation and are used to load the generation of documentation structures.

    Documentation / Generation

    This menu is used to launch a documentation generation. The generation can also be launched from the [Generation] button at the bottom of the window.

    Three types of generation can be launched one by one or simultaneously:

    • the generation of the documentation structure from the dictionary (tables ADOCUMENT, ADOCBLB, ADOCCLB).
    • the generation of the documentation from the previous tables.
    • the generation of the field documentation.

    The range suggested by default takes into account the current record but it can be modified upon launch.

    Error messages

    In addition to the generic error messages, the following messages can appear during the entry :

    Incorrect length

    The length associated with a field is incompatible with the given internal data type.

    Local menu not defined

    The local menu number is incorrect

    Invalid character

    Incorrect characters have been entered in the format.

    Incorrect format

    The format that has been defined is invalid.

    Incorrect option

    The option associated with the format is invalid.

    Data type not modifiable

    The database data types are not modifiable. Example : "A","C","D","L","M","MM","DCB","AV","W","ACB","ABB".

    Tables used

    SEEREFERTTO Refer to documentation Implementation