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

SAP Error Message - Details

• 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 fields are correctly filled (vendor, material, quantity, price, delivery date).
  Ensure the vendor and material master data are valid and active.
  Check info records and source lists if applicable.
  
  
  
  Review Authorizations:
  
  Confirm the user has the necessary roles and authorizations to create or change purchase orders.
  
  
  
  Analyze System Logs and Dumps:
  
  Use transaction SM21 (system log) and ST22 (ABAP dumps) to find detailed error information.
  Look for related short dumps or system errors at the time of PO creation.
  
  
  
  Check for Lock Entries:
  
  Use transaction SM12 to check if there are any locked entries related to the purchase order or vendor.
  Remove stale locks if necessary.
  
  
  
  Review Configuration:
  
  Verify purchasing document type settings in SPRO under Materials Management ? Purchasing ? Purchase Order ? Define Document Types.
  Check release strategy configuration if applicable.
  
  
  
  Debug or Trace the Process:
  
  If custom code or BAPIs are involved, debug the process to identify where the error occurs.
  Check user-exits or BADIs related to purchase order creation.
  
  
  
  Retry the Transaction:
  
  Sometimes, the error is transient. After checking the above, try creating the purchase order again.
  
  
  
  SAP Notes and Support:
  
  Search for SAP Notes related to WG345 for any known bugs or patches.
  If unresolved, raise a support ticket with SAP including detailed logs and steps to reproduce.
  
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  ME21N – Create Purchase Order
  ME22N – Change Purchase Order
  SM12 – Lock Entries
  SM21 – System Log
  ST22 – ABAP Dump Analysis
  
  
  
  SAP Modules:
  
  Materials Management (MM)
  Purchasing
  
  
  
  Common SAP Notes:
  
  Check SAP ONE Support Launchpad for notes referencing WG345 or purchase order creation errors.
  
  
  
  Best Practices:
  
  Always validate master data before creating purchase orders.
  Ensure proper user authorizations.
  Regularly monitor system logs for errors.
  
  
  
  
  If you provide more context (e.g., transaction used, customizations, exact scenario), I can help with a more targeted solution.