Search Results igf_aw_fn_rpkg_prty_u1

Overview

The IGF_AW_FN_RPKG_PRTY table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Institutional Grants and Financial Aid (IGF) module. This table is fundamental to the award packaging process, serving as a repository for defining the priority order in which different financial aid funds are to be applied to a student's award package. By establishing a fund priority sequence per award year, it ensures that institutional packaging rules are executed in a deterministic and consistent manner, directly impacting the final financial aid award calculation for students.

Key Information Stored

The table stores a concise set of columns that define the relationship between an award year, a specific fund, and its processing priority. The primary business columns are:

• CI_CAL_TYPE and CI_SEQUENCE_NUMBER: These columns together form a composite key that identifies the specific award year (Calendar Instance) for which the fund priority is defined.
• FUND_ID: A foreign key referencing the system fund type, identifying the specific financial aid fund (e.g., a particular loan, grant, or scholarship).
• FUND_ORDER_NUM: A numeric field that stores the priority sequence number for the associated fund within the specified award year. This is the column that dictates the order of application during packaging.

The table also includes standard Oracle EBS "Who" columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for auditing purposes. The unique indexes, IGF_AW_FN_RPKG_PRTY_PK and IGF_AW_FN_RPKG_PRTY_U1, enforce data integrity by preventing duplicate fund priorities for a given award year and calendar instance.

Common Use Cases and Queries

The primary use case is the configuration and review of fund packaging hierarchies. Administrators use this data to set up or modify the order in which funds are exhausted when building an award package—for instance, applying grants and scholarships before loans. Common reporting and validation queries involve joining to fund master tables. A typical query to list all fund priorities for an award year would be:

SELECT rpkg.ci_cal_type,
       rpkg.ci_sequence_number,
       rpkg.fund_order_num,
       rpkg.fund_id,
       fund.fund_code -- Example column from a fund master table
  FROM igf.igf_aw_fn_rpkg_prty rpkg,
       igf.igf_aw_fund_mst_all fund -- Hypothetical fund table
 WHERE rpkg.fund_id = fund.fund_id
   AND rpkg.ci_cal_type = '&Award_Year_Type'
   AND rpkg.ci_sequence_number = &Award_Year_Num
 ORDER BY rpkg.fund_order_num;

Troubleshooting packaging results often involves verifying the FUND_ORDER_NUM for specific funds to ensure business rules are correctly modeled in the system.

Related Objects

Based on the provided metadata, the IGF_AW_FN_RPKG_PRTY table is referenced by the APPS synonym IGF_AW_FN_RPKG_PRTY, which is the standard access point for all application code and reports within the EBS environment. While explicit foreign key relationships are not detailed in the excerpt, the FUND_ID column logically references a primary key in a fund master table (such as IGF_AW_FUND_MST or similar). Similarly, the CI_CAL_TYPE and CI_SEQUENCE_NUMBER columns would reference a calendar instance table to define the valid award year. The table's design, with its two unique indexes, indicates it is a central configuration table likely referenced by award packaging engine programs and setup forms within the IGF module.