Search Results access_level_code




Overview
Explore in AI Chat

Overview

POS_ORDER_SUMMARY_V is a reporting view owned by the APPS schema within the POS (iSupplier Portal) product of Oracle E-Business Suite. It presents a consolidated, supplier-facing summary of blanket and planned purchase order release information. Its principal design intent is to expose the header and release attributes that an external supplier requires when viewing orders and releases through the iSupplier Portal, while also surfacing the document security and access classification values carried on the underlying purchasing document type.

Because the view is defined over the archive editions of the purchasing tables (PO_HEADERS_ARCHIVE_ALL and PO_RELEASES_ARCHIVE_ALL), it reflects externally released and latest-external-flag rows rather than live transactional records. This makes it suitable for downstream reporting, portal page rendering, and integration extracts that require a stable, archival snapshot of buyer-specified order data. The view is documented as VALID in EBS 12.1.1 and 12.2.2.

In iSupplier Portal, the view supports the order summary display seen by suppliers, including approval status, revision information, agent name, vendor and site names, currency, and the release total. Significantly for security-related searches, it exposes the columns PDTA.SECURITY_LEVEL_CODE and PDTA.ACCESS_LEVEL_CODE sourced from the PO document type definition, allowing portal logic and reports to filter or categorize supplier visibility by the security and access classification configured for the document subtype.

Underlying Base Objects

The view joins several documented base objects:

The join to PO_DOCUMENT_TYPES_ALL_B is the mechanism through which SECURITY_LEVEL_CODE and ACCESS_LEVEL_CODE become available on each order row.

Key Columns

  • APPROVED_DATE, AUTHORIZATION_STATUS, REVISED_DATE, REVISION_NUM, RELEASE_NUM, RELEASE_TYPE — approval, revision, and release lifecycle data.
  • AGENT_ID plus the POS_GET-derived agent name — identify the responsible buyer.
  • VENDOR_NAME, VENDOR_SITE_CODE, VENDOR_ID, VENDOR_SITE_ID, VENDOR_CONTACT_ID — supplier identification.
  • CURRENCY_CODE and the formatted release total — monetary context for the release.
  • SEGMENT1 || '-' || RELEASE_NUM — composite document number.
  • SECURITY_LEVEL_CODE, ACCESS_LEVEL_CODE — security and access classification inherited from the purchasing document type, central to controlling supplier visibility.
  • ORG_ID — operating unit discriminator, essential for multi-org data filtering.
  • ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield content carried through from the release.

Common Use Cases and Queries

Typical usage includes supplier portal page rendering, order summary reporting, and extracts that must honor document security classification. A representative query retrieving security-level metadata alongside order detail is:

  • SELECT segment1 || '-' || release_num AS document_number, vendor_name, authorization_status, security_level_code, access_level_code, org_id FROM apps.pos_order_summary_v WHERE org_id = :p_org_id AND security_level_code IS NOT NULL;
  • SELECT vendor_name, COUNT(*) FROM apps.pos_order_summary_v WHERE security_level_code = :p_level GROUP BY vendor_name;
  • SELECT document_number, approved_date, revised_date FROM apps.pos_order_summary_v WHERE release_type = :p_type ORDER BY approved_date DESC;

Because the view already restricts rows to latest external archive records for blanket and planned orders, consumers need not re-apply those filters, though ORG_ID and, where relevant, SECURITY_LEVEL_CODE predicates remain advisable for downstream security enforcement.