Search Results igs_ad_perd_ad_cat




Overview
Explore in AI Chat

Overview

The table IGS_AD_PERD_AD_CAT is a core data object within the Oracle E-Business Suite Student System (IGS), specifically designed for managing admissions processes. As indicated by its description, it serves to define an admission period by establishing a relationship between an admission category and an admission calendar instance. This linkage is fundamental for structuring application cycles, deadlines, and associated processing rules within the institution's student lifecycle management. It is critical to note that the IGS product line is marked as "Obsolete" in the provided ETRM documentation. This status indicates that while the table may exist in legacy installations of versions 12.1.1 or 12.2.2, it is part of a system no longer under active development by Oracle, and its functionality may have been superseded or migrated in more recent application strategies.

Key Information Stored

The table's structure is centered on its composite primary key, which uniquely identifies each admission period definition. The key columns are ADM_CAL_TYPE (the calendar type, e.g., 'ADMISSION'), ADM_CI_SEQUENCE_NUMBER (the sequence identifier for a specific instance of that calendar), and ADMISSION_CAT (the code for the category of admission). The table also includes columns CI_START_DT and CI_END_DT, which are likely denormalized dates from the linked calendar instance (IGS_CA_INST_ALL) for performance or historical tracking purposes. These fields collectively enable the system to associate specific admission categories, such as "Undergraduate Freshman" or "Graduate International," with specific time-bound calendar instances, thereby creating a discrete operational period for that category.

Common Use Cases and Queries

This table is primarily queried in scenarios involving the setup and validation of admission timelines. Common operational and reporting use cases include generating lists of all active admission periods for a given term, validating application submissions against open periods, and configuring downstream processes like fee assessment or document tracking. A typical query would join IGS_AD_PERD_AD_CAT with related master tables to retrieve a comprehensible report. For example:

  • Listing all defined admission periods with their details:
    SELECT apac.ADM_CAL_TYPE, apac.ADM_CI_SEQUENCE_NUMBER, apac.ADMISSION_CAT, apac.CI_START_DT, apac.CI_END_DT FROM IGS_AD_PERD_AD_CAT apac WHERE SYSDATE BETWEEN apac.CI_START_DT AND apac.CI_END_DT;
  • Finding the specific calendar instance for an admission category:
    SELECT * FROM IGS_CA_INST_ALL ca WHERE ca.CAL_TYPE = :p_adm_cal_type AND ca.SEQUENCE_NUMBER = :p_adm_ci_sequence_num AND EXISTS (SELECT 1 FROM IGS_AD_PERD_AD_CAT apac WHERE apac.ADM_CAL_TYPE = ca.CAL_TYPE AND apac.ADM_CI_SEQUENCE_NUMBER = ca.SEQUENCE_NUMBER AND apac.ADMISSION_CAT = :p_admission_cat);

Related Objects

As defined by its foreign key relationships, IGS_AD_PERD_AD_CAT sits at the center of a small data model. It is a child table of IGS_AD_CAT_ALL (Admission Categories) and IGS_CA_INST_ALL (Calendar Instances), drawing its valid values from these master entities. Conversely, it acts as a parent table to at least two other entities: IGS_AD_PRD_AD_PRC_CA and IGS_AD_PECRS_OFOP_DT. These child tables likely store more granular processing rules or date exceptions that are specific to the admission period defined in IGS_AD_PERD_AD_CAT. Any data manipulation or reporting on admission periods must consider these relationships to maintain referential integrity and provide complete context.