How To Fix 67_RFC517 - Condition type setting missing for contract type &1/condition type &2

SAP Error Message - Details

• Message type: E = Error

• Message class: 67_RFC - Message Class for RFC Modules

• Message number: 517

• Message text: Condition type setting missing for contract type &1/condition type &2

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 67_RFC517 - Condition type setting missing for contract type &1/condition type &2 ?

  The SAP error message 67_RFC517 indicates that there is a missing condition type setting for a specific contract type and condition type in the system. This error typically arises in the context of pricing or conditions in sales and distribution (SD) or materials management (MM) modules.
  Cause:
  The error occurs when the system tries to process a contract or pricing condition, but it cannot find the necessary configuration for the specified contract type and condition type. This can happen due to:
  
  Missing Configuration: The condition type has not been defined for the specified contract type in the pricing procedure.
  Incorrect Customization: The pricing procedure may not be correctly assigned to the contract type.
  Transport Issues: If the configuration was recently transported from another system, it may not have been fully set up or activated.
  
  Solution:
  To resolve the error, you can follow these steps:
  
  
  Check Condition Type Configuration:
  
  Go to the transaction code SPRO (SAP Reference IMG).
  Navigate to Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define Condition Types.
  Ensure that the condition type in question is defined and properly configured.
  
  
  
  Check Pricing Procedure:
  
  Still in SPRO, navigate to Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define Pricing Procedures.
  Verify that the pricing procedure assigned to the contract type includes the required condition type.
  
  
  
  Assign Pricing Procedure to Contract Type:
  
  Ensure that the pricing procedure is assigned to the relevant contract type. This can be done in the same area of SPRO under Sales and Distribution > Sales > Sales Documents > Sales Document Header > Define Sales Document Types.
  
  
  
  Check for Transport Issues:
  
  If the configuration was recently transported, check if all necessary objects were included in the transport request and that they have been properly activated in the target system.
  
  
  
  Testing:
  
  After making the necessary changes, test the transaction again to see if the error persists.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  SPRO: Access the SAP Reference IMG.
  VK11/VK12: Create or change condition records.
  
  
  Documentation: Review SAP Help documentation for detailed information on pricing procedures and condition types.
  Support: If the issue persists after checking the configuration, consider reaching out to your SAP support team or consulting SAP Notes for any known issues related to this error message.
  
  By following these steps, you should be able to identify and resolve the cause of the error message 67_RFC517 in your SAP system.