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

ACE_RECON035 - Overview

• Message type: E = Error

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

• Message number: 035

• Message text: Field CPUTM 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_RECON035 - Field CPUTM of ACEPSOH and ACEV_ACEPSOH is not equal for &1/&2. ?

  The SAP error message ACE_RECON035 indicates a discrepancy between the CPU time (CPUTM) fields in the ACEPSOH and ACEV_ACEPSOH tables for the specified entries. This error typically arises during the reconciliation process in the SAP system, particularly in the context of the SAP Advanced Compliance Engine (ACE) or similar modules that deal with compliance and reporting.
  
  Cause:
  
  
  Data Inconsistency: The primary cause of this error is a mismatch in the CPU time recorded in the two tables (ACEPSOH and ACEV_ACEPSOH). This can happen due to:
  
  Manual data entry errors.
  Incomplete or interrupted processing of transactions.
  Issues during data migration or system upgrades.
  Concurrent processing where one process updates the data while another is reading it.
  
  
  
  System Bugs: Occasionally, bugs in the SAP system or specific configurations can lead to inconsistencies in the data.
  
  
  
  Solution:
  
  
  Data Verification: 
  
  Check the entries in both ACEPSOH and ACEV_ACEPSOH tables for the specified identifiers (&1 and &2) to understand the nature of the discrepancy.
  Use