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

ACE_RECON034 - Overview

• Message type: E = Error

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

• Message number: 034

• Message text: Field CPUDT 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.

ACE_RECON034 - Details

• The SAP error message ACE_RECON034 indicates a discrepancy between the CPUDT (CPU date) fields in the tables ACEPSOH and ACEV_ACEPSOH for the specified entries. This typically occurs in the context of the Asset Accounting (FI-AA) module, particularly during the reconciliation process of asset transactions.
  
  Cause:
  The error arises when there is a mismatch in the CPU date between the two tables:
  
  ACEPSOH: This table usually contains the header data for asset transactions.
  ACEV_ACEPSOH: This table is often used for storing the versioned data of asset transactions.
  
  The mismatch can occur due to various reasons, such as:
  
  Data inconsistencies due to manual changes or incorrect postings.
  Issues during data migration or system upgrades.
  Errors in the reconciliation process or batch jobs that update these tables.
  
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Identify the Entries: Use the provided identifiers (&1 and &2) to locate the specific entries in both tables. You can use transaction codes like SE16 or SE11