Search Results ship_to_organization_id




Overview
Explore in AI Chat

Overview

POS_ASN_RESULT_V is an Oracle E-Business Suite (EBS) database view owned by the APPS schema and delivered under the ICX – Oracle iProcurement product family. It is a reporting and integration-oriented view that surfaces the working result set of the Advanced Shipment Notice (ASN) search performed within Oracle iProcurement. In EBS 12.1.1 and 12.2.2, iProcurement allows buyers and receiving personnel to locate purchase order shipments eligible for an ASN so that supplier shipment details can be recorded against receipt-bound order lines. The search results are staged, and POS_ASN_RESULT_V exposes that staged set with a denormalized, business-friendly shape.

Because the view carries both identifiers and descriptive attributes — PO number, line number, shipment number, supplier details, ship-to location, item information, and ordered quantity — it serves as a convenient single-row-per-qualifying-shipment source for reporting, extensions, and integration extracts. It is a read-only view and is not intended for direct DML.

Underlying Base Objects

The documented object metadata identifies a single referenced base object: the synonym POS_ASN_SEARCH_RESULT. The view definition is a straight projection from that source:

  • SELECT ... FROM POS_ASN_SEARCH_RESULT — all exposed columns are selected directly from the base synonym, with no joins, filters, groupings, or transformations.

In other words, POS_ASN_RESULT_V is a thin presentation layer. The synonym resolves to the underlying APPS storage where iProcurement materializes the ASN search results for a session. The SESSION_ID column is the mechanism that distinguishes one user's or one search's result set from another's; without constraining by session, the view exposes rows from all populated searches.

Key Columns

The columns fall into logical groupings:

Common Use Cases and Queries

Typical uses include diagnosing why a shipment does or does not appear in the ASN search result set, validating that expected PO shipments are available for ASN entry, and building custom reports that reconcile ordered quantities against shipment schedules. The following sample returns the shipments staged for a given session, ordered by PO and line:

  • SELECT po_number, line_number, shipment_number, supplier_name, item_number, quantity_ordered, unit_of_measure_code, due_date, ship_to_organization_code FROM apps.pos_asn_result_v WHERE session_id = :p_session_id ORDER BY po_number, line_number, shipment_number;

To locate a specific shipment by its number across the staged results:

  • SELECT session_id, po_number, line_number, shipment_number, po_shipment_id, ship_to_location_code FROM apps.pos_asn_result_v WHERE shipment_number = :p_shipment_number;

Because no join logic is present in the view, any enrichment — for example resolving closed or cancelled status from PO tables — must be supplied by the calling query joining back to the appropriate purchasing tables on PO_HEADER_ID, PO_LINE_ID, or PO_SHIPMENT_ID.