Overview of Rolling Back Element Entries

You can only roll back new element entries that you loaded using the Element Entry object. To roll back element entries, there's an additional constraint that there should be no changes made to the object since it was created.

If HCM Data Loader identifies that the element entry has been updated, the rollback fails. The application doesn't make an attempt to roll back updates to an existing element entry. Also, it doesn't roll back the deletion of an existing element entry.

This figure illustrates how you can roll back element entries depending upon whether the entries were loaded using payroll flows or not.

If you submit an element entry using the Initiate Data Loader flow, then you can roll it back using one of the features:

• Payroll Flows

• The Import and Load Data page

• The HCM Data Loader web service

Alternatively, if you didn't submit your element entry using a flow pattern, then use the Import and Load Data page to roll them back.

Note: Let's assume you loaded Element Entry, Cost Allocation, and Cost Allocation account using a single data set from the Import and Load data page. To roll back the objects in that data set, you must roll back the objects in the reverse order. In other words, you must roll back Cost Allocation Account first, then Cost Allocation, and finally Element Entry.

Rollback and Events

When an element entry is rolled back, the application also rolls back any unprocessed events and notifications.

Consider these scenarios that explain the impact of a roll back on events.

• If the event has an unprocessed status, then the application removes the event. If the event is already processed, then the application lets it stay.

• If you created an element entry, then application removes the event. The application doesn't remove other types of element entry events, such as an update element entry event.

• If you updated an element entry, then the application doesn't delete that event.