IBM BJ0NJML Integration Guide - Page 118

Format of Interface Tables The system populates the ACTION column in the outbound messages. If the external system does not populate the column in the inbound messages, the integration framework tries to retrieve and replace the corresponding database record. If the record does not exist, the integration framework tries to add it to the database. IMPORTMESSAGE Column The IMPORTMESSAGE column holds any error message that was produced when the interface table row was moved to the inbound queue. TRANSLANGUAGE Column The TRANSLANGUAGE column identifies the language of the transaction. For an outbound transaction, this value indicates the language of the user who initiated the transaction. For an inbound transaction, this value indicates the language of the transaction. Any attributes that support a multilanguage environment are expected to be in the language that the TRANSLANGUAGE value defines. MESSAGEID Column The MESSAGEID column is a unique identifier that the system assigns to every outbound transaction. IFACETBNAME Column The IFACETBNAME column is the name of the interface table that corresponds to the IFACENAME column. This column applies to outbound transactions only. Long Description Columns in Oracle Databases Long description columns are stored in a CLOB (character large object) column in an Oracle database. However, interface tables contain two versions of each CLOB column, one with data type CLOB, and one with data type ALN with a character length of 4000. In the following example, the name of the CLOB column is the column alias. The name of the alphanumeric column is the column alias with the suffix 2. Data Type CLOB ALN Name of Description Column PO_DESCRIPTION_LD PO_DESCRIPTION_LD2 The system populates both columns in outbound transactions. For inbound transactions, the integration framework uses the value in the ALN column if it is not null; otherwise, the value in the CLOB column is used. 104 Integration Guide