Search Results oe_header_adj_security




Overview
Explore in AI Chat

Overview

APPS.OE_HEADER_ADJ_SECURITY is a PL/SQL package body in the Oracle Order Management (OM) module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its business purpose is to enforce security and constraint validation on header-level price adjustment (modifier and qualifier) data associated with order headers. In EBS Order Management, price adjustments are governed by pricing constraints — rules that dictate which modifiers and qualifiers apply to a given order, customer, or context. This package is the security gatekeeper that determines, at the header level, whether a price adjustment row is visible, updatable, or constrained based on the applicable pricing constraint definitions.

This object carries the API classification OTHER, meaning it is an internal, non-public API intended for use by other Oracle Order Management packages and concurrent processes rather than for direct external calls.

Key Procedures and Functions

The ETRM metadata documents 34 procedures/functions within this package body. The visible procedure names follow two groupings. The first grouping comprises attribute accessors — ATTRIBUTE1, ATTRIBUTE2, ATTRIBUTE3, ATTRIBUTE4, ATTRIBUTE5, ATTRIBUTE6, ATTRIBUTE7, ATTRIBUTE8, ATTRIBUTE9, ATTRIBUTE10, ATTRIBUTE11, ATTRIBUTE12, ATTRIBUTE13, ATTRIBUTE14, and ATTRIBUTE15. These correspond to the DFF (Descriptive Flexfield) attribute columns of the underlying order header adjustment structures, providing controlled get/set access so that contextual flexfield values participate in security evaluation.

The remaining documented names — AUTOMATIC, CONTEXT, CREATED_BY, CREATION_DATE, and DISCOUNT — reflect the core columns of the price adjustment entity. AUTOMATIC addresses adjustments applied automatically versus manually; CONTEXT identifies the DFF context; CREATED_BY and CREATION_DATE support audit and change tracking; DISCOUNT addresses discount-type adjustment handling. Collectively, these procedures expose the attributes required to evaluate header adjustment security. No parameter lists are documented and none are inferred.

Tables Accessed

The package references two documented base tables through APPS synonyms:

  • OE_ORDER_HEADERS_ALL — the core order header table. Security evaluation is anchored to the order header, so the package reads header context (customer, order type, pricing context) needed to determine applicable constraints.
  • OE_PC_CONSTRAINTS — the pricing constraint table. This is the authoritative source of the security rules that determine which price adjustments are permitted or protected for a given header.

Additional dependencies listed in the ETRM dependency section include OE_AK_HEADER_PRCADJS_V, OE_HEADER_ADJ_UTIL, OE_PC_CONSTRAINTS_ADMIN_PVT, OE_PC_GLOBALS, OE_ORDER_PUB, OE_ORDER_CACHE, OE_GLOBALS, OE_VERSIONING_UTIL, FND_API, FND_GLOBAL, OE_MSG_PUB, OE_DEBUG_PUB, and OE_CODE_CONTROL, indicating the package builds on the standard OM pricing and API infrastructure.

Usage Notes

OE_HEADER_ADJ_SECURITY is an internal package. It is not referenced by any other database object in the ETRM reverse dependency listing, yet it references 36 other packages upstream — it sits at the top of the internal security layering for header adjustments. It is typically invoked indirectly:

  • by Order Management forms when users view or modify header-level adjustments, to enforce constraint visibility and editability;
  • by the pricing engine and OE_ORDER_PUB during order entry, import, and update, to validate that adjustments conform to pricing constraints;
  • by concurrent programs (e.g., order import, pricing reprocessing) that must apply the same security rules as interactive sessions.

Because it is classified OTHER and undocumented as a public API, customizations should avoid direct invocation; customers requiring adjustment security extensions should use supported pricing constraint configuration or the public OE_ORDER_PUB APIs, allowing this package to apply security uniformly across all entry points in both 12.1.1 and 12.2.2.