Search Results create_deliveryrecord




Overview
Explore in AI Chat

Overview

PO_RELGEN_PKG is a VALID PL/SQL package owned by the APPS schema in Oracle E-Business Suite and is documented for both release 12.1.1 and 12.2.2. The name reflects its core purpose: release generation (RELGEN) for Oracle Purchasing. The package implements the business logic that transforms an approved blanket purchase agreement (or, in specific flows, a requisition-driven demand) into one or more released purchase order documents, and it maintains the supply, shipment, and accounting context that those releases require.

Functionally, PO_RELGEN_PKG couples the sourcing rules held in Oracle Purchasing with the transactional tables that store headers, lines, shipments, and releases. It is classified as an API of type OTHER in the ETRM metadata, indicating it is an internal engine rather than a formally published public interface, although it is callable by other Oracle modules and by extensions. Eleven documented procedures and functions constitute its documented surface, and the dependency list confirms it reads configuration from financials and purchasing system parameters while writing release documents into the purchasing schema.

Key Procedures and Functions

The documented program units cover the full release-creation lifecycle:

  • GET_ASL_ID — resolves the Approved Supplier List entry that authorizes sourcing for the item/ supplier/ organization combination, providing the ASL context used during release creation.
  • CREATE_RELEASES — the top-level driver that generates one or more releases for a given agreement or demand within a single invocation.
  • CREATE_RELEASE_HEADER — creates the release header record, populating document-level attributes inherited from the source agreement.
  • CREATE_RELEASE_SHIPMENT — creates the shipment and line-level detail associated with a release, including scheduling and quantity information.
  • OE_DROP_SHIP — supports the drop-shipment flow, where an order management demand is sourced directly from a supplier rather than through inventory.
  • MAINTAIN_SUPPLY — reconciles and maintains the supply picture, ensuring the newly created release is reflected in the supply and sourcing records.
  • GET_RCV_CONTROLS — retrieves receiving controls from the receiving parameters, which govern how the resulting release must be received.
  • GET_INVOICE_MATCH_OPTION — determines the invoice matching rule (for example, two-way, three-way, or four-way) applicable to the release.
  • GET_BEST_PRICE — derives the applicable price for the release, typically from the agreement price breaks or sourcing rules.
  • CREATE_DELIVERYRECORD — creates the associated delivery record used in the delivery-based receiving flows.
  • WRAPUP — performs post-processing and cleanup, finalizing the transaction state after the release documents have been written.

Tables Accessed

The package references a broad set of APPS synonyms. Sourcing and rule evaluation uses PO_AUTOSOURCE_DOCUMENTS, PO_AUTOSOURCE_RULES, and PO_ASL_ATTRIBUTES_VAL_V. Document creation and maintenance touches PO_HEADERS and PO_HEADERS_ALL, PO_LINES, PO_RELEASES, PO_REQUISITION_HEADERS, PO_REQUISITION_LINES, and PO_REQUISITION_LINES_ALL. Configuration and control values come from PO_SYSTEM_PARAMETERS, FINANCIALS_SYSTEM_PARAMETERS (and FINANCIALS_SYSTEM_PARAMS_ALL), GL_PERIOD_STATUSES for period validation, RCV_PARAMETERS for receiving controls, and AP_TAX_CODES_ALL for tax derivation. Supplier information is read from PO_VENDORS. The dependency list also records a reference to PO_PCARD_PKG, indicating the package participates in procurement card and related payment flows.

Usage Notes

PO_RELGEN_PKG is normally invoked indirectly. Standard entry points include the Oracle Purchasing Release form and the AutoCreate / release-generation concurrent programs that create releases against blanket agreements and global agreements. The presence of OE_DROP_SHIP and CREATE_DELIVERYRECORD confirms that Order Management drop-ship flows also call into this package, as does the requisition-to-release path. Because the package is listed as referenced by zero other packages, its callers are forms, concurrent programs, and seeded workflows rather than other PL/SQL packages. Custom code that needs to generate releases programmatically should be built on the supported public purchasing APIs where available; direct calls into PO_RELGEN_PKG should be treated as an internal integration, tested carefully on the target release (12.1.1 or 12.2.2), and re-validated after patching, since the package is not a formally published interface and its behavior is governed by the seeded purchasing and financials configuration it reads.