Search Results igs_ad_imp_prblty_val_pkg




Overview
Explore in AI Chat

Overview

The package body APPS.IGS_AD_IMP_PRBLTY_VAL_PKG is part of the Oracle E-Business Suite Advanced Admissions (IGS) product family, which underpins recruitment, prospect, and admissions processing in higher-education institutions. Its principal business function is the validation of Implicit Probability values associated with recruitment prospects and applicants. Institutions typically rank prospects by likelihood of conversion — an implicit probability or scoring value that drives list generation, targeted communications, and recruitment analytics. This package provides the server-side logic that validates, and where necessary derives or normalizes, the implicit probability attribute recorded against recruitment prospect records.

The package is in VALID status and owned by the APPS schema, which is consistent with standard EBS database object deployment conventions in 12.1.1 and 12.2.2. Because it is a package body, the callable interface is defined by its parent package specification; only one documented program unit, PRC_PRBLTY_VALUE, is exposed through the metadata.

Key Procedures and Functions

The ETRM metadata documents a single program unit for this package body:

  • PRC_PRBLTY_VALUE — The primary procedure of the package. Based on its name and the package's role, it processes an implicit probability value, performing the validation and/or calculation logic required before the value is accepted against recruitment prospect data. It is the single documented entry point and would carry the core business rules of the package. Parameter details are not exposed in the available metadata and should be confirmed against the deployed specification in the target instance.

No additional functions or procedures are documented; any internal helper routines in the body are private and not part of the documented interface.

Tables Accessed

The dependency information identifies the following base and view objects, accessed through APPS synonyms:

  • HZ_PARTIES — The Trading Community Architecture (TCA) party table, holding the person or organization that a prospect record relates to. The package uses it to resolve and confirm the party context for the probability value.
  • IGS_AD_CODE_CLASSES — Holds admissions code class definitions, used to determine the valid value set or classification applicable to implicit probability.
  • IGS_AD_RECRUIT_PI — The recruitment prospect/participant interview-prospect entity where the implicit probability attribute is persisted.
  • IGS_AD_RECRUIT_PI_V and IGS_PE_PERSON_ID_TYPE_V — Views supplying enriched prospect and person-identification data used during validation.

Dependencies also include Oracle Application Object Library utilities — FND_FILE, FND_MESSAGE, FND_STATS, FND_INSTALLATION — and the IGS_GE_MSG_STACK and IGS_GE_GEN_003 generic components, indicating message-based error reporting and standard EBS utility usage. The repeated self-reference (IGS_AD_IMP_PRBLTY_VAL_PKG shown under its own dependency list) typically reflects internal calls or recursive SQL blocks within the body.

Usage Notes

This package is an internal implementation package rather than a published public API: the metadata records that it is not referenced by any other database object and is referenced by zero other packages. That characteristic indicates the calls originate outside the PL/SQL dependency graph — most commonly from an EBS Forms-based recruitment or prospect maintenance screen, or from a concurrent program, both of which invoke APPS packages at runtime without creating a stored dependency.

Typical invocation scenarios include entry or amendment of a prospect's implicit probability; bulk prospect scoring or import routines; and list-management processes that derive candidate lists. In custom extensions, the package should be called rather than reimplemented, because it encapsulates the delivered validation semantics. ETRM confirms the object as VALID in both 12.1.1 and 12.2.2 releases, so behavior is expected to be consistent across those versions. As always, the parent package specification should be reviewed in the specific instance to confirm the exact signature before calling PRC_PRBLTY_VALUE from custom code.