Search Results retrieve_user_target_levels

Overview

The APPS.BIS_TARGET_LEVEL_PUB package body is the public, supported PL/SQL API layer for managing target level definitions within the Oracle E-Business Suite Balanced Scorecard and business intelligence framework. In the ETRM (E-Business Suite Technical Reference Manual) for releases 12.1.1 and 12.2.2, it carries a PUB API classification, meaning it is intended for external invocation by forms, concurrent programs, and custom extensions. The package encapsulates the business logic required to create, retrieve, update, validate, translate, and load target level records. Target levels represent the thresholds or objectives assigned to business indicators across the dimensions defined in the Balanced Scorecard model, and this package provides a stable transactional interface so that the underlying private implementation (BIS_TARGET_LEVEL_PVT) and utility routines (BIS_UTILITIES_PUB, BIS_UTILITIES_PVT, BIS_MEASURE_PUB, BIS_MEASURE_PVT) remain hidden. The object is documented as VALID in the APPS schema and it is referenced by 34 other database objects, indicating broad internal reuse across the Balanced Scorecard subsystem.

Key Procedures and Functions

The ETRM metadata documents 12 procedures and functions in this package body:

• CREATE_TARGET_LEVEL — Creates a new target level record using the standard EBS API pattern (validation, message handling, and commit control).
• RETRIEVE_TARGET_LEVELS — Returns the full set of target levels matching the requested context.
• RETRIEVE_TARGET_LEVEL — Returns a single target level record identified by its key.
• UPDATE_TARGET_LEVEL — Modifies an existing target level and persists the changes back to the base tables.
• DELETE_TARGET_LEVEL — Removes a target level definition.
• VALIDATE_TARGET_LEVEL — Performs server-side validation of the attributes supplied for a target level before insert or update.
• RETRIEVE_USER_TARGET_LEVELS — Returns target levels scoped to a particular user.
• TRANSLATE_TARGET_LEVEL — Handles the translated (language-specific) attributes of a target level.
• LOAD_TARGET_LEVEL — Loads target level data, typically as part of a bulk or setup loading operation.
• GET_ID_FROM_DIMLEVELSHORTNAMES — Resolves a target level identifier from dimension-level short names.
• RETRIEVE_TL_FROM_DIMLVLSHNMS — Retrieves translated target level information based on dimension-level short names.
• UPDT_TL_ATTRIBUTES — Updates target level attributes as a helper routine within the public API flow.

Tables Accessed

The package accesses the following base and translated tables through APPS synonyms:

• BIS_INDICATORS — Stores the business indicator definitions to which target levels are associated.
• BIS_INDICATORS_TL — Holds the translated (language-specific) indicator descriptions.
• BIS_LEVELS_TL — Stores translated target level definitions, including language-dependent text.
• FND_USER — Used by RETRIEVE_USER_TARGET_LEVELS to resolve user-scoped target levels.
• PLITBLM — The PL/SQL table (index-by) used for internal bulk processing of collections.

The package body additionally depends on BIS_MEASURE_PUB, BIS_MEASURE_PVT, BIS_TARGET_LEVEL_PVT, BIS_UTILITIES_PUB, BIS_UTILITIES_PVT, FND_API (standard API framework), FND_MSG_PUB (message stack), and the STANDARD package.

Usage Notes

Because BIS_TARGET_LEVEL_PUB is classified as a public API, it is the correct entry point for custom code and extensions that need to manipulate target levels; direct DML against BIS_LEVELS_TL or BIS_INDICATORS is not supported. Typical invocations occur from the Balanced Scorecard definition forms, from concurrent programs that load or translate target level setup data, and from custom PL/SQL wrappers that use the standard FND_API message and commit conventions. Callers should always check the returned API status and inspect FND_MSG_PUB for validation errors after invoking CREATE, UPDATE, or DELETE operations. The presence of LOAD_TARGET_LEVEL and TRANSLATE_TARGET_LEVEL confirms that both bulk setup loading and multilingual maintenance scenarios are anticipated uses. Since the package is not referenced by any other database object per the ETRM dependency report, its 34 inbound references are external callers rather than schema-level dependents, reinforcing its role as a boundary API for the Balanced Scorecard target level entity.