Search Results validate_dimension1_level_id

Overview

BIS_TARGET_LEVEL_VALIDATE_PVT is a private PL/SQL package owned by APPS within the Oracle E-Business Suite, associated with the Business Intelligence System (BIS) product family that underpins Oracle Daily Business Intelligence and related analytics. The package encapsulates the validation logic applied to the TARGET_LEVEL record used when creating, updating, or processing targets and their associated level identifiers across the analytic schema.

The package declares AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the invoking schema rather than the definer, a common convention for private APIs invoked from within other BIS packages. As indicated by the PVT classification and the header comment, it is a private API whose stated purpose is validating items in the MEASUREs record. It is not intended for direct invocation by external or customer code; rather, it is one of the internal layers sitting beneath the public target-level API, BIS_TARGET_LEVEL_PUB, whose TARGET_LEVEL_Rec_Type record structure is passed into each validation routine.

The object carries a source header dated 2002, reflecting that its design predates the 12.1.1 and 12.2.2 releases and has been carried forward largely unchanged. Both releases rely on the same generated specification and body, so behavior is consistent across them; the primary difference in 12.2.2 is deployment under the Online Patching (adop) model and the editioning views that wrap the underlying BIS tables.

Key Procedures and Functions

ETRM documents twelve procedures in this package, all sharing the same validation signature pattern: an API version, a validation level defaulting to FND_API.G_VALID_LEVEL_FULL, an input TARGET_LEVEL_Rec of type BIS_TARGET_LEVEL_PUB.TARGET_LEVEL_Rec_Type, and two OUT NOCOPY parameters — x_return_status and x_error_Tbl of type BIS_UTILITIES_PUB.Error_Tbl_Type. The procedures are:

• VALIDATE_ORG_LEVEL_ID — validates the organization level identifier in the target-level record.
• VALIDATE_TIME_LEVEL_ID — validates the time level identifier.
• VALIDATE_DIMENSION1_LEVEL_ID through VALIDATE_DIMENSION7_LEVEL_ID — seven parallel routines, each validating the corresponding dimension level identifier (DIMENSION1 through DIMENSION7) held on the record. The user search term "validate_dimension1_level_id" maps directly to the first of these.
• VALIDATE_WF_PROCESS_SHORT_NAME — validates the workflow process short name used for target notification or approval flow.
• VALIDATE_DEF_NOTIFY_RESP_ID — validates the default notification responsibility identifier.
• VALIDATE_DF_COMPUTED_TARGET_ID — validates the identifier of the computed target definition.

Although the excerpt shows only the first four dimension procedures, the documented inventory confirms all seven exist in parallel form. Each routine writes a return status and, on failure, appends one or more rows to the error table so callers can report all validation failures in a single pass.

Tables Accessed

The package references one documented table through an APPS synonym: BIS_LEVELS. This table holds the level definitions used throughout the BIS analytic model. Each validation routine reads BIS_LEVELS to confirm that the level identifier supplied on the TARGET_LEVEL_Rec — organization, time, or one of the seven dimensions — corresponds to a valid, enabled level definition. Validation is read-only; the package does not insert, update, or delete rows in BIS_LEVELS.

Usage Notes

Because this is a private API, it is normally invoked indirectly. Calling packages — the metadata records one referencing package — execute the individual validation procedures during the processing of target-level create, update, and delete operations. Typical entry points are the public BIS_TARGET_LEVEL_PUB API, DBI setup forms, and concurrent programs that load or refresh target definitions.

Custom code should not call BIS_TARGET_LEVEL_VALIDATE_PVT directly. Instead, customizations should invoke the corresponding public API, which performs its own validation orchestration and calls these private routines internally. When debugging validation errors surfaced during target-level maintenance, examining the returned error table clarifies which specific level identifier — organization, time, or a particular dimension — failed validation against BIS_LEVELS. Because the package runs AUTHID CURRENT_USER, the invoking schema must have appropriate execute privileges and read access to BIS_LEVELS for validation to succeed.