Search Results igs_ss_ad_sec_stat_u1

Overview

The IGS_SS_AD_SEC_STAT table is a core data object within the Oracle E-Business Suite (EBS) Student System (SS), specifically under the IGS (iGrants) schema in releases 12.1.1 and 12.2.2. It functions as a checklist or tracking mechanism for the completion status of specific sections within an admissions application process. The table's primary role is to maintain a granular, per-section status record for a given applicant and application, enabling the system to monitor which parts of a complex application form or workflow have been completed. This supports conditional logic, progress dashboards, and validation rules within the admissions module.

Key Information Stored

The table stores a composite record keyed by application, person, and section, along with the corresponding status and standard audit columns. The critical columns are:

• SS_ADM_APPL_ID (NUMBER): The unique identifier for the admissions application, linking to the main application header.
• PERSON_ID (NUMBER): The identifier for the applicant, linking to the person master (e.g., IGS_PE_PERSON).
• SECTION (VARCHAR2): A code identifying a specific section or region of the admissions application (e.g., 'PERSONAL_DETAILS', 'ACADEMIC_HISTORY').
• COMPLETION_STATUS (VARCHAR2): The status of the specified section for this application (e.g., 'COMPLETE', 'INCOMPLETE', 'IN_PROGRESS').
• Standard WHO Columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN): Audit trail recording the user and timestamp of record creation and modification.

The table's primary key constraint, IGS_SS_AD_SEC_STAT_PK, enforces uniqueness on the combination of SS_ADM_APPL_ID, PERSON_ID, and SECTION.

Common Use Cases and Queries

A primary use case is generating an application completeness report to identify applicants with pending sections. For example, an admissions officer may query for all incomplete sections for a specific application number. The user's search for "ss_adm_appl_id" indicates a common need to filter or join data using this key identifier.

Sample Query 1: Check Status for a Specific Application
SELECT SECTION, COMPLETION_STATUS
FROM IGS.IGS_SS_AD_SEC_STAT
WHERE SS_ADM_APPL_ID = :APPL_ID AND PERSON_ID = :PERSON_ID
ORDER BY SECTION;

Sample Query 2: Find Applications with Any Incomplete Sections
SELECT DISTINCT SS_ADM_APPL_ID, PERSON_ID
FROM IGS.IGS_SS_AD_SEC_STAT
WHERE COMPLETION_STATUS != 'COMPLETE';

Sample Query 3: Data Integrity Check (Count of Sections per Application)
SELECT SS_ADM_APPL_ID, COUNT(*) AS SECTION_COUNT
FROM IGS.IGS_SS_AD_SEC_STAT
GROUP BY SS_ADM_APPL_ID;

Related Objects

Based on the provided metadata, the table's relationships are primarily defined by its primary key columns. It is logically a child table to the main admissions application header table (likely named IGS_SS_ADM_APPL or similar) via the SS_ADM_APPL_ID column. Similarly, it references a core person table via PERSON_ID. The unique index IGS_SS_AD_SEC_STAT_U1 on (SS_ADM_APPL_ID, PERSON_ID, SECTION) supports the primary key and enforces data integrity. The dependency information notes that an object named IGS_SS_AD_SEC_STAT under the APPS synonym references this table, indicating it is accessed via a public synonym for use within the application tier. There are no foreign key constraints documented in the provided excerpt, implying relationships are enforced at the application level.