Results for “disb_int_rebate”

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

Overview

IGF_DB_YTD_DTL_ALL is a staging and detail table within the Oracle E-Business Suite Financial Aid (IGF) module, a component historically associated with the Oracle Student System and Title IV federal student aid processing. As documented in the ETRM 12.1.1 physical schema, the table stores data loaded through the Year-to-Date (YTD) disbursement data file. This places the object squarely in the disbursement reconciliation and reporting layer of the Financial Aid product, where inbound flat-file extracts from loan servicers, guaranty agencies, or the Common Origination and Disbursement (COD) system are parsed and persisted for downstream validation, aggregation, and audit.

The ETRM metadata explicitly labels IGF as "Obsolete." In Oracle EBS 12.1.1 and 12.2.2 environments the table is documented but "Not implemented in this database," meaning a given instance may carry the definition without populated rows. Consumers should therefore verify existence and row counts before depending on it for live reporting. From a heuristic Data Vault perspective, the mined FK structure classifies IGF_DB_YTD_DTL_ALL as standalone, which suggests modeling the table as a satellite or independent hub rather than a link, since no foreign-key relationships to parent entities were detected in the documented schema.

Key Information Stored

The table carries 36 documented columns in the ETRM 12.1.1 schema. The most operationally significant are:

• YTDD_ID — surrogate primary key, backed by unique index IGF_DB_YTD_DTL_PK, uniquely identifying each YTD detail record.
• DL_VERSION — data-load version, supporting regeneration and file-level traceability.
• RECORD_TYPE — classifier distinguishing record categories within the loaded file.
• BATCH_ID — groups records belonging to a single load or reconciliation batch.
• SCHOOL_CODE — institution identifier, the primary business dimension for financial aid reporting.
• LOAN_NUMBER — individual loan identifier linking the detail row to the underlying award.
• STAT_END_DT / PROCESS_DT — statistical period end and processing dates anchoring the record in time.
• DISB_GROSS, DISB_FEE, DISB_INT_REBATE, DISB_NET, DISB_NET_ADJ — the disbursement amount components, forming the core financial payload.
• TOTAL_GROSS, TOTAL_FEE, TOTAL_INT_REBATE, TOTAL_NET — cumulative YTD totals for the associated loan or student.
• ORG_ID — Multi-Org operating unit, the standard EBS partitioning key.
• REQUEST_ID — concurrent request that loaded the row, essential for batch tracing and error recovery.

Standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and program context columns (PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE) are also present. No business-key unique index beyond the surrogate key is documented, so deduplication must rely on composite attributes such as LOAN_NUMBER, DISB_SEQ_NUM, and DISB_BKD_DT.

Common Use Cases and Queries

The principal use case is reconciliation between the YTD disbursement file and internal loan/award balances. Typical patterns include:

• Batch validation: SELECT BATCH_ID, REC_COUNT, COUNT(*) FROM IGF_DB_YTD_DTL_ALL GROUP BY BATCH_ID, REC_COUNT; to confirm loaded row counts equal the file control totals.
• Per-school YTD aggregation: SELECT SCHOOL_CODE, SUM(TOTAL_NET) FROM IGF_DB_YTD_DTL_ALL WHERE STAT_END_DT = :p_dt GROUP BY SCHOOL_CODE;
• Error diagnosis by concurrent request: filtering on REQUEST_ID and DL_VERSION to isolate a failed load.
• Variance analysis: comparing DISB_NET against TOTAL_NET to detect adjustment or interest-rebate discrepancies.

Reporting extracts feeding federal reconciliation reports and internal audit trails are the most frequent downstream consumers. Extracts typically join on LOAN_NUMBER and restrict by ORG_ID and STAT_END_DT.

Related Objects

The mined relationship data classifies this table as standalone, meaning no FK constraints were detected in the documented schema. In practice, logical linkage occurs through shared business keys rather than enforced constraints. The most significant related objects are:

• IGF_DB_YTD_DTL_PK — the primary key index over YTDD_ID.
• Loan and award base tables in the IGF module, joined logically on LOAN_NUMBER.
• Institution/school reference data, joined on SCHOOL_CODE.
• Concurrent request tables (FND_CONCURRENT_REQUESTS), joined on REQUEST_ID to trace load jobs.
• Operating unit definitions, joined on ORG_ID.
• Various IGF reporting views and the disbursement summary routines that consume the TOTAL_* aggregates.

Because the schema lacks enforced foreign keys, referential integrity depends on application logic and the load process itself.