Search Results p_person_number

Overview

IGS_EN_IVR_PUB is a public PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that supports the Interactive Voice Response (IVR) build for the Student System / Enterprise Enrollment (IGS) product family. Its package header header comment identifies that it was created by Nalin Kumar on 16-Jan-2003 as part of an IVR build effort associated with Bug# 2745985. A subsequent change by sarakshi on 13-Apr-2004 (Bug#3555871) altered the declaration of the call_number attribute from NUMBER(10) to NUMBER, reflecting a broadening of the numeric precision available for that column in the schedule and cart-related record structures.

The package exposes a set of enrollment-related operations intended to be invoked by an external telephony or self-service layer. Rather than being a self-contained business API, IGS_EN_IVR_PUB bridges the IVR channel with the IGS enrollment data model, allowing a caller entering a person identifier to be validated, evaluated against enrollment steps, presented with a schedule, and permitted to add or drop sections. The package is classified as PUB, indicating that it is part of the documented public interface and is referenced by at least one other package in the APPS schema.

Key Procedures and Functions

The package documents fourteen procedures and functions grouped around a cart-style enrollment model:

• VALIDATE_PERSON_DETAILS — Confirms that the identifying information supplied for a person is valid before further processing. This is the entry point most closely associated with the search term p_person_number, since the person number is the standard IGS person identifier used to locate a learner.
• EVALUATE_PERSON_STEPS — Determines which enrollment steps a given person is eligible or required to complete, supporting step-by-step guidance of the caller.
• VALIDATE_CAREER_PROGRAM — Checks that a career, program code, and version combination is valid for the person, using the career_rec_type structure.
• VALIDATE_TERM — Validates a term alternate code (term_rec_type) against the enrollment calendar.
• ADD_TO_CART, REMOVE_FROM_CART, LIST_SECTION_IN_CART, CLEAN_UP_CART — Manage a temporary cart of proposed enrollments, letting callers accumulate sections before committing.
• ENROLL_CART — Commits the contents of the cart, creating the underlying unit attempt records.
• LIST_SCHEDULE — Returns the student's current schedule via the schedule_rec_type, which includes unit code, unit class, teach alternate code, call number, grading schema, credit points, unit attempt status, uoo_id, and administrative priority (waitlist position).
• DROP_SECTION_BY_CALL_NUMBER and DROP_ALL_SECTION — Remove individual sections identified by call number, or all sections, from the schedule.
• WAITLIST — Places the caller on the waitlist for a section, using the administrative priority field returned in the schedule record.
• UPDATE_ENROLL_STATS — Maintains enrollment statistics, typically as a follow-up to successful enrollment or drop actions.

Tables Accessed

Via APPS synonyms, the package works with four documented tables: FND_NEW_MESSAGES, used to retrieve or surface messages for the IVR session; IGS_EN_METHOD_TYPE, which supplies the enrollment method context; IGS_EN_SU_ATTEMPT_ALL, the core unit attempt table that stores enrollment, drop, and waitlist outcomes; and IGS_PE_PERSON_TYPES, which is consulted during person validation to confirm the person's type is appropriate for the operation. These tables reflect the package's dual role: validating the caller (person types) and manipulating enrollment (unit attempts).

Usage Notes

IGS_EN_IVR_PUB is intended for invocation from IVR telephony middleware or external self-service applications rather than from the standard Enrollment forms. Because it is a PUB package with a stable, documented interface and is referenced by one other package, custom code and integration layers may call it directly. Practitioners searching for p_person_number should confirm the actual parameter names against the deployed package specification in the target environment, since the public ETRM metadata documents procedure names and record structures but not the individual parameter lists.