Search Results subinventory_type




Overview
Explore in AI Chat

Overview

APPS.MTL_SUB_AST_VAL_V is a reporting and integration view in Oracle E-Business Suite (available in 12.1.1 and 12.2.2) that exposes a filtered subset of subinventory definitions. Despite its name, which might suggest an asset valuation view, the object surfaces attribute and account information for asset subinventories as maintained in Oracle Inventory (INV). It is most commonly consulted by users searching for the subinventory_type qualifier, since the view's defining predicate restricts rows based on that very column. Reporting tools, interfaces, and custom code can query this view rather than the base table to obtain only asset-tracked, active subinventories without re-implementing the filtering logic.

Underlying Base Objects

The view is defined over a single documented base object: MTL_SECONDARY_INVENTORIES, appearing as an APPS synonym. All columns projected by MTL_SUB_AST_VAL_V are drawn directly from that table; the view applies no joins and performs no aggregation. The WHERE clause imposes three conditions: the disable date must be null or in the future (NVL(DISABLE_DATE, SYSDATE+1) > SYSDATE), the subinventory must be asset-tracked (ASSET_INVENTORY = 1), and the subinventory type must be 1 or null (SUBINVENTORY_TYPE = 1 OR SUBINVENTORY_TYPE IS NULL). Because the view is a filtered projection, its row set is always a proper, current subset of the base table, and any DML performed against the base table is immediately reflected when the view is queried.

Key Columns

The projected columns mirror the persisted subinventory attributes in the base table. Notable ones include:

Common Use Cases and Queries

Typical usage includes validating that only active, asset-tracked subinventories are returned to downstream reporting, generating lists of valid subinventories for inventory transaction interfaces, and resolving account defaults for integration routines.

SELECT ORGANIZATION_ID,
       SECONDARY_INVENTORY_NAME,
       DESCRIPTION,
       SUBINVENTORY_TYPE,
       MATERIAL_ACCOUNT,
       EXPENSE_ACCOUNT
FROM   APPS.MTL_SUB_AST_VAL_V
WHERE  ORGANIZATION_ID = :p_org_id
ORDER BY SECONDARY_INVENTORY_NAME;

Because the view itself filters on ASSET_INVENTORY = 1 and SUBINVENTORY_TYPE = 1 OR SUBINVENTORY_TYPE IS NULL, callers do not need to restate those conditions. Any additional filtering should be limited to organization, locator, or accounting criteria. Where the underlying metadata does not guarantee it, developers should still confirm expected values of SUBINVENTORY_TYPE from the base table before relying on the view for validation logic.