Results for “oe_default_header_adj”

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

Overview

The APPS.OE_DEFAULT_HEADER_ADJ package body is a PL/SQL API belonging to the Oracle Order Management (OM) module of Oracle E-Business Suite. Its primary business function is to derive, populate, and default header-level price adjustment information for sales orders during order entry and order maintenance activities. In the Oracle EBS pricing model, price adjustments represent discount, surcharge, coupon, or promotion lines applied to an order header or order line. The header adjustment records are persisted in the OE_PRICE_ADJUSTMENTS entity (surfaced through the OE_PRICE_ADJUSTMENTS_S synonym referenced by this package).

In the context of a user search for oe_price_adjustments_s, this package is relevant because it is one of the internal order management units responsible for constructing and inserting the header-level adjustment rows that ultimately reside in that table. Unlike the pricing engine, which evaluates qualifiers and computes adjustment amounts, this package focuses on the mechanics of defaulting and staging header adjustments so they are consistent with the order header context established during the current transaction.

Key Procedures and Functions

The ETRM metadata documents a single exposed program unit within this package body:

• ATTRIBUTES — This procedure encapsulates the attribute-handling logic for header adjustments. In Oracle EBS API convention, an ATTRIBUTES procedure typically serves as an internal or helper routine that maintains the attribute fields (descriptive flexfield and DFF-related columns) and other supplemental descriptors on the adjustment record. It ensures that the adjustment rows defaulted onto the order header carry the correct attribute values required for downstream pricing, validation, and reporting. Its parameters and exact signature are not documented in the supplied ETRM excerpt and should not be assumed; implementers must inspect the package specification for the definitive interface.

No other procedures or functions are documented in the provided metadata for this package body, indicating the remainder of the logic is either private (unexposed) or handled by the referenced utility packages.

Tables Accessed

The documented table and view references for this package are:

• OE_PRICE_ADJUSTMENTS_S — The APPS synonym for the header/line price adjustment entity. OE_DEFAULT_HEADER_ADJ reads and writes against this object to materialize header-level adjustment records that were defaulted for the order. This is the central table tied to the user's search term.
• DUAL — The standard SYS dummy table, used in this package for scalar evaluations such as retrieving sequence values, evaluating sysdate, or performing PL/SQL context queries.

In addition, the dependency tree shows the package relies on OE_HEADER_ADJ_UTIL, OE_ORDER_CACHE, OE_ORDER_PUB, OE_GLOBALS, OE_DEBUG_PUB, and FND_API, which provide adjustment utility logic, cached order context, the public order API, global constants, debug instrumentation, and the standard API error-handling framework respectively.

Usage Notes

OE_DEFAULT_HEADER_ADJ is an internal, non-public API in the Oracle Order Management pricing and defaulting stack. It is not referenced by any other database object per the ETRM dependency listing, confirming it is called from within the OM order-entry flow rather than exposed as a standalone interface.

Typical invocation scenarios include:

• Order Entry forms (OEXOEORD) and the Sales Order pad, where header adjustments are defaulted as the user enters or modifies an order header.
• Programmatic order creation and updates through OE_ORDER_PUB, where the process order or pre-processing logic applies header adjustments before saving.
• Concurrent pricing and adjustment processes that re-evaluate or repopulate adjustment records on existing orders.

Because this is a private implementation package, customizations should not call it directly. Instead, developers should use supported public APIs such as OE_ORDER_PUB or the pricing engine (QP) APIs, and should treat OE_DEFAULT_HEADER_ADJ as an internal dependency relevant only for debugging, dependency tracing, and upgrade impact analysis.