Diagnosis
The changes to planned order &V1& were terminated. The cause of thetermination is the presence of differences with regard to the plannedorder time stamp between the planned order (outbound status before thechange) and the database status of the corresponding planned order.
For every database change to a planned order, the system checks thetime stamp for the planned order and sets this again. This stores thelast time at which the planned order was changed.
The timestamp check is successful, when the timestamp of a plannedorder read from the database by another application at the time whenthe database change is made exactly matches the timestamp of theplanned order in the database.
In all other cases, the planned order has been changed by a parallelapplication at some point in between times.
Whem timestamp problems occur, the system usually skips over theplanned order in question during updating. Updating is only terminatedwhen parallel changes are made to any dependent data in further updateupdate processes for the planned order, for example, status informationabout capacity requirements records.

System Response
To avoid inconsistent planned orders, the changes have been terminated.

Procedure
Start the transaction again in order to make your required changes atthe most current status.