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

PER_ALLOC_CHKLST_CONTACTS

HCMUsed in 0 subject areas15 reporting columns

Person / Worker (PER).

Likely primary key: ALLOC_CHKLST_CONTACT_ID (inferred from Oracle naming conventions, verify against Tables & Views)
Joins (inferred from key columns): ALLOCATED_CHECKLIST_ID → PER_ALLOCATED_CHECKLISTS · CHECKLIST_CONTACT_ID → PER_CHECKLIST_CONTACTS

Columns

ColumnKeyIn reportsDescription (inferred)
ADHOC_USER_GUID●Adhoc user guid.
ALLOCATED_CHECKLIST_ID●Identifier for the allocated checklist.
ALLOC_CHKLST_CONTACT_IDPK?●Identifier for the alloc chklst contact.
CHECKLIST_CONTACT_ID●Identifier for the checklist contact.
CONTACT_TITLE_CODE●Code identifying the contact title.
CONTACT_TYPE●Type of contact.
CREATED_BY●User who created the row.
CREATION_DATE●Date and time the row was created.
CUSTOM_CONTACT●Custom contact.
ENTERPRISE_ID●Identifier for the enterprise.
LAST_UPDATED_BY●User who last updated the row.
LAST_UPDATE_DATE●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.
RESPONSIBILITY_TYPE●Type of responsibility.

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