Populating the FTM Data Structure

Table 1, Table 2, and Table 3 show the data placed in the outbound FTM transmission structure when building transmissions in Distribution. Only those columns that are used are shown here. For a complete list of all of the columns in these views, refer to the FTM data model documentation (http://www.ibm.com/support/docview.wss?uid=swg21969789 has information about obtaining the documentation for the FTM data model.).

Distribution also creates outbound Payment Feature Services extensions when building transmissions. It uses the following extension keys:

ElementSeparator
OutPresGrpId
OutPresId
ReceiverType
SegmentTerminator
SenderType
Version
824 ack
997 ack

For information about all of the Payment Feature Services extensions, see Payment Feature Services Extensions.

Table 1. TRANSMISSION_V
Column	Description
ID	Unique identifier for the transmission. It is auto generated.
APP_ID	In file to file mode, this is the application ID from the inbound transmission. Otherwise, the application ID is retrieved using System Property-> Application Name.
STATUS	The status indicator It is always "S_OutPTCreated".
OWNER_ID	In file to file mode, this is the owner ID from the inbound transmission. Otherwise, it is null.
SUBTYPE	The SUBTYPE custom attribute from the transmission definition.
SENDER	In file to file mode, this is the sender from the inbound transmission. Otherwise, the transmission definition is used to determine the sender. The sending point from transmission definition is used unless it is null. If the sending point is null, the bank name is used.
RECEIVER	In file to file mode, this is the receiving point from the inbound transmission. Otherwise, it is the name of the receiving partner.
FILENAME	The file name pattern from the transmission definition.
BAT_COUNT	This value is calculated from number of batches (ICLs) in the transmission.

Table 2. BATCH_V
Column	Description
ID	Unique identifier for the batch (ICL). It is auto generated.
APP_ID	The value used for this column depends on the mode being used. The modes are listed in descending order of precedence. batch to batch mode the application ID from the incoming batch (ICL) is used file to file mode the application ID from the inbound transmission is used neither the application ID is retrieved using System Property-> Application Name
STATUS	The status indicator It is always "S_OutBatCreated".
OWNER_ID	The value used for this column depends on the mode being used. The modes are listed in descending order of precedence. batch to batch mode the owner ID from the inbound batch (ICL) is used file to file mode the owner ID from the inbound transmission is used neither null is used
SENDER	The value used for this column depends on the mode being used. The modes are listed in descending order of precedence. batch to batch mode the sender from the inbound batch (ICL) is used file to file mode the sender from the inbound transmission is used neither the bank name is used
RECEIVER	The value used for this column depends on the mode being used. The modes are listed in descending order of precedence. batch to batch mode the receiving point from the inbound batch (ICL) is used file to file mode the receiving point from the inbound transmission is used neither the name of the receiving partner is used
TRANSMISSION_ID	The value is calculated.
VALUE_AMOUNT	The value is calculated.
BATCH_DATE	The date that Distribution created the batch (ICL).
TXN_COUNT	The value is calculated.
SEQUENCE	The value is calculated.

Table 3. TXN_PAYMENT_V
Column	Description
ID	Unique identifier for the transaction. It is auto generated.
APP_ID	The application ID from the incoming transaction.
STATUS	The status indicator It is always "S_OutTxnCreated".
OWNER_ID	The owner ID from the inbound transaction.
SENDER	The sender from the inbound transaction.
RECEIVER	The receiving point from the inbound transaction.
TRANSMISSION_ID	The value is calculated.
BATCH_ID	The value is calculated.
CURRENCY	CURRENCY_CODE from the PAYMENT table.
AMOUNT	CURRENT_AMOUNT from the PAYMENT table.
BANK_CODE	BANK_CODE from the incoming transaction.
ACCCOUNT	ACCOUNT from the incoming transaction.
DEST_BANK_CODE	FIELD_5 from the ITEM table.
DEST_ACCCOUNT	FIELD_3 from the ITEM table.
ISF_DATA	ISF_DATA from the incoming transaction.
PAYMENT_TYPE	PAYMENT_TYPE from the incoming transaction.
PMC	PMC from the incoming transaction.
TXN_TIMESTAMP	TXN_TIMESTAMP from the incoming transaction.
BOOK_DATE	BOOK_DATE from the incoming transaction.
VALUE_DATE	VALUE_DATE from the incoming transaction.
SETTLE_DATE	SETTLE_DATE from the incoming transaction.
ALT_ID	PAYMENT_ID from the PAYMENT table.
ISF_FMT_ID	ISF_FMT_ID from the incoming transaction.
DEBIT_CREDIT_FLAG	If the PAYMENT-> CREDIT_ITEM column is 0, this column is set to N. Otherwise, it is set to Y.
TXN_SEQUENCE	The value is calculated. It is the relative sequence number from the start of the batch (ICL).