Search Results igs_ge_gen_001




Overview
Explore in AI Chat

Overview

IGS_GE_GEN_001 is a general-purpose utility package body in the APPS schema belonging to the Oracle E-Business Suite Higher Education / Student Systems product family (the IGS% namespace, historically delivered as Oracle Student System and later integrated into EBS 12.1.1 and 12.2.2). It serves as a low-level "common services" library used across the student information model, providing reusable PL/SQL logic for date arithmetic, address resolution, audit stamping, log and note maintenance, and dynamic metadata inspection. Its documented API classification is OTHER, indicating it is an internal implementation package rather than a public, business-facing API. The package holds STATUS VALID in the ETRM repository and exposes eleven documented program units. It is a heavy dependency consumer, referencing HZ, IGS_AD, IGS_CA, IGS_GE, IGS_OR, and IGS_PE objects, and is referenced by twelve other packages — confirming its role as foundational infrastructure rather than an entry-point process.

Key Procedures and Functions

The eleven documented program units fall into functional clusters:

  • GENP_CHK_COL_UPPER — validates or converts a column value to upper case, a normalization helper used for consistent key comparison.
  • GENP_CLC_DT_DIFF — calculates the difference between two dates, supporting scheduling, eligibility, and calendar logic throughout the student modules.
  • GENP_CLC_WEEK_END_DT — derives the week-ending date for a given date, used by calendar and attendance processing.
  • GENP_DEL_LOG and GENP_DEL_NOTE — delete or purge records from the logging and note subsystems, maintaining housekeeping of the IGS_GE_S_LOG family and IGS_GE_NOTE.
  • GENP_GET_ADDR — retrieves a formatted address, resolving the party/location/venue relationships across HZ and IGS address structures.
  • GENP_GET_APPL_OWNER — returns the application owner, used for schema qualification and dynamic SQL construction.
  • GENP_GET_AUDIT — populates standard WHO audit columns (created/updated by, dates), typically via FND_GLOBAL.
  • GENP_GET_CMP_CUTOFF — returns the comparison cut-off value, generally a date or effective boundary used in effective-dated queries.
  • ADM_GET_NAME — resolves and returns an admissions or person name.
  • ADM_GET_UNIT_TITLE — returns the title of an organizational unit from IGS_OR_UNIT.

Tables Accessed

The package reads and writes the following documented objects via APPS synonyms. Party and location data are sourced from HZ_PARTIES and HZ_LOCATIONS, with address detail assembled from IGS_OR_ADDR, IGS_PE_PERSON_ADDR_V, IGS_AD_LOCVENUE_ADDR, and IGS_PE_LOCVENUE_USE, supporting the GENP_GET_ADDR logic. Notes are handled through IGS_GE_NOTE. Logging uses IGS_GE_S_LOG and IGS_GE_S_LOG_ENTRY. Calendar and institution context come from IGS_GE_S_GEN_CAL_CON, IGS_CA_INST, IGS_OR_INSTITUTION, and IGS_OR_UNIT. Helper views IGS_AD_UNIT_SETS_V, IGS_PE_PERSON_BASE_V, and IGS_CA_DA_INST_V supply flattened reference data. Dynamic SQL and metadata inspection rely on DBMS_SQL together with USER_COL_COMMENTS, USER_CONSTRAINTS, and USER_OBJECTS, consistent with the GENP_GET_APPL_OWNER and column-check routines.

Usage Notes

IGS_GE_GEN_001 is not invoked directly by end users. It is called from Forms-based student maintenance screens, concurrent programs, and — most importantly — from the twelve dependent packages that consume its utility routines, including sibling general packages IGS_GE_GEN_002/003, IGS_GE_NOTE_PKG, IGS_GE_S_LOG_PKG, and IGS_GE_S_LOG_ENTRY_PKG. Typical invocation contexts include address display in person and venue forms, audit stamping during DML in student and admissions transactions, week-ending and date-difference calculations for calendar and attendance processing, and note/log purging during cleanup or archival jobs. Error handling is routed through APP_EXCEPTION and FND_MESSAGE, so failures surface as standard EBS messages. Because the package references USER_* data dictionary views and DBMS_SQL, customizations should exercise care in any environment where the runtime schema differs from APPS. The package is not referenced by any database object, so it can be recompiled independently; however, invalidating it will cascade recompilation to its twelve dependent packages.