How To Fix FTR_LC158 - Postings for fee flows after rollover date have already been made

FTR_LC158 - Overview

• Message type: E = Error

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

• Message number: 158

• Message text: Postings for fee flows after rollover date have already been made

What causes this issue?

The fee flows after the rollover date in this company code have already
been posted. For this reason, you cannot enter a date in the
<LS>Rollover Date</> field.

System Response

The system does not allow you to change the rollover date.

How to fix this error?

Create a new transaction or perform a corresponding reversal to
eliminate any errors that may have occurred during the change in
rollover date for 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_LC158 - Postings for fee flows after rollover date have already been made ?

  The SAP error message FTR_LC158 indicates that there are postings for fee flows that have already been made after the rollover date. This typically occurs in the context of financial transactions, particularly in the area of treasury and risk management, where fee flows are processed.
  
  Cause:
  The error is triggered when the system detects that there are already financial postings related to fee flows that have been executed after the defined rollover date. The rollover date is a critical date in financial processes, marking the end of a period for which certain transactions can be processed. Once this date has passed, the system restricts further postings to maintain data integrity and ensure that financial reports reflect accurate information.
  
  Solution:
  To resolve this error, you can consider the following steps:
  
  
  Check Rollover Date: Verify the rollover date set in the system. Ensure that it is correctly configured and that you are not attempting to post transactions