| Name | Helptext Description | Data Type | Len | Codetable |
|---|---|---|---|---|
| INR | Internal Unique ID | Text | 8 | |
| NAM | Name | Text | 40 | |
| OBJTYP | Object Type | Text | 6 | |
| OBJINR | Object INR | Text | 8 | |
| SMHINR | INR of (First) Associated Incoming Message (Optional) | Text | 8 | |
| PTAINR | INR of Ordering Party Address (Optional) | Text | 8 | |
| EXTKEY | External Key | Text | 32 | |
| INFDSP | Infoflag | Text | 1 | INFDSP |
| INFTXT | Infotext | Block | 65 | |
| STA | Status | Text | 3 | Embedded |
| STADATTIM | Timestamp of Last Status Update | Datetime | 15 | |
| OWNUSG | Responsible Group (Optional) | Text | 6 | <fixed-length> |
| OWNUSR | Responsible User | Text | 8 | <fixed-length> |
| INIDATTIM | Timestamp of Creation | Datetime | 15 | |
| TARDATTIM | Target for Completion | Datetime | 15 | |
| CPLDATTIM | Timestamp of Completion | Datetime | 15 | |
| TOTDUR | Duration (in Seconds) | Numeric | 10 | |
| SLACLA | Predefined Priority Class | Text | 6 | |
| SLACHA | Channel | Text | 3 | CORTYP |
| CREOBJTYP | Object Type of Creating Object | Text | 6 | |
| CREOBJINR | INR of Creating Object | Text | 8 | |
| VER | Version | Text | 4 | |
| ETYEXTKEY | Entity | Text | 8 | |
| CHKFLG | Order OK | Text | 1 | YESNO |
| GETFLDNRM | Field holding the normalized search fields. | Text | 60 |
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.
External readable name of the order.
The field identifies the object type of associated item,
i.e. the type of object the order entry refers to. This is the table the object is stored in.
Internal unique ID of object.
Unique ID of (first) associated Incoming Message (optional).
An optional field supplying the unique ID of the Ordering Party Address.
Field to identify a message.
Flag to indicate whether the contents of an infotext should be displayed when using the contract. No content switches the automatic display 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 has been activated.
Status of order.
| Code | Text |
|---|---|
| CRE | Order created |
| TRN | TRN created |
| COR | TRN sent to correction |
| DEL | TRN deleted |
| FIN | Order closed |
| CAN | Order canceled |
| REL | TRN released |
| DES | SPT deleted |
| BRK | TRN interrupted |
| INC | Message received |
| SPT | SPT released |
| SIG | Signature |
| JOI | Order joined |
Date and time when the status relating to this order was last changed.
User group responsible for picking up the entry.
This field holds the User ID of the person responsible for picking up the entry.
Date and time when this order was stored in the system.
Target time (i.e. date + time) by which the service is to be completed.
Date and time when this order was completed.
The number of seconds the transaction took to process the order (allowing performance statistics). This is the difference between the beginning and end timestamps.
Predefined Priority Class (as defined in the service level agreement with the ordering customer).
Channel (CORTYP) by which this order was received
Optional field to identify the object type of the creating object. For SPT's created via autoregistration (STA='RIM') this object type is usual 'TRN', thus the business transaction which created the autoregistered entry is identified by CREOBJTYP and CREOBJINR.
Optional field to identify the concrete object which initiated the creation of this SPT. In SPT's created via autoregistration (STA='RIM') this is usually the INR of the creating business transaction (TRN\INR).
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.
Sample of additional project-specific fields.
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.
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.