How To Fix ACEPS055 - A accrual run has already been carried out in company code &1 on &3

SAP Error Message - Details

• Message type: E = Error

• Message class: ACEPS - Fehlermeldungen Abgrenzungsbuchungen

• Message number: 055

• Message text: A accrual run has already been carried out in company code &1 on &3

trados = docu -> fi -> figl

What causes this issue?

You want to carry out an accrual run with run type "repeat" in company
code &V1& for key date &V2&.

System Response

However, an accrual (run type = normal) has already been carried out on
a later key date &V3&.
The key date of a repeat run must always be consistent with the key date
of the last normal run.
See the <DS:TX.ACEPS_PER_RUN_EXCEPTION>exception for the last run in a
fiscal year</>:

How to fix this error?

Check the accrual runs that have already been carried out for the
company code and make any corrections with regard to the entry
parameters of the accrual run.

Procedure for System Administrators

INCLUDE ACE_MESSAGE_SWITCH_OFF OBJECT DOKU ID TX
Note:
It may be useful to deactivate this message if certain accrual items
were not processed in subsequent accrual runs after &V2& and you want to
post the (missing) accruals.
If you deactivate this message and execute an accruals run on the key
date required, the system only processes accrual items that were not
processed in subsequent accruals runs in the period between &V2& and the
end of the fiscal year.
If the date is in a later fiscal year, you have to <zh>repeat</> the
accruals runs of the subsequent fiscal years for the accrual items
concerned.
You do this by running the periodic accrual run with run type "repeat"
for the relevant key dates in the following fiscal years. This corrects
the period values in Financial Accounting.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ACEPS055 - A accrual run has already been carried out in company code &1 on &3 ?

  The SAP error message ACEPS055 indicates that an accrual run has already been executed for a specific company code on a given date. This error typically arises when you attempt to run an accrual process (like the accrual accounting process) for a period where an accrual run has already been completed.
  Cause:
  
  Duplicate Accrual Run: The most common cause is that the accrual run has already been processed for the specified company code and date.
  Incorrect Date: You may be trying to run the accrual for a period that has already been closed or for which the accrual has already been executed.
  Configuration Issues: There might be issues with the configuration settings in the accrual accounting module.
  
  Solution:
  
  Check Accrual Runs: Verify if an accrual run has indeed been executed for the specified company code and date. You can do this by checking the relevant transaction logs or reports in SAP.
  Use Different Date: If you need to run the accrual process again, consider using a different date or period that has not been closed or processed.
  Reversal of Accrual: If the accrual run was executed in error, you may need to reverse it before you can run it again. This can typically be done through the appropriate reversal transaction.
  Consult Documentation: Review the SAP documentation or help files related to accrual accounting for any specific instructions or guidelines.
  Contact Support: If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  FBS1: For posting a manual accrual.
  F.81: For executing the accrual run.
  
  
  Logs and Reports: Use transaction codes like S_ALR_87012357 or S_ALR_87012358 to view accrual run logs and reports.
  Configuration Settings: Check the configuration settings in the Financial Accounting (FI) module related to accruals to ensure they are set up correctly.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.