Search Results lpn_controlled_flag




Overview
Explore in AI Chat

Overview

APPS.MTL_SUBINVENTORIES_TRK_VAL_V is a reporting view in Oracle E-Business Suite that exposes the configuration of quantity-tracked subinventories across inventory organizations. It is defined over the MTL_SECONDARY_INVENTORIES base table and returns one row per active, quantity-tracked subinventory, combining organizational context, accounting defaults, ATP and reservation rules, locator control, sourcing attributes, project references, and the LPN_CONTROLLED_FLAG that indicates whether the subinventory is license plate number (LPN) controlled. The view is used throughout Oracle Inventory and Oracle Warehouse Management (WMS) reporting to validate subinventory setup before transactions are permitted.

Unlike many inventory views that expose all subinventory definitions, this view applies two restrictive predicates: DISABLE_DATE must be null or in the future (the row is not disabled), and QUANTITY_TRACKED must equal 1. As a result, the view returns only subinventories for which on-hand quantities are actually maintained — a critical distinction for valuation, reservation, and LPN-driven picking logic. In 12.1.1 and 12.2.2 the structure is identical, though the WMS and LPN feature set receives greater emphasis in 12.2.x.

Because the object is a view, it is query-only and carries no DML privileges for data changes. It is generally resolved through the APPS synonym, allowing custom reports, concurrent programs, and integrations to query it without qualifying the underlying table.

Underlying Base Objects

The view is defined solely over MTL_SECONDARY_INVENTORIES, referenced via its APPS synonym. No joins or outer tables are present. The defining query selects all listed columns from that table and filters with:

  • NVL(DISABLE_DATE, SYSDATE+1) > SYSDATE — retaining only subinventories that are currently active.
  • QUANTITY_TRACKED = 1 — retaining only subinventories that maintain on-hand quantities.

Consequently, the view inherits the column semantics and datatypes of MTL_SECONDARY_INVENTORIES, and its row count varies dynamically as subinventories are enabled, disabled, or reconfigured. Since it is built on the base table rather than a snapshot, reads reflect committed state at query time.

Key Columns

Common Use Cases and Queries

Typical usage includes setup validation, WMS/LPN reporting, and integration feeds. A representative query to identify LPN-controlled, quantity-tracked subinventories is:

  • SELECT organization_id, secondary_inventory_name, lpn_controlled_flag FROM apps.mtl_subinventories_trk_val_v WHERE lpn_controlled_flag = 'Y';
  • SELECT secondary_inventory_name, locator_type, reservable_type FROM apps.mtl_subinventories_trk_val_v WHERE organization_id = :org_id;
  • SELECT secondary_inventory_name, material_account, expense_account FROM apps.mtl_subinventories_trk_val_v WHERE organization_id = :org_id AND asset_inventory = 1;

Because the view filters out non-quantity-tracked and disabled subinventories, it is well suited to populating LOVs and validation lists for transaction entry, and to driving downstream ETL where only active, quantity-bearing subinventories should be surfaced.