Search Results igf_aw_gen_004




Overview
Explore in AI Chat

Overview

APPS.IGF_AW_AWD_LTR_V is a reporting and integration view within the Oracle E-Business Suite Grants and Awards Management (formerly Oracle Grants/Projects) product family, delivered under the IGF application schema. It is designed to present consolidated party (person or organization) information for use in award letter generation and related award-processing workflows. The view draws primarily from the trading community (TCA) data model, exposing columns that originate from HZ_PARTIES and related party entities, so that award letter templates, concurrent programs, and correspondence processes can retrieve demographic, address, and contact attributes in a single query.

The view name incorporates "AW_AWD_LTR," indicating its role as the award letter view. Rather than storing data, it provides a denormalized, read-only projection of party attributes joined with award-specific processing logic, making it suitable for RTF templates, BI Publisher reports, and custom extensions. The column selection is heavily oriented toward correspondence: names, salutations, addresses, and communication preferences are all included so that generated award letters can be properly addressed.

Underlying Base Objects

The view's SELECT list derives almost entirely from HZ_PARTIES and associated TCA objects, aliased as "hz" in the view text. TCA (Trading Community Architecture) is the foundational data model for parties, locations, and contacts across EBS, shared by CRM, Receivables, and Grants modules. Because ETRM metadata documents no referenced base objects explicitly, the relationships are inferred from the aliased columns:

  • HZ_PARTIES — the primary source, supplying party_id, party_name, party_number, party_type, address lines, classification attributes (category_code, group_type), fiscal attributes (analysis_fy, curr_fy_potential_revenue, next_fy_potential_revenue, fiscal_yearend_month), and numerous person and organization name columns.
  • HZ_CUST_ACCOUNTS / HZ_CUST_ACCT_SITES — likely contributors of customer_key and address-related fields, since customer_key appears in the projection.
  • IGS_CO_GEN_003 — a stored PL/SQL package referenced via the function get_per_addr_for_corr, which assembles a formatted correspondence address for the party and returns it into the person_name_address column.

The view therefore acts as a party-correspondence abstraction: consumers reference IGF_AW_AWD_LTR_V without needing to know the underlying TCA joins or the package-based address formatting logic.

Key Columns

The view exposes a broad set of party attributes. Noteworthy columns include:

  • party_id / person_id — the unique party identifier, used as the join key to other views and tables.
  • party_name, party_number, person_number — display and reference identifiers for the party.
  • party_type, group_type — classification of the party as person, organization, or group, driving conditional rendering in letters.
  • address_line1 through address_line4, city, county, state, province, postal_code, country — structured address fields for mail-merge.
  • person_name_address — the preformatted correspondence address returned by get_per_addr_for_corr.
  • given_names, surname, middle_name, prefix, suffix, salutation, title — name components for personalized letters.
  • email_address, do_not_mail_flag, reference_use_flag, status — communication preferences and party status.
  • customer_key, duns_number, sic_code, employees_total, competitor_flag, gsa_indicator_flag — organization-level attributes relevant to eligibility and compliance checks.
  • analysis_fy, curr_fy_potential_revenue, next_fy_potential_revenue — fiscal analysis columns used in award evaluation reporting.

Common Use Cases and Queries

Typical scenarios include award letter generation, correspondence tracking, and party data extracts for grants reporting.

  • Retrieve correspondence details for a specific award recipient to populate a letter template:
  • SELECT person_id, party_name, salutation, person_name_address FROM apps.igf_aw_awd_ltr_v WHERE person_id = :p_party_id;
  • Identify parties flagged as unavailable for mailing before generating a batch of letters:
  • SELECT party_id, party_name, do_not_mail_flag FROM apps.igf_aw_awd_ltr_v WHERE do_not_mail_flag = 'Y';
  • Produce an organization directory with classification and fiscal data for award planning:
  • SELECT party_name, category_code, curr_fy_potential_revenue FROM apps.igf_aw_awd_ltr_v WHERE party_type = 'ORGANIZATION';
  • Filter by fiscal analysis year for year-specific award summaries.

Because the view performs the address-formatting call to IGS_CO_GEN_003 at query time, large unfiltered extracts can be resource-intensive; queries should be filtered on party_id or party_type whenever possible.