Search Results transmit_configuration_id




Overview
Explore in AI Chat

Overview

The IBY_TRANSMIT_CONFIGS_B table is a core data object within the Oracle Payments (IBY) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as the master repository for defining and storing electronic payment transmission configurations. These configurations are critical for orchestrating the secure and reliable delivery of payment instruction files from Oracle EBS to external banking partners or payment networks. Each record in this table represents a distinct setup that dictates the technical parameters, such as communication protocol and connection details, required to transmit payment files successfully. The table's role is foundational to the outbound payment flow, linking payment process profiles to specific technical transmission endpoints.

Key Information Stored

The table's primary key is the TRANSMIT_CONFIGURATION_ID, a unique system-generated identifier for each configuration. Based on the provided foreign key relationships, other crucial columns include the TRANSMIT_PROTOCOL_CODE, which references the IBY_TRANSMIT_PROTOCOLS_B table to define the communication standard (e.g., FTP, SFTP, HTTPs). A notable structural feature is the self-referencing foreign key on TUNNELING_TRANS_CONFIG_ID, which allows for complex, layered transmission setups where one configuration can tunnel through another. While the full column list is not detailed in the excerpt, typical data stored would encompass server addresses, port numbers, directory paths, encryption settings, and authentication credentials required for establishing the connection to the bank's server.

Common Use Cases and Queries

This table is primarily accessed during the setup and execution of payment transmission processes. A common use case is troubleshooting failed payment file transmissions, where an administrator must verify the configuration details being used by a specific payment process request. A typical query would join this table to the payment process profile setup to review active configurations.

Sample Query to List Configurations with Protocol:
SELECT tc.transmit_configuration_id,
tc.configuration_name,
tp.protocol_name
FROM iby_transmit_configs_b tc,
iby_transmit_protocols_b tp
WHERE tc.transmit_protocol_code = tp.transmit_protocol_code
ORDER BY tc.transmit_configuration_id;

Another critical scenario involves validating the hierarchical relationship between configurations when tunneling is employed, using the self-referencing key to trace the configuration chain.

Related Objects

The IBY_TRANSMIT_CONFIGS_B table maintains defined relationships with several key objects in the Payments schema, as documented in the provided metadata.

  • IBY_TRANSMIT_PROTOCOLS_B: Linked via the TRANSMIT_PROTOCOL_CODE foreign key. This table stores the definition of the transmission protocols (e.g., FTP, SFTP) available for use.
  • IBY_TRANSMIT_CONFIGS_B (Self-Reference): Linked via the TUNNELING_TRANS_CONFIG_ID foreign key. This relationship allows a transmission configuration to reference another configuration as a tunnel or proxy, enabling complex network routing scenarios.

Furthermore, this table is a parent to various other IBY tables (not listed in the excerpt but inherent to the module) such as those storing process profile assignments and transmission execution logs, forming the central hub for outbound payment communication setup.