Search Results validate_record

Overview

BIS_DIMENSION_VALIDATE_PVT is a private API package body in the APPS schema that supports the Oracle EBS Business Intelligence System (BIS) dimensional modeling framework. Its specific business function is to validate the contents of a Dimensions record before that record is persisted or processed by the public dimension APIs. In EBS, dimension definitions describe the axes of analysis (such as product, customer, time, and channel) used by the BIS/Data Warehouse products. Because invalid dimension metadata can cascade into reports, collections, and analytical structures, the private validator enforces minimum data-integrity rules at the point of entry. The package header dates from April 1999, and the body carries the file identifier BISVDIVB.pls, reflecting its origin in the BIS dimensional infrastructure that remains part of the APPS schema in 12.1.1 and 12.2.2. The "PVT" designation indicates that the package is not intended for direct customer invocation; it is a private implementation layer invoked by public or sibling packages within the same product.

Key Procedures and Functions

The documented package exposes a single procedure:

• VALIDATE_RECORD — The core validation routine for a dimension record. It accepts a dimension record structure, evaluates the record's fields for completeness and correctness, and returns a status indicator along with an error table populated with any validation failures. The procedure is the sole documented entry point, confirming the package's narrow, single-purpose design as a validation utility. Callers pass the record to be checked and receive back a return status and a collection of error messages that can be surfaced to the user or logged by the calling process. The procedure raises the standard FND_API error exceptions when validation fails.

No public functions are documented for this body; all other logic in the file is internal implementation detail supporting VALIDATE_RECORD.

Tables Accessed

The documented metadata for this package body does not list any tables referenced through APPS synonyms. This is consistent with the excerpt, which shows the procedure performing field-level checks against the incoming record structure and delegating message handling to BIS_UTILITIES_PVT rather than querying base tables directly. Validation is therefore record-driven rather than table-driven: the caller supplies the dimension record, and the procedure evaluates it in memory. Where lookups against dimension definitions occur, they would be performed by the calling public API before or after this validation call. Any consumer of this package should not assume the validator performs its own database reads.

Usage Notes

This package is a private API and is referenced by one other package, which is expected to be the corresponding public BIS dimension package or a closely related utility. It is not designed to be called directly from Oracle Forms, concurrent programs, or customer extensions. Standard EBS practice is to invoke the public API, which in turn calls the private validator as part of its processing sequence. Custom code that needs dimension validation should use the public interface rather than calling BIS_DIMENSION_VALIDATE_PVT.VALIDATE_RECORD directly, because the private signature and validation semantics are subject to change without notice. The procedure follows the Oracle Applications API conventions of the period, including use of the FND_API validation level parameter and the standard return status values, and it raises FND_API exceptions that propagate to the caller for consistent error handling. Because the package is distributed in the APPS schema, it is available in both 12.1.1 and 12.2.2 environments, though it should be treated as internal infrastructure.