Search Results retrieve_measure_security




Overview

APPS.BIS_MEASURE_SECURITY_PUB is the public API package body within the Oracle E-Business Suite Business Intelligence System (BIS) schema that governs the creation and maintenance of Performance Measurement security. Performance Measurements are the analytical objects exposed through the Oracle Balanced Scorecard and related BIS reporting components, and the security metadata associated with each measurement determines which responsibilities and users are permitted to view, modify, or administer a given measurement. This package encapsulates that logic behind a documented, versioned PL/SQL interface so that callers do not manipulate the underlying BIS tables directly.

The package implements the standard EBS API contract, accepting a p_api_version argument, honoring the p_commit flag through FND_API constants such as G_FALSE, and returning status through x_return_status along with a structured error table of type BIS_UTILITIES_PUB.Error_Tbl_Type. It is classified as a PUB API, meaning it is intended for external consumption by other BIS packages, Oracle Forms, and custom extensions rather than being restricted to internal schema use. Internal helper logic is delegated to BIS_MEASURE_SECURITY_PVT, including value identifier conversion and error message assembly.

Key Procedures and Functions

  • CREATE_MEASURE_SECURITY — Establishes a new security definition for a performance measurement, accepting a Measure_Security_Rec_Type record. It first invokes BIS_MEASURE_SECURITY_PVT.Value_ID_Conversion to translate the supplied identifiers into their internal values, then validates the conversion result before persisting the record.
  • RETRIEVE_MEASURE_SECURITIES — Returns the complete set of security assignments associated with measurements, supporting bulk retrieval for administrative and reporting use.
  • RETRIEVE_MEASURE_SECURITY — Returns the security definition for a single measurement, providing the singular counterpart to the bulk retrieval above.
  • UPDATE_MEASURE_SECURITY — Modifies an existing measurement security definition, applying the same identifier conversion and error-handling discipline as creation.
  • DELETE_MEASURE_SECURITY — Removes a measurement-level security definition.
  • VALIDATE_MEASURE_SECURITY — Performs consistency and validity checks on a prospective security record without committing it, allowing callers to pre-validate input.
  • DELETE_TARGETLEVEL_RESP — Added in version 115.25 (25-NOV-03) to delete responsibilities at the target level, extending security administration beyond the measurement level. Package history also notes an earlier revision separating local variables for IN and OUT parameters, and the original creation in November 1998.

Tables Accessed

The supplied metadata does not enumerate the base tables reached through APPS synonyms. By their naming and function, the procedures operate on the BIS measurement security tables that store the pairing of a performance measurement with the responsibility or user granted access to it, together with the target-level responsibility mappings administered by DELETE_TARGETLEVEL_RESP. Identifier conversion performed by BIS_MEASURE_SECURITY_PVT implies lookups against measurement and responsibility definition tables to resolve internal keys from externally supplied values. The package itself is referenced by four other packages, confirming it acts as a dependency for downstream BIS security consumers.

Usage Notes

The package is typically invoked from the Oracle Balanced Scorecard administrative forms, from concurrent programs that provision or synchronize measurement security, and from custom PL/SQL that extends BIS security behavior. Callers must supply a valid p_api_version, inspect x_return_status for FND_API.G_RET_STS_SUCCESS, and read the returned error table when failures occur; the validation path raises the BIS_INVALID_MSR_SECURITY_VALUE message when supplied measurement security identifiers cannot be resolved. The p_commit parameter should be set to FND_API.G_TRUE only when the caller wants the API to commit independently of an enclosing transaction.