Message type: E = Error
Message class: 61 - Fehlermeldungen fuer Bedarfsplanung
Message number: 339
Message text: Time stamp problem: Changes to planned order '&1' terminated
The changes to planned order &V1& were terminated. The cause of the
termination is the presence of differences with regard to the planned
order time stamp between the planned order (outbound status before the
change) and the database status of the corresponding planned order.
For every database change to a planned order, the system checks the
time stamp for the planned order and sets this again. This stores the
last time at which the planned order was changed.
The timestamp check is successful, when the timestamp of a planned
order read from the database by another application at the time when
the database change is made exactly matches the timestamp of the
planned order in the database.
In all other cases, the planned order has been changed by a parallel
application at some point in between times.
Whem timestamp problems occur, the system usually skips over the
planned order in question during updating. Updating is only terminated
when parallel changes are made to any dependent data in further update
update processes for the planned order, for example, status information
about capacity requirements records.
To avoid inconsistent planned orders, the changes have been terminated.
Start the transaction again in order to make your required changes at
the most current status.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
61339
- Time stamp problem: Changes to planned order '&1' terminated ?The SAP error message 61339, which states "Time stamp problem: Changes to planned order '&1' terminated," typically occurs when there is a discrepancy in the time stamps associated with a planned order. This can happen due to various reasons, such as: Causes: Time Stamp Mismatch: The planned order has a time stamp that does not match the current system time or the time stamp of the user session. Database Locking Issues: If another user or process is trying to modify the same planned order simultaneously, it can lead to a conflict. System Time Issues: If the system time is not synchronized correctly across different servers or clients, it can lead to this error. Transport Issues: If there have been recent transports or changes in the system that affect the planned order, it may lead to inconsistencies. Solutions: Check System Time: Ensure that the system time on the server and client machines is synchronized. You can use NTP
Get instant SAP help. Sign up for our Free Essentials Plan.
61338
Single item planning in simultation mode not possible for material &1 &2
What causes this issue? You want to plan material &V1& plant &V2& within multilevel single-item planning. This material is part of a ...
61337
Sales order planning/project planning not possible for material &1 &2
What causes this issue? You want to execute sales order planning or project planning for material &V1& plant &V2&. Requirements total...
61340
******* COMMENT: 340- BOM explosion number checks
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
61341
BOM explosion number & is not active
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.