Results for “igf_db_disb_holds_all”

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

Overview

IGF.IGF_DB_DISB_HOLDS_ALL is a transaction table within the Oracle EBS Financial Aid (IGF) module that stores the various holds placed on a student disbursement. Disbursement holds represent financial or administrative blocks that prevent an award disbursement from being released, refunded, or posted to the student account until the underlying condition is resolved. The table is owned by the IGF schema and is documented as VALID in ETRM for both 12.1.1 and 12.2.2.

The table is classified by heuristic analysis as satellite-leaning in Data Vault terms. This is a modeling suggestion: the table is keyed by a surrogate HOLD_ID and carries descriptive, multi-valued state attributes (hold code, hold date, release date, release flag, release reason) attached to an award disbursement, which is the classic profile of a satellite hanging off a disbursement hub or link. It should not be treated as an independent hub, since its business meaning is derived entirely from the parent disbursement it qualifies.

Key Information Stored

The physical schema lists 15 columns. The surrogate primary key is HOLD_ID, enforced by the unique index IGF_DB_DISB_HOLD_PK. No separate business-key unique index is documented, so the business identity of a hold is the combination of the parent disbursement and hold attributes rather than a single natural key.

• HOLD_ID — surrogate primary key for each hold record.
• AWARD_ID and DISB_NUM — the foreign key that identifies the specific award disbursement being held; these columns point to IGF_AW_AWD_DISB_ALL.
• HOLD — the hold code or identifier applied to the disbursement.
• HOLD_TYPE — categorizes the hold (for example, a financial or administrative classification).
• HOLD_DATE — the date the hold was placed.
• RELEASE_FLAG — indicates whether the hold has been released.
• RELEASE_DATE — the date the hold was lifted.
• RELEASE_REASON — free-text or code explaining why the hold was released.
• ORG_ID — the multi-org operating unit that owns the record, relevant for security and reporting.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS WHO columns supporting audit and change tracking.

Common Use Cases and Queries

Typical usage centers on hold resolution reporting and disbursement release processing. Financial aid administrators query the table to identify disbursements that are blocked, to measure the age of outstanding holds, and to audit who released a hold and when.

A representative query for active holds joins the disbursement parent and filters on the release flag:

• SELECT h.hold_id, h.award_id, h.disb_num, h.hold, h.hold_type, h.hold_date FROM igf_db_disb_holds_all h WHERE h.release_flag = 'N' AND h.org_id = :p_org_id;
• Ageing analysis: SELECT h.hold_type, TRUNC(SYSDATE) - TRUNC(h.hold_date) days_held, COUNT(*) FROM igf_db_disb_holds_all h WHERE h.release_flag = 'N' GROUP BY h.hold_type, TRUNC(SYSDATE) - TRUNC(h.hold_date);
• Release audit: join CREATED_BY/LAST_UPDATED_BY to PER_ALL_PEOPLE_F to identify the administrator who applied or cleared the hold.

Because ORG_ID is present, all reporting queries against a shared ledger should be restricted by operating unit to respect multi-org access control. The WHO columns support incremental extraction into a data warehouse using LAST_UPDATE_DATE as the high-water mark.

Related Objects

The principal parent object is IGF_AW_AWD_DISB_ALL, joined on AWARD_ID and DISB_NUM; any query resolving holds to the underlying award and student must traverse this relationship. Other significant objects include IGF_AW_AWD_ALL and its disbursement scheduling tables for award-level context, the IGF disbursement release and validation concurrent programs that read this table to determine eligibility for release, and the financial aid self-service views that surface hold status to students and staff. Person and organization tables (PER_ALL_PEOPLE_F, HR_OPERATING_UNITS) are commonly joined for audit attribution and multi-org filtering. Because the documented FK data identifies only IGF_AW_AWD_DISB_ALL as a hard dependency, that relationship is the authoritative anchor when integrating IGF_DB_DISB_HOLDS_ALL with downstream reporting models.