QUE - Interactive Queue

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.

Contains the class of the queue entry. Class 'INC': If the first interactive action for an incoming order within the application is a business transaction, a pending transaction (status 'INC') is created together with an 'INC' queue entry.

Class 'ORD': If interactive preprocessing within the application is required prior to the first business transaction an 'ORD'queue entry can be created (as no pending transaction has yet bee created).

Type of object this queue entry refers to. Typical values are:

'SPT': For every pending transaction that must be handled interactively a respective queue entry is created.

'TRN': For every signature that has to be applied interactively to a transaction a queue record is created. SUBID contains the identification of the signature.

'DIA': For every diary entry that requires manual interaction a queue entry is created automatically by QUETSK manager when it becomes due.

'ORD': If prior to the first business transaction interactive preprocessing within the application is required (like with program DBMORD) a queue entry with 'ORD' can be created (as no pending transaction is created yet).

The unique ID of the object within the table, as defined in the object table.

This field is used to uniquely identify multiple entries. It is implemented as a counter with a maximum value of 99. This is needed to handle multiple signatures for one transaction.

This field identifies the pending entry in a way that is readable to the user.

This field identifies the reference key of the object identified by the object type and ID number.

For incoming messages: message type and the BIC of the sender.

If this field is not empty, the record is not be picked up/displayed for further processing.

Unique ID of the session which last updated the Hold Flag.

Time when the Hold Flag was set.

This flag indicates how the user group/user (USG/USR) for this item was assigned:

'C'reation: USG/USR were assigned when creating a transaction (load balancing was included at this moment)

'A'utomatic: USG/USR was assigned via the 'Load Balance Manager' transaction

'M'anual: USG/USR were assigned manually by operator (BALSRTKEY, = sort key within BALCLA, is automatically determined by transaction 'Load Balance Manager' QUETSK)

'U'rgent: USG/USR and BALSRTKEY (sort key within BALCLA) were assigned manually by operator. USR/USG will not be changed automatically for such entries.

'F'ree: Entry was manually released to be assigned by transaction 'Load Balance Manager'

The table in which the parent contract is stored. This field is optional.

This field contains the internal unique ID of the contract.

If the Object Type field is set to 'SPT' (pending transaction) it contains a copy of field SPTFRM. This field identifies the transaction which should be used to process the 'SPT' entry.

If the Object Type field is set to 'TRN' (transaction) it contains a copy of field TRNINIFRM. This field identifies the transaction that created this transaction

If the Object Type field is is set to 'DIA' (diary) it contains a copy of field DIAFRM. This field holds the optional transaction ID, which should be started when handling the diary entry.

User group responsible for picking up the entry.

User responsible for picking up the entry.

Predefined priority class from the service level agreement.

The priority class is used for sorting the items in the display and for netting purposes.

This field contains the sort key within the priority class for balancing.

If a relevant amount for this message can be determined, the currency of the amount is stored here. Otherwise this field is left blank.

If a relevant amount for this message can be determined, the amount can be stored here. In this case the associated currency has to be stored in the Currency field.

Currency for field 'Relevant Amount (system currency)', always system currency.

Value of relevant amount in system currency.

Date and time by when handling of this queue entry should be started.

Conceptually this is the target termination time of this QUE entry minus expected processing time.

After this time the QUE entry becomes 'critical'=yellow.

This field might be empty if no target time is set.

This field is used to describe the queue entry in a way that is readable to the user.

This field is typically filled from the corresponding field in the triggering record.

Duration contains the time in seconds during which the transaction named in FRM worked on the order (allowing performance statistics). Duration is calculated as difference between the fields BEGDATTIM and ENDDATTIM.

Empty if TRN was not triggered by an ORD. Otherwise the INR of the ORD entry which triggered this transaction.

Latest point of time when this record is to be processed.

This field holds the external key of the owning entity group 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 group are visible to the user.

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 identifies the pending entry itself in a user readable way. It is usually made up of the EXTKEY/OWNREF/COD combined with the NAM field.