How To Fix 61362 - & BOM explosion number(s) was(were) saved

SAP Error Message - Details

• Message type: E = Error

• Message class: 61 - Fehlermeldungen fuer Bedarfsplanung

• Message number: 362

• Message text: & BOM explosion number(s) was(were) saved

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 61362 - & BOM explosion number(s) was(were) saved ?

  The SAP error message 61362 typically relates to issues encountered during the Bill of Materials (BOM) explosion process. This error indicates that there was a problem with the BOM explosion, which is a critical step in production planning and material requirements planning (MRP) processes.
  Cause:
  The error message "61362 & BOM explosion number(s) was(were) saved" usually occurs due to one or more of the following reasons:
  
  BOM Configuration Issues: There may be inconsistencies or errors in the BOM configuration, such as missing components or incorrect item categories.
  Material Master Data: The material master data for the components may be incomplete or incorrect, leading to issues during the explosion.
  BOM Status: The BOM may be in a status that does not allow for explosion (e.g., inactive or locked).
  Authorization Issues: The user may not have the necessary authorizations to perform the BOM explosion.
  System Configuration: There may be issues with the system configuration or settings that affect how BOMs are processed.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  Check BOM Configuration: Review the BOM for the material in question. Ensure that all components are correctly defined and that there are no missing or incorrect entries.
  Verify Material Master Data: Check the material master records for all components in the BOM. Ensure that they are complete and correctly configured.
  Review BOM Status: Ensure that the BOM is active and not locked. You can check the status in the BOM management transaction (CS02 or CS03).
  Check Authorizations: Ensure that the user has the necessary authorizations to perform BOM explosions. This may require coordination with your SAP security team.
  Consult SAP Notes: Look for any relevant SAP Notes that may address known issues related to BOM explosions. You can search the SAP Support Portal for specific notes related to error 61362.
  System Configuration: If the issue persists, consult with your SAP Basis or technical team to review system configurations that may affect BOM processing.
  
  Related Information:
  
  Transaction Codes: Common transaction codes related to BOM management include:
  
  CS01: Create BOM
  CS02: Change BOM
  CS03: Display BOM
  CS11: Display BOM for a material
  
  
  BOM Types: Understand the different types of BOMs (e.g., production BOM, sales BOM) and their specific configurations.
  Documentation: Refer to SAP documentation for detailed information on BOM management and troubleshooting.
  
  If the issue continues after following these steps, it may be beneficial to engage with SAP support or your internal SAP team for further investigation.