Search Results translate_dimension

Overview

BIS_DIMENSION_PVT is a private PL/SQL API package owned by the APPS schema in Oracle E-Business Suite, introduced with the Key Performance Framework that underpins the Balanced Scorecard (BSC) and Business Intelligence System (BIS) product family. The package header ($Header: BISVDIMS.pls 120.0, dated 01-JUN-2005) identifies it as the "Private API for managing Dimensions and dimension levels for the Key Performance Framework." Dimensions in this context are the analytical axes — organizational unit, time period, product line, customer segment, and similar — against which key performance indicators are measured and aggregated.

The package is classified as PVT, meaning it is an internal implementation layer rather than a published integration surface. The header comment explicitly notes that the package "should be maintained by EDW once it gets integrated with BIS," signalling that the code originated as a staging utility and was expected to be absorbed into the broader Enterprise Data Warehouse dimension services. Customizations should therefore avoid direct dependencies on this package.

Because the object name is sometimes matched loosely against unrelated businesses, it is worth stating plainly: APPS.BIS_DIMENSION_PVT is an Oracle EBS seeded database object, not a vendor or consulting entity. Its sole purpose is programmatic dimension and dimension-level administration within the BIS/BSC schema.

Key Procedures and Functions

The package exposes sixteen documented procedures, grouped by function:

• RETRIEVE_DIMENSIONS — populates a collection of dimension records for the caller, returning status and error information.
• RETRIEVE_DIMENSION — fetches a single dimension record matching the supplied identifier or key.
• CREATE_DIMENSION — inserts a new dimension definition along with its associated levels.
• UPDATE_DIMENSION — modifies attributes of an existing dimension definition.
• TRANSLATE_DIMENSION and TRANSLATE_DIM_BY_GIVEN_LANG — maintain translated dimension names and descriptions, either across all installed languages or restricted to one requested language.
• VALIDATE_DIMENSION — performs business-rule validation prior to create or update, a check strengthened by the 09-FEB-05 fix for Bug 4172055 covering dimension name validation.
• DUPLICATEDIMENSION and REMOVEDUPLICATES — copy an existing dimension definition and clean up resulting duplicate level or group rows.
• DELETE_DIMENSION — removes a dimension and its dependent level records; added 23-FEB-2003.
• VALUE_ID_CONVERSION — converts between dimension value identifiers and internal representations; the OUT parameter was changed to IN OUT on 04-JAN-03 as the fix for Bug 2735908.
• VALIDATE_PMF_UNIQUE_NAME — enforces name uniqueness against Performance Management Framework constraints.

All retrieval procedures follow the standard EBS API convention of returning an x_return_status flag and an error table (BIS_UTILITIES_PUB.Error_Tbl_Type) so that callers can inspect failures without relying on exceptions.

Tables Accessed

The package works against a tightly scoped set of BIS/BSC base tables, all addressed through APPS synonyms:

• BIS_DIMENSIONS, BIS_DIMENSIONS_S, BIS_DIMENSIONS_TL — the base, sequence/primary-key staging, and translation tables for dimension definitions.
• BSC_SYS_DIM_LEVELS_B and BSC_SYS_DIM_LEVELS_BY_GROUP — dimension level hierarchies and their grouping assignments.
• FND_LANGUAGES — drives the translation procedures by identifying installed languages.
• DUAL — used for scalar evaluation and sequence-style queries.
• PLITBLM — the standard EBS PL/SQL index-by table of VARCHAR2 used by the utility error-handling routines.

Usage Notes

As a PVT-classified package, BIS_DIMENSION_PVT is not intended for direct invocation by customer code. It is called from the BSC/BIS application forms and concurrent programs that administer scorecard dimensions, and ETRM records five other packages that reference it, which are responsible for the public-facing wrapper logic. The historical note that get_unique_dim_group_name() was added in July 2003 and then removed days later — with the logic relocated to the BSC API — illustrates the package's role as a back end whose responsibilities were progressively migrated upward. Developers extending Balanced Scorecard functionality should call BIS_DIMENSION_PUB or the BSC public APIs instead, and any augmentation of this package should be treated as an upgrade-sensitive modification requiring an EBS patch impact assessment.