Search Results update_application_measure




Overview
Explore in AI Chat

Overview

BIS_APPLICATION_MEASURE_PVT is a private PL/SQL package in the APPS schema that provides the internal API layer for creating and managing Performance Measurements within the Oracle E-Business Suite Business Intelligence System (BIS) product family. Performance Measurements represent the quantifiable metrics that are captured against applications and indicators and subsequently used by BIS reporting, benchmarking, and analytics functionality. The package is classified as PVT (private), meaning it is not intended to be called directly by external consumers; instead it is exposed indirectly through the corresponding public wrapper package BIS_APPLICATION_MEASURE_PUB, which is the sole documented referrer of this package.

The header history shows the package originated in November 1998 and has been incrementally enhanced through bug fixes, most notably the addition of dataset_id to the application measure record in 2003 (Bug 3004651), the introduction of WHO audit columns in 2004 (Bug 3891748), and further modifications in 2005 (Bug 4397786). The recorded source carries a 120.0 version stamp, confirming it is a stable, low-change component of the EBS 12.1.1 and 12.2.2 code lines.

Key Procedures and Functions

  • CREATE_APPLICATION_MEASURE — Inserts a new application measure definition, associating an application with a measure, its short name and name, owning application flag, and dataset.
  • RETRIEVE_APPLICATION_MEASURES — Returns one or more application measure records, typically into the Application_Measure_Tbl_Type PL/SQL table.
  • UPDATE_APPLICATION_MEASURE — Modifies an existing application measure record. This is the procedure most commonly targeted by the search term "update_application_measure" and is invoked indirectly through the public API.
  • DELETE_APPLICATION_MEASURE — Removes an application measure definition.
  • VALIDATE_APPLICATION_MEASURE — Performs internal consistency and referential validation before create, update, or delete operations proceed.
  • VALUE_ID_CONVERSION — Converts or resolves identifier values used internally by the measure framework.
  • RETRIEVE_LAST_UPDATE_DATE — Returns the last update timestamp for an application measure, supporting concurrency and synchronization logic.
  • LOCK_RECORD — Obtains a row-level lock on the underlying record to enforce serialized updates.

The package also declares the Application_Measure_Rec_Type record structure and the Application_Measure_Tbl_Type table type, which carry application identification, measure identification, owning application, dataset_id, and the standard WHO audit columns.

Tables Accessed

  • BIS_APPLICATION_MEASURES — The primary base table holding application measure definitions and audit columns; all DML operations target this table.
  • BIS_INDICATORS — Referenced for the dataset_id column domain and for validation of indicator/dataset relationships.
  • PLITBLM — A standard EBS indexing helper table used to resolve primary key values and support surrogate key generation.

Usage Notes

Because this is a private package, it should never be invoked directly by customer code. External callers should use the public package BIS_APPLICATION_MEASURE_PUB, which wraps and delegates to these procedures and manages error handling and API conventions. The procedures are typically invoked from BIS setup forms and concurrent programs where administrators maintain performance measurement definitions, and from internal BIS flows during data collection and benchmarking. Customers implementing custom integrations or extensions should route all create, update, and delete operations through the public API to preserve validation, locking, and audit behaviour. In EBS 12.2.2 the same source metadata continues to apply, though operational deployment shifts to the online patching edition framework; the API contract itself remains unchanged.