Search Results validate_time_level_value_id




Overview
Explore in AI Chat

Overview

APPS.BIS_ACTUAL_VALIDATE_PVT is a private validation package within the Oracle EBS Business Intelligence System (BIS) product family, responsible for validating records that populate the ACTUALs fact tables used by the BIS/Discoverer reporting schema. The package name carries the _PVT suffix, which by Oracle EBS API naming convention denotes a private API — it is not intended for direct invocation by external callers and instead forms the internal validation layer behind the public BIS_ACTUAL_PUB API. Its header comment explicitly states its purpose as a "Private API for validating items in the ACTUALs record." The package body carries the source identifier BISVAVVS.pls and is compiled with AUTHID CURRENT_USER, and its copyright header dates to 1998 with a revision date of 2002. The package remains documented in both 12.1.1 and 12.2.2, with the same eleven documented validation routines.

Key Procedures and Functions

The package exposes a family of granular validation routines, each targeting a specific segment of an ACTUAL record passed in as a BIS_ACTUAL_PUB.ACTUAL_Rec_Type structure. All routines follow a uniform contract: they accept an API version and a validation level (defaulting to FND_API.G_VALID_LEVEL_FULL), receive the ACTUAL record, and return a return status along with an error table of type BIS_UTILITIES_PUB.Error_Tbl_Type.

  • VALIDATE_TARGET_LEVEL_ID — validates the target level identifier on the ACTUAL record.
  • VALIDATE_ORG_LEVEL_VALUE_ID — validates the organization level value identifier (present in the documented signature list).
  • VALIDATE_DIM1_LEVEL_VALUE_ID through VALIDATE_DIM7_LEVEL_VALUE_ID — seven routines validating each of the seven generic dimension level value identifiers that make up the multi-dimensional key of an ACTUAL record.
  • VALIDATE_TIME_LEVEL_VALUE_ID — validates the time level value identifier. Notably, the ETRM source excerpt shows this procedure commented out in the source body, meaning the routine is documented in metadata but disabled within the shipped code.
  • VALIDATE_ACTUAL_VALUE — validates the measure/amount value stored on the ACTUAL record.
  • VALIDATE_RECORD — orchestrates validation of the complete ACTUAL record, invoking the individual level and value checks.

Because these are private routines, no direct parameter lists should be assumed beyond the documented uniform signature pattern.

Tables Accessed

The ETRM metadata does not enumerate specific tables referenced through APPS synonyms for this package. Functionally, the validation routines resolve the various level value identifiers against the BIS level and hierarchy metadata tables (such as the BIS level value and dimension member definitions), and they rely on FND_API and BIS_UTILITIES_PUB for error handling. The validation layer checks that each identifier supplied on an incoming ACTUAL record corresponds to a valid, existing level value within the BIS dimensional model before the fact row is committed.

Usage Notes

BIS_ACTUAL_VALIDATE_PVT is invoked indirectly through the public BIS_ACTUAL_PUB API, which the metadata notes is referenced by two other packages. It is not intended to be called directly from forms, concurrent programs, or custom code; direct calls would bypass the public API contract and risk incompatibility across patches. The user search term validate_time_level_value_id maps to the VALIDATE_TIME_LEVEL_VALUE_ID routine, which — per the source excerpt — is commented out in the shipped package, so callers seeking time-level validation should confirm actual behavior against the installed code in their 12.1.1 or 12.2.2 instance rather than relying on the metadata listing alone.