How To Fix FSH_PP_MD123 - Selected Profiles are still use in BOM ;reset cannot be done

FSH_PP_MD123 - Overview

• Message type: E = Error

• Message class: FSH_PP_MD - Message Class for PP Master Data

• Message number: 123

• Message text: Selected Profiles are still use in BOM ;reset cannot be done

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_PP_MD123 - Selected Profiles are still use in BOM ;reset cannot be done ?

  The SAP error message FSH_PP_MD123 indicates that the selected profiles are still in use in a Bill of Materials (BOM), and therefore, a reset cannot be performed. This typically occurs when you attempt to delete or reset a profile that is currently being referenced in one or more BOMs.
  
  Cause:
  
  Active References: The profiles you are trying to reset or delete are actively referenced in BOMs. This means that the system is preventing the action to maintain data integrity.
  Data Integrity Constraints: SAP enforces constraints to ensure that no critical data is lost or corrupted, which is why it does not allow the reset of profiles that are still in use.
  
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Identify the BOMs: Determine which BOMs are using the profiles in question. You can do this by:
  
  Using transaction codes like CS03 (Display BOM) to check the BOMs that reference the profiles.
  Running a report or using