Deleting Assigned Journeys using HDL

In HR systems, those built on Oracle HCM, Journeys or Assigned Checklists help guide employees through tasks like onboarding, training, or offboarding. But what happens when a journey is no longer relevant? Maybe a task needs to be removed—or perhaps an employee has left the organization, and all their active assigned checklists must go. This blog explores different scenarios and how to handle them using HCM Data Loader (HDL).

1. Delete Entire Assigned Journeys

Here is the HDL:

METADATA|AllocateChecklist|ChecklistName|ChecklistCategory|ChecklistInstance|PersonNumber
DELETE|AllocateChecklist|Holiday Calendar 2025|ONBOARD|1|101
DELETE|AllocateChecklist|Holiday Calendar 2025|ONBOARD|2|101

Explanation for fields for AllocateChecklist

ChecklistName: Name of the checklist/Journey assigned.

ChecklistCategory: Pass the appropriate lookup code for the journey category from set up page, which is derived from the CHECKLIST_CATEGORY lookup based on the journey setup.

ChecklistInstance: A journey instance starts with the number 1. If you do not see any number in brackets, then default to 1 else default to the number in brackets.

PersonNumber: Employee ID

Save the HDL as AllocateChecklist.dat and run it.

2. Delete Specific Tasks from an Assigned Journey

There may be times when the journey remains valid, but a particular task within that checklist needs to be removed. HDL allows granular management of assigned tasks too.

Here is the HDL – save it as AllocateChecklist.dat

METADATA|AllocateChecklistTask|TaskName|ChecklistName|ChecklistCategory|ChecklistInstance|PersonNumber
DELETE|AllocateChecklistTask|Calendar Task|Holiday Calendar 2025|ONBOARD|1|101

Explanation for fields for AllocateChecklist

• TaskName : Specify the task name which you would like to delete.

• ChecklistName : Name of the checklist/Journey assigned.

• ChecklistCategory : Pass the appropriate lookup code for the journey category from set up page, which is derived from the CHECKLIST_CATEGORY lookup based on the journey setup.

• ChecklistInstance : A journey instance starts with the number 1. If you do not see any number in brackets, then default to 1 else default to the number in brackets.

• PersonNumber : Employee ID

3. Sample SQL to retrieve assigned checklist/Journey data

SELECT
  PAPF.PERSON_NUMBER,
  PACV.CHECKLIST_NAME,
  PACV.CHECKLIST_CATEGORY,
  PACV.CHECKLIST_INSTANCE,
  PATV.TASK_NAME
FROM
  PER_ALL_ASSIGNMENTS_M PAAM,
  PER_ALL_PEOPLE_F PAPF,
  PER_ALLOCATED_CHECKLISTS_VL PACV,
  PER_ALLOCATED_TASKS_VL PATV
WHERE
  1 = 1
  AND PAPF.PERSON_ID = PAAM.PERSON_ID
  AND PAAM.EFFECTIVE_LATEST_CHANGE = 'Y'
  AND PAAM.PRIMARY_FLAG = 'Y'
  AND PAAM.ASSIGNMENT_TYPE IN ('E', 'C')
  AND SYSDATE BETWEEN PAAM.EFFECTIVE_START_DATE
  AND PAAM.EFFECTIVE_END_DATE
  AND SYSDATE BETWEEN PAPF.EFFECTIVE_START_DATE
  AND PAPF.EFFECTIVE_END_DATE
  AND PACV.PERSON_ID (+) = PAPF.PERSON_ID
  AND PACV.CHECKLIST_NAME IN ('Holiday Calendar 2025')
  AND PACV.CHECKLIST_CATEGORY = 'ONBOARD'
  AND PACV.ALLOCATED_CHECKLIST_ID = PATV.ALLOCATED_CHECKLIST_ID
  AND PAPF.PERSON_NUMBER = '101'

With HDL, managing the lifecycle of assigned journeys is not only possible but also efficient and scalable. Whether you’re fine-tuning tasks or wiping out unneeded assignments after terminations, HDL gives you the control you need.

---

References:

• Oracle Document >> HCM Data Loading Business Objects

** Oracle Document URL is subject to change with every upgrade.