Results for “from_organization_name”

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

Overview

INVFV_INVENTORY_SUPPLIES is a read-only view owned by the APPS schema in Oracle E-Business Suite (validated in both 12.1.1 and 12.2.2). It is classified under the INV — Inventory product family and is documented in ETRM as "Retrofitted," indicating the object was re-implemented or re-pointed during an upgrade or patch cycle rather than introduced as net-new functionality. The view presents inventory supply records sourced from MTL_SUPPLY, filtered to the supply type REQ, meaning it exposes requisition-based supply lines — anticipated receipts that have been committed through a purchase requisition but have not yet been realized as a purchase order or receipt.

Its role is primarily reporting and integration. Because it joins supply records to organization, item, requisition, transfer, and location details in a single flattened structure, it serves as a denormalized feeder for supply/demand analysis, ATP-style availability reporting, inbound transfer tracking, and custom concurrent programs. The inclusion of descriptive segment values (via PRH.SEGMENT1, PRL.LINE_NUM, organization names) makes the view directly usable without additional joins for many business-facing reports.

Underlying Base Objects

The view is defined over fifteen documented base objects (all referenced as PUBLIC synonyms resolved to the APPS tables): HR_ALL_ORGANIZATION_UNITS, MTL_ITEM_LOCATIONS, MTL_PARAMETERS, MTL_SUPPLY, MTL_SYSTEM_ITEMS, PO_DISTRIBUTIONS_ALL, PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_RELEASES_ALL, PO_REQUISITION_HEADERS_ALL, PO_REQUISITION_LINES_ALL, RCV_SHIPMENT_HEADERS, RCV_SHIPMENT_LINES, and RCV_TRANSACTIONS.

MTL_SUPPLY is the driving table and is aliased MTS; it is inner-joined to PO_REQUISITION_LINES_ALL (PRL) and PO_REQUISITION_HEADERS_ALL (PRH) via REQ_LINE_ID and REQ_HEADER_ID. The HR_ALL_ORGANIZATION_UNITS table appears three times as HOU1, HOU2, and HOU3 — supplying the names for the from-organization, to-organization, and intransit-owning-organization respectively. MTL_PARAMETERS appears three times (MP1, MP2, MP3) to supply organization codes. Critically, all of these joins are outer joins (noted by the (+)= operator), so supply rows are preserved even when organization, item, or location master data is missing. The references to PO and RCV tables in the base-object list are present in the view's broader definition but are not active in the REQ branch selected by the WHERE clause.

Key Columns

• SUPPLY_TYPE_CODE — Restricts the view to 'REQ' rows; identifies the supply category.
• SUPPLY_SOURCE_ID, REQ_HEADER_ID, REQ_LINE_ID — Keys linking back to the requisition header/line.
• SEGMENT1, LINE_NUM — Requisition number and requisition line number for human-readable output.
• ITEM_ID, ITEM_REVISION, QUANTITY, UNIT_OF_MEASURE — Item and quantity detail for the supply line.
• TO_ORG_PRIMARY_QUANTITY, TO_ORG_PRIMARY_UOM — Requisition quantity expressed in the destination organization's primary UOM.
• FROM_ORGANIZATION_ID / FROM_SUBINVENTORY and TO_ORGANIZATION_ID / TO_SUBINVENTORY — Source and destination inventory context; the FROM pair is typically null for external requisitions.
• INTRANSIT_OWNING_ORG_ID — Owning organization during in-transit transfer scenarios.
• ORGANIZATION_CODE (MP1/MP2/MP3) and NAME (HOU1/HOU2/HOU3) — Resolved via outer joins to MTL_PARAMETERS and HR_ALL_ORGANIZATION_UNITS.
• RECEIPT_DATE, NEED_BY_DATE, EXPECTED_DELIVERY_DATE — Scheduling dates used in supply timing calculations.
• LOCATION_ID — Destination inventory location (MTL_ITEM_LOCATIONS).
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard audit columns.

Common Use Cases and Queries

Typical scenarios include pending-receipt reporting, inbound transfer visibility, and supply/demand reconciliation. A representative query selecting requisition-based supplies with resolved organization names:

SELECT supply_source_id,
       segment1        req_number,
       line_num        req_line,
       item_id,
       quantity,
       to_org_primary_quantity,
       need_by_date,
       hou2_name       to_org_name,
       hou1_name       from_org_name
FROM   apps.invfv_inventory_supplies
WHERE  need_by_date BETWEEN :p_start AND :p_end;

Because the view restricts to SUPPLY_TYPE_CODE = 'REQ', no additional filter is needed for requisition-only reporting. For organization-level rollups, aggregate on ORGANIZATION_CODE (MP2) or the HOU2 NAME column; for aging analysis, group by NEED_BY_DATE. Note that the view is read-only and its joins are all outer, so consumers should expect possible NULL organization codes or names when master data is incomplete.