Search Results shipment_last_acceptable_date




Overview
Explore in AI Chat

Overview

ECE_POCO_SHIPMENTS_V is a private APPS-owned database view in the Oracle E-Business Suite e-Commerce Gateway (EC) module. Its documented purpose is to extract shipment-level information for the outbound Purchase Order Change (860/ORDCHG) transaction, and its display name within the ETRM repository is "Purchase Order Change Shipment View." The object is registered with lifecycle status "active," scope "private," and product affiliation to PO, indicating that although it physically resides in the APPS schema alongside other e-Commerce Gateway extraction views, it is functionally tied to Oracle Purchasing and is not intended as a public, general-purpose interface.

For users researching shipment_need_by_date, this view is directly relevant. The view's defining SELECT maps POLL.NEED_BY_DATE to the output alias SHIPMENT_NEED_BY_DATE. It is the alias — not the base column name — that appears in the outbound 860/ORDCHG shipment segment, so any investigation of a need-by date discrepancy on a purchase order change extract should begin here. The view is status VALID in the documented 12.2.2 environment, and the same definition is applicable across 12.1.1, since the underlying PO_LINE_LOCATIONS structure was not rearchitected between these releases.

Underlying Base Objects

The documented base objects are PO_LINE_LOCATIONS (synonym), HR_LOCATIONS_ALL and HR_LOCATIONS_ALL_TL (synonyms), HR_ALL_ORGANIZATION_UNITS, HR_GENERAL (package), the HZ party and location synonyms (HZ_PARTIES, HZ_LOCATIONS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_ORG_CONTACTS, HZ_RELATIONSHIPS), PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, OE_ORDER_HEADERS_ALL, and OE_DROP_SHIP_SOURCES.

PO_LINE_LOCATIONS is the driving table and the source of all shipment scheduling data, including NEED_BY_DATE, PROMISED_DATE, LAST_ACCEPT_DATE, QUANTITY, QUANTITY_CANCELLED, QUANTITY_RECEIVED, PRICE_OVERRIDE, and the fifteen shipment-level DFF attributes. HR_LOCATIONS_ALL and HR_LOCATIONS_ALL_TL supply the ship-to address and location code, while HR_ALL_ORGANIZATION_UNITS and HR_GENERAL support organizational resolution. The HZ objects resolve ship-to contact names through party relationships; PER_ALL_PEOPLE_F and PER_ALL_ASSIGNMENTS_F provide person and assignment context. OE_ORDER_HEADERS_ALL and OE_DROP_SHIP_SOURCES allow the view to recognize drop-shipment sourcing relationships where the purchasing shipment is fulfilled directly by a supplier against a sales order.

Key Columns

Common Use Cases and Queries

Typical uses include diagnosing 860/ORDCHG extract content, reconciling need-by dates reported to trading partners against Purchasing, and building validation queries for e-Commerce Gateway interface troubleshooting.

To inspect need-by dates for a purchase order's shipments:

SELECT shipment_number, shipment_need_by_date, shipment_promised_date, quantity_original, cancelled_flag FROM apps.ece_poco_shipments_v WHERE shipment_need_by_date >= :from_date ORDER BY shipment_need_by_date;

To locate shipments with a missing need-by date before an outbound run:

SELECT shipment_number, shipment_need_by_date, ship_to_location_code FROM apps.ece_poco_shipments_v WHERE shipment_need_by_date IS NULL;

To compare need-by against promised dates for supplier performance analysis:

SELECT shipment_number, shipment_need_by_date, shipment_promised_date, shipment_promised_date - shipment_need_by_date date_variance FROM apps.ece_poco_shipments_v WHERE shipment_promised_date IS NOT NULL;

Because the view is private and specifically shaped for the 860 outbound transaction, it should be queried read-only and not modified. Custom reporting should preferably join PO_LINE_LOCATIONS directly when full flexibility is required.