Tables

The table code consists of 1 to 10 alphanumeric characters. It needs to start with a letter.

It is the unique identifier for tables in the data dictionary.

Adonix reserved words are prohibited.

The table abbreviation consists of 1 to 3 alphanumeric characters. It needs to start with a letter.

It is the unique identifier for table abbreviations in the data dictionary.

Adonix reserved words are prohibited.

The activity code and module determine whether the table must be created in the folder’s database. A table is created only if:

• The activity code field is empty or the referenced activity code, defined in the corresponding table, is active.

• The associated module is activated for the folder.

Tables associated with activity codes starting with X, Y, or Z are considered specific or custom and are not affected by version changes. You can place these activity codes at line level.

Defines the module to which the table belongs. Module dependencies include:

• Supervisor and Common data must be installed first. Following these, you can install the Stock, Development and Financials modules.
• Stock enables Sales, Purchasing, and Manufacturing.
• Sales enables CRM activities.
• Financials enables Fixed assets and A/P-A/R accounting.

Defines the target database where the table will be generated.

Folder indicates that tables are created using the folder’s database type.

Some exceptional cases, such as external tables, can require additional parameters.

Select this checkbox if a v130 folder needs to access a v140 table.

This forces the table structure to comply with v130 limitations (no CLOB or BLOB types).

Indicates the expected table size. Used for initial sizing during folder creation.

Values are calculated using the sizing formula and folder-defined variables.

During folder revalidation, the number of records is recalculated and updated only if the new value is bigger.

You can manually increase this value, but decreasing it persists only until the next revalidation.

Oversizing is preferred for performance and safety reasons.

It is not necessary to protect the modification of this field with an activity code.

This checkbox determines how translated texts are handled in Crystal Reports:

• Selected: Generates sequential translation files such as textrafra and textraeng (version 140 behavior). These are used in Crystal Reports by the X3TranslatedText function.

• Cleared: Uses the V5 view‑based translation method. There is no file generation. The Crystal report acting on this table uses a view.

New texts to translate should use the view method to avoid overloading sequential files.

This parameterization field does not require an activity code to protect it. It needs to be consistent with the technique used in the Crystal report linked to the table.

This checkbox is used by the return to zero utility, which resets data in a folder.

The utility protects fixed master data (such as products, business partners, accounts, and BOMs) while deleting all transactional data (such as movements, documents, invoices, stock transactions, or work orders). This is typically used after test scenarios or trial start-ups.

When this checkbox is selected, the return to zero utility deletes all rows in the associated table. One of these flags is found in each field, when a field must be reset to zero without the table being emptied.

Use this option when you want a clean slate for movements while preserving master data.

This checkbox controls whether access to the table’s data is restricted within the folder owning the table and certain authorized folders. The same logic also applies to views. Changing this setting requires revalidating the table, so the database configuration can be updated.

• If selected, all folders in the solution can read and write data in the table. This is the case, for system tables, dictionary tables, and some supervisor tables.
• If cleared, access to the table depends on the permissions of the calling folder. A folder can have no access, read-only access, or read/write access. This mode is used for functional tables and most supervisor tables.

When the table is secured, access is authorized for:

• The folder where the table is defined. System tables belong to the solution’s reference folder. For example, X3 for Sage X3.
• Parent folders of the defining folder.
• Folders explicitly authorized in the Folder management function (GESADS) under the Links tab.
• Folders for other solutions, when cross‑solution access is defined through links in the Folder management function (GESADS) under the Links tab.

This checkbox is not updated by patches, since table security is treated as a configuration parameter. When the table is validated and this checkbox is selected, the system generates a .cfg configuration file containing:

$SECURITY
{"LEVEL0"}
End

If other manual directives already exist in the configuration file, they are preserved.

You can also add additional directives manually from the Tables function (GESATB), under the Configuration file section in the Index tab.

This field classifies tables according to a typology used by folder management. The type determines how a table behaves during folder creation, copying, synchronization, updates, and dictionary management. The possible values are:

• Application: This is the default classification. These are standard functional tables belonging to a folder. Their presence depends on activity codes and module management.

• Supervisor: These tables contain supervisor‑level data that must exist in every folder, but are not part of the dictionary. For example, users, operation logs, and attachments. They are always present in each folder.

• Sage X3 system: These tables contain global system data, not tied to any specific folder. For example, folder management tables and batch server tables.

  They appear only in the supervisor folder, named X3, PAYE, or GX depending on the product.

  They are common to all folders and never copied, so Copy types and Copy options fields do not apply.

