Results for “source_lang”

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

Overview

PRP_COMPONENT_STYLES_TL is the translation (TL) table for component styles within the Oracle EBS Proposals (PRP) module. In Oracle EBS 12.1.1 and 12.2.2, the Proposals module supports the definition and reuse of proposal components, and each component may be associated with a named style that controls its presentation or behavior. PRP_COMPONENT_STYLES_TL stores the language-dependent, translated attributes of those styles, while the corresponding base table, PRP_COMPONENT_STYLES_B, holds the language-independent definition and the master surrogate key.

The table resides in the PRP schema and is owned by the Proposals product. It carries a composite primary key, PRP_COMPONENT_STYLES_TL_PK, defined on (COMPONENT_STYLE_ID, LANGUAGE), and a unique index, PRP_COMPONENT_STYLES_TL_U1, on the same column pair. The single foreign key relationship, PRP_COMPONENT_STYLES_TL.COMPONENT_STYLE_ID → PRP_COMPONENT_STYLES_B, confirms that this table is a dependent child of the base table.

From a Data Vault modeling perspective, this object is classified heuristically as satellite-leaning. It captures descriptive, language-specific context keyed to a parent entity, rather than introducing new independent business entities (hubs) or associations (links). This classification is offered as a modeling suggestion; in the Oracle EBS operational schema, the table functions as a standard translated descriptor child of PRP_COMPONENT_STYLES_B.

Key Information Stored

The documented physical schema contains nine columns. The most significant are:

• COMPONENT_STYLE_ID — Surrogate foreign key to the base table PRP_COMPONENT_STYLES_B. Together with LANGUAGE it forms the composite primary key and the unique business-key candidate defined by PRP_COMPONENT_STYLES_TL_U1.
• LANGUAGE — The language code identifying the translation row. Also part of the composite primary key and unique index.
• SOURCE_LANG — Indicates the source language from which the translation was derived, supporting multilingual maintenance.
• COMPONENT_STYLE_NAME — The translated, user-visible name of the component style; the principal descriptive attribute exposed to end users.
• CREATED_BY, CREATION_DATE — Standard EBS audit columns recording the creating user and creation timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard audit columns recording the most recent updater and update timestamp.
• LAST_UPDATE_LOGIN — The login identifier associated with the last update, used for auditing and concurrent-program tracking.

The surrogate primary key (COMPONENT_STYLE_ID, LANGUAGE) should be distinguished from the business-key candidate captured by the unique index PRP_COMPONENT_STYLES_TL_U1, which enforces one translation row per style per language.

Common Use Cases and Queries

Typical scenarios involve retrieving localized style names for display or reporting, and joining translated attributes back to the base definition. A representative query joining the translation to its base table is:

• SELECT b.component_style_id, t.language, t.component_style_name
• FROM prp.prp_component_styles_b b, prp.prp_component_styles_tl t
• WHERE b.component_style_id = t.component_style_id
• AND t.language = 'US';

Reporting use cases include multilingual style listings, translation completeness checks (identifying styles lacking a row for a given LANGUAGE), and auditing of translation currency via LAST_UPDATE_DATE and SOURCE_LANG. Because the table is keyed by COMPONENT_STYLE_ID and LANGUAGE, queries should always constrain LANGUAGE to avoid returning every translation of a style.

Related Objects

The following objects are most relevant to PRP_COMPONENT_STYLES_TL:

• PRP_COMPONENT_STYLES_B — Parent base table; joined on COMPONENT_STYLE_ID via the documented foreign key.
• PRP_COMPONENT_STYLES_TL_PK — Primary key constraint on (COMPONENT_STYLE_ID, LANGUAGE).
• PRP_COMPONENT_STYLES_TL_U1 — Unique index enforcing one translated row per style per language.
• PRP component definition tables — Components that reference component styles through the base table, enabling style-driven rendering of proposal content.
• FND_LANGUAGES — Reference for valid LANGUAGE and SOURCE_LANG values used in translation lookups.