Search Results pos_po_summary_v




Overview
Explore in AI Chat

Overview

POS_PO_SUMMARY_V is a database view owned by the APPS schema in Oracle E-Business Suite, defined within the iSupplier Portal (POS) product family. Its documented purpose is to display all purchase orders, consolidating header-level purchasing data with vendor, vendor site, and agent information into a single denormalized result set suitable for supplier-facing and internal reporting. The view resides in the APPS schema with a status of VALID in both 12.1.1 and 12.2.2.

The view derives its PO_RELEASE_FLAG column from a literal 'PO' value, distinguishing the rows it returns from the corresponding iSupplier Portal summary view used for releases. Because it joins purchase order headers to vendor master and vendor site records and resolves agent names through a cached function call, it serves as a convenient read-only source for listing purchasers, suppliers, terms, and status attributes without requiring callers to reconstruct the multi-table join themselves. It is not a base table and should never be used as a target for DML.

Underlying Base Objects

The view is defined primarily over PO_HEADERS_ALL (accessed through a synonym), supplying the overwhelming majority of its columns. It is joined to PO_VENDORS and PO_VENDOR_SITES_ALL (both views/synonyms) for vendor name and address data, and to AP_TERMS for payment term names. Agent names are retrieved via the POS_GET package function GET_PERSON_NAME_CACHE, and messages for PO type descriptions are resolved through FND_MESSAGE.GET_STRING.

Documented referenced objects also include PO_RELEASES_ALL, PO_ACCEPTANCES, PO_LOOKUP_CODES, PO_INQ_SV, POS_TOTALS_PO_SV, FND_LOOKUP_VALUES_VL, FND_CURRENCY_CACHE, FND_GLOBAL, HR_ALL_ORGANIZATION_UNITS_TL, and HR_LOCATIONS_ALL. These support lookup decoding, currency information, organization and location resolution, and totals or inquiry functionality exposed elsewhere in the iSupplier Portal. The structure therefore reflects a reporting aggregation layer rather than a transactional table.

Key Columns

Common Use Cases and Queries

Typical uses include supplier portal dashboards, buyer workload reports, and integration extracts that require PO header data with vendor address and agent names pre-resolved. A basic inquiry by PO number is shown below.

  • List open purchase orders by supplier: SELECT po_num, vendor_name, authorization_status, closed_code FROM pos_po_summary_v WHERE vendor_name = :vendor AND closed_code = 'OPEN';
  • Buyer workload extract: SELECT agent_name, COUNT(*) FROM pos_po_summary_v WHERE authorization_status = 'APPROVED' GROUP BY agent_name;
  • Supplier site detail for a PO: SELECT po_num, vendor_site_code, address_line1, city, state, zip, country, phone FROM pos_po_summary_v WHERE po_header_id = :header_id;
  • Blanket and contract agreements: SELECT po_num, type_lookup_code, vendor_name FROM pos_po_summary_v WHERE type_lookup_code IN ('BLANKET','CONTRACT');

Because the view references cached package functions and multiple synonyms, query performance benefits from filtering on indexed columns such as PO_HEADER_ID or VENDOR_ID where possible. Reports should be aware that CANCEL_FLAG returns NULL when the underlying flag is 'I' and that several status columns are defaulted, so null-handling logic in downstream code should account for these transformations.