Search Results add_date

Overview

The APPS.IGF_AP_TD_ITEM_INST view is a multi-org database object within the Oracle E-Business Suite Financial Aid (IGF) module. It exposes loan item instance data used primarily by the U.S. Department of Education Title IV (TD) processing flows. In EBS 12.1.1 and 12.2.2 the view is documented in the ETRM repository as object type VIEW, owned by the APPS schema, with the FND Design Data reference IGF.IGF_AP_TD_ITEM_INST and a status of VALID.

As a "multi-org view" the object automatically restricts query results to the operating unit of the current session. Records belonging to other operating units are suppressed by the underlying organization security predicate, so report writers, concurrent programs, and PL/SQL packages can query the view without writing their own ORG_ID predicates. This makes the view a standard reporting and integration surface for Title IV loan item instances rather than a raw table.

Underlying Base Objects

The view is defined over a single documented base object: APPS.IGF_AP_TD_ITEM_INST_ALL. The "_ALL" table holds the denormalized rows across every operating unit, and the view projects those rows through the multi-org security clause, filtering by ORG_ID to return only data relevant to the current organization.

The view is referenced by several dependent program units and objects, confirming its role as a shared interface:

• APPS.IGF_AP_ISIR_GEN_PKG
• APPS.IGF_AP_LG_TD_IMP
• APPS.IGF_AP_MATCHING_PROCESS_PKG
• APPS.IGF_AP_PROFILE_MATCHING_PKG
• APPS.IGF_AP_TD_ITEM_INST_V
• APPS.IGF_AP_TODO_GRPS_PRC_PKG
• APPS.IGF_AW_GEN_004
• APPS.IGF_AW_LI_IMPORT

These dependencies indicate the view feeds ISIR generation, loan import, matching, profile-matching, and award-generation logic — a central position in the financial aid data model.

Key Columns

The view exposes the following columns, each carrying specific semantics for Title IV loan item instances:

• ROW_ID – ROWID of the underlying row.
• BASE_ID / ITEM_SEQUENCE_NUMBER – Identifiers linking the item instance to its parent record and ordering.
• STATUS / STATUS_DATE – Current processing status and the date it was set.
• ADD_DATE – Date the item instance was added; the column most directly referenced by the user's "add_date" search.
• CORSP_DATE / CORSP_COUNT – Correspondence date and count tracked against the item.
• INACTIVE_FLAG – Indicates whether the record is inactive.
• REQUIRED_FOR_APPLICATION – Whether the item is required to complete the application.
• FREQ_ATTEMPT / MAX_ATTEMPT – Attempt frequency and configured maximum.
• LEGACY_RECORD_FLAG – Marks records imported through the legacy import process.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard audit columns.
• ORG_ID – Operating unit used for the multi-org filter.
• CLPRL_ID – The lender the student selected as preferred.

Common Use Cases and Queries

Typical uses include reporting on loan item instance status, tracing when instances were created, and supplying ISIR, matching, and award-generation processes with current operating-unit data. A basic query filtered on the requested column follows:

• Items added in a date range:
  SELECT base_id, item_sequence_number, status, add_date
FROM apps.igf_ap_td_item_inst
WHERE add_date >= :start_date
AND add_date < :end_date;
• Inactive or legacy records:
  SELECT base_id, inactive_flag, legacy_record_flag
FROM apps.igf_ap_td_item_inst
WHERE inactive_flag = 'Y';
• Preferred lender per instance:
  SELECT base_id, clprl_id, status
FROM apps.igf_ap_td_item_inst
WHERE clprl_id IS NOT NULL;

Because the view is multi-org, these queries automatically return only the rows for the session's operating unit, which is essential when the same base_id exists across organizations.