Search Results preprocessing_lead_time




Overview
Explore in AI Chat

Overview

MTL_SUBINVENTORIES_ALL_V is a read-only view in the APPS schema that exposes subinventory master data for organizations enabled in Oracle Inventory (INV). In the ETRM 12.2.2 metadata it is classified as a VALID view belonging to the INV – Inventory product and is annotated as Retrofitted, indicating it was reintroduced to preserve backward compatibility for customizations, reports, and interfaces that referenced the view prior to changes in the underlying data model. The view presents one row per defined subinventory per organization, including hierarchical, accounting, ATP, locator-control, and lead-time attributes. Because it carries the _ALL_V naming convention, it is intended to present subinventory definitions across all operating units and organizations visible to the querying responsibility, rather than being restricted to a single organization. It serves as the standard reporting and integration surface for subinventory setup data consumed by purchasing, order management, manufacturing, and costing modules.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over a single referenced base object: the synonym MTL_SECONDARY_INVENTORIES (the underlying INV table MTL_SECONDARY_INVENTORIES in the APPS schema). The view text is a straightforward projection with a filter predicate:

  • SELECT ... FROM MTL_SECONDARY_INVENTORIES WHERE SUBINVENTORY_TYPE = 1 OR SUBINVENTORY_TYPE IS NULL
  • The SUBINVENTORY_TYPE filter restricts output to standard (material) subinventories (value 1) and rows where the type is null, excluding other subinventory types such as receiving or supplier-managed qualifying types.
  • No joins, unions, or analytical functions appear in the documented view text; therefore the view inherits the columns and row grain of the base table directly.
  • All DML is prohibited against the view; maintenance occurs through the base table and the standard Inventory setup forms.

Key Columns

Common Use Cases and Queries

Typical scenarios include validating subinventory setup, extracting lead times for scheduling analytics, verifying accounting assignments before period close, and feeding downstream integrations. A representative query returning lead-time attributes is:

  • SELECT organization_id, secondary_inventory_name, preprocessing_lead_time, processing_lead_time, postprocessing_lead_time FROM apps.mtl_subinventories_all_v WHERE organization_id = :p_org_id ORDER BY secondary_inventory_name;
  • SELECT organization_id, secondary_inventory_name, locator_type, quantity_tracked, asset_inventory FROM apps.mtl_subinventories_all_v WHERE quantity_tracked = 1;
  • SELECT organization_id, secondary_inventory_name, material_account FROM apps.mtl_subinventories_all_v WHERE disable_date IS NULL;

Because the view is unfiltered by organization except through the query predicate, callers should always qualify on ORGANIZATION_ID (or restrict by security profile) to avoid returning subinventories across all accessible organizations.