Results for “igw_roles”

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

Overview

The IGW_ROLES table is a foundational reference object within the IGW (Grants Proposal) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the master definitions of roles that govern user access and authorization behavior throughout the Grants Proposal application. Each row represents a single role that can be assigned to users, referenced by role-rights mappings, and translated across languages. Because IGW_ROLES acts as the central registry from which dependent tables draw their ROLE_ID values, it functions as the anchor object for role-based security in the module.

From a Data Vault modeling perspective, the metadata classifies this table as hub-leaning. This is a heuristic classification rather than a prescribed design. It reflects the fact that IGW_ROLES carries a stable business key (ROLE_ID) and serves as the parent for multiple child relationships, which is characteristic of a hub entity in a dimensional or Data Vault construct. The table is owned by the IGW schema and holds a status of VALID in the documented ETRM release.

Key Information Stored

The table contains nine documented columns in the 12.1.1 physical schema. The most significant are summarized below.

• ROLE_ID — The single-column primary key, defined by the unique index IGW_ROLES_U1 and constraint IGW_ROLES_PK. It is the surrogate identifier that all foreign key relationships reference. It also qualifies as the business-key candidate, since no additional unique index is documented.
• START_DATE_ACTIVE — The date on which the role becomes effective and available for assignment.
• END_DATE_ACTIVE — The date on which the role is deactivated. Roles with a null end date are generally treated as open-ended.
• SEEDED_FLAG — Indicates whether the role is a system-seeded (predefined, Oracle-delivered) role or a user-defined custom role. This distinction is important when assessing which roles may be safely modified or deleted.
• LAST_UPDATE_DATE / LAST_UPDATED_BY — Standard audit columns capturing when and by whom the role row was last changed.
• CREATION_DATE / CREATED_BY — Audit columns recording the original insert of the role record.
• LAST_UPDATE_LOGIN — The login identifier associated with the most recent update, used for concurrent-program and user-session auditing.

Descriptive and translatable name text is not held on this base table; it resides in the IGW_ROLES_TL translation table, joined by ROLE_ID.

Common Use Cases and Queries

Typical usage centers on role administration, access audits, and data extraction for security reporting. A common pattern lists currently active, non-expired roles:

• Active role listing: SELECT ROLE_ID, SEEDED_FLAG FROM IGW_ROLES WHERE (END_DATE_ACTIVE IS NULL OR END_DATE_ACTIVE > SYSDATE) AND (START_DATE_ACTIVE IS NULL OR START_DATE_ACTIVE <= SYSDATE).
• Seeded vs. custom reporting: aggregate counts grouped by SEEDED_FLAG to distinguish Oracle-delivered roles from client-defined ones.
• Audit tracing: filter by LAST_UPDATED_BY or LAST_UPDATE_DATE to identify recent security configuration changes.
• Role assignment reporting: join IGW_PROP_USER_ROLES on ROLE_ID to enumerate which users hold which roles.
• Permission mapping: join IGW_ROLE_RIGHTS on ROLE_ID to determine the rights granted to each role.
• Multilingual reporting: join IGW_ROLES_TL on ROLE_ID to obtain translated role names for locale-specific output.

Related Objects

IGW_ROLES is referenced by three documented child tables, each linked through the ROLE_ID column.

• IGW_PROP_USER_ROLES — Maps users to roles; joins on IGW_PROP_USER_ROLES.ROLE_ID = IGW_ROLES.ROLE_ID.
• IGW_ROLES_TL — Stores translated role names; joins on IGW_ROLES_TL.ROLE_ID = IGW_ROLES.ROLE_ID.
• IGW_ROLE_RIGHTS — Associates roles with functional rights; joins on IGW_ROLE_RIGHTS.ROLE_ID = IGW_ROLES.ROLE_ID.

Together these three dependents form the complete role-security footprint: identity assignment, localization, and privilege definition all resolve back to the ROLE_ID hub defined in IGW_ROLES.