Results for “igf_aw_award”

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

Overview

IGF_AW_AWARD is a reporting and inquiry view within the Oracle E-Business Suite IGF — Financial Aid module. It presents award-level records maintained by the Financial Aid award engine, exposing the amounts offered, accepted, and paid against each student award, together with packaging, batch, and workflow status attributes. The view is an org-stripped, security-filtered presentation of the underlying award entity: rather than querying the full multi-org table directly, callers read IGF_AW_AWARD and rely on the view's embedded ORG_ID predicate to return only the awards visible to the current operating unit context.

In Oracle EBS 12.1.1 and 12.2.2 the object is documented as belonging to the IGF — Financial Aid (Obsolete) product family. ETRM explicitly records the implementation state as "Not implemented in this database" and documents no owning schema or referenced base objects. This is significant: the view text exists in the shipped Financial Aid code set, but the instance against which the documentation was generated does not contain the object. Any integration or report referencing IGF_AW_AWARD must therefore be preceded by a existence check in the target environment.

Underlying Base Objects

The view is defined over a single base object, IGF_AW_AWARD_ALL, aliased as AWD in the view text. The _ALL suffix confirms that the base table is partitioned by operating unit and carries ORG_ID; IGF_AW_AWARD is the corresponding secured view that narrows the result set to the caller's organization. The projection additionally surfaces AWD.ROWID as ROW_ID, permitting updatable-view behavior and row-level identification of the persisted award row.

The organization filter is implemented through a nested DECODE on USERENV('CLIENT_INFO'), comparing the first ten characters of the client information string — the standard EBS mechanism by which the Multi-Org security context is communicated to the database session — against ORG_ID. Both sides of the comparison are wrapped in NVL(..., -99), so rows whose organization cannot be resolved collapse to a sentinel value rather than being silently dropped by a null comparison.

Key Columns

• AWARD_ID — primary identifier of the award record; the principal join key to award lines, disbursements, and revisions.
• FUND_ID / BASE_ID — the funding source and the base (need-analysis) record against which the award was calculated.
• OFFERED_AMT, ACCEPTED_AMT, PAID_AMT — the award lifecycle amounts, from initial offer through student acceptance to actual disbursement.
• PACKAGING_TYPE, BATCH_ID, MANUAL_UPDATE, RULES_OVERRIDE — indicators of how the award was produced: automatically by packaging, as part of a batch run, or overridden manually.
• AWARD_DATE, AWARD_STATUS — the effective date and current processing state of the award.
• ORG_ID — the operating unit that owns the row; drives the view's security predicate.
• RVSN_ID — revision identifier linking the award to its revision history.
• AWD_PROC_STATUS_CODE, NOTIFICATION_STATUS_CODE, NOTIFICATION_STATUS_DATE, PUBLISH_IN_SS_FLAG — award processing and student self-service notification indicators.
• ALT_PELL_SCHEDULE, LEGACY_RECORD_FLAG, AWARD_NUMBER_TXT, ADPLANS_ID, LOCK_AWARD_FLAG, APP_TRANS_NUM_TXT — Title IV and migration-related attributes carried forward from legacy aid systems.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — the standard EBS descriptive flexfield columns for client-specific extensions.
• Standard WHO and concurrent columns: CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID.

Common Use Cases and Queries

Reports and integrations use this view to reconcile offered versus disbursed aid, to identify awards produced by a specific packaging batch, and to extract award data for downstream student information systems. Because the view text mirrors the base table column-for-column, it is also used when building ad hoc extracts where the org security context is already set by the application.

Confirm existence before use, since ETRM records the object as not implemented:

• SELECT object_name, owner, status FROM all_objects WHERE object_name = 'IGF_AW_AWARD';

Typical award extract for the current operating unit:

• SELECT award_id, fund_id, award_status, offered_amt, accepted_amt, paid_amt, award_date FROM igf_aw_award WHERE award_status IN ('A','O') ORDER BY award_date DESC;

Batch reconciliation of packaging output:

• SELECT batch_id, count(*) awards, sum(offered_amt) offered, sum(accepted_amt) accepted FROM igf_aw_award WHERE batch_id = :batch_id GROUP BY batch_id;

Because the org predicate derives from USERENV('CLIENT_INFO'), queries issued outside an EBS session — for example from a standalone SQL client — should expect either no rows or the -99 sentinel branch, and should set the client information explicitly if cross-organization reporting is required.