Search Results last_ordered_date
Overview
IGS_AD_POSTADM_MISS_ITM_LTR_V is a reporting view in the Oracle E-Business Suite (EBS) Student System (IGS) product, owned by the APPS schema. Its documented purpose is to return missing items associated with Post Admission Requirements, supporting correspondence and letter generation for admitted applicants who have outstanding admissions checklist items. The view is delivered as a VALID database object in both EBS 12.1.1 and 12.2.2 and is intended primarily for XML Publisher / BI Publisher letter templates and operational reports rather than for transactional processing.
Operationally, the view joins party-level data from the Trading Community Architecture (TCA) registry to admissions requirement data, allowing a letter template to print recipient identity, address, and the outstanding requirement description in a single query. It therefore occupies the reporting tier of the IGS architecture: it does not store data and should not be used as an update surface.
Underlying Base Objects
The ETRM metadata for 12.2.2 does not enumerate referenced base tables for this view; the documented excerpt contains only the inline view text, in which the TCA party columns are projected through the HZ alias. Based on that text, the principal contributor is the TCA party/party-site layer (HZ_PARTIES and the associated address, contact-point, and profile-denormalization objects supplying ADDRESS1–ADDRESS4, EMAIL_ADDRESS, and the currency/category columns).
The admissions "missing item" side of the query is drawn from the IGS post-admission requirements tables, which hold the checklist line definitions and the per-person completion status that determines whether an item is outstanding. Because the published metadata lists no confirmed base objects, all dependency claims beyond the HZ party projection should be validated against DBA_DEPENDENCIES in the target instance before use.
Key Columns
- PERSON_ID — party identifier from HZ_PARTIES; the join key to the student person record.
- PERSON_NUMBER — human-readable party number used on correspondence.
- PARTY_NAME, GIVEN_NAMES, SURNAME, MIDDLE_NAME, PREFIX, SUFFIX — name components supporting merge-field formatting in letters.
- KNOWN_AS, PREFERRED_GIVEN_NAME, KNOWN_AS2 through KNOWN_AS5 — alternate name attributes exposed for salutation and preferred-name handling; this is the column family referenced by the search term "known_as3", where
KNOWN_AS3is projected directly from HZ_PARTIES and aliased as KNOWN_AS3. - ADDRESS_LINE1–ADDRESS_LINE4, CITY, COUNTY, PROVINCE, POSTAL_CODE, COUNTRY — mailing address elements.
- EMAIL_ADDRESS — primary electronic contact point, where populated.
- PERSON_IDEN_TYPE, PERSON_IDENTIFIER — identification type and value (for example institutional or national identifier).
- ANALYSIS_FY, CURR_FY_POTENTIAL_REVENUE, NEXT_FY_POTENTIAL_REVENUE, CATEGORY_CODE — TCA classification and analysis attributes carried through for institutional reporting.
- DO_NOT_MAIL_FLAG, REFERENCE_USE_FLAG — suppression and reference-use indicators that should be honored in any outward correspondence process.
Common Use Cases and Queries
The dominant use case is a Post Admission Requirements letter: a concurrent program passes a person or applicant range and the template prints each outstanding item alongside the addressee's preferred name and mailing address.
SELECT person_number,
party_name,
known_as3,
surname,
given_names,
address_line1,
city,
postal_code
FROM apps.igs_ad_postadm_miss_itm_ltr_v
WHERE person_id = :p_person_id;
A second scenario is an operational audit of outstanding post-admission items, filtered to exclude suppressed records:
SELECT person_id,
person_number,
party_name,
known_as,
known_as3,
email_address
FROM apps.igs_ad_postadm_miss_itm_ltr_v
WHERE do_not_mail_flag = 'N';
Because KNOWN_AS3 is a pass-through party attribute rather than an admissions attribute, it is typically consumed only when the institution configures a third alternate-name field for legal or cultural naming conventions. Queries should always filter on PERSON_ID or the institution's applicant set to avoid a full scan of the TCA party population.
-
View: IGS_AD_POSTADM_MISS_ITM_LTR_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IGS.IGS_AD_POSTADM_MISS_ITM_LTR_V, object_name:IGS_AD_POSTADM_MISS_ITM_LTR_V, status:VALID, product: IGS - Student System , description: It returns the Missing items for Post Admission Requirements , implementation_dba_data: APPS.IGS_AD_POSTADM_MISS_ITM_LTR_V ,
-
View: IGS_AD_RESI_LETTER_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IGS.IGS_AD_RESI_LETTER_V, object_name:IGS_AD_RESI_LETTER_V, status:VALID, product: IGS - Student System , description: It would return the Residency Details of a student , implementation_dba_data: APPS.IGS_AD_RESI_LETTER_V ,
-
View: IGS_AD_ACK_LETTER_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IGS.IGS_AD_ACK_LETTER_V, object_name:IGS_AD_ACK_LETTER_V, status:VALID, product: IGS - Student System , description: It would return the Acknowledgement Details of a student , implementation_dba_data: APPS.IGS_AD_ACK_LETTER_V ,
-
View: IGS_AD_OUTCOME_LETTERS_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IGS.IGS_AD_OUTCOME_LETTERS_V, object_name:IGS_AD_OUTCOME_LETTERS_V, status:VALID, product: IGS - Student System , description: The validations for the individual letters are placed at the SQLl query level that we attach to master document , implementation_dba_data: APPS.IGS_AD_OUTCOME_LETTERS_V ,
-
View: IGS_AD_MISSING_ITEMS_LETTER_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:IGS.IGS_AD_MISSING_ITEMS_LETTER_V, object_name:IGS_AD_MISSING_ITEMS_LETTER_V, status:VALID, product: IGS - Student System , description: Returns the missing items. For processing application of the student, few documents are required by the admission module. When student forget to send any document or miss out any document , then these documents are treated as missing items , implementation_dba_data: APPS.IGS_AD_MISSING_ITEMS_LETTER_V ,