Results for “per_allocated_checklists”

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

Overview

PER_ALLOCATED_CHECKLISTS is a Human Resources (PER) transactional table in the Oracle E-Business Suite 12.1.1 and 12.2.2 data model. It stores the individual allocations of checklist templates to persons and assignments. Oracle HRMS leverages allocated checklists to drive onboarding, offboarding, transfer, and compliance workflows, where a checklist definition (for example, "New Hire Setup" or "Exit Processing") is copied onto a specific person's record so that the resulting tasks can be tracked to completion. Each row represents one allocated checklist instance owned by a single PERSON_ID and, where applicable, a specific ASSIGNMENT_ID.

The table plays a supporting role in the HRMS person/assignment model. It does not itself define the checklist content; it references the source template in PER_CHECKLISTS and serves as the parent for the individual actionable rows in PER_ALLOCATED_TASKS. Based on the documented foreign key topology, the ETRM heuristic classifies this object as satellite-leaning — that is, it is primarily a descriptive, attribute-bearing detail table that hangs off a core parent (in this case the person/assignment and the checklist template) rather than acting as a pure hub or a many-to-many link. This classification is a modeling suggestion, not an enforced constraint.

Key Information Stored

The table contains 55 documented columns. The most significant columns are:

• ALLOCATED_CHECKLIST_ID — the surrogate primary key (PER_ALLOCATED_CHECKLISTS_PK); a system-generated unique identifier for each allocation row.
• CHECKLIST_ID — foreign key to PER_CHECKLISTS; identifies the checklist template from which this allocation was created.
• PERSON_ID — the person to whom the checklist is allocated; the principal business-key driver.
• ASSIGNMENT_ID — the assignment the checklist applies to, allowing checklist tracking at the assignment level.
• CHECKLIST_NAME — the display name of the allocated checklist instance.
• DESCRIPTION — free-form text describing the purpose or context of the allocation.
• CHECKLIST_CATEGORY — a classification code that groups checklists by type or business function.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the HRMS framework for concurrent update control.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard "who/when" auditing columns.
• CREATED_BY, CREATION_DATE — record creation audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — the standard EBS descriptive flexfield (DFF) segment columns.
• INFORMATION_CATEGORY and INFORMATION1–INFORMATION20 — the secondary DFF/context-flexfield segment columns.

The documented primary key is the surrogate ALLOCATED_CHECKLIST_ID. Business-key candidates such as the combination of PERSON_ID, ASSIGNMENT_ID, and CHECKLIST_ID should be treated as logical identifiers rather than enforced unique indexes unless validated in site-specific metadata.

Common Use Cases and Queries

Typical scenarios include onboarding dashboards listing outstanding checklists per new hire, audit reports of allocated versus completed tasks, and integrations that push checklist status to external HR or identity systems.

A basic allocation-to-template join:

• SELECT ac.ALLOCATED_CHECKLIST_ID, ac.CHECKLIST_NAME, c.CHECKLIST_NAME AS TEMPLATE_NAME, ac.PERSON_ID, ac.ASSIGNMENT_ID FROM HR.PER_ALLOCATED_CHECKLISTS ac JOIN HR.PER_CHECKLISTS c ON ac.CHECKLIST_ID = c.CHECKLIST_ID WHERE ac.PERSON_ID = :p_person_id;

An allocation-to-task drill-down for tracking completion:

• SELECT ac.ALLOCATED_CHECKLIST_ID, ac.PERSON_ID, at.ALLOCATED_TASK_ID, at.TASK_NAME FROM HR.PER_ALLOCATED_CHECKLISTS ac JOIN HR.PER_ALLOCATED_TASKS at ON at.ALLOCATED_CHECKLIST_ID = ac.ALLOCATED_CHECKLIST_ID WHERE ac.ASSIGNMENT_ID = :p_assignment_id;

Reporting queries should always filter on PERSON_ID or date ranges on CREATION_DATE because the table is transaction-heavy and can grow large.

Related Objects

• PER_CHECKLISTS — parent template table; joined via CHECKLIST_ID.
• PER_ALLOCATED_TASKS — child table holding individual tasks; references this table via ALLOCATED_CHECKLIST_ID.
• PER_ALL_PEOPLE_F — the person master; joined via PERSON_ID.
• PER_ALL_ASSIGNMENTS_F — the assignment master; joined via ASSIGNMENT_ID.
• PER_CHECKLIST_TEMPLATES / PER_CHECKLIST_TASK_TEMPLATES — template definitions consumed during allocation.
• HRMS PL/SQL APIs (such as the checklist allocation APIs in the HR_CHECKLIST_* packages) that create and manage allocated checklist rows.
• Standard DFF views such as PER_ALLOCATED_CHECKLISTS_DFV or _DF views exposing flexfield segments.