Results for “ont_line_def_hdlr”

50+ results




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

Overview

ONT_LINE_DEF_HDLR is an Oracle E-Business Suite Order Management (ONT) package owned by the APPS schema. Its name reflects its role as a handler for order line defaulting — the mechanism by which Oracle Order Management derives and applies default values to order line records when lines are created, copied, or otherwise populated within an order. In Oracle EBS Release 12.1.1 and 12.2.2, defaulting of order attributes is governed by the extensible OE_DEFAULT framework, and ONT_LINE_DEF_HDLR operates as a downstream participant in that framework, supplying line-level default processing logic that other defaulting components call into.

Its dependency footprint places it firmly inside the order defaulting and availability stack. The package reads from the order lines view OE_AK_ORDER_LINES_V, and it is referenced by OE_DEFAULT_LINE, OE_DEFAULT_PVT, OE_DEFAULT_TOLERANCE, OE_OE_AVAILABILITY, OE_OE_PRICING_AVAILABILITY, and OE_RELATED_ITEMS_PVT. This positions ONT_LINE_DEF_HDLR as a utility invoked while default records and related-item or availability candidates are being resolved for an order line.

Key Procedures and Functions

The documented interface exposes a single public procedure:

  • DEFAULT_RECORD — the principal entry point of the package. As documented, this procedure performs default-record processing for order line data on behalf of the calling defaulting components. It is the routine that the packages listed above invoke when a line-level default needs to be evaluated or applied. The ETRM metadata does not publish a parameter list for this procedure, and no parameter details should be assumed beyond its documented purpose of handling a default record.

Because the package body is marked as containing SQL statements and full source is not reproduced in the metadata excerpt, additional internal procedures, if any, are not part of the documented interface. Custom code should call only DEFAULT_RECORD, and only in the manner that the standard defaulting framework does.

Tables Accessed

The documented object dependency identifies one table or view reference:

  • OE_AK_ORDER_LINES_V — an Order Management order lines view exposed in the APPS schema. ONT_LINE_DEF_HDLR references this view, indicating that default processing reads order line attribute context from it in order to determine the current values and applicability of a default before the record is applied or returned to the caller.

No insert, update, or delete activity against base tables is documented for this package. Its role is that of a read-and-evaluate participant in the defaulting chain rather than a direct DML component; persistence of the resulting defaults is handled by the surrounding framework packages such as OE_DEFAULT_PVT and OE_DEFAULT_LINE.

Usage Notes

ONT_LINE_DEF_HDLR is not intended for direct invocation by end users. It is an internal dependency of the Order Management defaulting framework and is called programmatically during the following scenarios:

  • Order entry in the Sales Orders form, when a new line is created and line-level defaults must be derived.
  • Order copy and line duplication operations, where default attributes must be re-resolved for the new line.
  • Availability and pricing availability evaluation, since OE_OE_AVAILABILITY and OE_OE_PRICING_AVAILABILITY both depend on the package.
  • Related-items processing through OE_RELATED_ITEMS_PVT, and tolerance handling through OE_DEFAULT_TOLERANCE.

Invocation occurs through the standard defaulting APIs, which must execute inside a properly initialized Oracle Applications session so that APPS schema synonyms and Order Management security context resolve correctly. Customizations that modify defaulting behavior should hook into the supported OE_DEFAULT extensibility rather than calling ONT_LINE_DEF_HDLR directly, because its signature and behavior are Oracle-controlled and could change across patch levels in 12.1.1 and 12.2.2.