Text modules are predefined texts and formulations that can be retrieved by users, so that they do not have to enter recurring text over and over again.

In order that only the relevant and reasonable text modules are displayed for a particular field, the text modules have been grouped. Each text module group has a name (defined in codetable “TXMTXT - Text Module”).

For each group different text modules with a relevant name (short, technical module ID, max. 8 digits) and a description in plaintext (as textual short description for identifying the text modules) can be defined in the transaction “Maintaining Text Modules” (DBITXM).

The group name of the module group is assigned to each text field within the application for which text modules have to be available (details of this procedure can be found in the Developer Documentation under “TXMMOD - Assigning Text Modules”).

Clicking lists all the text modules for this module group from which the required text module can then be selected. The selected text modules are inserted at the end of the wording already present in the text field.

The 'Sel.' column determines the sequence of text modules, in which they are then entered in the text field.

Further information about IDs and identification numbers of text modules can be found under 'Info Text Module'.

Text modules may be directly retrieved via “*Text module ID” from the database and resolved in any given text fields. In the process, several text modules (*xxx) can be resolved at the same time.

Alternatively, the notation '**' contained in the text field also leads to the selection list of text modules. However, the text modules selected are inserted at the position of the notation '**', which is helpful particularly in the event of subsequent corrections or addenda.

Example

The textmodule 'Certificate of health' (LCRDOC.CERTHEAL), which can be found in group 'Documents L/C' (see also example under “Info Text Module” (INFTXM)) :

It is possible to call up previously defined texts directly in the text field by entering an asterisk (*) immediately before the text module ID used (i.e. for the above-mentioned example: '*LCRDOC.CERTHEAL'). By leaving the field in a transaction via the Tab key or by clicking the icon, the relevant text module will then be resolved in the text and (in this case) '+ certificate of health' will be displayed. If a '*Text module' cannot be clearly assigned, the selection list of text modules will be displayed. To ensure that all '*Text modules' are resolved prior to saving, this is controlled beforehand by means of an internal test.

If a manual entry by the user is necessary in one or several places in a pre-formulated text block, an asterisk '*' will be inserted in the relevant position as a wildcard. The asterisk acts as a stopper. If such a text module was retrieved, the cursor will jump to the first asterisk it contains so that the user can replace it by some other characters or numerals. The [tab] key allows the user to jump to the following asterisk. A transaction cannot be saved as long as there still are asterisks in one of the entry fields.

With Swift Release 2018/2020 the allowed characterset for several message tags was changed, so that asterix '*' became an allowed character. To save a text with an asterix in an entry field, the checkbox “Allow *” beside the respective entry field has to be checked.

It is possible to enter contract fields into the text area of a text module, so that the text automatically includes the relevant contract information.

In order to enter fields in text modules, the complete name of the relevant field is required. The following format is to be used, for example:

{<Main Group>\<Group>\<Field Name>}

An example for including the own reference number of the bank for a guarantee:

{GIDGRP\REC\OWNREF}

In the text module, the reference number of the contract is displayed at the location where the field is called.

It is possible to enter a description from a codetable into the text area of a text module, so that the description is displayed instead of the code.

Example for including the description from the embedded codetable of field GID.HNDDTYP in language “DE”:

{=gettbltext(gidgrp\rec\hndtyp,“GID:HNDTYP”,“DE”)}

For external codetables use the name of the codetable instead of the fieldname.