How To Fix WRF_APC583 - Calculated markup 2 &1 is too large; change your entry

SAP Error Message - Details

• Message type: E = Error

• Message class: WRF_APC - Messages for Operational Assortment Planning and Control

• Message number: 583

• Message text: Calculated markup 2 &1 is too large; change your entry

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 WRF_APC583 - Calculated markup 2 &1 is too large; change your entry ?

  SAP Error Message:
  
  WRF_APC583: Calculated markup 2 &1 is too large; change your entry
  
  Cause:
  This error occurs during the pricing or costing process in SAP when the system calculates a markup (usually a percentage or amount added to cost to determine price) that exceeds the allowed or configured limits. Specifically, "Calculated markup 2" refers to a second-level markup (often a secondary or additional markup step in pricing or costing procedures).
  The system detects that the calculated markup value is too large, which could be due to:
  
  Incorrect or unrealistic input values (costs, prices, or markup percentages).
  Configuration limits set in the system for maximum allowed markup.
  Errors in the pricing or costing procedure or condition records.
  Data inconsistencies or wrong master data (e.g., material master, condition records).
  
  
  Solution:
  
  
  Check Input Values:
  
  Verify the cost and price data entered.
  Ensure that the base values for markup calculation are correct and realistic.
  
  
  
  Review Markup Configuration:
  
  Check the pricing or costing procedure where the markup is calculated.
  Look at the condition records or formulas that define the markup.
  Confirm if there are any limits or validation rules restricting markup values.
  
  
  
  Adjust Markup or Limits:
  
  If the markup is genuinely too high, reduce the markup percentage or amount.
  If the markup should be allowed, adjust the system configuration to increase the allowed maximum markup.
  
  
  
  Check Master Data:
  
  Review material master data, especially pricing and costing views.
  Verify condition records for pricing or costing conditions related to markup.
  
  
  
  Debug or Trace:
  
  If the cause is unclear, use SAP debugging or pricing trace (transaction VK13 for condition records, CK13N for costing) to analyze how the markup is calculated.
  Identify where the markup exceeds limits.
  
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  CK11N / CK13N – Costing transactions to check cost estimates.
  VK11 / VK13 – Pricing condition maintenance.
  ME21N / ME22N – Purchase order creation/change (if markup is related to procurement).
  
  
  
  Tables:
  
  KONV – Condition records for pricing.
  MARC / MBEW – Material master costing data.
  
  
  
  Notes and Documentation:
  
  SAP Notes related to pricing and costing markups.
  Review SAP Help Portal for pricing and costing procedures.
  
  
  
  
  Summary:
  The error WRF_APC583 indicates that the system-calculated markup exceeds allowed limits. To resolve it, verify and correct input data, review and adjust markup configuration or limits, and ensure master data consistency. Use SAP tools to trace and debug the calculation if necessary.