Search Results igw_person_degrees




Overview
Explore in AI Chat

Overview

The IGW_PERSON_DEGREES table is a core master data object within the Oracle E-Business Suite Grants Proposal (IGW) module. It stores educational background information for individuals (persons) participating in the grants and sponsored-programs lifecycle — principal investigators, co-investigators, proposal team members, reviewers, and other named personnel whose academic credentials must be captured for proposal submission, compliance, and reporting purposes.

Sitting in the IGW schema, the table acts as the authoritative source of degree records that can be associated with proposals and other grant artifacts. From a Data Vault modeling perspective, the mined foreign-key structure suggests a hub-leaning classification. Because the table possesses its own surrogate primary key (PERSON_DEGREE_ID) and is referenced by downstream transactional tables rather than being a pure association or descriptive satellite, it functions as a durable business entity that anchors relationships and descriptive detail. This is a modeling suggestion only; the physical design in EBS follows traditional third-normal-form conventions rather than an explicit Data Vault schema.

Key Information Stored

The table comprises 32 documented columns in the 12.1.1 physical schema. The most significant include:

  • PERSON_DEGREE_ID — the surrogate primary key defined by the unique constraint/index IGW_PERSON_DEGREES_PK. This is the system-generated identifier and does not represent a user-visible business key.
  • PERSON_ID — the link to the underlying person (party) record, identifying whose degree this is.
  • PARTY_ID — the associated party identifier, aligning the record with the TCA/HZ party model.
  • DEGREE_TYPE_CODE — the classification of the degree (for example, associate, bachelor, master, doctorate).
  • DEGREE — the actual awarded degree, such as the discipline or title conferred.
  • DEGREE_SEQUENCE — an ordering value to distinguish multiple degrees held by the same person.
  • GRADUATION_DATE — the date the degree was conferred.
  • FIELD_OF_STUDY and SPECIALIZATION — the academic discipline and any narrower specialization.
  • SCHOOL_NAME — the name of the granting institution.
  • RECORD_VERSION_NUMBER — used for optimistic concurrency control during updates.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) column set, enabling client-specific extension data.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns tracking insert and update provenance.

The documented unique index IGW_PERSON_DEGREES covers only the surrogate PERSON_DEGREE_ID; no alternate business-key unique constraint on the natural attributes is documented, so PERSON_DEGREE_ID remains the sole guaranteed identifier.

Common Use Cases and Queries

Typical usage centers on credential reporting and proposal preparation. Common queries include retrieving all degrees for a given person, aggregating institution data for compliance reports, and joining degree records to proposal personnel.

  • Listing a person's academic history: SELECT DEGREE, FIELD_OF_STUDY, SCHOOL_NAME, GRADUATION_DATE FROM IGW_PERSON_DEGREES WHERE PERSON_ID = :person_id ORDER BY DEGREE_SEQUENCE;
  • Counting degrees by type across a population for analytics: SELECT DEGREE_TYPE_CODE, COUNT(*) FROM IGW_PERSON_DEGREES GROUP BY DEGREE_TYPE_CODE;
  • Linking degrees to proposal personnel through IGW_PROP_PERSON_DEGREES to verify reviewer qualifications and detect conflicts of interest.
  • Reporting on granting institutions for sponsored-research summaries and demographic dashboards.

Because the DFF columns are present, reports frequently extract ATTRIBUTE segments alongside the core descriptive fields.

Related Objects

The most significant dependent object is documented directly through the foreign-key relationship:

  • IGW_PROP_PERSON_DEGREES — references IGW_PERSON_DEGREES through the column PERSON_DEGREE_ID. This association table ties individual degree records to specific proposals, representing the primary downstream consumer of this hub.
  • Person / Party source tables — PERSON_ID and PARTY_ID imply integration with the Oracle person and trading-community (HZ) party model, which supplies the underlying individual and organization identities.
  • Grants proposal objects within the IGW module (proposal headers and personnel) that ultimately surface degree data through the PROP_PERSON_DEGREES link.

Together, these relationships confirm IGW_PERSON_DEGREES as a foundational credential hub whose records are selectively attached to grant proposals via IGW_PROP_PERSON_DEGREES.