Reprocess data from point in time
- Last UpdatedMar 01, 2023
- 3 minute read
Important: Reprocessing is currently available for Inventory events and Quality events.
You can reprocess data from a specific point in time, rather than having to reprocess all data since last Finalization point. This gives you greater flexibility to reprocess a smaller set of data on demand, which can be more time efficient.
You can specify the amount of data to reprocess; for example, the Last 2 Days or Last Week's set of data.

Some guidelines about reprocessing data
-
You can select a specific period of data to reprocess, without going all the way back to the Finalization point. However, you can not go earlier than the Finalization point.
-
If you specify a date that is earlier than the most recent Finalization point, the reprocessing action occurs from the Finalization point.
-
If a scheduled reprocessing action is currently running, you will have to wait for it to complete or cancel the action.
-
Users who do not have appropriate permissions cannot see the reprocessing window or start reprocessing operations.
-
Any user with appropriate permissions can view or cancel the progress of the reprocessing operation. Canceling the reprocess operation returns all records to their original state.
-
During the reprocessing, some movements may be unsuccessful due to business rules. In such cases, an appropriate message appends to the movement event and is visible in the Movement Events view; however, the reprocessing operation finishes as successful and then reports the number of movements with errors.
Note If you want to perform a full reprocessing action on all Inventory data since the Finalization point, see Reprocess data.
To reprocess a specific set of data from point in time
-
Click the Reprocess button to reprocess Inventory data.

-
On the Inventory reprocessing window, select Last.
-
Specify a number such as 1 or 2, and then a time period, such as Days or Weeks.
-
Click Start reprocessing.

The Inventory reprocessing window shows the real-time progress of the reprocessing operation and provides a summary on the results.

After a full reprocess you always see zero (0) pending changes after the operation; however, after a partial reprocessing action, any changes that were not within the reprocessing window will still be in a state of Pending.