Results for “cm_cldr_hdr_tl”

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

Overview

CM_CLDR_HDR_TL is the translation table for the Cost Calendar Header entity within the GMF – Process Manufacturing Financials module of Oracle E-Business Suite. In Oracle EBS, "_TL" suffixed tables store the language-specific, translatable descriptive attributes of a base ("_B") or header table. In this case, CM_CLDR_HDR_TL holds the translated columns of the Cost Calendar Header Table, allowing the calendar description to be presented in multiple installed languages. The table resides in the GMF schema and is documented as VALID in both 12.1.1 and 12.2.2.

From a heuristic Data Vault modeling perspective, this object is best classified as a satellite. It carries descriptive, language-dependent attributes (notably the calendar description) that are functionally dependent on the parent Cost Calendar Header business key, and it changes over time as translations are added or amended. It is documented as "standalone" in the FK structure, meaning the mined relationship data reveals no enforced foreign-key dependencies, though logically it participates in a parent-child relationship with the Cost Calendar Header business entity.

Key Information Stored

The documented physical schema contains 9 columns. The most significant are summarized below.

• CALENDAR_CODE – The business identifier of the cost calendar. Together with LANGUAGE it forms the composite primary key and the business-key candidate.
• LANGUAGE – The installed language code for the translated row. Also part of the composite primary key.
• SOURCE_LANG – The source language from which the translation originates, used by the EBS translation framework (e.g., the Translate-and-Submit / language merge utilities) to track the original language record.
• CALENDAR_DESC – The translated calendar description, the primary user-facing translated attribute of the Cost Calendar Header.
• CREATION_DATE, CREATED_BY – Standard who-columns recording when and by whom the row was inserted.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Standard audit columns recording when, by whom, and through which login session the row was last modified.

The surrogate/primary key is the composite CM_CLDR_HDR_TL_PK (CALENDAR_CODE, LANGUAGE). There is no separate single-column surrogate; the primary key itself doubles as the unique business-key candidate, since the combination of calendar code plus language uniquely identifies a translated description. CALENDAR_CODE is the logical linkage back to the untranslated Cost Calendar Header, while LANGUAGE distinguishes the translated rows.

Common Use Cases and Queries

The principal use of CM_CLDR_HDR_TL is to retrieve the correct-language description of a cost calendar for display and reporting. A typical query joins the translated row on the calendar code and the session/installed language:

• Multi-language description lookup: SELECT calendar_code, calendar_desc FROM cm_cldr_hdr_tl WHERE language = USERENV('LANG');
• Translation completeness reporting: identifying calendars that lack a row for a given LANGUAGE, or whose SOURCE_LANG indicates an untranslated source.
• Audit/change tracking: using LAST_UPDATE_DATE and LAST_UPDATED_BY to report on when descriptions were last refreshed during a language merge.

Because translation tables are populated and maintained through the standard EBS translation utilities, direct DML is discouraged. Reporting layers and concurrent programs that display calendar captions will generally resolve the description through this table rather than the base header.

Related Objects

The following objects are most significant in relation to CM_CLDR_HDR_TL. Note that the mined data vault classification reports this object as standalone, so the relationships below are logical rather than enforced by documented foreign keys.

• CM_CLDR_HDR_B / Cost Calendar Header table (GMF) – The base/header entity whose translatable columns CM_CLDR_HDR_TL mirrors, joined on CALENDAR_CODE.
• CM_CLDR_HDR_TL_PK – The unique index (CALENDAR_CODE, LANGUAGE) enforcing translation uniqueness.
• Translation framework tables/APIs – EBS language merge and Translate-and-Submit processes that populate SOURCE_LANG and the translated rows.
• Cost Calendar detail tables – Dependent calendar structure objects keyed indirectly through the calendar code.
• FND_LANGUAGES – Provides the valid values for LANGUAGE and SOURCE_LANG.

Together these objects allow the GMF costing calendar to be presented consistently across language installations while preserving a single authoritative business key.