How To Fix CNV20200459 - Depreciation posting periods of involved company codes differ

SAP Error Message - Details

• Message type: E = Error

• Message class: CNV20200 - Messages for development class CNV_20200

• Message number: 459

• Message text: Depreciation posting periods of involved company codes differ

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 CNV20200459 - Depreciation posting periods of involved company codes differ ?

  The SAP error message CNV20200459, which states "Depreciation posting periods of involved company codes differ," typically occurs during a migration or data transfer process, particularly when dealing with asset accounting. This error indicates that the depreciation posting periods for the company codes involved in the transaction or migration do not match, which can lead to inconsistencies in financial reporting and asset management.
  Cause:
  
  Different Fiscal Year Variants: The company codes may have different fiscal year variants, which define the posting periods for depreciation.
  Inconsistent Configuration: The configuration settings for asset accounting may not be aligned across the company codes, leading to discrepancies in the posting periods.
  Migration Issues: During data migration, if the source and target company codes have different settings, this error can arise.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Fiscal Year Variants:
  
  Go to the transaction code OB29 to check the fiscal year variants for the involved company codes.
  Ensure that the fiscal year variants are the same for all company codes involved in the transaction.
  
  
  
  Align Depreciation Posting Periods:
  
  Review the configuration settings for asset accounting in transaction code OAYZ (for asset accounting settings).
  Make sure that the depreciation posting periods are consistent across the company codes.
  
  
  
  Adjust Migration Settings:
  
  If this error occurs during a migration process, review the migration settings to ensure that the source and target company codes are correctly configured.
  You may need to adjust the migration data to align with the target company code's settings.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to asset accounting and migration processes for additional guidance on resolving this error.
  
  
  
  Testing:
  
  After making the necessary adjustments, perform a test run to ensure that the error no longer occurs and that the depreciation postings can be processed correctly.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  OB29: To check and configure fiscal year variants.
  OAYZ: To configure asset accounting settings.
  
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or solutions for this specific error.
  SAP Community: Engage with the SAP Community forums for discussions and solutions shared by other users who may have encountered the same issue.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.