Results for “cm_cldr_dtl”

50+ results




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

Overview

CM_CLDR_DTL is the Costing Calendar Details table within the Process Manufacturing Financials (GMF) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It defines the individual accounting periods that make up a costing calendar, acting as the granular control point for period-level costing, cost rollup, burdening, and adjustment activity in process manufacturing environments. Where the costing calendar header establishes the calendar itself, CM_CLDR_DTL establishes each period within that calendar, including its date boundaries and processing status.

The table is owned by the GMF schema and is documented as VALID in ETRM 12.2.2. Its physical schema comprises 18 columns. The primary key, CM_CLDR_DTL_PK, is a composite of CALENDAR_CODE and PERIOD_CODE, which also serves as the documented unique business-key candidate.

From a Data Vault modeling perspective, the FK topology suggests a hub-leaning classification. The table carries a natural composite business key (CALENDAR_CODE, PERIOD_CODE), is referenced by a broad set of dependent transactional tables, and itself references header and text master tables — behavior consistent with a hub that anchors period-level references across the costing subsystem.

Key Information Stored

The composite primary key (CALENDAR_CODE, PERIOD_CODE) is the surrogate uniqueness construct; CALENDAR_CODE additionally functions as a foreign key into the calendar header tables, so it is both a key component and a referential link.

Common Use Cases and Queries

CM_CLDR_DTL supports period validation, period-status reporting, and joins that resolve transaction rows to their calendar periods. A typical query lists the periods of a costing calendar with status:

  • SELECT period_code, period_desc, start_date, end_date, period_status FROM cm_cldr_dtl WHERE calendar_code = :calendar_code AND delete_mark = 0;

A frequent operational pattern joins dependent costing details back to this table on both key columns, for example:

  • SELECT a.*, d.period_status FROM cm_acst_led a JOIN cm_cldr_dtl d ON a.calendar_code = d.calendar_code AND a.period_code = d.period_code;

Reporting use cases include displaying the valid periods of a calendar, identifying open versus closed periods, and reconciling costing ledgers, burdens, and rollups to specific periods. Because many dependent tables reference this table, filtering by PERIOD_STATUS is a common way to restrict downstream reports to open periods.

Related Objects

  • CM_CLDR_HDR and CM_CLDR_HDR_B — Calendar header tables joined on CALENDAR_CODE.
  • CM_TEXT_HDR — Text master joined on TEXT_CODE.
  • CM_ACST_LED — Actual cost ledger, joined on CALENDAR_CODE and PERIOD_CODE.
  • CM_ALPR_CTL and CM_RLUP_CTL — Allocation and rollup control tables referencing CALENDAR_CODE and PERIOD_CODE.
  • CM_ADJS_DTL — Adjustment details tied to calendar and period.
  • CM_CMPT_DTL, CM_RSRC_DTL, and CM_BRDN_DTL — Component, resource, and burden detail tables.
  • CM_CUPD_CTL — Cost update control referencing the calendar period.
  • CM_WHSE_EFF and CM_WHSE_SRC — Warehouse effectivity and source tables.
  • GL_ITEM_CST and GL_ALOC_INP — General Ledger item cost and allocation input tables.
  • GL_PLCY_MST and GMF_BURDEN_PERCENTAGES — Policy master and burden percentage tables referencing calendar and period.