PER_ACTION_OCCURRENCES

HCMUsed in 0 subject areas26 reporting columnsBICC incremental-ready

Person / Worker (PER).

Likely primary key: ACTION_OCCURRENCE_ID (inferred from Oracle naming conventions — verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE

Columns

Column	Key	In reports	Description (inferred)
ACTION_DATE		●	Action date.
ACTION_ID		●	Identifier for the action.
ACTION_OCCURRENCE_ID	PK?	●	Identifier for the action occurrence.
ACTION_REASON_ID		●	Identifier for the action reason.
ACTION_TYPE_CODE		●	Code identifying the action type.
BUSINESS_GROUP_ID		●	Identifier for the business group.
CREATED_BY		●	User who created the row.
CREATION_DATE		●	Date and time the row was created.
ENTITY_ID		●	Identifier for the entity.
ENTITY_TYPE		●	Type of entity.
FREEZE_START_DATE		●	Freeze start date.
FREEZE_UNTIL_DATE		●	Freeze until date.
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.
LEGAL_ENTITY_ID		●	Identifier of the legal entity.
OBJECT_VERSION_NUMBER		●	Optimistic-locking version number, incremented on each update.
PARENT_ENTITY_KEY_ID		●	Identifier for the parent entity key.
PARENT_ENTITY_TYPE		●	Type of parent entity.
PROPOSED_ACTION_ID		●	Identifier for the proposed action.
PROPOSED_ACTION_TYPE		●	Type of proposed action.
PROPOSED_REASON_ID		●	Identifier for the proposed reason.
PROPOSED_START_DATE		●	Proposed start date.
PROPOSED_WORKER_TYPE		●	Type of proposed worker.
REF_ACTION_OCCURRENCE_ID		●	Identifier for the reference action occurrence.
SUBMITTED_BY		●	Submitted by.

Used by reports

No cataloged report reads from this table yet — it's part of the broader Fusion dictionary.

Subject areas

Need the extract + dbt staging for PER_ACTION_OCCURRENCES?

We ship parameterized SQL, BICC config, and dbt models you own.

Talk to us