Results for “get_sys_lookup_meaning”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BIS_REQUESTSET_VIEWHISTORY is an Oracle EBS PL/SQL package owned by the APPS schema and classified under the ETRM as an "OTHER" API type. In Oracle EBS 12.1.1 and 12.2.2, the BIS (Business Intelligence System) product family provides the infrastructure behind Oracle Daily Business Intelligence and related request-set reporting features. The BIS_REQUESTSET_VIEWHISTORY package supports the viewing and interpretation of request set history by providing lookup resolution utilities used when rendering historical run information. Its principal role is to translate stored lookup codes into human-readable meanings so that request set history displays correctly in the relevant BIS user interfaces. The package header carries the version identification BISRSVHS.pls 120.0, reflecting a mid-2005 source revision that persisted into the 12.x code lines. Note that the user's search term, "get_user_object_name," corresponds to a function that was part of this package's original specification but was explicitly removed, making its removal a documented fact of the package's evolution.

Key Procedures and Functions

The ETRM documents four functions for this package; however, the source header shows that one of these is no longer present in the active specification. The documented members are:

• GET_LOOKUP_MEANING — Returns the display meaning associated with a given lookup type and lookup code, resolving standard lookup values for presentation in request set history views.
• GET_SYS_LOOKUP_MEANING — Returns the meaning for a system-level lookup, used where the lookup is defined at the Oracle applications (system) level rather than the user or BIS level.
• GET_BIS_LOOKUP_MEANING — Returns the meaning for a BIS-specific lookup, used to resolve lookups defined within the Business Intelligence System lookup types.
• GET_USER_OBJECT_NAME — Historically resolved a user-facing object name from an object type and object name. The source explicitly removes this function with the comment "Removed Get_User_Object_Name for bug3950162." It therefore appears in the documented procedure list as a legacy entry but must be treated as absent from the compiled package specification in supported 12.1.1 and 12.2.2 environments.

No parameter lists are reconstructed here beyond what the metadata states, because the active function signatures should be verified against the deployed source.

Tables Accessed

The documented ETRM metadata does not list any tables referenced via APPS synonyms for this package. In practice, the lookup-meaning functions in the BIS family derive their results from the standard Oracle lookup infrastructure (the FND_LOOKUP_VALUES and associated FND lookup views) and, where applicable, BIS lookup definitions. Because no explicit table list is documented, integrators should not assume additional data access; the package should be treated as a lightweight, read-only utility that resolves codes to meanings without persisting state.

Usage Notes

BIS_REQUESTSET_VIEWHISTORY is typically invoked indirectly rather than called directly by end users. It is most commonly consumed by the forms, OAF pages, or JSP-based regions that render request set history within the BIS/Daily Business Intelligence framework, where lookup codes stored with historical runs must be converted to readable text. The ETRM records that the package is referenced by four other packages, indicating it is a shared dependency within the BIS code base rather than a top-level entry point. Custom code should avoid calling GET_USER_OBJECT_NAME, since it was removed under bug3950162; any legacy customization that depended on it must be redirected to the appropriate replacement utility. When extending or troubleshooting request set history displays, confirm the function signatures and current source revision (120.0) in the target environment, as behavior is consistent across 12.1.1 and 12.2.2 but governed by the deployed package body.