Search Results degree_sequence
Overview
IGW.IGW_PROP_PERSON_DEGREES is a transactional table within the Oracle E-Business Suite IGW (Grants/Proposals) schema. It stores the association between a proposal and the academic degrees held by a person, allowing proposal authors to selectively include, suppress, and sequence degree information that appears in a generated proposal document. Each row represents one person-degree line item belonging to a specific proposal, and the table supports the personnel qualification sections typically required in grant applications and research proposals.
Based on the heuristic Data Vault classification derived from its foreign key structure, this object is satellite-leaning. It functions as a descriptive detail table that hangs off the core proposal and person-degree entities, carrying attributes (SHOW_FLAG, DEGREE_SEQUENCE) that describe the context of the relationship rather than the entities themselves. In a Data Vault model, this table would most naturally be implemented as a satellite attached to a link between proposal and person degree.
Key Information Stored
The table comprises ten documented columns. The composite primary key, IGW_PROP_PERSON_DEGREES_PK, consists of PROPOSAL_ID and PERSON_DEGREE_ID. This same column pair also defines the unique index IGW_PROP_PERSON_DEGREES_U1, making it the business-key candidate for the object. PROPOSAL_ID is the proposal identifier (NUMBER 15) and PERSON_DEGREE_ID is the person degree identifier (NUMBER 10), which is a foreign key to IGW_PERSON_DEGREES.
The two principal business attributes are SHOW_FLAG and DEGREE_SEQUENCE. SHOW_FLAG is a VARCHAR2 flag with possible values Y and N; it determines whether the given degree line is printed in the proposal or excluded. DEGREE_SEQUENCE is a NUMBER that controls the order in which the degrees appear both on screen and in the printed proposal, and it is the attribute most directly relevant to the search term "degree_sequence."
The remaining columns are standard audit and concurrency fields: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN (the standard Who columns that capture row creation and modification metadata), and RECORD_VERSION_NUMBER, a locking sequence number used for optimistic concurrency control.
Common Use Cases and Queries
Typical reporting scenarios include extracting a proposal's personnel degree list in presentation order, auditing which degrees are suppressed from the printed output, and validating that degree ordering is unique per proposal. A representative query retrieves the visible, sequenced degrees for a proposal:
SELECT p.PROPOSAL_ID, p.PERSON_DEGREE_ID, p.DEGREE_SEQUENCE, p.SHOW_FLAGFROM IGW.IGW_PROP_PERSON_DEGREES pWHERE p.PROPOSAL_ID = :proposal_idAND p.SHOW_FLAG = 'Y'ORDER BY p.DEGREE_SEQUENCE;
To identify suppressed rows for audit purposes, filter on SHOW_FLAG = 'N'. To detect ordering conflicts, aggregate on PROPOSAL_ID and DEGREE_SEQUENCE and flag any sequence value appearing more than once. Joins to the parent degree definition (via PERSON_DEGREE_ID) enrich the report with degree titles and institutions. Standard Who columns support change-history and last-modified-by reporting, and RECORD_VERSION_NUMBER supports safe row updates in integration or extension code.
Related Objects
The documented foreign key relationship links PERSON_DEGREE_ID in this table to IGW.IGW_PERSON_DEGREES, the master degree record. The primary and unique keys both span PROPOSAL_ID and PERSON_DEGREE_ID, tying the table to the proposal header entity (typically IGW_PROPOSALS via PROPOSAL_ID). Significant related objects include:
- IGW.IGW_PERSON_DEGREES — parent degree definition, joined on PERSON_DEGREE_ID.
- IGW_PROPOSALS — proposal header, joined on PROPOSAL_ID.
- APPS.IGW_PROP_PERSON_DEGREES — the APPS synonym exposing this table to application code.
- Proposal personnel and qualifications tables in the IGW schema that share the PROPOSAL_ID context.
- Concurrent program and OA Framework page logic that reads DEGREE_SEQUENCE and SHOW_FLAG to render proposal documents.
No database objects are referenced by IGW_PROP_PERSON_DEGREES beyond its documented foreign key; dependency direction is inbound from the APPS synonym and application-layer consumers described above.
-
TABLE: IGW.IGW_PROP_PERSON_DEGREES
12.1.1
owner:IGW, object_type:TABLE, fnd_design_data:IGW.IGW_PROP_PERSON_DEGREES, object_name:IGW_PROP_PERSON_DEGREES, status:VALID,
-
APPS.IGW_PROP_PERSON_DEGREES_PVT SQL Statements
12.1.1
-
TABLE: IGW.IGW_PERSON_DEGREES
12.1.1
owner:IGW, object_type:TABLE, fnd_design_data:IGW.IGW_PERSON_DEGREES, object_name:IGW_PERSON_DEGREES, status:VALID,
-
APPS.IGW_PROP_PERSON_DEGREES_TBH SQL Statements
12.1.1
-
PACKAGE BODY: APPS.IGW_PROP_PERSON_DEGREES_TBH
12.1.1
-
PACKAGE BODY: APPS.IGW_PROP_PERSON_DEGREES_PVT
12.1.1
-
APPS.IGW_PROP_PERSON_DEGREES_TBH dependencies on IGW_PROP_PERSON_DEGREES
12.1.1
-
APPS.IGW_PROP_PERSON_DEGREES_PVT dependencies on IGW_PERSON_BIOSKETCH
12.1.1
-
APPS.IGW_PROP_PERSON_DEGREES_PVT dependencies on IGW_PROP_PERSON_DEGREES
12.1.1
-
eTRM - IGW Tables and Views
12.1.1
description: Information on proposal subjects ,