Interface queue tables
The interface queue tables identify the sequence in which a receiving system should process the records in the respective interface tables. Two queue tables exist, one for inbound transactions and the other for outbound transactions.
|
Interface queue table |
Processing direction |
|---|---|
|
MXOUT_INTER_TRANS |
Outbound |
|
MXIN_INTER_TRANS |
Inbound |
Some transactions depend on the successful processing of a previous transaction. For example, a PO record must be processed before the PO receipt record. The receiving system must process the records in the same sequence in which the sending system created the records.
All inbound and outbound transactions must have a record that is inserted into the corresponding inbound or outbound queue table. This record contains an IFACENAME column which identifies the publish channel or enterprise service. The TRANSID is a unique sequential identifier that the interface table uses to identify the record or records that are associated with the transaction. You can identify the contents of a transaction by looking up all the records with a given TRANSID value in the corresponding interface table.
The sequence of TRANSID identifies the sequence in which records are processed by the integration framework. For example, when the PO and receipt are entered into Maximo Asset Management, the TRANSID values for the PO record must be less than the TRANSID values for the PO receipt records that reference that PO.
The primary difference between the MXIN_INTER_TRANS and MXOUT_INTER_TRANS queue tables is the direction of the interface table records that they track. The external system must write to the MXIN_INTER_TRANS queue table, and the integration framework must read from it. The integration framework writes to the MXOUT_INTER_TRANS queue table, and the external system reads from it.
The external system can use the MXOUT_INTER_TRANS table or retrieve outbound records from interface tables. The interface queue tables are generated the first time that you create interface tables for an endpoint. Each endpoint has its own pair of interface queue tables and own a counter for maintaining the outbound TRANSID value.