Search Results bank_transmission_id_pk

Overview

The AP_BANK_TRANSMISSIONS table is a core data object within the Oracle E-Business Suite Payables (AP) module, specifically designed to support the electronic funds transfer (EFT) and payment transmission process. It corresponds directly to the Transmission Window, a key interface where users manage and monitor the creation and status of payment instruction files sent to banks. The table serves as the central repository for each unique transmission event, tracking critical metadata such as the originating bank branch, transmission date, status, and the associated file details. Its primary role is to maintain a definitive audit trail for all outbound payment transmissions, linking high-level transmission data to the individual payment instructions (stored in related tables) that comprise the file.

Key Information Stored

While the full column list is not provided in the excerpt, the documented primary and foreign keys reveal the table's fundamental structure. The primary identifier is BANK_TRANSMISSION_ID, a unique system-generated sequence number. A critical foreign key is BANK_BRANCH_ID, which links the transmission to a specific bank branch defined in the AP_BANK_BRANCHES table. This relationship is essential for determining the payment origin and formatting rules. Based on its functional purpose, the table typically stores columns for transmission status (e.g., 'CREATED', 'TRANSMITTED', 'ACKNOWLEDGED'), the transmission date and time, the generated file name, the transmission method, and identifiers for the payment process request that spawned the transmission. The presence of a primary key constraint (BANK_TRANSMISSION_ID_PK) ensures data integrity for this central entity.

Common Use Cases and Queries

This table is central to payment transmission reporting and troubleshooting. Common operational queries include identifying all transmissions for a specific bank branch within a date range or checking the status of recent transmissions to confirm successful bank delivery. For example, a query to list transmissions and their statuses for a given branch would join AP_BANK_TRANSMISSIONS to AP_BANK_BRANCHES on BANK_BRANCH_ID. Support personnel frequently query this table to find the transmission record for a specific payment file when investigating bank rejections or missing acknowledgments. The table is also pivotal in reconciliation processes, where the transmission record is linked through intermediary tables to individual invoice payments to verify the complete lifecycle of an electronic payment from initiation to bank processing.

Related Objects

• AP_BANK_BRANCHES: A direct parent table, as defined by the documented foreign key. This table supplies the bank and branch details (e.g., bank name, branch number, address) for each transmission.
• AP_SELECTED_INVOICES_ALL / AP_INVOICE_PAYMENTS_ALL: While not explicitly listed in the metadata, transmissions are logically linked to individual payments via these tables, often through the payment batch or instruction identifiers.
• AP_PAYMENT_PROGRAMS: The concurrent request that generates a payment batch and its subsequent transmission file would be related to records in this table.
• Key APIs: The transmission process is typically driven by internal Payables APIs, which populate and update this table during the "Format Payments" and "Transmit Payments" steps of the payment process.