How To Fix WG345 - System error creating purchase orders. Data reset.

WG345 - Overview

• Message type: E = Error

• Message class: WG - Messages for store order and investment buy

• Message number: 345

• Message text: System error creating purchase orders. Data reset.

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 WG345 - System error creating purchase orders. Data reset. ?

  SAP Error Message:
  WG345 - System error creating purchase orders. Data reset.
  
  
  Cause:
  The error message WG345 typically occurs during the creation of purchase orders in SAP when the system encounters an unexpected issue that prevents it from completing the process. This can be due to:
  
  Data inconsistencies or missing mandatory data in the purchase order or related master data (vendor, material, info records).
  Authorization issues where the user does not have sufficient rights to create or modify purchase orders.
  System or configuration errors such as incorrect settings in the purchasing document types, release strategies, or account assignment.
  Locking or update conflicts if the purchase order is being processed simultaneously by multiple users or background jobs.
  BAPI or user-exit errors if custom enhancements or interfaces are involved in the PO creation process.
  Temporary system glitches or memory issues causing the transaction to fail and reset data.
  
  
  
  Solution:
  To resolve the WG345 error, follow these steps:
  
  
  Check the Purchase Order Data:
  
  Verify all mandatory