How To Fix CRM_PRIDOC_COM418 - Use condition type &1 in accordance with sequence of pricing procedure &2

CRM_PRIDOC_COM418 - Overview

• Message type: E = Error

• Message class: CRM_PRIDOC_COM - Pricing Call

• Message number: 418

• Message text: Use condition type &1 in accordance with sequence of pricing procedure &2

What causes this issue?

Incorrect sequence when selecting the condition types.

System Response

You cannot save the condition types for the pricing procedure used.

How to fix this error?

Ensure that the condition types that you assign in the customizing are
in the same sequence as in the underlying pricing procedure.
For example, it is not possible to use a condition type in column 2 that
is maintained in the pricing procedure before the condition type from
column 1.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CRM_PRIDOC_COM418 - Use condition type &1 in accordance with sequence of pricing procedure &2 ?

  The SAP error message CRM_PRIDOC_COM418 indicates that there is an issue with the use of a specific condition type in the pricing procedure. This error typically arises when the condition type being used is not in accordance with the defined sequence of the pricing procedure. Here’s a breakdown of the cause, potential solutions, and related information:
  
  Cause:
  
  Incorrect Condition Type Usage: The condition type specified in the error message (&1) is being used in a way that does not align with the sequence defined in the pricing procedure (&2).
  Pricing Procedure Configuration: The pricing procedure may not be configured correctly to allow the specified condition type at the point in the sequence where it is being applied.
  Document Type Settings: The document type being processed may not be set up to use the specified pricing procedure, leading to conflicts in condition type application.
  
  
  Solution:
  
  
  Check Pricing Procedure Configuration:
  
  Go to the configuration settings for the pricing procedure