Search Results igf_ap_sap_types_pk

Overview

The IGF_AP_SAP_TYPES table is a reference table within the Oracle E-Business Suite (EBS) Financial Aid (IGF) module. Its primary function is to serve as a master repository for defining and storing the different types of Satisfactory Academic Progress (SAP) standards. SAP is a critical regulatory requirement for federal student financial aid programs in the United States, and institutions must define specific types of progress standards (e.g., qualitative, quantitative, maximum timeframe) against which student performance is measured. This table provides the foundational lookup data that categorizes these standards, enabling the system to consistently apply and track academic progress rules across the financial aid lifecycle. The metadata indicates it is a key component for configuring and managing SAP policies within the application.

Key Information Stored

Based on the provided ETRM documentation, the table's structure centers on a primary key that uniquely identifies each SAP type. The most critical column is SAP_TYPE, which serves as the table's primary key (IGF_AP_SAP_TYPES_PK). This column stores the unique code or identifier for a specific academic progress type. Another documented column is OUTCOME_NAME, which is referenced by a foreign key relationship. This column likely stores a descriptive name or label for the outcome associated with a particular SAP type, such as "Warning," "Termination," or "Good Standing." While other descriptive columns (e.g., DESCRIPTION, ENABLED_FLAG) are common in such reference tables, the confirmed core data elements from the metadata are the SAP_TYPE code and its related OUTCOME_NAME.

Common Use Cases and Queries

The primary use case for IGF_AP_SAP_TYPES is to provide a validated list of SAP types for configuration and transactional processing. Administrators use this data when setting up SAP policies and rules. The table is frequently queried in joins to retrieve meaningful descriptions for SAP type codes stored in transactional tables. Common reporting scenarios include listing all configured SAP standards or analyzing fund eligibility rules tied to specific progress types. A fundamental query pattern involves selecting all active types or joining to related transactional data:

• Basic Lookup: SELECT sap_type, outcome_name FROM igf_ap_sap_types ORDER BY sap_type;
• Join with Fund Master: SELECT fm.fund_code, st.outcome_name FROM igf_aw_fund_mast_all fm JOIN igf_ap_sap_types st ON fm.sap_type = st.sap_type; This query links financial aid funds to their associated SAP type descriptions.

Related Objects

The ETRM metadata explicitly defines the table's integration within the Financial Aid data model through its key relationships. The primary key (SAP_TYPE) is referenced by at least one other critical table, establishing its role as a parent lookup table.

• Primary Key: IGF_AP_SAP_TYPES_PK on the column SAP_TYPE.
• Referenced by (Child Table): The IGF_AW_FUND_MAST_ALL table, which stores master information for financial aid funds, contains a foreign key column named SAP_TYPE. This links each fund to a specific academic progress type defined in IGF_AP_SAP_TYPES, likely controlling fund eligibility based on a student's SAP status.
• Internal Foreign Key: The documentation notes a foreign key where IGF_AP_SAP_TYPES.OUTCOME_NAME references another column (indicated as "%"). This suggests a potential hierarchical or dependent relationship within the table itself or to another undocumented object, which may be used to structure different levels or categories of SAP outcomes.