Search Results transmission_id

Overview

The AP_TRANSMISSIONS_SETUP table is a core data object within the Oracle E-Business Suite Payables (AP) module. It serves as the primary repository for configuration details related to electronic bank transmissions, specifically for payment formats. This table directly corresponds to the "Bank Transmission Details" window in the application's user interface, where users define and manage the technical parameters required to generate electronic payment files (e.g., NACHA, BACS, SEPA). Its role is critical for the Payables payment process, as it links payment instructions to specific bank accounts and defines the file formatting and transmission protocols necessary for successful electronic funds transfer (EFT).

Key Information Stored

The table stores setup information for each distinct bank transmission method. While the full column list is not provided in the excerpt, the primary and foreign key relationships indicate the core data entities involved. The primary key, TRANSMISSION_ID, uniquely identifies each transmission setup record. A critical foreign key, BANK_BRANCH_ID, links the setup to a specific bank branch defined in the AP_BANK_BRANCHES table. Other typical columns in such a setup table would include configuration for the transmission protocol (e.g., FTP, SFTP details), output file naming conventions, encryption standards, the specific payment format code, and delivery parameters. This setup acts as a template applied when generating payment batches for the associated bank account.

Common Use Cases and Queries

The primary use case is the configuration and execution of electronic payments. When a payment batch is initiated for a bank account, the system references the AP_TRANSMISSIONS_SETUP record linked to that account's branch to determine how to format and transmit the payment file. Common queries involve listing all transmission setups for audit purposes or troubleshooting payment file generation issues. A typical SQL pattern retrieves setup details joined with bank information:

• SELECT ats.transmission_id, abb.bank_name, abb.bank_branch_name, ats.* FROM ap_transmissions_setup ats, ap_bank_branches abb WHERE ats.bank_branch_id = abb.bank_branch_id;
• Another common query identifies setups for a specific payment format or protocol to manage configurations centrally.

Related Objects

AP_TRANSMISSIONS_SETUP has defined relationships with other key Payables tables, primarily through foreign key constraints. As documented in the metadata:

• AP_BANK_BRANCHES: This is the primary related table. The column AP_TRANSMISSIONS_SETUP.BANK_BRANCH_ID is a foreign key referencing AP_BANK_BRANCHES. This relationship ensures that every transmission setup is associated with a valid, defined bank branch.
• While not listed in the provided excerpt, this table is also logically related to payment batch tables (e.g., AP_INVOICE_PAYMENTS, AP_CHECKS) and payment format definition tables, as the transmission setup is applied during the final stage of the payment process to create the output file.