How To Fix RDM_BBY421 - Missing scale type for total discount

SAP Error Message - Details

• Message type: E = Error

• Message class: RDM_BBY - Bonus Buy: Messages

• Message number: 421

• Message text: Missing scale type for total discount

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_BBY421 - Missing scale type for total discount ?

  The SAP error message RDM_BBY421, which indicates "Missing scale type for total discount," typically arises in the context of pricing and discount calculations in SAP systems, particularly in the Retail or Sales and Distribution (SD) modules. This error suggests that the system is unable to determine the appropriate scale type for calculating total discounts applied to a transaction.
  Cause:
  
  Missing Configuration: The scale type for total discounts may not be defined in the system. This can happen if the pricing procedure does not have the necessary settings for discounts.
  Incorrect Pricing Procedure: The pricing procedure assigned to the sales document may not include the required scale type for discounts.
  Master Data Issues: The customer or material master data may not have the necessary information related to discounts or pricing scales.
  Custom Development: If there are custom developments or enhancements in the pricing logic, they may not be handling the scale types correctly.
  
  Solution:
  
  
  Check Pricing Procedure:
  
  Go to the transaction code V/08 to review the pricing procedure.
  Ensure that the scale type for total discounts is defined and correctly assigned to the relevant pricing condition types.
  
  
  
  Define Scale Types:
  
  If the scale type is missing, you may need to define it in the configuration. This can be done in the transaction code V/06 (Define Condition Types) and V/07 (Define Scale Types).
  Ensure that the scale type is linked to the appropriate condition type for discounts.
  
  
  
  Review Condition Records:
  
  Check the condition records for the discount condition type using transaction code VK11 or VK12 to ensure that they are correctly set up and that the scale type is specified.
  
  
  
  Check Master Data:
  
  Review the customer and material master data to ensure that all necessary fields related to pricing and discounts are filled out correctly.
  
  
  
  Consult Documentation:
  
  If you are unsure about the configuration, refer to SAP documentation or consult with your SAP functional consultant for guidance on setting up pricing and discounts.
  
  
  
  Testing:
  
  After making the necessary changes, perform a test transaction to ensure that the error is resolved and that discounts are calculated correctly.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  V/08: Pricing Procedure Configuration
  V/06: Define Condition Types
  V/07: Define Scale Types
  VK11/VK12: Maintain Condition Records
  
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on configuration.
  
  
  User Exits and BAdIs: If custom logic is involved, review any user exits or BAdIs that may affect pricing calculations.
  
  
  By following these steps, you should be able to identify the root cause of the RDM_BBY421 error and implement the necessary changes to resolve it.