Results for “maximum_attempts”
7 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The IGFBV_TRACK_STUDENT_TODO_ITEMS view is a base, read-only reporting entity within the Oracle E-Business Suite Financial Aid (IGF) module. It consolidates item-instance information for student "to-do" items, which represent outstanding checklist requirements that a student must complete as part of an aid application or award-processing cycle. In the context of EBS 12.1.1 and 12.2.2, this view serves as the principal integration and reporting surface for downstream consumers, including OBIEE dashboards, self-service pages, and third-party connectivity. The view is defined WITH READ ONLY, so it is intended strictly for query access. It exposes both raw foreign-key identifiers and decoded, translated display values via the EBS lookup-view mechanism (the _LA: columns), enabling reporting tools to render lookup meanings without additional joins.
Underlying Base Objects
Although the documented ETRM metadata lists no referenced base objects, the view text reveals a multi-table join over five principal tables:
IGF_AP_TD_ITEM_INST_ALL(alias TDII) — the primary item-instance table that drives the view, supplying status, correspondence, attempt, and audit columns.IGF_AP_TD_ITEM_MST_ALL(alias TDM) — the item master, joined onTDM.TODO_NUMBER = TDII.ITEM_SEQUENCE_NUMBER, supplying item code and description.IGF_AP_FA_BASE_REC_ALL(alias BASE) — the financial aid base record, joined onTDII.BASE_ID = BASE.BASE_ID, supplying the person and calendar-instance context.IGS_CA_INST_ALL(alias CI) — the calendar instance, joined on calendar type and sequence number, supplying award-year alternate code and description.HZ_PARTIES(alias PE) — the TCA party registry, joined onBASE.PERSON_ID = PE.PARTY_ID, supplying party number and name.
Because the view spans institutional calendar (IGS) and TCA (HZ) schemas in addition to Financial Aid tables, it acts as a cross-module reporting hub.
Key Columns
The view exposes 24 columns. Central to the user's search term is CORRESPONDENCE_DATE, sourced from TDII.CORSP_DATE, which records the date on which correspondence regarding the item instance was sent. It is paired with CORRESPONDENCE_COUNT (TDII.CORSP_COUNT), the number of correspondence events. Other notable columns include:
ITEM_STATUSandITEM_STATUS_DATE— decoded status meaning and the date the status was set.ITEM_ADD_DATE,FREQUENCY_ATTEMPTS,MAXIMUM_ATTEMPTS— lifecycle and attempt-tracking attributes.INACTIVE_FLAG,REQD_FOR_COMPLETION_FLAG,LEGACY_RECORD_FLAG— decoded Yes/No flags.AWARD_YEAR,AWARD_YEAR_DESCRIPTION,PERSON_NUMBER,PERSON_NAME,ITEM_CODE,ITEM_DESCRIPTION— descriptive context.BASE_ID,ITEM_SEQUENCE_NUMBER,CLPRL_ID,PERSON_IDand the standard audit columns (CREATED_BY,CREATION_DATE,LAST_UPDATED_BY,LAST_UPDATE_DATE).
Common Use Cases and Queries
Typical usage includes tracking outstanding to-do items, measuring correspondence activity, and joining to award or disbursement data. A representative query follows:
SELECT PERSON_NUMBER, PERSON_NAME, ITEM_CODE, ITEM_STATUS, CORRESPONDENCE_DATE, CORRESPONDENCE_COUNT FROM APPS.IGFBV_TRACK_STUDENT_TODO_ITEMS WHERE AWARD_YEAR = :year AND CORRESPONDENCE_DATE IS NOT NULL ORDER BY CORRESPONDENCE_DATE DESC;- Identify students with repeated correspondence:
WHERE CORRESPONDENCE_COUNT > 1. - List incomplete requirements:
WHERE REQD_FOR_COMPLETION_FLAG = 'Y' AND ITEM_STATUS <> 'Complete'.
Because the view is read-only and already decodes lookups, it is well suited to direct report development with minimal SQL overhead.
-
Base View for the Entity that stores the item instance information
APPS.IGFBV_TRACK_STUDENT_TODO_ITEMS·↳ HZ_PARTIES·↳ IGF_AP_FA_BASE_REC_ALL·↳ IGF_AP_TD_ITEM_INST_ALL·Explore IGF module →
-
Full View for the Entity that stores the item instance information
APPS.IGFFV_TRACK_STUDENT_TODO_ITEMS·↳ HZ_PARTIES·↳ IGF_AP_FA_BASE_REC_ALL·↳ IGF_AP_TD_ITEM_INST_ALL·Explore IGF module →
-
Full View for the Entity that stores the item instance information
Not implemented in this database·Explore IGF module →
-
Base View for the Entity that stores the item instance information
Not implemented in this database·Explore IGF module →
-
eTRM - IGF Tables and Views 12.1.1
Holds pays only unit details for a pays only program