Search Results get_po_header_id

Overview

APPS.PO_HEADERS_SV3 is a server-side PL/SQL package in Oracle E-Business Suite Purchasing that provides lightweight, read-only access to core attributes of a purchasing document header. Its name follows the standard EBS "SV" (server view) convention, signifying a utility package whose routines are designed to be called from SQL statements, views, forms, and other PL/SQL units rather than to perform transactional DML. The package is declared with AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the invoking schema rather than the defining APPS schema, which is typical of shared utility packages that must respect the caller's security context. In the 12.1.1 and 12.2.2 releases, PO_HEADERS_SV3 is classified as an "OTHER" API and is referenced by eleven other packages within the application, indicating its role as a foundational helper for retrieving header-level facts such as currency, document number, and security level. Because it encapsulates simple lookups, it spares calling code from embedding repetitive queries against PO_HEADERS_ALL directly.

Key Procedures and Functions

The documented public interface includes several routines:

• get_security_level_code — Returns the security level code applicable to a given purchasing document type and sub-type. It accepts the PO type and sub-type as inputs and returns the resulting security level code through an IN OUT NOCOPY parameter. This supports the Purchasing document security model, where access to a document can be governed by an assigned security level.
• test_get_security_level_code — A standalone test/diagnostic procedure used to exercise and validate get_security_level_code during development and regression testing. It is not intended for production call paths.
• get_currency_code — A function that accepts a PO header identifier and returns the currency code for that purchasing document. The ETRM excerpt explicitly notes this is used in the PO_LINE_LOCATIONS_RELEASE_V view, confirming its role in view-based data retrieval.
• get_currency_info — A procedure that, given a PO header identifier, returns the full currency context for the document, including the currency code, rate type, rate date, and exchange rate. This consolidates header currency attributes in a single call.
• get_doc_num — Obtains the document number associated with a given PO header identifier, returning it through an IN OUT VARCHAR2 parameter.

The procedures consistently key on po_header_id, which is why a search for "get_po_header_id" surfaces this package as a relevant entry point for header lookups.

Tables Accessed

The package reads from the following documented tables via APPS synonyms:

• PO_HEADERS_ALL — The primary Purchasing document header table. It supplies currency code, rate type, rate date, rate, and document number information for a given po_header_id, and its columns are used as the anchored %TYPE definitions for the package parameters.
• PO_DOCUMENT_TYPES — Provides the document type and sub-type context used by get_security_level_code to derive the applicable security level.
• DUAL — Utilized for simple single-row computations or constant evaluations within the PL/SQL logic.

Because the package is read-oriented, it does not perform inserts or updates against these tables.

Usage Notes

PO_HEADERS_SV3 is typically invoked as a helper layer rather than as an end-user entry point. Its functions are suited to embedded SQL and view definitions — the metadata cites PO_LINE_LOCATIONS_RELEASE_V — where a currency code must be resolved from a header identifier at query time. Oracle Forms and OAF pages that display purchasing documents can call the currency and document-number routines to populate descriptive fields without duplicating header logic. Concurrent programs and custom extensions benefit from the consolidated get_currency_info call when they require the exchange rate context for revaluation, conversion, or reporting. The security-level routine is relevant to implementations using document security. Developers should note the AUTHID CURRENT_USER declaration, which means results depend on the caller's granted privileges to PO_HEADERS_ALL and PO_DOCUMENT_TYPES. As with all SV packages, it should be treated as an internal utility: signature behavior is tied to the EBS release level, and direct modification is unsupported.