How To Fix MN358 - Condition record price determination missing for purch. doc. &, item &

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 358

• Message text: Condition record price determination missing for purch. doc. &, item &

What causes this issue?

For the requested function involving the condition record (internal
number &V3&), the system needs the condition records set up for
purchasing document &V1&, item &V2& for price determination purposes.
The system has noted in a database table that purchasing document &V1&,
item &V2&, is relevant to "subsequent settlement" accounting for
condition record &V3& of arrangement &V4&. Consequently, an appropriate
data record should have set up in the price determination facility for
purchasing document &V1&, item &V2&.
However, the system could not find the data record.
The data for purchasing document &V1&, item &V2&, has either been lost
due to a hardware fault or software error or subsequently changed.

System Response

The incoming invoice for purchasing document &V1&, item &V2&, will not
be taken into account in the function (detailed statement,
recompilation of statistics, etc.). The data created is thus incomplete
or incorrect.

How to fix this error?

For correct business volume data, the above data record relating to
purchasing document &V1&, item &V2& must be available in the system.
If necessary, contact your system administrator.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MN358 - Condition record price determination missing for purch. doc. &, item & ?

  The SAP error message MN358 indicates that the system is unable to determine the price for a purchasing document and item because the condition record for pricing is missing. This typically occurs during the procurement process when the system tries to calculate the price for a purchase order or a purchase requisition, but it cannot find the necessary pricing conditions in the system.
  Cause:
  
  Missing Condition Records: The most common cause is that the condition records for the pricing procedure have not been maintained for the specific vendor, material, or purchasing organization.
  Incorrect Pricing Procedure: The pricing procedure assigned to the purchasing document may not be set up correctly or may not include the necessary condition types.
  Vendor or Material Master Issues: The vendor or material master data may not be correctly configured, leading to the absence of relevant pricing conditions.
  Document Type Issues: The document type used for the purchase order may not be configured to use the expected pricing conditions.
  
  Solution:
  
  
  Maintain Condition Records:
  
  Go to the transaction code MEK1 (Create Condition) or MEK2 (Change Condition) to create or modify the condition records for the relevant pricing conditions.
  Ensure that you have the correct combination of vendor, material, and purchasing organization.
  
  
  
  Check Pricing Procedure:
  
  Verify that the pricing procedure assigned to the purchasing document is correct. You can check this in the configuration settings under SPRO > Materials Management > Purchasing > Conditions > Define Price Determination Process.
  Ensure that the necessary condition types are included in the pricing procedure.
  
  
  
  Review Vendor and Material Master:
  
  Check the vendor master data (transaction code XK03) to ensure that the vendor is set up correctly and that the purchasing info record exists.
  Check the material master data (transaction code MM03) to ensure that the material is set up correctly for purchasing.
  
  
  
  Check Document Type Configuration:
  
  Ensure that the document type used for the purchase order is configured to allow the use of the relevant pricing conditions.
  
  
  
  Test Pricing:
  
  After making the necessary changes, create a test purchase order to see if the pricing can now be determined correctly.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  MEK1: Create Condition Record
  MEK2: Change Condition Record
  MEK3: Display Condition Record
  XK03: Display Vendor Master
  MM03: Display Material Master
  
  
  Configuration Path: SPRO > Materials Management > Purchasing > Conditions > Define Price Determination Process
  Common Condition Types: Ensure that common condition types like PB00 (Gross Price), PBXX (Discounts), etc., are maintained.
  
  By following these steps, you should be able to resolve the MN358 error and ensure that the pricing can be determined correctly for your purchasing documents.