Search Results create_unit_set_atmpt




Overview
Explore in AI Chat

Overview

IGS_EN_SUSA_LGCY_PUB is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified as a Public (PUB) API under the Student Systems (IGS) product family. Its purpose is to support the import of legacy Student Unit Set Attempt records into the Oracle Student System data model during system conversion and data migration activities. The package is explicitly documented as the Student Unit Set Attempt Import public API, designed for populating rows with data during a system conversion, and it is also leveraged by the Legacy Import Process for Enrollment and Records to transfer data from the staging interface table IGS_EN_LGY_SUSA_INT into the live application tables.

The package carries an active lifecycle status and is marked as compatible (S) within the ETRM repository. It is annotated under the business entity IGS_STUDENT_PROGRAM, reflecting that Student Unit Set Attempts represent a learner's enrolment attempts against defined unit sets within a program. The header comment indicates the source file IGSENA3S.pls at version 120.1, dated January 2006, and is flagged "noship," meaning it forms part of the shipped application codebase but is not intended for direct standalone distribution outside the supported API surface.

Key Procedures and Functions

The ETRM metadata documents a single public procedure for this package:

  • CREATE_UNIT_SET_ATMPT — Creates a Student Unit Set Attempt record. This is the primary entry point exposed by the package and corresponds directly to the user search term "create_unit_set_atmpt." The procedure accepts the legacy interface data — modeled through the package's susa_rec_type record structure, whose fields mirror the columns of IGS_EN_LGY_SUSA_INT (person number, program code, unit set code, unit set version number, selection date, student-confirmed indicator, end date, parent unit set code, primary set indicator, voluntary end indicator, authorised person number, authorised-on date, override title, requirements-complete indicator, requirements-complete date, completion source type, catalog calendar alternate code, and descriptive flexfield attributes) — and persists a corresponding row into the Student Unit Set Attempt table.

The record type declared in the package specification defines the interface between the caller and the procedure, ensuring that the full set of legacy attributes can be carried through the import. No additional public procedures or functions are documented for this package, reinforcing its narrow, conversion-focused scope.

Tables Accessed

The package interacts with the following objects, referenced through APPS synonyms:

  • IGS_EN_LGY_SUSA_INT — the legacy import interface/staging table for Student Unit Set Attempts. It supplies the source attribute set and underpins the susa_rec_type record definition.
  • IGS_AS_SU_SETATMPT — the destination Student Unit Set Attempt base table into which converted records are written.
  • IGS_AS_SU_SETATMPT_SEQ_NUM_S — the sequence used to generate the internal sequence number for newly created attempt rows.
  • DUAL — accessed for standard PL/SQL operations such as sequence value retrieval and simple expression evaluation.

Usage Notes

CREATE_UNIT_SET_ATMPT is intended to be invoked within the Legacy Import Process for Enrollment and Records, or directly by custom conversion code during a data migration project. Typical invocation paths include the delivered concurrent program that processes rows staged in IGS_EN_LGY_SUSA_INT, and bespoke PL/SQL scripts written to transform and load legacy student records. Because the package is classified as a public API, it forms a supported integration point; nevertheless, callers should ensure the interface table is populated with valid person numbers, program codes, and unit set codes before execution, and should anticipate that the procedure relies on the sequence IGS_AS_SU_SETATMPT_SEQ_NUM_S to assign keys. The metadata notes that the package is referenced by one other package, indicating that at least one dependent component consumes this API, so changes to its behaviour should be assessed against that dependency before upgrading between EBS 12.1.1 and 12.2.2.