Search Results mtl_secondary_inventories_fk_v




Overview
Explore in AI Chat

Overview

The view APPS.MTL_SECONDARY_INVENTORIES_FK_V is an Inventory (INV) module database object that presents subinventory master data together with resolved foreign key descriptions. Its ETRM description is recorded simply as "Retrofitted," reflecting that the object was regenerated or ported forward as part of the EBS code-line evolution rather than introduced as new functionality. The view is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2 and is owned by the APPS schema.

Functionally, the view exposes the full column set of MTL_SECONDARY_INVENTORIES — the base table that stores subinventory definitions for every inventory organization — while denormalizing several related attributes into human-readable codes. In this respect it behaves as an "FK view": a reporting and integration convenience layer that spares the developer from joining multiple lookup tables. It is commonly consumed by forms, concurrent programs, OAF pages, and custom reports that must display or validate subinventory attributes, including the DEFAULT_LOC_STATUS_ID searched by the user, which is resolved here to its material status code.

Underlying Base Objects

The ETRM metadata documents the following referenced objects:

These objects are accessed through APPS synonyms, and the view itself sits on the MTL_SECONDARY_INVENTORIES synonym, inheriting the security and synonym conventions of the APPS schema.

Key Columns

Common Use Cases and Queries

Typical uses include validating subinventory attributes in forms and concurrent programs, driving inventory reports, and supporting integrations that need readable codes rather than numeric IDs. The DEFAULT_LOC_STATUS_CODE column in particular is used when determining the default material status applied to locators created within a subinventory.

A representative query retrieving subinventory status information:

  • SELECT organization_id, secondary_inventory_name, status_code, default_loc_status_id, default_loc_status_code, default_cost_group_name FROM mtl_secondary_inventories_fk_v WHERE organization_id = :p_org_id ORDER BY secondary_inventory_name;
  • Filtering by resolved status: SELECT secondary_inventory_name FROM mtl_secondary_inventories_fk_v WHERE default_loc_status_code = 'Active';
  • Locator default status lookups for a specific subinventory: SELECT secondary_inventory_name, default_loc_status_id, default_loc_status_code FROM mtl_secondary_inventories_fk_v WHERE organization_id = :p_org_id AND secondary_inventory_name = :p_subinventory;

Because the view performs NVL substitutions and inline subqueries, it is best suited to moderate-volume reporting and validation rather than high-throughput batch processing, where direct joins against base tables may be preferable.