Results for “iby_transmit_configs_tl”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IBY_TRANSMIT_CONFIGS_TL is the translation (multi-language) table for transmit configurations in the Oracle Payments (IBY) module. A transmit configuration defines the transport mechanism — for example, protocol type, connection parameters, and delivery settings — that Oracle Payments uses to dispatch payment instruction files, remittance advice, and other outbound payment artifacts to a payment system, bank, or file-transfer endpoint. Because Oracle E-Business Suite supports multiple installed languages, the descriptive, user-facing attributes of each transmit configuration are stored in this TL table rather than in the base IBY_TRANSMIT_CONFIGS_B table, allowing the same configuration to be presented to users in their native session language.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this object as satellite-leaning. In practice, IBY_TRANSMIT_CONFIGS_TL behaves as a dependent descriptive child of the base transmit configuration entity: its key includes the owning configuration identifier plus a language discriminator, and it carries the human-readable name. It contains no independent business identity of its own, which is characteristic of a satellite or a translation-dependent record rather than a hub or link.

Key Information Stored

The table is documented with 10 columns. The most significant are:

• TRANSMIT_CONFIGURATION_ID — the surrogate identifier that ties the translated row back to its parent transmit configuration in the base table. It is the primary join key and forms part of the composite key of this table together with LANGUAGE.
• LANGUAGE — the language code of the translated row, identifying which installed language the descriptive text belongs to. This is the second component of the translation key.
• SOURCE_LANG — the language from which the text was originally entered or derived, used by the translation framework to track the origin of the descriptive content.
• TRANSMIT_CONFIGURATION_NAME — the user-visible name of the transmit configuration, and the primary business-facing attribute held in this table. This is the primary candidate for display and lookup reporting, and it is the only descriptive business column defined here.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Application Framework to detect concurrent modification of the row.
• 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 the row, when, and through which login session.

The surrogate primary key is TRANSMIT_CONFIGURATION_ID combined with LANGUAGE; TRANSMIT_CONFIGURATION_NAME is the principal business-key candidate for display purposes, since the name should be unique within a given language for a given configuration.

Common Use Cases and Queries

Typical usage centers on retrieving the translated display name of a transmit configuration for a given session language, either for user-interface, reporting, or integration purposes. A common query pattern joins this table to the base configuration and filters by language:

• Lookup the name for a specific configuration and language: SELECT transmit_configuration_name FROM iby_transmit_configs_tl WHERE transmit_configuration_id = :id AND language = USERENV('LANG');
• List all configured transmit mechanisms with their localized names for a setup report: SELECT b.transmit_configuration_id, t.transmit_configuration_name FROM iby_transmit_configs_b b, iby_transmit_configs_tl t WHERE b.transmit_configuration_id = t.transmit_configuration_id AND t.language = USERENV('LANG');
• Audit translations and detect missing entries by joining the base table left-outer to this table for each installed language, surfacing configurations that lack a translated name.
• Reporting on configuration maintenance activity using CREATION_DATE and LAST_UPDATE_DATE to identify recently added or changed transmit configurations.

In each case the join is driven by TRANSMIT_CONFIGURATION_ID, with LANGUAGE restricting the result to a single row per configuration.

Related Objects

The following objects are the most significant in relation to IBY_TRANSMIT_CONFIGS_TL:

• IBY_TRANSMIT_CONFIGS_B — the base (non-translated) table holding the core transmit configuration attributes. The documented foreign key relationship is IBY_TRANSMIT_CONFIGS_TL.TRANSMIT_CONFIGURATION_ID referencing the base configuration, making this the primary parent object.
• IBY_TRANSMIT_CONFIGS_VL — the translated view that typically exposes the joined base and TL data, providing the standard access path used by Oracle Payments forms and OAF pages.
• IBY_TRANSMIT_CONFIGURATIONS / transmit-configuration setup entities — configuration and setup screens in Oracle Payments that reference transmit configurations and depend on the translated name.
• IBY_PAY_SYSTEMS and payment system configuration objects — payment systems frequently associate transmit configurations to determine how files are delivered, referencing the configuration identifier.
• IBY_FD_* payment instruction and delivery objects — records describing payment file delivery may reference the transmit configuration used, linking back to this table for the localized name.

These relationships are joined through TRANSMIT_CONFIGURATION_ID, which propagates the configuration identity from the base table through this translation satellite.