How To Fix 61339 - Time stamp problem: Changes to planned order '&1' terminated

SAP Error Message - Details

• Message type: E = Error

• Message class: 61 - Fehlermeldungen fuer Bedarfsplanung

• Message number: 339

• Message text: Time stamp problem: Changes to planned order '&1' terminated

What causes this issue?

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.

System Response

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

How to fix this error?

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

Procedure for System Administrators

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message 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 (Network Time Protocol) to keep the time consistent.
  Refresh the Session: Log out and log back into the SAP system to refresh the session and clear any temporary inconsistencies.
  Check for Locks: Use transaction code SM12 to check for any locks on the planned order. If you find any locks that are not needed, you can delete them (ensure you have the necessary authorizations).
  Recreate the Planned Order: If the planned order is not critical, consider deleting it and recreating it to avoid the time stamp issue.
  Consult with Basis Team: If the issue persists, it may be necessary to involve the SAP Basis team to check for any underlying system issues or inconsistencies.
  
  Related Information:
  
  Transaction Codes: 
  
  SM12: To check and manage locks.
  CO02: To display and change planned orders.
  COHV: To manage and monitor production orders.
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for relevant notes in the SAP Support Portal.
  Documentation: Review the SAP documentation for planned orders and time management to understand how time stamps are handled in the system.
  
  If the problem continues after trying the above solutions, it may be necessary to escalate the issue to SAP support for further investigation.