How To Fix MN070 - Not possible to determine condition basis for condition &

MN070 - Overview

• Message type: E = Error

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

• Message number: 070

• Message text: Not possible to determine condition basis for condition &

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 MN070 - Not possible to determine condition basis for condition & ?

  The SAP error message MN070, which states "Not possible to determine condition basis for condition &," typically occurs in the context of pricing and conditions in SAP, particularly when working with sales documents, purchase orders, or other transactions that involve condition records.
  
  Cause:
  The error can arise due to several reasons, including:
  
  
  Missing Condition Records: The condition record for the specified condition type may not exist in the system for the relevant combination of key fields (e.g., customer, material, pricing date).
  
  
  Incorrect Condition Type: The condition type being referenced may not be correctly configured or may not be applicable for the transaction being processed.
  
  
  Inconsistent Data: There may be inconsistencies in the master data (e.g., customer master, material master) that prevent the system from determining the correct condition basis.
  
  
  Pricing Procedure Issues: The pricing procedure assigned to the document may not include the necessary condition types or may be incorrectly configured.
  
  
  Access Sequence Problems: The access sequence