How To Fix 29735 - BOM for document & & & & changed

29735 - Overview

• Message type: E = Error

• Message class: 29 - Bills of Material

• Message number: 735

• Message text: BOM for document & & & & changed

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 29735 - BOM for document & & & & changed ?

  The SAP error message 29735 typically relates to issues with Bill of Materials (BOM) changes in the system. This error indicates that a BOM document has been changed, and it may not be in sync with the related data or processes. Here’s a breakdown of the cause, potential solutions, and related information:
  
  Cause:
  
  Concurrent Changes: The BOM might have been modified by another user or process while you were trying to access or change it.
  Locking Issues: The document may be locked due to another transaction or user session, preventing you from making changes.
  Data Inconsistency: There could be inconsistencies in the BOM data, such as missing components or incorrect configurations.
  Authorization Issues: The user may not have the necessary permissions to view or modify the BOM.
  
  Solutions:
  
  Check for Locks: Use transaction code SM12 to check for any locks on the BOM document. If another user has it locked, you may need to wait until they