Search Results corsp_date

Overview

IGF_AP_TD_ITEM_INST is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IGF (Financial Aid) product family. In EBS 12.1.1 and 12.2.2, it exposes institution-level records representing the "item instances" maintained against a financial aid applicant's tracking data (TD), specifically the column definitions that originate in the IGF_AP_TD_ITEM_INST_ALL table. The view is documented as VALID in the ETRM metadata and is provided primarily as a multi-org secured read interface over the underlying base table.

Its principal role is to present a consistent, Org_ID-filtered projection of item-instance data to reports, concurrent programs, and integration routines without requiring the caller to repeat the multi-org security predicate. Because the view contains the INACTIVE_FLAG column, it is commonly used to surface active versus retired item-instance rows in inquiry and extract logic.

Underlying Base Objects

Per the documented view text, the view is defined over a single base object: IGF_AP_TD_ITEM_INST_ALL (aliased TDII). No other referenced base objects are documented. The view is a straight projection of columns from that table, wrapped in the standard multi-org security predicate:

• Every column listed in the view (BASE_ID, ITEM_SEQUENCE_NUMBER, STATUS, INACTIVE_FLAG, ORG_ID, CLPRL_ID, and the audit columns) is mapped directly from IGF_AP_TD_ITEM_INST_ALL.
• The ROW_ID column is derived from TDII.ROWID, giving each returned row a stable Oracle physical row identifier suitable for updating through the view's base table.
• The WHERE clause applies NVL/TO_NUMBER/DECODE logic against USERENV('CLIENT_INFO') positions 1–10, matching the client's current Org_ID (or -99 as a null-equivalent sentinel). This makes the view an Org_ID-secured window: a session sees only rows whose ORG_ID equals the operating unit set in CLIENT_INFO.

Because the view is defined over an _ALL table with this security predicate, it behaves like the policy-protected view class in EBS: reports and forms that query it automatically receive the correct operating-unit scope.

Key Columns

• ROW_ID — physical row identifier derived from the base table ROWID; used for locating/updating records.
• BASE_ID — identifier of the parent financial aid base record to which the item instance belongs.
• ITEM_SEQUENCE_NUMBER — ordering sequence of the item instance within its parent.
• STATUS / STATUS_DATE — current processing status of the item instance and the date it was set.
• INACTIVE_FLAG — the column of interest in the user's search; indicates whether the item instance has been inactivated. Consumers filter on it to exclude retired rows from active processing.
• REQUIRED_FOR_APPLICATION — flags items mandatory to the application.
• FREQ_ATTEMPT / MAX_ATTEMPT — attempt frequency and maximum allowed attempts.
• CORSP_DATE / CORSP_COUNT — correspondence date and count associated with the item instance.
• ADD_DATE — date the record was added.
• LEGACY_RECORD_FLAG — indicates data migrated from a legacy system.
• ORG_ID — operating unit; drives the view's security predicate.
• CLPRL_ID — related classification/period reference identifier.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

The view supports applicant item-instance inquiries, multi-org extracts, and integration feeds. A typical query filtering on the searched column is:

SELECT base_id, item_sequence_number, status, inactive_flag, org_id
FROM apps.igf_ap_td_item_inst
WHERE inactive_flag = 'N';

Other practical patterns include joining BASE_ID to the parent application records for applicant-level reporting, and using ROW_ID for targeted DML against IGF_AP_TD_ITEM_INST_ALL. Because Org_ID security is embedded, the same SQL returns only the current operating unit's data, which simplifies responsibility-specific reports and concurrent extracts in both 12.1.1 and 12.2.2.