This is the table holding all application profile information about a user.
The intention is, that within a customized installation, additional profile information per user might be declared as additional fields on security level 6.
| Name | Description | Data Type | Len | Dec. | View lines | View type | Inst. | Visible | Codetable |
|---|---|---|---|---|---|---|---|---|---|
| INR | Internal Unique ID of User | Text | 8 | 1 | Edit | Yes | Public | ||
| EXTKEY | User ID | Text | 8 | 1 | 30 | Edit | Yes | Public | |
| NAM | User Name | Text | 40 | 1 | Edit | Yes | Public | ||
| LGIFLG | Login Disabled | Text | 1 | 1 | Edit | Yes | Public | Embedded | |
| SSNBEGDATTIM | Last Session / Login | Datetime | 15 | 0 | Unknown | Yes | Public | ||
| SSNINR | INR of Last Session | Text | 8 | 1 | Edit | Yes | Public | ||
| VER | Version Counter | Text | 4 | 1 | Edit | Yes | Public | ||
| PRI | Priority Flag to Mark Initial Record | Text | 1 | 1 | Edit | Yes | Public | Embedded | |
| DOCEDTFLG | Document Editor | Text | 1 | 1 | Edit | Yes | Public | ||
| ETY | Default/Initial ETY of User | Text | 8 | 1 | Edit | Yes | Public | ||
| USG | Workgroup of User | Text | 6 | 1 | Edit | Yes | Public | USGTXT | |
| LSTDIADAT | Last Display of Diary | Date | 12 | 0 | Date | Yes | Public | ||
| RELCUR | Release Currency | Text | 3 | 1 | Edit | Yes | Public | CURTXT | |
| RELAMT | Release amount | Numeric | 18 | 3 | Edit | Yes | Public | ||
| RELAMT2ND | 2nd Release Amount | Numeric | 18 | 3 | Edit | Yes | Public | ||
| RELGRP | Release Group | Text | 1 | 1 | Edit | Yes | Public | SIGTYP | |
| SPQFLG | Remote Client Printing activated, if not empty | Text | 3 | 1 | Edit | Yes | Public | Embedded | |
| APLPRF | Application Profile | Text | 16 | 1 | Edit | Yes | Public | ||
| SASFLG | SaaS User | Text | 1 | 1 | Edit | Yes | Public | ||
| TEL | Phone | Text | 30 | 1 | Edit | Yes | Public | ||
| FAX | Fax Number of User | Text | 30 | 1 | Edit | Yes | Public | ||
| EML | Email Address of User | Text | 140 | 1 | 80 | Edit | Yes | Public | |
| QUEPOW | Available Time | Numeric | 6 | 2 | Edit | Yes | Public | ||
| LETOENR | Organizational Unit for Letters | Text | 30 | 1 | Edit | Yes | Public | ||
| COLOR | Color for charts | Text | 6 | 1 | Edit | Yes | Public | CHSCOL | |
| 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 | ||
| WRKPLNHRS | Part of working time to be planned [h] | Numeric | 5 | 2 | Edit | Yes | Public | ||
| EML2 | Group e-mail Address of User | Text | 140 | 1 | 80 | Edit | Yes | Public | |
| ETYEXTKEY | Entity of profiledata of User | Text | 8 | 1 | Edit | Yes | Public | ||
| GETFLDNRM | Field holding the normalized search fields | Text | 60 | 1 | Edit | Yes | Public | ||
| OENR | Organisationseinheit | Text | 4 | 1 | Edit | Yes | Public | ||
| ETAEXTKEY | Entity Address | Text | 8 | 1 | Edit | Yes | Public | ||
| PRF | Profile | Text | 40 | 1 | Edit | Yes | Public | ||
| ADMFLG | Security Administrator | Text | 1 | 1 | Edit | Yes | Public | ||
| DSGFLG | Designer | Text | 1 | 1 | Edit | Yes | Public | ||
| SECLEV | Security Level | Numeric | 2 | 0 | Edit | Yes | Public | ||
| SECSTA | Security Status | Text | 1 | 1 | Edit | Yes | Public | Embedded |
| Name | Fields | Properties |
|---|---|---|
| USR_ETYEXTKEY | ETYEXTKEY | |
| USR_EXTKEY | EXTKEY | |
| USR_GETFLDNRM | GETFLDNRM | |
| USR_INR | INR | Unique |
| USR_USG | USG |
/
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 USR. The field INR is used to maintain the standard technical links from other tables into this table. Additionally for performance reasons the EXTKEY of a user is used in many application tables as a link, as only the user ID is often needed and in this case no resolution of a link is necessary to get this information.
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.
This is the technical short name used to identify a user within an installation. This user ID might be different to the user ID used to login to the application server. This depends on the used login mechanism and the environment.
This is the technical short name used to identify a user within an installation. This user ID might be different to the user ID used to login to the application server, depending on the login mechanism used and the environment.
This is the long name of a user. This name is used to be shown in user selections and in any place, where a detailed name of a user is required.
This is the long name of a user. This name is used throughout the application where a detailed name of a user is required to make a selection.
Setting this field to a “Y” disables the login. When using the default TradeDesign rights handling the master file, maintenance routines would automatically delete the TradeDesign rights entry of this user, making any logins of this user impossible.
The LGIFLG is a global data element and will automatically update all other occurances in other entities where LGIFLG is “Y” or “ ” if it is set to “Y” or “ ”. A value of “D” is not automatically updated.
Setting this field to a non-empty value disables the login. If default TradeDesign rights are used to handlethe master file, maintenance routines would automatically delete the TradeDesign rights entry for this user, making it impossible for the user to login.
| Code | Text |
|---|---|
| Login Profile enabled | |
| Y | No Login Profile |
| D | Entity Profile canceled |
Timestamp of the last login to the system.
Timestamp of the last login to the system.
INR of the session used for the last login.
Unique ID of the session used for the last login.
This field holds the version counter to keep track of the version history of a USR entry. 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.
The PRI flag is used to optionally mark the initial record in a multi-entity environment, where the USR table is not declared global. If multiple entries are existing for a single user ID, the entry with a non-space value in the PRI field is used for the initial login.
The Priority flag can be used to identify the initial record in a multi-entity environment, where the User table has not been declared global. If multiple entries are available for a single user ID, the entry with a non-empty value in the Priority field is used for the initial login.
| Code | Text |
|---|---|
| keep last used entity | |
| X | This is the initial entity |
This field defines the initial entity of a user after login when this profile has been selected during login. This field is not intended to be used as search field for the entity of a user in a multi-entity environment. The search entity is generic located in the field ETYEXTKEY of each table and thus USR\ETYEXTKEY should be used as search reference. In a multi-entity environment the field USR\ETY has to hold the identical content as USR\ETYEXTKEY (if the latter field is available).
This field defines the initial entity of a user after login.
User group the user is associated to.
User group the user is associated to.
The date of the last display of the personal diary entries. This date is used to remind the users every day until they take a look into the diary.
The date the personal diary entries were last displayed. This date is used to remind users to take a look into the diary.
This field holds the currency of the base release amount. Together with the amount taken from RELAMT this field defines the base release amount used by the release functions.
This field contains the currency for the amount to be released.
This field holds the amount of the base release amount. Together with the currency taken from RELCUR this field defines the base release amount used by the release functions. Usually this amount is used as maximum amount for the release of transactions.
This field contains the maximum amount the user is allowed to release transactions (see also the Release field)
This field holds a second release amount. Together with the currency taken from RELCUR this field supplies a second amount to be used by the release functions. Usually this amount is used as amount tier to allow the release of own transactions.
This field contains the maxium amount users are allowed to release for their own transactions. (See also field “Release”)
This field defines the release level or release group this user is associated to. This field controls the release functions.
This field contains the release rights. “Officer” = allowed to release, “Clerk” = not authorized to release
This field controls whether this user is allowed to print request created for local printing (remote client printing).
This field controls whether this user is allowed to print request created for local printing (remote client printing).
| Code | Text |
|---|---|
| Not Activated | |
| USR | Only Own Printouts |
| USF | Printouts For Selected Other Users |
This field contains the telephone number of the user which then can be used during creation of correspondence.
This field contains the user's telephone number which can then be used during correspondence.
This field holds the fax number of the user, which can be used when creating correspondence.
This field holds the fax number of the user used for correspondence.
This field contains the Email address of the user which then can be used during creation of correspondence.
This field contains the Email address of the user used for correspondence.
Capacity for Queue Processing. This field describes the availability of this user for queue processing. This can e.g. be daily time this user is available.
The this value and its relation to the total for all users resp. all users of a user group is used for estimation of static and dynamic capacity for automatic load balancing in transaction QUETSK.
This field describes the user's availability for queue processing. This can be the user's daytime availability, for example.
This value and its relation to the total for all users or all users of a user group is used to estimate static and dynamic capacities for automatic load balancing.
This field holds the name of organizational unit for output in header of letters.
This field contains the name of the organisational unit (department) of the user and is printed in the header of the outgoing correspondence.
Color to be used if user 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 defines the entity of the profiledata of the user in a multi-entity environment, where users are associated to different entities. Thus the same userid is defined in different entities with different profiles (i.e. transaction execution profile, release rights, language).
If a user is defined in more than one entity the different entries hold the same userid in the field EXTKEY and the respective entity in the field ETYEXTKEY.
If the field ETYEXTKEY exists for USR, its content must always be identical to USR\ETY and exactly one entry of the user has to be marked with a contents in the field PRI to describe the initially used entity + userprofile after login.
This field holds the external key of the owning entity to identify the logical owner of this entry.
This field is filled automatically during insert and is used as filter when accessing the database. Without special implementation only entries of the currently active entity are visible to the user.
This field holds the organizational unit to which the user is associated.
This field holds the organizational unit to which the user is associated.
This optional field defines the address within the table ETA this user is associated to. This address might be used in messages as senders address.
This field contains the entity address as defined in 'Displaying an Entity Address'.
Application Profile for - Load Balancing
The field application profile defines, which type of queue entries are assigned to a user. If no application profile is defined, any types of queue entries are assigned to a user.
In order to exclude certain queue types, it is possible to define an application profile with the ending *.tda in the ini-folder. In section [Balance CLA] for each value of the embedded codetable QUECLA (e.g. INC or RIM or REL) the assignment of entries can be excluded.
Example:
clerk.tda, [Balance CLA] REL=X excludes that Release queue entries (type REL) are assigned to users that have no authorization rights.
In the MyModelbank, these application profiles are available: Clerk.tda: Any type of queue entries, except release Officer.tda: Any type of queue entries Releaser.tda: Only queue entries of type = Release (REL) Admin/Manager.tda: No queue entries are assigned
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 specifies the part of the working time which should be planned with SLA.
This field specifies the part of the working time which should be planned with SLA.
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.
Field used in outgoing compliance file (MGRTSK, service SRVEMB)
This field contains the Group Email address the user is associated with
User Profile
User Profile
If checked the user has system administration rights that include user administration right.
If checked the user has system administration rights that include user administration right.
Indicates, if a user is allowed to switch to the designer mode of this application. This enables the user to define helptexts, rules and XML templates etc.
Indicates, if a user is allowed to switch to the designer mode of this application. This enables the user to define helptexts, rules and XML templates etc.
For developer only.
In case TradeDesign is configured to run in restricted mode this field defines the minimum security level on which this user can change sources.
For developer only.
In case TradeDesign is configured to run in restricted mode this field defines the minimum security level on which this user can change sources.
This field contains the user status and indicates whether the user status is normal, expired, blocked, reset or a new password was defined.
This field contains the user status and indicates whether the user status is normal, expired, blocked, reset or a new password was defined.
| Code | Text |
|---|---|
| 0 | Normal |
| 1 | Expired |
| 2 | Blocked |
| 4 | Reset |
| 5 | New Password |
If this flag is set the relevant user is allowed to edit XML templates via document editor. Only if in addition also the designer flag is set one can also edit document rules.
If this flag is set the relevant user is allowed to edit XML templates via document editor.
Only if in addition also the designer flag is set, document rules can be edited.
Indicates if the current user is a user of a TFaaS solution of this application. On TFaaS systems all application users have to be defined as TFaaS user, except those of the vendor.
Indicates if the current user is a user of a TFaaS solution of this application. On TFaaS systems all application users have to be defined as TFaaS user, except those of the vendor.