Format of Interface Tables
Interface Tables 103
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.
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 of EXTSYSNAME Direction of
Transaction
The external system that is the destination of the
transaction.
Outbound
The value of a valid and enabled external system
that is defined in the integration framework.
Inbound
Value in ACTION
Column
Integration Framework or External System
Action
Add Inserts the data that is provided in the message.
Delete Deletes the parent data, and any related child data,
from the database.
Change Updates parent and child data contents of the
message, but does not delete existing child data that
is not explicitly specified in the message.
Replace Replaces the existing records with the contents of
the message and deletes existing child data that is
not referenced in the message.
AddChange If the primary record does not exist, processes as an
add action; otherwise, processes as a change action.
Null If the primary record does not exist, processes as an
add action; otherwise, process as a replace action.
To Next Page
Loading...