Search Results person_degree_sequence

Overview

The view IGW_PROP_PERSON_DEGREES_V is a reporting and integration object belonging to the IGW – Grants Proposal module, which is flagged as obsolete in Oracle EBS 12.1.1 and 12.2.2. Per the documented ETRM metadata, the object is identified as "10SC Only," meaning its use is restricted to that specific configuration or release context and it is not generally available across standard installations. The view is explicitly annotated as "Not implemented in this database," indicating that in the reference environment from which the metadata was extracted, the object does not physically exist. Its purpose, as reflected by its structure, is to present a consolidated, proposal-scoped list of person degree records — combining proposal-level presentation attributes with the underlying biographical degree data held against the person.

In a functioning deployment where the view exists, its role would be to serve as the read interface for Grants Proposal screens, reports, and integration extracts that need to display or transmit a proposant's academic credentials. Because the object is obsolete and unreferenced in current releases, it should be treated as a legacy artifact rather than a supported extension point.

Underlying Base Objects

The ETRM documentation lists no referenced base objects for this view, and the owner is null. However, the embedded view text defines the dependency explicitly. The view is built over two tables:

• IGW_PROP_PERSON_DEGREES (aliased PPPD) — the proposal-to-person-degree association table, which carries the proposal linkage and ordering/display flags.
• IGW_PERSON_DEGREES (aliased PPD) — the person-level degree record holding the academic detail itself.

The two are joined on PPPD.PERSON_DEGREE_ID = PPD.PERSON_DEGREE_ID, producing one row per proposal-degree association. The ROW_ID column is derived from PPPD.ROWID, exposing the physical row identifier of the association table rather than of the degree table.

Key Columns

The view exposes eighteen columns drawn from both base tables. The most significant are:

• ROW_ID, PROPOSAL_ID, PERSON_DEGREE_ID, SHOW_FLAG, and PROP_DEGREE_SEQUENCE — association-level attributes controlling which degrees appear on a given proposal and in what order.
• GRADUATION_DATE — the date the degree was conferred, sourced from PPD.GRADUATION_DATE. This is the column most commonly targeted by searches, since graduation dates are frequently required for eligibility validation, sponsor reporting, and personnel qualification checks.
• PERSON_ID, DEGREE_TYPE_CODE, DEGREE, PERSON_DEGREE_SEQUENCE, FIELD_OF_STUDY, SPECIALIZATION, and SCHOOL_NAME — the biographical degree detail, sourced from PPD.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — standard audit columns taken from the association table.

Note that two sequence columns coexist: PROP_DEGREE_SEQUENCE (proposal-specific ordering) and PERSON_DEGREE_SEQUENCE (person-specific ordering). Ambiguity between the two is a common source of ordering defects in reporting queries.

Common Use Cases and Queries

Where the view is present, typical usage centers on extracting degree and graduation information for a specific proposal or person. A representative query retrieving credentials for a proposal, sorted by the proposal's own degree order, is:

• SELECT person_id, degree, degree_type_code, school_name, field_of_study, graduation_date FROM igw_prop_person_degrees_v WHERE proposal_id = :proposal_id AND show_flag = 'Y' ORDER BY prop_degree_sequence;

A second common pattern filters on graduation date to determine whether a listed credential meets a sponsor's qualification threshold, or to validate that a degree was conferred on or before a proposal's submission deadline:

• SELECT proposal_id, person_id, degree, graduation_date FROM igw_prop_person_degrees_v WHERE graduation_date <= :cutoff_date ORDER BY proposal_id, person_id;

Because the object is documented as obsolete, "10SC Only," and not implemented in the reference database, queries against it will fail with an ORA-00942 error in most 12.1.1 and 12.2.2 environments. Any requirement formerly served by this view should be met by querying IGW_PERSON_DEGREES joined directly to IGW_PROP_PERSON_DEGREES, or by using the supported successor objects provided by the Grants module in the target release.