Search Results competitor_flag

Overview

IGF_AP_MIS_ITMS_LTR_V is a reporting view in the Oracle E-Business Suite Financial Aid (IGF) module, owned by the APPS schema. As documented in the ETRM metadata, its purpose is to return the missing items (missing documents) that are required for Financial Aid processing. In practice, the view functions as a driver for correspondence and follow-up activity: it exposes the set of parties for whom required documents have not yet been received, together with formatted name and address information suitable for generating letters and reminders.

The view is validated across both Oracle EBS 12.1.1 and 12.2.2 and is intended for read-only consumption by reports, concurrent programs, and integration layer queries. It does not itself enforce the missing-item logic through stored procedures; rather, it supplies a flattened projection of party information that downstream Financial Aid processes join to their own missing-document criteria. This separation allows the institution to plug different tracking tables into the same correspondence output without altering the underlying data model.

Underlying Base Objects

The ETRM documentation for this view records no explicitly documented base objects; the definition is expressed through a single visible source in the view text — the HZ (Trading Community Architecture / Customer) party tables, aliased as HZ. This is consistent with Oracle's design of customer-facing views, which often expose large multi-column projections of HZ_PARTIES, HZ_PARTY_SITES, and related location attributes while shielding the physical table joins from the caller.

Because the metadata identifies no documented base tables, the authoritative relationship is the one stated in the object description: the view returns missing items required for Financial Aid processing. The HZ-sourced columns in the view text provide the party identity, address, and communication attributes that the missing-item list is enriched with. Functional key elements — the missing document definition, aid year, and application status — originate in the Financial Aid tables that are not enumerated in the documented view metadata and are therefore treated as undocumented for reference purposes. Practitioners should treat the HZ attributes as the stable, selectable portion of the view and verify any Financial Aid-specific join keys against the system data dictionary for the deployment's patch level.

Key Columns

• PARTY_ID / PERSON_ID — the unique party identifier, used as the primary join key to other Financial Aid and HZ objects.
• PARTY_NAME, PERSON_NUMBER, PARTY_TYPE — party display name, person number, and whether the record represents a person, organization, or group.
• ADDRESS_LINE1 through ADDRESS_LINE4, CITY, COUNTY, COUNTRY, POSTAL_CODE — the structured mailing address components used for correspondence.
• PERSON_NAME_ADDRESS — a derived column produced by IGS_CO_GEN_003.GET_PER_ADDR_FOR_CORR, returning the party's name and address formatted for correspondence.
• GIVEN_NAMES, SURNAME, MIDDLE_NAME, PREFIX, SUFFIX, PREFERRED_GIVEN_NAME — the name components derived from HZ.PERSON_FIRST_NAME, PERSON_LAST_NAME, PERSON_MIDDLE_NAME, and related name fields.
• EMAIL_ADDRESS, DO_NOT_MAIL_FLAG, LANGUAGE_NAME — communication attributes that govern delivery channel, mailing suppression, and language of the correspondence.
• PERSON_IDENTIFIER, PERSON_IDEN_TYPE — the identifying number and its type, typically the student or third-party identifier.
• ANALYSIS_FY, LAST_ORDERED_DATE — fiscal-year analysis and most recent order date attributes sourced from HZ.

Note that the view text enumerated in the metadata does not expose a column named REFERENCE_USE_FLAG, despite the search term used to locate this object. Readers searching on that flag should confirm whether the attribute resides in a sibling HZ or Financial Aid view rather than in IGF_AP_MIS_ITMS_LTR_V.

Common Use Cases and Queries

The most common application is generating missing-document reminder letters. A report joins the view to the Financial Aid missing-item criteria and selects the correspondence columns. A representative query follows:

• Reminder extract: SELECT p.PERSON_ID, p.PARTY_NAME, p.PERSON_NAME_ADDRESS, p.EMAIL_ADDRESS FROM APPS.IGF_AP_MIS_ITMS_LTR_V p WHERE p.DO_NOT_MAIL_FLAG = 'N';
• Address validation: SELECT p.PERSON_ID, p.ADDRESS_LINE1, p.CITY, p.COUNTRY, p.POSTAL_CODE FROM APPS.IGF_AP_MIS_ITMS_LTR_V p ORDER BY p.PARTY_NAME;
• Identifier lookup: SELECT p.PERSON_NUMBER, p.PERSON_IDENTIFIER, p.PERSON_IDEN_TYPE, p.PARTY_NAME FROM APPS.IGF_AP_MIS_ITMS_LTR_V p WHERE p.PERSON_IDENTIFIER = :identifier;
• Join to aid processing: SELECT p.PERSON_ID, p.PARTY_NAME FROM APPS.IGF_AP_MIS_ITMS_LTR_V p, APPS. m WHERE p.PERSON_ID = m.PERSON_ID;

Because the documented metadata does not enumerate the Financial Aid base tables, the join in the final example must be completed against the deployment's actual missing-item table and validated in each environment. All queries should be executed with the APPS schema context (or via a synonym) under standard EBS security, and results filtered by the institution's aid year and document rules before use in correspondence.