Search Results study_title_id

Overview

IGW.IGW_STUDY_TITLES is a transaction data table within the Oracle E-Business Suite Grants and Proposal Management (IGW) schema. It stores the titles of studies conducted on human subjects, typically in the context of research proposals, grants, or institutional review board (IRB) related workflows. Each row captures a single study title associated with a proposal, allowing a one-to-many relationship between a proposal and the study titles it contains. This supports compliance-driven research administration where human subject involvement must be documented and tracked per proposal.

The table resides in the APPS_TS_TX_DATA tablespace and is registered in FND Design Data as IGW.IGW_STUDY_TITLES, indicating it is a seeded, application-managed object. Its status is VALID. Based on the foreign key topology — IGW_STUDY_TITLES references IGW_PROPOSALS_ALL via PROPOSAL_ID, while IGW_SUBJECT_INFORMATION references IGW_STUDY_TITLES via STUDY_TITLE_ID — the heuristic Data Vault classification is satellite-leaning. It acts as a descriptive detail table hanging off the proposal hub, capturing attributes about each study title rather than defining an independent entity on its own.

Key Information Stored

The table contains six documented columns. The surrogate primary key is STUDY_TITLE_ID (NUMBER(15)), which is also enforced by the unique index IGW_STUDY_TITLES_U1 on APPS_TS_TX_IDX. This identifier is the value most commonly searched by users querying for "study_title_id."

• STUDY_TITLE_ID — Surrogate primary key and unique business-key candidate; identifies each study title record.
• STUDY_TITLE — VARCHAR2(240); the descriptive name/title of the study conducted on a particular subject.
• PROPOSAL_ID — NUMBER(15); foreign key to IGW_PROPOSALS_ALL, linking the study title to its parent proposal.
• RECORD_VERSION_NUMBER — NUMBER; a locking sequence number supporting optimistic concurrency control during updates.
• ENROLLMENT_STATUS — VARCHAR2(30); indicates whether the study involves targeted or included human subjects, with documented values T (Targeted) and I (Included).
• PROTOCOL_NUMBER — VARCHAR2; the institutional protocol or IRB reference number for the study.

The distinction between the surrogate key and business keys is significant: STUDY_TITLE_ID is system-generated, while STUDY_TITLE and PROTOCOL_NUMBER are the human-readable attributes that practitioners typically use to identify a study.

Common Use Cases and Queries

Typical use cases include researching human subject involvement per proposal, reporting enrollment status distributions, and joining study titles to their proposal details for grant reporting. A frequent pattern is to look up a study title by its identifier:

• Retrieve a study title by ID: SELECT * FROM IGW.IGW_STUDY_TITLES WHERE STUDY_TITLE_ID = :id;
• List all study titles for a proposal: SELECT STUDY_TITLE, PROTOCOL_NUMBER, ENROLLMENT_STATUS FROM IGW.IGW_STUDY_TITLES WHERE PROPOSAL_ID = :proposal_id;
• Report on targeted versus included enrollment: group by ENROLLMENT_STATUS across portfolios.
• Join to IGW_PROPOSALS_ALL on PROPOSAL_ID to surface proposal-level context alongside each study.
• Join to IGW_SUBJECT_INFORMATION on STUDY_TITLE_ID to trace which subjects relate to a given study title.

Related Objects

IGW_STUDY_TITLES participates in a small but meaningful relationship network within the IGW schema:

• IGW_PROPOSALS_ALL — parent object referenced via PROPOSAL_ID; supplies proposal context.
• IGW_SUBJECT_INFORMATION — child table referencing STUDY_TITLE_ID; holds subject-level details tied to each study title.
• APPS.IGW_STUDY_TITLES — the APPS synonym/backing reference exposed for querying in the EBS environment.
• IGW_STUDY_TITLES_U1 — the unique index enforcing uniqueness on STUDY_TITLE_ID.

Together these objects form the proposal-to-study-to-subject chain that underpins human subjects research administration in Oracle EBS Grants Management.