Search Results bis_dim_level_value_pvt




Overview
Explore in AI Chat

Overview

APPS.BIS_RESPONSIBILITY_PVT is a private PL/SQL package in the Oracle E-Business Suite (12.1.1 / 12.2.2) that belongs to the Business Intelligence System (BIS) product family. It provides the responsibility-resolution layer used by the Oracle Daily Business Intelligence and ETRM performance-management components. Its central purpose is to translate Oracle EBS responsibilities, notification responsibilities, and application user context into the internal identifiers and value sets that the BIS reporting engine requires when validating dimension level values, target levels, measures, and intermediate list-of-values queries.

The package is classified as a PVT (private) API, meaning it is not intended for direct customer invocation. It is consumed internally by other BIS packages to determine which responsibilities a given user may access, to validate an incoming responsibility ID, and to convert between the external responsibility identifier presented in a user interface and the internal value identifier used in the BIS repository. Because the object is documented as VALID and owned by APPS, it is a core, supported component of the shipped BIS schema rather than a customization artifact.

Key Procedures and Functions

  • RETRIEVE_USER_RESPONSIBILITIES — Returns the set of responsibilities associated with the current user, forming the basis of responsibility-based security filtering in BIS reports.
  • RETRIEVE_ALL_RESPONSIBILITIES — Returns the complete list of responsibilities defined in the environment, used where an unrestricted selection is permitted.
  • RETRIEVE_RESPONSIBILITY — Retrieves the details of a single responsibility, typically to resolve a name, application, or identifier from an internal key.
  • VALIDATE_DEF_NOTIFY_RESP_ID — Validates a default notification responsibility identifier supplied as a parameter or profile value.
  • RETRIEVE_NOTIFY_RESP_NAME — Resolves the descriptive name of a notification responsibility from its identifier.
  • VALIDATE_NOTIFY_RESP_ID — Confirms that a supplied notification responsibility identifier exists and is usable.
  • VALUE_ID_CONVERSION — Performs the core conversion between a responsibility value identifier and its corresponding internal representation.
  • DFR_VALUE_ID_CONVERSION — A variant of the conversion routine used in the DFR (Daily Financials Reporting) code path, applying the same identifier-mapping logic in that context.
  • REMOVEDUPLICATES — Eliminates duplicate entries from responsibility result sets, ensuring distinct rows are returned to callers.
  • GET_NOTIFY_RESP_AK_INFO — Returns the alternate-key information for a notification responsibility, supporting key-based lookup and integrity checks.

The package metadata records eleven documented procedures or functions in total; the entries above represent the API surface defined in the ETRM 12.1.1 documentation.

Tables Accessed

The documented table references are limited to the HTP and PLITBLM synonyms. HTP is the Oracle HTML/PLSQL Toolkit package used to render markup when the package participates in HTML output generation. PLITBLM is the PL/SQL integer table type used to pass and manipulate collections of identifiers, which is consistent with routines such as RETRIEVE_USER_RESPONSIBILITIES returning arrays of responsibility IDs. The bulk of the package's data access is performed indirectly through dependent packages, notably BIS_COMMON_UTILS, BIS_UTILITIES_PUB, and FND_API, which supply the underlying queries against the responsibility and application tables.

Usage Notes

BIS_RESPONSIBILITY_PVT is referenced by eight other packages, including BIS_DIM_LEVEL_VALUE_PVT, BIS_INTERMEDIATE_LOV_PVT, BIS_MEASURE_SECURITY_PVT, BIS_TARGET_LEVEL_PVT, BIS_TARGET_LEVEL_VALIDATE_PVT, BIS_TARGET_PVT, BIS_UTILITIES_PUB, and POA_REPORT_UTIL. This dependency pattern explains why a search for "bis_dim_level_value_pvt" surfaces this object: BIS_DIM_LEVEL_VALUE_PVT depends directly on BIS_RESPONSIBILITY_PVT to resolve the responsibility context before validating dimension level values.

Because it is a private package, it should not be called directly from custom code or concurrent programs. Invocation occurs through the public BIS and ETRM APIs, through OAF/Forms-based BIS dashboards, and through concurrent programs that render daily business intelligence reports. Any security validation performed here indirectly enforces that users see only the responsibility-scoped data they are entitled to within the BIS reporting layer.