Search Results from_subinventory_name

Overview

INVBV_INVENTORY_SUPPLIES is an Oracle E-Business Suite view owned by the APPS schema and registered under the INV (Inventory) product family. Its status is VALID, and the underlying definition is a retrofitted wrapper over the MTL_SUPPLY table. The view exposes the consolidated supply picture across an enterprise: purchase orders, requisitions, internal shipments, and in-transit stock destined for a receiving organization. Because it carries the security predicates '_SEC:MTS.FROM_ORGANIZATION_ID' and '_SEC:MTS.TO_ORGANIZATION_ID', the view is a secure reporting object. Oracle's Multi-Org Access Control (MOAC) substitutes these tokens at runtime so that a session only sees supply rows whose source and destination organizations fall within the operating unit context of the logged-in user. The WITH READ ONLY clause guarantees that the view can never be used as an update path, making it safe for ad-hoc querying, FSG-style reporting, OBIEE extracts, and inbound interfaces that need a stable, read-only supply snapshot.

Underlying Base Objects

The documented metadata lists a single referenced base object: MTL_SUPPLY, accessed through an APPS synonym. All projected columns originate from this source, aliased as MTS in the view text. MTL_SUPPLY is the shared supply repository consumed by supply-chain planning and by the inventory replenishment engine; it aggregates supplies from multiple sub-systems into one row-level structure. The view does not join to MTL_SYSTEM_ITEMS, MTL_PARAMETERS, or PO headers itself, so descriptive attributes beyond the identifiers must be resolved by the caller. A notable detail is the inline lookup token '_LA:MTS.DESTINATION_TYPE_CODE:PO_LOOKUP_CODES:DESTINATION TYPE:DESCRIPTION', which the EBS framework translates into a lookup join for the DESTINATION TYPE lookup on PO_LOOKUP_CODES, while CATEGORY_ID is commented out and therefore not exposed.

Key Columns

• SUPPLY_TYPE_CODE / SUPPLY_SOURCE_ID — Classify each supply and link it to its originating transaction.
• PO_HEADER_ID, PO_RELEASE_ID, PO_LINE_ID, PO_LINE_LOCATION_ID, PO_DISTRIBUTION_ID — Purchase-order lineage for supplier-delivered supply.
• REQUISITION_HEADER_ID / REQUISITION_LINE_ID — Internal requisition lineage.
• SHIPMENT_HEADER_ID / SHIPMENT_LINE_ID — Internal shipment lineage; these pair with the FROM/TO organization columns.
• INVENTORY_ITEM_ID, REVISION, QUANTITY, UNIT_OF_MEASURE — Item identity and the quantity expressed in the item's primary UOM.
• TO_ORG_PRIMARY_QUANTITY / TO_ORG_PRIMARY_UOM — Quantity converted to the destination organization's primary UOM, essential for cross-org aggregation.
• RECEIPT_DATE, NEED_BY_DATE, EXPECTED_DELIVERY_DATE — Scheduling columns used for availability and shortage analysis.
• FROM_ORGANIZATION_ID / FROM_SUBINVENTORY_NAME — Source organization and its subinventory; FROM_SUBINVENTORY_NAME is the column that answers the search term from_subinventory_name.
• TO_ORGANIZATION_ID / TO_SUBINVENTORY_NAME — Destination organization and subinventory.
• INTRANSIT_OWNING_ORG_ID, INVENTORY_LOCATOR_ID — In-transit ownership and locator detail.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard audit columns.

Common Use Cases and Queries

Typical uses include intransit-visibility dashboards, replenishment sourcing reports, and data extracts feeding planning systems. The query below isolates in-transit supply moving between organizations, filtering on the from-subinventory column the user searched for.

SELECT from_organization_id,
       from_subinventory_name,
       to_organization_id,
       to_subinventory_name,
       inventory_item_id,
       quantity,
       unit_of_measure,
       to_org_primary_quantity,
       need_by_date,
       expected_delivery_date
  FROM apps.invbv_inventory_supplies
 WHERE from_subinventory_name IS NOT NULL
   AND to_subinventory_name IS NOT NULL
   AND supply_type_code = 'INTRANSIT';

A second pattern aggregates available supply per destination subinventory for a given item, summing the destination-UOM quantity to avoid cross-org unit mismatches. Because both organization security tokens are embedded in the view, joins to MTL_SYSTEM_ITEMS, MTL_PARAMETERS, or PO_HEADERS should be performed outside the view using the natural identifier columns rather than attempting to project additional restricted attributes. Keeping queries read-only aligns with the view's own WITH READ ONLY constraint and preserves MOAC security enforcement.