Results for “work_phone”

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

Overview

The IGW_ADMIN_OFFICIAL_V view belongs to the IGW (Grants Proposal) product family in Oracle E-Business Suite and exposes the person-level details of the Administrative Official associated with a grant or proposal record. Its documented ETRM classification is "Obsolete" under the IGW – Grants Proposal module, and the current database metadata explicitly notes "Not implemented in this database," meaning the object exists in the historical ETRM catalog but is not deployed in a live 12.1.1 or 12.2.2 environment. The view is a reporting-only construct rather than a transactional entity; it joins proposal data from the grants proposal tables to human-resources person data in order to render the administrator's name, title, contact information, and formatted name variants.

Its principal design value lies in the fact that it pre-computes three distinct name display formats—LAST_FIRST_MIDDLE_NAME, FIRST_MIDDLE_LAST_NAME, and the decoded last-name variant—directly in the SELECT list, which is precisely why a lookup for "first_middle_last_name" surfaces this object. It also calls packaged PL/SQL functions in IGW_REPORT_PROCESSING to derive a job name and work phone, making it a convenience layer for grants reporting.

Underlying Base Objects

Although the documented base object list is empty, the view text exposes its true dependencies. It is defined over IGW_PROPOSALS_ALL PA, joined on PA.ADMIN_OFFICIAL_ID = AP.PERSON_ID to PER_PEOPLE_X AP. Assignment data is brought in with an outer join to PER_ASSIGNMENTS_X ASG on AP.PERSON_ID = ASG.PERSON_ID(+), restricted to the primary assignment via ASG.PRIMARY_FLAG(+) = 'Y'. Address information is retrieved through an outer join from the assignment's LOCATION_ID to HR_LOCATIONS LOC. Two PL/SQL functions from IGW_REPORT_PROCESSING are invoked directly: GET_JOB_NAME(AP.PERSON_ID) and GET_PHONE_NUMBER(AP.PERSON_ID, 'WF'|'W1'). This three-table link (proposal → person → assignment → location) is characteristic of EBS grants and HR cross-module reporting views.

Key Columns

• PROPOSAL_ID, PROPOSAL_NUMBER — identifiers of the governing proposal.
• PERSON_ID — the administrative official's HR person key.
• FULL_NAME, LAST_NAME, FIRST_NAME, MIDDLE_NAME — atomic name components.
• FIRST_MIDDLE_LAST_NAME — concatenation of first name, optional middle names, last name, and optional suffix.
• LAST_FIRST_MIDDLE_NAME — actually populated via GET_JOB_NAME, a documented metadata quirk.
• JOB_NAME — derived job title from IGW_REPORT_PROCESSING.GET_JOB_NAME.
• WORK_PHONE, WORK_FAX — derived telephone data from GET_PHONE_NUMBER.
• EMAIL_ADDRESS, TITLE, PREFIX, SUFFIX — display attributes.
• Address columns — ADDRESS_LINE1–3, TOWN_OR_CITY, POSTAL_CODE, REGION_1–3, COUNTRY.

Common Use Cases and Queries

Because the view is obsolete and not deployed, the practical use case is migration or replacement of legacy grants reports. A typical retrieval would be:

• SELECT proposal_number, first_middle_last_name, job_name FROM igw_admin_official_v WHERE proposal_id = :id;
• SELECT person_id, full_name, email_address, work_phone FROM igw_admin_official_v WHERE lead_unit_org_id = :org;

Report developers seeking the modern equivalent should replicate the join chain directly against IGW_PROPOSALS_ALL, PER_PEOPLE_X, and HR_LOCATIONS, since the obsolete view's logic is fully reconstructible from the view text shown in ETRM.