How To Fix FTR_LC160 - Postings for fee flows after nominal change have already been made

FTR_LC160 - Overview

• Message type: E = Error

• Message class: FTR_LC - Message class for Letter of Credit

• Message number: 160

• Message text: Postings for fee flows after nominal change have already been made

What causes this issue?

The fee flows after a nominal change (increase/decrease) in this company
code have already been posted. For this reason, you cannot perform a
nominal change.

System Response

The system does not allow you to perform a nominal change.

How to fix this error?

Create a new transaction or perform the corresponding reversal to
eliminate any errors that may have occurred during the presentation
change of this transaction.

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 FTR_LC160 - Postings for fee flows after nominal change have already been made ?

  The SAP error message FTR_LC160 indicates that there are postings for fee flows that have already been made after a nominal change. This typically occurs in the context of financial transactions, particularly in the area of treasury and risk management, where fee flows are associated with financial instruments.
  
  Cause:
  The error arises when you attempt to make changes to a nominal value (such as a change in the principal amount of a financial instrument) after fee flows have already been posted. This situation can occur if:
  
  Nominal Change: A nominal change was made to a financial instrument, but fee flows related to that instrument have already been processed.
  Timing Issues: There may be timing issues where the nominal change is attempted after the fee flows have been posted.
  
  Configuration Issues: There may be configuration settings in the system that do not allow for changes to be made after certain postings have occurred.
  
  
  Solution:
  To resolve this error,