Understand Inventory data reprocessing

Inventory reprocessing is about having the ability to make changes or corrections to your Inventory data, and also to process late-arriving data and requests to update the Inventory database. Reprocessing enables AVEVA™ Production Management to update Inventory data by processing changes made to movement events, quality data, or planning data with a new version of the data that considers all recent changes.

Possible inputs to Inventory data reprocessing

The following items can be inputs to Inventory reprocessing:

• Movement events

• Quality events

• Planning records and Material Requirement records

Reprocessing workflow

These are the steps in the reprocessing work flow.

• Change - Make changes to the Inventory, Planning, or Quality data in AVEVA™ Production Management.

• Reprocess - Execute the Reprocessing operation.

• Review - Review the candidate data. Make more changes or accept the new data.

• Finalize - Finalize the new data set.

Versions of data

There are these versions of the Inventory data:

• Base version - The base version of finalized inventory data. This version cannot be modified and therefore not reprocessed.

• Current version - The most recent successfully processed or reprocessed version of Inventory data. This version that has not been finalized. It can be modified and therefore can be reprocessed.

• Candidate version - The set of Inventory data that is actively being reprocessed.

  • If reprocessing completes with success the candidate version becomes the current version.

  • If reprocessing is canceled or fails to complete, then it is abandoned and deleted.

Before and after status

New Movement events that have not been reprocessed before or have some changes will have Pending status before reprocessing.

After reprocessing, the HasPendingChanges property changes to false.

Guidelines

Some guidelines about reprocessing:

• Users who do not have appropriate permissions are not able to 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.

• During reprocessing, some events may be unsuccessful due to business rules. In such cases, an appropriate message is appended to either the movement event (visible in the Movement Events view) or quality event (visible in the Quality Events view); however, the reprocessing operation finishes as successful and then reports the number of events with error. A breakdown of movement versus quality event errors can be seen by hovering over the error icon on the Event Editor.

  Note: Warnings are not included in the error count.

Related topics

• Finalizing Data

• Reprocessing data from earliest change

• Reprocessing data from point in time

• Reprocessing Late Arriving data