Results for “gl_item_cst”

50+ results




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

Overview

GL_ITEM_CST is a transactional cost table owned by the GMF schema (Process Manufacturing Financials) in Oracle EBS 12.1.1 and 12.2.2. It stores item costs for transactions, maintaining both accounting costs and current costs at the organization, warehouse, and item level. Component-level cost breakdowns are held separately in GL_ITEM_DTL, making GL_ITEM_CST the header record for each cost transaction, with detail lines attached through the ITEMCOST_ID key.

The table carries 28 documented columns and is uniquely identified by the primary key GL_ITEM_CST_PK on ITEMCOST_ID. A second unique index, GL_ITEM_CST_U1, covers ORGN_CODE, WHSE_CODE, ITEM_ID, COST_MTHD_CODE, and END_DATE, functioning as the business-key candidate that defines the effective-dated uniqueness of a cost record. The status is VALID in the ETRM repository. Heuristically, the FK structure classifies this object as satellite-leaning within a Data Vault model, given its dependence on multiple hub-style reference tables (organization, warehouse, item, cost method) and its effective-dated, descriptive cost attributes.

Because GL_ITEM_CST exists in the GMF schema, it is typically accessed through Process Manufacturing Financials, Cost Management, and related inventory costing flows rather than through standard Oracle Financials tables.

Key Information Stored

The most operationally significant columns include:

  • ITEMCOST_ID — surrogate primary key and the join key to all child detail tables.
  • ORGN_CODE and WHSE_CODE — organization and warehouse context for the cost record.
  • ITEM_ID — the inventory item to which the cost applies.
  • COST_MTHD_CODE — cost method used to derive the value (joins to CM_MTHD_MST).
  • COST_TYPE and COST_TYPE_ID — classification of the cost component being stored.
  • ACCTG_COST — the accounting cost amount recorded for the transaction.
  • START_DATE and END_DATE — effective dating that determines which row is current for a given item/warehouse combination; END_DATE is part of the GL_ITEM_CST_U1 unique index.
  • CALENDAR_CODE and PERIOD_CODE — the cost period context (joins to CM_CLDR_DTL).
  • FMEFF_ID — formula effectivity reference linking the cost to a process formula version.
  • FINAL_FLAG — indicates whether the cost record is final for the period.
  • TRANS_CNT — transaction count accumulated against the cost record.
  • DELETE_MARK — logical deletion indicator.
  • REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, and the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — concurrent program and audit tracking.

Common Use Cases and Queries

Typical applications include cost rollup verification, period-end cost reporting, and reconciliation of accounting to current cost. A common pattern retrieves the current cost row by filtering on the unique-index columns and open effective dating:

  • SELECT ITEMCOST_ID, ORGN_CODE, WHSE_CODE, ITEM_ID, COST_MTHD_CODE, ACCTG_COST, START_DATE, END_DATE FROM GMF.GL_ITEM_CST WHERE ORGN_CODE = :orgn AND WHSE_CODE = :whse AND ITEM_ID = :item AND SYSDATE BETWEEN START_DATE AND NVL(END_DATE, SYSDATE);

Cost analysts join GL_ITEM_DTL on ITEMCOST_ID to obtain component-level cost detail, while period comparisons join to CM_CLDR_DTL through CALENDAR_CODE and PERIOD_CODE. Reporting extracts frequently aggregate ACCTG_COST by ORGN_CODE and PERIOD_CODE, or track TRANS_CNT to identify high-volume cost records. Because rows are effective-dated, any point-in-time query must constrain START_DATE and END_DATE to avoid returning historical and current versions simultaneously.

Related Objects

The following objects are most significant to GL_ITEM_CST through foreign-key relationships:

  • GL_ITEM_DTL — child table; joins via GL_ITEM_DTL.ITEMCOST_ID → GL_ITEM_CST.ITEMCOST_ID, supplying component cost detail.
  • GL_ITEM_CST_EFC and GL_ITEM_DTL_EFC — EFC (Enterprise Financials Consolidation) companion objects referencing ITEMCOST_ID.
  • IC_ITEM_MST and IC_ITEM_MST_B — item master tables; GL_ITEM_CST.ITEM_ID references both.
  • IC_WHSE_MST — warehouse master; join on WHSE_CODE.
  • SY_ORGN_MST and SY_ORGN_MST_B — organization masters; join on ORGN_CODE.
  • CM_MTHD_MST — cost method master; join on COST_MTHD_CODE.
  • CM_CLDR_DTL — cost calendar detail; join on CALENDAR_CODE and PERIOD_CODE.
  • FM_FORM_EFF — formula effectivity; join on FMEFF_ID.
  • CST_COST_TYPES — cost type reference; join on COST_TYPE_ID.