Results for “quantity_shipped”

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

Overview

The APPS.POS_UPD_DATE_PO_SHIP_V view is a denormalized reporting object within the Oracle iProcurement (ICX) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its purpose is to expose a flat, joined representation of purchase order shipment schedules together with the surrounding header, line, vendor, ship-to, and item context needed by iProcurement and related self-service flows. The view consolidates purchasing data across PO_HEADERS, PO_LINES, PO_RELEASES, and PO_LINE_LOCATIONS, then enriches it with vendor, location, item, and category attributes. A defining characteristic is that it filters to active, actionable shipments: only shipments with APPROVED_FLAG = 'Y', CANCEL_FLAG = 'N', CLOSED_CODE = 'OPEN', and shipment types of STANDARD, BLANKET, or SCHEDULED are returned. Because it surfaces the purchase order revision number (REVISION_NUM) alongside line, shipment, and promised-date details, it is well suited to queries that track changes to an order over time — the scenario implied by the search term po_revision_num.

Underlying Base Objects

Per the documented metadata, the view is owned by APPS and is defined over the following base objects: PO_HEADERS, PO_LINES, PO_RELEASES, and PO_LINE_LOCATIONS (all PO synonyms), plus HR_LOCATIONS, ORG_ORGANIZATION_DEFINITIONS, PO_VENDORS, and PO_VENDOR_SITES (views). Item and category descriptions are resolved through the MTL_SYSTEM_ITEMS_KFV and MTL_CATEGORIES_KFV synonyms. Person display names are resolved via the PO_INQ_SV package function GET_PERSON_NAME. The join topology is header-to-line-location anchored: PO_LINE_LOCATIONS is joined to PO_HEADERS on PO_HEADER_ID and to POL.PO_LINE_ID on PO_LINE_ID, with an outer join to PO_RELEASES (PRL.PO_RELEASE_ID(+)) so that non-release orders are still returned. Vendor and vendor-site joins are constrained by matching ORG_ID (via NVL(...,-1)), and the item join uses a conditional organization match to the ship-to organization.

Key Columns

• PO_HEADER_ID, PO_RELEASE_ID, PO_LINE_ID, LINE_LOCATION_ID — primary keys linking back to the underlying purchasing entities.
• PO_NUMBER — derived as either the header SEGMENT1 or, for releases, SEGMENT1-RELEASE_NUM.
• REVISION_NUM — the purchase order revision number from PO_HEADERS; central to revision-tracking queries.
• LINE_NUM, SHIPMENT_NUM — line and shipment identification.
• ITEM_ID, CONCATENATED_SEGMENTS (item and category), ITEM_DESCRIPTION, ITEM_REVISION, VENDOR_PRODUCT_NUM — item and catalog context.
• PROMISED_DATE, NEED_BY_DATE, CHANGE_PROMISED_DATE_REASON — scheduling and change-reason data.
• QUANTITY, QUANTITY_RECEIVED, QUANTITY_SHIPPED, unit of measure — fulfillment quantities.
• VENDOR_ID, VENDOR_NAME, VENDOR_SITE_CODE, and ship-to organization/location columns — supplier and destination context.
• AGENT_ID and the derived buyer name from PO_INQ_SV.GET_PERSON_NAME.

Common Use Cases and Queries

Typical uses include iProcurement shipment monitoring, promised-date change analysis, and buyer workload reporting. The REVISION_NUM column allows comparison of an order against its revision history.

• Revision tracking: SELECT PO_NUMBER, LINE_NUM, SHIPMENT_NUM, REVISION_NUM, PROMISED_DATE FROM POS_UPD_DATE_PO_SHIP_V WHERE PO_NUMBER = :po;
• Promised-date change investigation: filter on CHANGE_PROMISED_DATE_REASON IS NOT NULL.
• Outstanding-quantity reporting: compute QUANTITY - QUANTITY_RECEIVED where remaining quantity is positive.