Results for “validate_flag”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PV_COMMON_CHECKS_PVT is a private PL/SQL package in the Oracle EBS APPS schema that provides centralized, item-level validation routines for the Process Validation (PV) family of APIs. Its principal business function is to enforce data integrity and consistency for attributes and process rules used in Oracle Process Manufacturing-related validation logic. Rather than repeating validation code inside each public API, PV consumes these shared private checks to confirm that inbound values (object version numbers, lookup codes, rule identifiers, attribute identifiers, operators, and flags) conform to expected definitions before committing data.

The package header carries a source marker of pvrvlkps.pls 120.0 and was originally created in January 2002. It is classified as an API of type PVT (private), meaning it is intended for internal consumption by other PV packages and is not part of the publicly supported interface.

Key Procedures and Functions

The documented interface exposes eight procedures, most of which follow a common error-handling contract using FND_API message list semantics (an initialization flag, a validation mode, and OUT parameters for return status, message count, and message data).

• SET_MESSAGE — Overloaded utility that populates the FND message stack. One form accepts up to two token name/value pairs; the other accepts up to four, supporting richer, parameterized error and warning text.
• VALIDATE_OBJECT_VERSION_NUMBER — Validates the supplied object version number for the given validation mode (create versus update, using AS_UTILITY_PVT constants such as G_CREATE and G_UPDATE). This is the routine most relevant to callers searching for "validate_object_version_number," and it safeguards optimistic locking and concurrency control.
• VALIDATE_LOOKUP — Confirms that a lookup code is valid for a specific lookup type and target table/column combination, ensuring values exist in the lookup repository.
• VALIDATE_PROCESS_RULE_ID — Verifies that a supplied process rule identifier exists and is valid for the operation being performed.
• VALIDATE_ATTRIBUTE_ID — Confirms the validity of an attribute identifier referenced by PV business objects.
• VALIDATE_OPERATOR — Checks that a relational or logical operator value used in rule expressions is recognized and permitted.
• VALIDATE_FLAG — Validates yes/no or status flag values against the accepted domain.

Tables Accessed

The package references two base tables through APPS synonyms:

• FND_LOOKUP_VALUES — read by VALIDATE_LOOKUP to confirm that a given lookup code is enabled and active for the requested lookup type and context.
• PV_ATTRIBUTES_B — read to resolve and validate attribute identifiers used across PV entities.
• PV_PROCESS_RULES_B — read to confirm the existence and validity of process rule identifiers.

Usage Notes

As a PVT-class package, PV_COMMON_CHECKS_PVT is not registered as an exposed, published API. Instead it is invoked internally by other PV packages; the ETRM metadata records that it is referenced by seven sibling packages. The standard invocation pattern begins by optionally initializing the message list (P_Init_Msg_List), passing the intended P_Validation_mode, the value under test, and then inspecting X_Return_Status, X_Msg_Count, and X_Msg_Data on return. Callers should treat a non-success return status as a validation failure and surface the accumulated FND messages to the user.

Because the routines are private, customizations should avoid direct dependencies where possible and instead use the supported public PV APIs. When PV-based validation errors appear in forms or concurrent programs, the underlying cause often traces to one of these item-level checks. Oracle EBS 12.1.1 and 12.2.2 share the same package behavior; the 12.2 online patching architecture does not alter the package's logic, only the file-system editioning under which it is deployed.