Results for “po_line_locations_draft_pvt”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PO_LINE_LOCATIONS_DRAFT_PVT is a private PL/SQL package in the APPS schema that supports the Oracle EBS Purchasing module's draft management framework. In EBS 12.1.1 and 12.2.2, the Purchasing application allows buyers to create, modify, and stage changes to purchase order lines and shipments without immediately committing them to the transactional tables. This staging mechanism is known as "draft" processing, and it relies on a set of shadow (draft) tables that mirror the core purchasing tables.

PO_LINE_LOCATIONS_DRAFT_PVT specifically manages the shipment or line-location layer of that draft model. A "line location" in Purchasing represents a scheduled shipment of a purchase order line — the combination of ship-to, quantity, promised date, and price. When a buyer edits shipment details in the Enter Purchase Orders form, those edits are written to the draft tables and later merged into the base tables upon approval. This package encapsulates that logic for the line-location draft records, keeping the public-facing packages separated from the internal implementation details. Because it is classified as a private (PVT) API, it is not intended for direct customer invocation; it is called by the public draft packages that orchestrate the overall draft lifecycle.

Key Procedures and Functions

The ETRM metadata documents four procedures or functions within this package. Their documented purposes are as follows:

• DRAFT_CHANGES_EXIST — A function that determines whether any draft changes are pending for the line-location records being processed. It allows the calling draft framework to short-circuit processing when no changes need to be applied, avoiding unnecessary writes.
• APPLY_CHANGES — The central procedure that merges the staged draft line-location records into the base transactional structures. This is the action that promotes a buyer's staged shipment edits to the live purchase order.
• MAINTAIN_RETROACTIVE_CHANGE — A procedure that handles retroactive changes to line-location drafts. Retroactive changes are adjustments that must be recorded against existing, already-established shipments rather than simple forward-going edits.

A fourth documented routine is listed in the metadata count; the excerpt enumerates the above three by name plus supporting package-level logic. No parameter lists are documented, and callers should not assume signatures.

Tables Accessed

Via APPS synonyms, the package references a focused set of tables reflecting its shipment-draft scope:

• PO_LINE_LOCATIONS_DRAFT_ALL — The draft staging table for line locations; this is the primary table the package reads and writes.
• PO_LINE_LOCATIONS_ALL — The permanent line-location table into which draft changes are ultimately applied.
• PO_LINES_DRAFT_ALL — The draft table for the parent purchase order line, needed to correlate shipment-level changes with line-level drafts.
• PO_HEADERS_ALL — The purchase order header table, accessed for context such as document type and status.
• PO_DOC_STYLE_HEADERS — Controls document style behavior, which can influence how drafts are processed.
• PO_SESSION_GT — A global temporary table holding session context used by the purchasing forms and draft framework.
• DUAL and PLITBLM — Standard utility references used for single-row selection and large-table (index-by) handling within PL/SQL.

Usage Notes

PO_LINE_LOCATIONS_DRAFT_PVT is an internal implementation package. The dependency metadata confirms it is referenced by two other packages: PO_DRAFTS_PVT (the overarching draft orchestration package) and PO_LINE_LOCATIONS_DRAFT_PKG. The package in turn references PO_DRAFTS_PVT, indicating a coordinated relationship within the draft subsystem. Its types PO_TBL_NUMBER and PO_TBL_VARCHAR1, along with the SYS.STANDARD and PO_DRAFTS_PVT dependencies, show that it relies on shared collection types and the parent draft package for common logic.

In practice, this package is invoked indirectly whenever a user saves or applies draft changes to purchase order shipments through the Purchasing forms, or when concurrent programs perform draft cleanup or application. Customers and integrators should not call this private package directly; the supported entry point is the public Purchasing API layer, typically PO_DRAFTS_PVT or the corresponding document open/change interfaces. Direct modification of PO_LINE_LOCATIONS_DRAFT_ALL outside this framework can corrupt the draft-to-base reconciliation, so all interaction should flow through the standard draft processing path. Because it is a PVT package, Oracle may change its internals across patch levels, making it unsuitable for custom extensions.