Search Results oe_oe_html_line_ext




Overview
Explore in AI Chat

Overview

OE_OE_HTML_LINE_EXT is an Oracle E-Business Suite order management support package owned by the APPS schema and classified in the ETRM metadata as an "OTHER" API. Its name and the presence of the Line_Dff_Rec_Type record structure indicate that it exists to service the descriptive flexfield (DFF) and extensibility attributes attached to order lines that are entered or edited through the Oracle Order Management HTML-based user interface (the ONT HTML / self-service ordering flow). The package declares a strongly typed record, Line_Dff_Rec_Type, that mirrors the full line DFF surface: thirty generic attribute columns (attribute1 through attribute20 in non-sequential declaration order), thirty global attribute columns plus a global_attribute_category, the industry attributes, and the line identifier. This record type allows the HTML line entry pages to carry the flexfield payload as a single PL/SQL structure rather than as dozens of discrete parameters.

The package has been stable for a long period; its archived header comment dates to 2005, reflecting the generation-era architecture of the ONT HTML line screens. It remains present and documented in both 12.1.1 and 12.2.2, although it operates on the same OE_ORDER_LINES data model in both releases.

Key Procedures and Functions

The ETRM metadata documents three program units, all procedures:

  • SAVE_LINES — the persistence entry point. It accepts the accumulated line-level DFF data held in the Line_Dff_Rec_Type structure and writes it against the corresponding order line, keeping the HTML editing session synchronized with the underlying order line rows.
  • PREPARE_LINES_DFF_FOR_SAVE — a pre-persistence normalization step. It readies the descriptive flexfield values (including the global attribute category and context-dependent segments) so that they conform to the DFF definition before SAVE_LINES commits them.
  • POPULATE_TRANSIENT_ATTRIBUTES — populates the transient, non-persistent attributes used by the HTML line pages. These are display-only or intermediate values needed during line rendering and validation that are not themselves stored in OE_ORDER_LINES.

No parameter signatures are documented in the metadata; the procedures should be treated as internally scoped helpers for the HTML line flow rather than as a general-purpose public API.

Tables Accessed

The package references the following tables through APPS synonyms:

  • OE_ORDER_LINES and OE_ORDER_LINES_ALL — the primary order line entities whose DFF columns (attribute1–20, global attributes, industry attributes) the package reads and writes; OE_ORDER_LINES_ALL is the base table, OE_ORDER_LINES the operational view.
  • MTL_SYSTEM_ITEMS_TL — the translated item master, consulted to resolve item descriptions and item-level information presented on the HTML line page.
  • MTL_CUSTOMER_ITEMS — customer-specific item cross-references, used when the ordered item is identified by the customer's own item number.
  • MTL_CROSS_REFERENCES — the cross-reference type table, used to resolve the relationship between internal items and external/customer item identifiers.
  • PLITBLM — the standard EBS PL/SQL table-to-blob buffer used for bulk serialization and transfer of the line/DFF payload.

Usage Notes

OE_OE_HTML_LINE_EXT is not a documented public API and carries no API classification beyond "OTHER." It is invoked by the ONT HTML line entry processing path — effectively the underlying PL/SQL that supports the Order Management HTML/self-service line pages — and it is referenced by one other package within the ETRM inventory, consistent with its role as a subordinate helper. It is declared AUTHID CURRENT_USER, so it executes with the privileges of the calling schema, which is consistent with internal APPS-invoked code rather than a hardened external interface.

In practice the package is called during line add/update operations to marshal DFF values from the HTML form into the line record, prepare those values for validation against the flexfield definition, resolve item context from MTL_SYSTEM_ITEMS_TL and the customer item tables, and finally persist the attributes to OE_ORDER_LINES via SAVE_LINES. Because the procedures are undocumented and version-stable, customizations should not call them directly; use the supported Order Management APIs (for example, OE_ORDER_PUB) instead. Treat the package as read-only reference material when tracing how HTML line DFF data reaches the order line schema.