Search Results get_msg_name_mapping




Overview

IGS_AD_UPD_INITIALISE is an APPS-owned PL/SQL package within the Oracle E-Business Suite 12.1.1 / 12.2.2 footprint for the Student System (formerly Student Information Management) footprint, specifically the Admissions (IGS_AD) module. It is classified as an API type of OTHER, indicating that it is an internal helper package rather than a public, versioned API intended for direct third-party invocation. Its documented purpose is to support the initialisation and updating of applicant/admission records during admissions processing.

The package sits at a low dependency level in the admissions call stack. Its dependency chain shows it references only a small set of objects (notably IGS_AD_PS_APPL_INST via APPS and the SYS.STANDARD construct) yet it is referenced by a substantial number of higher-level packages and public APIs. This asymmetry confirms a design role as a shared initialisation utility invoked broadly across the admissions lifecycle, not as a functional entry point exposed to end users.

Key Procedures and Functions

  • ADMP_UPD_ACAIU_INIT — From its name, this routine performs the "update ACAIU init" step, where ACAIU denotes the Admissions Category Application Instance Unit structure. It initialises the relationship between the applicant instance and the associated unit/offering hierarchy during admissions processing.
  • PERFORM_PRE_ENROL — Executes the pre-enrolment validation or setup steps required before an application proceeds to the enrolment stage, typically after an offer is accepted.
  • GET_MSG_NAME_MAPPING — Returns the mapping between internal message codes and the message names used in the Oracle messages repository, enabling consistent error and warning reporting during admissions routines.
  • UPDATE_PER_STATS — Updates person statistic records (the PER_STATS structures) for applicants, keeping the person-level statistical/status information aligned with admissions outcomes.

The metadata lists five documented procedures/functions in total; the enumerated names above cover the substantive routines referenced in the ETRM record. Parameter signatures are not reproduced here because the documented metadata does not publish them.

Tables Accessed

The package operates exclusively through APPS synonyms. The documented table list includes: HZ_PERSON_PROFILES, IGS_AD_APPL_ALL, IGS_AD_PRCS_CAT_STEP_ALL, IGS_AD_PS_APPL_INST_ALL, IGS_AD_UNIT_OU_STAT, IGS_CA_INST_ALL, IGS_CA_INST_REL, IGS_CA_TYPE, IGS_EN_SU_ATTEMPT_ALL, and USER_OBJECTS.

  • IGS_AD_APPL_ALL and IGS_AD_PS_APPL_INST_ALL hold the core application and application-instance (person-specific) admissions records that the initialisation routines update.
  • IGS_AD_PRCS_CAT_STEP_ALL and IGS_AD_UNIT_OU_STAT describe processing category steps and unit/offering statuses, used to drive workflow state during initialisation.
  • IGS_CA_INST_ALL, IGS_CA_INST_REL, and IGS_CA_TYPE belong to the Calendar (IGS_CA) schema and supply the academic period/instance context against which admissions records are initialised.
  • IGS_EN_SU_ATTEMPT_ALL holds enrolment attempt data, relevant to the pre-enrolment routine.
  • HZ_PERSON_PROFILES provides the TCA person profile attributes updated by UPDATE_PER_STATS.
  • USER_OBJECTS is queried for metadata/dependency validation.

Usage Notes

IGS_AD_UPD_INITIALISE is normally invoked indirectly. It is referenced by ten higher-level packages, including IGS_ADMAPPLICATION_PUB (the public admissions application API), IGS_AD_CANCEL_RECONSIDER, IGS_AD_DEF_APPL_PKG, IGS_AD_GEN_012, IGS_AD_IMP_OFF_RESP_DATA, IGS_AD_PRC_TAC_OFFER, IGS_AD_PS_APPL_INST_PKG, IGS_AD_SS_GEN_001, IGS_AD_VAL_ACAI_FTR_OFFER, and IGS_PERSONSTATS_PUB. This reference set demonstrates use across admissions forms (via IGS_ADMAPPLICATION_PUB), concurrent/generation programs (IGS_AD_GEN_012, IGS_AD_SS_GEN_001), offer processing (IGS_AD_PRC_TAC_OFFER, IGS_AD_VAL_ACAI_FTR_OFFER), and person-statistics synchronisation (IGS_PERSONSTATS_PUB). Customisations should call the public wrappers rather than this package directly, since the API classification is OTHER and the package may be recompiled without notice between EBS point releases. When debugging admissions initialisation defects, the dependency list above provides the correct trace path to identify which of the ten caller packages triggered the failing routine.