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

SAP Error Message - Details

• 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 Authorizations: The user may not have the necessary authorizations to access or use the specified condition type.
  
  
  Solution:
  To resolve the MN142 error, you can take the following steps:
  
  
  Check Condition Type Configuration:
  
  Go to the transaction code V/06 (for sales) or V/08 (for purchasing) to review the configuration of the condition type.
  Ensure that the condition type is correctly defined and is part of the relevant pricing procedure.
  
  
  
  Review Condition Records:
  
  Use transaction code VK11 (for sales) or VK31 (for purchasing) to check if there are valid condition records for the condition type in question.
  If records are missing, create the necessary condition records.
  
  
  
  Examine Pricing Procedure:
  
  Check the pricing procedure assigned to the document type in question (transaction code V/08).
  Ensure that the condition type is included in the pricing procedure and is set up correctly.
  
  
  
  Check Document Type Settings:
  
  Verify that the document type being used allows the condition type in question. This can be checked in the configuration settings for the document type.
  
  
  
  User Authorizations:
  
  Ensure that the user has the necessary authorizations to access and use the condition type. This can be checked with your SAP security team.
  
  
  
  Consult SAP Notes:
  
  Check for any relevant SAP Notes that may address known issues or provide additional guidance related to the MN142 error.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11, VK31, V/06, V/08, and V/02 for condition maintenance and pricing procedure configuration.
  Documentation: Review SAP documentation or help files related to pricing conditions and procedures for a deeper understanding of how they work.
  SAP Community: Engage with the SAP Community or forums for additional insights and solutions from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the root cause of the MN142 error and implement the necessary corrections to resolve it.