Results for “tag_uom”

22 results




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

Overview

MTL_PHY_INV_TAGS_COST_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered under the Inventory (INV) product module. In the ETRM 12.2.2 metadata, the object carries the description Retrofitted, indicating that its definition was adapted for the current release rather than authoring a distinct new interface. The view joins physical inventory tag data to item cost information, giving reconciliation and audit users a single query surface that couples counted tag quantities with the cost of the item being counted.

The view is read-only and is intended for reporting, inquiry, and downstream integration rather than transactional maintenance. Physical inventory tags themselves are recorded in MTL_PHYSICAL_INVENTORY_TAGS; this view enriches those rows with cost values so that tag-level valuations can be produced without repeated application logic. The presence of the TAG_UOM column — the search term that leads users to this object — reflects its role in exposing the unit of measure in which each tag quantity was captured, alongside the standardized conversion column TAG_QUANTITY_AT_STANDARD_UOM and its corresponding STANDARD_UOM.

Underlying Base Objects

The documented base objects referenced by MTL_PHY_INV_TAGS_COST_V are:

  • MTL_PHYSICAL_INVENTORY_TAGS (SYNONYM) — the primary source, supplying tag identity, quantities, UOM, item, subinventory, locator, lot, serial, LPN, and DFF attribute columns.
  • CST_CG_ITEM_COSTS_VIEW (VIEW) — supplies ITEM_COST values for the item/cost group combination.
  • MTL_PARAMETERS (SYNONYM) — used to resolve the organization's primary cost method and drive the cost group decode.
  • MTL_ITEM_LOCATIONS (SYNONYM) — location context.
  • MRP_PROJECT_PARAMETERS (SYNONYM) — project-related parameters.

The view text is a UNION ALL of two branches. The first branch filters to tags where LOCATOR_ID IS NULL, while the second covers tags with a locator. In both branches the cost join is driven by organization, inventory item, and a cost group resolved through DECODE on MP.PRIMARY_COST_METHOD — when the primary cost method is 1, cost group 1 is used; otherwise NVL(MPIT.COST_GROUP_ID, 1) is applied.

Key Columns

Common Use Cases and Queries

Typical uses include physical inventory tag valuation, variance analysis by subinventory or item, and extraction of counted quantities in standard UOM for reconciliation to perpetual balances.

List costed tags for an organization and physical inventory:

  • SELECT tag_number, inventory_item_id, tag_quantity, tag_uom, tag_quantity_at_standard_uom, standard_uom, item_cost FROM mtl_phy_inv_tags_cost_v WHERE physical_inventory_id = :pi_id;

Retrieve tags recorded in a specific unit of measure:

  • SELECT tag_number, tag_quantity, tag_uom, standard_uom FROM mtl_phy_inv_tags_cost_v WHERE tag_uom = :tag_uom;

Summarize extended tag value by subinventory:

  • SELECT subinventory, SUM(tag_quantity_at_standard_uom * item_cost) tagged_value FROM mtl_phy_inv_tags_cost_v WHERE organization_id = :org_id AND NVL(void_flag,'N') = 'N' GROUP BY subinventory;