Results for “igw_roles_u1”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGW.IGW_ROLES is a seed-data table within the Oracle E-Business Suite (EBS) IGW schema, which supports Oracle Grants Management and the associated proposal and project lifecycle. In the context of EBS 12.1.1 and 12.2.2, the table stores the master definition of proposal roles — the functional designations assigned to individuals participating in a grant proposal or research project. Each row represents a single role and carries the effective dating that governs when that role is considered active.

The table is classified by the ETRM metadata as hub-leaning under a heuristic Data Vault model. This classification suggests treating IGW_ROLES as a hub entity, with ROLE_ID as the durable business key at its center. Its descriptive attributes, such as effective dates and the seeded flag, would naturally be modelled as satellite columns attached to that hub. This mirrors how the table behaves in the operational schema: a central, relatively narrow set of role identities referenced by multiple dependent objects.

The table resides in the APPS_TS_SEED tablespace, which is consistent with its role as a seeded reference table populated during installation and patching rather than through routine transactional use.

Key Information Stored

The table contains nine documented columns. The most significant are:

• ROLE_ID (NUMBER, 10) — The surrogate primary key defined by IGW_ROLES_PK and additionally protected by the unique index IGW_ROLES_U1. It is the identifier referenced by all dependent tables.
• START_DATE_ACTIVE (DATE) — The first effective date on which the role becomes valid for assignment.
• END_DATE_ACTIVE (DATE) — The last effective date of the role. Together with START_DATE_ACTIVE, these two columns determine which roles are active at any point in time, forming the temporal business rule behind role availability.
• SEEDED_FLAG (VARCHAR2) — Indicates whether the row was delivered by Oracle seeding (Y) or created by a user (NULL). This distinguishes out-of-the-box roles from customer-defined extensions.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — The five standard Who columns that audit row creation and modification, including the responsible user and login.

ROLE_ID is the surrogate primary key. No separate natural business key is documented; IGW_ROLES_U1 is a unique index on the same column, so the surrogate and the unique candidate coincide.

Common Use Cases and Queries

The primary use case is retrieving the set of roles assignable to proposal personnel and determining which are currently active. Effective-dating logic is applied by comparing SYSDATE against the start and end dates. A typical pattern is:

• Selecting active roles for a proposal assignment screen: SELECT ROLE_ID, START_DATE_ACTIVE, END_DATE_ACTIVE FROM IGW.IGW_ROLES WHERE SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE);
• Separating Oracle-delivered roles from user-defined roles using SEEDED_FLAG to support upgrade and impact analysis.
• Auditing role maintenance through the standard Who columns to identify who last changed a role definition and when.
• Feeding reporting extracts that join role identifiers to user-role assignments for research administration dashboards.

Related Objects

IGW_ROLES is referenced by three dependent tables through the ROLE_ID foreign key, and is surfaced to applications via the APPS synonym:

• IGW_PROP_USER_ROLES — joins on ROLE_ID to associate specific users with proposal roles.
• IGW_ROLES_TL — the translation table, joined on ROLE_ID, supplying language-specific role names and descriptions.
• IGW_ROLE_RIGHTS — joins on ROLE_ID to define the privileges or access rights granted to each role.
• APPS.IGW_ROLES — the application-facing synonym through which Forms, concurrent programs, and reports normally query the table.

These dependencies confirm IGW_ROLES as the central role definition object within the IGW proposal model.