Search Results create_ind_level_view




Overview
Explore in AI Chat

Overview

APPS.BIS_TARGET_UTIL is a utility package within the Oracle EBS Balanced Scorecard and Business Intelligence System (BIS) product family. Its principal business function is to dynamically generate and manage database views over the BIS target and indicator metadata schema at runtime. Rather than storing fixed, pre-built views for every dimension level or indicator, the package constructs SQL-backed views on demand using dynamic SQL, allowing the application to support a configurable, user-defined hierarchy of target levels and indicators without requiring schema changes. This design supports the flexible, metadata-driven nature of Balanced Scorecard, where administrators can define indicator levels and their associated dimension structures at implementation time and evolve them over time.

Key Procedures and Functions

The package exposes six documented procedures, all following the standard EBS API error-handling convention with x_return_status, x_msg_count, and x_msg_data output parameters.

  • Create_Ind_Level_View — Accepts an indicator level name and generates a database view for that target level, enabling downstream reporting and query access against the level's indicator data.
  • Create_Indicator_views — Generates views for a specific named indicator, giving the indicator a queryable relational representation.
  • Create_BIS_views — A broader orchestration routine that creates the full set of BIS views, typically invoked after bulk metadata changes or system initialization.
  • Drop_Ind_Level_View — Removes a previously created indicator level view, taking the target level identifier. This maintains schema hygiene when levels are reconfigured or deleted.
  • Get_Dimension_Display_Value — Resolves a dimension level value identifier into its human-readable display name, supporting UI rendering of target hierarchies.
  • Validate_Resp_Org — Validates that a responsibility, organization, and user context combination is permissible for a given dimension level, enforcing access control over which users can view or manage specific targets.

Note that the parameter signatures above reflect Oracle's documented specification; callers should rely on the published API rather than assuming additional parameters.

Tables Accessed

The package references several tables through APPS synonyms, which serve as both the source of view-generation metadata and the validation targets:

  • BIS_TARGET_LEVELS — the primary driver for Create_Ind_Level_View and Drop_Ind_Level_View; stores the configured target level definitions.
  • BIS_INDICATORS — provides indicator metadata used by Create_Indicator_views.
  • BIS_LEVELS — supplies level and dimension hierarchy information, used particularly in display value resolution and validation.
  • DBMS_SQL — the Oracle-supplied dynamic SQL package, used to parse and execute the generated DDL statements. DBMS_SQL is not a BIS table but is essential to the package's view-creation mechanism.

Usage Notes

Because it is an internal utility (API classification UTIL) rather than a functional API, BIS_TARGET_UTIL is not typically invoked by end users. It is called by the Balanced Scorecard setup forms and by concurrent programs whenever administrator actions alter target level or indicator metadata — for example, saving a new target level triggers Create_Ind_Level_View, while deleting one invokes Drop_Ind_Level_View. Setup and migration processes may call Create_BIS_views to rebuild the full view set. Custom code that integrates with Balanced Scorecard reporting may also call these routines, but should do so cautiously: the procedures execute DDL, so they require appropriate privileges and should be run within a controlled transaction context. Implementers are advised to treat the package as a schema-maintenance utility and to invoke it through supported setup flows rather than directly modifying its behavior.