Search Results igw_applicant_org_v




Overview
Explore in AI Chat

Overview

IGW_APPLICANT_ORG_V is a reporting view within the Oracle E-Business Suite Grants Proposal module (IGW), a component of the Oracle Grants Management application family. It presents the organizational and institutional details of the applicant organization that submits a grant proposal, joining proposal header data to organization, location, and grants-specific organization attributes. In Oracle EBS 12.1.1 and 12.2.2, this view is classified as obsolete under the IGW product line, and the ETRM metadata explicitly states that it is not implemented in this database for the documented environment. Consequently, it exists as a reference definition rather than a live, populated runtime object in that instance.

Its role is primarily historical and informational: it exposes a flattened, denormalized projection of applicant organization attributes suitable for reporting, integration extracts, and downstream interfaces that need a single-row representation of the submitting organization per proposal. The inclusion of fax, phone, address, DUNS, CAGE, EIN, and TIN attributes reflects the regulatory and administrative reporting requirements typical of federal grant submissions.

Underlying Base Objects

The view is defined over five referenced objects, combined through outer joins keyed primarily on organization and proposal identifiers:

Joins are outer (the (+) operator) so that proposals lacking complete organization or location data still return rows. Two extension function calls, IGW_EXTENSION_PKG.PERSON_GOVT_ID, derive the government identifiers for the administrative official and signing official.

Key Columns

The view returns proposal identifiers (PROPOSAL_ID, PROPOSAL_NUMBER) and the submitting ORGANIZATION_ID, alongside ORGANIZATION_NAME from HR_ALL_ORGANIZATION_UNITS. Address columns include ADDRESS_LINE_1 through ADDRESS_LINE_3, POSTAL_CODE, TOWN_OR_CITY, COUNTRY, and three region columns.

Of particular relevance to the search term fax_number, the view exposes LO.TELEPHONE_NUMBER_2 under the alias FAX_NUMBER, while LO.TELEPHONE_NUMBER_1 is aliased as PHONE_NUMBER. This aliasing reflects the common convention in HR_LOCATIONS where the second telephone attribute is repurposed as the facsimile number. Additional institutional identifiers include EIN, TIN, DUNS_NUMBER, DUNS4_NUMBER, DODAAC_NUMBER, CAGE_NUMBER, NSF_INSTITUTIONAL_CODE, and various assurance and exemption numbers (HUMAN_ASSURANCE_NUMBER, ANIMAL_ASSURANCE_NUMBER, HUMAN_EXEMPTION_NUMBER). Agreement-related columns such as AGREEMENT_DATE, NEGOTIATING_AGREEMENT_WITH, RATE_ESTABLISHED_WITH, and RATE_ESTABLISHED_DATE describe the negotiated cost rate context.

Common Use Cases and Queries

Typical applications include applicant profile extracts, sponsor reporting, and integration feeds requiring institutional identifiers and contact details. A representative query retrieving contact information, including the fax number, is shown below:

  • SELECT PROPOSAL_NUMBER, ORGANIZATION_NAME, PHONE_NUMBER, FAX_NUMBER, EIN, DUNS_NUMBER FROM IGW_APPLICANT_ORG_V WHERE FAX_NUMBER IS NOT NULL;
  • SELECT ORGANIZATION_NAME, TOWN_OR_CITY, COUNTRY, NSF_INSTITUTIONAL_CODE FROM IGW_APPLICANT_ORG_V WHERE PROPOSAL_ID = :proposal_id;
  • SELECT COUNT(*), ORGANIZATION_NAME FROM IGW_APPLICANT_ORG_V GROUP BY ORGANIZATION_NAME ORDER BY COUNT(*) DESC;

Because the view is documented as obsolete and not implemented in the referenced database, queries should be validated against the target instance before deployment. Where the view is unavailable, equivalent data can be reconstructed directly from IGW_ORG_DETAILS joined to HR_ALL_ORGANIZATION_UNITS and HR_LOCATIONS using the same key relationships.