How To Fix FTR_FLP035 - Transaction locks are deactivated (see long text)

FTR_FLP035 - Overview

• Message type: E = Error

• Message class: FTR_FLP - Messages for Forward Loan Transaction

• Message number: 035

• Message text: Transaction locks are deactivated (see long text)

What causes this issue?

You have chosen the "Deactivate Locks" function.

System Response

The position locks generated by the transaction are changed so that the
system only generates a warning as opposed to an error message if the
forward sale exceeds the available position.
When the transaction is resaved, the locks are reset so that an error
message will be generated again. You may then have to deactivate the
locks once more.
If you want to return the locks to their original state, you need to
call "Change Transaction" and save the transaction without deactivating
the locks.

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_FLP035 - Transaction locks are deactivated (see long text) ?

  The SAP error message FTR_FLP035 indicates that transaction locks are deactivated in the system. This can occur in the context of financial transactions, particularly in the area of treasury and risk management, where transaction locks are essential for ensuring data integrity during processing.
  
  Cause:
  The error typically arises due to one of the following reasons:
  
  Configuration Settings: The system may be configured to not use transaction locks, which can lead to issues when multiple users attempt to access or modify the same data simultaneously.
  System Settings: The settings in the SAP system might have been altered, either intentionally or unintentionally, leading to the deactivation of transaction locks.
  User Authorizations: The user may not have the necessary authorizations to access or modify the transaction locks.
  
  
  Solution:
  To resolve the error, consider the following steps:
  
  
  Check Configuration:
  
  Navigate to the configuration settings for the relevant module (e.g., Treasury and Risk Management).
  Ensure that transaction locks are enabled. This may involve checking the