Search Results cst_inv_layers_pk

Overview

CST_INV_LAYERS is a cost management table owned by the BOM schema in Oracle E-Business Suite 12.1.1 and 12.2.2. As its description states, it stores layer information — specifically, the individual incremental cost layers that accumulate against inventory items within an organization. It is a foundational object in the Oracle Cost Management subledger, where it supports the layer-based cost accumulation model used for perpetual inventory valuation, periodic costing, and margin analysis.

Each row in CST_INV_LAYERS represents a distinct cost layer associated with a parent quantity layer. This design allows Oracle to track the quantity and unit cost contributed by each receipt, adjustment, or transaction, enabling accurate valuation on a first-in-first-out (FIFO) or average cost basis depending on the organization's costing method. The table is classified heuristically as standalone in the Data Vault sense, meaning it functions as an independent table in the mined FK graph rather than as a classic hub, link, or satellite. In Data Vault modeling terms, this suggests it behaves as a standalone entity rather than fitting neatly into hub/link/satellite constructs, and implementers may choose to model it as an independent satellite or reference table when building downstream analytics.

Key Information Stored

CST_INV_LAYERS contains 23 documented columns. The most significant include:

• INV_LAYER_ID — The surrogate primary key (CST_INV_LAYERS_PK), uniquely identifying each inventory cost layer record.
• LAYER_ID — Foreign key referencing CST_QUANTITY_LAYERS; ties the cost layer to its parent quantity layer. Part of the composite unique index CST_INV_LAYERS_U2 (LAYER_ID, INV_LAYER_ID), which serves as a business-key candidate.
• ORGANIZATION_ID — Identifies the inventory organization in which the layer resides.
• INVENTORY_ITEM_ID — The item to which the cost layer belongs.
• CREATION_QUANTITY and LAYER_QUANTITY — The quantity originally created for the layer and the remaining (or current) layer quantity, respectively.
• LAYER_COST — The unit cost associated with the layer.
• CREATE_TRANSACTION_ID — The inventory transaction that generated the layer.
• TRANSACTION_ACTION_ID and TRANSACTION_SOURCE_TYPE_ID — Describe the transaction action and source; TRANSACTION_SOURCE_TYPE_ID is a foreign key to MTL_TXN_SOURCE_TYPES.
• TRANSACTION_SOURCE_ID, TRANSACTION_SOURCE — Identify the originating document or source of the layer.
• UNBURDENED_COST and BURDEN_COST — Hold the cost components before and after burden application, supporting landed-cost and overhead analysis.

The audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the concurrent program columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) are also present, enabling standard EBS audit and diagnostics reporting. Note that CST_INV_LAYERS_U1 is a unique index on INV_LAYER_ID, confirming it as the surrogate key; LAYER_ID and INV_LAYER_ID together form the composite business key candidate.

Common Use Cases and Queries

Cost accountants and developers query CST_INV_LAYERS to reconcile layer balances, diagnose valuation discrepancies, and report on cost accumulation. A typical query joins to CST_QUANTITY_LAYERS to obtain the parent quantity context:

SELECT l.INV_LAYER_ID, l.LAYER_ID, l.ORGANIZATION_ID, l.INVENTORY_ITEM_ID,
       l.CREATION_QUANTITY, l.LAYER_QUANTITY, l.LAYER_COST,
       l.UNBURDENED_COST, l.BURDEN_COST
FROM   BOM.CST_INV_LAYERS l
WHERE  l.ORGANIZATION_ID = :org_id
AND    l.INVENTORY_ITEM_ID = :item_id
ORDER BY l.CREATION_DATE;

Other common scenarios include: tracing a layer back to its originating transaction using CREATE_TRANSACTION_ID; analyzing burden versus unburdened cost for landed-cost reporting; and reconciling quantity layers against inventory transaction history. Reporting use cases include FIFO layer aging reports, cost variance analysis, and period-end valuation extracts feeding GL.

Related Objects

The following objects are most significant to CST_INV_LAYERS based on documented relationships:

• CST_QUANTITY_LAYERS — Parent layer table; joined via CST_INV_LAYERS.LAYER_ID = CST_QUANTITY_LAYERS.LAYER_ID.
• MTL_TXN_SOURCE_TYPES — Reference table for transaction sources; joined via TRANSACTION_SOURCE_TYPE_ID.
• MTL_TRANSACTIONS — Source of originating inventory transactions (via CREATE_TRANSACTION_ID).
• MTL_SYSTEM_ITEMS_B — Item definition for INVENTORY_ITEM_ID.
• CST_ITEM_COSTS — Item cost master used to validate layer cost values.
• MTL_PARAMETERS / ORG_ORGANIZATION_DEFINITIONS — Organization context for ORGANIZATION_ID.

These relationships make CST_INV_LAYERS a central point for cost layer reconciliation and valuation reporting in Oracle Cost Management.