• Dictionary: These tables are part of the dictionary stored in every folder, such as reports, actions, screens, and data types. They are always present and handled in a special way during updates, through the dictionary fusion procedure. As for system tables, Copy types and Copy options fields do not apply.

• Internal: This type is used only during internal software development. No delivered tables use this type and it must not be used for external development.

This field defines whether data should be transferred from the reference folder to the new folder when the table is created.

It applies during folder creation and influences how initial data is populated.

You can select the following values:

• No copy: The table is created empty. No data is transferred from the reference folder.

• Automatic copy: Data from the corresponding table in the source folder (by default, the reference folder) is automatically copied into the new folder’s table.

• Conditional copy: Data is copied based on logical groups. Each group corresponds to a value selected from local menu 26, entered in the Copy option field.

  Each group includes a set of related tables that must be copied together.

  Common predefined groups include:

  • Users and profiles

  • Miscellaneous tables

  • Sequence numbers

  • Parameters

  • General chart of accounts

  During table creation, the system prompts for each group whether its data should be copied. Select Yes or No.

You can use this field only when the Copy type field is set to Conditional copy.

You can decide which subgroups of table data are copied from the source folder to the destination folder.

This checkbox defines the copy method in the dictionary validation.

• Select this checkbox to apply a filter using the Legislation field of this table or its master table.

• If unselected, no additional legislation filter is applied.

When the folder is validated, only the data whose legislation is either managed by the folder or left empty will be retrieved into the validated folder.

This parameter is used internally during the industrialization of a software version.

It determines how the table is delivered in the reference folders during installation or version deployment.

The possible values are:

• Not delivered: The table is not generated in the Sage X3 folder.
• Delivered empty: The table is delivered without any data.
• Delivered with indus data: The table is delivered with the industrialization (indus) folder data, such as styles, import templates, and other setup elements.
• Common data: The table is delivered from the X3REFFRA reference folder.
• Data by country: The table is delivered from an X3REFxxx reference folder, where xxx corresponds to the language or locale selected during installation on the customer workstation.

This field identifies the primary descriptive field in the table. It contains the name of the column that holds the main title or description of a record. It is used to automatically display the readable title of a record when its key is known.

For example, in screens, deletion controls, code changes, and similar functions.

This field identifies the short description column for the table.

It is typically used when a condensed label is required in the UI or in lists.

This field specifies the name of the column containing a symbol or code representing the record.

It can be used in displays, lookups, or when a graphical or abbreviated identifier is required.

For numeric descriptive fields, this value defines the number of decimals to be used.

It is ignored for non‑numeric formats.

Define the field name for the table as it will display in the software. A field with the name FIELDNAME defined in an ABV abbreviation table can be accessed using the [F:ABV]FIELDNAME syntax.

For custom or specific fields, the field name must start with X_, Y_, or Z_.

In the database, each zone corresponds to one or more fields, according to whether the zone is sized. The corresponding fields are named FIELDNAME_0, FIELDNAME_1, and FIELDNAME_2.

To enter and display the corresponding field on a screen, it is assigned the same name in the screen dictionary. The screen and the table are used simultaneously in object management.

The field type is defined here, which characterizes the entry format (numeric, alphanumeric, date, and so on) and the consistency controls (for example, reference to a table).

The main generic types are:

• A: Alphanumeric
• C: Short integer
• L: Long integer
• DCB: Decimal
• D: Date
• M: Local menu
• MM: Local menu with filter
• ACB: CLOB
• ABB: BLOB

However, many other predefined types exist. They often reference an auxiliary table (currency, country, and so on). A dedicated dictionary is used to describe them. You can select them using the F12 key, which displays the list.

Defines the local menu number associated with the field defined on the line.

When a field is of the local menu type (from 1 to 255), it corresponds to the position of a title in a table called local menu, stored in the APLSTD messages table.

On entry or on display, the following appear depending on the user interface settings:

• Either a title selected from a scrolling list, commonly called a combo box.
• Or a list of buttons.

The advantage of this type of entry is that the list of choices is displayed in the user's connection language.

Each local menu number defines the list of available titles. For example, local menu 1 corresponds to the No/Yes choice in this order. In this particular case, the user interface can also display a checkbox.

Used to define the length of a field when this field uses a generic data type for which the length is not fixed.

