Search Results oe_header_payment_util




Overview
Explore in AI Chat

Overview

OE_HEADER_PAYMENT_UTIL is a utility PL/SQL package in the APPS schema that centralizes programmatic access to payment information held at the order header level in Oracle Order Management. It is classified as a UTIL-layer API, meaning it is not intended as an externally supported public interface but rather as a shared internal service that other Order Management packages, forms, and validation routines call to manipulate header payment records. The package primarily operates against the OE_PAYMENTS table and its associated interface structures, providing a consistent, single point of control for inserting, updating, deleting, querying, and locking payment rows tied to a sales order header.

A significant part of the package's responsibility is the conversion between database rows and the Order Management public API record structures. The presence of OE_ORDER_PUB and OE_AK_HEADER_PAYMENTS_V among its dependencies confirms that OE_HEADER_PAYMENT_UTIL bridges persistent payment data and the standardized API record type used throughout the module.

Key Procedures and Functions

The package exposes eighteen documented procedures and functions:

Tables Accessed

The package works against several core and supporting tables. OE_PAYMENTS is the primary store for header-level payment records. OE_ORDER_HEADERS and OE_ORDER_HEADERS_ALL supply and validate the owning order context. Hold-related logic references OE_ORDER_HOLDS, OE_HOLD_SOURCES, and OE_HOLD_RELEASES. Payment instrument data is drawn from the IBY payment tables — IBY_CREDITCARD, IBY_PMT_INSTR_USES_ALL, and IBY_FNDCPT_TX_EXTENSIONS. PLITBLM is used for PL/SQL table (index-by table) handling.

Usage Notes

OE_HEADER_PAYMENT_UTIL is invoked indirectly rather than directly by end users. It is referenced by nine other packages, including OE_ORDER_PVT, OE_ORDER_GRP, OE_DEFAULT_HEADER_PAYMENT, OE_HEADER_PAYMENT_SECURITY, OE_ORDER_COPY_UTIL, and OE_HEADER_PAYMENT_CL_DEP_ATTR, as well as the form-level package OE_OE_FORM_HEADER_PAYMENT. Consequently it fires whenever header payments are created, defaulted, copied, validated, or modified through the Order Management forms, order copy logic, or dependent-attribute processing. Custom code should treat the package as an internal implementation detail and prefer the supported OE_ORDER_PUB interfaces, since the utility layer is subject to change between releases.