Results for “igs_en_val_bulkrule”

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

Overview

IGS_EN_VAL_BULKRULE is an APPS-owned PL/SQL package within the Oracle E-Business Suite Student System (Oracle Student System / IGS) product family. The prefix IGS_EN identifies it as belonging to the Enrollment functional area, and the VAL segment indicates that its role is validation rather than transaction processing. Specifically, the package supports bulk rule validation — the evaluation of enrollment rules against large sets of student unit attempts in a single pass, rather than validating one enrollment record at a time.

Institution-defined enrollment rules govern whether a student may proceed with a unit attempt: prerequisite satisfaction, calendar and teaching-period constraints, course-level restrictions, and similar academic policy checks. Bulk rule validation is used when the institution must apply these rules across an entire population of attempts, for example during bulk enrollment processing, end-of-period compliance checks, or when a rule definition is changed and existing attempts must be re-evaluated. The package is classified as OTHER in the ETRM API classification, meaning it is an internal processing utility rather than a published open interface. It is documented as VALID in the 12.1.1 ETRM repository and exhibits no outward package dependencies: it references only SYS.STANDARD and is not referenced by any other package.

Key Procedures and Functions

The ETRM metadata documents exactly two callable units within the package:

• ENRP_VAL_SCA_RULTODO — The "rule to do" validation routine. It evaluates outstanding enrollment rule actions against the relevant student records, populating the student to-do list where rule outcomes require action (for example, a warning about an unmet requirement or a task a student must complete). The name follows the standard IGS convention of EN (Enrollment), RP (procedure, in this schema's naming style), and the VAL_SCA_RUL stem denoting validation of scheduling/scalability-related rules.
• ENRP_VAL_SCA_URULE — The unit-rule validation routine. It applies the institution's unit-level enrollment rules to candidate student unit attempts, determining which attempts satisfy the defined rule criteria. Results are used by the calling process to accept, flag, or reject the attempts in question.

No parameter signatures are published in the ETRM extract, and parameter lists should not be assumed. Both procedures are internal to the enrollment validation layer and are intended to be driven by Oracle's own enrollment processes rather than by direct external calls.

Tables Accessed

Access to base tables occurs through APPS synonyms. The documented tables are:

• IGS_EN_SU_ATTEMPT_ALL — The student unit attempt entity, the primary subject of rule validation. Records are read to identify attempts requiring rule evaluation and may be updated with validation outcomes.
• IGS_EN_CAL_CONF — Enrollment calendar configuration, supplying the calendar and teaching-period context within which rules are applied.
• IGS_CA_TYPE — Calendar type reference data, used to resolve the calendar category that a rule depends on.
• IGS_PS_COURSE — The course entity, providing course-level attributes referenced by unit rules.
• IGS_PE_STD_TODO — The person/student to-do table, written by the RULTODO routine to raise actionable items for students or administrators.
• IGS_GE_S_LOG — The generic Student System log table, used to record processing events, warnings, and errors produced during bulk validation.

Usage Notes

IGS_EN_VAL_BULKRULE is not exposed as a form-level or standalone concurrent program entry point in the documented metadata. In practice, packages of this class are invoked from within the IGS enrollment batch and validation logic — typically from concurrent programs that process student unit attempts in bulk, and from the enrollment forms that need to confirm rule compliance before committing an attempt. Because it is unpublished and version-specific, customizations should never call the procedures directly; the supported integration approach is to drive the standard enrollment processes that in turn invoke this package.

Two operational characteristics should be noted. First, its worklist tables (IGS_PE_STD_TODO and IGS_GE_S_LOG) mean the package has side effects: running bulk validation can generate to-do entries and log rows, so re-running it without cleanup can produce duplicate notifications. Second, the absence of package-level dependents confirms it is a leaf utility, and its behavior is therefore governed entirely by the data it reads from the enrollment, calendar, and course tables listed above.