How To Fix MN621 - Condition records inconsistent (old arrangement currency missing)

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 621

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

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

  The SAP error message MN621, which states "Condition records inconsistent (old arrangement currency missing)," typically occurs in the context of pricing conditions in SAP, particularly when dealing with condition records for pricing in sales and distribution (SD) or materials management (MM). This error indicates that there is an inconsistency in the condition records related to currency settings.
  Cause:
  
  Missing Currency Information: The error usually arises when the condition records are expected to have a currency defined, but the currency information is missing or not properly maintained.
  Old Arrangement: The term "old arrangement" suggests that there may be legacy data or condition records that were created under a different currency setup, and the system is unable to find the necessary currency information for those records.
  Data Migration Issues: If data was migrated from an older system or if there were changes in the currency settings, it could lead to inconsistencies in the condition records.
  
  Solution:
  
  
  Check Condition Records: 
  
  Go to the transaction code VK13 (Display Condition) or VK12 (Change Condition) to review the condition records related to the pricing procedure.
  Ensure that the currency is correctly defined for each condition record.
  
  
  
  Update Currency Information:
  
  If you find that the currency is missing, you may need to create or update the condition records to include the correct currency.
  Use the transaction code VK11 to create new condition records with the appropriate currency.
  
  
  
  Review Pricing Procedure:
  
  Check the pricing procedure assigned to the relevant sales document or purchasing document to ensure that it is correctly configured to handle the currencies involved.
  
  
  
  Data Consistency Check:
  
  Run a consistency check on the condition records to identify any other potential inconsistencies. This can often be done through specific SAP reports or tools designed for data integrity checks.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to condition records and currency settings for any additional guidance or known issues.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking and updating the condition records, consider reaching out to SAP support for further assistance, especially if this is a recurring issue or if it affects multiple records.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11, VK12, VK13, and VK31 (for mass changes).
  Pricing Procedure Configuration: Understanding how pricing procedures are configured in SAP can help in troubleshooting similar issues.
  SAP Notes: Search for SAP Notes related to MN621 for any specific patches or updates that may address this issue.
  User Roles and Authorizations: Ensure that the user has the necessary authorizations to view and modify condition records.
  
  By following these steps, you should be able to resolve the MN621 error and ensure that your condition records are consistent and correctly configured.