Results for “igs_uc_cycle_not_found”

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

Overview

The APPS.IGS_UC_EXPORT_UCAS_PKG package body is a component of the Oracle E-Business Suite Student Systems (formerly Oracle Student System) integration layer that supports data exchange between the institution and UCAS (the Universities and Colleges Admissions Service). Its principal responsibility is to export admissions and applicant data held in EBS tables into the format and control structures required by UCAS, including the derivation of the correct UCAS entry year and cycle from the institution's configured control records.

The package is classified as an OTHER API in ETRM. It is a standalone, self-contained body and is referenced by no other packages, which indicates that it is invoked directly rather than being consumed as a shared library. The header comment shows a long maintenance history spanning the R12 transition, including the modification that disabled the OSS mandate (Bug 4950285) and changes made for UCAS support in 2006. Notably, several legacy export routines (such as export_inst_conts, export_crse_dets and export_offer_abbrev) were removed because UCAS no longer supports those views as updateable.

Key Procedures and Functions

The documented package exposes a single public procedure:

• EXPORT_DATA — The main extraction routine. It drives the export of UCAS-bound data and accepts control parameters that select the contact, program details, keywords, abbreviations, and the transaction sets for UCAS, GTTR and NMAS respectively. The ETRM metadata does not publish the formal parameter list, so the signature is deliberately not restated here. Its internal cursors reveal its intent: cur_cycle raises the configured UCAS cycle from the defaults table, and cur_control resolves the entry year from the UCAS control table for the active system code and configured cycle. The "cycle not found" search term maps directly to the failure mode where igs_uc_defaults returns no usable configured cycle, leaving downstream control lookups without a value.

Tables Accessed

The package reads the following tables through APPS synonyms:

• IGS_UC_DEFAULTS — Provides the current_cycle and configured_cycle values that anchor every subsequent lookup. This is the table implicated in the igs_uc_cycle_not_found condition.
• IGS_UC_UCAS_CONTROL — Supplies the entry year for a given system code and UCAS cycle; the cursor here joins on system_code and the configured cycle.
• IGS_UC_CYC_DEFAULTS — Referenced for cycle-level default configuration used during export processing.

Usage Notes

The routine is typically invoked from a concurrent program or a UCAS export form that collects the toggle parameters (program details, keywords, abbreviations, and transaction types) before submission. Because the package is not called by any other PL/SQL unit, support diagnostics should focus on the control data rather than on callers. When the igs_uc_cycle_not_found error is reported, the standard remediation is to verify that IGS_UC_DEFAULTS contains a non-null configured_cycle and that a matching row exists in IGS_UC_UCAS_CONTROL for the operative system code. The output parameters Errbuf and Retcode carry the concurrent program's completion status back to the request log.