How To Fix MN379 - No price determination carried out for purchasing document &, item &

SAP Error Message - Details

• Message type: E = Error

• Message class: MN - Message class for subsequent settlement (Purchasing)

• Message number: 379

• Message text: No price determination carried out for purchasing document &, item &

What causes this issue?

The system needs the price determination data for purchasing document
&V1& in order to perform the function you requested relating to the
condition record with the internal number &V3&.
The system has recorded in a database table that purchasing document
&V1&, item &V2& is relevant to subsequent (end-of-period) rebate
settlement with regard to condition record &V3& belonging to rebate
arrangement &V4&. For this reason, pricing should have been carried
out.
However, no reference to the price determination data exists for
purchasing document &V1&.
A program error has probably occurred.

System Response

The invoice receipt relating to purchasing document &V1&, item &V2&
will not be taken into account when the function is performed (detailed
statement, compilation of statistics, etc.). The generated data is
consequently incomplete or incorrect.

How to fix this error?

Contact your R/3 system administrator.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MN379 - No price determination carried out for purchasing document &, item & ?

  The SAP error message MN379 ("No price determination carried out for purchasing document &, item &") typically occurs in the context of purchasing documents, such as purchase orders or purchase requisitions, when the system is unable to determine the price for a specific item. This can happen for several reasons, and understanding the cause is essential for resolving the issue.
  Causes:
  
  Missing or Incorrect Info Records: The system may not find a valid purchasing info record for the material and vendor combination.
  Missing Conditions: The pricing conditions (like discounts, surcharges, etc.) may not be maintained in the system for the relevant purchasing document.
  Material Master Data Issues: The material master may not have the necessary purchasing data set up, or it may be set to a status that prevents price determination.
  Vendor Master Data Issues: The vendor master data may not be correctly maintained, or the vendor may not be assigned to the relevant purchasing organization.
  Price Control Settings: The price control settings in the material master (e.g., moving average price vs. standard price) may not be configured correctly.
  Document Type Configuration: The document type used for the purchasing document may not be configured to allow price determination.
  Currency Issues: There may be currency conversion issues if the document currency does not match the currency of the pricing conditions.
  
  Solutions:
  
  Check Info Records: Verify that the purchasing info record exists for the material and vendor combination. If it does not exist, create or update it.
  Maintain Pricing Conditions: Ensure that the necessary pricing conditions are maintained in the condition records for the relevant material and vendor.
  Review Material Master Data: Check the material master data for the purchasing view to ensure all necessary fields are filled out correctly.
  Verify Vendor Master Data: Ensure that the vendor master data is complete and correctly assigned to the purchasing organization.
  Check Price Control Settings: Review the price control settings in the material master to ensure they are appropriate for the purchasing scenario.
  Document Type Configuration: Check the configuration of the document type used for the purchasing document to ensure it allows for price determination.
  Currency Settings: Ensure that the currency settings are correct and that there are no discrepancies between the document currency and the pricing conditions.
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like ME11 (Create Info Record), ME12 (Change Info Record), ME13 (Display Info Record), and MM02 (Change Material) to check and maintain the relevant data.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Debugging: If the issue persists, consider debugging the pricing procedure to identify where the price determination is failing.
  Consult Documentation: Refer to SAP documentation or help resources for detailed information on pricing procedures and configuration.
  
  By systematically checking these areas, you should be able to identify the root cause of the MN379 error and implement the necessary corrections to resolve it.