Search Results mtl_subinventories_trk_val_v

Overview

MTL_SUBINVENTORIES_TRK_VAL_V is an APPS-owned database view in the Oracle E-Business Suite Inventory (INV) module. As its name implies, it exposes subinventory definitions restricted to those that are quantity-tracked and currently active. The view is documented in ETRM for both 12.1.1 and 12.2.2 and is flagged with the description "Retrofitted," indicating it was re-created or adapted during the ETRM documentation cycle. Because it is a view rather than a table, it holds no data of its own; it presents a filtered, denormalized projection of subinventory setup information for reporting, integration, and validation purposes. The suffix "_TRK_VAL_V" reflects its dual filter: tracked (QUANTITY_TRACKED = 1) and valid (not disabled as of the current date). It is commonly consulted wherever application logic must confirm that a subinventory exists and is an active, quantity-tracked location before processing inventory transactions. The presence of the column PICKING_ORDER is significant to users searching for "picking_order," since this view is one of the primary read sources that surfaces subinventory picking sequence for picking, put-away, and material handling workflows.

Underlying Base Objects

The view is defined over a single base object, MTL_SECONDARY_INVENTORIES, referenced through a synonym in the APPS schema. MTL_SECONDARY_INVENTORIES is the master setup table for subinventories in Oracle Inventory. The view applies two WHERE-clause predicates against that table:

• Active filter: NVL(DISABLE_DATE, SYSDATE+1) > SYSDATE — returns only subinventories whose disable date is null or in the future.
• Tracked filter: QUANTITY_TRACKED = 1 — returns only subinventories for which on-hand quantities are tracked.

No joins are performed; every column in the view maps directly to a column of the same name in MTL_SECONDARY_INVENTORIES. The view therefore inherits the organization-level partitioning of the base table through ORGANIZATION_ID, so results are always scoped to a specific inventory organization.

Key Columns

• SECONDARY_INVENTORY_NAME — the subinventory name; combined with ORGANIZATION_ID it forms the logical key.
• ORGANIZATION_ID — the inventory organization to which the subinventory belongs.
• PICKING_ORDER — the numeric sequence used to prioritize subinventories during picking; central to the "picking_order" search.
• QUANTITY_TRACKED — always 1 in this view, confirming the record is quantity-tracked.
• INVENTORY_ATP_CODE, AVAILABILITY_TYPE, RESERVABLE_TYPE, LOCATOR_TYPE — ATP eligibility, availability, reservability, and locator control characteristics.
• MATERIAL_ACCOUNT, MATERIAL_OVERHEAD_ACCOUNT, RESOURCE_ACCOUNT, OVERHEAD_ACCOUNT, OUTSIDE_PROCESSING_ACCOUNT, EXPENSE_ACCOUNT, ENCUMBRANCE_ACCOUNT — the accounting flexfield assignments for the subinventory.
• ASSET_INVENTORY, SOURCE_TYPE, SOURCE_SUBINVENTORY, SOURCE_ORGANIZATION_ID — asset and replenishment source attributes.
• REQUISITION_APPROVAL_TYPE, PROJECT_ID, TASK_ID, SUBINVENTORY_USAGE, LPN_CONTROLLED_FLAG — requisition approval behavior, project/task defaults, usage type, and LPN (license plate number) control flag.

Common Use Cases and Queries

The view is typically used to validate eligible subinventories, drive picking and put-away ordering, and populate LOVs or integration payloads. A representative query retrieving picking order for an organization is:

• SELECT secondary_inventory_name, picking_order FROM mtl_subinventories_trk_val_v WHERE organization_id = :org_id ORDER BY picking_order;
• SELECT secondary_inventory_name, locator_type, lpn_controlled_flag FROM mtl_subinventories_trk_val_v WHERE organization_id = :org_id AND subinventory_usage = 'STORAGE';
• SELECT secondary_inventory_name, material_account, expense_account FROM mtl_subinventories_trk_val_v WHERE organization_id = :org_id;

Typical scenarios include filtering valid picking locations ahead of a sales order pick, resolving the picking sequence for warehouse tasks, and confirming quantity-tracked status before posting inventory or move-order transactions. Because it excludes disabled and non-tracked subinventories, it is safe for operational lookups where only active, tracked locations are valid.