Search Results release_flag

Overview

IGF_DB_DISB_HOLDS_V is a reporting view owned by the APPS schema within the IGF (Financial Aid) product family of Oracle E-Business Suite. It presents disbursement hold records maintained against financial aid awards, joining the base hold table to the lookup repository so that the internal lookup code carried on each hold record is resolved to its descriptive meaning. In ETRM 12.2.2 the object is registered as a VIEW with a status of VALID, making it a supported read-only access point for operational reporting, extracts, and downstream integrations that require visibility into which disbursements are blocked, why they are blocked, and whether the block has been lifted.

The view is significant because it consolidates two logically separate concerns — the transactional hold itself and the lookup-driven classification of that hold — into a single projection. Consumers do not need to know the lookup type name or join to the lookup view independently; the descriptive MEANING column is materialized directly in the result set.

Underlying Base Objects

The view text is defined over two objects:

• IGF_DB_DISB_HOLDS — the base hold table, aliased HOLD in the view definition. This supplies the transactional columns and all of the key identifiers and audit columns.
• IGF_LOOKUPS_VIEW — the lookup repository, aliased LKP. This supplies the descriptive MEANING value for the hold code.

The join condition is deliberately narrow and type-scoped. It restricts lookup rows to LOOKUP_TYPE = 'IGF_DB_DISB_HOLDS' and matches HOLD.HOLD = LKP.LOOKUP_CODE. Because the filter is applied on lookup type, the view returns only holds whose code participates in the IGF_DB_DISB_HOLDS lookup set; hold codes that have no matching enabled lookup row will be excluded from the result set entirely. This is an inner-join semantics consideration that matters when reconciling the view against the base table.

Key Columns

• ROW_ID — the unique row identifier for the hold record.
• HOLD_ID — primary key of the hold, used to reference the hold in update or release transactions.
• AWARD_ID — the financial aid award to which the hold is attached; the principal linkage for award-level reporting.
• DISB_NUM — the disbursement number identifying the specific disbursement affected by the hold.
• HOLD — the lookup code representing the hold; this is the value joined to the lookup repository.
• HOLD_TYPE — the classification or category of the hold.
• MEANING — the descriptive text for the hold code sourced from IGF_LOOKUPS_VIEW; the human-readable label for HOLD.
• HOLD_DATE — the date on which the hold was applied.
• RELEASE_FLAG — indicates whether the hold has been released. This column is the focus of the search term "release_flag" and is the standard mechanism for distinguishing active holds from released ones.
• RELEASE_DATE — the date the hold was released, populated when release processing has occurred.
• RELEASE_REASON — free-text or coded explanation recorded at the time of release.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns for change tracking and ownership attribution.

Common Use Cases and Queries

The view is typically queried to enumerate active blocks on disbursement, to report hold history for an award, and to validate that release processing has completed. A representative query listing outstanding holds for an award is:

SELECT award_id, disb_num, hold, meaning, hold_date
FROM   apps.igf_db_disb_holds_v
WHERE  release_flag = 'N'
AND    award_id = :p_award_id;

Reporting on released holds and their reasons uses the release columns:

SELECT hold_id, disb_num, meaning, hold_date,
       release_date, release_reason
FROM   apps.igf_db_disb_holds_v
WHERE  release_flag = 'Y'
AND    release_date BETWEEN :p_from AND :p_to;

A third pattern counts active holds per hold type to identify systemic disbursement blocking:

SELECT meaning, COUNT(*) active_cnt
FROM   apps.igf_db_disb_holds_v
WHERE  release_flag = 'N'
GROUP  BY meaning
ORDER  BY active_cnt DESC;

Because the view exposes RELEASE_FLAG directly, it is well suited to both operational dashboards that require current blocking states and to historical extracts that document the lifecycle of each hold.