Search Results payment_prd_st_date

Overview

IGF_AW_AWD_DISB is an Oracle E-Business Suite view owned by the APPS schema and defined in the Oracle iGrants (IGF) module. It presents award disbursement data — one row for each scheduled or processed disbursement against a student award — and is the primary reporting and integration interface for disbursement-level information such as disbursed amounts, fees, eligibility, holds, and fund status. In the context of Oracle EBS 12.1.1 and 12.2.2, this view is the read-only access path used by concurrent programs, reports, and downstream extracts in place of the underlying transactional table.

The view is most commonly referenced when an implementer or analyst searches for the disbursement paid amount. In this view that attribute is exposed as the column DISB_PAID_AMT, which carries the amount actually paid against a given disbursement record.

Underlying Base Objects

The view is defined over a single base table, IGF_AW_AWD_DISB_ALL, aliased as ADISB in the view text. No other base objects are documented in the ETRM metadata for this view. The _ALL suffix is significant: the base table is partitioned by operating unit (ORG_ID), and the view enforces that partition.

The WHERE clause restricts rows to the current operating unit using the standard multi-org security predicate:

• NVL(ADISB.ORG_ID, NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'),1,1),' ',NULL,SUBSTRB(USERENV('CLIENT_INFO'),1,10))),-99)) = NVL(...)

Operating-unit-scoped queries return only the disbursement rows belonging to the active organization, including rows whose ORG_ID is null treated as belonging to a default (-99) organization. Because the view is a simple projection over IGF_AW_AWD_DISB_ALL, its columns map one-for-one to the base table, with the exception of several literal NULL placeholders (documented in the view text as trailing NULL expressions) that exist to preserve positional compatibility with related views.

Key Columns

The view exposes the full disbursement attribute set. Important columns include:

• ROW_ID — the ROWID of the underlying base table row, used for direct row addressing.
• AWARD_ID, DISB_NUM — identify the parent award and the disbursement sequence.
• DISB_GROSS_AMT, DISB_NET_AMT, DISB_ACCEPTED_AMT, DISB_PAID_AMT — the gross, net, accepted, and paid amounts for the disbursement.
• FEE_1, FEE_2, FEE_PAID_1, FEE_PAID_2, FEE_CLASS — fee amounts assessed and paid, and the fee classification.
• DISB_DATE, DISB_STATUS, DISB_STATUS_DATE, DISB_EXP_DT — disbursement date, status, status date, and expiration.
• ELIG_STATUS, ELIG_STATUS_DATE, AFFIRM_FLAG — eligibility determination and affirmation indicator.
• HOLD_REL_IND, MANUAL_HOLD_IND — hold release and manual hold indicators.
• FUND_DIST_MTHD, FUND_STATUS, FUND_STATUS_DATE, FUND_RELEASE_DATE, FUND_RETURN_MTHD_CODE — fund distribution and funding lifecycle attributes.
• CHEQUE_NUMBER — payment instrument reference.
• INT_REBATE_AMT, FORCE_DISB, LATE_DISB_IND, PAYMENT_PRD_ST_DATE — interest rebate, forced disbursement flag, late indicator, and payment period start.
• Standard Who columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and concurrent program columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE).

Common Use Cases and Queries

The primary use case is reporting paid disbursement amounts by award. A typical query is:

• SELECT award_id, disb_num, disb_gross_amt, disb_net_amt, disb_paid_amt, disb_status, disb_date FROM apps.igf_aw_award_disb WHERE award_id = :award_id ORDER BY disb_num;
• Summing amounts paid per award: SELECT award_id, SUM(disb_paid_amt) paid_total FROM apps.igf_aw_award_disb WHERE disb_status = 'PAID' GROUP BY award_id;
• Identifying outstanding or held disbursements: SELECT award_id, disb_num, disb_paid_amt FROM apps.igf_aw_award_disb WHERE manual_hold_ind = 'Y' OR hold_rel_ind = 'N';
• Reconciling fees against disbursements using fee_paid_1 and fee_paid_2.

Because the view is secured by operating unit, callers should ensure the correct organization context is set (or use the Multi-Org views/APIs) when querying in a multi-org environment.