How To Fix WG473 - System error during creation of purchase requisitions. Data was reset

WG473 - Overview

• Message type: E = Error

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

• Message number: 473

• Message text: System error during creation of purchase requisitions. Data was 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 WG473 - System error during creation of purchase requisitions. Data was reset ?

  SAP Error Message:
  WG473 - System error during creation of purchase requisitions. Data was reset
  
  
  Cause:
  The error message WG473 typically occurs during the creation of purchase requisitions in SAP MM (Materials Management) module. It indicates that a system error happened internally while processing the purchase requisition, causing the data to be reset or lost.
  Common causes include:
  
  
  Inconsistent or missing master data:  
  
  Vendor master, material master, or info records might be incomplete or inconsistent.
  
  
  
  Authorization issues:  
  
  The user might lack necessary authorizations to create or modify purchase requisitions.
  
  
  
  Custom enhancements or user exits:  
  
  Custom code (user exits, BADIs, or enhancements) triggered during PR creation might cause runtime errors or data inconsistencies.
  
  
  
  System or database errors:  
  
  Temporary system glitches, database locks, or update failures.
  
  
  
  Incorrect or missing configuration:  
  
  Missing or incorrect settings in the purchasing document types, release strategies, or account assignment categories.
  
  
  
  
  
  Solution:
  
  
  Check the detailed error log:  
  
  Use transaction SLG1 (Application Log) or