Results for “source_subinventory”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MTL_SUBINVENTORIES_VAL_V is a validation (VAL) view owned by the APPS schema in Oracle E-Business Suite, defined in the INV (Inventory) product module. It exposes a filtered, report-friendly projection of subinventory definitions, exposing only those subinventories that are currently active and that represent valid storage subinventories. The view is documented in ETRM with status VALID and carries a "Retrofitted" designation, indicating it was introduced or adapted to preserve backward compatibility with earlier validation views that Oracle Forms and integration points relied upon.

Because it is a view rather than a base table, MTL_SUBINVENTORIES_VAL_V presents no independent storage. Its primary role is to serve as a validated source of subinventory metadata for concurrent programs, value-set validation, reports, and external integrations that must be restricted to non-obsolete, stockable subinventories. The user search term "default_cost_group_id" appears directly in the view's SELECT list, making this view a useful access point for cost group assignments defined at the subinventory level.

Underlying Base Objects

The view is defined over a single documented base object: MTL_SECONDARY_INVENTORIES (referenced through a synonym). The defining query selects subinventory attributes subject to two documented predicates:

  • NVL(DISABLE_DATE, SYSDATE+1) > SYSDATE — excludes any subinventory whose disable date has passed; rows with a null disable date are treated as active.
  • SUBINVENTORY_TYPE = 1 OR SUBINVENTORY_TYPE IS NULL — restricts output to storage-type subinventories, filtering out receiving or other special-purpose subinventory definitions.

No joins, unions, or additional tables appear in the documented view text, so cardinality matches MTL_SECONDARY_INVENTORIES after filtering. One row is returned per active storage subinventory per organization.

Key Columns

Common Use Cases and Queries

Typical uses include validating subinventory LOVs in custom forms, feeding subinventory attributes into costing and accounting reports, and driving integrations that require the default cost group or account assignments. Because the view already excludes disabled and non-storage subinventories, applications can avoid reimplementing the disable-date and subinventory-type filters.

Retrieve the default cost group for each active subinventory in an organization:

SELECT organization_id,
       secondary_inventory_name,
       description,
       default_cost_group_id
  FROM apps.mtl_subinventories_val_v
 WHERE organization_id = :org_id
 ORDER BY secondary_inventory_name;

Confirm accounting and availability attributes for a specific subinventory:

SELECT secondary_inventory_name,
       availability_type,
       reservable_type,
       quantity_tracked,
       lpn_controlled_flag,
       material_account
  FROM apps.mtl_subinventories_val_v
 WHERE organization_id = :org_id
   AND secondary_inventory_name = :subinventory;

The view should be treated as read-only reference data; changes to subinventory definitions must be made through supported Inventory forms or APIs against MTL_SECONDARY_INVENTORIES so that validation rules, audit controls, and cost group integrity remain enforced.