Database views for extracting runtime data

These database views are used to help extract runtime data. The views are defined in izgview.ddl under the schema name FTMPUB.

Batch (ICL) states

The batch (ICL) states view (DEPOSIT_STATES) presents the data corresponding to status of batches (ICLs). The presentment ID field can be used in an SQL select statement to access the status information of a specific batch (ICL).

Business day state

The business day view (BUSINES_DAY_STATE) presents the information for business days. The business day ID field can be used in an SQL select statement to access the information corresponding to a specific business day.

Business day state change log

The business day log view (BUSINESS_DAY_LOG_V) stores information about the business day actions. The business day ID field can be used in an SQL select statement to access the information corresponding to a specific business day. The purpose column of the business day log view is set to Completed when the following business day actions complete successfully:

open
activate
close
end of day check
end of day
holdover
purge

Current transaction data

The current transaction data view (CURRENT_PAYMENT_DATA) presents data corresponding to transactions. Each row includes the document type, field values and validity, and original read field values for specific version numbers.

Entry data

The entry data view (ENTRY_DATA) presents data corresponding to entries that group batches (ICLs). The entry ID field can be used in an SQL select statement to access data corresponding to the bundles or segments that are contained in the entry by matching it against the entry ID field in the inbound bundle data view (INBOUND_BUNDLE_DATA).

Entry states

The entry states view (ENTRY_STATES) presents the data corresponding to status of entries. The entry ID field can be used in an SQL select statement to access the status information of a specific entry.

Inbound batch (ICL) to processing batch (ICL) cross-reference

The inbound batch (ICL) to processing batch (ICL) cross-reference view (PRES_PRES_XREF_V) provides the IDs of the processing batches (ICLs) that are associated with an inbound batch (ICL) ID. The INBOUND_PRES_ID field can be used in an SQL select statement to find the associated processing batch (ICL) IDs.

Inbound bundle data

The inbound bundle data view (INBOUND_BUNDLE_DATA) presents data corresponding to bundles contained in incoming transmissions. The field segment ID can be used in an SQL select statement to access data corresponding to the transactions contained in the bundle by matching it against the segment ID field in the inbound transaction data view (INBOUND_PAYMENT_DATA).

Inbound bundle validation

The inbound bundle validation view (INBOUND_BUNDLE_VALIDATION) presents the data corresponding to incoming bundle validations. The segment ID filed can be used in an SQL select statement to access the validation results for a specific incoming bundle.

Inbound cash letter control records

The inbound cash letter control records view (INBOUND_CL_CTL_RECS) presents the data corresponding to an inbound cash letter. The CASHLTR_ID field can be used in an SQL select statement to access the characteristics of a specific cash letter.

Inbound cash letter data

The inbound cash letter data view (INBOUND_CASHLETTER_DATA) presents data corresponding to cash letters contained in incoming transmissions. The deposit ID field can be used in an SQL select statement to access data corresponding to the bundles contained in the cash letter by matching it against the presentment ID field in the inbound bundle data view (INBOUND_BUNDLE_DATA). The field is used to select data corresponding to the transactions contained in the cash letter by matching it against the deposit ID field in the inbound transaction data view (INBOUND_PAYMENT_DATA).

Inbound cash letter validation

The inbound cash letter validation view (INBOUND_CASHLETTER_VALIDATION) presents the data corresponding to incoming cash letter validations. The cash letter ID field can be used in an SQL select statement to access the validation results for a specific incoming cash letter.

Inbound transaction records

The inbound transaction records view (INBOUND_ITEM_REC) presents the format and data type for transaction records. The PAYMENT_ID field can be used in an SQL select statement to access the data of a specific transaction.

Inbound transmission control records

The inbound transmission control records view (INBOUND_FILE_CTL_RECS) presents the data corresponding to the type of incoming transmissions. The file ID field can be used in an SQL select statement to access the characteristics of a specific transmission.

Inbound transmission data

The inbound transmission data view (INBOUND_FILE_DATA) presents data corresponding to incoming files. The inbound group ID field is used in an SQL select statement to access data corresponding to a particular inbound transmission. The field can be used to select data corresponding to cash letters contained in the file by matching it against the deposit group ID field in the inbound cash letter data view (INBOUND_CASHLETTER_DATA).

Inbound transmission states

The inbound transmission states view (INBOUND_FILE_STATES) presents the data corresponding to status of incoming transmissions. The file ID field can be used in an SQL select statement to access the status information of a received transmission.

Inbound transmission validation

The inbound transmission validation view (INBOUND_FILE_VALIDATION) presents the data corresponding to incoming transmission validations. The file ID field can be used in an SQL select statement to access the validation results for a specific incoming transmission.

Partner custom attributes

The partner custom attributes view (PARTNER_CUSTOM_ATTR) presents the custom attributes for participants. The partner ID field can be used in an SQL select statement to access the custom attribute information corresponding to a specific participant.

Partner profile

The partner profile view (PARTNER_PROFILE) presents data corresponding to participants. The partner ID field can be used in an SQL select statement to access information corresponding to a specific participant.

Processing bank

The processing bank view (PROCESSING_BANK) presents data corresponding to the processing banks. The bank ID field can be used in an SQL select statement to access information corresponding to a specific bank.

Transaction addendum

The transaction addendum view (PAYMENT_ADDENDUMS) presents more data corresponding to transactions. The payment ID field can be used in an SQL select statement to access the additional information of a specific transaction.

Transaction data

The transaction data view (PAYMENT_DATA) presents data corresponding to transactions. Each row includes the document type, field values and validity, and original read field values for the transaction.

Transaction image data

The transaction image data view (PAYMENT_IMAGE_DATA) presents the image-related information corresponding to transactions. The payment ID field can be used in an SQL select statement to access data corresponding to a specific transaction.

Transmission validation

The transmission validation view (ITEM_VALIDATION) presents the data corresponding to transmission validations. The payment ID field can be used in an SQL select statement to access the validation results for a specific transaction.

Validation results

The validation results view (VALIDATION_RESULTS) presents the data corresponding to all transmission, batch (ICL), bundle, and transaction validations. The file ID field can be used in an SQL select statement to access the validation results for a specific transmission.