Results for “netted_cancel_amt”

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

Overview

IGF_SL_LI_ORG_DISB_INTS is a legacy interface table within the Oracle E-Business Suite Financial Aid (IGF) module. It functions as a staging and integration structure for Common Line origination and disbursement (disbursement roster) records exchanged between the institution, lenders, guarantors, and the Common Line processor. Because it is an interface ("_INTS") table rather than a transactional base table, its rows typically represent inbound or outbound payloads that are loaded, validated, corrected, and then propagated into the core Financial Aid tables or transmitted to external parties. The object is owned by the IGF schema and is documented as VALID in ETRM for both 12.1.1 and 12.2.2.

The documented physical schema lists 53 columns. Heuristic Data Vault classification mined from the foreign-key structure marks this object as standalone, meaning no outgoing parent references are declared. From a modeling perspective, it is best treated as a raw staging area (a satellite-like landing zone) rather than a strictly normalized hub or link; the composite business key behaves as the hub key, while the descriptive financial and status columns behave as satellite attributes.

Key Information Stored

The primary key is IGF_SL_LI_ORG_DISB_INTS_PK, defined over four columns: CI_ALTERNATE_CODE, PERSON_NUMBER, AWARD_NUMBER_TXT, and DISBURSEMENT_NUM. There is no separate single-column surrogate key; the composite key itself is the unique index and the business-key candidate. This is important when writing joins, because disbursement identity is only unique in combination with the student and award.

• CI_ALTERNATE_CODE, PERSON_NUMBER, AWARD_NUMBER_TXT, DISBURSEMENT_NUM — the composite business key identifying a student, award, and disbursement sequence.
• LOAN_NUMBER_TXT, SCH_DISBURSEMENT_NUM — lender loan identifier and the school-assigned disbursement sequence.
• DISBURSEMENT_DATE, FUND_RELEASE_DATE — the scheduled/actual disbursement and fund release dates.
• GROSS_DISBURSEMENT_AMT, NET_CANCEL_AMT, NETTED_CANCEL_AMT, OUTSTD_CANCEL_AMT — disbursement and cancellation amounts.
• ORIGINATION_FEE_AMT, GUARANTEE_FEE_AMT, ORIGINATION_FEES_PAID_AMT, GUARANTEE_FEES_PAID_AMT — fee amounts assessed and remitted.
• DISBURSEMENT_STATUS_CODE, DISBURSEMENT_STATUS_DATE, FUND_STATUS_CODE, FUND_STATUS_DATE — status tracking for disbursement and funding.
• ERR_MESG_1_CD through ERR_MESG_5_CD — validation error codes populated during interface processing.
• LENDER_NAME, GUARANTOR_USE_TXT, SCHOOL_USE_TXT, LENDER_USE_TXT — free-form and party identification fields.
• LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE — standard EBS audit columns.

Common Use Cases and Queries

Typical scenarios include troubleshooting a specific disbursement number, reconciling lender-reported disbursement rosters against expected awards, and reviewing records that failed validation. A common search begins with the disbursement number the user queried:

• Lookup by disbursement number: SELECT person_number, award_number_txt, disbursement_num, gross_disbursement_amt, disbursement_status_code FROM igf.igf_sl_li_org_disb_ints WHERE disbursement_num = :p_disb_num;
• Error resolution: filter on ERR_MESG_1_CD IS NOT NULL for the current load batch.
• Fee reconciliation: aggregate ORIGINATION_FEE_AMT and GUARANTEE_FEE_AMT by LENDER_NAME or SCH_DISBURSEMENT_NUM.
• Status reporting: group by DISBURSEMENT_STATUS_CODE and FUND_STATUS_CODE for a period based on DISBURSEMENT_DATE.

Related Objects

The metadata identifies this object as standalone with no declared foreign keys. In practice, integration occurs logically through the composite key columns rather than enforced constraints:

• IGF core award/person tables — joined via PERSON_NUMBER and AWARD_NUMBER_TXT.
• Common Line disbursement base tables — joined via CI_ALTERNATE_CODE and DISBURSEMENT_NUM.
• ROSTER_BATCH_ID_TXT — links records to a disbursement roster processing batch.
• RECIPIENT_ID_TXT / SOURCE_ID_TXT — used to tie records to trading partners in Common Line exchanges.

Because no enforced parent-child relationships are documented, referential integrity must be validated during loading and reconciliation rather than assumed by the database.