Search Results shipment_quantity




Overview
Explore in AI Chat

Overview

APPS.PO_SOURCE_SHIPMENT_NUM_V is a supplementary Oracle EBS view owned by the APPS schema and registered under FND Design Data as PO.PO_SOURCE_SHIPMENT_NUM_V. It is documented as VALID in ETRM for both 12.1.1 and 12.2.2. The view consolidates shipment-level sourcing information from Oracle Purchasing line locations with descriptive attributes drawn from HR and organization reference data, exposing a flattened result set intended to simplify forms coding and reporting logic.

Oracle explicitly warns that this is a supplementary view for forms development and does not recommend querying or altering data through it, since its definition may change dramatically in subsequent minor or major releases. Consequently, the view should be treated as a read-only, convenience construct rather than a stable integration contract. The user search term "shipment_quantity" maps directly to the SHIPMENT_QUANTITY column exposed by this view.

Underlying Base Objects

The view is defined over the following documented objects: FINANCIALS_SYSTEM_PARAMS_ALL (synonym), HR_GENERAL (package), HR_LOCATIONS (view), HR_SECURITY (package), ORG_ORGANIZATION_DEFINITIONS (view), PO_LINE_LOCATIONS (synonym), and PO_LINE_LOCATIONS_ALL (synonym). The core transactional data originates from the purchasing line locations tables, while location descriptions, organization names, and security-based access restrictions are supplied through the HR and organization definition objects. The HR_SECURITY package typically enforces operating unit and organization-level access filtering, ensuring rows returned respect the caller's security profile. The view is not referenced by any other database object, confirming it is a terminal consumer view.

Key Columns

Common Use Cases and Queries

Typical use cases include forms-driven shipment inquiry, validation lookups for shipment quantities and UOMs, and lightweight reporting on where shipments are dispatched. Because HR_SECURITY is referenced, queries return only rows permitted by the session's security context.

Example query returning shipment quantities for a purchase order line:

  • SELECT shipment_num, shipment_quantity, unit_meas_lookup_code, organization_code FROM apps.po_source_shipment_num_v WHERE po_line_id = :p_line_id AND org_id = :p_org_id;

Example query aggregating shipped quantity by destination organization:

  • SELECT organization_code, SUM(shipment_quantity) total_qty FROM apps.po_source_shipment_num_v WHERE org_id = :p_org_id GROUP BY organization_code;

Given Oracle's warning, production integrations should query the underlying PO_LINE_LOCATIONS_ALL table directly rather than relying on this view, using it strictly as a reference for understanding forms behavior.