Results for “pos_po_arch_summary_v”

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

Overview

POS_PO_ARCH_SUMMARY_V is an APPS-owned database view within the Oracle E-Business Suite iSupplier Portal (POS) product family. Its primary function is to present a consolidated, denormalized summary of purchasing documents — both standard purchase orders and releases — as stored across the live and archived purchasing tables. The view merges purchase order headers from PO_HEADERS_ALL with their archived counterparts in PO_HEADERS_ARCHIVE_ALL, and similarly unifies PO_RELEASES_ALL with PO_RELEASES_ARCHIVE_ALL. This design allows the iSupplier Portal and associated reporting components to expose a single, continuous view of purchasing activity without requiring the caller to query live and archive segments separately.

The object is registered as VALID in the APPS schema and appears in both Oracle EBS 12.1.1 and 12.2.2 environments. Within the ETRM framework it is catalogued as a reporting and integration artifact, supporting supplier-facing summaries and internal purchasing analytics. A distinguishing flag column, PO_RELEASE_FLAG, indicates whether a given row originates from a purchase order header ('PO') or from a release against a blanket agreement.

Underlying Base Objects

The view is defined over a set of documented base objects spanning purchasing, human resources, and shared foundation schemas. The central tables are PO_HEADERS_ALL and PO_HEADERS_ARCHIVE_ALL (SYNONYM), joined to PO_RELEASES_ALL and PO_RELEASES_ARCHIVE_ALL. Vendor and site context is drawn from PO_VENDORS and PO_VENDOR_SITES_ALL (VIEW). Location data arrives via HR_LOCATIONS_ALL, and organization names via HR_ALL_ORGANIZATION_UNITS_TL. Payment terms are resolved through AP_TERMS, while currency and lookup decoding rely on FND_CURRENCY_CACHE, FND_LOOKUP_VALUES_VL, PO_LOOKUP_CODES, and FND_MESSAGE. Several PL/SQL packages are referenced in the view text: POS_GET, POS_TOTALS_PO_SV, PO_ACKNOWLEDGE_PO_GRP, PO_INQ_SV, and FND_GLOBAL, which supply person-name caching, totals computation, acknowledgement logic, inquiry services, and session context respectively.

Key Columns

The view exposes a wide set of descriptive, status, and derived columns:

• PO_RELEASE_FLAG — Literal 'PO', indicating document origin; combined with release-level data elsewhere in the family.
• PO_HEADER_ID, FROM_HEADER_ID, PO_NUM (SEGMENT1), REVISION_NUM — Core document identity and revision tracking.
• AUTHORIZATION_STATUS, CLOSED_CODE, FIRM_STATUS_LOOKUP_CODE, CANCEL_FLAG, FROZEN_FLAG, USER_HOLD_FLAG — Lifecycle and hold-state indicators, several with NVL defaults such as 'INCOMPLETE', 'OPEN', and 'N'.
• VENDOR_NAME, VENDOR_SITE_CODE, VENDOR_ID, VENDOR_SITE_ID, VENDOR_CONTACT_ID — Supplier and shipping site identification.
• AGENT_ID / AGENT_NAME — Buyer identity, with the name resolved via POS_GET.GET_PERSON_NAME_CACHE.
• ADDRESS_LINE1–3, CITY, STATE, ZIP, COUNTRY, PHONE, FAX — Denormalized supplier-site address and formatted contact numbers.
• CURRENCY_CODE, RATE, RATE_TYPE, RATE_DATE — Currency and exchange-rate context.
• Dates — APPROVED_DATE, CLOSED_DATE, FIRM_DATE, REVISED_DATE, PRINTED_DATE, ACCEPTANCE_DUE_DATE, CREATION_DATE, LAST_UPDATE_DATE.
• Descriptive fields — COMMENTS, NOTE_TO_AUTHORIZER, NOTE_TO_RECEIVER, NOTE_TO_VENDOR, TYPE_LOOKUP_CODE, and a decoded document-type name using FND_MESSAGE.GET_STRING.
• Audit/WHO columns — CREATED_BY, LAST_UPDATED_BY, PROGRAM_ID, REQUEST_ID, and related Concurrent Manager fields.

Common Use Cases and Queries

Typical applications include iSupplier Portal summary dashboards, purchasing archive reporting, and supplier-facing document listings that must span live and archived records. A representative query retrieves open, authorized purchase orders for a supplier:

• SELECT po_num, vendor_name, authorization_status, approved_date, agent_name FROM pos_po_arch_summary_v WHERE vendor_id = :p_vendor AND closed_code = 'OPEN' ORDER BY approved_date DESC;
• SELECT po_num, type_lookup_code, currency_code, rate, firm_date FROM pos_po_arch_summary_v WHERE po_release_flag = 'PO' AND authorization_status = 'APPROVED';
• SELECT po_header_id, po_num, vendor_site_code, city, country FROM pos_po_arch_summary_v WHERE agent_id = :p_agent AND frozen_flag = 'N';

Because the view resolves names, addresses, and lookup meanings inline, it reduces the join overhead in downstream reports. Queries should filter by indexed identifiers such as PO_HEADER_ID, VENDOR_ID, or AGENT_ID to avoid full scans across the combined live and archive datasets.