How To Fix WRF_APC575 - Enter at least markup 1 and basic purchasing price

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 575

• Message text: Enter at least markup 1 and basic purchasing price

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_APC575 - Enter at least markup 1 and basic purchasing price ?

  The SAP error message WRF_APC575: Enter at least markup 1 and basic purchasing price typically occurs in the context of pricing and conditions in purchasing or invoice verification processes, especially when dealing with automatic price determination or condition records involving markups.
  
  Cause
  
  The system expects at least one markup value (Markup 1) and a basic purchasing price to be entered for the material or condition record.
  This error usually arises when:
  
  The markup field(s) in the pricing condition or material master are left blank or zero.
  The basic purchasing price (standard price or price in the purchase order) is missing or not maintained.
  The pricing procedure or condition technique requires a markup to calculate the final price, but the markup is not provided.
  
  
  It can also occur during invoice verification or purchase order processing if the system tries to calculate the price but lacks the necessary markup or base price data.
  
  
  Solution
  
  
  Check and Maintain Markup 1:
  
  Go to the relevant pricing condition record (transaction MEK1/MEK2/MEK3 for purchasing conditions).
  Ensure that the field for Markup 1 is filled with a valid percentage or amount.
  If markup is not applicable, confirm that the pricing procedure or condition type does not require it.
  
  
  
  Maintain Basic Purchasing Price:
  
  Verify the material master record (transaction MM02) under the purchasing view.
  Ensure that the Standard Price or Moving Average Price is maintained.
  Check the purchase order or contract to confirm that a basic price is entered.
  
  
  
  Review Pricing Procedure:
  
  Check the pricing procedure assigned to the purchasing document type or vendor.
  Confirm that the condition types requiring markup and basic price are correctly configured.
  Adjust the pricing procedure if markup is not needed or make sure the markup is maintained.
  
  
  
  Invoice Verification:
  
  If the error occurs during invoice verification (transaction MIRO), verify that the purchase order or contract has the necessary price and markup data.
  Correct the purchase order or condition records as needed.
  
  
  
  
  Related Information
  
  
  Transaction Codes:
  
  MEK1/MEK2/MEK3 — Maintain Pricing Conditions
  MM02 — Change Material Master
  ME21N/ME22N — Create/Change Purchase Order
  MIRO — Enter Incoming Invoice
  
  
  
  SAP Notes and Documentation:
  
  Check SAP Notes related to pricing and markups in purchasing.
  Review SAP Help Portal documentation on pricing procedures and condition records.
  
  
  
  Common Scenario:
  
  When a company uses markups to calculate prices (e.g., adding a percentage on top of a base price), missing markup or base price data will cause this error.
  This ensures that the system can correctly calculate the final purchasing price.
  
  
  
  
  If you provide more context (e.g., transaction where the error occurs, document type, or configuration details), I can help with more specific guidance.