Search Results po_temp_labor_headers_v




Overview
Explore in AI Chat

Overview

PO_TEMP_LABOR_HEADERS_V is an APPS-owned database view within the Oracle E-Business Suite Purchasing (PO) module. It presents a consolidated header-level result set covering approved standard purchase orders that contain at least one temporary labor line. The view is read-only in nature and serves as a reporting and integration surface, allowing developers, report authors, and interface programs to retrieve header information for temp labor POs without having to reassemble the joins across purchasing, HR, and vendor tables manually.

The view exposes a curated projection of columns rather than the full PO_HEADERS_ALL record. Each row represents a single approved purchase order header, enriched with operating unit name, business group identifier, PO document type name, vendor and vendor site details, buyer identity, and the displayed authorization status. This makes it particularly suitable for Business Intelligence Publisher reports, Oracle Discoverer workbooks, OBIEE repository layers, and custom concurrent programs where a flat, denormalized result is preferred.

Because the view filters on AUTHORIZATION_STATUS in ('APPROVED','PRE-APPROVED') and APPROVED_FLAG = 'Y', it intrinsically excludes unapproved, rejected, cancelled, frozen, and disabled documents. Consumers therefore do not need to reapply those business filters.

Underlying Base Objects

The view is defined over the following documented base objects:

Key Columns

The view exposes a header-identification and descriptive column set. Important columns include:

  • PO_NUMBER — the user-visible SEGMENT1 purchase order number.
  • PO_HEADER_ID — the internal primary key, useful for drill-down joins to PO_HEADERS_ALL or PO_LINES_ALL.
  • OPERATING_UNIT_NAME — the translated name of the HR organization unit acting as the operating unit.
  • BUSINESS_GROUP_ID — the business group associated with the operating unit.
  • PO_TYPE — the translated document type name (for example, Standard Purchase Order).
  • AUTHORIZATION_STATUS_DSP — the displayed authorization status description derived from PO_LOOKUP_CODES; this is the column frequently referenced by the search term "authorization_status_dsp".
  • VENDOR_ID, VENDOR_SITE_ID, VENDOR_NAME, VENDOR_SITE_NAME — vendor identification and descriptive fields.
  • BUYER_ID, BUYER_FULL_NAME — the purchasing agent and their current full name from PER_ALL_PEOPLE_F.

Common Use Cases and Queries

Typical scenarios include reporting on temp labor spend by buyer, vendor, or operating unit; populating an interface table with approved temp labor PO headers; and validating document status before downstream processing.

A representative query retrieving headers for a given operating unit and vendor:

  • SELECT PO_NUMBER, OPERATING_UNIT_NAME, PO_TYPE, AUTHORIZATION_STATUS_DSP, VENDOR_NAME, BUYER_FULL_NAME FROM PO_TEMP_LABOR_HEADERS_V WHERE OPERATING_UNIT_NAME = :p_org AND VENDOR_ID = :p_vendor ORDER BY PO_NUMBER;
  • SELECT BUYER_FULL_NAME, COUNT(*) FROM PO_TEMP_LABOR_HEADERS_V GROUP BY BUYER_FULL_NAME;
  • SELECT PO_NUMBER, AUTHORIZATION_STATUS_DSP FROM PO_TEMP_LABOR_HEADERS_V WHERE AUTHORIZATION_STATUS_DSP = :p_status;

Because the view already restricts to approved standard temp labor POs, these queries remain concise and performant when supported by existing indexes on PO_HEADERS_ALL and PO_LINES_ALL.