Search Results cm_cldr_hdr




Overview
Explore in AI Chat

Overview

PMIFV_GL_CM_COST_COMPARISON_V is an APPS-owned database view shipped with the Process Manufacturing Intelligence (PMI) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. PMI is now marked Obsolete in the ETRM repository, but the view remains VALID in the database and continues to be referenced by legacy installations that have not fully migrated off Process Manufacturing costing analytics. As its name implies, the view is designed to present costing information drawn simultaneously from the General Ledger and from the Process Manufacturing costing tables, allowing cost accountants and report developers to reconcile GL inventory valuation against the operational cost roll-up maintained by Process Manufacturing.

The view is not an operational transaction object; it is a read-only reporting construct. Its principal role is to serve as the data source for PMI cost comparison dashboards, ad hoc reconciliations, and any custom concurrent program or OBIEE/BIP report that requires a side-by-side presentation of CM-sourced costs versus GL-sourced costs at the item, warehouse, calendar, and period grain.

Underlying Base Objects

The view is defined over the following documented base objects, all exposed to APPS through synonyms:

  • CM_CLDR_DTL (synonym) and CM_CLDR_HDR (synonym) — the Process Manufacturing costing calendar detail and header, supplying period and calendar descriptive text. This is the object most closely related to the user's search term cm_cldr_dtl; the view joins CM_CMPT_DTL.CALENDAR_CODE and PERIOD_CODE to these tables with outer joins.
  • CM_CMPT_DTL and CM_CMPT_MST (synonyms) — the CM cost component detail and master, providing the component class and per-component cost amounts used in the first branch of the union.
  • GL_ITEM_CST and GL_ITEM_DTL (synonyms) — the GL item cost tables that supply the second branch of the union, giving the General Ledger perspective on item cost.
  • IC_ITEM_MST and IC_ITEM_MST_B (synonyms) — inventory item master tables providing ITEM_NO and ITEM_ID.
  • IC_WHSE_MST (synonym) — warehouse master, outer-joined for warehouse description and organization security checks.
  • SY_ORGN_MST (synonym) and PMI_SECURITY_PKG (package) — together they enforce organization-level security, restricting returned rows to organizations for which PMI_SECURITY_PKG.SHOW_RECORD returns TRUE.

Key Columns

  • ITEM_NO — the inventory item identifier from IC_ITEM_MST.
  • WHSE_CODE — warehouse code from the CM cost component detail.
  • CALENDAR_CODE / CALENDAR_DESC — the costing calendar and its description from CM_CLDR_HDR.
  • PERIOD_CODE / PERIOD_DESC — the costing period and its description from CM_CLDR_DTL.
  • COST_MTHD_CODE — cost method; populated in the CM branch and null in the GL branch.
  • COST_CMPNTCLS_CODE — cost component class from CM_CMPT_MST.
  • COST_ANALYSIS_CODE — cost analysis code, taken from CM_CMPT_DTL in the first branch and from GL_ITEM_DTL in the second.
  • Cost amount columns — the CM branch returns SUM(COSTDETAIL.CMPNT_COST) against a zero GL amount; the GL branch returns SUM(ITEMDETAIL.CMPTCOST_AMT) against a zero CM amount. This mirrored structure is what enables side-by-side comparison.

Common Use Cases and Queries

Typical scenarios include reconciling CM cost roll-ups to GL inventory balances, validating period-close cost values, and driving cost variance dashboards. Because the view applies PMI security, results are automatically filtered to the user's authorized organizations.

A representative query comparing CM and GL amounts for a specific item and period:

  • SELECT item_no, whse_code, calendar_code, period_code, cost_cmpntcls_code, cost_analysis_code, cm_cost, gl_cost FROM apps.pmifv_gl_cm_cost_comparison_v WHERE item_no = :item AND calendar_code = :calendar AND period_code = :period ORDER BY cost_cmpntcls_code;

To aggregate the comparison across all components:

  • SELECT item_no, calendar_code, period_code, SUM(cm_cost) total_cm, SUM(gl_cost) total_gl, SUM(cm_cost) - SUM(gl_cost) variance FROM apps.pmifv_gl_cm_cost_comparison_v GROUP BY item_no, calendar_code, period_code HAVING SUM(cm_cost) - SUM(gl_cost) <> 0;

Because PMI is obsolete, new development should target supported costing views; however, existing dependencies on PMIFV_GL_CM_COST_COMPARISON_V remain functional in both 12.1.1 and 12.2.2.