Search Results required_for_application




Overview
Explore in AI Chat

Overview

IGF_AP_TD_ITEM_MST is a valid Oracle E-Business Suite view owned by the APPS schema within the IGF (Financial Aid) product family. It presents master reference data for financial aid tracking items and "to-do" requirements that applicants must complete as part of the aid application lifecycle. In EBS 12.1.1 and 12.2.2, the view functions as an organization-secured, Multi-Org-compliant projection over the underlying base table IGF_AP_TD_ITEM_MST_ALL, exposing only the rows relevant to the operating unit identified through the session's CLIENT_INFO context. Because the view is defined with a WHERE clause that resolves against ORG_ID, it serves as the standard access point for forms, concurrent programs, OAF pages, and custom reporting rather than querying the _ALL table directly.

Underlying Base Objects

The ETRM metadata documents no separately listed referenced base objects, but the embedded view text establishes the definition precisely. The view selects from IGF_AP_TD_ITEM_MST_ALL and applies an organization security predicate:

  • Base table: IGF_AP_TD_ITEM_MST_ALL, which stores the unfiltered, Multi-Org enabled rows spanning all operating units.
  • Row filter: NVL(ORG_ID, NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'),1,1),' ',NULL,SUBSTRB(USERENV('CLIENT_INFO'),1,10))),-99)) = NVL(TO_NUMBER(...),-99). This classic Multi-Org view pattern derives the current operating unit from CLIENT_INFO, substituting -99 when the session context is blank, and preserves rows whose ORG_ID is null.
  • Structure: The view is a simple single-table projection; it introduces no joins, unions, or aggregations, so it remains updatable in the same manner as the base table for the visible organization.

Key Columns

Common Use Cases and Queries

Typical reporting scenarios include listing mandatory application items, validating self-service display configuration, and resolving document URLs for applicant portals. Because ORG_ID filtering is implicit, queries executed under a properly initialized session return only the current operating unit's rows.

  • Retrieve all required items: SELECT TODO_NUMBER, ITEM_CODE, DESCRIPTION FROM APPS.IGF_AP_TD_ITEM_MST WHERE REQUIRED_FOR_APPLICATION = 'Y';
  • Filter by application context: SELECT ITEM_CODE, APPLICATION_CODE, SYSTEM_TODO_TYPE_CODE FROM APPS.IGF_AP_TD_ITEM_MST WHERE APPLICATION_CODE = :p_app_code;
  • Identify self-service enabled documents: SELECT ITEM_CODE, SS_INSTRUCTION_TXT, DOCUMENT_URL_TXT FROM APPS.IGF_AP_TD_ITEM_MST WHERE DISPLAY_IN_SS_FLAG = 'Y' AND ALLOW_ATTACHMENT_FLAG = 'Y';
  • Inspect attempt controls: SELECT ITEM_CODE, FREQ_ATTEMPT, MAX_ATTEMPT FROM APPS.IGF_AP_TD_ITEM_MST ORDER BY ITEM_CODE;

When the value of :p_app_code must resolve across applications, join to the corresponding application table on APPLICATION_CODE, taking care to initialize FND_CLIENT_INFO or use MO_GLOBAL so the Multi-Org predicate returns the intended organization's rows.