Search Results igs_ad_ss_appl_pgs




Overview

The IGS_AD_SS_APPL_PGS table is a core data object within the Oracle E-Business Suite (EBS) Student System (IGS) module, specifically in the context of Admissions. Its primary function is to manage the configuration of the Self Service Applicant Portal by storing the association between specific Admission Application Types and the Self Service web pages (Page Names) that are presented to applicants during the online application process. This table acts as a critical junction, enabling the system to dynamically determine which sequence of pages and data collection forms an applicant must complete based on the type of application they are submitting, such as undergraduate, graduate, or transfer applications.

Key Information Stored

The table's structure is designed to enforce and maintain the relationship between an application type and its associated portal pages. The two key columns that constitute the table's primary key are ADMISSION_APPLICATION_TYPE and PAGE_NAME. The ADMISSION_APPLICATION_TYPE column stores a code that identifies a specific category of admission application, as defined in the related IGS_AD_SS_APPL_TYP table. The PAGE_NAME column holds identifiers for the specific Self Service pages or components that are sequentially attached to that application type. Together, these columns define the permissible page flow for an application type. Additional descriptive or control columns may exist but are not detailed in the provided metadata; the core business logic is encapsulated in this fundamental relationship.

Common Use Cases and Queries

This table is primarily accessed for configuration and inquiry purposes within the Admissions functional setup. A common administrative task is to query all pages assigned to a particular application type to verify or audit the Self Service application flow. For example, a functional consultant might run a query to list the page sequence for the 'UG_FRESHMAN' application type. Another typical use case involves troubleshooting, where support personnel might need to identify which application type is using a specific page that is experiencing an issue. Sample SQL to retrieve the page mapping would be: SELECT admission_application_type, page_name FROM igs.igs_ad_ss_appl_pgs WHERE admission_application_type = '&APPL_TYPE' ORDER BY <sequence_column_if_present>;. This data is foundational for generating reports on Self Service application structure and ensuring consistency across different admission pathways.

Related Objects

The IGS_AD_SS_APPL_PGS table sits at the center of a small but important hierarchy within the Self Service Admissions configuration. It has documented foreign key relationships with two other tables:

  • IGS_AD_SS_APPL_TYP: This is the parent table for the ADMISSION_APPLICATION_TYPE column. The foreign key (IGS_AD_SS_APPL_PGS.ADMISSION_APPLICATION_TYPE references IGS_AD_SS_APPL_TYP) ensures that a page can only be attached to a valid, predefined application type.
  • IGS_AD_SS_APPL_COMPS: This table is a child of IGS_AD_SS_APPL_PGS. The foreign key (IGS_AD_SS_APPL_COMPS.PAGE_NAME, IGS_AD_SS_APPL_COMPS.ADMISSION_APPLICATION_TYPE references IGS_AD_SS_APPL_PGS) indicates that the specific components or items on a given Self Service page are defined at a more granular level, linked back to the page-application type combination defined in IGS_AD_SS_APPL_PGS.

This structure creates a configuration chain: Application Type -> Page -> Page Components, which the Self Service portal runtime uses to render the correct applicant experience.