06613 - '-' will be set as percentage basis

SAP Error Message - Details

• Message type: E = Error

• Message class: 06 -

• Message number: 613

• Message text: '-' will be set as percentage basis

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 06613 - '-' will be set as percentage basis ?

  The SAP error message "06613 '-' will be set as percentage basis" typically occurs in the context of SAP's configuration for pricing, particularly when dealing with condition records in pricing procedures. This message indicates that a certain condition type is being set to a percentage basis, but there may be an issue with the configuration or the data being processed.
  Cause:
  
  Condition Type Configuration: The condition type may not be properly configured to handle the data being input. For example, if a condition type is expected to be a fixed amount but is being treated as a percentage, this message may appear.
  Missing or Incorrect Data: The data being processed may be incomplete or incorrect, leading the system to default to a percentage basis.
  Pricing Procedure: The pricing procedure may not be set up correctly, causing the system to misinterpret the condition type.
  Master Data Issues: There may be issues with the master data (e.g., customer master, material master) that affect how pricing is calculated.
  
  Solution:
  
  
  Check Condition Type Configuration:
  
  Go to the configuration for the condition type in transaction code SPRO.
  Ensure that the condition type is set up correctly for the intended use (fixed amount vs. percentage).
  
  
  
  Review Pricing Procedure:
  
  Check the pricing procedure assigned to the sales document or purchase order.
  Ensure that the condition types are correctly defined and that their sequence is appropriate.
  
  
  
  Validate Master Data:
  
  Review the relevant master data (customer, material) to ensure that all necessary fields are filled out correctly.
  Check for any inconsistencies that might lead to incorrect pricing calculations.
  
  
  
  Test with Different Data:
  
  Try processing the transaction with different data to see if the error persists. This can help identify if the issue is data-specific.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for more detailed information on the specific condition type and pricing procedure.
  
  
  
  Seek Support:
  
  If the issue persists after checking the above, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as VK11 (Create Condition), VK12 (Change Condition), and VK13 (Display Condition) for managing condition records.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Community Forums: Engage with SAP community forums or user groups for shared experiences and solutions from other users who may have encountered the same issue.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.