How To Fix RDM_BBY355 - Cond. types for 'Disc. Price' on 'Buy' and 'Get' side must be different

RDM_BBY355 - Overview

• Message type: E = Error

• Message class: RDM_BBY - Bonus Buy: Messages

• Message number: 355

• Message text: Cond. types for 'Disc. Price' on 'Buy' and 'Get' side must be different

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 RDM_BBY355 - Cond. types for 'Disc. Price' on 'Buy' and 'Get' side must be different ?

  The SAP error message RDM_BBY355 indicates that there is a mismatch in the condition types for 'Discount Price' on the 'Buy' and 'Get' sides of a transaction. This typically occurs in scenarios involving rebate agreements or promotions where different pricing conditions are expected for the buying and getting sides of a transaction.
  
  Cause:
  
  Condition Type Mismatch: The error arises when the condition types defined for the 'Buy' side (the price you pay) and the 'Get' side (the price you receive or discount) are not set up correctly. For example, if both sides are using the same condition type, it can lead to this error.
  
  Configuration Issues: There may be issues in the configuration of the pricing procedure or condition records that lead to this mismatch.
  Master Data Issues: The master data for the materials or customers involved may not be set up correctly, leading to the wrong condition types being applied.
  
  
  Solution:
  
  Check Condition Types: Review