Do you have any question about this error?
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
Incorrect sequence when selecting the condition types.
You cannot save the condition types for the pricing procedure used.
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.
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.
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 in SAP (Transaction code:
V/08
).- Verify that the condition type is correctly defined in the pricing procedure and that it is in the correct sequence.
- Ensure that the condition type is allowed to be used at the point in the pricing procedure where it is being applied.
Review Condition Type Settings:
- Check the settings for the condition type in question (Transaction code:
V/06
).- Ensure that the condition type is active and properly configured to be used in the relevant pricing procedure.
Document Type Configuration:
- Verify that the document type being used is correctly assigned to the pricing procedure that includes the condition type.
- Check the settings for the document type in the configuration (Transaction code:
V/08
).Testing:
- After making any changes, test the pricing procedure with the relevant document type to ensure that the error no longer occurs.
Consult Documentation:
- Review SAP documentation or help resources for additional guidance on pricing procedures and condition types.
Related Information:
V/08
: Maintain Pricing ProceduresV/06
: Maintain Condition TypesV/01
: Maintain Access SequencesBy following these steps, you should be able to resolve the error message CRM_PRIDOC_COM418 and ensure that the condition type is used correctly within the pricing procedure.
Get instant SAP help. Start your 7-day free trial now.
CRM_PRIDOC_COM417
Pricing procedure &1 not found
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CRM_PRIDOC_COM416
Enter a valid pricing procedure
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CRM_PRIDOC_COM419
Pricing procedure &1: Maintain without gaps from left to right
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CRM_PRIL_CUST000
******* Messages in class CL_CRMC_PRIL_OBJ_OL *******
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.