In the MultiEntity module, the EXTKEY of an entity (instead of the INR) in the ETYEXTKEY field is used as a selector in many tables, to facilitate a reduction of the visibility of data of a certain entity. Unique internal ID of a record within the table. The INR is a text field, which is created by retrieving the next valid entry from the counter of this table. The field INR is used to enable links from other tables to this table.

For contractdata the INR also links the two tables xxD and xxT as associated entries hold the same INR.

Externally used descriptive key to identify an entity. This key has to be unique. The field is used in all tables specific to the entity to associate these entries to the entity.

This field indicates descriptive name of the entity.

Externally used descriptive key to identify the group the current entity belongs to. The content of this field is used in all tables specific to the entity group to associate these entries to the entity.

The field indicates the logo file for the image displayed above clock. The file name is specified relatively to the frame partition and might hold the special tag %uil% to represent the current user language when it comes to specifying a language-dependent logo file.

The field identifies the file to be used to show the logo in the letterhead in correspondence. The file name is specified relative to the frame partition and might hold the special tag %uil% to represent the current user language when it comes to specifying a language-dependent logo file.

File name of the image that can be displayed in the picture frame on the filing cabinet. The file name is specified relatively to the frame partition and might hold the special tag %uil% to represent the current user language when it comes to specifying a language-dependent picture file.

If set, this icon is automatically used instead of the default icon. The icon file used is specified relative to the frame partition.

This field holds the version counter used to keep track of the history of an entry of this table. The individual versions are managed by entries in the SLG table.

Identification number of the own PTA address used to logically access account information associated to the entity.

This default user group is used to route incoming messages within this entity, if no other group can be determined.

The field contains details of the relevant address (or building) for the entity. This link is normally used to default the address used in the letterhead, if no other building is specified.

This BIC is used when sending SWIFT messages from different entities. The length of this BIC is 12 digits instead of the normal 11, because this BIC must include the Logical Terminal Code as the 9th digit. The terminal code identifies a specific terminal connection within a destination. It consists of one alphanumeric character (“0” and “1” are not permitted).

This TID is used when sending TradeConnect messages from different entities.

One user can be defined as application administrator for each entity. This user receives Notify messages necessary to administer the application. The default value which is used, if no default is set in the entity, is defined in DNGPARA.INI in section [Defaults], entry ETY-ADMUSR.

The time zone for this entity. All time stamps relevant for the user are converted to this time zone in displays. In the database, time stamps are stored in system time. The time zone is only used, if the Time Zone system is also used.

The language code defines the language to be used of language dependent output where the language is not defined by user or correspondent/document. Used e.g. for language of 'File Copy' Header.

To allow a different XSI-file for a different ETY create a XSI-file eg. “A4xxx.XSI”, where xxx is written in this field for the respective entity. An empty field or a not available XSI-file will result in the use of the default value of the document (eg. A4.XSI).

This optional field specifies an entity-specific calender to be used for date calculations based on working days such as in 'date' fields, or on internal functions where no calendar is specified.

Color to be used if entity is represented in charts.

Typically specified in form rgb(rrr,ggg,bbb) as this allows automatic modification of color to create color gradients. This field controls the color in which the entries assigned to the user are displayed in the Dashboard charts.

This field contains the time the work has to beginn on Sunday. The format is hh.mm.

This field contains the time the work has to beginn on Monday. The format is hh.mm.

This field contains the time the work has to beginn on Tuesday. The format is hh.mm.

This field contains the time the work has to beginn on Wednesday. The format is hh.mm.

This field contains the time the work has to beginn on Thursday. The format is hh.mm.

This field contains the time the work has to beginn on Friday. The format is hh.mm.

This field contains the time the work has to beginn on Saturday. The format is hh.mm.

This field contains the time the work should end on Sunday. The format is hh.mm.

This field contains the time the work should end on Monday. The format is hh.mm.

This field contains the time the work should end on Tuesday. The format is hh.mm.

This field contains the time the work should end on Wednesday. The format is hh.mm.

This field contains the time the work should end on Thursday. The format is hh.mm.

This field contains the time the work should end on Friday. The format is hh.mm.

This field contains the time the work should end on Saturday. The format is hh.mm.

This field contains the time that should be worked on Sunday. The format is hh.mm.

This field contains the time that should be worked on Monday. The format is hh.mm.

This field contains the time that should be worked on Tuesday. The format is hh.mm.

This field contains the time that should be worked on Wednesday. The format is hh.mm.

This field contains the time that should be worked on Thursday. The format is hh.mm.

This field contains the time that should be worked on Friday. The format is hh.mm.

This field contains the time that should be worked on Saturday. The format is hh.mm.

The bank's own clearing ID used in payment messages using the SIC clearing system. This is a field specific for the customer.

This field contains the allNETT Entity that is linked to the DOKA Entity, on Incoming and Outgoing allNETT messages.

This field contains the allNETT Department that is linked to the Doka Entity, on Incoming and Outgoing allNETT messages. Implementation examples: 1. Implement as customer branch code 2. Implement as DOKA entity id 3. Implement as DOKA entity BIC code

Field holding the concatenated and normalized sum of all search fields used by quick search. This is one of the fields set in a SdbSetNRMFields method defined in the table definition module.

In case the standard logo should not be used in top area on the right any alternate logo file can be defined here.

In case the standard logo should not be used in lower area on the right any alternate logo file can be defined here.

This field specifies if an entity is a Hub, ie considered a central processing center.

Hub/ Parent entity to design multi level branch structures.

The bank's ALADI Identifier code for the ALADI Inter-bank settlement system.