Results for “user_hold_flag”

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

Overview

POS_VIEW_PO_SUMMARY_V is a reporting view owned by the APPS schema within the iSupplier Portal (POS) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to present a consolidated summary of purchase orders sourced from the archived purchasing tables, allowing historical procurement documents to be surfaced alongside their active counterparts. Because the view draws on the archive headers rather than the live operational tables alone, it is particularly useful for supplier-facing inquiries, audit history, and reconciliation where documents may have been archived out of the primary transactional tables. The view joins vendor, vendor site, organization, and document-type information so that a single row presents a denormalized, human-readable purchase order summary rather than a set of foreign keys.

The most frequently searched attribute against this object is po_num, which the view exposes as an alias for the SEGMENT1 column of the purchase order header. This mirrors the visible purchase order number that end users recognize, and it also supplies a parallel SEGMENT1 column for compatibility with other query patterns.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is defined over several documented base objects:

• PO_HEADERS_ARCHIVE_ALL — the primary source of archived purchase order header data (aliased POH).
• PO_HEADERS_ALL — joined to the archive header on PO_HEADER_ID to confirm the document definition.
• PO_VENDORS and PO_VENDOR_SITES_ALL — supply vendor name, vendor number, and vendor site code.
• HR_ALL_ORGANIZATION_UNITS_TL — supplies the operating unit name.
• PO_DOCUMENT_TYPES_ALL_B — supplies the security and access level codes for the document type.
• FND_MESSAGE_CACHE — a package used to translate document type lookup codes into user-facing type names.
• FND_GLOBAL — the standard EBS context package referenced for session and organization context.

Additional objects listed in the metadata include PO_DOCUMENT_TYPES_ALL, PO_DOC_STYLE_HEADERS, and PO_RELEASES_ARCHIVE_ALL, which support document type and release information.

Key Columns

• PO_NUM (aliased from POH.SEGMENT1) — the visible purchase order number, the most-searched column.
• SEGMENT1 — the same underlying order number, exposed under its technical name.
• PO_HEADER_ID — unique identifier of the purchase order header.
• VENDOR_NAME, VENDOR_NUMBER, VENDOR_SITE_CODE — supplier identification details.
• TYPE_LOOKUP_CODE and TYPE_NAME — the document type; TYPE_NAME is decoded via FND_MESSAGE_CACHE into descriptions such as Standard, Blanket, Contract, or Planned.
• CLOSED_CODE — defaults to 'OPEN' where the header value is null.
• CURRENCY_CODE, ORG_ID, ORG_NAME — financial and operating unit context.
• APPROVED_DATE, ACCEPTANCE_DUE_DATE, CREATION_DATE — key procurement dates.
• ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY — descriptive flexfield values.
• PO_RELEASE_ID and RELEASE_NUM — returned as NULL, indicating this view summarizes headers rather than releases.

Common Use Cases and Queries

A typical use is retrieving a purchase order summary by its visible number. The following query returns the order, vendor, and status:

• SELECT po_num, vendor_name, type_name, closed_code, currency_code FROM pos_view_po_summary_v WHERE po_num = '12345';
• SELECT po_num, vendor_name, approved_date FROM pos_view_po_summary_v WHERE vendor_name LIKE 'Acme%' ORDER BY approved_date DESC;
• SELECT po_num, org_name, type_name FROM pos_view_po_summary_v WHERE org_id = :p_org_id;

These patterns support supplier portal displays, archived order lookups, and ad hoc reporting against historical procurement data.