Search Results inventory_atp_code




Overview
Explore in AI Chat

Overview

MTL_SUB_TRK_ALL_V is an Oracle E-Business Suite (EBS) inventory view owned by the APPS schema and classified under the INV – Inventory product. Its object type is VIEW, and its status in ETRM is VALID. The view is flagged as "Retrofitted," indicating it was carried forward from an earlier release line into the 11i and R12 code stack and maintained for backward compatibility rather than intentionally redesigned. It exposes subinventory definitions from MTL_SECONDARY_INVENTORIES, but unlike the full base table, it restricts output to those subinventories that participate in on-hand quantity tracking. Specifically, the view definition filters on QUANTITY_TRACKED = 1 and (SUBINVENTORY_TYPE = 1 OR SUBINVENTORY_TYPE IS NULL). This effectively isolates asset subinventories (SUBINVENTORY_TYPE = 1, the standard asset subinventory) and legacy rows where the type is not yet populated. The name suffix "_TRK" reinforces the quantity-tracked qualification, while "_ALL" reflects that all eligible organizations and subinventories are surfaced without additional organization or user security predicates. For reporting and integration, the view provides a stable, de-normalized projection of the most commonly referenced subinventory attributes, including accounting flexfield accounts, ATP and reservability flags, locator control, picking order, source information, and the SUBINVENTORY_USAGE classification.

Underlying Base Objects

The view is defined over a single documented base object, MTL_SECONDARY_INVENTORIES, which is referenced through an APPS-owned synonym. MTL_SECONDARY_INVENTORIES is the master table that stores subinventory definitions per inventory organization, including asset subinventories, expense subinventories, and other type classifications. Because MTL_SUB_TRK_ALL_V simply projects a fixed column list with a filtering WHERE clause, it adds no aggregation or joins. The relationship is therefore one-to-one between a qualifying row in MTL_SECONDARY_INVENTORIES and a row in the view. No columns are renamed, and no expressions are applied to the exposed columns in the documented view text. This means the view is not a security mechanism and does not enforce organization-level access; callers must still apply organization and responsibility context in their own queries. It does, however, enforce a functional scope: only quantity-tracked asset subinventories appear, so expense and non-quantity-tracked definitions are excluded by design.

Key Columns

Common Use Cases and Queries

The view is commonly used in reports and interfaces that need only asset, quantity-tracked subinventories. A typical query filters by organization and inspects usage and accounting setup:

SELECT organization_id, secondary_inventory_name, subinventory_usage, asset_inventory, locator_type, material_account
FROM apps.mtl_sub_trk_all_v
WHERE organization_id = :p_org_id
ORDER BY secondary_inventory_name;

To list subinventories by usage classification, as suggested by the "subinventory_usage" search:

SELECT organization_id, secondary_inventory_name, subinventory_usage
FROM apps.mtl_sub_trk_all_v
WHERE subinventory_usage = :p_usage;

Integration scenarios include loading valid subinventory values into custom interfaces, validating locator-controlled subinventories before transactions, and driving accounting default derivations. Because the view excludes expense and non-quantity-tracked subinventories, callers requiring the complete catalogue should query MTL_SECONDARY_INVENTORIES directly. All access should be granted through the APPS synonym, and queries should always restrict ORGANIZATION_ID to respect multi-org isolation.