Search Results log_adj_requests

Overview

OE_LINE_ADJ_UTIL is an Oracle E-Business Suite PL/SQL utility package owned by the APPS schema and classified by ETRM as a UTIL (utility) API. It provides the low-level infrastructure used by Oracle Order Management to create, maintain, and query order line-level price adjustments — the discount and surcharge records that determine the final selling price of an order line. Because it is a UTIL API rather than a public business API, it is intended primarily for internal consumption by other Oracle Order Management packages and by tightly coupled customization code.

The package is built as a table-handler style utility. It defines a large set of global constants mapping each logical attribute of a line adjustment record (for example G_DISCOUNT, G_PERCENT, G_PRICE_ADJUSTMENT, G_LIST_HEADER_ID, G_LIST_LINE_ID, G_MODIFIER_MECHANISM_TYPE_CODE, G_MODIFIED_FROM, and G_MODIFIED_TO) to a numeric attribute identifier, up to G_MAX_ATTR_ID. These constants allow generic routines to operate on individual columns without hard-coded names. The package header carries the $Header revision marker OEXULADS.pls 120.2.12020000.1, dated 2012/06/26, which is consistent with the 12.1.1 and 12.2.2 code lines.

Key Procedures and Functions

ETRM documents 33 procedures and functions. The most significant include:

• LOG_ADJ_REQUESTS — the routine associated with the search term "log_adj_requests". It records adjustment-related requests, providing an audit or diagnostic trail of adjustment activity triggered during order processing.
• G_MISS_OE_AK_LINE_ADJ_REC — a global "missing" record used as a null/default template for the line adjustment API record structure.
• API_REC_TO_ROWTYPE_REC and ROWTYPE_REC_TO_API_REC — conversion routines that translate between the public API record type and the %ROWTYPE representation of the underlying adjustment table.
• CLEAR_DEPENDENT_ATTR, APPLY_ATTRIBUTE_CHANGES, COMPLETE_RECORD, and CONVERT_MISS_TO_NULL — attribute-level maintenance routines that reset dependent attributes, apply pending changes, populate mandatory defaults, and translate placeholder values into true NULLs before a write.
• UPDATE_ROW, INSERT_ROW, DELETE_ROW — the core DML routines for line adjustment records.
• QUERY_ROW, QUERY_ROWS, LOCK_ROW, LOCK_ROWS, GET_VALUES, GET_IDS — retrieval and concurrency routines, supporting single-row fetch, multi-row fetch, optimistic locking, and key lookup.
• CONVERT_HDR_ADJ_TO_LINE_ADJ and COPY_ADJUSTMENT_LINES — business transformation routines that convert header-level adjustments into line-level adjustments and replicate adjustment lines across order lines.
• PRE_WRITE_PROCESS — a pre-write validation and preparation hook invoked before persistence.

Tables Accessed

The package operates against the principal Order Management pricing tables through APPS synonyms:

• OE_ORDER_LINES and OE_ORDER_LINES_ALL — the order line entities to which adjustments are attached.
• OE_PRICE_ADJUSTMENTS and OE_PRICE_ADJUSTMENTS_S — the price adjustment definitions and their translated (TL/secure) counterpart.
• OE_PRICE_ADJ_ASSOCS — the association table linking adjustments to specific order lines.
• DUAL — used for scalar evaluation and sequence or value derivation.
• PLITBLM — the PL/SQL integer table type used for bulk ID and value collections in the GET_IDS and GET_VALUES routines.

Usage Notes

OE_LINE_ADJ_UTIL is referenced by 26 other packages, confirming its role as a shared internal dependency within the Order Management pricing and adjustment flow. It is typically invoked indirectly — from the Order Management sales order forms, from concurrent programs that price or reprice orders, and from Oracle pricing and modifier engine processing — rather than called directly by end users. Customizations that call it directly must respect the attribute constants and supply records in the expected API structure; because many routines are non-public helper methods, Oracle does not guarantee interface stability across patches. Developers should prefer documented public APIs where available, use this package only for adjustment-level maintenance that those APIs do not expose, and always run in a test instance first.