Results for “process_ivstarg”

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

Overview

IGS_UC_PROC_APPLICATION_DATA is an Oracle E-Business Suite PL/SQL package body owned by APPS and classified as an OTHER API within the Student System (IGS) product family. Its principal business function is to orchestrate the inbound processing of UCAS (Universities and Colleges Admissions Service) application data into the Oracle EBS student information model. UCAS is the United Kingdom's centralised admissions service, and institutions running the IGS UCAS integration rely on this package to translate externally supplied applicant records into native interface and person structures.

The package is invoked from the main UCAS processing routine Process_ucas_data, and it performs general setup validations before processing the application data views. The header comment confirms provenance: originally created by rgangara on 12-JUNE-2003, with subsequent modification by jchakrab on 27-JUL-04 to accommodate UCFD308, the 2005 UCAS regulatory changes. The version string (120.8, dated 2006/09/07) indicates a mature, stabilised object maintained under the IGS UCAS product line.

A notable design characteristic is the use of package-level global variables — g_success_rec_cnt, g_error_rec_cnt, g_error_code, g_crnt_institute, and g_config_cycle — which persist state across the processing procedures and allow aggregate success and error counts to be accumulated during a run. The g_config_cycle variable was deliberately made global to support the UCAS 2005 changes.

Key Procedures and Functions

The package exposes 18 documented procedures. APPL_DATA_SETUP is the entry-point validation routine. It queries IGS_UC_DEFAULTS to retrieve the current institution code and the maximum configured cycle value, and raises the messages IGS_UC_CURR_INST_NOT_SET and IGS_UC_CYCLE_NOT_FOUND when either is absent, returning retcode 2 to signal failure.

The remaining procedures follow a consistent naming convention that mirrors the UCAS record types received in the inbound feed:

• PROCESS_IVSTARN, PROCESS_IVSTARK, PROCESS_IVSTARC, PROCESS_IVSTARG, PROCESS_IVSTART, PROCESS_IVSTARA — process the core applicant and application record variants.
• PROCESS_IVSTARX, PROCESS_IVSTARH, PROCESS_IVSTARZ1, PROCESS_IVSTARZ2, PROCESS_IVSTARW — process auxiliary and specialised UCAS record types.
• PROCESS_IVQUALIFICATION — processes applicant qualification records.
• PROCESS_IVSTATEMENT — processes personal statement data.
• PROCESS_IVREFERENCE — processes referee and reference information.
• PROCESS_IVOFFER — processes offer records issued against applications.
• PROCESS_IVFORMQUALS — processes formatted qualification data.

Each procedure writes to the IGS admission interface tables and updates the corresponding UCAS staging tables, tracking outcomes through the global counters.

Tables Accessed

The package reads and writes a broad set of APPS synonyms. Core UCAS staging tables include IGS_UC_APPLICANTS, IGS_UC_APP_ADDRESES, IGS_UC_APP_CHOICES, IGS_UC_APP_CLEARING, and IGS_UC_APP_CLR_RND, which hold raw applicant, address, choice, and clearing-round data. Configuration is read from IGS_UC_DEFAULTS (the institution and cycle), with reference lookups drawn from IGS_UC_ISTARK_INTS, IGS_HE_CODE_MAP_VAL, IGS_PE_ALT_PERS_ID, IGS_PE_SRC_TYPES_ALL, and FND_LOOKUP_VALUES.

Output is directed into the admission interface layer: IGS_AD_INTERFACE_ALL, IGS_AD_INTERFACE_S, IGS_AD_INTERFACE_CTL, IGS_AD_INTERFACE_BATCH_ID_S, IGS_AD_API_INT_S, and IGS_AD_IMP_BATCH_DET. These tables stage the transformed data for subsequent validation and import into person and application records.

Usage Notes

This package is not intended for direct invocation by end users. It is called programmatically by the UCAS data-processing concurrent program chain, whose controlling routine is Process_ucas_data. The APPL_DATA_SETUP procedure must succeed before any of the PROCESS_IV* routines execute, since the current institution code and configured cycle are prerequisites for correct record interpretation. The errbuf and retcode OUT parameters conform to the standard Oracle EBS concurrent program interface, allowing the calling program to report failures through the concurrent manager log. Only one other package references this object, confirming its position as a tightly scoped internal component of the IGS UCAS integration rather than a general-purpose API.