How To Fix FML_CUST028 - A posting AVR run with revaluation is not allowed

SAP Error Message - Details

• Message type: E = Error

• Message class: FML_CUST - Message Class for ML Customizuing

• Message number: 028

• Message text: A posting AVR run with revaluation is not allowed

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 FML_CUST028 - A posting AVR run with revaluation is not allowed ?

  The SAP error message FML_CUST028 indicates that a posting run for Asset Accounting (AA) with revaluation is not allowed. This error typically arises when there are attempts to perform a posting run that includes revaluation of assets, but the system settings or configurations do not permit it.
  Cause:
  
  Configuration Settings: The system may be configured to disallow revaluation postings in certain scenarios. This could be due to specific settings in the Asset Accounting configuration.
  Posting Run Type: The type of posting run being executed may not support revaluation. For example, if the posting run is intended for a different purpose (like depreciation posting), it may not allow revaluation.
  Authorization Issues: The user executing the posting run may not have the necessary authorizations to perform revaluation postings.
  Asset Class Settings: Certain asset classes may have restrictions on revaluation based on their configuration.
  
  Solution:
  
  
  Check Configuration: Review the configuration settings in Asset Accounting (transaction code SPRO). Navigate to:
  
  Financial Accounting (New) > Asset Accounting > Valuation > Define Revaluation.
  Ensure that the settings allow for revaluation postings as needed.
  
  
  
  Review Posting Run Type: Verify that the posting run type you are using is appropriate for revaluation. If it is not, consider using a different posting run type that supports revaluation.
  
  
  User Authorizations: Ensure that the user has the necessary authorizations to perform revaluation postings. This can be checked in the user roles and profiles.
  
  
  Asset Class Configuration: Check the configuration of the asset class involved in the posting. Ensure that it is set up to allow revaluation if that is required.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific details on the error message and related configurations.
  
  
  Testing in a Sandbox: If possible, test the posting run in a sandbox environment to identify if the issue persists and to experiment with different configurations without affecting production data.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as AS01 (Create Asset), AS02 (Change Asset), AS03 (Display Asset), and ABT1N (Transfer within Company Code) for asset management.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.