How To Fix AAPO723 - Revaluation of ordinary depreciation not allowed for posting

AAPO723 - Overview

• Message type: E = Error

• Message class: AAPO - Asset Accounting - Posting

• Message number: 723

• Message text: Revaluation of ordinary depreciation not allowed for posting

What causes this issue?

You are trying to post a revaluation of ordinary depreciation.
However, either transaction type &V1& does <ZH>not</> allow revaluation
of ordinary depreciation, or depreciation area &V2& does <ZH>not</>
manage revaluation values for ordinary depreciation.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

Posting is <ZH>not</> possible.

How to fix this error?

Change the transaction type or change Customizing for the depreciation
area.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message AAPO723 - Revaluation of ordinary depreciation not allowed for posting ?

  The SAP error message AAPO723, which states "Revaluation of ordinary depreciation not allowed for posting," typically occurs in the context of asset accounting when there is an attempt to post a revaluation of an asset that is not permitted under the current configuration or circumstances.
  
  Cause:
  
  Asset Class Settings: The asset class may not allow for revaluation. Each asset class in SAP can have specific settings that determine whether revaluation is permitted.
  Depreciation Areas: The depreciation area settings may not allow for revaluation. Some depreciation areas are configured to only allow certain types of postings.
  Posting Period: The posting period may be closed, preventing any further postings, including revaluations.
  Transaction Type: The transaction type used for the posting may not support revaluation.
  Asset Status: The asset may be in a status that does not allow for revaluation (e.g., retired or fully depreciated).
  
  
  Solution:
  
  Check Asset Class Configuration: Review the configuration of the asset class in transaction code OAOA.