Results for “first_middle_last_name”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGW_SIGNING_OFFICIAL_V is a reporting and integration view belonging to the Oracle E-Business Suite product family IGW – Grants Proposal. The view is documented in the E-Business Suite Technical Reference Manual (ETRM) for releases 12.1.1 and 12.2.2, where the product is flagged as Obsolete. Its purpose is narrow and well defined: it returns the identifying, biographical, address, and contact details of the individual designated as the Signing Official on a given grants proposal record.

The Signing Official is the authorized institutional representative—typically a grants officer, contracts officer, or sponsored-programs administrator—whose name and credentials appear on a submitted proposal. Because sponsored-programs offices routinely need to print, transmit, or audit this information, IGW_SIGNING_OFFICIAL_V serves as a single denormalized source that joins proposal data with the person, assignment, and location records required to produce a complete signing-official block. In that role it functions as a presentation-layer construct: consumers do not need to reconstruct the person/location/contact relationships themselves.

It is important to note that the documentation states the view is not implemented in this database. In practice this means the object may be absent from an instance, or may exist only in environments where the deprecated IGW module was originally installed. Objects referencing it should therefore be validated against each target instance before deployment, particularly during 12.1.1 to 12.2.2 upgrades.

Underlying Base Objects

The view text is defined over four base objects joined together:

• IGW_PROPOSALS_ALL (aliased PA) — the driving table; supplies PROPOSAL_ID, PROPOSAL_NUMBER, SUBMITTING_ORGANIZATION_ID, and the SIGNING_OFFICIAL_ID used as the join key.
• PER_PEOPLE_X (aliased AP) — supplies the person-level attributes: name components, title, prefix, suffix, and email address. The join is an inner join on PA.SIGNING_OFFICIAL_ID = AP.PERSON_ID, so proposals without a valid signing official are excluded.
• PER_ASSIGNMENTS_X (aliased ASG) — joined outer ((+)) on PERSON_ID with PRIMARY_FLAG(+) = 'Y', restricting to the person's primary assignment. This assignment supplies the LOCATION_ID used for the address block.
• HR_LOCATIONS (aliased LOC) — joined outer on LOCATION_ID, supplying the mailing address used for the signing-official correspondence block.

Because PER_ASSIGNMENTS_X and HR_LOCATIONS are outer-joined while PER_PEOPLE_X is inner-joined, the row grain is one row per proposal, provided each proposal resolves to exactly one person. Where a person has multiple primary assignments, duplication is theoretically possible.

Key Columns

The view exposes the following documented columns:

• PROPOSAL_ID, PROPOSAL_NUMBER, ORGANIZATION_ID — identifiers linking the row back to the proposal and its submitting organization.
• PERSON_ID — the signing official's party/person identifier, useful for joins to other HR or proposal objects.
• FULL_NAME, LAST_NAME, FIRST_NAME, MIDDLE_NAME, TITLE, PREFIX, SUFFIX — discrete name and honorific components suitable for formatted output.
• LAST_FIRST_MIDDLE_NAME — a derived concatenation (last name plus first and middle names) for alphabetized listings.
• FIRST_MIDDLE_LAST_NAME — a derived concatenation with suffix appended, for signature-style display.
• JOB_NAME — resolved via IGW_REPORT_PROCESSING.GET_JOB_NAME, giving the official's job title from assignment data.
• ADDRESS_LINE1 through ADDRESS_LINE3, TOWN_OR_CITY, POSTAL_CODE, REGION_1 through REGION_3, COUNTRY — the correspondence address from HR_LOCATIONS.
• WORK_PHONE, WORK_FX — phone and fax retrieved by IGW_REPORT_PROCESSING.GET_PHONE_NUMBER using contacts types 'WF' and 'W1'.
• EMAIL_ADDRESS — the person's electronic mail address from PER_PEOPLE_X.

Common Use Cases and Queries

Typical uses include proposal signature-block generation for printed applications, grants-office contact directories, and cross-checking that each active proposal carries a valid signing official. A straightforward query for a single proposal:

• SELECT proposal_number, first_middle_last_name, job_name, work_phone, email_address FROM igw_signing_official_v WHERE proposal_id = :p_proposal_id;

For a mailing-label extract, select the address and name columns together:

• SELECT full_name, title, address_line1, address_line2, town_or_city, region_1, postal_code, country FROM igw_signing_official_v WHERE organization_id = :p_org_id;

Because the view depends on obsolete IGW tables, replacements should be built directly against the PER and HR base tables when migrating off the deprecated module.