Search Results degree_type_code

Overview

APPS.IGW_PROP_PERSON_DEGREES_V is a synonym-backed database view in the Oracle E-Business Suite Applications (APPS) schema, registered in the Application Object Library under FND Design Data identifier IGW.IGW_PROP_PERSON_DEGREES_V. The IGW product prefix identifies it as belonging to the Oracle Grants Management (formerly Oracle Grants Proposal / OGM) family of objects. In EBS 12.1.1 and 12.2.2 this view presents the biographical degree records that a principal investigator, key person, or other named participant has associated with a grant proposal. It is a reporting and integration surface rather than a transactional entity: the underlying data is maintained through the proposal-person entry forms, while the view supplies a flattened, denormalized read model that joins person-level degree history to the proposal-specific degree assignments.

Underlying Base Objects

According to the documented dependency information, APPS.IGW_PROP_PERSON_DEGREES_V is defined over two base objects, both owned by APPS:

• IGW_PERSON_DEGREES — the person-level degree repository, holding the authoritative biographical degree information (degree type, degree name, graduation date, institution, field of study, and specialization) for a person identified by PERSON_ID.
• IGW_PROP_PERSON_DEGREES — the proposal-level association table that links a proposal (PROPOSAL_ID) to a person (PERSON_ID) and carries proposal-specific sequencing and display attributes.

The view is not referenced by any other database object, so it functions as a terminal read layer used directly by forms, concurrent programs, reports, and external integrations. Its status is VALID. Because it is a view, no direct DML should be issued against it; inserts and updates must be performed against the underlying base tables through the supported Grants Management APIs or forms.

Key Columns

• ROW_ID — the ROWID of the driving row, useful for identifying a specific record during diagnostics.
• PROPOSAL_ID — foreign key to the proposal with which the person degree record is associated.
• PERSON_ID — the person (party) for whom the degree is recorded.
• PERSON_DEGREE_ID — unique identifier of the degree record.
• DEGREE_TYPE_CODE — the coded classification of the degree (for example, the code distinguishing a doctorate, master's, or bachelor's award). This is the column most frequently searched by report authors and integration developers.
• DEGREE — the descriptive name of the degree awarded.
• GRADUATION_DATE — the date the degree was conferred.
• FIELD_OF_STUDY and SPECIALIZATION — the academic discipline and any narrower specialization.
• SCHOOL_NAME — the awarding institution.
• PERSON_DEGREE_SEQUENCE and PROP_DEGREE_SEQUENCE — ordering attributes that establish display sequence for the person's degrees and for the proposal's presentation of them.
• SHOW_FLAG — a display control indicating whether the degree should be presented on the proposal output.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide standard EBS WHO-column auditing.

Common Use Cases and Queries

Typical uses include proposal biographical sketches and "Other Support" reporting, sponsor-format CV extracts, data validation of degree coding, and integrations that extract proposal personnel credentials. The following query lists all degrees for a given proposal, ordered for presentation:

SELECT proposal_id, person_id, degree_type_code, degree, graduation_date, school_name, field_of_study FROM apps.igw_prop_person_degrees_v WHERE proposal_id = :p_proposal_id ORDER BY prop_degree_sequence, person_degree_sequence;

To locate every record of a particular credential type across proposals:

SELECT proposal_id, person_id, degree, school_name, graduation_date FROM apps.igw_prop_person_degrees_v WHERE degree_type_code = :p_degree_type_code;

Because the view is read-only and its dependencies are confined to the two Grants Management base tables, it can be queried safely in custom reports and extracts without side effects. Access should be granted through the standard APPS schema responsibilities, and any requirement to add or change degree data must be routed through the supported Grants Management maintenance screens rather than direct SQL.