Search Results cost_alloc

Overview

PMIBV_STANDARD_COST_LEDGER_V is an APPS-owned database view in Oracle E-Business Suite, registered as VALID and associated with the product family PMI — Process Manufacturing Intelligence, which is documented as obsolete within the ETRM reference for releases 12.1.1 and 12.2.2. The view exposes a ledger of Oracle Process Manufacturing (OPM) costing detail information produced during Cost Rollup processing. Each row represents a discrete costing ledger line generated by the rollup engine, capturing the relationship between a rolled-up item, its components or resources, and the cost elements assigned to them.

In EBS reporting and integration terms, the view functions as a read-only, denormalized projection of the underlying OPM standard cost ledger. Because it consolidates quantity, unit of measure, cost allocation, and resource usage attributes into a single horizontal structure, it is well suited to ad hoc queries, custom concurrent programs, and extract routines that must reconcile cost rollup output without joining multiple OPM costing tables. The presence of the ITEM_FMQTY_UM column makes it a relevant target for the common search term "item_fmqty_um," which denotes the unit of measure associated with the item's fixed or formula quantity recorded on the costing ledger line.

Underlying Base Objects

The documented view text defines PMIBV_STANDARD_COST_LEDGER_V over a single referenced base object, CM_SCST_LED, accessed in the APPS schema through a SYNONYM. The SELECT aliases this source as STDLEDGER and filters rows with the predicate DELETE_MARK = 0, ensuring that logically deleted costing records are excluded from the result set. The view is defined WITH READ ONLY, so no DML may be issued against it.

Where the view text and the published column listing differ in spelling — for example FORM_PROD_UM in the view text versus FORM_PROD_UOM in the column list, COMPONENT_COST versus CMPNT_COST, and USAGE_UOM versus USAGE_UM — the underlying projection remains the same logical attribute sourced from CM_SCST_LED. The view therefore acts as a stable, business-friendly presentation layer over the OPM cost rollup ledger, insulating report authors from the base synonym and the soft-delete mechanism.

Key Columns

• STD_QTY — Standard quantity on which the ledger line is based.
• FORM_PROD_UOM — Formula product unit of measure for the rolled item.
• ROUTING_QTY — Quantity driven by routing or recipe definition.
• PRODUCT_QTY — Product quantity associated with the costing line.
• COST_ALLOC — Cost allocation amount applied to the line.
• LINE_TYPE — Classification of the ledger line (for example component or resource).
• ITEM_QTY — Item quantity used in the rollup calculation.
• ITEM_FMQTY — Formula/fixed quantity for the item.
• ITEM_FMQTY_UM — Unit of measure for ITEM_FMQTY; the explicit source of the searched term.
• COMPONENT_COST / CMPNT_COST — Cost attributed to the component.
• RESOURCE_COUNT, RESOURCE_USAGE, RESOURCES — Resource consumption details for the line.
• NOMINAL_COST — Nominal cost recorded on the rollup line.
• USAGE_UOM — Unit of measure for usage quantities.
• RUDTL_ID, ITEM_ID, CMPNTCOST_ID — Surrogate identifiers linking to routing detail, item, and component cost entities.
• WHSE_CODE — Warehouse code associated with the costing entry.
• WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY.

Common Use Cases and Queries

Typical scenarios include auditing a cost rollup by item, validating formula quantity units, and extracting component and resource cost detail for downstream analysis. The following query retrieves formula quantity and its unit of measure for a specific item:

SELECT item_id, item_qty, item_fmqty, item_fmqty_um, component_cost, line_type
FROM apps.pmibv_standard_cost_ledger_v
WHERE item_id = :p_item_id;

Aggregate reporting by warehouse and resource can be performed as follows:

SELECT whse_code, resources, SUM(nominal_cost) total_nominal_cost
FROM apps.pmibv_standard_cost_ledger_v
GROUP BY whse_code, resources;

Because the object is documented as part of an obsolete product family, new development should confirm support status, but the view remains a dependable read-only source for OPM standard cost ledger reporting where it is still deployed.