Setup > General parameters > Personalization > Vocabulary 

The Sage x3 software makes it possible to work in several languages (notably French, English, Spanish, Italian, Portuguese, Chinese). The user, on connecting to the software, chooses the language in which the dialogue screens must be displayed.

This functionality is based on the presence of two tables in the database, storing all the elements likely to be translated : The ATEXTE table, which contains the texts identified by a number, and the APLSTD table, which contains the messages organized in chapters. In these two tables, the language code is present, in order to stock the text in several languages.

The ATEXTE table corresponds to the field titles located on the screens. The standard texts are stored with a number less than 50,000. Specific/custom text is stored with a number greater than this. The access key to this table is composed of two elements : the language and the message number.

The APLSTD table contains the error message or warnings sent by the software, as well as the local menus and the radio button titles. Each chapter, identified by number, regroups all the elements identified by a number in the chapter. The access key includes the language code, the chapter and the number.

These elements are delivered in a standard fashion with each new major version and can be re-updated at each intermediate version for all standard languages (with the exception of custom/specific texts, and certain local menus that can be parameterized). Their inclusion in the screens is made during the validation of the software's screens and windows (for performance reasons, the texts are directly inserted as a function of the language in the interface descriptions in XML format).

It can be useful to be able to personalize certain vocabulary elements. For example, it may be appropriate to replace the generic term Representatives by the term Commercial agents, or possibly to replace the term Routing by the term Recipe. To carryout such modifications directly in the APLSTD and ATEXTE table does not make sense, because these are not permanent. It is for this reason that a specific table has been created, managed by this function.

This table, named AVOCAB in the database, stores a list of exceptions. It is in this way possible to say, for a given language, a chapter and/or a given text number, that a special text replaces the standard text. At the generation of the interface code (by the revalidation of the screens and windows, or more globally by a folder validation), the texts that are personalized in this way, will replace the standard texts in the generated XML code.

It should be noted that only the standard messages (i.e. the messages from ATEXTE where the number is less than 100,000) can be personalized.

As standard, the AVOCAB table is delivered empty, and it is never modified by an update.

The function described here is used to update this table in a given language.


SEEREFERTTO Refer to documentation Implementation

Screen management

Entry screen


Firstly enter the a working language then a grid containing the texts to be modified.




The following fields are present on this tab :

Block number 1

This field defines the language in which the standard messages are to be modified.

  • Version (field VER)


  • Current version (field LIBCUR)



  • Text type (field TYP)

This type can correspond to :

  •  either to the messages table(APLSTD) that notably stores the local menus. In this table, the texts are structured in the form of a chapter number and a message number.
  • or to the texts table (ATEXTE) that notably stores messages coming from the screens. The access key is a message number less than 100,000 for the standard texts, which are only ones concerned with the vocabulary personalization function.
  • Chapter (field CHP)

When the text to be translated comes from the messages table APLSTD, the corresponding chapter number is specified here.

  • Number (field NUM)

This field is used to enter the number corresponding to the text to be translated. It should be noted that a text search can be carried out when a message or text containing a given chain of characters is searched. In this case, the right click Message search or Text search makes it possible to enter the chain to be searched for; but the selection window only allows the entry of a message or a text, which means it is necessary to use this facility carefully if it is used on a group of texts. Then moving to the line by right click, described in the function documentation.

  • Standard text (field STD)

This field is used to display the standard text as it exists in the dictionary shipped with the software.

  • Text (field TXT)

Entered here is the text destined to replace the standard text in the screens for the folder.



Functions accessed by right click on the grid

Additional text

This button makes it possible to load into the grid all the texts containing a given chain of characters. Once these texts are loaded, it is possible to enter the translation in the Text column.




Specific Buttons

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.


This button makes it possible to transfer the contents of the complete table to another folder.

Error messages

The only error messages are the generic ones.

Tables used

SEEREFERTTO Refer to documentation Implementation