Search Results subject_ethnicity_code

Overview

IGW_SUBJECT_INFORMATION is a table within the Oracle E-Business Suite IGW – Grants Proposal product family. Its documented description is simply "Information on proposal subjects," indicating that it stores demographic and category attributes recorded against subjects attached to a grant or proposal study. In the ETRM 12.1.1 documentation, IGW is flagged as Obsolete, and the table is noted as Not implemented in this database. This means the object survives in the data dictionary and in reference documentation but is not actively instantiated in a standard 12.1.1 or 12.2.2 installation. It remains relevant for upgrade analysis, legacy data migration, and archival reporting from prior Grants Proposal deployments.

From a Data Vault modeling perspective, the metadata's heuristic classification lists this object as satellite-leaning. The presence of descriptive measures such as NO_OF_SUBJECTS alongside a composite primary key positioned within a study-title grouping supports treating it as a satellite keyed to a parent study hub rather than as an independent hub or link.

Key Information Stored

The physical schema documents twelve columns. The most important are:

• SUBJECT_INFORMATION_ID – surrogate identifier unique to each record row.
• STUDY_TITLE_ID – foreign key linking the subject record to IGW_STUDY_TITLES; the principal join column.
• SUBJECT_TYPE_CODE – classifies the nature of the subject being described.
• SUBJECT_RACE_CODE – race category captured for the subject, and a business-key component.
• SUBJECT_ETHNICITY_CODE – ethnicity category; the column referenced in the user's search and part of the unique business key.
• NO_OF_SUBJECTS – aggregate count of subjects falling into the given race, ethnicity, and type combination.
• RECORD_VERSION_NUMBER – optimistic locking / concurrency control column.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – standard EBS audit (WHO) columns.

The declared primary key IGW_SUBJECT_INFORMATION_PK is composite, spanning SUBJECT_RACE_CODE, SUBJECT_ETHNICITY_CODE, STUDY_TITLE_ID, and SUBJECT_TYPE_CODE. The unique index IGW_SUBJECT_INFORMATION_U1 covers the same four business columns, confirming that the surrogate SUBJECT_INFORMATION_ID is a non-key attribute while the business key is the demographic-plus-study combination.

Common Use Cases and Queries

Typical reporting extracts summarize subject demographics per study. A representative query joins the study title to aggregate subject counts:

• SELECT s.study_title_id, i.subject_race_code, i.subject_ethnicity_code, SUM(i.no_of_subjects) FROM igw_subject_information i, igw_study_titles s WHERE i.study_title_id = s.study_title_id GROUP BY s.study_title_id, i.subject_race_code, i.subject_ethnicity_code;
• Ethnicity-focused lookups filter directly on SUBJECT_ETHNICITY_CODE to produce demographic breakdowns for compliance and grant reporting.
• Data migration or archival queries select all twelve columns ordered by STUDY_TITLE_ID to reconstruct legacy Grants Proposal data.

Because the table is obsolete and not implemented in current instances, most modern 12.1.1 / 12.2.2 work with this object is investigative: confirming absence, validating historical extracts, or mapping legacy columns to successor structures.

Related Objects

The documented foreign key relationship governs dependency:

• IGW_STUDY_TITLES – parent table referenced via IGW_SUBJECT_INFORMATION.STUDY_TITLE_ID = IGW_STUDY_TITLES.STUDY_TITLE_ID; the most significant related object.
• IGW_SUBJECT_INFORMATION_PK and IGW_SUBJECT_INFORMATION_U1 – the primary-key constraint and unique index that enforce uniqueness across the four business columns.
• Sibling IGW Grants Proposal tables sharing the STUDY_TITLE_ID foreign key, which collectively form the study-centric data model around which subject information is organized.

No additional views or public APIs are documented for this object in the supplied metadata; integration is therefore limited to direct table access within the obsolete IGW schema.