Search Results value_id_table

Overview

BIS_LOV_PVT is a private PL/SQL utility package owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Oracle Business Intelligence System (BIS) module. Its declared purpose, as recorded in the package specification header (BISVLOVS.pls), is to provide a suite of list-of-values (LOV) utilities. The package is compiled with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the invoking session rather than the definer, which is significant in the context of EBS form-based and self-service applications where runtime schema resolution is required.

The package was originally created in March 2000 and carries a header revision identifier of 115.18. In EBS 12.1.1 and 12.2.2, it continues to be encountered as a supporting dependency for interactive LOV rendering, particularly in HTML-based or Forms-integrated BI components. Its classification as a private (PVT) API confirms that it is not intended as a public integration surface; it is an internal implementation artifact invoked by other BIS packages.

Key Procedures and Functions

The documented metadata lists seven procedures or functions, of which three distinct callable units are named in the excerpt:

• NULL_ALERT — A utility procedure that raises a null or empty alert, typically used to signal the absence of a meaningful selection to the user interface layer. It acts as a standardized no-op or warning path within LOV handling flows.
• DEPENDENT_LOVFUNCTION — A procedure supporting dependent LOV behavior, where the permissible values in one LOV are constrained by the selection made in a parent attribute, region, or form context. It accepts parameters identifying the LOV function, attribute, region, form, frame, and optional WHERE clause and null-handling text, allowing the caller to define the dependency relationship and fallback behavior.
• GET_LIST — The core LOV population routine, overloaded in the specification. Each overload accepts a set of attribute, name, and selected-value parameters, a no-selection flag defaulting to FND_API.G_FALSE, and a list of value/ID pairs, returning an output collection of type BIS_UTILITIES_PUB.BIS_VARCHAR_TBL. A second overload adds a p_label parameter, and a third overload keys off attribute application ID, attribute code, attribute name, and region application ID. These overloads allow the same underlying logic to serve both name-based and ID-based LOV definitions.

The specification also declares a VALUE_ID_RECORD record type and a VALUE_ID_TABLE index-by table type, along with a constant DSP_NO_SELECTION_STRING derived from the FND message BIS_NO_SELECTION_MESSAGE.

Tables Accessed

The ETRM metadata records access to HTF, HTP, and PLITBLM (via APPS synonyms). HTF and HTP are the Oracle Web Toolkit packages used to emit HTML markup, confirming that BIS_LOV_PVT renders LOV content directly as HTML output rather than relying solely on native Forms LOV widgets. PLITBLM is the standard PL/SQL table-to-integer mapping used in this family of utilities. No application data tables are documented as directly referenced, reinforcing the package's role as a presentation and selection utility rather than a data-retrieval layer.

Usage Notes

BIS_LOV_PVT is not a supported public API. Its name and package classification indicate it is intended for internal invocation by BIS framework packages — the metadata confirms it is referenced by one other package. In practice, custom code should not call this package directly; doing so risks breakage across patches and upgrades, since Oracle may change or remove private procedures without notice. When troubleshooting "get_list" behavior in EBS 12.1.1 or 12.2.2, the appropriate diagnostic path is to trace the calling BIS package and the FND message BIS_NO_SELECTION_MESSAGE, rather than to modify or wrap BIS_LOV_PVT itself.