Search Results g_modifier_mechanism_type_code

Overview

OE_HEADER_ADJ_UTIL is a PL/SQL utility package in the APPS schema that supports header-level order adjustment (charge, discount, and promotion) processing within Oracle Order Management. It falls in the UTIL API classification, meaning it is an internal helper package rather than a public business API. Its role is to manipulate and maintain the header adjustment records that Order Management stores against sales orders — records such as freight, surcharges, order-level discounts, and promotional price adjustments. The package provides the low-level plumbing that other order management packages rely on when they must create, change, query, lock, or delete header adjustment rows, and it encapsulates the attribute-change rules and dependent-attribute handling that govern how those records may be modified. Both the 12.1.1 and 12.2.2 ETRM documentation list the object as VALID in the APPS schema, and the documented package exposes 27 procedures and functions.

Key Procedures and Functions

The documented procedures fall into several functional groups. Record construction and conversion routines include API_REC_TO_ROWTYPE_REC and ROWTYPE_REC_TO_API_REC, which translate between the public API record structures and the internal rowtype structures used against OE_AK_HEADER_PRCADJS_V, COMPLETE_RECORD, which populates defaulted or missing attributes, and CONVERT_MISS_TO_NULL, which normalizes missing values. Data manipulation routines include INSERT_ROW, UPDATE_ROW, DELETE_ROW, DELETE_HEADER_CHARGES (which removes the charge records attached to a header), and CLEAR_DEPENDENT_ATTR, which resets dependent attributes that no longer apply after a change. Query and concurrency routines include QUERY_ROW, QUERY_ROWS, GET_VALUES, GET_IDS, LOCK_ROW, and LOCK_ROWS. GET_LINE_ADJUSTMENTS returns the line-level adjustments associated with a header adjustment. APPLY_ATTRIBUTE_CHANGES applies the package's attribute-change logic, while LOG_REQUEST_FOR_MARGIN and LOG_ADJ_REQUESTS record requests for downstream processing of margin calculations and adjustment actions. A package-level global, G_MISS_OE_AK_HEADER_ADJ_REC, holds the missing-value record used by the conversion routines.

Tables Accessed

The package operates against the core Order Management header and adjustment tables accessed through APPS synonyms: OE_ORDER_HEADERS and OE_ORDER_HEADERS_ALL (the header being adjusted), OE_ORDER_LINES_ALL (for line context associated with header adjustments), and OE_PRICE_ADJUSTMENTS and OE_PRICE_ADJS_HISTORY (the transactional adjustment records and their audit history). PLITBLM is used as an Oracle Forms-style global temporary table for list processing. These objects explain the package's focus: it maintains the header-level rows in the pricing adjustment tables while remaining aware of the parent order header and its lines.

Usage Notes

OE_HEADER_ADJ_UTIL is not intended to be called directly by customers or integrators; it is invoked by other Order Management packages and by the Order Management forms. The dependency metadata confirms that it is referenced by 25 packages, including OE_ORDER_PUB, OE_HEADER_UTIL, OE_CHARGE_PVT, OE_ORDER_ADJ_PVT, OE_LINE_ADJ_UTIL, OE_DEFAULT_HEADER_ADJ, OE_HEADER_ADJ_SECURITY, OE_HEADER_ADJ_CL_DEP_ATTR, OE_ORDER_PVT, OE_RETROBILL_PVT, OE_INVOICE_UTIL, and the header adjustment forms (OE_OE_FORM_HEADER_ADJ and related form packages). It also depends on FND_API for the standard API return-status conventions and on OE_ORDER_PUB, and it reads OE_AK_HEADER_PRCADJS_V. In practice, header adjustments are created or modified through the Sales Orders form or through OE_ORDER_PUB, which in turn routes the work through this utility. Because it is a UTIL-class package with unpublished parameter lists and no documented public contract, it should not be called from custom code; customizations should instead use the supported Order Management public APIs so that attribute defaulting, dependent-attribute processing, security checks, and history logging remain intact.