How To Fix ACEC_S4093 - Make sure posting and closing frequencies follow the same rule.

ACEC_S4093 - Overview

• Message type: E = Error

• Message class: ACEC_S4 - Customizing Message for Accrual Engine in S4 Version

• Message number: 093

• Message text: Make sure posting and closing frequencies follow the same rule.

What causes this issue?

INCLUDE ACE_POST_FREQUENCY OBJECT DOKU ID TX LANGUAGE EN

System Response

&V1& is a combination of accrual component, accrual item type, company
code and ledger group. Leger group may be empty.

How to fix this error?

Change the configuration of periodic frequency or the closing frequency
of &V1& and make sure they follow the same rule, either
fiscal-year-based or calendar based.
You can change it in Customizing activity
<DS:SIMG.VC_TACE_ITEMTY>Define Accrual Item Types</>.

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.

ACEC_S4093 - Details

• The SAP error message ACEC_S4093 typically occurs in the context of financial closing processes, particularly when there is a mismatch between the posting frequency and the closing frequency for a specific account or transaction type. This error indicates that the system has detected an inconsistency in the configuration settings that govern how often postings can be made versus how often the closing processes are executed.
  
  Cause:
  
  Configuration Mismatch: The most common cause of this error is a mismatch in the configuration settings for posting frequencies and closing frequencies. For example, if postings are allowed on a monthly basis but the closing frequency is set to quarterly, this inconsistency will trigger the error.
  Account Settings: Specific accounts may have different posting and closing frequency settings, leading to conflicts during the closing process.
  Transaction Type Settings: Different transaction types may have different rules regarding posting and closing frequencies, which can also lead to this error.
  
  
  Solution:
  
  
  Review Configuration