How To Fix 29736 - BOM for document & & & & deleted

29736 - Overview

• Message type: E = Error

• Message class: 29 - Bills of Material

• Message number: 736

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

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 29736 - BOM for document & & & & deleted ?

  The SAP error message 29736, which states "BOM for document & & & & deleted," typically occurs when you are trying to access a Bill of Materials (BOM) that has been deleted or is no longer available in the system. This can happen in various scenarios, such as during production planning, material requirements planning, or when trying to view or edit a BOM.
  
  Cause:
  
  Deletion of BOM: The BOM you are trying to access has been deleted from the system.
  Incorrect Document Number: The document number you are using to access the BOM may be incorrect or does not exist.
  Authorization Issues: You may not have the necessary authorizations to view the BOM, leading to the perception that it has been deleted.
  Data Consistency Issues: There may be inconsistencies in the database or issues with data integrity that prevent the BOM from being accessed.
  
  
  Solution:
  
  Check BOM Status: Verify if the BOM has indeed been deleted. You