In the log file of SPTs it can be retraced, which SPTs have been generated for which records and at what point in time particular processes took place.
These log files are stored in the standard log and have the following format:
“spt.<Date>.log”

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.

Type of object the pending entry refers to. Usually this is the table the object is associated to.

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 identifies the reference key of the object identified by object type and the internal unique ID of object.

This field is used to describe the source of the pending entry in a way that is readable to the user.

On pending entries the name of the storing transaction might be used. For incoming messages, the type of message and the sender who is sending the message can be used.

Date and time when this pending transaction was initially created.

Identifies the user who created this entry.

Holds the unique ID of the session creating this pending transaction.

This field identifies the transaction used to process the pending transaction entry.

If a certain panel is to be displayed when a pending transaction entry is picked up, the respective panel ID can be set here. If the field is not empty, the pick up routine focuses on the panel defined here. If the panel does not exist, the error is skipped.

The stored SaveData structure holds the following information depending on the status of the pending transaction entry: PEN / DEL: A SAVEDATA of the main transaction record/record group and additional stored data depending of additional logic. Normally the dataset of a master file maintenance transaction. REJ / COR: The complete SAVEDATA of the business transaction stored in TRNDATA upon save plus the BIMDATA information. INC / STP: The record group of the contract to be handled upon processing of the incoming message plus the SWIADD group. STP handles a incoming message which might be processed without any user interaction. AUT / MAN: The record group of the contract to be processed holding primarily the INR to identify the contract. RIM: SWIADD as a dummy group. The contents of this group has no relevance.

If not empty, the entry is no longer active. To reactivate the entry the flag has to be cleared.

If not empty, this pending transaction cannot be picked up/displayed.

Flag to define whether the infotext stored is to be displayed when picked up.

Infotext associated to the entry. The Info Flag field controls whether this text must be prompted to the user when picking up the entry.

User group responsible for picking up the entry.

This field holds the User ID of the person responsible for the follow-up transaction.

If an incoming message is associated to the pending entry, the SMH entry of that message is identified here.

If not empty, the data stored in the savedata structure of this pending transaction (SPT) can be recreated using SPTRER.

This flag should only be set for incoming pending transactions created in SRVxxx.

Transaction name used to create this entry.

This field is empty if the pending transaction was not triggered by an order. Otherwise it shows the unique ID of the order entry which triggered this entry.

Defineds the target date and time on which this entry is to be processed. The time is usually set some hours ahead of the initial creation of the entry or to '0' if no special target time is required.

Optional field to identify the object type of the creating object.

Optional field to identify the concrete object that triggered the creation of this pending transaction.

Predefined Priority Class (as defined in service level agreement with ordering customer).

Channel (CORTYP) by which this order was received

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

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

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.

Unique interal ID of the service layer

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

Incoming Messages SWITSK to set to 1 MGRTSK to set to 2 MQITSK/SWITSK to set to A/N

Parties SPTREL to set to 1 MGRTSK to set to 2 MQITSK/SWITSK to set to A/N DBEPTx set to ' ' - if CCS check not necessary

This field identifies the transaction for which the mapping had been executed. Will be set initially in switsk to the same value as FRM and updated whenever the incoming message is reroutet.

It is used to decide if INCSPT needs to be rerouted by comparing FRM with MAPFRM. If not the same, inc message is picked up whith chaining through SPTRER for FRM.

Might include switches with values as arguments for the target transaction. E.g. Type of SPT. When SPT target is a xxtFRE then we can use the a switch in the field to direct which message to produce. Extract the content by GetSwitchFromLine.