Search Results igs_pr_val_pra




Overview
Explore in AI Chat

Overview

IGS_PR_VAL_PRA is a validation package body in the APPS schema belonging to the Oracle E-Business Suite Student Systems (Higher Education) product family, specifically the Prospect and Recruitment (IGS_PR) module. Its name follows the module convention IGS_PR_VAL_*, where "VAL" denotes a validation package and "PRA" identifies the entity or business object being validated. The package encapsulates server-side validation logic that enforces the business rules governing prospect and recruitment data before records are inserted, updated, or transitioned in status. In Oracle EBS 12.1.1 and 12.2.2, such validation packages are typically invoked from the PL/SQL form and OA Framework layers, from concurrent programs, or from other packages as part of a validation chain. The ETRM metadata records IGS_PR_VAL_PRA as VALID with an API classification of OTHER, indicating that it is an internal technical component rather than a published, supported public API. It is not referenced by any database object at the schema-dependency level, although the functional layer records it as referenced by three other packages. This asymmetry is characteristic of Oracle seed data: the package body is a leaf in the dependency graph and is expected to be called dynamically or from form-level triggers.

Key Procedures and Functions

The ETRM metadata documents four procedures and functions within the package body:

  • PRGP_VAL_PRA_RQRD — Validates that all required (mandatory) attributes of the prospect/recruitment entity have been supplied. This procedure enforces completeness before a record is accepted for further processing.
  • PRGP_VAL_PRGC_CLOSED — Checks whether the associated prospect/recruitment category is closed and raises the appropriate validation failure when a transaction or status change is attempted against a closed category.
  • PRGP_VAL_PRR_CLOSED — Performs the analogous closed-status check for the prospect/recruitment rule or rule set, preventing activity against rules that have been closed for use.
  • CRSP_VAL_CRV_ACTIVE — Verifies that the relevant curriculum version is active, ensuring that prospect/recruitment records reference only currently valid curriculum structures.

No parameter lists are documented here; callers should consult the package specification (IGS_PR_VAL_PRA) for exact signatures. Each routine follows the standard validation contract: it returns or raises a validation outcome and emits a message through FND_MESSAGE when a rule is violated.

Tables Accessed

The package body reads the following tables via APPS synonyms:

  • IGS_PS_VER_ALL — the curriculum version view/table, queried to confirm that a referenced version exists and is active (supporting CRSP_VAL_CRV_ACTIVE).
  • IGS_PR_RU_CAT — the prospect/recruitment category table, read to determine category closed status for PRGP_VAL_PRGC_CLOSED.
  • IGS_PS_STAT — the status table used to resolve status codes and their meanings during validation, notably to identify closed states.

Additional documented dependencies include IGS_PR_RULE, IGS_PS_VER, the package specification IGS_PR_VAL_PRA itself, FND_MESSAGE (for error message retrieval), and the SYS STANDARD package. These are referenced statically; the package performs no DML on the listed tables, being a read-only validation component.

Usage Notes

IGS_PR_VAL_PRA is an internal validation layer. It is normally invoked indirectly rather than called directly by custom code: the Prospect and Recruitment forms and related OA Framework pages call these routines during record validation and save processing, and other IGS_PR packages invoke them as part of broader validation sequences — consistent with the metadata noting three referencing packages. Because the object is classified OTHER and is not a published API, Oracle does not guarantee the signature or behaviour of its procedures across releases; customisations should avoid direct calls and instead rely on the supported public APIs of the IGS_PR module. When troubleshooting validation errors originating from this package, the FND_MESSAGE dependency is significant: error text presented to the user is retrieved through the message dictionary, so the message name and the failing routine together identify the rule that has been breached. As with all APPS validation package bodies in 12.1.1 and 12.2.2, the compiled body resides in the APPS schema and should only be modified through supported patching, never by direct recompilation in a production environment.