Results for “iby_f_crdt_app_status_tl”

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

Overview

IBY_F_CRDT_APP_STATUS_TL is a translation table within the Oracle E-Business Suite Payments (IBY) module. It stores the language-specific, multi-lingual (ML) descriptive text associated with credit application statuses defined in the base table IBY_F_CRDT_APP_STATUS_B. In Oracle EBS 12.1.1 and 12.2.2, the "_TL" suffix denotes an Oracle Applications translation table that follows the standard MLS (Multi-Language Support) framework pattern. Each row represents the displayable name and description of a credit application status in a specific installed language, allowing the application to present statuses to users in their native language.

From a data modeling perspective, the mined foreign key structure suggests a satellite-leaning classification. This table does not introduce independent business entities or define relationships between other entities; instead, it depends entirely on the base table through its CREDIT_APP_STATUS_ID column and enriches it with language-dependent attributes. Under Data Vault conventions it would reasonably be modeled as a satellite attached to the IBY_F_CRDT_APP_STATUS_B hub.

Key Information Stored

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

• CREDIT_APP_STATUS_ID — The surrogate key inherited from the base table IBY_F_CRDT_APP_STATUS_B. It identifies the parent status whose translation is stored here.
• LANGUAGE — The NLS language code identifying the locale of the translated text. Together with CREDIT_APP_STATUS_ID, it forms the composite primary key IBY_F_CRDT_APP_STATUS_TL_PK.
• NAME — The translated, user-facing name of the credit application status. A unique index, IBY_F_CRDT_APP_STATUS_TL_U2, enforces uniqueness on (NAME, LANGUAGE), making NAME a business-key candidate alongside the primary key.
• DESCRIPTION — The translated longer description of the status, providing additional explanatory context to end users.
• CUST_FACING_NAME — A customer-facing variant of the status name, used when the status is surfaced to external parties rather than internal users.
• SOURCE_LANG — The source language from which the current translation was derived, following standard MLS convention for translation origin tracking.
• SECURITY_GROUP_ID — The multi-org security group identifier, with a foreign key to FND_SECURITY_GROUPS, controlling data access across operating units.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns capturing who created and last modified each translation row and when.

Common Use Cases and Queries

Typical usage centers on reporting and lookup resolution. Queries resolve the translated name for a given status in the user's session language using a join to the base table:

• Status lookup by language: SELECT t.NAME, t.DESCRIPTION FROM IBY.IBY_F_CRDT_APP_STATUS_TL t WHERE t.CREDIT_APP_STATUS_ID = :status_id AND t.LANGUAGE = USERENV('LANG').
• All translations for a status: SELECT t.LANGUAGE, t.NAME, t.CUST_FACING_NAME FROM IBY_F_CRDT_APP_STATUS_TL t WHERE t.CREDIT_APP_STATUS_ID = :status_id ORDER BY t.LANGUAGE, to compare locale coverage.
• Translation completeness audit: compare row counts per LANGUAGE against the installed languages to detect missing translations, a common validation performed after patching or upgrades.
• Reporting: join IBY_F_CRDT_APP_STATUS_TL to IBY_F_CRDT_APP_STATUS_B and payment credit application tables to render human-readable status labels in custom payment or credit reports.

Related Objects

The following objects reference or are referenced by this table:

• IBY_F_CRDT_APP_STATUS_B — The base (non-translated) table. Joined via CREDIT_APP_STATUS_ID; it holds the language-neutral status definition while this table holds the translated attributes.
• FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID for multi-org access control.
• IBY_F_CRDT_APP_STATUS_TL_PK — The composite primary key index on (CREDIT_APP_STATUS_ID, LANGUAGE).
• IBY_F_CRDT_APP_STATUS_TL_U1 — Unique index on (CREDIT_APP_STATUS_ID, LANGUAGE), reinforcing the business key.
• IBY_F_CRDT_APP_STATUS_TL_U2 — Unique index on (NAME, LANGUAGE), enforcing translation-name uniqueness.
• Payment and credit application transactional tables in the IBY schema that consume CREDIT_APP_STATUS_ID and depend on this table for localized status display.

Because the "_TL" pattern is a standard Oracle Applications construct, any form, report, OAF page, or concurrent program listing credit application statuses in a localized environment implicitly depends on this table.