Results for “layer_quantity”

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

Overview

MTL_CST_LAYER_ACT_COST_DETAILS is an Inventory (INV) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores actual cost information broken out by cost element and by level. It is a cost-layer detail table: whereas the parent cost layer records define the monetary and quantity basis of an inventory valuation layer, this table decomposes that layer into its constituent cost elements and the level at which each element was incurred. It is therefore central to periodic and perpetual costing, cost-rollup analysis, and variance reporting where element-level granularity is required.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. In Data Vault modeling terms this suggests the object behaves more like a self-contained structure than a classic hub, link, or satellite, because the documented relationship data does not expose conventional parent-child FK wiring within the metadata. Modelers designing a warehouse layer around EBS costing data should treat this as a modeling suggestion only and validate it against the live constraint definitions in their instance.

The table is owned by the INV schema, is marked VALID, and is documented with 23 columns in ETRM 12.2.2. Oracle classifies the underlying documentation as proprietary and confidential.

Key Information Stored

The primary key is the constraint MTL_CST_LAYER_ACT_CST_DTLS_PK, defined over six columns: TRANSACTION_ID, ORGANIZATION_ID, LAYER_ID, INV_LAYER_ID, COST_ELEMENT_ID, and LEVEL_TYPE. These six columns are business-meaningful rather than surrogate; there is no generated sequence-based surrogate key. A unique index, MTL_CST_LAYER_ACT_CST_DTLS_U1, enforces the identical column list, confirming that the composite constitutes both the relational key and the natural business key.

The most significant columns are:

• TRANSACTION_ID — identifies the inventory transaction that generated the cost layer entry; part of the primary key.
• ORGANIZATION_ID — the inventory organization owning the layer; part of the primary key and the principal partitioning dimension in multi-org reporting.
• LAYER_ID — the cost layer to which the detail belongs; part of the primary key.
• INV_LAYER_ID — the inventory-side layer identifier, paired with LAYER_ID in the key.
• COST_ELEMENT_ID — the cost element (material, material overhead, resource, overhead, outside processing) being detailed; part of the key.
• LEVEL_TYPE — the level at which the cost was incurred (for example this-level versus previous-level); part of the key and the column that gives the table its "by level" character.
• LAYER_QUANTITY — the quantity associated with the layer detail.
• ACTUAL_COST — the actual cost amount recorded for the element and level combination.
• LAYER_COST — the cost attributed to the layer itself.
• INVENTORY_ITEM_ID — the item being costed.
• VARIANCE_AMOUNT, PAYBACK_VARIANCE_AMOUNT, ONHAND_VARIANCE_AMOUNT — the variance components tracked against the layer, supporting cost adjustment and reconciliation analysis.
• USER_ENTERED — indicates whether the cost detail was manually entered rather than system-generated.

The table also carries the standard EBS audit and concurrent-program columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical uses include cost-element drill-down for a valuation layer, period-end variance analysis, reconciliation between inventory and general ledger cost figures, and cost rollup validation for manufactured items.

A representative query retrieves element-level detail for a given layer and organization:

• SELECT transaction_id, layer_id, inv_layer_id, cost_element_id, level_type, actual_cost, layer_cost, layer_quantity FROM mtl_cst_layer_act_cost_details WHERE organization_id = :org_id AND layer_id = :layer_id ORDER BY cost_element_id, level_type;
• Aggregation by element for variance reporting: SELECT cost_element_id, SUM(actual_cost) actual_cost, SUM(variance_amount) variance_amount FROM mtl_cst_layer_act_cost_details WHERE organization_id = :org_id AND inventory_item_id = :item_id GROUP BY cost_element_id;
• Traceback to the originating transaction: join on TRANSACTION_ID and ORGANIZATION_ID to MTL_MATERIAL_TRANSACTIONS.
• Audit and provenance checks using REQUEST_ID and PROGRAM_ID to identify the costing process that populated the rows.

Related Objects

The documented metadata flags the object as standalone, so no FK relationships are asserted within ETRM. The following joins are the practical ones used in EBS costing and inventory reporting, keyed on the columns present in the composite key:

• MTL_CST_LAYERS or the corresponding cost-layer header — joined on LAYER_ID and ORGANIZATION_ID to obtain layer-level totals and layer dates.
• MTL_MATERIAL_TRANSACTIONS — joined on TRANSACTION_ID and ORGANIZATION_ID to resolve the source inventory transaction.
• MTL_SYSTEM_ITEMS_B — joined on INVENTORY_ITEM_ID and ORGANIZATION_ID for item descriptions and attributes.
• CST_COST_ELEMENTS (or the cost element reference table) — joined on COST_ELEMENT_ID to resolve element names.
• MTL_PARAMETERS — joined on ORGANIZATION_ID to resolve organization context and costing method.
• CST_LAYER_COST_DETAILS and related CST layer-cost detail tables — used together when comparing actual versus standard or frozen layer cost.
• GL_IMPORT_REFERENCES — used to reconcile layer cost and variance amounts to general ledger entries.