Search Results subject_race_code




Overview

IGW_SUBJECT_INFORMATION is a table in the Oracle E-Business Suite product IGW — Grants Proposal, a module that is marked Obsolete in the ETRM documentation. The table stores information on proposal subjects, capturing the demographic composition of study populations by race, ethnicity, subject type, and headcount, tied to a specific study title. In Oracle EBS 12.1.1 and 12.2.2 environments the object remains registered in the data dictionary for reference purposes, but its ETRM record explicitly states "Not implemented in this database." Implementations should therefore treat it as a legacy or dormant structure rather than an active transactional table.

The documented physical schema for ETRM 12.1.1 lists the owner as IGW with 12 columns. The metadata's heuristic Data Vault classification describes the table as satellite-leaning. Interpreted as a modeling suggestion, this indicates the object behaves primarily as a descriptive satellite whose business keys resolve to a parent entity — here IGW_STUDY_TITLES — rather than acting as a hub or a relationship link in its own right.

Key Information Stored

The table's documented key structure distinguishes a declared primary key constraint from the physical surrogate and business-key candidates present in the schema.

The unique index IGW_SUBJECT_INFORMATION_U1 is documented over STUDY_TITLE_ID, SUBJECT_RACE_CODE, SUBJECT_ETHNICITY_CODE, and SUBJECT_TYPE_CODE, making that combination the principal business-key candidate. This set matches the columns of the declared primary key constraint, so the same four columns serve as both the documented PK and the U1 business key.

Common Use Cases and Queries

Because the table is documented as obsolete and not implemented, the primary practical use cases are impact analysis, upgrade assessment, and data-model archaeology rather than operational reporting. Analysts verifying whether demographic subject data exists for a grant proposal typically check for row counts and for any residual data before an upgrade or decommissioning exercise.

A representative query joins the table to its parent study title and restricts by race code, which is the pattern implied by the searched term:

  • SELECT s.study_title_id, s.subject_race_code, s.subject_ethnicity_code, s.subject_type_code, s.no_of_subjects FROM igw_subject_information s WHERE s.subject_race_code = :race_code;
  • Join for descriptive context: SELECT s.*, t.* FROM igw_subject_information s, igw_study_titles t WHERE s.study_title_id = t.study_title_id;
  • Business-key validation query using the U1 column set to detect duplicate population records for a study title.

Related Objects

  • IGW_STUDY_TITLES — the parent table referenced by the foreign key IGW_SUBJECT_INFORMATION.STUDY_TITLE_ID; the principal join path for this object.
  • IGW_SUBJECT_INFORMATION_PK — the documented primary key constraint over SUBJECT_RACE_CODE, SUBJECT_ETHNICITY_CODE, STUDY_TITLE_ID, and SUBJECT_TYPE_CODE.
  • IGW_SUBJECT_INFORMATION_U1 — the unique index over STUDY_TITLE_ID, SUBJECT_RACE_CODE, SUBJECT_ETHNICITY_CODE, and SUBJECT_TYPE_CODE, serving as the business-key candidate.
  • IGW schema objects — the broader IGW Grants Proposal set of tables and views, which collectively form the obsolete module context for this table.

Given the obsolete status and the absence of implementation in the database, no public APIs or dependent views are documented for this table. Any integration or extension work should first confirm object presence in the target instance.