Results for “task_sequence”

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

Overview

HR.PER_ALLOCATED_TASKS is a Human Resources (PER) module table that stores the individual tasks belonging to an allocated checklist in Oracle EBS 12.1.1 and 12.2.2. In the E-Business Suite, allocated checklists represent a reusable definition of work to be performed (for example, a new-hire onboarding checklist or an offboarding checklist), and each row in PER_ALLOCATED_TASKS represents a single unit of work within that checklist — such as "Issue laptop", "Complete tax forms", or "Assign security badge". The table is a child of PER_ALLOCATED_CHECKLISTS, linked through the ALLOCATED_CHECKLIST_ID foreign key, giving a one-to-many relationship between a checklist header and its constituent tasks. The ETRM relationship data classifies this object heuristically as standalone with respect to Data Vault modeling; however, because it carries a natural parent key and a dependent lifecycle, a modeling exercise may find it more appropriate to treat it as a satellite attached to the checklist hub/link. Either interpretation should be validated against actual usage.

Key Information Stored

The table is documented with 63 columns in the 12.2.2 physical schema. The most operationally significant columns are:

• ALLOCATED_TASK_ID — surrogate primary key (unique index PER_ALLOCATED_TASKS_PK); no separate business-key unique index beyond the PK is documented, so this is the sole unique identifier.
• ALLOCATED_CHECKLIST_ID — foreign key to PER_ALLOCATED_CHECKLISTS; the parent checklist to which the task belongs.
• TASK_NAME and DESCRIPTION — the short label and long description of the task.
• MANDATORY_FLAG — indicates whether the task must be completed for the checklist to be considered finished.
• STATUS — the current task state (for example, not started, in progress, completed).
• PERFORMER_ORIG_SYSTEM and PERFORMER_ORIG_SYS_ID — identify the external/owning system and record of the person responsible for performing the task.
• TASK_OWNER_PERSON_ID — the person assigned as owner of the task.
• TASK_SEQUENCE — ordering of the task within the checklist.
• TARGET_START_DATE, TARGET_END_DATE, ACTUAL_START_DATE, ACTUAL_END_DATE — planned versus actual execution dates for tracking progress and SLA completion.
• ACTION_URL — the deep link used to launch the task's action.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — standard EBS concurrency and audit columns.
• ATTRIBUTE1–ATTRIBUTE20 and INFORMATION1–INFORMATION20 with INFORMATION_CATEGORY — the descriptive flexfield (DFF) and information-type flexfield segments.

Common Use Cases and Queries

Typical uses include reporting on outstanding or overdue tasks for a checklist, driving notifications to task owners, and reconciling checklist completion status against the parent checklist. A representative pattern joins task to checklist by the documented foreign key:

• SELECT t.task_name, t.status, t.target_end_date, c.allocation_date FROM per_allocated_tasks t, per_allocated_checklists c WHERE t.allocated_checklist_id = c.allocated_checklist_id AND t.status != 'COMPLETE';
• Overdue tasks: filter on TARGET_END_DATE < SYSDATE and STATUS != 'COMPLETE'.
• Workload by owner: group by TASK_OWNER_PERSON_ID.
• Join to PER_PEOPLE_F via TASK_OWNER_PERSON_ID = PERSON_ID to resolve owner names.

Concurrency/audit reporting should always qualify by OBJECT_VERSION_NUMBER and the audit columns when extracting to a warehouse.

Related Objects

• PER_ALLOCATED_CHECKLISTS — parent header; joined on ALLOCATED_CHECKLIST_ID (documented FK).
• PER_PEOPLE_F — resolves TASK_OWNER_PERSON_ID and performer identities to assignment data.
• PER_ALL_PEOPLE_F (or PER_PERSON_NAMES_F in 12.2.2) — current-effective person name lookups for owners.
• PER_CHECKLIST_* definition tables — the task templates from which allocated tasks may be generated.
• Standard EBS audit columns link implicitly to FND_USER via CREATED_BY/LAST_UPDATED_BY.

Because the object carries DFF segments and an ACTION_URL, the related flexfield definition objects (FND_FLEX_VALUES, FND_DESCR_FLEX_COL_USAGE) are also relevant when interpreting the attribute columns.