Search Results po_headers_sv4




Overview
Explore in AI Chat

Overview

APPS.PO_HEADERS_SV4 is a server-side PL/SQL package in Oracle E-Business Suite Purchasing (PO). It is declared with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the calling schema rather than the package owner, so callers must themselves hold the necessary grants on the underlying PO tables and views. The package belongs to the family of PO_HEADERS server-side validation and utility units whose names carry the SV (server validation) prefix and are suffixed with a version number. These units encapsulate reusable derivations and validations over purchasing document headers so that forms, concurrent programs, and other PL/SQL packages do not have to replicate the same lookup and query logic.

The unit is small and tightly scoped. Its documented purpose is to translate and resolve purchasing document type information — returning the human-readable document type name and the corresponding lookup code for a supplied document type code and subtype — and to expose header-level attribute lookups keyed on PO_HEADER_ID. It also supplies quotation and contract related predicates used by higher-level purchasing flows. In 12.1.1 and 12.2.2 the package is classified as OTHER (not a public API), which signals that Oracle does not guarantee its signature across releases; customers should treat it as an internal utility to be read and wrapped rather than modified.

Key Procedures and Functions

The package exposes the following documented units:

  • get_doc_type_lookup_code — The procedure most commonly sought when users search on this identifier. It returns the purchasing document type name and the type lookup code for a given document type code and subtype, populating both values through IN OUT NOCOPY parameters. This is the standard mechanism for converting stored document type codes into displayable names and FND_LOOKUPS-style codes.
  • get_lookup_code_dsp — Resolves the displayed value for a given PO lookup type and lookup code, returning the displayed description through an IN OUT NOCOPY parameter. Created 06-NOV-1995 (WLAU).
  • is_quotation — Returns a BOOLEAN indicating whether the document identified by the supplied header ID is a quotation.
  • get_type_name — Returns the document type name for a given PO_HEADER_ID, typed against PO_DOCUMENT_TYPES_ALL.type_name.
  • get_doc_num — Returns the document number (PO_HEADERS_ALL.segment1) for a given PO_HEADER_ID.
  • get_vendor_quote_num — Returns the vendor quotation number associated with a given PO_HEADER_ID.
  • cumulative_lines_exist — Predicate used to determine whether cumulative lines exist for a document, relevant to blanket and planned purchasing agreements.
  • references_exist — Predicate indicating whether referencing documents exist against a header, used before cancellation or deletion decisions.
  • is_contract_valid — Predicate validating that a contract document is in a valid state for the operation being performed.
  • name — A supporting routine contributing to the package's naming and resolution behavior.

Because several of these are GA FPI (functional programming interface) marked units, they are intended for internal Oracle use and may change.

Tables Accessed

The package reads through APPS synonyms against PO_DOCUMENT_TYPES_ALL and PO_DOCUMENT_TYPES to resolve document type names and lookup codes; PO_HEADERS_ALL (and its PO_HEADERS synonym) to obtain segment1 document numbers and header-level attributes; and PO_LINES_ALL to evaluate whether cumulative lines exist for a document. No direct DML against these tables is documented; the package is read-oriented, supplying values to callers rather than persisting changes.

Usage Notes

PO_HEADERS_SV4 is invoked from Purchasing forms and from other PL/SQL packages — five packages are documented as referencing it — rather than being called directly from SQL, since it exposes BOOLEAN returns and IN OUT NOCOPY parameters that are not SQL-callable. When custom code is needed, the safest approach is to wrap the specific routine required (for example, calling get_doc_type_lookup_code to resolve a document type name) inside a customer-owned package, and to avoid binding to the package signature directly, because the OTHER classification permits Oracle to alter these interfaces between 12.1.1 and 12.2.2 and later releases.