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

PER_USERS

HCMUsed in 27 subject areas22 reporting columnsBICC incremental-ready

Person / Worker (PER).

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

Columns

ColumnKeyIn reportsDescription (inferred)
ACTIVE_FLAGIndicator (Y/N) for the active.
BUSINESS_GROUP_IDIdentifier for the business group.
CREATED_BYUser who created the row.
CREATION_DATEDate and time the row was created.
CREDENTIALS_EMAIL_SENTCredentials email sent.
END_DATEEnd date.
EXTERNAL_IDIdentifier for the external.
HR_TERMINATEDHr terminated.
LAST_UPDATED_BYUser who last updated the row.
LAST_UPDATE_DATEINCRDate and time the row was last updated (the incremental-extract key).
LAST_UPDATE_LOGINSession login of the user who last updated the row.
MULTITENANCY_USERNAMEMultitenancy username.
OBJECT_VERSION_NUMBEROptimistic-locking version number, incremented on each update.
PARTY_IDIdentifier for the party.
PERSON_IDIdentifier for the person.
START_DATEStart date.
SUSPENDEDSuspended.
USERNAMEUsername.
USER_DATA_CHECKSUMUser data checksum.
USER_DISTINGUISHED_NAMEName of the user distinguished.
USER_GUIDUser guid.
USER_IDPK?Identifier for the user.

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_USERS.

Where this surfaces in OTBI

The OTBI subject areas that expose this table. You can't join across them in OTBI, the owned conformed model joins them on shared keys.

Need the extract + dbt staging for PER_USERS?
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