Analytics Catalog/Data dictionary/PER_USER_ROLES
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Oracle Fusion · Data dictionary

PER_USER_ROLES

HCMUsed in 0 subject areas16 reporting columnsBICC incremental-ready

Person / Worker (PER).

Likely primary key: USER_ROLE_ID (inferred from Oracle naming conventions, verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE
Joins (inferred from key columns): USER_ID → PER_USERS

Columns

ColumnKeyIn reportsDescription (inferred)
ACTIVE_FLAG●Indicator (Y/N) for the active.
BUSINESS_GROUP_ID●Identifier for the business group.
CREATED_BY●User who created the row.
CREATION_DATE●Date and time the row was created.
END_DATE●End date.
LAST_UPDATED_BY●User who last updated the row.
LAST_UPDATE_DATEINCR●Date and time the row was last updated (the incremental-extract key).
LAST_UPDATE_LOGIN●Session login of the user who last updated the row.
METHOD_CODE●Code identifying the method.
OBJECT_VERSION_NUMBER●Optimistic-locking version number, incremented on each update.
ROLE_GUID●Role guid.
ROLE_ID●Identifier for the role.
START_DATE●Start date.
TERMINATED_FLAG●Indicator (Y/N) for the terminated.
USER_ID●Identifier for the user.
USER_ROLE_IDPK?●Identifier for the user role.

8 reports read from this table

Change a column here and these are the reports that move with it, the blast radius for any change to PER_USER_ROLES.

Subject areas

Need the extract + dbt staging for PER_USER_ROLES?
We ship parameterized SQL, BICC config, and dbt models you own.
Talk to us
Problems that run through this table
The report that lies quietly · Approval history vanishes · What the extract does not carry