Results for “mtl_phy_adj_cost_v”

26 results




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

Overview

MTL_PHY_ADJ_COST_V is an Oracle E-Business Suite 12.1.1 / 12.2.2 inventory view owned by the APPS schema and classified under the INV (Inventory) product family. It exposes the physical inventory adjustment lines stored in MTL_PHYSICAL_ADJUSTMENTS together with the item cost that Oracle Cost Management would apply when the adjustment is approved and posted. In 12.2.2 the object is described in the ETRM repository simply as "Retrofitted," indicating that it was carried forward from earlier releases to preserve downward compatibility for reports, Discoverer workbooks, and custom extensions that referenced the earlier definition.

The view's principal role is to provide a single read-only result set for physical inventory count reconciliation, adjustment review, and cost impact analysis. It joins adjustment lines to the cost group item cost view so that a pending or approved adjustment can be valued without invoking the Cost Management APIs directly. Because it is a UNION ALL construct, rows are returned from both locator-based and non-locator-based adjustment paths in a consistent column layout.

Underlying Base Objects

The documented base objects are MTL_PHYSICAL_ADJUSTMENTS (the primary driver), CST_CG_ITEM_COSTS_VIEW (the costing source), MTL_PARAMETERS (organization-level cost method), and MTL_ITEM_LOCATIONS (locator validation). MRP_PROJECT_PARAMETERS appears in the dependency list as a synonym reference. The view text restricts the first branch to rows where MPA.LOCATOR_ID IS NULL and joins CST_CG_ITEM_COSTS_VIEW on ORGANIZATION_ID, INVENTORY_ITEM_ID, and COST_GROUP_ID, where the cost group is resolved as DECODE(MP.PRIMARY_COST_METHOD, 1, 1, NVL(MPA.COST_GROUP_ID, 1)). A UNION ALL branch returns adjustment lines that have no matching cost row, substituting 0 for ITEM_COST, which ensures that uncosted or newly created items still appear in adjustment reports rather than being silently dropped.

Key Columns

Common Use Cases and Queries

Typical applications include pending-adjustment approval reports, cost impact analysis of a physical inventory, and lot/serial audit extracts. Because LOT_SERIAL_CONTROLS is exposed directly, a frequent query filters adjustments for items under lot or serial control:

SELECT adjustment_id, organization_id, inventory_item_id, lot_number, serial_number, adjustment_quantity, item_cost, approval_status FROM apps.mtl_phy_adj_cost_v WHERE lot_serial_controls IN (2, 5) AND approval_status <> 7 AND organization_id = :org_id;

A second common pattern values the total adjustment amount for an organization by multiplying the adjustment quantity by the viewed item cost, while excluding zero-cost fallback rows with a NVL or ITEM_COST check. Developers should note that the view is read-only and that the embedded DECODE on PRIMARY_COST_METHOD means the cost group resolution behaves differently in standard versus average costing organizations; report logic should therefore avoid reproducing the join independently.