Search Results igf_db_awd_disb_dtl

Overview

The view IGF_DB_AWD_DISB_DTL belongs to the IGF (Financial Aid) product family within Oracle EBS. The ETRM metadata explicitly classifies the owning module as IGF – Financial Aid (Obsolete), and the object carries the "Not implemented in this database" designation in the supplied documentation. Consequently, the view is a legacy or dormant database object that may exist in certain 12.1.1 / 12.2.2 environments but is not guaranteed to be present or populated in a given instance. Its structural purpose is to expose award disbursement detail records — the individual disbursement transactions that make up the award schedule for a student or sponsor — through an operating-unit-filtered, security-aware presentation layer suitable for reporting and integration.

The view is clearly not a base-table replacement: it is a projection and filtering vehicle. Its primary functional role is to present disbursement detail rows for downstream consumers such as disbursement reconciliation reports, sponsor billing extracts, and interfaces to external financial systems, while enforcing multi-org access controls at query time.

Underlying Base Objects

The view text is defined exclusively over a single underlying table, IGF_DB_AWD_DISB_DTL_ALL, aliased as DBDTL. ETRM documents no other referenced base objects, which indicates that the view is a straight projection with a security filter rather than a join-heavy construct. The naming convention of the underlying table (_ALL) is consistent with Oracle's multi-organization architecture: the _ALL table stores rows for every operating unit, and the view applies the standard operating-unit predicate to restrict results to the current session's organization context.

The operating-unit filter is implemented using the traditional client-info pattern: the value is parsed from USERENV('CLIENT_INFO') using SUBSTRB and DECODE, and compared against NVL(DBDTL.ORG_ID, -99). This construction means rows with a null ORG_ID are treated as belonging to a sentinel organization (-99) and are only visible when the session's parsed client info also resolves to that sentinel. This is the classic pre-MO_GLOBAL multi-org filtering technique used throughout older EBS modules.

Key Columns

The column list maps directly to the IGF_DB_AWD_DISB_DTL_ALL table, with a synthetic ROW_ID derived from the table's ROWID. Notable columns include:

• AWARD_ID, DISB_NUM, DISB_SEQ_NUM — identify the award and the specific disbursement (number and sequence) within that award.
• DISB_GROSS_AMT, FEE_1, FEE_2, DISB_NET_AMT, DISB_ADJ_AMT — gross, fee-deducted, net, and adjustment amounts for the disbursement.
• DISB_DATE, DISB_ACTIVITY, NOTIFICATION_DATE — timing and activity status information.
• FEE_PAID_1, FEE_PAID_2 — indicators of whether associated fees have been paid.
• SF_STATUS, SF_STATUS_DATE, SF_INVOICE_NUM — student financials (SF) posting status, the date it was set, and the related invoice.
• SPNSR_CREDIT_ID, SPNSR_CHARGE_ID, SF_CREDIT_ID — identifiers linking the disbursement to sponsor and SF credit/charge records.
• INTEREST_REBATE_AMT — interest rebate amount for the disbursement.
• LD_CAL_TYPE, LD_SEQUENCE_NUMBER — load calendar type and sequence, used for academic-period attribution.
• ERROR_DESC — description of errors encountered during processing or interface attempts.
• Standard WHO/audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, plus concurrent-program columns REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.
• DISB_BATCH_ID, DISB_ACK_DATE, BOOKING_BATCH_ID, BOOKED_DATE, DISB_STATUS, DISB_STATUS_DATE — appear in the documented column list but are projected as NULL literals in the view text, indicating these attributes are not sourced from the current underlying table.

Common Use Cases and Queries

Typical use cases include reconciling disbursements for a given award, listing disbursements by status for a student financials posting run, and extracting sponsor-related credit/charge references for billing. Because the view filters on operating unit via client info, queries are generally executed from within an EBS session that sets the organization context, or from a reporting tool configured to emulate that context.

A representative query retrieving net disbursements for an award:

• SELECT award_id, disb_num, disb_seq_num, disb_date, disb_net_amt, sf_status, sf_invoice_num
• FROM igf_db_awd_disb_dtl
• WHERE award_id = :p_award_id
• ORDER BY disb_num, disb_seq_num;

Given the "Obsolete" and "Not implemented" classifications, any implementation depending on this view should verify its existence and population before use, and consider migrating to the supported successor objects for award disbursement reporting.