Oracle Fusion · Data dictionary
PER_CHECKLIST_CONTACTS
HCMUsed in 0 subject areas14 reporting columns
Person / Worker (PER).
Likely primary key: CHECKLIST_CONTACT_ID (inferred from Oracle naming conventions, verify against Tables & Views)
Joins (inferred from key columns): CHECKLIST_ID → PER_CHECKLISTS_B
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| ADHOC_USER_GUID | ● | Adhoc user guid. | |
| CHECKLIST_CONTACT_ID | PK? | ● | Identifier for the checklist contact. |
| CHECKLIST_ID | ● | Identifier for the checklist. | |
| 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_CHECKLIST_CONTACTS?
We ship parameterized SQL, BICC config, and dbt models you own.
Problems that run through this table