Search Results oe_oe_html_line




Overview
Explore in AI Chat

Overview

OE_OE_HTML_LINE is an internal Oracle E-Business Suite PL/SQL package owned by APPS and classified under the OTHER API category. It belongs to the Oracle Order Management (ONT) module and is part of the server-side processing layer that supports the HTML-based Order Management user interface. The package encapsulates row-level operations for order lines — defaulting attribute values, applying attribute changes, deleting rows, locking rows against concurrent modification, and clearing transient record structures — for use by the HTML order entry flow.

The package is declared AUTHID CURRENT_USER, meaning that its SQL statements execute with the privileges of the calling user rather than the definer, and it participates in the standard Oracle EBS API error-handling convention: every documented procedure exposes x_return_status, x_msg_count, and x_msg_data OUT parameters so that the caller can interrogate the outcome of the call through the FND message stack. The header dates from 2005 (revision 120.0) and the package remains in place through EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The documented interface consists of five procedures:

  • DEFAULT_ATTRIBUTES — Populates default values onto an order line record for a given header, returning the line record, a line validation record, and the associated header record. This is the initialisation routine used when a new HTML order line is first presented to the user.
  • CHANGE_ATTRIBUTE — Applies one or more attribute changes to an existing line, identified by line identifier and attribute identifier/value pairs, and also accepts optional bulk attribute tables to support multi-attribute updates in a single call. Change reason and comment parameters capture the audit context. The prior line values are returned alongside the updated record.
  • DELETE_ROW — Removes an order line identified by its line identifier, with optional change reason code and change comments supplied for audit purposes.
  • LOCK_ROW — Acquires a logical lock on a line record, using a lock control value, so that the HTML session can prevent conflicting concurrent edits before update or delete operations proceed.
  • CLEAR_RECORD — Resets the working record structures held by the HTML line flow, providing a clean state between operations.

The package also declares two PL/SQL collection types, Number_Tbl_Type and Varchar2_Tbl_Type, together with two module-level empty collection constants (G_NULL_NUMBER_TBL and G_NULL_VARCHAR2_TBL) that serve as defaults for the bulk attribute parameters of CHANGE_ATTRIBUTE. No functions are documented.

Tables Accessed

The documented table reference is OE_ORDER_LINES, accessed through the APPS synonym. This is the base transaction table for order lines in Order Management. The package reads it to validate the existence and current state of a line, and writes to it when attribute changes or deletions are committed. All access is performed under the caller’s schema privileges because of the AUTHID CURRENT_USER declaration.

Usage Notes

OE_OE_HTML_LINE is not a public integration API. It is invoked from within the Order Management HTML user-interface layer, where the transactional servlet or form calls these procedures to drive line-level defaulting, attribute modification, deletion, and record locking. The package is referenced by one other package in the documented metadata, consistent with its role as a component of the internal HTML order entry stack rather than a standalone entry point.

Because the procedures are tightly coupled to OE_ORDER_PUB record types, they must not be called with arbitrary ad hoc record structures. The required data structures — OE_ORDER_PUB.Line_Rec_Type, Line_Val_Rec_Type, and Header_Rec_Type — must be initialised by the caller before invocation, with results communicated through the standard x_return_status / x_msg_count / x_msg_data trio. Any error message text is retrieved via standard FND message retrieval against x_msg_count. Extensions or customisations should prefer the public Order Management APIs, since the HTML line package is an internal implementation detail and is subject to change between releases.