Search Results iby_fndcpt_pmt_chnnls_tl




Overview
Explore in AI Chat

Overview

IBY_FNDCPT_PMT_CHNNLS_TL is the translation table for IBY_FNDCPT_PMT_CHNNLS within the Oracle E-Business Suite Payments (IBY) module. The base entity, IBY_FNDCPT_PMT_CHNNLS, defines all payment methods available to the funds capture flow. Payment methods are categorized by instrument type, with the supported classifications being BANKACCOUNT, CREDITCARD, and DEBITCARD. Each payment method record carries the attributes that govern how funds are captured against a given channel and instrument combination.

The "_TL" suffix identifies this as a language-specific translation (_TL) table, meaning it stores the user-facing text for the payment channel in each installed language rather than the operational configuration itself. This separation allows a single payment channel definition to be presented to users in multiple languages without duplicating the underlying configuration data. Based on the foreign key structure and the translation role of the object, a Data Vault modeling exercise would most likely classify this table as satellite-leaning — a descriptive, slowly changing companion to the parent channel entity rather than an independent hub or a link resolving relationships between hubs.

Key Information Stored

The documented physical schema for this object in ETRM 12.2.2 contains twelve columns. The most significant are:

  • PAYMENT_CHANNEL_CODE — The business identifier for the payment channel. This is both the join key back to the base table IBY_FNDCPT_PMT_CHNNLS and a component of the unique business key on this translation table.
  • PAYMENT_CHANNEL_NAME — The translated, display-facing name of the payment channel in the row's language.
  • DESCRIPTION — The translated long description of the payment channel.
  • LANGUAGE — The language code for the translated text, and a component of the unique index IBY_FNDCPT_PMT_CHNNLS_TL_U1.
  • SOURCE_LANG — The language of the source text from which the translation was derived, used by the translation framework to track language lineage.
  • ZD_EDITION_NAME — The editioning column introduced by the EBS 12.2 online patching architecture; it forms the third component of the unique index and isolates rows per edition.
  • OBJECT_VERSION_NUMBER — The optimistic locking column used by Oracle Forms and the OAF framework to detect concurrent updates.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard EBS audit columns populated by the WHO columns framework.

The unique index IBY_FNDCPT_PMT_CHNNLS_TL_U1 spans (LANGUAGE, PAYMENT_CHANNEL_CODE, ZD_EDITION_NAME), confirming that the combination of language, channel code, and edition is the business-key candidate. Note that the parent table's own documented foreign key reference is IBY_FNDCPT_PMT_CHNNLS_TL.PAYMENT_CHANNEL_CODE, reflecting the metadata's presentation of the relationship; in practice the translation row references its base-table parent through PAYMENT_CHANNEL_CODE and LANGUAGE.

Common Use Cases and Queries

The primary use case is multilingual reporting on payment method configuration. A typical query joins the translation back to the base channel table, restricted to a user's session language:

  • Listing all active payment channels with their localized names: SELECT b.PAYMENT_CHANNEL_CODE, t.PAYMENT_CHANNEL_NAME FROM IBY_FNDCPT_PMT_CHNNLS b, IBY_FNDCPT_PMT_CHNNLS_TL t WHERE b.PAYMENT_CHANNEL_CODE = t.PAYMENT_CHANNEL_CODE AND t.LANGUAGE = USERENV('LANG')
  • Detecting missing translations by comparing row counts between the base table and this table per language.
  • Auditing description text changes across languages for compliance or localization review.
  • Feeding downstream reporting or integration extracts where the localized channel name is required on payment capture documents.

Because the table is a translation satellite, direct DML is generally performed through the Payments setup UI rather than by custom code; modifications should follow the standard _TL maintenance conventions.

Related Objects

The following objects are significant to the use of this table:

  • IBY_FNDCPT_PMT_CHNNLS — The base (non-translated) channel definition table; joined on PAYMENT_CHANNEL_CODE and LANGUAGE.
  • IBY_FNDCPT_PMT_CHNNLS_TL_U1 — The unique index enforcing the business key (LANGUAGE, PAYMENT_CHANNEL_CODE, ZD_EDITION_NAME).
  • IBY_FNDCPT_PMT_CHNNLS_B and IBY_FNDCPT_PMT_CHNNLS_VL — In the standard EBS _B/_TL/_VL pattern, the base and view-layer counterparts used by OAF pages.
  • IBY_CREDITCARD_TYPE and related instrument tables — Instrument-type consumers (BANKACCOUNT, CREDITCARD, DEBITCARD) whose validation relies on channel configuration.
  • IBY_FNDCPT_PAYER_INSTRUMENTS — Payer instrument records that reference the payment channel used for funds capture.
  • IBY_FNDCPT_TRXN_B — Funds capture transaction records associated with a payment channel.

Together these objects form the configuration backbone of the IBY funds capture payment method model.