Search Results iby_pmt_sys_transmissions




Overview
Explore in AI Chat

Overview

The IBY_PMT_SYS_TRANSMISSIONS table is a core repository within the Oracle E-Business Suite (EBS) Payments (IBY) module. It serves as a configuration and control table that defines and manages the available electronic transmission methods for payment files to specific Banking Execution Products (BEPs). In essence, it establishes the permissible communication links between the Oracle Payments engine and external banking partners or payment networks. This table is critical for the successful generation and secure delivery of payment instructions, such as NACHA files, SEPA credit transfers, or other electronic funds transfer (EFT) formats, from the system to the designated financial institution.

Key Information Stored

The table's structure is defined by its primary and foreign key relationships. The primary key is a composite of TRANSMIT_PROTOCOL_CODE and BEPID, enforcing a unique combination of transmission method and banking partner. The TRANSMIT_PROTOCOL_CODE identifies the specific technical protocol used for file transmission, such as FTP, SFTP, HTTP, or a proprietary banking protocol. The BEPID is a foreign key that uniquely identifies the Banking Execution Product, which represents the external payment system or bank interface. Together, these columns define which transmission protocols are enabled for a given BEP. The table may also contain additional control columns, such as those indicating the active status of a transmission link or configuration parameters specific to the protocol-BEP combination.

Common Use Cases and Queries

This table is primarily referenced during the payment file submission process. When the Payment Manager initiates transmission for a generated payment batch, it queries this table to determine the valid transmission options configured for the target BEP. Common administrative and reporting use cases include auditing the configured bank communication methods and troubleshooting transmission failures. A typical query would join this table to its referenced lookup tables to get descriptive information.

  • Listing all configured transmission protocols for a specific BEP:
    SELECT t.transmit_protocol_code, p.protocol_name
    FROM iby_pmt_sys_transmissions t, iby_transmit_protocols_b p
    WHERE t.transmit_protocol_code = p.transmit_protocol_code
    AND t.bepid = &BEP_ID;
  • Identifying all BEPs configured to use a specific protocol (e.g., SFTP):
    SELECT b.bank_name, b.bep_name
    FROM iby_pmt_sys_transmissions t, iby_bepinfo b
    WHERE t.bepid = b.bepid
    AND t.transmit_protocol_code = 'SFTP';

Related Objects

The IBY_PMT_SYS_TRANSMISSIONS table maintains defined foreign key relationships with two key reference tables in the Payments schema, as documented in the ETRM metadata.

  • IBY_TRANSMIT_PROTOCOLS_B: This table provides the master list of all transmission protocols supported by Oracle Payments. The relationship is established via the column IBY_PMT_SYS_TRANSMISSIONS.TRANSMIT_PROTOCOL_CODE referencing IBY_TRANSMIT_PROTOCOLS_B. It validates the protocol code used in the transmissions table.
  • IBY_BEPINFO: This table stores the master definition and details of all configured Banking Execution Products. The relationship is established via the column IBY_PMT_SYS_TRANSMISSIONS.BEPID referencing IBY_BEPINFO. It ensures that a transmission record is associated with a valid, defined BEP.

These relationships are fundamental, ensuring that transmission configurations are based on valid, existing protocols and banking partners, maintaining data integrity within the payment transmission framework.