Results for “iby_fndcpt_sys_dc_pf_tl”

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

Overview

IBY_FNDCPT_SYS_DC_PF_TL is a translation (TL) table in the IBY — Payments module of Oracle E-Business Suite. It stores the language-specific, user-visible text for system-level funds disbursement capture (FNDCPT) profile definitions. The base table IBY_FNDCPT_SYS_DC_PF_B holds the language-independent attributes of each system disbursement capture profile, while this _TL table holds the translated profile name and description that are rendered to users according to their session language. The suffix "SYS_DC_PF" denotes "System Disbursement Capture Profile," a configuration object that governs how payment instruments are captured and processed for a given operating unit or system context.

From a dimensional modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table's only outbound relationship points to a profile code that is itself the parent business key, which is characteristic of a satellite table extending a hub or parent entity with descriptive, language-dependent attributes. This classification is a heuristic suggestion rather than a documented fact, and should be validated against the actual data model before being relied upon for warehouse design.

Key Information Stored

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

• SYS_DC_PROFILE_CODE — The business key identifying the system disbursement capture profile. It joins upward to the base profile definition and is a component of the unique index.
• LANGUAGE — The language code for the translated row; part of the composite unique key.
• ZD_EDITION_NAME — The edition identifier used by the E-Business Suite editioning and online patching framework; also part of the unique key.
• SYS_DC_PROFILE_NAME — The translated, display-facing name of the profile.
• DESCRIPTION — The translated textual description of the profile's purpose or behavior.
• SOURCE_LANG — The language from which the translation was derived.
• CREATED_BY, CREATION_DATE — Standard audit columns recording row insertion.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification and the login context.
• OBJECT_VERSION_NUMBER — Optimistic locking token used by the Oracle Application Framework (OAF) to detect concurrent updates.

The composite unique index IBY_FNDCPT_SYS_DC_PF_TL_U1 (LANGUAGE, SYS_DC_PROFILE_CODE, ZD_EDITION_NAME) is the documented business-key candidate. No separate surrogate primary key column is documented in the metadata; the profile code, language, and edition jointly enforce uniqueness.

Common Use Cases and Queries

Typical usage centers on resolving the correct display text for a profile given the user's language, and on validating that translations exist for all required languages.

• Retrieve the localized name for a profile: SELECT SYS_DC_PROFILE_NAME, DESCRIPTION FROM IBY.IBY_FNDCPT_SYS_DC_PF_TL WHERE SYS_DC_PROFILE_CODE = :code AND LANGUAGE = USERENV('LANG');
• Detect missing translations: compare the distinct languages present in the _TL table against the installed languages in FND_LANGUAGES to find profiles lacking a translation.
• Reporting joins against the base profile table on SYS_DC_PROFILE_CODE, filtering on LANGUAGE to produce language-specific extracts for audit or documentation.
• Seed data and migration scripts often insert rows here after creating a base profile, supplying the translated name and description.

Because the table is small and read-mostly, queries are inexpensive and typically performed during page rendering or report generation rather than batch processing.

Related Objects

The principal related objects are:

• IBY_FNDCPT_SYS_DC_PF_B — The base (language-independent) profile definition; joined on SYS_DC_PROFILE_CODE.
• IBY_FNDCPT_SYS_DC_PF_VL — The translated view that presents base and TL columns as a single logical entity; the preferred access path for most queries.
• IBY_FNDCPT_SYS_DC_PF_TL — The table itself, referencing its own SYS_DC_PROFILE_CODE as documented in the FK metadata.
• FND_LANGUAGES — Supplies valid language codes and installation status.
• FND_APPLICATION / FND_PRODUCT_INSTALLATIONS — Determine which languages are active for the IBY application.
• IBY_FNDCPT_PAYER_INSTR_ASSIGN and related disbursement capture configuration tables — Depend indirectly on the system profile through the base table.

Because the metadata documents only the self-referencing foreign key, additional relationships are inferred from the IBY schema conventions and should be confirmed against the application's own views and PL/SQL APIs before being used in custom development.