Results for “cst_item_costs_for_gl_view”

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

Overview

CST_ITEM_COSTS_FOR_GL_VIEW is a single-organization view owned by the APPS schema in Oracle E-Business Suite, catalogued under the BOM (Bills of Material) product family and the Cost Management module. Its documented purpose is to expose item costs selected according to the organization's costing method — that is, the costs associated with the cost type designated as the primary cost method for a given inventory organization. It is typically used as a reporting and integration source, particularly for feeds that supply item cost information to General Ledger, hence the "_FOR_GL_" naming convention.

The view is defined as a join between MTL_PARAMETERS and CST_ITEM_COSTS, filtered so that only records whose COST_TYPE_ID matches the organization's PRIMARY_COST_METHOD are returned, and only for the organization whose COST_ORGANIZATION_ID is referenced. All cost amount columns are wrapped in NVL(…,0), so consumers receive zero rather than NULL for absent cost elements. This makes the view safe for aggregation and for downstream GL interfaces that require numeric values.

The view is VALID and documented in ETRM for both 12.1.1 and 12.2.2; the underlying base objects are referenced through synonyms (CST_ITEM_COSTS and MTL_PARAMETERS) pointing to the Cost Management and Inventory schemas respectively.

Underlying Base Objects

The view is defined over two documented base objects:

• CST_ITEM_COSTS (SYNONYM) — the primary cost detail table, holding per-item, per-cost-type cost elements and rolled-up amounts. This is the driving table in the query (aliased CIC).
• MTL_PARAMETERS (SYNONYM) — the inventory organization parameters table (aliased MP), which supplies COST_ORGANIZATION_ID and PRIMARY_COST_METHOD.

The join predicate is CIC.ORGANIZATION_ID = MP.COST_ORGANIZATION_ID AND CIC.COST_TYPE_ID = MP.PRIMARY_COST_METHOD. This effectively restricts rows to the cost type that the organization treats as its primary costing method (Standard, Average, FIFO, LIFO, etc.), and maps the cost organization to the corresponding inventory organization. Because the filter is driven by MTL_PARAMETERS, the view returns at most one cost type per organization, presenting a single canonical cost picture per item.

Key Columns

The view exposes item identity, cost-type context, and a wide set of cost elements and totals. Notable columns include:

• INVENTORY_ITEM_ID, ORGANIZATION_ID — the item and the inventory organization (from the cost organization mapping).
• INVENTORY_ASSET_FLAG — indicates whether the item is asset-tracked; significant for capitalization in GL.
• COST_UPDATE_ID — the cost update that produced the record, enabling traceability to a specific cost roll-up or update.
• Element costs: MATERIAL_COST, MATERIAL_OVERHEAD_COST, RESOURCE_COST, OUTSIDE_PROCESSING_COST, OVERHEAD_COST — the five cost elements.
• Prior-level and this-level variants: PL_MATERIAL, PL_MATERIAL_OVERHEAD, PL_RESOURCE, PL_OUTSIDE_PROCESSING, PL_OVERHEAD, and the corresponding TL_ columns, plus PL_ITEM_COST and TL_ITEM_COST.
• ITEM_COST — the total item cost (NVL-wrapped).
• UNBURDENED_COST and BURDEN_COST — unbundled and burdened views of cost, useful where overhead burden applies.
• LOT_SIZE, SHRINKAGE_RATE, BASED_ON_ROLLUP_FLAG, DEFAULTED_FLAG — cost computation attributes.
• ATTRIBUTE1…ATTRIBUTE15 — descriptive flexfield columns carried through from CST_ITEM_COSTS for extensibility.

Common Use Cases and Queries

Typical applications include general ledger cost feeds, inventory valuation reports, margin and standard-cost analysis, and reconciliation of item costs across organizations. Because the view resolves the primary cost method automatically, it is convenient for cross-organization reporting where the costing method varies.

Example — list primary-method costs for an organization:

• SELECT inventory_item_id, organization_id, item_cost, material_cost, resource_cost, overhead_cost FROM apps.cst_item_costs_for_gl_view WHERE organization_id = :org_id;

Example — retrieve asset-tracked items and their total cost:

• SELECT inventory_item_id, item_cost, burden_cost FROM apps.cst_item_costs_for_gl_view WHERE organization_id = :org_id AND inventory_asset_flag = 'Y';

Example — aggregate total cost across all organizations in the view:

• SELECT organization_id, SUM(item_cost) total_cost FROM apps.cst_item_costs_for_gl_view GROUP BY organization_id ORDER BY organization_id;

When joining to master item or GL mapping tables, use INVENTORY_ITEM_ID and ORGANIZATION_ID as the keys. Note that, being a single-org view, callers must filter or join by ORGANIZATION_ID explicitly to avoid unintentionally mixing organizations.