Search Results disb_net_amt




Overview
Explore in AI Chat

Overview

IGF_SL_DB_COD_REP_V is a reporting view within the Oracle E-Business Suite IGF – Financial Aid product family. As documented in the ETRM metadata, it belongs to a module marked Obsolete, meaning it is not part of the currently supported Financial Aid functionality and may exist only in legacy or historical installations. The view carries no documented owner and is recorded in the 12.2.2 metadata as not implemented in this database, so it will not necessarily be present in every environment upgraded to 12.1.1 or 12.2.2.

Its stated purpose is narrow and specific: it is a view used for reporting the disbursement tags in the outbound XML file. In the Financial Aid context, outbound XML files are the machine-readable messages transmitted to external agencies and loan servicers (for example, Common Origination and Disbursement, or COD, processing). This view therefore functions as a denormalized, report-ready projection of disbursement detail data, presenting selected attributes in the exact shape required for inclusion in those outbound message payloads — most visibly through its formatting of date values and its trimming of identifier text fields.

Underlying Base Objects

The view is defined over a single documented base object: the table IGF_AW_DB_COD_DTLS. The metadata records no other referenced base objects, indicating a straightforward one-to-one projection rather than a join across multiple tables. The relationship is therefore direct: each row returned by the view corresponds to a disbursement detail record held in that table.

The select list performs light transformation rather than aggregation. Character identifiers are passed through TRIM(), and the two date columns — the disbursement date and the payment period start date — are converted to character using TO_CHAR(..., 'YYYY-MM-DD'). This formatting is characteristic of integration views, since XML payloads require unambiguous, locale-independent date literals rather than session-dependent date representations.

Because no owner is documented and the view is reported as not implemented, DBAs should confirm existence and validity against ALL_OBJECTS and ALL_VIEWS before relying on it.

Key Columns

Common Use Cases and Queries

Typical usage is diagnostic or reporting-oriented: verifying the disbursement data that will populate an outbound XML feed, reconciling transmitted values against the base table, or extracting historical disbursement detail for audit. A representative query is:

  • SELECT document_id_txt, award_id, disb_num, disb_net_amt, disb_date, disb_conf_flag FROM igf_sl_db_cod_rep_v WHERE disb_conf_flag = 'Y';
  • SELECT award_id, disb_num, disb_seq_num, disb_accepted_amt, pymnt_per_start_date FROM igf_sl_db_cod_rep_v ORDER BY award_id, disb_seq_num;
  • SELECT * FROM igf_sl_db_cod_rep_v WHERE first_disb_flag = 'Y'; — identifies first disbursements for reporting or validation.

Because the view is obsolete and not implemented in the documented database, these queries should be treated as reference patterns and validated against the actual environment before operational use.