Results for “retrieve_user_target_levels”

8 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

BIS_TARGET_LEVEL_PUB is a public PL/SQL API within the Oracle EBS Business Intelligence System (BIS) product family that creates and manages Indicator Target Levels and their associated dimensional attributes. Target Levels define the specific organizational, time, and dimension-level context against which a performance indicator (measure) is evaluated, enabling the Balanced Scorecard and indicator framework to associate measurements with meaningful business targets. As a PUB classified package, it is designed for external invocation by Oracle Forms, other APIs, and custom code, in contrast to the private BIS_Target_Level package it fronts. The package header carries a header comment identifying an original internal filename (BISVINLS.pls) and describes the API as one for "creating and managing Indicator Levels," reflecting its lineage and evolution across releases. The ETRM metadata documents twelve procedures/functions, five referenced tables, and references from 34 other packages, indicating broad use across the BIS indicator and reporting subsystems.

Key Procedures and Functions

  • CREATE_TARGET_LEVEL — Creates a new target level record, persisting the measure, dimension, organization, and time level associations that define the target.
  • RETRIEVE_TARGET_LEVELS — Returns the full set of target levels matching the caller's criteria; used by list and query screens.
  • RETRIEVE_TARGET_LEVEL — Returns a single target level, typically keyed by target level identifier, for detail display and validation.
  • UPDATE_TARGET_LEVEL — Modifies an existing target level's attributes.
  • DELETE_TARGET_LEVEL — Removes an existing target level definition.
  • VALIDATE_TARGET_LEVEL — Performs business-rule validation on a target level record prior to create or update.
  • RETRIEVE_USER_TARGET_LEVELS — Returns target levels scoped to a specific user, drawing on FND_USER assignments.
  • TRANSLATE_TARGET_LEVEL — Populates or maintains the translatable name and description attributes for a target level.
  • LOAD_TARGET_LEVEL — Loads target level data, supporting bulk initialization or migration scenarios.
  • GET_ID_FROM_DIMLEVELSHORTNAMES — Resolves a dimension level identifier from its short name, which allows callers to work with user-friendly names instead of internal IDs.
  • RETRIEVE_TL_FROM_DIMLVLSHNMS — Retrieves target level information based on dimension-level short names, complementary to the preceding function.
  • UPDT_TL_ATTRIBUTES — The procedure corresponding to the search term "updt_tl_attributes"; it updates target level attributes, including name and description values, on an existing target level record.

Tables Accessed

  • BIS_INDICATORS — The base indicator (measure) definition table, supplying measure identity and dataset context.
  • BIS_INDICATORS_TL — The translatable name/description table for indicators, providing measure name and description.
  • BIS_LEVELS_TL — The translatable level table, providing organization, time, and dimension level names.
  • FND_USER — The application user table, used to resolve user-specific target level assignment.
  • PLITBLM — Oracle's PL/SQL index-by table (array) package used for bulk data handling within PL/SQL collections.

Usage Notes

BIS_TARGET_LEVEL_PUB is typically invoked from the Business Intelligence System's indicator setup and Balanced Scorecard forms, where administrators define and maintain target levels, and from concurrent programs that load or migrate target level data. Because it is a published API and referenced by 34 other packages, it is also the sanctioned integration point for custom PL/SQL that needs to create, query, or update target levels; callers should prefer this package over direct DML on the underlying BIS tables. The name and description fields are drawn from _TL tables, so language-specific behavior governed by TRANSLATE_TARGET_LEVEL applies during setup and maintenance. The trailing "_PUB" suffix confirms the package is intended for supported external use, and its procedures should be invoked with the standard EBS API conventions (FND_API-style success/error handling) rather than as low-level utilities.