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

Columns

Column	Key	In reports	Description (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.
CREDENTIALS_EMAIL_SENT		●	Credentials email sent.
END_DATE		●	End date.
EXTERNAL_ID		●	Identifier for the external.
HR_TERMINATED		●	Hr terminated.
LAST_UPDATED_BY		●	User who last updated the row.
LAST_UPDATE_DATE	INCR	●	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.
MULTITENANCY_USERNAME		●	Multitenancy username.
OBJECT_VERSION_NUMBER		●	Optimistic-locking version number, incremented on each update.
PARTY_ID		●	Identifier for the party.
PERSON_ID		●	Identifier for the person.
START_DATE		●	Start date.
SUSPENDED		●	Suspended.
USERNAME		●	Username.
USER_DATA_CHECKSUM		●	User data checksum.
USER_DISTINGUISHED_NAME		●	Name of the user distinguished.
USER_GUID		●	User guid.
USER_ID	PK?	●	Identifier for the user.

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

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.