Search Results base_attendance_type_code

Overview

The IGF.IGF_AW_LI_DISB_INTS table is the Award Disbursements Interface Table for Legacy Data Import within the Oracle E-Business Suite Financial Aid (IGF) product. It serves as a staging and integration surface through which award and disbursement records originating from external or legacy financial aid systems are loaded into Oracle EBS, most notably through the "Legacy - Award and Disbursement Data Import Process." The object is owned by the IGF schema, resides in the APPS_TS_INTERFACE tablespace with a PCT Free of 10, and carries a lifecycle status of active. Under the FND Design Data classification it is registered as IGF.IGF_AW_LI_DISB_INTS and is categorized as a business entity of type IGF_AWARD. Because the documented FK structure exposes no parent-child foreign key constraints, the heuristic Data Vault classification is standalone; from a modeling perspective, this object is best treated as an interface or staging structure rather than a conformed hub, link, or satellite.

Key Information Stored

The table contains 31 documented columns in the 12.1.1 physical schema. The most significant are summarized below.

• CI_ALTERNATE_CODE – Award Year Calendar Instance Alternate Code (the Award Year) for the Financial Aid Award.
• PERSON_NUMBER – Person number of the student recipient.
• AWARD_NUMBER_TXT – Unique award number for the student in context.
• DISBURSEMENT_NUM – Disbursement number of the award.
• LD_ALTERNATE_CODE / TP_ALTERNATE_CODE – Calendar instance alternate codes for the Term and Teaching Period respectively.
• OFFERED_AMT / ACCEPTED_AMT – Total offered and accepted disbursement amounts.
• DISB_DATE – Disbursement date.
• TRANS_TYPE_CODE – Indicates whether the transaction is Planned or Actual.
• FEE_1_AMT / FEE_2_AMT – Origination or Direct Loan lender fees and CommonLine guarantor fees.
• AFFIRM_FLAG / FORCE_DISB_FLAG – Confirmation and forced-disbursement indicators.
• ATTENDANCE_TYPE_CODE / BASE_ATTENDANCE_TYPE_CODE – Attendance classification values relevant to the user search term.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard WHO audit columns.

The surrogate primary key is IGF_AW_LI_DISB_INTS_PK, a unique NORMAL index on (CI_ALTERNATE_CODE, PERSON_NUMBER, AWARD_NUMBER_TXT, DISBURSEMENT_NUM). This same composite is the only documented unique business-key candidate; no separate single-column surrogate identifier exists in the metadata.

Common Use Cases and Queries

The principal use case is bulk import of legacy award and disbursement data, followed by validation and reconciliation reporting.

• Attendance type resolution – Because the user searched for base_attendance_type_code, the most direct query filters by that column alongside ATTENDANCE_TYPE_CODE to compare base versus actual attendance classification.
• Disbursement reconciliation – Compare OFFERED_AMT against ACCEPTED_AMT and the fee columns to detect mismatches prior to posting.
• Load monitoring – Use TRANS_TYPE_CODE and DISB_DATE to track Planned versus Actual disbursements by term.

Representative SQL:

• SELECT person_number, award_number_txt, disbursement_num, base_attendance_type_code, attendance_type_code FROM igf.igf_aw_li_disb_ints WHERE base_attendance_type_code IS NOT NULL;
• SELECT award_number_txt, SUM(offered_amt), SUM(accepted_amt) FROM igf.igf_aw_li_disb_ints GROUP BY award_number_txt;

Related Objects

Although the metadata classifies this object as standalone, it functions within the broader IGF award and disbursement model. The following objects are the most significant conventional participants.

• IGF_AW_AWARDS_ALL / IGF_AW_AWARDS_B – Joined on AWARD_NUMBER_TXT to resolve the award header.
• IGF_AW_DISBURSEMENTS – Joined on AWARD_NUMBER_TXT and DISBURSEMENT_NUM to reconcile posted disbursements.
• IGF_AP_PERSON_ID / IGF_AP_FUNDS – Resolved through PERSON_NUMBER to identify the recipient.
• IGF_AW_CI_CAL_INSTANCES – Joined on CI_ALTERNATE_CODE, LD_ALTERNATE_CODE, and TP_ALTERNATE_CODE to resolve calendar instances.
• FND_FLEX_VALUES_VL – Used to validate TRANS_TYPE_CODE and ATTENDANCE_TYPE_CODE lookup values.

These relationships are inferred from documented column semantics; no explicit FK constraints are recorded in the ETRM metadata.