This is particularly the case for A and DCB types.

An activity code is used to:

• Make an element optional in the dictionary if the value associated with the activity code is null.
• Identify the specific or custom elements if they are marked with a code starting with X, Y, or Z.
• Define a maximum number of lines when the activity code applies to elements in a grid.

If the activity code is disabled:

• The marked element will not be useable.
• The associated code will not be generated nor activated.

Dimension of the field in the table. You can also assign the dimension based on the activity code.

Title for the field over three lengths: short title being limited to 12 characters, normal title at 20 characters and the long title at 35 characters.

These titles are translatable texts and they are stored in a dedicated table, ATEXTE. When a new text is entered, after creation of a section, a window appears whose title is Text. There is then a choice between the following three options:

• consider that the entered text is a new text and integrate it in the database by assigning a new number. This number must be greater than 50,000 (because it is a custom/specific text).
• search for a text close to that entered in order to select the same. A selection will then open for this.
• cancel the text entry.

When in modification mode for a text already entered there is also an additional choice of displaying in the window, where the title is presented Text nnn (nnn being its number). It is then possible to modify the text whose number is given, to conform with the text that is being entered (this modification is made wherever the corresponding text is used, once the corresponding screens have been revalidated).

In addition, it is possible to call, using the right button on the mouse, the Abbreviation function that is used to select one of the standardized abbreviations defined when a title is too long (the use of abbreviations must be avoided as far as possible to facilitate the readability of the screens).

Title for the field over three lengths: short title being limited to 12 characters, normal title at 20 characters and the long title at 35 characters.

These titles are translatable texts and they are stored in a dedicated table, ATEXTE. When a new text is entered, after creation of a section, a window appears whose title is Text. There is then a choice between the following three options:

• consider that the entered text is a new text and integrate it in the database by assigning a new number. This number must be greater than 50,000 (because it is a custom/specific text).
• search for a text close to that entered in order to select the same. A selection will then open for this.
• cancel the text entry.

When in modification mode for a text already entered there is also an additional choice of displaying in the window, where the title is presented Text nnn (nnn being its number). It is then possible to modify the text whose number is given, to conform with the text that is being entered (this modification is made wherever the corresponding text is used, once the corresponding screens have been revalidated).

In addition, it is possible to call, using the right button on the mouse, the Abbreviation function that is used to select one of the standardized abbreviations defined when a title is too long (the use of abbreviations must be avoided as far as possible to facilitate the readability of the screens).

Title for the field in three lengths. The short title is limited to 12 characters, the normal title to 20 characters, and the long title to 35 characters.

These titles are translatable texts and are stored in a dedicated table, ATEXTE. When a new text is entered, after creating a section, a window titled Text displays. You then have the following three options:

• Consider that the entered text is a new text and integrate it into the database by assigning it a new number. This number must be greater than 50,000 (because it is a custom or specific text).
• Search for an existing text similar to the entered one and select it. A selection window will open for this.
• Cancel the text entry.

When modifying an already existing text, there is an option displayed in the window, where the title appears as Text nnn (with nnn being its number). It is then possible to modify the text corresponding to that number so that it matches the newly entered text. This change is applied wherever the corresponding text is used, once the relevant screens have been revalidated.

In addition, by right-clicking, it is possible to call the Abbreviation function, which lets you select one of the standardized abbreviations defined when a title is too long.

Avoid using abbreviations whenever possible to maintain screen readability.

These options are represented by characters that can be concatenated when several options are required.

You can select these options through a selection window.

A detailed description for all possible options is available.

Code for a table linked to the one being modified through the current field.

For the data types that reference an object, this field is assigned automatically.

This field is entered only if a linked table has been specified. If this field is not assigned, the link is made directly from the field on the current line (which assumes that the primary linked table key is not the only component).

If the primary key contains several components, the link expression must be written in the form: comp1;comp2;comp;..., where comp1,comp2, comp3,... are the components of the key.
Here are a few examples of possible expressions:

• If a MYFIELD field is controlled in one of the miscellaneous tables (for example, table number 43), the 43; MYFIELD value will be entered in the Linked table column linked to the ATABDIV value and in the Link expression column.

• If a MYFIELD field is indexed, the expression can use the index variable, which can vary from 0 to dim(MYFIELD)-1.

  Examples: Multiple statistics groups (products, suppliers, customers, and so on) whose key structure is the group number followed by a statistics code. The key expression is then written as: index+1; MYFIELD (index).

