Search Results process_ivstara

Overview

IGS_UC_PROC_APPLICATION_DATA is an APPS-owned PL/SQL package within the Oracle E-Business Suite student systems product family, specifically the UK UCAS (Universities and Colleges Admissions Service) integration component of the IGS (Student System) schema. The package resides in the APPS schema and holds a VALID status, confirming it is a deployed and compiled database object. Its name and structure indicate it serves as a processing engine for inbound application data received from the UCAS clearing and admissions channels, transforming and staging that data for loading into the Oracle Student System application tables.

The package is part of the broader IGS_UC family of objects that manage the interface between external admissions sources and the local student records. It is referenced by IGS_UC_PROC_UCAS_DATA, which acts as a higher-level driver, and is itself self-referential through the dependency listing. Only a small dependency footprint is recorded, with a direct reference to the SYS.STANDARD package, indicating standard PL/SQL runtime behaviour rather than reliance on a large set of external application APIs.

Key Procedures and Functions

The package exposes eighteen documented procedures and functions, most of which share the PROCESS_IV prefix, indicating an "*IV" (inbound processing) naming convention. These routines isolate handling of distinct UCAS record categories:

• PROCESS_IVSTAR* series — A family of procedures keyed by trailing letters and identifiers: PROCESS_IVSTARA, PROCESS_IVSTARC, PROCESS_IVSTARG, PROCESS_IVSTARH, PROCESS_IVSTARK, PROCESS_IVSTARPQR, PROCESS_IVSTART, PROCESS_IVSTARW, PROCESS_IVSTARX, PROCESS_IVSTARZ1, and PROCESS_IVSTARZ2. These individual routines parse and stage specific UCAS "STAR"-type records, using suffix letters to distinguish record subtypes or transaction codes received in the inbound feed.
• PROCESS_IVQUALIFICATION — Processes applicant qualification records, typically mapping external qualification evidence into the local interface structures.
• PROCESS_IVSTATEMENT — Handles applicant personal statement data included in the UCAS transmission.
• PROCESS_IVREFERENCE — Processes referee or reference records supplied by applicants.
• PROCESS_IVOFFER — Processes offer information returned from institutions through the UCAS exchange.
• PROCESS_IVFORMQUALS — Handles "form" qualification entries, distinguishing them from standard qualification records.
• APPL_DATA_SETUP — A setup routine that initialises control and configuration data required before application record processing begins, drawing on control tables and lookup values.

No parameter lists are documented in the available metadata; therefore the precise invocation signatures should be confirmed against the deployed package specification. The procedures collectively perform validation, code mapping and staging of incoming application data.

Tables Accessed

The package references application tables through APPS synonyms, grouped into three functional categories:

• Interface and staging tables — IGS_AD_INTERFACE_ALL, IGS_AD_INTERFACE_CTL, IGS_AD_IMP_BATCH_DET, IGS_AD_API_INT_S, IGS_AD_INTERFACE_S, IGS_AD_INTERFACE_BATCH_ID_S. These are the core inbound data repositories where processed UCAS records are written and controlled, including batch identification and interface control records.
• UCAS-specific tables — IGS_UC_APPLICANTS, IGS_UC_APP_ADDRESES, IGS_UC_APP_CHOICES, IGS_UC_APP_CLEARING, and IGS_UC_APP_CLR_RND. These store applicant biographical data, addresses, course choices, and clearing round details, forming the source of the inbound application data.
• Reference and mapping tables — FND_LOOKUP_VALUES, IGS_HE_CODE_MAP_VAL, IGS_PE_ALT_PERS_ID, IGS_PE_SRC_TYPES_ALL. These support code translation (mapping external UCAS codes to internal values), alternate person identification, and source-type configuration.

Usage Notes

IGS_UC_PROC_APPLICATION_DATA is not an end-user API; it is an internal processing package invoked by the higher-level package IGS_UC_PROC_UCAS_DATA during the UCAS data load cycle. Typical invocation occurs through concurrent programs that import and process UCAS transmissions, most commonly in scheduled admissions batch runs. The APPL_DATA_SETUP routine is expected to be called first to establish control and setup context before the individual PROCESS_IV routines execute against staged records.

Because the dependency metadata records only one referencing package, customisations should avoid calling these routines directly unless the calling program also replicates the setup and control context expected by the driver. All behaviour is identical between Oracle EBS 12.1.1 and 12.2.2, as the IGS schema and its UCAS integration objects are shared across both releases. Developers investigating errors from this package should begin with the IGS_AD_INTERFACE_CTL and IGS_AD_IMP_BATCH_DET records to correlate failures with specific inbound batches.