Results for “ship_to_postal_code”

18 results




Overview
Explore in AI Chat

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

Overview

ECE_POO_SHIPMENTS_V is a private, active view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the e-Commerce Gateway (EC) product and associated with the Purchasing (PO) product family. Its documented display name is "Purchase Order Shipment View." The view extracts shipment-level information for the outbound Purchase Order (850/ORDERS) transaction, meaning it supplies the shipment (schedule) segment of the EDI 850 document that Oracle transmits to suppliers. Within the e-Commerce Gateway architecture, this view functions as a data source for the outbound order mapping and extraction programs, presenting shipment scheduling, shipping destination, and delivery contact details in a flat, transaction-oriented format suitable for translation into EDI segments.

Underlying Base Objects

The view is defined primarily over PO_LINE_LOCATIONS, aliased POLL, which is the authoritative Purchasing table for shipment/schedule lines. Each row in PO_LINE_LOCATIONS carries one shipment number and its associated quantity, dates, and shipping controls. The ship-to address and contact data are resolved through HR_LOCATIONS_ALL (HRL, synonym over HR_LOCATIONS_ALL_TL) for location code and address lines, and through PER_ALL_PEOPLE_F / PER_ALL_ASSIGNMENTS_F (PPF) for the ship-to contact name. Documented referenced base objects also include HR_ALL_ORGANIZATION_UNITS, HR_GENERAL, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_ORG_CONTACTS, HZ_PARTIES, HZ_RELATIONSHIPS, OE_DROP_SHIP_SOURCES, and OE_ORDER_HEADERS_ALL. These Trading Community Architecture (HZ) and Order Management (OE) objects support customer, organization contact, and drop-ship resolution paths, allowing the view to surface a consistent ship-to destination for both standard and drop-ship purchase orders.

Key Columns

Common Use Cases and Queries

The view is used to verify and troubleshoot shipment-level data before or after an outbound 850 run, and to inspect the ship-to location code resolved for a given schedule. A typical query filters by shipment number or location code:

  • SELECT shipment_number, ship_to_location_code, ship_to_city, shipment_need_by_date FROM ece_poo_shipments_v WHERE ship_to_location_code = :location_code;
  • SELECT shipment_number, quantity_original, quantity_cancelled, cancelled_flag FROM ece_poo_shipments_v WHERE cancelled_flag = 'Y';
  • SELECT shipment_number, ship_to_contact_last_name, ship_to_address_line_1 FROM ece_poo_shipments_v WHERE shipment_number = :shipment_num;

Because the view is private and intended for the e-Commerce Gateway extraction layer, direct custom use should be limited to diagnostics and validation, with the understanding that its column list is driven by the EDI 850 shipment mapping.