This entry holds the profile information about the currently used
entity. Entities are logical units within the application which might
have separate dynamic data sets, when using the multi-entity
module.
In installations without multi-entity, the data is shared between all
entities and the entities just provide central information about the
using bank. In this case usually only one entry is stored in the
database.
| Name | Description | Data Type | Len | Dec. | View lines | View type | Inst. | Visible | Codetable |
|---|---|---|---|---|---|---|---|---|---|
| INR | Internal Unique ID of Entity | Text | 8 | 1 | Edit | Yes | Public | ||
| EXTKEY | Entity ID | Text | 8 | 1 | Edit | Yes | Public | ||
| NAM | Name of the Entity | Text | 40 | 1 | Edit | Yes | Public | ||
| ETG | Group to which this Entity Belongs | Text | 8 | 1 | Edit | Yes | Public | ||
| NGULOG | Logo used in top area on the right | Text | 38 | 1 | Edit | Yes | Public | ||
| NGLLOG | Logo used in lower area on the right | Text | 38 | 1 | Edit | Yes | Public | ||
| OFFLOG | Logo File Used in Office on the Wall | Text | 38 | 1 | Edit | Yes | Public | ||
| LETLOG | Logo File Used in Letterhead | Text | 38 | 1 | Edit | Yes | Public | ||
| USERPIC | Picture Used in Office in Picture Frame | Text | 38 | 1 | Edit | Yes | Public | ||
| DEFICO | Default Icon for Entity | Text | 38 | 1 | Edit | Yes | Public | ||
| VER | Version Counter | Text | 4 | 1 | Edit | Yes | Public | ||
| OWNPTAINR | INR of the Own PTA Address | Text | 8 | 1 | Edit | Yes | Public | ||
| DEFROUUSG | Default User Group for Routing | Text | 6 | 1 | Edit | Yes | Public | ||
| ETAEXTKEY | Relevant Entity Address | Text | 8 | 1 | Edit | Yes | Public | <fixed-length> | |
| OWNBIC | BIC of Entity | Text | 12 | 1 | Edit | Yes | Public | ||
| OWNTID | TID of Entity | Text | 23 | 1 | Edit | Yes | Public | ||
| ADMUSR | Application Administrator (Optional) | Text | 8 | 1 | Edit | Yes | Public | ||
| TIMZON | Timezone | Text | 6 | 1 | Edit | Yes | Public | TIMZON | |
| UIL | Default Language Code | Text | 2 | 1 | Edit | Yes | Public | UILTXT | |
| XSIPST | Postfix for entityspecific XSI-Files | Text | 8 | 1 | Edit | Yes | Public | ||
| CAL | Default Calendar of Entity | Text | 3 | 1 | Edit | Yes | Public | ||
| COLOR | Color for charts | Text | 16 | 1 | Edit | Yes | Public | ||
| BEGTIM1 | Begin of working 1st day | Numeric | 4 | 2 | Edit | Yes | Public | ||
| BEGTIM2 | Begin of working 2nd day | Numeric | 4 | 2 | Edit | Yes | Public | ||
| BEGTIM3 | Begin of working 3rd day | Numeric | 4 | 2 | Edit | Yes | Public | ||
| BEGTIM4 | Begin of working 4th day | Numeric | 4 | 2 | Edit | Yes | Public | ||
| BEGTIM5 | Begin of working 5th day | Numeric | 4 | 2 | Edit | Yes | Public | ||
| BEGTIM6 | Begin of working 6th day | Numeric | 4 | 2 | Edit | Yes | Public | ||
| BEGTIM7 | Begin of working 7th day | Numeric | 4 | 2 | Edit | Yes | Public | ||
| ENDTIM1 | End of working 1st day | Numeric | 4 | 2 | Edit | Yes | Public | ||
| ENDTIM2 | End of working 2nd day | Numeric | 4 | 2 | Edit | Yes | Public | ||
| ENDTIM3 | End of working 3rd day | Numeric | 4 | 2 | Edit | Yes | Public | ||
| ENDTIM4 | End of working 4th day | Numeric | 4 | 2 | Edit | Yes | Public | ||
| ENDTIM5 | End of working 5th day | Numeric | 4 | 2 | Edit | Yes | Public | ||
| ENDTIM6 | End of working 6th day | Numeric | 4 | 2 | Edit | Yes | Public | ||
| ENDTIM7 | End of working 7th day | Numeric | 4 | 2 | Edit | Yes | Public | ||
| WRKHRS1 | Working hours 1st day | Numeric | 4 | 2 | Edit | Yes | Public | ||
| WRKHRS2 | Working hours 2nd day | Numeric | 4 | 2 | Edit | Yes | Public | ||
| WRKHRS3 | Working hours 3rd day | Numeric | 4 | 2 | Edit | Yes | Public | ||
| WRKHRS4 | Working hours 4th day | Numeric | 4 | 2 | Edit | Yes | Public | ||
| WRKHRS5 | Working hours 5th day | Numeric | 4 | 2 | Edit | Yes | Public | ||
| WRKHRS6 | Working hours 6th day | Numeric | 4 | 2 | Edit | Yes | Public | ||
| WRKHRS7 | Working hours 7th day | Numeric | 4 | 2 | Edit | Yes | Public | ||
| ANTETY | allNETT/RIVO Entity | Text | 3 | 1 | Edit | Yes | Public | ||
| ANTDPT | allNETT/RIVO Department | Text | 12 | 1 | Edit | Yes | Public | ||
| HUBFLG | If checked it's a HUB (central processing center) | Text | 1 | 1 | Edit | Yes | Public | ||
| ALADIID | ALADI ID | Text | 4 | 1 | Edit | Yes | Public | ||
| CLEARID | Clearing Number | Text | 4 | 1 | Edit | Yes | Public | ||
| GETFLDNRM | Field holding the normalized search fields | Text | 60 | 1 | Edit | Yes | Public | ||
| PNTETY | Hub Entity/ Parent Entity | Text | 8 | 1 | Edit | Yes | Public |
| Name | Fields | Properties |
|---|---|---|
| ETY_ETG | ETG | |
| ETY_EXTKEY | EXTKEY | Unique |
| ETY_GETFLDNRM | GETFLDNRM | |
| ETY_INR | INR | Unique |
/
INR
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 ETY. The field INR is used to maintain links from other tables into this table. In the Multi-Entity module the EXTKEY of an entity (instead of the INR) is used in the field ETYEXTKEY in many application tables as selector to enable the reduction of the visibility of data to a certain entity.
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 content of this field is used in all entity-specific tables to associate these entries to the entity by storing the content in the column ETYEXTKEY.
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 name of the entity is a descriptive name, which is intended to be used to identify the entity internally .
This field indicates descriptive name of the entity.
Externally used descriptive key to identify the entity group the current entity belongs to. The content of this field is used in all entity group-specific tables to associate these entries to the entity by storing the content in the column ETGEXTKEY.
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.
Logo file to be used to hold the logo to be displayed as upper part of the clock on the wall. The file name is specified relatively to the frame partition and might hold the special tag %uil% to represent the current user interface language to specify a language-dependent logo file.
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.
Logo file to be used to hold the logo to be shown as part of the letterhead in correspondence (in MyModelbank correspondence used in sub XMLPrintHeader in TRNDOC). The file name is specified relatively to the frame partition and might hold the special tag %uil% to represent the current user interface language to specify 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 picture that can optionally 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 interface language to specify a language dependent picture 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 relatively to the frame partition.
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 to keep track of the version history of an entity. The individual versions are controlled by entries in the SLG table.
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.
INR of the own address PTA used to logically access account information associated to the entity.
Identification number of the own PTA address used to logically access account information associated to the entity.
This default user group is used as default value for the routing of incoming messages within this entity, if no other group can be determined.
This default user group is used to route incoming messages within this entity, if no other group can be determined.
Specification of the relevant entity address (or building) where the entity is located in. This association is normally used to defaultwise determine the addresses used in the letterhead, if no other building is specified.
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 instead of the normal length 11, because this BIC must include the Logical Terminal Code at the 9'th position. The terminal code identifies a specific terminal connection within a destination. It consists of one alphanumeric character (the digits “0” and “1” are not permitted).
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.
This TID is used when sending TradeConnect messages from different entities.
One user might be defined as application administrator for each entity. This user gets notify messages which are necessary to administrate the application. The default value, which will be used if no value is specified with an entity, is defined in DNGPARA.ini in section [Defaults] in entry Ety-ADMUSR.
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.
Time zone for this entity. User will see all timestamps converted to this timezone. In database all timestamps are stored in system time.
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.
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 entity specific XSI-files use the postfix to extend the standard filename (eg. “A4xxx.XSI”). An empty field contents or a not existing XSI-file will use of the default XSI-name as specified for the document (eg. “A4.XSI”).
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).
Default calendar for the entity. This calendar can be maintained in DBxETY and is used instead of the default system calendar as defined in tdpara.ini.
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.
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.
Own clearing ID used in payment messages with the SIC clearing system. This field is a customer specific field.
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 time the work has to beginn on Sunday. The format is hh.mm.
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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 Friday. The format is hh.mm.
This field contains the time that should be worked on Saturday. The format is hh.mm.
This field contains the time that should be worked on Saturday. The format is hh.mm.
This field contains the allNETT Entity that is linked to the Doka Entity, on Incoming and Outgoing allNETT messages.
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
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.
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 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.
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.
This field specifies if an entity is a Hub, ie considered a central processing center.
Hub/ Parent entity to design multi level branch structures.
Hub/ Parent entity to design multi level branch structures.
The bank using DOKA can enter a 4 digit ALADI identifier code (ALADIID) per Entity.
It is used for issuing the ALADI Reimbursement code on customer request when an LC is issued and when an Export Collection is opened.
The bank's ALADI Identifier code for the ALADI Inter-bank settlement system.