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

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 039

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

  The SAP error message ACE_RECON039 indicates a discrepancy between the FIRSTYEAR field in the tables ACEPSOH and ACEV_ACEPSOH for a specific entity (represented by &1 and &2). This error typically arises in the context of Asset Accounting (FI-AA) and can occur during processes such as asset reconciliation or reporting.
  Cause:
  
  
  Data Inconsistency: The most common cause of this error is that the FIRSTYEAR field in the two tables does not match. This can happen due to:
  
  Manual changes to asset data that were not properly synchronized.
  Data migration issues where the initial year was not correctly set in both tables.
  Incomplete or incorrect postings that affect the asset records.
  
  
  
  Configuration Issues: There may be configuration settings in the Asset Accounting module that are not aligned, leading to discrepancies in the data.
  
  
  Solution:
  
  
  Data Comparison: 
  
  Check the values of the FIRSTYEAR field in both ACEPSOH and ACEV_ACEPSOH for the specified entity. You can do this using SQL queries or through transaction codes that allow you to view table data.
  Identify the source of the discrepancy.
  
  
  
  Correcting Data:
  
  If the discrepancy is due to incorrect data entry or migration, you may need to manually correct the FIRSTYEAR field in one of the tables to ensure they match.
  Use transaction codes like AS02 (Change Asset) to update asset records if necessary.
  
  
  
  Reconciliation:
  
  After correcting the data, perform a reconciliation to ensure that all related records are consistent across the system.
  You may also want to run any relevant reports or transactions that can help identify other potential inconsistencies.
  
  
  
  Consult Documentation: 
  
  Review SAP documentation or notes related to Asset Accounting for any specific guidelines or recommendations regarding this error.
  
  
  
  Seek Support: 
  
  If the issue persists or if you are unsure about making changes, consider reaching out to your SAP support team or consulting with an SAP expert who specializes in Asset Accounting.
  
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  AS01 (Create Asset)
  AS02 (Change Asset)
  AS03 (Display Asset)
  S_ALR_87011990 (Asset History Sheet)
  
  
  
  SAP Notes: Check for any SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  
  Backup Data: Always ensure that you have a backup of your data before making any changes to the database to prevent data loss.
  
  
  By following these steps, you should be able to resolve the ACE_RECON039 error and ensure that your asset data is consistent across the relevant tables.