Results for “record_version_number”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
IGW_STUDY_TITLES is a table within the Oracle E-Business Suite IGW (Grants Proposal) module, which is documented as obsolete in ETRM release 12.1.1 and 12.2.2. The table stores information on proposal titles, functioning as a descriptive repository for the titles assigned to grant proposals and related study or protocol records. Within the IGW schema, the table serves as a supporting detail structure that enriches proposal header records with human-readable title text and associated enrollment and protocol attributes.
The ETRM documentation explicitly states that IGW_STUDY_TITLES is not implemented in the reference database, which is consistent with its obsolete product classification. Consequently, the table should be treated as a historical schema artifact rather than an active transactional object in current EBS implementations. From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure is satellite-leaning. This suggests that IGW_STUDY_TITLES is best modeled as a satellite attached to the IGW_PROPOSALS_ALL hub, carrying descriptive and potentially volatile attributes such as title, enrollment status, and protocol number.
Key Information Stored
The table contains six documented columns. The surrogate primary key is STUDY_TITLE_ID, which is enforced by the IGW_STUDY_TITLES_PK constraint and is also the sole unique index candidate (IGW_STUDY_TITLES_U1). While this column uniquely identifies each title record, it is a system-generated identifier rather than a natural business key.
- STUDY_TITLE_ID — surrogate primary key uniquely identifying each study title record.
- STUDY_TITLE — the descriptive title text associated with the proposal or study.
- PROPOSAL_ID — foreign key to IGW_PROPOSALS_ALL, linking the title to its parent proposal.
- RECORD_VERSION_NUMBER — optimistic locking or versioning column used to detect concurrent updates.
- ENROLLMENT_STATUS — status indicator describing enrollment state associated with the study title.
- PROTOCOL_NUMBER — protocol identifier associated with the study or title record.
The foreign key relationship indicates that title records are subordinate to a single proposal, while IGW_SUBJECT_INFORMATION references STUDY_TITLE_ID, establishing the title as a parent for subject information rows.
Common Use Cases and Queries
Although the object is obsolete, historical reporting and data migration exercises may still require queries against IGW_STUDY_TITLES. A typical retrieval joins titles to their parent proposal:
SELECT t.STUDY_TITLE_ID, t.STUDY_TITLE, t.PROTOCOL_NUMBER, t.ENROLLMENT_STATUS
FROM IGW_STUDY_TITLES t, IGW_PROPOSALS_ALL p
WHERE t.PROPOSAL_ID = p.PROPOSAL_ID;
A second common pattern resolves the reverse relationship to subject information:
SELECT t.STUDY_TITLE, s.SUBJECT_ID
FROM IGW_STUDY_TITLES t, IGW_SUBJECT_INFORMATION s
WHERE s.STUDY_TITLE_ID = t.STUDY_TITLE_ID;
Reporting use cases include auditing proposal title inventories, reconciling enrollment status values against protocol numbers, and analyzing record version histories to detect repeated updates. Because the table is not implemented in current databases, these queries primarily support legacy data extraction, archival conversion, and upgrade impact assessments from older IGW installations.
Related Objects
The most significant related objects are those connected through the documented foreign key relationships and the IGW module's core proposal structures.
- IGW_PROPOSALS_ALL — parent table referenced by IGW_STUDY_TITLES.PROPOSAL_ID; holds proposal header information.
- IGW_SUBJECT_INFORMATION — child table referencing IGW_STUDY_TITLES.STUDY_TITLE_ID through the STUDY_TITLE_ID column.
- IGW_STUDY_TITLES_PK — the primary key constraint enforcing uniqueness of STUDY_TITLE_ID.
- IGW_STUDY_TITLES_U1 — the unique index on STUDY_TITLE_ID, serving as the business-key candidate.
- IGW_PROPOSALS_ALL primary key — the parent-side key supporting the PROPOSAL_ID join.
Together these objects define the proposal-to-title-to-subject lineage within the obsolete IGW Grants Proposal schema.
-
Information on proposal titles
-
PA_DELIVERABLES_TASKS_V selects all tasks and the deliverables associated to it.
APPS.PA_DELIVERABLES_TASKS_V·↳ PA_PROJ_ELEMENTS·↳ PA_PROJ_ELEMENT_VERSIONS·Explore PA module →
-
Table: PA_DISTRIBUTION_LISTS 12.2.2
The table PA_DISTRIBUTION_ LISTS consists of the name and description of the lists.
-
Information about a person's degrees
-
Table: PA_OBJECT_REGIONS 12.1.1
This table identifies replacement regions for placeholder regions. Replacement regions are associated with an object and object type.
-
Contract document approval hierarchy
-
Customer representatives who are involved in projects
-
This table stores all the comments in the action log. A comment can be a requestor, closure or progress comment on an action, or unsolicited comment to the control item. For each action, there will be only one requestor comment and one cl
-
Table to store information about the association of project parties and assignments to project subteams.
-
Customer representatives who are involved in projects
-
Contract document approval hierarchy
-
View: OKE_APPROVAL_STEPS_V 12.2.2
APPS.OKE_APPROVAL_STEPS_V·↳ OKE_APPROVAL_STEPS·↳ PA_PROJECT_ROLE_TYPES·Explore OKE module →
-
PA_ROLE_LIST_MEMBERS stores the information about the roles which make up the role list
-
Non-standard job billing titles negotiated for specific projects and tasks
-
Information about a person's biosketch
-
The table PA_DIST_ LIST_ITEMS defines list of recipients who can access a particular object. The recipient can be a role or project team member or an email address
-
Information about the roles assigned to users for proposal access
-
View: PA_STATUS_LIST_ITEMS_V 12.1.1
This view provides the attribute values from all comments from the table pa_status_list_items.
APPS.PA_STATUS_LIST_ITEMS_V·↳ PA_STATUS_LIST_ITEMS·Explore PA module →
-
PA_LIFECYCLE_USAGES stores information about the usuage types of the existing lifecycle.
-
Table: PA_DISTRIBUTION_LISTS 12.1.1
The table PA_DISTRIBUTION_ LISTS consists of the name and description of the lists.
-
This table stores the statuses in a status list.
-
Non-standard employee job assignments and/or billing titles negotiated for specific projects and tasks
-
PA_PRODUCT_FUNCTIONS stores the functions defined for each product in the Oracle Projects suite.
-
Information about a person's proposal biosketch
-
This table stores the thresholds of exception notification rule.
-
Overhead and employee benefit amounts for a budget line
-
This table stores report types that enable users to create multiple reports for a project.
-
View: PA_PERIOD_MASKS_VL 12.2.2
MLS View for pa_period_masks_b and pa_period_masks_tl.
APPS.PA_PERIOD_MASKS_VL·↳ PA_PERIOD_MASKS_B·↳ PA_PERIOD_MASKS_TL·Explore PA module →
-
PA_ROLE_LIST_MEMBERS stores the information about the roles which make up the role list
-
Keywords used in preparing proposals
-
Table: PA_OBJECT_REGIONS 12.2.2
This table identifies replacement regions for placeholder regions. Replacement regions are associated with an object and object type.
-
Contract document approval hierarchy steps
-
View: PA_PROJECT_RETENTION_V 12.2.2
Stores retention summary balances
APPS.PA_PROJECT_RETENTION_V·↳ PA_CUSTOMERS_V·↳ PA_LOOKUPS·↳ PA_PROJECT_CUSTOMERS·Explore PA module →
-
PA_DELIVERABLES_TASKS_V selects all tasks and the deliverables associated to it.
APPS.PA_DELIVERABLES_TASKS_V·↳ PA_PROJ_ELEMENTS·↳ PA_PROJ_ELEMENT_VERSIONS·Explore PA module →
-
Contract document approval hierarchy steps
-
The table PA_DIST_ LIST_DENORM holds the materialized list of people with their access details for a given distribution list. The records for a given list get populated from the pa_distribution_lists table whenever the list_id did not exis
-
Intermediate table used to store the mappings between resource lists and resource formats.
-
PA_PRODUCT_FUNCTIONS stores the functions defined for each product in the Oracle Projects suite.
-
View: PA_STATUS_LIST_ITEMS_V 12.2.2
This view provides the attribute values from all comments from the table pa_status_list_items.
APPS.PA_STATUS_LIST_ITEMS_V·↳ PA_STATUS_LIST_ITEMS·Explore PA module →
-
This table stores the integration between change document types and financial plan types that is done as part of setup.
-
Stores tasks which have been excluded for financial planning purposes.
-
Quick Entry fields for project templates
-
Information on proposal subjects
-
View: OKE_APPROVAL_STEPS_V 12.1.1
APPS.OKE_APPROVAL_STEPS_V·↳ OKE_APPROVAL_STEPS·↳ PA_PROJECT_ROLE_TYPES·Explore OKE module →
-
PA_ROLE_CONTROLS stores the information about the controls defined on roles
-
Navigation options for each project template
-
Navigation options for each project template
-
Multipliers, assigned to projects or tasks, that are applied to raw cost to determine the revenue and/or bill amounts
-
Multipliers, assigned to projects or tasks, that are applied to raw cost to determine the revenue and/or bill amounts
-
This table stores the integration between change document types and financial plan types that is done as part of setup.