Search Results mtl_sub_ast_trk_val_v




Overview
Explore in AI Chat

Overview

MTL_SUB_AST_TRK_VAL_V is an APPS-owned database view in Oracle E-Business Suite, registered under the INV – Inventory product family. Its ETRM description is recorded only as "Retrofitted," indicating the object was migrated forward as part of the EBS 12.1.1 to 12.2.2 upgrade path and retained for backward compatibility with dependent forms, reports, and interfaces rather than being designed as a new 12.2.2 artifact.

Functionally, the view exposes the subset of secondary inventory definitions that represent asset-tracked, quantity-tracked subinventories. It is a filtered projection of MTL_SECONDARY_INVENTORIES, returning only rows where QUANTITY_TRACKED equals 1, ASSET_INVENTORY equals 1, and the subinventory is not disabled as of the current system date. This makes the view a convenient reference point for reporting and integration logic that needs to distinguish asset subinventories from ordinary material stores without repeatedly re-implementing the filter predicates.

Underlying Base Objects

The view is defined over a single referenced base object, MTL_SECONDARY_INVENTORIES, accessed through a synonym in the APPS schema. All columns exposed by the view are sourced directly from that table; the view performs no joins, aggregations, or derived calculations. Its behavior is therefore entirely governed by the base table's row population and by the WHERE clause applied at definition time.

  • Filter condition: NVL(DISABLE_DATE, SYSDATE+1) > SYSDATE — returns only subinventories that are currently active; a NULL disable date is treated as indefinitely valid.
  • QUANTITY_TRACKED = 1 — restricts output to subinventories for which on-hand quantities are tracked.
  • ASSET_INVENTORY = 1 — restricts output to subinventories designated as asset inventory, used for capitalized items.

Because the predicates are embedded in the view text, any query against the view automatically inherits the currency of the SYSDATE evaluation at execution time; rows for subinventories disabled after the fact will drop out of results without any code change.

Key Columns

The view projects the full set of columns listed in the ETRM metadata. The most significant for asset-subinventory reporting include:

Common Use Cases and Queries

Typical usage centers on asset-subinventory validation, account-default lookups, and inventory configuration reporting. A standard listing query is:

  • SELECT organization_id, secondary_inventory_name, description, material_account FROM apps.mtl_sub_ast_trk_val_v WHERE organization_id = :org_id ORDER BY secondary_inventory_name;

A join to on-hand balances to identify asset stock positions:

  • SELECT v.organization_id, v.secondary_inventory_name, SUM(moh.transaction_quantity) qty FROM apps.mtl_sub_ast_trk_val_v v, apps.mtl_onhand_quantities_detail moh WHERE v.organization_id = moh.organization_id AND v.secondary_inventory_name = moh.subinventory_code GROUP BY v.organization_id, v.secondary_inventory_name;

A lookup of account defaults for a specific asset subinventory:

  • SELECT material_account, material_overhead_account, resource_account, overhead_account FROM apps.mtl_sub_ast_trk_val_v WHERE organization_id = :org_id AND secondary_inventory_name = :sub_name;

Because the view returns only active, asset-tracked, quantity-tracked subinventories, it is well suited to reports and validation lists where capitalized inventory storage locations must be distinguished from expense or non-tracked locations. Consumers should note that the object carries only a "Retrofitted" description and no documented column comments, so downstream code should rely on the underlying MTL_SECONDARY_INVENTORIES semantics.