Results for “delivery_channel_code”

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

Overview

IBY_DELIVERY_CHANNELS_TL is the translation (TL) table within the Oracle Payments (IBY) module that stores language-specific descriptive text for payment delivery channels. A delivery channel defines the medium by which a payment is transmitted to a payee, such as check, wire, ACH, or electronic funds transfer. The base or language-independent attributes reside in IBY_DELIVERY_CHANNELS_B, while this companion table supplies the translated MEANING and DESCRIPTION values used to render delivery channel values in the user's selected locale.

Functionally, the table resembles FND_LOOKUPS but adds a territory identification column, allowing delivery channel definitions to be scoped by geography. It supplies lookup values consumed during external payee setup and documents payable processing. From a Data Vault modeling perspective, the metadata's foreign key structure suggests a satellite-leaning classification: the table carries no independent business identity of its own and instead hangs off the base table through the DELIVERY_CHANNEL_CODE key, making it a descriptive satellite of IBY_DELIVERY_CHANNELS_B rather than a hub or link.

Key Information Stored

The table is keyed at the row level by the primary key IBY_DELIVERY_CHANNELS_TL_PK, composed of DELIVERY_CHANNEL_CODE and LANGUAGE. The unique index IBY_DELIVERY_CHANNELS_TL_U1 extends this combination with ZD_EDITION_NAME, which is the documented business-key candidate that supports edition-based redefinition and online patching in 12.2.2.

• DELIVERY_CHANNEL_CODE — the foreign key linking each translation row back to IBY_DELIVERY_CHANNELS_B; the identifier of the channel itself.
• LANGUAGE — the NLS language code identifying the locale of the translated text (for example, US or DE).
• SOURCE_LANG — indicates the language in which the source text was originally entered.
• MEANING — the translated display name of the delivery channel presented to users, such as "Check" or "Wire".
• DESCRIPTION — a longer translated explanation of the delivery channel's use.
• ZD_EDITION_NAME — the edition identifier enabling coexistence of multiple application versions under EBR.
• OBJECT_VERSION_NUMBER — the optimistic locking and concurrency control column used by the Oracle Application Framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard audit columns recording who created and last modified each row and when.

The surrogate-style uniqueness is imposed through the composite of DELIVERY_CHANNEL_CODE plus LANGUAGE, with the base-table reference acting as the business key anchor rather than a separately generated sequence column.

Common Use Cases and Queries

A frequent requirement is presenting delivery channel values in the appropriate language while filtering out rows belonging to other locales. A typical query joins the translation and base tables:

SELECT tl.meaning, tl.description
FROM   iby_delivery_channels_tl tl
WHERE  tl.language = USERENV('LANG')
AND    tl.delivery_channel_code = :code;

Reporting on external payee setup often needs to confirm which delivery channels are enabled for a given territory, which requires joining to the base table rather than querying the TL table alone. In EBR environments, adding AND ZD_EDITION_NAME = 'ORA$BASE' or the current edition predicate prevents duplicate or cross-edition rows from appearing. Translation audits and language-coverage checks compare counts per LANGUAGE to ensure all channels have been localized, and integration scripts frequently read MEANING to populate dropdown lists in payments user interfaces.

Related Objects

• IBY_DELIVERY_CHANNELS_B — the base table; the TL table references it via DELIVERY_CHANNEL_CODE and inherits its non-translated attributes.
• IBY_EXTERNAL_PAYEES_ALL and related payee assignment tables — consume delivery channel codes when configuring how a payee is paid.
• IBY_DOCS_PAYABLE_ALL — documents payable reference permitted delivery channels during payment processing.
• IBY_PAYMENT_METHODS_B — payment methods are frequently associated with specific delivery channels.
• FND_LOOKUPS — the analogous general-purpose lookup table whose structure IBY_DELIVERY_CHANNELS mirrors, useful for developers migrating patterns.
• IBY_DELIVERY_CHANNELS_VL — the commonly exposed view layered over the base and TL tables for localized reads.

Because the TL table is a dependent satellite, all maintenance activity should flow from the base table through the Applications Dictionary or FND translation APIs; direct DML is discouraged, as it can leave translations out of sync with the base rows and with the edition definition.