Search Results oe_oe_form_line_adj




Overview
Explore in AI Chat

Overview

OE_OE_FORM_LINE_ADJ is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified as a form-support API within Oracle Order Management. Its responsibility is to manage price adjustment records associated with order lines — the discounts, surcharges, and other modifiers that alter the selling price of a line beyond its base list price. The package encapsulates the attribute-defaulting, validation, and persistence logic required by the Order Management order-entry forms when a user creates, modifies, or deletes a price adjustment on an order line.

Rather than allowing the form's client-side logic to write directly to the underlying pricing tables, OE_OE_FORM_LINE_ADJ centralizes that access. It reads and writes the transient and persistent structures that represent line-level adjustments, thereby insulating the form layer from the physical data model and ensuring that standard validation, locking, and audit conventions are applied consistently. Because the package header carries a $Header tag dated 2005, it is a stable, long-lived component whose interface has been preserved across the 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

  • DEFAULT_ATTRIBUTES — Returns default values for a price adjustment record. It accepts header and line identifiers and returns a comprehensive set of output attributes describing the adjustment, including the price adjustment identifier, discount identifiers, automatic and applied flags, percent and amount values, modifier mechanism, pricing phase, change reason, and the descriptive flexfield context and attribute columns. This is the entry point used to pre-populate a new adjustment form block.
  • CHANGE_ATTRIBUTES — Applies modifications to the attributes of an existing adjustment record, enforcing the business rules that govern which fields may be changed.
  • VALIDATE_AND_WRITE — Performs validation of the adjustment data and, on success, persists the record to the underlying tables.
  • DELETE_ROW — Removes a price adjustment row, handling the associated cleanup.
  • PROCESS_DELAYED_REQUESTS — Processes requests that were deferred, supporting deferred or batch-style handling of adjustment operations.
  • REPLACE_ATTRIBUTES — Substitutes the stored attribute values for a record, used when a block is re-queried or refreshed.
  • LOCK_ROW — Acquires a lock on the adjustment row to prevent concurrent modification, consistent with Oracle Forms record-locking semantics.
  • INSERT_ROW — Inserts a new price adjustment row into the persistent structures.

Tables Accessed

  • OE_ORDER_LINES_ALL — The base order line table. The package references it to resolve the line against which an adjustment applies and to validate header/line context.
  • OE_PRICE_ADJUSTMENTS — The principal table holding line-level price adjustment records. Inserts, updates, and deletes performed by INSERT_ROW, VALIDATE_AND_WRITE, and DELETE_ROW are directed here.
  • OE_PRICE_ADJUSTMENTS_S — The corresponding secure (row-level security) synonym through which the adjustment data is accessed under the Order Management security model.
  • DUAL — Used for scalar evaluations and lookups.
  • PLITBLM — The PL/SQL integer table type used for bulk or list processing within the package's internal routines.

Usage Notes

This package is primarily invoked by the Oracle Order Management order-entry forms, specifically the line-level adjustment and pricing blocks that allow users to view and maintain modifiers on an order line. Standard form triggers such as WHEN-NEW-RECORD-INSTANCE, WHEN-VALIDATE-RECORD, and post-query logic call DEFAULT_ATTRIBUTES to seed new records, LOCK_ROW to protect concurrent edits, VALIDATE_AND_WRITE or INSERT_ROW to commit changes, and DELETE_ROW to remove adjustments.

Although the package is classified as OTHER rather than as a published open API, its procedures may be referenced by custom forms customizations and extensions that need to manipulate line adjustments through the supported form interface. Direct invocation from concurrent programs or external integrations is uncommon; such processing is normally routed through the Order Management open APIs instead. The documented metadata records zero dependent packages, indicating that OE_OE_FORM_LINE_ADJ occupies a leaf position in the dependency hierarchy and does not serve as a shared utility for other PL/SQL units.