PER_ABSENCE_ATTENDANCES

HCMUsed in 0 subject areas24 reporting columnsBICC incremental-ready

Person / Worker (PER).

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

Columns

Column	Key	In reports	Description (inferred)
ABSENCE_ATTENDANCE_ID	PK?	●	Identifier for the absence attendance.
ABSENCE_ATTENDANCE_TYPE_ID		●	Identifier for the absence attendance type.
ABSENCE_CASE_ID		●	Identifier for the absence case.
ABS_ATTENDANCE_REASON_ID		●	Identifier for the abs attendance reason.
ABS_INFORMATION_CATEGORY		●	Abs information category.
BATCH_ID		●	Identifier for the batch.
BUSINESS_GROUP_ID		●	Identifier for the business group.
CREATED_BY		●	User who created the row.
CREATION_DATE		●	Date and time the row was created.
DATE_END		●	Date end.
DATE_NOTIFICATION		●	Date notification.
DATE_PROJECTED_END		●	Date projected end.
DATE_PROJECTED_START		●	Date projected start.
DATE_START		●	Date start.
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.
OBJECT_VERSION_NUMBER		●	Optimistic-locking version number, incremented on each update.
PERIOD_OF_INCAPACITY_ID		●	Identifier for the period of incapacity.
PERSON_ID		●	Identifier for the person.
TIME_END		●	Time end.
TIME_PROJECTED_END		●	Time projected end.
TIME_PROJECTED_START		●	Time projected start.
TIME_START		●	Time start.

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_ABSENCE_ATTENDANCES?

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

Talk to us