How To Fix FSH_MM_COMMON072 - Data saved successfully

SAP Error Message - Details

• Message type: E = Error

• Message class: FSH_MM_COMMON -

• Message number: 072

• Message text: Data saved successfully

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_MM_COMMON072 - Data saved successfully ?

  The SAP error message FSH_MM_COMMON072 typically indicates that data has been saved successfully, but it may also be associated with a warning or informational message rather than an actual error. This message is often encountered in the context of the SAP Fashion Management (FSH) module, particularly when dealing with master data or transactional data related to materials, styles, or other fashion-related entities.
  
  Cause:
  
  Data Validation: The message may appear after a data entry process where the system has validated the input but has also identified some conditions that may require attention.
  Business Logic: The message could be triggered by specific business rules or logic that are part of the FSH module, indicating that while the data was saved, there may be additional considerations or follow-up actions needed.
  User Actions: It may also occur due to user actions that lead to a successful save but with some warnings or notes that the user should be