Search Results iby_transmit_parameters_b




Overview
Explore in AI Chat

Overview

The IBY_TRANSMIT_PARAMETERS_B table is a core reference data object within the Oracle Payments (IBY) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as a master repository for the configurable parameters associated with various electronic payment transmission protocols. In the context of EBS payment processing, a transmission protocol defines the technical method for sending payment files to a bank or financial institution (e.g., FTP, SFTP, HTTP). This table stores the specific parameters required to configure and execute each protocol, such as server addresses, port numbers, directory paths, and authentication details. Its role is critical for the secure and accurate setup of payment file delivery, enabling the automated transmission of payment instructions generated by the system.

Key Information Stored

The table's structure is designed to support a flexible, code-based model for protocol parameters. Its primary key is a composite of TRANSMIT_PROTOCOL_CODE and TRANSMIT_PARAMETER_CODE, ensuring unique parameter definitions per protocol. The TRANSMIT_PROTOCOL_CODE links the parameter to a specific transmission method defined in the IBY_TRANSMIT_PROTOCOLS_B table. The TRANSMIT_PARAMETER_CODE is a unique identifier for the parameter itself (e.g., 'HOST_NAME', 'USERNAME', 'REMOTE_DIRECTORY'). While the provided metadata does not list all columns, typical columns in such a table would include fields for the parameter's display name, data type, default value, and whether it is mandatory or encrypted for security. This design allows administrators to define and maintain the necessary configuration points for each supported transmission protocol centrally.

Common Use Cases and Queries

The primary use case is the setup and maintenance of payment transmission configurations within the Oracle Payments Manager. When an implementer defines a new payment process profile and selects a transmission protocol, the system references this table to determine which parameters must be collected and validated. For troubleshooting and reporting, database queries against this table are common. A sample query to list all parameters for a specific protocol, such as FTP, would be:

  • SELECT transmit_parameter_code, parameter_name, default_value FROM iby_transmit_parameters_b WHERE transmit_protocol_code = 'FTP' ORDER BY 1;

Another frequent pattern is joining with the protocol table to get a comprehensive view of all available transmission methods and their required settings for audit or documentation purposes.

Related Objects

This table maintains a direct foreign key relationship with the IBY_TRANSMIT_PROTOCOLS_B table, which is the master table for transmission protocols. The relationship is defined on the TRANSMIT_PROTOCOL_CODE column. This means that every record in IBY_TRANSMIT_PARAMETERS_B must correspond to a valid, pre-existing protocol code in IBY_TRANSMIT_PROTOCOLS_B. In application logic, the parameters defined here are referenced by various entities that store actual configuration values for specific payment setups, such as the IBY_EPAY_TRANSMIT_CONFIGS table or similar configuration entities. The table is also likely referenced by key Payment APIs and the underlying PL/SQL packages that construct and execute the file transmission processes.