Search Results max_gift_perct_fact

Overview

The view IGF_AW_TARGET_GRP belongs to the Oracle Financial Aid (IGF) product family — specifically the Award Disbursement / Award Management area of the legacy Student System module. The ETRM metadata classifies the product as Obsolete and notes that the object is not implemented in this database, meaning no live deployment of the view exists in the reference environment. Nonetheless, the object survives in the data dictionary and ETRM catalog as a documented artifact of the pre-12.x Financial Aid schema that was carried forward into the 12.1.1 and 12.2.2 releases for backward compatibility.

The view exposes "Target Group" (TGRP) definitions — configuration records that declare the maximum allowable award amounts and percentages an aid applicant may receive across each aid category: grants, loans, work study, supplemental educational opportunity help (SHELP), gap, gift aid, and scholarships. In reporting and integration terms, IGF_AW_TARGET_GRP acts as an org-striped security view over the multi-organization table IGF_AW_TARGET_GRP_ALL, filtering rows by the ORG_ID captured in the session's CLIENT_INFO. This is the classic "ORG_ID = user's operating unit" pattern used throughout EBS self-service and OA Framework (IGF) screens.

Underlying Base Objects

ETRM documents no explicit referenced base objects, but the view text unambiguously reads from a single underlying table:

• IGF_AW_TARGET_GRP_ALL — the "all orgs" base table holding one row per target group definition per operating unit.

The name suffix _ALL indicates a public, unrestricted table; IGF_AW_TARGET_GRP is the corresponding secured (reporting) view that applies operating-unit security. The WHERE clause uses the legacy USERENV('CLIENT_INFO') mechanism, decoding the first ten characters of the client info string into a numeric ORG_ID and matching it against the table row, defaulting to -99 (no match) when no value is set. This confines visibility to the current operating unit.

Key Columns

The view projects nearly every column of the base table, including the following functional groups:

• Identity and control: TGRP_ID (PK surrogate), GROUP_CD, DESCRIPTION, ACTIVE, ORG_ID, ROWID.
• Calendar/sequencing: CAL_TYPE, SEQUENCE_NUMBER, ADPLANS_ID (award plan reference).
• Award ceilings by category — each category supplies a fixed dollar amount, a percentage, and a percentage factor:
  • MAX_GRANT_AMT, MAX_GRANT_PERCT, MAX_GRANT_PERCT_FACT
  • MAX_LOAN_AMT, MAX_LOAN_PERCT, MAX_LOAN_PERCT_FACT
  • MAX_WORK_AMT, MAX_WORK_PERCT, MAX_WORK_PERCT_FACT
  • MAX_SHELP_AMT, MAX_SHELP_PERCT, MAX_SHELP_PERCT_FACT
  • MAX_GAP_AMT, MAX_GAP_PERCT, MAX_GAP_PERCT_FACT
  • MAX_GIFT_AMT, MAX_GIFT_PERCT, MAX_GIFT_PERCT_FACT
  • MAX_SCHLRSHP_AMT, MAX_SCHLRSHP_PERCT, MAX_SCHLRSHP_PERCT_FACT
• Flags and packaging: USE_FIXED_COSTS, MAX_AID_PKG.
• Who-columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Note that the view itself defines four additional columns — ROW_ID, RULE_ORDER, S_RULE_CALL_CD, and RUL_SEQUENCE_NUMBER — though only ROW_ID maps to the source ROWID; the remaining three are emitted as NULL placeholders in the view text.

Common Use Cases and Queries

Two scenarios dominate. First, validating award limits for a student's package: reporting teams join the target group to the applicant's award records to confirm no category exceeds its ceiling.

SELECT group_cd, description, active,
       max_grant_amt, max_grant_perct,
       max_loan_amt,  max_loan_perct
FROM   igf_aw_target_grp
WHERE  active = 'Y'
ORDER  BY sequence_number;

Second, configuration auditing across operating units — though ORG_ID security restricts the reporting view, DBAs typically query the base table IGF_AW_TARGET_GRP_ALL for cross-org comparisons:

SELECT org_id, group_cd, cal_type,
       use_fixed_costs, max_aid_pkg
FROM   igf_aw_target_grp_all
ORDER  BY org_id, sequence_number;

Because the object is obsolete and unimplemented in the reference database, integrators should confirm its presence in their specific instance before relying on it, and should migrate logic to the current Financial Aid award-management APIs where available.