Search Results apply_changes

Overview

PO_HEADERS_DRAFT_PVT is a private (PVT-classified) PL/SQL package in the Oracle Purchasing module of Oracle E-Business Suite. Its central business function is to manage and reconcile changes made to purchase order headers while those changes are still held in a draft state. In Oracle Purchasing, buyers can save modifications to an existing purchase order as a draft rather than committing them directly to the live document. This draft mechanism allows changes to be staged, reviewed, and validated before they are promoted to the actual purchase order. PO_HEADERS_DRAFT_PVT provides the internal programmatic logic that detects whether such draft changes exist and, when appropriate, applies those staged changes to the live purchase order header records.

The package carries the AUTHID CURRENT_USER designation and is owned by APPS. The header comment indicates a fairly stable code line, with the earliest referenced revision dated 2005. It is classified as a private API, meaning it is intended for internal use by Oracle Purchasing components rather than as a public interface for customer extensions.

Key Procedures and Functions

The documented package metadata lists three callable program units: DRAFT_CHANGES_EXIST (two overloaded functions) and APPLY_CHANGES (one procedure).

• DRAFT_CHANGES_EXIST (overloaded): This function determines whether pending draft modifications exist for one or more purchase order headers. Two overloads are documented, one operating on table-based collections of draft identifiers and purchase order header identifiers, and one operating on single scalar values. It returns a boolean-like indicator, allowing callers to branch logic based on whether a draft contains unapplied changes. This is typically used to decide whether a draft workflow should proceed, prompt user confirmation, or skip processing when no changes are present.
• APPLY_CHANGES: This procedure performs the core commit action of the package. It takes a draft information record and promotes the staged header-level changes into the live purchase order header data. It is the point at which a draft transitions from a provisional state to an applied state. The procedure relies on a record type defined externally in PO_DRAFTS_PVT (DRAFT_INFO_REC_TYPE), indicating tight coupling with the broader draft handling framework.

Tables Accessed

The package references several tables through APPS synonyms. PO_HEADERS_ALL is the base table storing the live purchase order header records and is the primary target when changes are applied. PO_HEADERS_DRAFT_ALL holds the draft version of those header changes, and the package reads this table to detect and source pending modifications. PO_SESSION_GT is a global temporary table used to hold session-level working data during processing. DUAL is referenced for trivial single-row operations common in PL/SQL logic. PLITBLM is an Oracle Applications-supplied table typically used for message and string manipulation. Together these tables support the full lifecycle of identifying draft content and writing it to the live header records.

Usage Notes

As a private API, PO_HEADERS_DRAFT_PVT is not documented for direct customer invocation. It is most commonly called from the Oracle Purchasing forms (such as the Purchase Orders window) and from internal concurrent or workflow programs that handle the draft approval and application cycle. The DRAFT_CHANGES_EXIST functions are used defensively to determine whether applying or displaying changes is necessary, while APPLY_CHANGES executes the actual promotion. Because the metadata indicates the package is referenced by two other packages, it forms part of a layered dependency chain within the Purchasing draft-handling subprograms. Custom developers should avoid calling this package directly and should instead rely on supported public APIs; direct calls risk incompatibility across EBS 12.1.1 and 12.2.2 releases and may bypass validation logic enforced elsewhere in the draft framework.