Results for “igf_aw_fn_rpkg_prty”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGF_AW_FN_RPKG_PRTY is a table in the IGF (Financial Aid) product module of Oracle E-Business Suite, owned by the IGF schema. It stores funding priority and packaging details used during the need analysis and award packaging process. The table captures the ordering of funds within an award package, allowing Financial Aid administrators to define which funds are applied first when distributing available aid to students.

The object is classified as VALID in the ETRM metadata and is documented in both EBS 12.1.1 and 12.2.2. It contains nine columns and carries two unique indexes that establish its relational identity. The heuristic Data Vault classification is standalone, meaning the mined foreign-key structure does not point to a clear parent hub or link. In Data Vault modeling terms, this would suggest treating the table as a self-contained entity rather than as a dependent satellite, though caution is warranted because the classification is heuristic and not authoritative.

Key Information Stored

The table is identified by a primary key, IGF_AW_FN_RPKG_PRTY_PK, defined as a composite of CI_CAL_TYPE, CI_SEQUENCE_NUMBER, and FUND_ORDER_NUM. These three columns define the granularity of each row. CI_CAL_TYPE identifies the calendar type associated with the financial aid cycle, CI_SEQUENCE_NUMBER identifies the specific calendar instance or sequence within that type, and FUND_ORDER_NUM records the ordinal position of a fund in the packaging sequence.

A second unique index, IGF_AW_FN_RPKG_PRTY_U1, is defined on CI_CAL_TYPE, CI_SEQUENCE_NUMBER, and FUND_ID. This constitutes the principal business-key candidate: it asserts that within any given calendar type and sequence, a specific fund may appear only once. FUND_ID is the identifier of the fund being given a packaging priority.

The remaining columns are standard EBS audit columns present on nearly every transactional table: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN. These record who created and last modified each priority assignment and when. The table contains no descriptive or amount-bearing columns in the documented schema; it functions purely as an ordering and association record between calendars and funds.

Common Use Cases and Queries

The primary use case is to determine the sequence in which funds are applied when packaging a student's award. Reporting on packaging rules typically joins this table to fund definitions using FUND_ID and filters by the active calendar type and sequence. A representative query pattern selects the fund order for a given packaging cycle:

• SELECT fund_id, fund_order_num FROM igf.igf_aw_fn_rpkg_prty WHERE ci_cal_type = :cal_type AND ci_sequence_number = :seq ORDER BY fund_order_num;
• Joining to fund master data on FUND_ID to retrieve fund codes and descriptions for a packaging rule report.
• Auditing when a particular fund's priority was last changed using LAST_UPDATED_BY and LAST_UPDATE_DATE.
• Validating uniqueness of fund assignments per calendar using the U1 index columns before loading new packaging rules.

Because the table is small and carries no foreign keys, queries are inexpensive and are usually part of a broader packaging-rule extraction rather than standalone extracts.

Related Objects

The metadata documents no formal foreign keys, so related objects are inferred from the business semantics of the columns rather than from enforced constraints. The most significant associations are:

• Fund definition tables joined on FUND_ID (the U1 business key).
• Calendar type and sequence reference tables joined on CI_CAL_TYPE and CI_SEQUENCE_NUMBER.
• Award packaging process objects that consume the FUND_ORDER_NUM sequence to determine disbursement priority.
• Need analysis and fund packaging procedures within the IGF module that read this table at packaging time.

Implementers should treat these relationships as logical rather than enforced, and confirm integration points against the specific 12.1.1 or 12.2.2 installation.