Search Results bis_measure_pvt




Overview
Explore in AI Chat

Overview

BIS_APPLICATION_PVT is a private PL/SQL package in the APPS schema that belongs to the Oracle Business Intelligence System (BIS) family of application programming interfaces. In Oracle EBS 12.1.1 and 12.2.2, the BIS modules underpin the Oracle Balanced Scorecard and related performance-management and analytics functionality. The _PVT suffix denotes a private API package: its procedures are intended for internal consumption by sibling packages rather than for direct invocation from forms, concurrent programs, or customer extensions.

Business-wise, BIS_APPLICATION_PVT encapsulates the logic that ties scorecard measures and related analytics objects to the Oracle E-Business Suite applications against which they are defined. It provides reusable application-validation, application-retrieval, and identifier-conversion services so that the measurement packages (BIS_APPLICATION_MEASURE_PVT and BIS_MEASURE_PVT) do not duplicate that logic. The package therefore acts as a shared internal utility layer for application-context handling within the Balanced Scorecard schema.

Key Procedures and Functions

The ETRM documentation records four procedures/functions for this package (three named plus one implied by the count):

  • RETRIEVE_APPLICATIONS — Returns the set of Oracle EBS applications known to the BIS layer. It is used by caller packages to obtain the applicable application context for a measure or scorecard object.
  • VALIDATE_APPLICATION — Performs validity checking on a supplied application identifier, ensuring that a measure or scorecard definition references a legitimate, existing application before downstream processing continues.
  • VALUE_ID_CONVERSION — Converts between an internal value identifier and its corresponding external/published representation, allowing the BIS measurement tables to store compact internal IDs while presenting meaningful values to callers and end users.

Parameter lists are not reproduced here; the documented metadata does not enumerate them, and they should be confirmed against the deployed package specification for the specific patch level. Each routine follows the standard EBS API conventions inherited from FND_API, including the use of a standard return status and message-handling pattern.

Tables Accessed

The ETRM metadata records a single table reference, accessed through an APPS synonym: PLITBLM. This is a translated/lookup table used by the BIS layer to hold application-related value definitions. BIS_APPLICATION_PVT reads from this table to satisfy RETRIEVE_APPLICATIONS and VALUE_ID_CONVERSION, and it relies on the same source when VALIDATE_APPLICATION confirms that a given application is properly registered. No insert, update, or delete activity is documented; the package should be regarded as a read-oriented utility layer.

Usage Notes

BIS_APPLICATION_PVT is not intended for direct invocation. It is referenced by BIS_APPLICATION_MEASURE_PVT, BIS_MEASURE_PVT, and BSC_BIS_MEASURE_PUB, which are the entry points normally exercised from the Balanced Scorecard setup forms and from concurrent programs that initialize or refresh scorecard measure definitions. Customizations that need application-context services should call the public wrapper BSC_BIS_MEASURE_PUB rather than this private package, because Oracle may change private API signatures between patch sets.

The package itself depends on BIS_UTILITIES_PUB, the FND_API error-handling framework, and standard SYS constructs. Any modification to its behavior must be validated against all three dependent packages, as all of them share the routines described above. In 12.2.2 the object remains valid in the APPS schema, and the same dependency set applies as in 12.1.1. The search term bis_measure_pvt is a near neighbour in the same package family; users tracing dependencies between these packages will find BIS_APPLICATION_PVT on the dependency chain of BIS_MEASURE_PVT.