How To Fix FSH_POGT_WB_MSG060 - Data records have been restored.

FSH_POGT_WB_MSG060 - Overview

• Message type: E = Error

• Message class: FSH_POGT_WB_MSG - FSH_POGT_WB_MSG

• Message number: 060

• Message text: Data records have been restored.

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 FSH_POGT_WB_MSG060 - Data records have been restored. ?

  The SAP error message FSH_POGT_WB_MSG060 with the description "Data records have been restored" typically occurs in the context of the SAP Fashion Management (FSH) module, particularly when dealing with the planning and management of fashion articles.
  
  Cause:
  This error message usually indicates that there was an attempt to modify or delete data records in the system, but the system has restored the original data due to certain conditions not being met. This can happen for several reasons, including:
  
  Data Integrity Issues: The system may have detected that the changes would violate data integrity rules or constraints.
  User Authorizations: The user may not have the necessary authorizations to make changes to the data.
  Locked Records: The records being modified may be locked by another user or process, preventing changes.
  System Configuration: Certain configurations in the system may prevent modifications to specific data records.
  
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  Check User Authorizations: Ensure that the