Search Results prepare_lines_dff_for_save

Overview

APPS.OE_OE_HTML_LINE_EXT is a PL/SQL package body within the Oracle Order Management (ONT) schema of Oracle E-Business Suite. It is classified under the ETRM taxonomy as an "OTHER" API, indicating it is not part of the public, formally supported order capture API surface (such as OE_ORDER_PUB), but rather an extension package used to support HTML-based order entry flows, commonly associated with the iStore and Oracle Order Management HTML user interfaces. Its primary business function is to manage line-level and shipment-level processing for orders entered through HTML rendering paths, including the retrieval of shipment numbering, preparation of descriptive flexfield (DFF) data prior to persistence, and handling of transient (non-persistent) attributes that exist only during a user session or UI transaction.

The package header declaration references a global collection type, Line_Dff_Tbl_Type, and package-level globals G_LINE_NUMBER and G_SHIPMENT_NUMBER, which serve as cached state for line and shipment enumeration. The documented source excerpt also references the GET_LINE_SHIPMENT_NUMBER procedure, which returns a line number and shipment number for a given header identifier. This procedure is directly relevant to the search term "get_line_shipment_number," as it exposes the routine responsible for resolving sequential line and shipment references during HTML order line processing.

Key Procedures and Functions

The ETRM documentation identifies three procedures and functions within this package body:

• SAVE_LINES — Persists order line changes originating from the HTML line entry flow. The source excerpt shows it accepts a return status, message count, message data, and a cascade flag as OUT parameters, along with new and old line table collections (OE_ORDER_PUB.Line_Tbl_Type) as IN parameters. It initializes controlled-record flags, disables API cache clearing, and orchestrates saving through OE_GLOBALS control settings, effectively bridging HTML line data into the order management persistence layer.
• PREPARE_LINES_DFF_FOR_SAVE — Prepares descriptive flexfield values associated with order lines prior to save. This ensures DFF segments collected in the HTML interface are properly formatted and staged for insertion into the underlying order line tables.
• POPULATE_TRANSIENT_ATTRIBUTES — Populates attributes that are transient in nature, meaning they are not permanently stored in the database but are required during runtime display or validation within the HTML order entry session.

The procedure GET_LINE_SHIPMENT_NUMBER, visible in the source excerpt, is not listed among the three ETRM-documented procedures but is present in the package body and is central to the user's search context, returning line and shipment numbers for a specified header identifier.

Tables Accessed

The package references the following tables through APPS synonyms:

• OE_ORDER_LINES and OE_ORDER_LINES_ALL — The primary order line tables. SAVE_LINES writes line data and DFF values here, while shipment and line number queries read from these tables.
• MTL_SYSTEM_ITEMS_TL — Used to resolve translated item descriptions or names, supporting HTML display and validation of ordered items.
• MTL_CUSTOMER_ITEMS — Customer item cross-reference data used to validate or display customer-specific item numbers on HTML order lines.
• MTL_CROSS_REFERENCES — Cross-reference information linking internal items to external or customer identifiers.
• PLITBLM — An Order Management interface/interface-line table used during line processing and staging operations.

Usage Notes

OE_OE_HTML_LINE_EXT is invoked internally by the HTML order entry flow rather than by external custom code. It is referenced by one other package within the ETRM repository, indicating a tightly scoped dependency chain. It is typically called from the HTML order line rendering and save logic in Order Management and iStore, and should be treated as an internal, non-public API. Customizations requiring line or shipment number resolution should generally use supported public APIs such as OE_ORDER_PUB instead of calling this package directly, since its interface is undocumented in the public API guides and may change between releases. The package is compatible with both 12.1.1 and 12.2.2 environments, with the header version string reflecting a 2005-era baseline carried forward.