Search Results validate_range1_high

Overview

APPS.BIS_TARGET_VALIDATE_PVT is a private PL/SQL API package within the Oracle E-Business Suite Business Intelligence System (BIS) product family. It is declared with AUTHID CURRENT_USER and carries a header stamp of 115.8 dated 2003, confirming its lineage as a long-standing component of the EBS codebase carried forward through releases 12.1.1 and 12.2.2.

The package serves as the internal validation engine for the Targets record structure. As indicated by its embedded description, it is a "Private API for validating items in the targets record," operating against the BIS_TARGET_PUB.Target_Rec_Type record type defined in the public targets API layer. Its role is to enforce attribute-level correctness before a targets row is committed, allowing the public API to surface structured errors rather than failing on database constraint violations. The PVT designation signals that it is not intended as a public integration point; callers should use BIS_TARGET_PUB instead.

The user search term "validate_plan_id" maps directly to the VALIDATE_PLAN_ID procedure documented in the package source, confirming coverage of this specific validation concern.

Key Procedures and Functions

The ETRM metadata documents 24 procedures in total. The source excerpt exposes four, and the remainder are enumerated in the documented procedure list. All follow a consistent signature pattern: an API version, a validation level defaulting to FND_API.G_VALID_LEVEL_FULL, an inbound BIS_TARGET_PUB.Target_Rec_Type record, an outbound return status, and an outbound error table of type BIS_UTILITIES_PUB.Error_Tbl_Type.

• VALIDATE_TARGET_LEVEL_ID — validates the target level identifier against the targets record.
• VALIDATE_PLAN_ID — validates the business plan referenced by the targets record; this is the procedure most directly relevant to the "validate_plan_id" search.
• VALIDATE_ORG_LEVEL_VALUE_ID — validates the organization level value identifier.
• VALIDATE_TIME_LEVEL_VALUE_ID — validates the time level value identifier.
• VALIDATE_DIM1_LEVEL_VALUE_ID through VALIDATE_DIM7_LEVEL_VALUE_ID — seven parallel procedures validating each of the seven dimension level value identifiers against the targets record.
• VALIDATE_TARGET_VALUE — validates the numeric target value.
• VALIDATE_RANGE1_LOW, VALIDATE_RANGE1_HIGH, VALIDATE_RANGE2_LOW, VALIDATE_RANGE2_HIGH, VALIDATE_RANGE3_LOW, VALIDATE_RANGE3_HIGH — six procedures validating the low and high bounds of three target ranges.
• VALIDATE_NOTIFY_RESP1_ID and VALIDATE_NOTIFY_RESP1 — validate the notification responsibility identifier and the associated responsibility attribute.

Tables Accessed

Only one table is documented as referenced via APPS synonyms: BIS_BUSINESS_PLANS. This is consistent with the presence of VALIDATE_PLAN_ID, which must confirm that the plan identifier supplied in the targets record corresponds to a valid row in the business plans table. Validation procedures for organization, time, and dimension level values resolve their lookups through the relevant BIS level definitions, while range and target value validations are predominantly numeric or formatting checks that may not require table access. The notification responsibility validations resolve through FND responsibility data.

Usage Notes

BIS_TARGET_VALIDATE_PVT is referenced by two other packages, reflecting its position as a subordinate validation layer beneath the public targets API. It is not invoked directly by forms, concurrent programs, or customer extensions. Instead, BIS_TARGET_PUB calls into this private package during create and update processing, passing the in-progress targets record and the API version. The outbound error table lets the public API aggregate multiple validation failures into a single structured response, which the calling UI or batch process can present to the user.

Because the package is compiled AUTHID CURRENT_USER, it executes with the privileges of the invoker; the APPS synonym grants access to BIS_BUSINESS_PLANS at runtime. Custom code should never call the PVT procedures directly, as their signatures are not part of the supported interface and may change across point releases, including between 12.1.1 and 12.2.2.