Search Results cost_per_unit




Overview
Explore in AI Chat

Overview

APPS.INVBV_PHYSICAL_ADJUSTMENTS is a Business Intelligence System (BIS) view in the Oracle E-Business Suite Inventory module, owned by the APPS schema. It exposes physical inventory adjustment records generated when an item count is performed and reconciled. The view presents the delta between the system-observed quantity and the physically counted quantity for a given item, organization, subinventory, and locator, together with the resulting adjustment quantity and associated cost, lot, and serial attributes. The BV naming convention identifies it as a reporting-oriented view intended for downstream BI, discoverer, and integration consumption rather than for transactional update. It carries FND Design Data reference INV.INVBV_PHYSICAL_ADJUSTMENTS and is documented as VALID in ETRM 12.2.2.

Underlying Base Objects

Per the documented dependency metadata, the view is defined over a single base object: MTL_PHYSICAL_ADJUSTMENTS, referenced through the APPS schema (documented as a SYNOPSIS/SYNONYM in the ETRM extract). This means the view is essentially a flattened, denormalized projection of the physical adjustment transaction table. No other database object is documented as referencing INVBV_PHYSICAL_ADJUSTMENTS; it is a terminal, read-only presentation object. Because the view derives entirely from the physical adjustments table, its one-row-per-adjustment granularity matches the base table, and joining back to MTL_PHYSICAL_ADJUSTMENTS on ADJUSTMENT_ID is the canonical way to enrich these records with additional attributes not surfaced here.

Key Columns

Common Use Cases and Queries

The view is typically used to report count variances, quantify shrinkage, and feed reconciliation or audit processes. A frequent requirement, mirroring the search term inventory_locator_id, is to resolve the locator for each adjustment:

  • Variance reporting: select all adjustments for a physical inventory and sum ADJUSTMENT_QUANTITY to measure net variance.
  • Locator-level analysis: join INVENTORY_LOCATOR_ID to MTL_ITEM_LOCATIONS to report adjustments by physical bin or locator.
  • Valuation: multiply ADJUSTMENT_QUANTITY by COST_PER_UNIT to quantify the financial impact of each adjustment.

A representative query follows:

  • SELECT a.ADJUSTMENT_ID, a.ORGANIZATION_ID, a.INVENTORY_ITEM_ID, a.SUBINVENTORY_NAME, a.INVENTORY_LOCATOR_ID, a.COUNT_QUANTITY, a.SYSTEM_QUANTITY, a.ADJUSTMENT_QUANTITY, a.COST_PER_UNIT FROM APPS.INVBV_PHYSICAL_ADJUSTMENTS a WHERE a.PHYSICAL_INVENTORY_ID = :p_physical_inventory_id AND a.INVENTORY_LOCATOR_ID IS NOT NULL;

Because the object is a read-only view, no INSERT, UPDATE, or DELETE should be issued against it; adjustments must be created through the standard Inventory count and approval process.