Results for “cm_cldr_hdr_vl”

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

Overview

CM_CLDR_HDR_VL is a language-resolved (VL) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GMF – Process Manufacturing Financials product. It presents Cost Calendar Header data together with the translated calendar description, resolving the description text to the session language through the USERENV('LANG') mechanism. The view is defined with status VALID in both Oracle EBS 12.1.1 and 12.2.2, and it functions as the reporting and integration facing layer over the cost calendar header entity, shielding consumers from the need to join the base and translation tables manually.

For users searching on the term "in_use," the relevant fact is that IN_USE is one of the columns explicitly selected and exposed by this view. It is inherited directly from the base table CM_CLDR_HDR_B and appears in the view text immediately before TEXT_CODE. This makes CM_CLDR_HDR_VL a legitimate access point for querying the in-use status of a cost calendar header alongside its translated description.

Underlying Base Objects

The documented referenced base objects are CM_CLDR_HDR_B (SYNONYM) and CM_CLDR_HDR_TL (SYNONYM). These correspond to the standard EBS multi-language architecture pattern of a "_B" base table holding language-independent attributes and a "_TL" translation table holding language-dependent descriptions.

• CM_CLDR_HDR_B — the base Cost Calendar Header table. All non-translated columns (CALENDAR_CODE, CO_CODE, COST_MTHD_CODE, START_DATE, FISCAL_IND, IN_USE, DELETE_MARK, TEXT_CODE, the audit columns, and ATTRIBUTE1 through ATTRIBUTE30) are drawn from this table alias B.
• CM_CLDR_HDR_TL — the translation table, alias T, contributing the CALENDAR_DESC column. It is joined to the base table on CALENDAR_CODE with the additional predicate T.LANGUAGE = USERENV('LANG').
• ROW_ID — surfaced as B.ROWID, exposing the physical row identifier of the base table record.

The view therefore performs a single equi-join between CM_CLDR_HDR_B and CM_CLDR_HDR_TL, filtered to the caller's language environment, and projects the full base header attribute set plus the resolved description.

Key Columns

• CALENDAR_CODE — primary identifying key of the cost calendar header and the join key to the translation table.
• CALENDAR_DESC — language-resolved description from CM_CLDR_HDR_TL, the principal reason to use this view rather than the base table.
• IN_USE — the column most relevant to the search term; carried from the base table and indicating whether the calendar header record is currently in use.
• CO_CODE — company/organization code associated with the calendar.
• COST_MTHD_CODE — the costing method code attached to the calendar.
• START_DATE — effective start date of the calendar.
• FISCAL_IND — fiscal indicator for the calendar.
• DELETE_MARK — soft-delete flag; typically 0 for active rows.
• TEXT_CODE — text reference code carried from the base table.
• ATTRIBUTE1–ATTRIBUTE30 — the standard EBS descriptive flexfield (DFF) attribute columns.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns inherited from the base table.

Common Use Cases and Queries

The view is typically used to report cost calendar headers with human-readable descriptions and to filter by usage or deletion status. A common scenario is locating active, in-use cost calendars for a given costing method:

• Listing all language-resolved cost calendars: SELECT calendar_code, calendar_desc, co_code, cost_mthd_code, start_date FROM cm_cldr_hdr_vl ORDER BY calendar_code;
• Filtering on the in-use flag: SELECT calendar_code, calendar_desc, in_use FROM cm_cldr_hdr_vl WHERE in_use = 1;
• Excluding soft-deleted records: SELECT calendar_code, calendar_desc FROM cm_cldr_hdr_vl WHERE delete_mark = 0 AND in_use = 1;
• Joining to downstream costing objects by CALENDAR_CODE while benefiting from the translated description, avoiding a manual join to CM_CLDR_HDR_TL.

Because the view already enforces the language predicate, integration and reporting code can consume CALENDAR_DESC without replicating the translation join logic.