Reprocess from earliest change with quality matching

When using Reprocess from Earliest Change, the SampleDateTime of the Quality Event is assumed to be equal to, or less than, the SampleDateTime of the matching Movement Events. Any Movement Events with an earlier SampleDateTime will not be factored when calculating the reprocessing window.

Example scenario

Movement Events are captured every hour. Quality Events capture from real-time source (online analyzer) every hour. The Movement Events capture every hour from 10:00 am to 9:00 pm. However, a single Quality Event that represents the full 12 hour shift is created from late-bound LIMS data with a SampleDateTime of 9:00 am, not 9:00 pm.

Some guidelines

Some guidelines about reprocessing data.

• 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 Inventory data.

Related topics

• Finalizing Data

• Understand Inventory data reprocessing

• Reprocessing data from point in time