Search Results validate_dim1_level_value_id




Overview
Explore in AI Chat

Overview

BIS_ACTUAL_VALIDATE_PVT is a private (PVT) PL/SQL API belonging to the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It forms part of the Oracle Business Intelligence System (BIS) foundation layer, which underpins the DBI/BIS intelligence products used for dimensional reporting and business analysis. The package provides the internal validation engine for records written to the ACTUALs entity — the transactional fact records that capture measured results against a defined dimensional model. Its responsibilities include verifying that a record's target level, organizational context, and each of the dimensional level value identifiers conform to the expected structure of the intelligence schema before the record is persisted or manipulated. As a private API, it is not exposed for direct customer invocation; it is called by the public BIS_ACTUAL_PUB package and a small number of related internal packages that depend on it. This design isolates referential and structural validation logic from the public programming interface, allowing Oracle to evolve the checks without altering the public contract. The package header carries the AUTHID CURRENT_USER directive and an early source control header (BISVAVVS.pls, version 115.7, dated December 2002), reflecting its long-standing stability across releases.

Key Procedures and Functions

The documented API surface comprises eleven procedures, each following a consistent validation signature that accepts an API version, a validation level defaulting to FND_API.G_VALID_LEVEL_FULL, an ACTUAL_Rec_Type record based on BIS_ACTUAL_PUB, and returns a status plus an error table.

  • VALIDATE_TARGET_LEVEL_ID — validates the target level identifier within the actuals record, confirming the record is directed at a valid level of the intelligence hierarchy.
  • VALIDATE_ORG_LEVEL_VALUE_ID — the procedure matching the user's search term; validates the organization level value identifier, ensuring the organizational dimension value referenced by the record is valid. Note that in the excerpted source this procedure appears within a commented block, indicating it may be conditionally present or superseded, while the documented metadata confirms it as an exposed procedure.
  • VALIDATE_DIM1_LEVEL_VALUE_ID through VALIDATE_DIM7_LEVEL_VALUE_ID — seven parallel procedures that validate the level value identifier for each of the seven generic dimensions supported by the intelligence model. Each checks that the supplied value belongs to the appropriate dimension level.
  • VALIDATE_ACTUAL_VALUE — validates the measured actual value itself, covering its presence and type conformance.
  • VALIDATE_RECORD — the master orchestrator that invokes the individual validation routines to perform a full-record check.

Tables Accessed

The ETRM metadata lists no tables referenced through APPS synonyms for this package. Validation of level value identifiers is generally accomplished through programmatic checks, lookup against cached level metadata, and helper calls in BIS_UTILITIES_PUB rather than through direct DML against base tables. Consequently, the package is best characterized as a read-only validation component that returns error information through BIS_UTILITIES_PUB.Error_Tbl_Type rather than issuing inserts, updates, or deletes itself.

Usage Notes

BIS_ACTUAL_VALIDATE_PVT is invoked internally by the public BIS_ACTUAL_PUB API during the create, update, and validate operations on actuals records, and by at least two other packages recorded in the metadata. It is typically reached through PL/SQL calls originating from concurrent programs, business intelligence data loading routines, and custom integrations that operate on the actuals entity through the public API layer. Developers who search for validate_org_level_value_id should note that the organization-level validation is one facet of a broader suite of dimension checks executed by VALIDATE_RECORD. Because this is a private package, direct calls are unsupported; custom code should target BIS_ACTUAL_PUB and rely on the error table to interpret validation failures.