Results for “per_checklist_items”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PER_CHECKLIST_ITEMS is a Human Resources (PER) module table in the Oracle E-Business Suite, owned by the HR schema. It stores checklist information associated with persons, typically used by Oracle HRMS onboarding, offboarding, and task-tracking functionality such as the Oracle iRecruitment and Applicant/Employee onboarding flows. Each row represents an individual checklist item — a discrete task, document, or action that a person must complete — tracked against a person record, with due dates, completion dates, and status.

Physically, the table is documented in ETRM 12.2.2 as an HR-owned object with 44 columns. Its primary key is PER_CHECKLIST_ITEMS_PK on CHECKLIST_ITEM_ID, a surrogate system-generated identifier. A unique business-key index, PER_CHECKLIST_ITEMS_U1, enforces uniqueness on the combination of PERSON_ID and ITEM_CODE. Under the heuristic Data Vault classification provided in the metadata, PER_CHECKLIST_ITEMS is assessed as standalone — meaning it is modelled as neither a hub, link, nor satellite in a strict Data Vault sense, but rather as an independent entity that does not participate in foreign-key enforcement relationships. This classification should be treated as a modelling suggestion only, since the table carries descriptive attributes and person-context columns that would ordinarily resemble a satellite or link.

Key Information Stored

The most significant columns include:

• CHECKLIST_ITEM_ID — the surrogate primary key (PER_CHECKLIST_ITEMS_PK), uniquely identifying each checklist item row.
• PERSON_ID — identifies the person (employee, applicant, or contingent worker) to whom the checklist item belongs; part of the business-key unique index PER_CHECKLIST_ITEMS_U1.
• ITEM_CODE — the code of the checklist item (e.g., a task or document code); the second column in the PER_CHECKLIST_ITEMS_U1 business key.
• DATE_DUE — the date by which the checklist item must be completed.
• DATE_DONE — the date the item was actually completed.
• STATUS — the current state of the item (e.g., open, complete).
• NOTES — free-text notes or comments associated with the item.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OA Framework.
• ATTRIBUTE_CATEGORY plus ATTRIBUTE1 through ATTRIBUTE30 — the standard EBS descriptive flexfield (DFF) columns for capturing client-specific extensions.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — the standard WHO audit columns tracking row creation and last modification.

The distinction between the surrogate primary key (CHECKLIST_ITEM_ID) and the business-key candidates (PERSON_ID, ITEM_CODE) is important: the latter enforces that a given person cannot have duplicate checklist items of the same code, while the former provides a stable internal reference for joins and integrations.

Common Use Cases and Queries

Typical reporting uses include tracking outstanding onboarding tasks, measuring completion rates, and producing overdue checklists. A common query pattern joins on PERSON_ID to retrieve items by person and filters by status or due date:

• List all incomplete checklist items for a person: select CHECKLIST_ITEM_ID, ITEM_CODE, DATE_DUE, STATUS from PER_CHECKLIST_ITEMS where PERSON_ID = :person_id and STATUS <> 'COMPLETE'.
• Identify overdue items: where DATE_DUE < sysdate and DATE_DONE is null.
• Completion time analysis: DATE_DONE minus DATE_DUE to compute lateness per item.
• DFF reporting: joining ATTRIBUTE_CATEGORY and ATTRibute segments to the DFF definition for client-specific fields.

Related Objects

Because the metadata classifies PER_CHECKLIST_ITEMS as standalone, no foreign-key targets are documented explicitly. In practice, the most relevant related objects join via PERSON_ID and the object’s own PK:

• PER_ALL_PEOPLE_F (PER_ALL_PEOPLE_F.PERSON_ID = PER_CHECKLIST_ITEMS.PERSON_ID) — the person master.
• PER_ALL_ASSIGNMENTS_F — assignment context for the person.
• PER_CHECKLISTS / PER_CHECKLIST_ITEM definitions — the setup metadata defining ITEM_CODE values.
• HR/PERSON APIs and the OA Framework checklist UI pages that read and write this table.

Any integration or report should filter on PERSON_ID and ITEM_CODE to respect the PER_CHECKLIST_ITEMS_U1 business key.