How To Fix MN142 - Inadmissible condition type in document conditions (Please check)

MN142 - Overview

• Message type: E = Error

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

• Message number: 142

• Message text: Inadmissible condition type in document conditions (Please check)

What causes this issue?

The settlement program has created a settlement document and checked
it. The document conditions created within the framework of price
determination contain a condition record of condition class &V3& and
belonging to condition type &V2& under item number &V1&.
Only the condition class 'C' ("subsequent settlement") or the classes
'D' or 'G' (taxes) are permitted.

System Response

Settlement accounting cannot take place.

How to fix this error?

In Customizing, check whether condition class 'C' ("subsequent
settlement") is set for condition type &V2& for application &V4&. Check
the calculation schema for inadmissible condition types.
INCLUDE 'NA_CUST_MAINTAIN' OBJECT DOKU ID TX LANGUAGE EN

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

<DS:SIMG.SIMG_CFMENUOLMEKONDT>Set up condition technique</>
ENDIF
Otherwise, it is likely that a program error has occurred. Contact your
system administrator.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MN142 - Inadmissible condition type in document conditions (Please check) ?

  The SAP error message MN142 ("Inadmissible condition type in document conditions (Please check)") typically occurs in the context of pricing and condition records in SAP, particularly when dealing with sales documents, purchase orders, or other transactional documents that involve pricing conditions.
  
  Cause:
  The error message MN142 can be triggered by several factors, including:
  
  
  Invalid Condition Type: The condition type used in the document may not be valid for the specific transaction or may not be configured correctly in the system.
  
  
  Condition Records Missing: The condition type may not have any valid condition records maintained in the system for the relevant combination of key fields (e.g., customer, material, pricing date).
  
  
  Inconsistent Configuration: There may be inconsistencies in the configuration of the pricing procedure, such as missing or incorrectly defined condition types in the pricing procedure.
  
  
  Document Type Restrictions: Certain condition types may be restricted for specific document types or may not be allowed in the current context.
  
  
  User