How To Fix FTR_GENERAL170 - Status of few of the selected correspondences changed by concurrent users

SAP Error Message - Details

• Message type: E = Error

• Message class: FTR_GENERAL - Common messages for Correspondence object

• Message number: 170

• Message text: Status of few of the selected correspondences changed by concurrent users

What causes this issue?

The status of a few of the selected correspondence objects has been
changed by concurrent users.

System Response

The displayed view is refreshed to display the current and consistent
status of all the correspondence objects.

How to fix this error?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FTR_GENERAL170 - Status of few of the selected correspondences changed by concurrent users ?

  The SAP error message FTR_GENERAL170 indicates that the status of some of the selected correspondences has changed due to actions taken by concurrent users. This typically occurs in environments where multiple users are working on the same data or transactions simultaneously, leading to conflicts in the status of the correspondences.
  Cause:
  
  Concurrent Access: Multiple users are trying to update or process the same correspondence at the same time, leading to a conflict in the status.
  Data Locking: SAP uses locking mechanisms to prevent data inconsistencies. If one user locks a record and another user tries to access or modify it, the second user may encounter this error.
  System Performance: In some cases, system performance issues can lead to delays in status updates, causing discrepancies when multiple users are involved.
  
  Solution:
  
  Refresh the Data: After encountering this error, refresh the screen or re-fetch the data to ensure you are working with the most current status of the correspondences.
  Check for Locks: Use transaction codes like SM12 to check for locks on the correspondences. If you find locks that are no longer needed, you can release them (if you have the necessary authorizations).
  Coordinate with Users: If possible, coordinate with other users to avoid simultaneous updates on the same correspondence. Establishing a protocol for handling correspondences can help minimize conflicts.
  Retry the Operation: After refreshing and ensuring no locks are present, try to perform the operation again.
  Consult Documentation: Review SAP documentation or notes related to this error for any specific guidance or patches that may address the issue.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FTR_EDIT (for editing financial transactions) and FTR_COM (for correspondence management).
  SAP Notes: Check SAP Notes for any known issues or updates related to this error message. You can search for notes using the SAP Support Portal.
  User Training: Ensure that users are trained on how to handle correspondences and the importance of checking the status before making updates.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis or technical support team to investigate further.