Search Results quantity_tracked




Overview
Explore in AI Chat

Overview

APPS.MTL_SUB_AST_TRK_VAL_V is a reporting view in Oracle E-Business Suite (EBS) Release 12.1.1 and 12.2.2 that exposes a filtered subset of secondary inventory definitions from the Oracle Inventory (INV) module. Specifically, the view returns only those secondary inventories (subinventories) that are both quantity-tracked and designated as asset inventories. As such, it serves as a convenience layer for reporting, inquiry, and integration scenarios where consumers require an authoritative, pre-filtered list of "valid" asset-tracked subinventories without having to encode the filtering logic themselves against the base table.

The view is not a transactional object. It does not hold on-hand balances or material transactions; rather it exposes configuration metadata about the subinventory definition. Because it is a database view rather than a table, it inherits no independent storage and always reflects the current state of its underlying base object. The user search term "quantity_tracked" is central to this view, as QUANTITY_TRACKED = 1 is one of its two hard-coded filter predicates.

Underlying Base Objects

The view is defined over a single base object: MTL_SECONDARY_INVENTORIES, which in the APPS schema is referenced through a synonym. All columns exposed by MTL_SUB_AST_TRK_VAL_V are drawn directly from that table with no joins, unions, or derived computations. The view conceptually projects a column list and applies a WHERE clause.

The documented view text is:

Three predicates govern membership: (1) the subinventory must not be disabled — NVL(DISABLE_DATE, SYSDATE+1) > SYSDATE, which treats a null disable date as still active; (2) QUANTITY_TRACKED = 1, indicating the subinventory tracks quantities; and (3) ASSET_INVENTORY = 1, indicating the subinventory is an asset (as opposed to expense) subinventory. Records meeting all three criteria are returned.

Key Columns

The most significant columns of the view include:

  • SECONDARY_INVENTORY_NAME — the subinventory name; combined with ORGANIZATION_ID, this forms the logical identity of a subinventory.
  • ORGANIZATION_ID — the inventory organization to which the subinventory belongs.
  • DESCRIPTION — free-text description of the subinventory.
  • QUANTITY_TRACKED — always 1 in this view, since it is a filter predicate; indicates the subinventory tracks on-hand quantities.
  • ASSET_INVENTORY — always 1 in this view; indicates the subinventory is classified as an asset subinventory.
  • INVENTORY_ATP_CODE, AVAILABILITY_TYPE, RESERVABLE_TYPE, LOCATOR_TYPE, PICKING_ORDER — material control and availability attributes influencing how stock is picked and promised.
  • SUBINVENTORY_USAGE — describes how the subinventory is used (for example, for storing, receiving, or shipping).
  • MATERIAL_ACCOUNT, MATERIAL_OVERHEAD_ACCOUNT, RESOURCE_ACCOUNT, OVERHEAD_ACCOUNT, OUTSIDE_PROCESSING_ACCOUNT, EXPENSE_ACCOUNT, ENCUMBRANCE_ACCOUNT — the accounting flexfield accounts associated with the subinventory for cost and encumbrance posting.
  • SOURCE_TYPE, SOURCE_SUBINVENTORY, SOURCE_ORGANIZATION_ID — sourcing rules used when the subinventory draws supply from another subinventory or organization.
  • REQUISITION_APPROVAL_TYPE, PROJECT_ID, TASK_ID — requisition approval behavior and project/task defaulting attributes.

Common Use Cases and Queries

Typical uses include validating that a target subinventory is suitable for asset-tracked quantity transactions, driving drop-down lists in custom forms or concurrent programs, and feeding integration extracts with a curated list of subinventories. Because the view already enforces the quantity-tracked and asset filters, callers avoid duplicating that logic.

A representative query listing all valid asset-tracked, quantity-tracked subinventories for a given organization:

  • SELECT organization_id, secondary_inventory_name, description, subinventory_usage FROM apps.mtl_sub_ast_trk_val_v WHERE organization_id = :org_id ORDER BY secondary_inventory_name;
  • SELECT organization_id, secondary_inventory_name, material_account FROM apps.mtl_sub_ast_trk_val_v WHERE material_account IS NOT NULL;
  • SELECT COUNT(*) FROM apps.mtl_sub_ast_trk_val_v WHERE organization_id = :org_id;

Note that the view filters out disabled subinventories dynamically relative to SYSDATE, so results change over time as disable dates are set. For transaction-level or balance-level information, consumers must join to on-hand or transaction tables separately, since this view supplies configuration data only.