Results for “authorization_status”

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

Overview

The PO_POS_ALL_V view is an APPS-owned database object within the Purchasing (PO) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its ETRM documentation designates it as "10SC ONLY - Retrofitted," indicating that the object originated from a specialized localization or vertical build (10SC) and was subsequently retrofitted into the standard application schema. Despite this origin note, the view is a fully valid, deployed object in the APPS schema.

Functionally, PO_POS_ALL_V presents a consolidated, user-facing projection of purchase order headers and their associated descriptive attributes. It joins document header data to vendor information, document type classifications, approval (authorization) status descriptions, operating unit names, and purchasing agent employee names. The view is intended for reporting and integration scenarios in which a denormalized, human-readable representation of purchasing documents is required without navigating the multiple underlying transactional tables directly. It surfaces records for standard purchase orders, planned orders, blanket purchase agreements, and contracts, filtered and decorated through Oracle's lookup and multi-organization security mechanisms.

Underlying Base Objects

The view is defined over the following documented base objects, resolved through APPS synonyms or package calls:

• PO_HEADERS_ALL — the primary driver table, supplying the purchase order header rows.
• PO_DOCUMENT_TYPES_ALL_B and PO_DOCUMENT_TYPES_ALL_TL — document type and subtype definitions, with the translation table supplying the language-specific type name.
• AP_SUPPLIERS (referenced in documentation as PO_VENDORS) — supplier master data, joined via an outer join on VENDOR_ID.
• FND_LOOKUP_VALUES — two references, one for the PO TYPE lookup and one for AUTHORIZATION STATUS, providing the displayed meanings.
• HR_ALL_ORGANIZATION_UNITS_TL — the operating unit name for the header's ORG_ID.
• PO_GA_ORG_ASSIGNMENTS — used in the global agreement organization security logic.
• FINANCIALS_SYSTEM_PARAMETERS — provides the set of ORG_IDs against which multi-org access is validated.
• FND_GLOBAL (package) — supplies LOOKUP_SECURITY_GROUP and language context.
• PO_EMPLOYEES_SV (package) — resolves the purchasing agent's display name.
• HZ_PARTIES — referenced for party-related supplier information.

Key Columns

• SEGMENT1 — the purchase order number.
• PO_HEADER_ID — the unique header identifier, used for joins and drill-down.
• TYPE_NAME — the language-specific document type/subtype description.
• TYPE_LOOKUP_CODE — the internal code (STANDARD, PLANNED, BLANKET, CONTRACT).
• VENDOR_NAME and VENDOR_ID — supplier identification.
• AGENT_ID and the employee-name function result — the buyer/agent responsible.
• AUTHORIZATION_STATUS and AUTHORIZATION_STATUS_DSP — approval state code and its displayed meaning.
• DISPLAYED_FIELD — the PO TYPE lookup meaning.
• GLOBAL_AGREEMENT_FLAG — indicates whether the document is a global agreement.
• ORG_ID and NAME (operating unit name) — multi-organization context.
• CREATION_DATE, COMMENTS, SECURITY_LEVEL_CODE — audit, descriptive, and security classification attributes.

Common Use Cases and Queries

Typical uses include purchasing document listings, agent workload reports, approval status dashboards, and supplier-facing extracts.

• List all open blanket agreements for the current operating unit.
• Report purchase orders by buying agent name and authorization status.
• Extract supplier and document type details for integration into downstream systems.

SELECT segment1, type_name, vendor_name,
       authorization_status_dsp, name
  FROM po_pos_all_v
 WHERE type_lookup_code = 'BLANKET'
   AND authorization_status = 'APPROVED';

SELECT agent_id, COUNT(*) po_count
  FROM po_pos_all_v
 WHERE creation_date >= SYSDATE - 30
 GROUP BY agent_id;

Because the view enforces multi-organization and lookup security filters internally, querying it directly returns only data the session is entitled to view.