ORE contains one record per (relevant) status modification of “order” (ORD).
BEGDATTIM contains the date and time, when the ORD was picked up by transaction TRN.
ENDDATTIM contains the date and time when the transaction was finished (i.e. save, release,…).
| Name | Description | Data Type | Len | Dec. | View lines | View type | Inst. | Visible | Codetable |
|---|---|---|---|---|---|---|---|---|---|
| ORDINR | INR of Parent ORD | Text | 8 | 1 | Edit | Yes | Public | ||
| SSNINR | INR of SSN where Event was Written | Text | 8 | 1 | Edit | Yes | Public | ||
| BEGDATTIM | Start of Processing | Datetime | 15 | 0 | Unknown | Yes | Public | ||
| ENDDATTIM | End of Processing | Datetime | 15 | 0 | Unknown | Yes | Public | ||
| PRCDUR | Processing Duration (in Seconds) | Numeric | 10 | 2 | Edit | Yes | Public | ||
| WAIDUR | Wait Time (in Seconds) | Numeric | 10 | 2 | Edit | Yes | Public | ||
| USR | User ID | Text | 8 | 1 | Edit | Yes | Public | ||
| TYP | Type of Event | Text | 3 | 1 | Edit | Yes | Public | <fixed-length> | |
| FRM | Transaction | Text | 8 | 1 | Edit | Yes | Public | ||
| OBJTYP | Object Type of Additional Object (Optional) | Text | 6 | 1 | Edit | Yes | Public | ||
| OBJINR | Object INR of Additional Object (Optional) | Text | 8 | 1 | Edit | Yes | Public | ||
| ETYEXTKEY | Entity owning Order | Text | 8 | 1 | Edit | Yes | Public |
| Name | Fields | Properties |
|---|---|---|
| ORE_ETYEXTKEY | ETYEXTKEY | |
| ORE_ORD | ORDINR |
/
ORDINR
Internal Unique ID of order to which this ORE record belongs.
Internal unique ID of the order to which this ORE record belongs.
INR of session in which this ORE was written. Allows to identify server and client machine used.
Unique ID of the session in which this ORE was written. Allows server and client machine used to be identified .
The date and time when the transaction FRM picked up the order.
The date and time when the FRM transaction (the name of the transaction handling the order) picked up the order.
The date and time when the transaction updated the order to the new state.
The date and time when the transaction updated the order.
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.
The number of seconds the transaction took to process the order (allowing performance statistics). This is the difference between the beginning and end timestamps.
Total time (in seconds) the status level for this entry was 'W'aiting
Total time (in seconds) the status level for this entry was 'W'aiting
The user ID of the user who performed the transaction.
The ID of the user who performed the transaction.
Embedded codetable of ORD\STA is used for this field, as status of ORD is set by ORE\TYP of the last ORE record.
REL is created when the last required signature is set.
SIG is created when a signature is applied but signatures are not yet sufficient for release.
The embedded ORDSTA codetable is used for this field, as status of ORD is set by ORETYP of the last ORE record.
REL is created when the last required signature is set.
SIG is created when a signature is applied but signatures are not yet sufficient for release.
Name of the transaction that handled the order.
Name of the transaction that handled the order.
SPT or TRN or SMH record handled.
Referenced object can become invalid/deleted at any time.
SPT or TRN or SMH record handled.
Referenced object can become invalid/deleted at any time.
(Can become invalid at any time).
(Can become invalid at any time).
This table is defined on entity level with separate entries for each entity. This field holds the EXTKEY 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 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.