Search Results get_concat_hist_line_number

Overview

APPS.OE_ORDER_MISC_PUB is a public PL/SQL package in Oracle Order Management that provides utility functions for deriving concatenated order line number values. The package declares AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the invoking schema rather than as a definer-rights unit. The documented header carries an RCS revision marker of 120.0, dated 2005/05/31, and is classified as a PUB (public) API in ETRM for both Oracle EBS 12.1.1 and 12.2.2.

Its business purpose is narrow and presentational: the Order Management data model stores a line identifier (LINE_ID) and a line number, but omits a single scalar that combines the order context and the line into a displayable "concatenated line number" string. OE_ORDER_MISC_PUB supplies that derived value, both for current order lines and for historical versions of those lines, so that forms, reports, and integrations can render a consistent human-readable line reference without independently reimplementing the concatenation logic.

Key Procedures and Functions

The package exposes three documented callable units, all functions returning VARCHAR2.

• GET_CONCAT_LINE_NUMBER — Returns the concatenated line number for a current order line, accepting the line identifier as input. This is the primary entry point used when the caller holds a LINE_ID from the active order line table and requires the composite display value.
• GET_CONCAT_HIST_LINE_NUMBER (two-parameter overload) — Returns the concatenated line number for a specific historical version of a line, accepting both a line identifier and a version number. The caller supplies the version explicitly when a particular revision must be rendered.
• GET_CONCAT_HIST_LINE_NUMBER (single-parameter overload) — Returns the concatenated line number for a historical line when only the line identifier is known, allowing the package to resolve the applicable version internally.

The presence of two overloads of GET_CONCAT_HIST_LINE_NUMBER is significant: it lets calling code resolve history either with or without an explicit version, which is common in Order Management change-history and audit displays. No parameter lists beyond those captured in the documented header are asserted here.

Tables Accessed

ETRM documents two base tables accessed through APPS synonyms:

• OE_ORDER_LINES_ALL — The primary order line table. The current-line function reads from it to resolve the line identifier into a concatenated line number.
• OE_ORDER_LINES_HISTORY — The corresponding history table retaining prior versions of order lines. The historical functions read from it, joining on line identifier and, where supplied, version number.

The functions are read-only in nature; they derive and return a VARCHAR2 value and are not documented as writing to either table.

Usage Notes

The package is referenced by fourteen other packages within the APPS schema, indicating that it functions as shared infrastructure consumed by higher-level Order Management APIs and internal processing rather than as an end-user entry point. Typical invocation contexts include:

• Order Management forms and descriptive flexfield or display logic that must show a combined line reference.
• Concurrent programs and reports extracting order line data for printing or integration.
• Custom PL/SQL that requires the standard concatenated line number rather than reimplementing concatenation rules, ensuring consistency with Oracle's own formatting.

Because it is a PUB package, direct calls with a valid line identifier are supported. Callers should pass a LINE_ID that exists in the relevant table; for historical retrieval without an explicit version, the package determines the version internally, so callers should not assume a specific version is returned.