Manage Workforce Schedule Deletion
Organizations can use a third-party scheduling application to manage their workforce schedule, including clearing department or workers schedules. Oracle Fusion Cloud Workforce Scheduling imports these schedules by performing a POST operation on the scheduleRequests resource.
Schedule managers can verify imported schedule deletions using the Workforce Schedules page.
Let's discuss these scenarios:
Clear a Workforce Schedule for a Staffing Department
Let's say that a department needs to close unexpectedly during a work week and its schedule needs to be cleared. The third-party scheduling application sends the updates to the department schedule for the week.
Workforce Scheduling clears the schedule for department using the POST operation on the scheduleRequests resource with importMode FULL and no child details.
Here's the Workforce Scheduling configuration that applies to this scenario.
Configuration | Purpose |
Schedule Generation Profiles | Define schedule generation profiles to identify staffing departments, the scheduling period, and other configuration options. |
Work Patterns | Define work patterns for workers. |
Manage Common Lookups |
Review the lookup type ORA_HWM_SHIFT_ENTRY_OWNER values. For shifts imported from a third-party scheduling application, the RequestSource field in the ScheduleRequest object is controlled by the owner.
|
To clear a department's workforce schedules:
- Extract from your third-party scheduling application, the revised schedules for the departments, and the required period. The schedule content is empty.
- Load the extracted data to Oracle Fusion Cloud Workforce Scheduling using the
scheduleRequests REST service.
- Perform a POST operation on the scheduleRequests REST resource by using the sample payload.
- Verify the details returned in the response.
- Clear the workforce schedules by running the Process Imported Shifts process to delete the shifts from the workforce schedule.
Example URL
Use this resource URL format.
POST
/hcmRestApi/resources/11.13.18.05/scheduleRequests
Example Request
Here's an example of the request body in JSON format:
{
"scheduleRequestNumber": "Import002",
"requestTime": "2025-01-01T12:00:00.010+01:00",
"requestSource": "ORA_HWM_WFM",
"importMode": "FULL",
"startDate": "2025-06-02",
"endDate": "2025-06-08",
"validationFlag": "Y",
"departmentName": "Clinic",
"locationCode": "SAN_FRAN",
"locationSetCode": "COMMON"
}
Example Response
Here's an example of the response body in JSON format.
Status 201
{
"scheduleRequestNumber": "Import002",
"requestSource": "ORA_HWM_WFM",
"schedRequestId": 300100658360900,
"requestTime": "2025-01-01T12:00:00.010+01:00",
"importMode": "FULL",
"startDate": "2025-06-02",
"endDate": "2025-06-08",
"validationFlag": true,
"departmentName": "Clinic",
"locationCode": "SAN_FRAN",
"locationSetCode": "COMMON",
"locationId": null,
"departmentId": null,
"links": [
{....
}
]
}
Clear a Workforce Schedule for a Worker
Let's say that a nurse practitioner, Alan Smith, works Monday through Friday on an 8 AM to 6 PM shift. Alan is in training this week and is unavailable to work, so his schedule needs to be cleared.
Third-party scheduling sends the updates for Alan's schedule the week he's in training.
Workforce Scheduling imports the schedule for the department using the POST operation on the scheduleRequests resource, with these attribute values.
- importMode is UPDATE for the scheduleRequests resource.
- importMode is FULL for the scheduleEvents resource for Alan.
Here's the Workforce Scheduling configuration that applies to this scenario.
Configuration | Purpose |
Schedule Generation Profiles | Define schedule generation profiles to identify staffing departments, the scheduling period, and other configuration options. |
Work Patterns | Define work patterns for workers. |
Manage Common Lookups |
Review the lookup type ORA_HWM_SHIFT_ENTRY_OWNER values. For shifts imported from a third-party scheduling application, the RequestSource field in the ScheduleRequest object is controlled by the owner.
|
To clear a worker's workforce schedules:
- Extract from your third-party scheduling application, the revised schedules for the departments and the required period. The schedule content for the worker is empty.
- Load the extracted data to Oracle Fusion Cloud Workforce Scheduling using the
scheduleRequests REST service.
- Perform a POST operation on the scheduleRequests REST resource by using the sample payload.
- Verify the details returned in the response.
- Clear the worker's workforce schedules by running the Process Imported Shifts process to delete the shifts from the worker workforce schedule.
Example URL
Use this resource URL format.
POST
/hcmRestApi/resources/11.13.18.05/scheduleRequests
Example Request
Here's an example of the request body in JSON format:
{
"scheduleRequestNumber": "Import003",
"requestTime": "2025-01-01T12:00:00.010+01:00",
"requestSource": "ORA_HWM_WFM",
"importMode": "UPDATE",
"startDate": "2025-06-02",
"endDate": "2025-06-08",
"validationFlag": "Y",
"departmentName": "Clinic",
"locationCode": "SAN_FRAN",
"locationSetCode": "COMMON",
"scheduleEvents": [
{
"scheduleEventNumber": "SE301",
"resourceReferenceType": "PERSON_NUMBER",
"resourceReference": "CLINIC_001",
"importMode": "FULL"
}
]
}
Example Response
Here's an example of the response body in JSON format.
Status 201
{
"scheduleRequestNumber": "Import003",
"requestSource": "ORA_HWM_WFM",
"schedRequestId": 300100658362579,
"requestTime": "2025-01-01T12:00:00.010+01:00",
"importMode": "UPDATE",
"startDate": "2025-06-02",
"endDate": "2025-06-08",
"validationFlag": true,
"departmentName": "Clinic",
"locationCode": "SAN_FRAN",
"locationSetCode": "COMMON",
"locationId": null,
"departmentId": null,
"scheduleEvents": [
{
"resourceReferenceType": "PERSON_NUMBER",
"resourceReference": "CLINIC_001",
"importMode": "FULL",
"periodStartDate": "2025-06-02",
"periodEndDate": "2025-06-08",
"publish": null,
"workerNotification": null,
"allowEdits": null,
"schedEventId": 300100658362580,
"schedRequestId": 300100658362579,
"scheduleEventNumber": "SE301",
"links": [
{...
}
]
}
]
}