Search Results igs_ad_app_req




Overview
Explore in AI Chat

Overview

The IGS_AD_APP_REQ table is a core data object within the Oracle E-Business Suite (EBS) Student System (IGS) module. It serves as the central repository for storing and managing the specific requirements associated with a prospective student's admission application. Its primary role is to track the various conditions, fees, and supporting documentation that an applicant must fulfill as part of the admissions process. By linking an applicant's core application data to their specific obligations, this table enables institutions to systematically manage application completeness, assess applicant readiness, and process associated financial transactions. It is a critical component for ensuring the integrity and auditability of the student admissions lifecycle in EBS versions 12.1.1 and 12.2.2.

Key Information Stored

The table stores a detailed record of each application requirement. Key columns include the unique identifier APP_REQ_ID, which serves as the primary key for the record. The table is fundamentally linked to the applicant's master application via the composite foreign key columns PERSON_ID and ADMISSION_APPL_NUMBER. A significant portion of the data pertains to financial obligations, captured through columns such as APPLICANT_FEE_TYPE and APPLICANT_FEE_STATUS, which classify the fee and its current state (e.g., paid, waived, pending). Financial accounting integration is facilitated by the REV_ACCOUNT_CD and CASH_ACCOUNT_CD columns, which link to the General Ledger. Other typical data points would include requirement due dates, completion dates, and descriptive notes regarding the specific condition or document required from the applicant.

Common Use Cases and Queries

This table is central to several operational and reporting functions. Common use cases include generating lists of incomplete application items for specific applicants or admission batches, tracking fee payment statuses, and auditing the application review process. A typical query might involve joining to the main application table to retrieve a summary of all pending requirements for an applicant. For example:

  • Pending Requirements Report: SELECT aar.* FROM igs_ad_app_req aar, igs_ad_appl_all app WHERE aar.person_id = app.person_id AND aar.admission_appl_number = app.admission_appl_number AND aar.applicant_fee_status = 'PENDING' AND app.admission_appl_number = :app_number;
  • Application Completeness Check: Queries often aggregate counts of requirements by status (e.g., COMPLETE, WAIVED, PENDING) against the total required for a given application to determine overall readiness for evaluation.
  • Financial Reconciliation: The table is used in conjunction with the Financials module to reconcile application fee revenue by joining on the REV_ACCOUNT_CD to the IGS_FI_ACC_ALL table.

Related Objects

The IGS_AD_APP_REQ table maintains defined relationships with several other key tables in the Student System, primarily through foreign key constraints. These relationships are essential for maintaining referential integrity and constructing accurate joins in reports and interfaces.

  • IGS_AD_APPL_ALL: The primary parent table. The relationship is defined on the composite key (PERSON_ID, ADMISSION_APPL_NUMBER). This links each requirement record to its corresponding master application.
  • IGS_AD_CODE_CLASSES: Likely used as a lookup source for valid status codes. A foreign key exists on the APPLICANT_FEE_STATUS column to ensure data validity for the fee condition.
  • IGS_FI_ACC_ALL: The table is linked twice for financial accounting purposes: once via the REV_ACCOUNT_CD column and again via the CASH_ACCOUNT_CD column. This integrates application fee data with the General Ledger chart of accounts.