Results for “cm_whse_eff”

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

Overview

CM_WHSE_EFF is the Costing Warehouse Effectivities table owned by the GMF schema (Process Manufacturing Financials) in Oracle EBS 12.1.1 and 12.2.2. It records the period-by-period effectivity of costing warehouse assignments, determining which warehouse, organization, calendar period, and item cost class combination participates in the Cost Rollup Process. Each row essentially states that a given item belongs to a specific cost class within a specific costing organization and period, driving how costs are rolled up and applied across the process manufacturing inventory.

From a Data Vault modeling perspective, the mined foreign key structure suggests classification as a link — the table sits at the intersection of independent business entities (item, cost class, warehouse, calendar period, organization) and records the relationship among them rather than describing a single entity's attributes.

Key Information Stored

The 17 documented columns center on effectivity keys and audit metadata. The most important include:

• TRGT_WHSE_ID — surrogate primary key (CM_WHSE_EFF_PK); identifies the effectivity record itself.
• ORGN_CODE — operating organization; part of the business key and FK to SY_ORGN_MST / SY_ORGN_MST_B.
• CALENDAR_CODE, PERIOD_CODE — define the effectivity window; both participate in CM_WHSE_EFF_U1 and reference CM_CLDR_DTL.
• ITEMCOST_CLASS — the cost class assigned to the item; FK to IC_COST_CLS and a business-key element. This is the column most often queried by users searching "itemcost_class".
• ITEM_ID — the item being costed; FK to IC_ITEM_MST and IC_ITEM_MST_B, and part of the unique index.
• COSTING_WHSE — the costing warehouse; FK to IC_WHSE_MST.
• COST_CATEGORY_ID, PERIOD_ID — surrogate references to cost category and period definitions.
• TEXT_CODE — FK to CM_TEXT_HDR for descriptive text.
• TRANS_CNT — transaction count, typically supporting concurrency or change tracking.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, DELETE_MARK — standard audit and logical-deletion columns.

The unique index CM_WHSE_EFF_U1 (ORGN_CODE, CALENDAR_CODE, PERIOD_CODE, ITEMCOST_CLASS, ITEM_ID) is the business-key candidate; TRGT_WHSE_ID is the surrogate PK.

Common Use Cases and Queries

Typical uses include cost rollup validation, cost class reporting, and troubleshooting missing or duplicate effectivity rows. Because ITEMCOST_CLASS is central, analysts frequently join to IC_COST_CLS to resolve class descriptions.

• Listing effectivities for a given item and cost class within a period.
• Auditing warehouse/organization effectivity coverage before running cost rollup.
• Reconciling cost class assignments across periods.

Sample pattern:

SELECT w.ORGN_CODE, w.ITEM_ID, w.ITEMCOST_CLASS, w.COSTING_WHSE, w.PERIOD_CODE
FROM GMF.CM_WHSE_EFF w, GMF.IC_COST_CLS c
WHERE w.ITEMCOST_CLASS = c.COST_CLASS
AND w.DELETE_MARK = 0
AND w.PERIOD_CODE = :period;

Related Objects

The documented FKs identify the principal dependencies:

• IC_ITEM_MST / IC_ITEM_MST_B — via ITEM_ID.
• IC_COST_CLS — via ITEMCOST_CLASS.
• IC_WHSE_MST — via COSTING_WHSE.
• CM_CLDR_DTL — via CALENDAR_CODE and PERIOD_CODE.
• SY_ORGN_MST / SY_ORGN_MST_B — via ORGN_CODE.
• CM_TEXT_HDR — via TEXT_CODE.

These relationships anchor CM_WHSE_EFF within the GMF costing model and make it a key link between item costing, warehouse, and calendar data.