Results for “oe_line_util_ext”

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

Overview

The APPS.OE_LINE_UTIL_EXT package body is a status-VALID PL/SQL object residing in the APPS schema within Oracle E-Business Suite releases 12.1.1 and 12.2.2. In the Order Management (OM) module, it functions as the external-facing extension utility for order line processing. Whereas the closely related OE_LINE_UTIL package encapsulates the internal line-handling engine, the _EXT variant exposes a controlled interface for converting between the Oracle Forms-style API record structures and the underlying database rowtypes used throughout the order line workflow. It is classified in ETRM with an API classification of OTHER, indicating a utility/support package rather than a high-level public business API such as OE_ORDER_PUB. Its principal role is to support the population, validation, clearing, and defaulting of order line attributes as records flow between the form layer (OE_AK_ORDER_LINES_V), the PL/SQL API layer (OE_ORDER_PUB, OE_DEFAULT_LINE), and persistent storage, thereby enforcing consistent attribute derivation and dependency rules.

Key Procedures and Functions

ETRM documents six constructs within the package body:

• G_MISS_OE_AK_LINE_REC — A global miss (empty) record constant for the order-line view record type, used as a null-comparison template during record transformation logic.
• API_REC_TO_ROWTYPE_REC — Maps a field-level API record into the corresponding %ROWTYPE record used for database operations.
• ROWTYPE_REC_TO_API_REC — Performs the inverse mapping, translating a database rowtype record back into the API record structure.
• CLEAR_DEPENDENT_ATTR — Clears dependent line attributes when a controlling attribute changes, ensuring attributes that are no longer applicable do not persist with stale values.
• CLEAR_DEP_AND_DEFAULT — Combines clearing of dependencies with re-application of defaulting, so that attribute changes trigger both removal of obsolete values and re-derivation of newly applicable ones.
• The sixth documented construct is present in the ETRM count and complements this defaulting and transformation logic (a further record-conversion/utility routine).

No parameter lists are asserted here; the descriptions reflect the documented purpose only.

Tables Accessed

ETRM records two tables referenced through APPS synonyms: OE_SETS and PLITBLM.

• OE_SETS — The order line sets context table, used to resolve set-based attribute relationships during defaulting and dependent-attribute processing.
• PLITBLM — The PL/SQL integer-table (index-by) facility used for in-memory collection handling.

The package additionally depends on OE_DEPENDENCIES, which defines attribute dependency rules that drive CLEAR_DEPENDENT_ATTR and CLEAR_DEP_AND_DEFAULT. Dependencies include FND_API, OE_AK_ORDER_LINES_V, OE_CODE_CONTROL, OE_DEBUG_PUB, OE_DEFAULT_LINE, OE_GLOBALS, OE_LINE_UTIL, OE_MSG_PUB, OE_ORDER_PUB, OE_SCHEDULE_UTIL, and STANDARD. ETRM notes the object is not referenced by any database object, confirming it operates as a leaf-level dependency invoked by other order-entry packages (referenced by eight packages overall).

Usage Notes

OE_LINE_UTIL_EXT is not intended for direct end-user invocation. It is called internally by Order Management forms (the Order Organizer and Sales Orders windows), by OE_ORDER_PUB and OE_LINE_UTIL during line insert, update, and defaulting cycles, and by concurrent processing that manipulates order lines. Customizations that extend order line behavior should invoke these routines through the supported OE_ORDER_PUB API rather than calling the extension utility directly. The dependency on OE_DEBUG_PUB permits diagnostic tracing when OE debugging is enabled.