How To Fix MN620 - Condition records inconsistent (different old arrangement currency)

SAP Error Message - Details

• Message type: E = Error

• Message class: MN - Message class for subsequent settlement (Purchasing)

• Message number: 620

• Message text: Condition records inconsistent (different old arrangement currency)

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 MN620 - Condition records inconsistent (different old arrangement currency) ?

  The SAP error message MN620, which states "Condition records inconsistent (different old arrangement currency)," typically occurs in the context of pricing conditions in SAP, particularly when dealing with condition records for pricing, discounts, or surcharges. This error indicates that there is a mismatch in the currency used in the condition records for a specific pricing arrangement.
  Cause:
  
  
  Currency Mismatch: The primary cause of this error is that the condition records are set up with different currencies than what is expected or required for the transaction. For example, if a condition record is created in one currency (e.g., USD) and the system is trying to process it in another currency (e.g., EUR), this inconsistency will trigger the error.
  
  
  Old Arrangement Currency: This error can also occur if there are legacy or old condition records that were created with a different currency than the current arrangement or pricing procedure being used.
  
  
  Master Data Issues: Sometimes, inconsistencies in master data (like customer or material master records) can lead to this error if the currency settings do not align with the condition records.
  
  
  Solution:
  
  
  Check Condition Records: Review the condition records in the relevant pricing condition tables (e.g., KONV) to ensure that they are all set up with the correct and consistent currency. You can use transaction codes like VK13 (Display Condition) to view the records.
  
  
  Update or Delete Inconsistent Records: If you find condition records with the wrong currency, you may need to update them to the correct currency or delete them if they are no longer needed.
  
  
  Review Pricing Procedure: Ensure that the pricing procedure being used is correctly configured to handle the currencies involved. Check the configuration in the SPRO transaction under Sales and Distribution > Basic Functions > Pricing > Pricing Control.
  
  
  Check Master Data: Verify that the master data (customer, vendor, material) is set up correctly with the appropriate currency settings. This includes checking the customer master record for the sales area and ensuring that the currency matches the condition records.
  
  
  Consult Documentation: If the issue persists, refer to SAP documentation or consult with your SAP support team for further troubleshooting steps specific to your system configuration.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11 (Create Condition), VK12 (Change Condition), and VK13 (Display Condition) for managing condition records.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP Notes can provide additional insights or solutions that may not be covered in standard documentation.
  User Exits and Enhancements: If your organization has custom enhancements or user exits related to pricing, ensure that they are not causing the inconsistency.
  
  By following these steps, you should be able to identify and resolve the issue causing the MN620 error in your SAP system.