Results for “iby_fndcpt_user_dc_pf_tl”

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

Overview

IBY_FNDCPT_USER_DC_PF_TL is the translation table for user-defined disbursement channel (payee/electronic payment) profiles within the Oracle Payments (IBY) module. In Oracle EBS 12.1.1 and 12.2.2, this table stores the language-specific, translated display names for those profiles, while the base (untranslated) attributes reside in the companion table IBY_FNDCPT_USER_DC_PF_B. Payment administrators use disbursement channel profiles to define how a payee receives funds — for example, by check, ACH/EFT, wire, or a clearinghouse mechanism — and the profile name is what users actually see when selecting a payment method at the payee or payment-process level.

The object is registered in the IBY schema with VALID status and is documented with 10 physical columns in the ETRM 12.2.2 metadata. Its foreign key relationship is a single, self-contained dependency: USER_DC_PROFILE_CODE references IBY_FNDCPT_USER_DC_PF_B. Under the heuristic Data Vault classification provided (mined from its FK structure), the table is described as satellite-leaning. Modelling such objects as satellites — child rows keyed to a parent business key plus a language/context discriminator — aligns with standard practice, since a translation table qualifies each base entity record with additional descriptive, non-key attributes rather than introducing new hubs or links. The companion "_B" table acts as the base (hub-like) entity, and this "_TL" translation table carries the language-dependent attributes.

Key Information Stored

The most significant columns (all documented) are:

• USER_DC_PROFILE_CODE — the business key that ties every translation row back to its parent profile in IBY_FNDCPT_USER_DC_PF_B. This is the foreign key and a business-key candidate for joining and de-duplication.
• LANGUAGE — the language of the translated display name; combined with USER_DC_PROFILE_CODE this forms the effective unique composite key of the translation record.
• SOURCE_LANG — the base language from which the translation originated, used to identify the originating language at the time a row was created or last maintained.
• USER_DC_PROFILE_NAME — the translated, user-facing name of the disbursement channel profile; this is the primary descriptive attribute the table exists to store.
• CREATED_BY, CREATION_DATE — standard audit columns recording who created the row and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns recording the most recent modification and its author.
• LAST_UPDATE_LOGIN — the login session identifier associated with the most recent update, useful for auditing session context.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the Oracle Applications framework to detect concurrent updates.

Note that this translation table does not itself carry a surrogate single-column primary key in the documented schema; the identifying key is the combination of USER_DC_PROFILE_CODE and LANGUAGE. The primary key of the underlying profile belongs to the base table.

Common Use Cases and Queries

Typical scenarios include multi-language payee payment configuration, profile-name reporting, and data-migration validation when moving or extracting disbursement channel setups. A common query pattern joins the translation table to its base table to produce a language-resolved profile name:

SELECT b.user_dc_profile_code, t.user_dc_profile_name, t.language
FROM iby_fndcpt_user_dc_pf_b b, iby_fndcpt_user_dc_pf_tl t
WHERE b.user_dc_profile_code = t.user_dc_profile_code
AND t.language = USERENV('LANG');

Reporting queries frequently filter by a specific LANGUAGE or use SOURCE_LANG to identify translation gaps — profiles that exist in the base table but lack a translation for a required language. Auditing scenarios leverage CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_DATE to track when a translated profile name changed and by whom. Migration or data-conversion scripts validate that every USER_DC_PROFILE_CODE in IBY_FNDCPT_USER_DC_PF_B has a corresponding translation row, and use OBJECT_VERSION_NUMBER to detect concurrency conflicts.

Related Objects

• IBY_FNDCPT_USER_DC_PF_B — the base, untranslated table holding the primary profile attributes; joined on USER_DC_PROFILE_CODE. This is the direct parent of the translation table per the documented foreign key.
• IBY_FNDCPT_PAYEE_ASSIGNMENTS — associate payees with disbursement channel profiles, providing the context in which profile names are surfaced.
• IBY_FNDCPT_PROFILE_ASSIGNMENTS / IBY_FNDCPT_DC_PF_ASSIGNMENTS — assignment tables that link profiles to payment processing contexts.
• IBY_DISBURSEMENT_TYPES and the IBY payment method configuration tables — define the disbursement mechanisms that profiles reference.
• IBY_PAYEE / IBY_PMT_INSTR_USES — consume disbursement channel information for actual payment instructions.
• FND_LANGUAGES — provides the valid LANGUAGE codes referenced by translation rows.

Because the ETRM metadata for this object is limited to its schema and FK structure, column-level business semantics beyond the documented list should be confirmed against the application's profile setup UI and the IBY Payments implementation guide for the specific release.