• If the key component is a global variable, you need to specify the [V] class before the name of this variable.

Defines the initial value assigned to a global variable when it is used in a link expression or API context.

This ensures the global variable has a valid default value when the table is accessed.

This field is linked to the Copy legislation checkbox.

It specifies the field that contains the legislation, or the field that links to the master table containing the legislation.

During the cancellation of a line in the linked table (source table), a specific action can be applied to the table currently being modified or created (destination table). This action is defined by the following codes:

• Block: Cancellation of the record in the source table is impossible if a linked exists with the table currently being defined.
• Delete: Records in the destination table that match the link with the source table are deleted.
• RTZ: The linked field in the destination table is reset to zero.
• Other: No specific action is performed.

This field is used to indicate whether the coherence verification utility must check the link.

You can define whether the field can be empty or whether it needs to contain a value (not empty).

An empty field can be:

• A string with zero length

• A null numeric value

• A local menu value equal to zero (no choice made)

• An empty date [0/0/0]

When the field is a key in a table, if the cancellation control is set to RTZ, the link cannot be mandatory because the cancellation can clear the key field. In this case, the Mandatory field is automatically set to No.

Indicates whether the field is affected by the Return to zero (RTZ) process.

When enabled, the field is reset to zero during the RTZ processing applied to the table.

If RTZ is active for the field and the field is part of a key, the field cannot be mandatory, since the reset operation can clear its value.

This field corresponds to the name under which the index is known in the database. A standard naming convention is used in all application tables. Keys are named using the table abbreviation followed by 0 for the primary key, 1 for the secondary key, and so on.

For the specific or custom indexes, this code must begin with one of the following letters: X, Y or Z.

Enter here the list of fields that make up the index. The fields are separated by a + if the index contains multiple fields. For example, in the FACILITY sites table, there is a key defined as LEGCPY+FCY.

A descending sort field is preceded by the - sign. This is used in the left list.

The first field in the index is written without a sign and is therefore considered ascending.

Define whether the key can or cannot accept duplicate values (homonyms).

Use this column to define a default clustered index provided by Sage.

If you select No, a default clustered index is not defined.

If you select Yes, this is the clustered index used.

To change the clustered index, you need to define a Specific cluster index or select the Clustered index disabled checkbox to prevent the use of any clustered index.

This value can be modified by patch.

This default setting does not apply if you already set up a clustered index locally in the configuration file or in the Specific clustered index field.

Select Yes to define this index as the clustered index. Only one index can be selected per table.

A clustered index is a specific type of index that determines the physical order in which records are physically stored in the table.

This is a special setting that can never be modified by patch.

If this field is not assigned, the index will always be present.

If this field corresponds to an inactive activity code, the index will not be generated.

It is possible to add a specific or custom key using an activity code that begins with X, Y or Z.

Use this column to disable the clustered indexes for the table. The clustered index delivered by Sage in the Default clustered index column is disabled, even if you have not defined a clustered index in the field dedicated to this setup.

Select this checkbox to disable the clustered index.

A text describing the technical configuration of the table in the database is entered in this section. This text is recorded in a file named name.cfg in the FIL directory of the application.

This file is used by the valfil instruction.

Refer to the dedicated technical annex for more information.

Select this checkbox to log each time a record is created in the table.

Select this checkbox to log each time a record is modified.

Select this checkbox to log each time a record is deleted.

Select this checkbox to activate automated workflow notifications based on audit activity.

A workflow batch task generates a workflow event for each line in AUDITH whose workflow status is to be processed, then updates the status to processed.

Select this checkbox to activate incremental synchronization of the BI fact table.

This option is available only when the ABI activity code is active.

During data warehouse generation, this flag is updated according to the update type defined for the fact table.

According to BI synchronization rules, if a BI fact table is incrementally synchronized from a Sage X3 table, that table must be flagged AUDIT BI.

Specify the key used to identify audited records.

It is recommended to use a key without duplicates (homonyms) to ease record identification in audit inquiries.

If not specified, the primary key is used.

Lists the fields to be audited.

Leave this grid empty if you only want to log record‑level operations without logging field content.

A log entry is created when at least one condition defined for the field is met.

For record creation or deletion, a field log is always generated.

Defines the operator used to evaluate the condition.

For example: =, <>, >, or <.

Select this action in the Audit tab to load the grid with every field defined in the table.