This table holds information about the release of masterfile maintenance transactions executed under four eyes principles.
Name | Description | Data Type | Len | Dec. | View lines | View type | Inst. | Visible | Codetable |
---|---|---|---|---|---|---|---|---|---|
INR | Internal Unique ID of Pending Release | Text | 8 | 1 | Edit | Yes | Public | ||
SPTINR | INR of the Associated SPT | Text | 8 | 1 | Edit | Yes | Public | ||
OBJTYP | Table Used to Store Object | Text | 6 | 1 | Edit | Yes | Public | ||
OBJINR | INR of Object | Text | 8 | 1 | Edit | Yes | Public | ||
CREDAT | Date of Creation | Date | 12 | 0 | Date | Yes | Public | ||
CRETIM | Time of Creation | Numeric | 6 | 4 | Edit | Yes | Public | ||
CREUSR | Creating User ID | Text | 8 | 1 | Edit | Yes | Public | ||
CRESSNINR | INR of Creating Session | Text | 8 | 1 | Edit | Yes | Public | ||
RELLEV | Release Level | Text | 1 | 1 | Edit | Yes | Public | ||
RELDAT | Date of Release | Date | 12 | 0 | Date | Yes | Public | ||
RELTIM | Time of Release | Numeric | 6 | 4 | Edit | Yes | Public | ||
RELUSR | Releasing User ID | Text | 8 | 1 | Edit | Yes | Public | ||
RELSSNINR | INR of Releasing Session | Text | 8 | 1 | Edit | Yes | Public | ||
RELSTA | Release Status | Text | 1 | 1 | Edit | Yes | Public | Embedded | |
PUPSTA | Processing Status | Text | 1 | 1 | Edit | Yes | Public | Embedded |
Name | Fields | Properties |
---|---|---|
SPR_INR | INR | Unique |
SPR_OBJIDX | OBJTYP, OBJINR |
/
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 SPR. The field INR is used to maintain links from other tables into this table. The INR is additionally used as file name in the directory structure 'data/delete' to hold the 'savedata' structure of the pending entry.
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.
INR of the SPT entry holding the relevant pending PUR or PUP.
Unique ID of the pending transaction entry holding the relevant pending PUR or PUP.
Type of object the pending entry refers to. Usually this is the table the object is associated to. Partially the table ID is postfixed by the literal 'GRP'.
Type of object the pending entry refers to. Usually this is the table the object is associated to.
INR of the object within the table, defined in OBJTYP.
Unique ID of the object within the table, defined in the Object Type field.
This date defines the date at which this SPT was initially created. The field TIM holds the associated time.
This date field identifies the date the entry was physically added to the database.
This field defines the time at which this SPT was initially created. The field DAT holds the associated time.
This field defines the time when this pending transaction was initially created. The date field holds the corresponding date.
This is the user who created this entry.
This identifies the user who created this entry.
This holds the INR of the session where this SPT has been created.
This field holds the ID of the session that created the pending transaction.
This fields holds the result of the call to the global accessible routine GetSprRelLev which controls the four-eye principle within the application.
This field contains the results of running the globally accessible routine GetSprRelLev, that controls the 4-eye principle in the application.
This date defines the date at which this SPT was released (or sent to correction/deletion). The field TIM holds the associated time.
This date defines the date when this pending transaction was released (or sent to correction/deletion). The time field holds the corresponding time.
This field defines the time at which this SPT was released (or sent to correction/deletion). The field DAT holds the associated time.
This field defines the time when this pending transaction was released (or sent to correction/deletion). The date field holds the corresponding date.
This is the user who released this entry (or sent to correction/deletion).
The field identifies the user who released this entry (or sent it to correction/deletion).
This holds the INR of the session where this SPT has been released (or sent to correction/deletion).
This field holds the unique ID of the session that released (or sent to correction/deletion) this pending transaction.
Code | Text |
---|---|
Waiting | |
R | Released |
C | Sent to Correction |
D | Sent to Deletion |
Any non-empty content marks that this masterfile modification has been processed and is no longer pending.
Any non-empty content indicates that this masterfile modification has been processed and is no longer pending.
Code | Text |
---|---|
Waiting | |
P | Finally Processed |
E | Update Canceled |
N | Not Released |