IBM BJ0NJML Integration Guide - Page 117

Format of Interface Tables For example, if a purchase order has three line items, that transaction might produce the following records: T One entry in the MXOUT_INTER_TRANS queue table, with the IFACENAME value equal to the MXPOInterface value, and the TRANSID value equal to 1065. T Three entries in the MXPO_INTERFACE table: „ One entry (PO line 1) with the TRANSID value equal to 1065 and the TRANSSEQ value equal to 1. „ One entry (PO line 2) with the TRANSID value equal to 1065 and the TRANSSEQ value equal to 2. „ One entry (PO line 3) with the TRANSID value equal to 1065 and the TRANSSEQ value equal to 3. The TRANSSEQ column is only in the interface tables. EXTSYSNAME Column An interface table can contain both inbound and outbound transactions. The following table shows that the EXTSYSNAME column in the interface queue tables can contain inbound or outbound data. Value of EXTSYSNAME The external system that is the destination of the transaction. The value of a valid and enabled external system that is defined in the integration framework. Direction of Transaction Outbound Inbound ACTION Column The following table shows the ACTION column values in an interface queue table and the corresponding action that is applied to the interface table. Value in ACTION Column Add Delete Change Replace AddChange Null Integration Framework or External System Action Inserts the data that is provided in the message. Deletes the parent data, and any related child data, from the database. Updates parent and child data contents of the message, but does not delete existing child data that is not explicitly specified in the message. Replaces the existing records with the contents of the message and deletes existing child data that is not referenced in the message. If the primary record does not exist, processes as an add action; otherwise, processes as a change action. If the primary record does not exist, processes as an add action; otherwise, process as a replace action. Interface Tables 103