Search Results po_headers_sv2




Overview
Explore in AI Chat

Overview

APPS.PO_HEADERS_SV2 is a server-side PL/SQL package body in the Oracle E-Business Suite Purchasing module. It belongs to the family of "SV" (server) packages that encapsulate the business logic used to validate, default, and persist purchasing document headers. Whereas the companion package PO_HEADERS_SV1 provides header-level validation and defaulting routines, PO_HEADERS_SV2 layers additional processing on top of it, most notably contract terms validation, encumbrance retrieval, and supporting utilities invoked during the creation and update of purchase orders, purchase agreements, and releases.

The package is classified as an "OTHER" API in the Oracle ETRM repository rather than as a public, supported interface. Its procedures are therefore intended primarily for internal consumption by Purchasing forms, concurrent programs, and other PL/SQL packages, though they can be called from custom code with appropriate care. It resides in the APPS schema and is marked VALID, confirming it has compiled successfully.

Key Procedures and Functions

The ETRM metadata documents ten procedures and functions within PO_HEADERS_SV2. The relevant entries include:

  • TEST_GET_PO_ENCUMBERED — A diagnostic or utility routine used to retrieve encumbrance information associated with a purchase order. It assists in determining whether funds have been encumbered against a given document, supporting budgetary control integration.
  • VAL_CONTRACT_EFF_DATE — Validates the effective date range applicable to a contract or agreement. It ensures that a purchasing document's dates fall within permissible contract effective periods before the record is accepted.
  • Additional routines — The metadata lists ten documented procedures/functions in total, including the package NAME routine. These complement PO_HEADERS_SV1 by handling header-level derivations and cross-entity checks required before the Purchasing application commits header, line, and schedule data.

Because the ETRM extract truncates the full procedure list and parameter signatures, only the purposes above should be treated as authoritative; parameter lists are deliberately not reproduced here.

Tables Accessed

PO_HEADERS_SV2 reads and writes the core Purchasing tables, all accessed through APPS synonyms:

  • PO_HEADERS / PO_HEADERS_ALL — The primary header tables for purchase orders, agreements, and releases. The package derives and validates header attributes before insert or update.
  • PO_LINES_ALL — Provides line-level context needed for header-level aggregations and validation rules.
  • PO_LINE_LOCATIONS_ALL — Supplies shipment/schedule details used in date and quantity validations.
  • PO_RELEASES — Read to validate and process release documents associated with agreements.
  • PO_REQUISITION_LINES_ALL — Referenced for requisition-to-order linkage and defaulting of sourced attributes.

It additionally depends on PO_HEADERS_SV1, PO_MESSAGE_S, and the PO_LOOKUP_CODES view for error messaging and lookup validation, plus FND_API, FND_GLOBAL, and FND_PROFILE for standard API and profile-option infrastructure.

Usage Notes

PO_HEADERS_SV2 is typically invoked indirectly. The Purchasing forms (such as POXPOEPO and POXPOERL) and the PO_HEADERS_PUB wrapper chain call into PO_HEADERS_SV2 during header processing. Concurrent programs that import or amend purchasing documents, and any custom PL/SQL that must reproduce standard header validations, may call its routines directly. As an "OTHER" classification API it is not covered by Oracle's public API commitment, so customizations should call it defensively, avoid relying on undocumented signatures, and prefer supported entry points such as PO_HEADERS_PUB or the Purchasing open interfaces wherever possible.