Search Results person_edi_code

Overview

IGW_PRPO_PROP_PERSONS_V is an Oracle EBS business intelligence system view owned by the APPS schema, registered in FND Design Data as IGW.IGW_PRPO_PROP_PERSONS_V. Its documented purpose is to expose biographical information for personnel associated with proposals, including name, social security number, gender, and date of birth, for use in generating flat files for Electronic Data Interchange (EDI). The view is part of the IGW (Grants/Proposal) module lineage and is status VALID in both Oracle EBS 12.1.1 and 12.2.2. Because it is a reporting-oriented view rather than a transactional entity, it consolidates person, party, address, and proposal-role attributes into a single denormalized projection suitable for extraction. The user-searched column WORK_FAX is present in this projection as VARCHAR2(4000), representing the work facsimile number for the associated person, and is commonly used when proposal submissions require a contact fax channel.

Underlying Base Objects

The documented dependency list identifies the view as referencing APPS.FND_LOOKUP_VALUES and HR_GENERAL. FND_LOOKUP_VALUES supplies decoded lookup meanings (for example, code-to-meaning translation for role, sex, citizenship, race, key person, and EDI code values), while HR_GENERAL is a standard HRMS-based source for person biographical and legislative attributes such as date of birth, sex, and national identifiers. The view joins these to proposal-person relationships using PROPOSAL_ID, PERSON_ID, and PARTY_ID as the principal correlation keys. No additional base objects are documented in the ETRM metadata, so downstream dependencies such as address and phone/fax derivations should be validated against the actual view DDL in the target instance before relying on them for custom development.

Key Columns

• PROPOSAL_ID, PERSON_ID, PARTY_ID — correlation identifiers linking the person record to the proposal and TCA party.
• FIRST_NAME, MIDDLE_NAME, LAST_NAME, FULL_NAME, PREFIX, SUFFIX — name components and the concatenated full name.
• TITLE, PROPOSAL_ROLE, JOB_NAME, PERSON_SEQUENCE, PERCENT_EFFORT — proposal participation and effort attributes.
• SEX, DATE_OF_BIRTH, SSN, PERSON_GOVT_ID, CITIZENSHIP, RACE — biographical and legislative attributes sourced primarily through HR_GENERAL.
• KEY_PERSON_FLAG, PERSON_EDI_CODE — indicators used when formatting EDI flat-file output.
• ADDRESS_LINE1/2/3, TOWN_OR_CITY, COUNTY, STATE, POSTAL_CODE, COUNTRY — mailing address components.
• WORK_PHONE, WORK_FAX, EMAIL_ADDRESS — contact channels; WORK_FAX and WORK_PHONE are VARCHAR2(4000), reflecting the flexible concatenation typical of phone/fax derivations from HR or TCA structures.

Common Use Cases and Queries

Typical applications include EDI flat-file generation for proposal personnel, sponsor-facing personnel rosters, and data-quality audits of biographical completeness. The following query retrieves proposal personnel with fax contact details:

• SELECT PROPOSAL_ID, PERSON_ID, FULL_NAME, PROPOSAL_ROLE, WORK_PHONE, WORK_FAX, EMAIL_ADDRESS FROM APPS.IGW_PRPO_PROP_PERSONS_V WHERE PROPOSAL_ID = :p_proposal_id;
• SELECT PERSON_ID, FULL_NAME, WORK_FAX FROM APPS.IGW_PRPO_PROP_PERSONS_V WHERE WORK_FAX IS NOT NULL AND KEY_PERSON_FLAG = 'Y';

Because the view is APPS-owned and status VALID, it is safe for read-only reporting; no DML should be issued against it. Integrations extracting WORK_FAX should be aware of the 4000-character datatype and possible concatenated formatting, applying appropriate trimming and normalization before file output.