Search Results retrieve_target_owners

Overview

APPS.BIS_PMF_DATA_SOURCE_PUB is the public API for the Data Source Connector within the Oracle E-Business Suite Balanced Scorecard and Performance Management Framework (BIS/PMF) product family. In the Oracle EBS 12.1.1 and 12.2.2 releases, this package functions as the programmatic bridge between the Performance Management Framework's metadata layer and external or internal data sources that supply measure values, targets, actuals, and target ownership information. The package header identifies it as the "Public API for the Data Source Connector," with a documented revision history spanning its creation in April 2000 through Sonar (Java) conversion work completed in January 2003. Because it is a connector-layer API, it abstracts the physical retrieval logic for performance measures away from the calling applications, allowing scorecard, alert, and analytics components to request data in a consistent, strongly typed manner.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking user rather than the definer, so callers must themselves hold the necessary object privileges on the underlying BIS tables and synonyms. It is a member of the PUB API classification and is referenced by three other packages in the documented metadata, confirming its role as a reusable dependency in the BIS measure-retrieval chain.

Key Procedures and Functions

The documented package exposes seven procedures and functions, of which five are identified in the excerpt:

• RETRIEVE_TARGET_LEVEL — Returns the target level record associated with a given measure instance and dimension level value collection. It accepts an optional all-information flag and returns a BIS_TARGET_LEVEL_PUB.Target_Level_Rec_Type record.
• RETRIEVE_TARGET — Retrieves the target record for a specified measure instance and dimension level values, returning a BIS_TARGET_PUB.Target_Rec_Type record.
• RETRIEVE_TARGET_OWNERS — Returns the target owners record for a measure instance and dimension level values, with optional alert type and alert level filters (both defaulting to NULL) and an all-information flag. The output is a BIS_TARGET_PUB.Target_Owners_Rec_Type record. This is the procedure most frequently located by users searching for "retrieve_target_owners," as it supplies the ownership detail needed for accountability and alert routing.
• RETRIEVE_ACTUAL — Documented as part of the same package, this procedure follows the same pattern to return actual (as opposed to target) values for a measure instance and dimension context.
• POST_ACTUAL — Provides the inverse write path, allowing actual results to be posted back into the framework for a measure instance and dimension context.

Across the retrieval procedures, the common input signature consists of a measure instance, a dimension-level-value table, and an all-information flag, ensuring consistent invocation semantics for every call.

Tables Accessed

The ETRM metadata does not enumerate specific base tables referenced through APPS synonyms; the documented tables referenced list is empty. Operationally, the package reads and writes the BIS Performance Management Framework measure, target, target-level, target-owner, and actual-value tables (typically the BIS_MEASURE, BIS_TARGET, BIS_TARGET_LEVEL, BIS_TARGET_OWNERS, and BIS_ACTUAL family of tables). Retrieval procedures read target, target-level, owner, and actual records for a given measure instance and dimensional context, while POST_ACTUAL writes actual values back into the framework. Because the package is AUTHID CURRENT_USER, table access is performed under the caller's schema privileges.

Usage Notes

BIS_PMF_DATA_SOURCE_PUB is typically invoked from Balanced Scorecard and Performance Management Framework UI components, concurrent programs that populate or refresh measure data, and custom PL/SQL code that extends the standard scorecard behavior. The 2003 Sonar conversion note confirms the APIs are also called from Java, underscoring their role as a stable integration surface. Customizations should treat the package as a published API: declare records using the BIS_*_PUB types, pass a populated measure instance and dimension-level-value table, and observe the all-information flag to control payload breadth. Because three other packages depend on it, changes to call conventions carry cross-package impact.