Search Results use_blank_flag

Overview

IGF_AP_INST_VER_ITEM is an APPS-owned database view within the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 financials and student-aid module. It exposes verification item data captured against institutional student records, specifically the user-defined verification items associated with an award or applicant base record. The view is registered in FND Design Data as IGF.IGF_AP_INST_VER_ITEM and is flagged as a multi-org view, meaning it automatically filters its result set to the operating unit of the current session and suppresses rows belonging to other operating units. Its status is VALID, and it presents a curated projection of verification item attributes rather than a denormalized reporting structure.

The view participates in the ETRM verification workflow. It is referenced by several PL/SQL packages, including IGF_AP_BATCH_VER_PRC_PKG, IGF_AP_SS_PKG, and IGF_AP_VER_GRPS_PRC_PKG, indicating that it supports batch verification processing, self-service access, and verification grouping logic. Because it is referenced by the view IGF_AP_INS_VERN_ITEM_V and by batch processing packages, it functions both as a data source for downstream views and as a runtime dependency for verification business logic.

Underlying Base Objects

The documented dependency metadata identifies APPS.IGF_AP_INST_VER_ITEM_ALL as the referenced base object. The view therefore projects a filtered subset of the columns available on that underlying table. The "_ALL" suffix is consistent with the multi-org designation: the base table holds verification item rows across operating units, and the view applies the standard MO security predicate so that querying users see only records for their current org. The metadata does not document foreign-key relationships to other base tables, but the BASE_ID column provides the join key back to the parent institutional/award record. Additional ISIR-related attributes (ISIR_MAP_COL) imply a relationship to ISIR lookup values, though the underlying lookup table is not enumerated in the supplied metadata.

Key Columns

• ROW_ID — ROWID of the row, useful for direct row addressing.
• BASE_ID — Identifier for the student/base record to which the verification item belongs.
• UDF_VERN_ITEM_SEQ_NUM — Sequence number ordering the user-defined verification items.
• ITEM_VALUE — The user-defined verification value captured for the item.
• WAIVE_FLAG — Indicates the waive status of the user-defined value.
• USE_BLANK_FLAG — The specific column of interest in this search. It is a Y/N identifier determining whether a null value is treated as a documented value. A value of Y permits a blank entry to satisfy the verification item requirement; N requires an explicit non-null value.
• LEGACY_RECORD_FLAG — Flags records imported via the legacy import process.
• INCL_IN_TOLERANCE — Indicates whether the item is included in the Total Tolerance Amount calculation.
• ISIR_MAP_COL — Stores the ISIR SAR column number from lookups, establishing the item as a verification item.
• ORG_ID — Operating unit identifier used by the multi-org predicate.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard who columns for audit tracking.

Common Use Cases and Queries

Typical uses include retrieving verification items for a student award, auditing which items permit blank values, and reconciling legacy-imported records. The following query returns the sequence, item value, and blank-handling behavior for a given base record:

SELECT BASE_ID, UDF_VERN_ITEM_SEQ_NUM, ITEM_VALUE,
       WAIVE_FLAG, USE_BLANK_FLAG, ISIR_MAP_COL
FROM   APPS.IGF_AP_INST_VER_ITEM
WHERE  BASE_ID = :p_base_id
ORDER  BY UDF_VERN_ITEM_SEQ_NUM;

A focused audit of blank-value behavior can be expressed as follows:

SELECT BASE_ID, UDF_VERN_ITEM_SEQ_NUM, ITEM_VALUE
FROM   APPS.IGF_AP_INST_VER_ITEM
WHERE  USE_BLANK_FLAG = 'Y'
AND    ITEM_VALUE IS NULL;

Because the view is multi-org, callers must be operating within the correct operating unit context (or initialize the MO environment) for ORG_ID filtering to apply correctly. Queries intended for cross-org reporting should target the underlying IGF_AP_INST_VER_ITEM_ALL table instead.