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.

Date and time when this transaction was stored in the system.

Frame Used to Create the Transaction

User who created the contract of the selected transaction

Full name of the transaction selected

This field contains the reference number of the Transaction Control Record.

Type of contract the TRN entry refers to. This is the table the contract is stored in.

Unique ID of the object within the table, defined in the Object Type field.

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

This field holds the ID of the session creating a transaction.

This field holds the next counter to be used should there be multiple SMHs per transaction.

User group responsible for picking up the entry.

User responsible for picking up the entry.

Date and time when this transaction was completed.

Flag to indicate whether the contents of an infotext should be displayed when using the contract. If content is blank the automatic display is switched off.

This field is used to store any relevant information about this object.This information is displayed to the user during daily processing, if the display info flag is activated.

The RELFLG describes the signature status of the transaction.

Entered ('E'): Temporary status of transaction during creation of transaction. Transaction is incomplete and cannot be used in this status. Status remains 'entered' only if saving of a transaction fails for technical reasons.

Waiting ('W'): Waiting for release, i.e. not all requested signatures are yet applied.

Released ('R'): The count of requested signatures and applied? signatures are identical. This status is set by either the business transaction (if autosigned or no signature required) or by releasing the transaction when the last missing signature is applied.

Final ('F'): The transaction was released, has passed the workflow and? can no longer be rolled back.

Correct ('C'): The transaction is sent to correction.

Rejected ('N'): The transaction is deleted.

Picked Up ('P'): this status is set when the pending transaction is picked up and the new transaction saved or paused.

External ('X'): The transaction waits for external confirmation.

Closed ('M'): This status is exlusively set by the housekeeping transaction which cleans up historic data.

Only if the External Confirmation Flag field contains a 'C', will the transaction have a permanent effect on the relevant contract. Otherwise the transaction was either rolled back ('D') or its final status is not yet determined (' ').

Only if this flag is set to 'C', will the service pass to other transactions that depend on this transaction.

Holds the date when the transaction was committed.

If the transaction was initially loaded from a corrected or deleted transaction, the ID of that transaction is stored here.

This shows the current status of the recalculation for the transaction. It is empty if no recalculation is needed (i.e. because transaction does not lead to a settlement).

1: waiting for current rates, SRVPDX cannot be executed now 2: SRVPDX created XRE-SPT, transaction is waiting for recalculation by SPTTSK/TRN 3: Recalculation successful E: Error occurred

The field shows the block of currencies handled by the transaction.

This field contains the currency for the amount to be released.

This field contains the maximum amount the user is allowed to release transactions.

Currency of Relevant Amount for Release in Original Currency

Relevant Amount for Release in Original Currency

Required Signatures This field is set upon transaction creation and holds a list of up to 10 signatures that are required to sign the transaction. Each character represends one required signature. If multisignature is activated for a transaction in ETP, the list of required signatures is determined based on the transactions relevant amount matching the signature matrix from SIH

Applied Signatures If a required signature has been applied, the same character as in RELREQ is inserted at the same position as in RELREQ. If RELREQ = RELRES the transaction is determined as being fully signed

e.g. If RELREQ = “ ABC” and RELRES = “A C” the signatures with level A and C have been applied and the signature with Level B has not yet been given.

Flag to determine if external confirmation is necessary or not

The originally passed textual description of the event. This Text concatenated with the filename of the Logfile will be stored in the Event.

This field holds the ID of the user this transaction was sent to for repair.

Empty if the transaction was not triggered by an ORD.

If the Execution Date has been set, the transaction will not be processed before this date.

If the execution date is set, the service recalculation won't be processed before this date.

This field shows whether a transaction was generated either automatically by a batch process, or interactively by the user.

This field holds the user ID of the user this transaction was sent for release to.

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.

Release of the transaction shall be excecuted in the designated group.

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.

Flag for closing the contract

1 = WFE EMB was created, waiting for MGRTSK sending XML file 2 = WFE EMB is done, waiting for Smaragd TCM reply from QA interface (received in MQITSK/SWITSK) A = Ack received from TCM N = Nack received from TCM