Results for “po_headers_v”

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

Overview

PO_HEADERS_V is an Oracle E-Business Suite view owned by the APPS schema within the Purchasing (PO) product family. It is documented in ETRM as a 10SC-only object, meaning its presence and behaviour are tied to the Discrete Industries / Supply Chain configuration rather than the standard commercial Purchasing deployment. The view exposes purchasing document header information by projecting a defined subset of columns from the PO_HEADERS entity, enriched with denormalised values derived from lookups, vendor, site, contact, location, currency, and personnel sources.

Functionally, the view presents a single row per purchasing document header — quotations, RFQs, blanket agreements, contracts, and standard purchase orders — with descriptive flexfield attributes, approval and acceptance indicators, control flags, and currency and rate information. In EBS reporting and integration contexts it serves as a simplified, security-aware projection of header data, allowing concurrent programs, extensions, and third-party interfaces to retrieve purchasing header details without joining the full normalised set of PO base tables.

Underlying Base Objects

The view is defined primarily over PO_HEADERS (referenced as a synonym in APPS). Around that anchor the ETRM metadata lists the following referenced objects: AP_TERMS, GL_DAILY_CONVERSION_TYPES, PO_DOCUMENT_TYPES_ALL_B and PO_DOCUMENT_TYPES_ALL_TL, PO_DOC_STYLE_HEADERS, PO_LOOKUP_CODES, PO_VENDORS, PO_VENDOR_CONTACTS, PO_VENDOR_SITES_ALL, HR_LOCATIONS_ALL_TL, PER_PEOPLE_F, and the PL/SQL packages FND_GLOBAL, HR_GENERAL, HR_PERSON_NAME, HR_SECURITY, and PO_HEADERS_SV3.

The foreign-key style relationships are evident from the join keys returned by the view: VENDOR_ID and VENDOR_SITE_ID resolve through the vendor views, VENDOR_CONTACT_ID through PO_VENDOR_CONTACTS, SHIP_TO_LOCATION_ID and BILL_TO_LOCATION_ID through HR_LOCATIONS_ALL_TL, TERMS_ID through AP_TERMS, RATE_TYPE through GL_DAILY_CONVERSION_TYPES, and AGENT_ID through PER_PEOPLE_F. The lookup code columns are translated via PO_LOOKUP_CODES, while the HR_SECURITY package applies organisation-level access control. The PO_HEADERS_SV3 package supplies derived or secured values consistent with the Purchasing document security model.

Key Columns

• PO_HEADER_ID, SEGMENT1–SEGMENT5, TYPE_LOOKUP_CODE — primary identifier, document number segments, and document type (e.g. PO, blanket, contract, quotation).
• VENDOR_ID, VENDOR_SITE_ID, VENDOR_CONTACT_ID — supplier, purchasing site, and contact references.
• AUTHORIZATION_STATUS, APPROVED_FLAG, APPROVED_DATE, USER_HOLD_FLAG, CANCEL_FLAG, FROZEN_FLAG, CLOSED_CODE, CLOSED_DATE — approval workflow and lifecycle status indicators.
• ACCEPTANCE_REQUIRED_FLAG, ACCEPTANCE_DUE_DATE, CONFIRMING_ORDER_FLAG, SUMMARY_FLAG, ENABLED_FLAG — control flags governing acceptance and document behaviour.
• CURRENCY_CODE, RATE_TYPE, RATE, RATE_DATE, AMOUNT_LIMIT, MIN_RELEASE_AMOUNT, BLANKET_TOTAL_AMOUNT — currency, exchange rate, and monetary limits.
• SHIP_TO_LOCATION_ID, BILL_TO_LOCATION_ID, TERMS_ID, FOB_LOOKUP_CODE, FREIGHT_TERMS_LOOKUP_CODE, SHIP_VIA_LOOKUP_CODE — shipping, billing, and commercial terms.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, REVISION_NUM, REVISED_DATE — audit and revision tracking.
• PROGRAM_ID, PROGRAM_APPLICATION_ID, REQUEST_ID, PROGRAM_UPDATE_DATE — concurrent request lineage for integrated processes.

Common Use Cases and Queries

Typical uses include supplier performance reporting, open commitment analysis, contract expiry monitoring, and inbound interface validation. The view is particularly convenient where only header-level fields are required and the standard security predicates applied through HR_SECURITY must be honoured.

List active standard purchase orders for a supplier:

• SELECT poh.segment1, poh.type_lookup_code, poh.authorization_status, poh.currency_code, poh.blanket_total_amount FROM po_headers_v poh WHERE poh.vendor_id = :p_vendor_id AND poh.type_lookup_code = 'STANDARD' AND poh.closed_code = 'OPEN';

Identify contracts approaching expiry with their terms and currency rate:

• SELECT poh.segment1, poh.start_date, poh.end_date, poh.terms_id, poh.rate_type, poh.rate FROM po_headers_v poh WHERE poh.type_lookup_code IN ('BLANKET','CONTRACT') AND poh.end_date BETWEEN SYSDATE AND SYSDATE + 90 AND poh.enabled_flag = 'Y';

Trace documents generated by a concurrent request for reconciliation purposes:

• SELECT poh.po_header_id, poh.segment1, poh.request_id, poh.program_id, poh.creation_date FROM po_headers_v poh WHERE poh.request_id = :p_request_id ORDER BY poh.creation_date;

Because the view is documented for 10SC configurations only, consumers should confirm availability against the target EBS release and instance before embedding it in production integrations.