Results for “retrieve_time_level”

4 results




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

Overview

BIS_TARGET_LEVEL_PVT is the private implementation package body for the Oracle EBS Business Intelligence System (BIS) target level subsystem, residing in the APPS schema. In the Oracle EBS layered API architecture, the _PVT suffix denotes an internal, implementation-level package whose procedures are typically invoked only by its public counterpart, BIS_TARGET_LEVEL_PUB. The package manages the definition, maintenance, and retrieval of target levels — the hierarchical entities against which business performance targets are assigned and measured across dimensions, indicators, and organizational structures within Oracle Balanced Scorecard and related BIS modules.

The package is documented as VALID and exposes 24 procedures and functions, encompassing the full lifecycle of target level records: creation, query, update, deletion, translation, and validation. It therefore acts as the persistence and business-rule engine behind the public target level API.

Key Procedures and Functions

The documented procedures fall into several functional clusters:

No parameter signatures are documented in the ETRM record; callers must consult the package specification for exact arguments.

Tables Accessed

The package reads and writes the following documented tables, primarily via APPS synonyms:

Usage Notes

BIS_TARGET_LEVEL_PVT is an internal layer and is not intended for direct customer invocation; the documented dependency list shows it is referenced by 14 other packages, including BIS_TARGET_LEVEL_PUB, BIS_TARGET_LEVEL_VALIDATE_PVT, BIS_TARGET_PUB, and BIS_COMPUTED_TARGET_PVT. It draws on shared utilities such as FND_API for API error handling, BIS_UTILITIES_PUB/PVT, and BIS_MEASURE_PVT, and FND_MSG_PUB for message stack management. In practice it is invoked indirectly from Oracle Balanced Scorecard forms and concurrent programs that maintain target levels, and from custom code that calls the public wrapper. Customizations should always target BIS_TARGET_LEVEL_PUB rather than this private body to remain upgrade-safe.