Results for “level_type_dsp”

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

Overview

The APPS.MTL_CST_TXN_COST_DETAILS_V view is a cost management reporting object within the Oracle E-Business Suite Inventory (INV) module. It exposes detailed transaction-level costing information drawn from the transaction cost detail tables maintained by the Cost Management subsystem, and is defined in the APPS schema with a status of VALID. The view is available in both Oracle EBS 12.1.1 and 12.2.2 environments and is owned by the APPS schema.

The primary purpose of this view is to surface, in a report-friendly form, the per-cost-element impact of inventory and manufacturing transactions. For each transaction the view decomposes the cost effect across cost elements, providing the transaction cost, the resulting new average cost, the absolute value change, and the percentage change attributable to each element. It plays a supporting role in cost analysis reporting, cost adjustment investigations, and integration scenarios where external systems require normalized transaction costing data.

Underlying Base Objects

The view is defined over three documented base objects:

• MTL_CST_TXN_COST_DETAILS (accessed via a SYNONYM) — the central fact source supplying transaction identifiers, item and organization context, level type, transaction cost, new average cost, percentage change, and value change.
• CST_COST_ELEMENTS (accessed via a SYNONYM) — supplies the cost element name, joined on COST_ELEMENT_ID.
• MFG_LOOKUPS (a VIEW) — supplies the decoded meaning for the level type, joined where LOOKUP_CODE equals the level type and LOOKUP_TYPE equals 'CST_LEVEL'.

The join structure is an inner join across all three objects. Because MFG_LOOKUPS and the cost detail source must both match, rows lacking a valid cost element or a recognized CST_LEVEL lookup code will not appear in the result set. The view carries the ROWID of the underlying MTL_CST_TXN_COST_DETAILS row, preserving a link back to the base table for drill-down or update-through-view scenarios.

Key Columns

• ROW_ID / TRANSACTION_ID — The base row identifier and the inventory or manufacturing transaction identifier.
• INVENTORY_ITEM_ID / ORGANIZATION_ID — The item and inventory organization context.
• LEVEL_TYPE / LEVEL_TYPE_DSP — The level type code from the base table and its decoded meaning obtained from MFG_LOOKUPS.
• ITEM_COST — The item-level cost value associated with the transaction.
• COST_ELEMENT / COST_ELEMENT_ID — The cost element description and its identifier, sourced from CST_COST_ELEMENTS.
• NEW_AVERAGE_COST — The average cost resulting after the transaction's effect.
• PERCENTAGE_CHANGE — The relative cost impact expressed as a percentage, matching the search term the user queried. This column quantifies how much the cost element's contribution shifted relative to the prior cost.
• VALUE_CHANGE — The absolute cost change contributed by the cost element.

Common Use Cases and Queries

A frequent requirement is identifying transactions whose cost movement exceeded a threshold, which is directly addressed through PERCENTAGE_CHANGE. A representative query follows:

SELECT TRANSACTION_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID, COST_ELEMENT, TRANSACTION_COST, NEW_AVERAGE_COST, VALUE_CHANGE, PERCENTAGE_CHANGE FROM APPS.MTL_CST_TXN_COST_DETAILS_V WHERE PERCENTAGE_CHANGE > 10 ORDER BY PERCENTAGE_CHANGE DESC;

Analysts also group results by cost element to understand which elements drive volatility:

SELECT COST_ELEMENT, COUNT(*) NUM_TXNS, SUM(VALUE_CHANGE) TOTAL_CHANGE, AVG(PERCENTAGE_CHANGE) AVG_PCT FROM APPS.MTL_CST_TXN_COST_DETAILS_V WHERE ORGANIZATION_ID = :org_id GROUP BY COST_ELEMENT;

Because transactional costing data volumes are typically high, queries against this view should filter on ORGANIZATION_ID, TRANSACTION_ID, or date-adjacent criteria where supported, and should avoid unbounded scans to preserve performance.