Search Results iby_transmit_values




Overview
Explore in AI Chat

Overview

IBY_TRANSMIT_VALUES is a configuration table in the IBY (Payments) module of Oracle E-Business Suite. It stores the individual parameter values that make up a transmission configuration used by Oracle Payments when delivering payment instructions, remittance advice, and related output to external payment systems, banks, and clearing networks. Each row captures a single parameter — for example a file path, a host name, a delimiter character, or a numeric threshold — that the payment transmission framework reads at runtime when building and sending outbound files.

The table sits beneath the transmission configuration header and behaves as a dependent child of it. Under the heuristic Data Vault classification derived from its foreign key structure, the object leans toward a satellite: it holds descriptive, time-stamped attributes (the parameter values) that qualify a parent business entity. It is not itself a hub, because its identity is driven by the driving key TRANSMIT_CONFIGURATION_ID rather than by an independent business key. Modeling teams using Data Vault 2.0 conventions would therefore treat this table as a satellite attached to a configuration hub, retaining the audit columns as load metadata.

Key Information Stored

The table contains 13 documented columns. The most significant are:

  • TRANSMIT_VALUE_ID — the surrogate primary key, enforced by the IBY_TRANSMIT_VALUES_PK constraint. It uniquely identifies each parameter value row and should be used as the reliable join key in downstream queries.
  • TRANSMIT_CONFIGURATION_ID — the foreign key back to the transmission configuration parent. This is the primary business-key candidate and the column that groups related parameter rows together.
  • TRANSMIT_PARAMETER_CODE — identifies which parameter the row supplies. Together with TRANSMIT_CONFIGURATION_ID it forms the natural business key of a configuration's parameter set.
  • TRANSMIT_VARCHAR2_VALUE — the character-based value for the parameter, used whenever the parameter is textual (paths, host names, templates, codes).
  • TRANSMIT_NUMBER_VALUE — the numeric value, used for parameters that represent counts, sizes, ports, or other quantities.
  • TRANSMIT_DATE_VALUE — the date value, used for parameters that carry effective dates or scheduling dates.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns, recording who created and last modified each parameter row and when.
  • OBJECT_VERSION_NUMBER — the optimistic locking column used by the Payments forms and APIs to detect concurrent updates.
  • VAL_SEC_SEGMENT_ID — a segment identifier used in value-set / security validation, allowing parameter values to be restricted or resolved against a defined segment.

The parameter code acts as a discriminator: only one of the three typed value columns is normally populated for a given row, depending on the data type expected by the parameter. Queries should therefore coalesce the three value columns when they need a single display value.

Common Use Cases and Queries

This table is consulted whenever administrators review or troubleshoot a payment transmission setup — for example auditing the file output directory, verifying the transmission protocol parameters, or checking why a payment instruction file was written to an unexpected location. Reporting queries typically join the parameter values back to the parent configuration to present a complete, readable setup.

A representative join pattern is:

  • SELECT v.TRANSMIT_PARAMETER_CODE, COALESCE(v.TRANSMIT_VARCHAR2_VALUE, TO_CHAR(v.TRANSMIT_NUMBER_VALUE), TO_CHAR(v.TRANSMIT_DATE_VALUE)) AS PARAM_VALUE FROM iby.iby_transmit_values v WHERE v.TRANSMIT_CONFIGURATION_ID = :config_id ORDER BY v.TRANSMIT_PARAMETER_CODE;

Because the audit columns are populated automatically, a useful secondary query projects the last update timestamp and user to support change tracking and SOX-style configuration audits. Reconciliation reporting can also compare parameter values across environments when promoting a configuration from test to production.

Related Objects

The following objects are most significant to working with IBY_TRANSMIT_VALUES:

  • IBY_TRANSMIT_CONFIGURATIONS — the parent configuration table. Join on IBY_TRANSMIT_VALUES.TRANSMIT_CONFIGURATION_ID = IBY_TRANSMIT_CONFIGURATIONS.TRANSMIT_CONFIGURATION_ID to retrieve the configuration name and format for each parameter row.
  • IBY_TRANSMIT_VALUES_PK — the primary key constraint on TRANSMIT_VALUE_ID that enforces uniqueness and drives the index used by most lookups.
  • IBY_PAYMENT_SYSTEM_FORMATS and IBY_PAYMENT_SYSTEMS — the payment system definitions whose output ultimately consumes these parameter values when generating payment files.
  • IBY_FD_PAYMENT_INSTRUCTIONS — the payment instruction table whose outbound delivery depends on the resolved configuration parameter values.
  • IBY_TRANSMIT_CONFIGURATION_APIS (Payments public APIs) — the PL/SQL interfaces through which configuration and parameter values are created and maintained, rather than by direct DML.

Direct inserts and updates against this table are discouraged; the supported path is the Oracle Payments configuration UI or its underlying APIs, which preserve the audit columns, the object version number, and the relationship to the parent configuration.