How To Fix ACE_RECON036 - Field DEACTDATE of ACEPSOH and ACEV_ACEPSOH is not equal for &1/&2.

ACE_RECON036 - Overview

• Message type: E = Error

• Message class: ACE_RECON - Accrual Engine migration: Messages from reconciliation

• Message number: 036

• Message text: Field DEACTDATE of ACEPSOH and ACEV_ACEPSOH is not equal for &1/&2.

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message ACE_RECON036 - Field DEACTDATE of ACEPSOH and ACEV_ACEPSOH is not equal for &1/&2. ?

  The SAP error message ACE_RECON036 indicates a discrepancy between the DEACTDATE fields in the tables ACEPSOH and ACEV_ACEPSOH for the specified entries (identified by &1 and &2). This error typically arises during reconciliation processes in Asset Accounting or similar modules where consistency between different tables is crucial.
  
  Cause:
  
  
  Data Inconsistency: The most common cause of this error is that the deactivation date (DEACTDATE) for the same asset or transaction is not matching between the two tables. This can happen due to:
  
  Manual data entry errors.
  Incomplete or failed data updates.
  Issues during data migration or system upgrades.
  Concurrent processing where one process updates the data while another reads it.
  
  
  
  
  Configuration Issues: There may be configuration settings that are not aligned, leading to discrepancies in how data is processed or stored.
  
  
  
  Solution:
  
  
  Data Verification: 
  
  Check the entries in both ACEPSOH and ACEV_ACEPSOH for the specified asset or transaction IDs (&1 and &2).
  Compare the DEACTDATE values to identify the inconsistency.
  
  
  
  Correct the