How To Fix WRF_APC705 - Purchase price generation failed for mat. &1, supplier &2, purch. org. &3

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 705

• Message text: Purchase price generation failed for mat. &1, supplier &2, purch. org. &3

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_APC705 - Purchase price generation failed for mat. &1, supplier &2, purch. org. &3 ?

  Certainly! Here's a detailed explanation for the SAP error message:
  
  SAP Error Message:
  WRF_APC705
  
  Text: Purchase price generation failed for mat. &1, supplier &2, purch. org. &3
  
  Cause:
  This error occurs during the automatic generation of purchase prices in the SAP system, typically in the context of Automatic Price Control (APC) or during the update of purchase info records or conditions. The system attempts to generate or update the purchase price for a specific material (&1), supplier (&2), and purchasing organization (&3), but fails due to one or more of the following reasons:
  
  Missing or incomplete master data: The material master, vendor master, or purchasing info record may be incomplete or inconsistent.
  Incorrect or missing condition records: The pricing conditions required to calculate the purchase price are missing or not maintained properly.
  Configuration issues: The pricing procedure or automatic price control settings are not correctly configured.
  Authorization issues: The user or background job running the price generation does not have sufficient authorization.
  Data inconsistencies: There may be inconsistencies in the data, such as invalid validity dates, currency mismatches, or missing units of measure.
  Technical issues: Problems with the background job or batch input session that processes the price generation.
  
  
  Solution:
  To resolve the error, follow these steps:
  
  
  Check Master Data:
  
  Verify that the material master record exists and is correctly maintained for the relevant purchasing organization.
  Check the vendor master data for completeness and correctness.
  Ensure that the purchasing info record for the material-vendor combination exists and is valid.
  
  
  
  Review Condition Records:
  
  Check if the relevant condition records (e.g., PB00, PB01, etc.) are maintained for the material and vendor.
  Verify validity dates, currency, and units of measure in the condition records.
  
  
  
  Check Configuration:
  
  Review the pricing procedure assigned to the purchasing document type and purchasing organization.
  Verify the Automatic Price Control (APC) settings in transaction MEK1, MEK2, or related APC customizing.
  Ensure that the system is set up to generate purchase prices automatically if required.
  
  
  
  Authorization:
  
  Confirm that the user or background job has the necessary authorizations to create or update purchase prices.
  
  
  
  Run Price Generation Manually:
  
  Try to manually generate or update the purchase price using transaction MEK2 or MEK3 to identify if the error persists.
  Check for any error messages or warnings during manual processing.
  
  
  
  Check Logs and Dumps:
  
  Review system logs (SM21), application logs (SLG1), and short dumps (ST22) for more detailed error information.
  
  
  
  Technical Checks:
  
  If the price generation is part of a batch job, check the job logs (SM37) for errors.
  Re-run the job after correcting the issues.
  
  
  
  
  Related Information:
  
  
  Transactions:
  
  MEK1 – Create Purchasing Info Record
  MEK2 – Change Purchasing Info Record
  MEK3 – Display Purchasing Info Record
  MEK5 – Automatic Price Control
  MEK6 – Conditions: Price Determination
  MEK7 – Price Analysis
  MEK8 – Price History
  
  
  
  Tables:
  
  EINA – Purchasing Info Record: General Data
  EINE – Purchasing Info Record: Purchasing Organization Data
  EKPO – Purchasing Document Item
  KONV – Conditions (Transaction Data)
  
  
  
  Notes and Documentation:
  
  Check SAP Notes related to APC and purchase price generation.
  Review SAP Help Portal documentation on Automatic Price Control and Purchasing Info Records.
  
  
  
  
  If after these checks the problem persists, consider raising a support ticket with SAP, providing detailed logs and screenshots of the error context.
  
  Let me know if you need help with specific transaction steps or further troubleshooting!