Search Results get_level_name

Overview

BIS_TARGET_UTIL is a PL/SQL utility package body owned by the APPS schema and classified under the ETRM (E-Business Suite Technology Reference Model) taxonomy as a UTIL object. It forms part of the Oracle Balanced Scorecard / Business Intelligence System (BIS) subsystem, which underpins the enterprise performance management features in Oracle E-Business Suite 12.1.1 and 12.2.2. The package provides a set of reusable helper routines for resolving target level metadata, dynamically constructing database views over target and indicator data, and validating responsibility-organization associations. Its most frequently referenced routine, GET_LEVEL_NAME, returns the descriptive short name for a given target level identifier, allowing callers to translate internal BIS_LEVELS surrogate keys into human-readable labels without embedding direct SQL against the level table. Because the package relies on FND_API and FND_MSG_PUB conventions for return status and message stacking, it conforms to the standard EBS API error-handling model and can be safely composed within larger concurrent or forms-based workflows.

Key Procedures and Functions

• GET_LEVEL_NAME — Accepts a numeric level identifier and returns the corresponding short name from BIS_LEVELS. It sets a standard FND_API return status, and on exception invokes FND_MSG_PUB.Add_Exc_Msg and FND_MSG_PUB.Count_And_Get to populate the message stack. This is the routine most commonly associated with the search term "get_level_name".
• CREATE_IND_LEVEL_VIEW — Dynamically generates an indicator-level database view by assembling a SELECT list and FROM/WHERE clauses over BIS_target_values, BIS_business_plans, and BIS_target_levels. It uses DBMS_SQL to execute the generated DDL.
• CREATE_INDICATOR_VIEWS — Wrapper routine that drives creation of the indicator-related views, typically invoking CREATE_IND_LEVEL_VIEW for each applicable level.
• CREATE_BIS_VIEWS — Top-level orchestration procedure for building the BIS reporting views. It is the entry point used during setup or maintenance operations.
• DROP_IND_LEVEL_VIEW — Removes a previously created indicator-level view, providing the inverse operation to CREATE_IND_LEVEL_VIEW.
• GET_DIMENSION_DISPLAY_VALUE — Resolves the display value for a dimension, used to present dimensional members in reports and forms.
• VALIDATE_RESP_ORG — Validates that a responsibility is correctly associated with an organization, supporting access control over Balanced Scorecard data.

Tables Accessed

• BIS_LEVELS — Read by GET_LEVEL_NAME to retrieve the SHORT_NAME for a given LEVEL_ID.
• BIS_TARGET_LEVELS — Provides target level definitions joined into view-generation SQL.
• BIS_INDICATORS — Supplies indicator metadata consumed by the view creation routines.
• DBMS_SQL — Not a table but the dynamic SQL engine used to parse and execute generated view DDL.

Usage Notes

BIS_TARGET_UTIL is normally invoked indirectly. GET_LEVEL_NAME is called by forms and concurrent programs that need to display target level names, and can be called from custom PL/SQL provided the caller supplies the standard x_return_status, x_msg_count, and x_msg_data OUT parameters. The CREATE_* and DROP_* routines are administrative and are typically run during Balanced Scorecard setup, upgrade, or view regeneration, often through concurrent program wrappers rather than ad hoc SQL. Because the package is not referenced by other documented packages, it functions as a leaf-level utility whose callers reside in forms, concurrent managers, or customer extensions. In both 12.1.1 and 12.2.2 the APPS synonyms and FND message framework remain compatible, so behavior is consistent across releases.