How To Fix 61367 - BOM explosion number & has been flagged for deletion

SAP Error Message - Details

• Message type: E = Error

• Message class: 61 - Fehlermeldungen fuer Bedarfsplanung

• Message number: 367

• Message text: BOM explosion number & has been flagged for deletion

What causes this issue?

BOM explosion number &V1& exists already with deletion mark.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

BOM explosion number can be retrieve over the Menu Choose -> All deleted
entries and Function Retrieve.
BOM explosion numbers which are marked for deletion and no further usage
can be deleted with report RMMDSN01.

Procedure for System Administrators

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 61367 - BOM explosion number & has been flagged for deletion ?

  The SAP error message "61367 BOM explosion number & has been flagged for deletion" typically occurs in the context of Bill of Materials (BOM) processing. This message indicates that the BOM explosion number you are trying to use has been marked for deletion, which means that it is no longer valid for processing.
  Cause:
  
  Flagged for Deletion: The BOM explosion number has been explicitly marked for deletion in the system. This could happen due to a change in the product structure, a decision to discontinue a product, or a data cleanup process.
  Data Integrity Issues: There may be inconsistencies in the BOM data, leading to the system flagging certain entries for deletion.
  User Actions: A user with the appropriate permissions may have flagged the BOM for deletion, either intentionally or accidentally.
  
  Solution:
  
  Check BOM Status: Verify the status of the BOM explosion number in the BOM master data. You can do this by navigating to the BOM transaction (e.g., CS03) and checking the status of the BOM.
  Unflag the BOM: If the BOM is indeed flagged for deletion and you need it, you can unflag it. This typically requires access to the BOM maintenance transaction (e.g., CS02) where you can change the status of the BOM.
  Create a New BOM: If the BOM is no longer needed and you cannot unflag it, consider creating a new BOM with the required components and structure.
  Consult Documentation: Review any documentation or change logs to understand why the BOM was flagged for deletion. This can help prevent similar issues in the future.
  User Permissions: Ensure that the user attempting to access or modify the BOM has the necessary permissions to do so.
  
  Related Information:
  
  Transaction Codes: Common transaction codes related to BOM management include:
  
  CS01: Create BOM
  CS02: Change BOM
  CS03: Display BOM
  CS11: BOM for a Material
  
  
  BOM Types: Understand the different types of BOMs (e.g., single-level, multi-level) and how they are used in your organization.
  SAP Notes: Check SAP Notes for any known issues or patches related to BOM processing that might address this error.
  User Training: Ensure that users are trained on BOM management processes to minimize accidental deletions or changes.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in BOM management.