How To Fix BOM304 - Error during delete: of &1 records, &2 records were updated

SAP Error Message - Details

• Message type: E = Error

• Message class: BOM - BOMs (2)

• Message number: 304

• Message text: Error during delete: of &1 records, &2 records were updated

What causes this issue?

INCLUDE EWB_TXT_INTERNAL_ERROR1 OBJECT DOKU ID TX
Cause is an error during delete of table STZU.
INCLUDE EWB_TXT_INTERNAL_ERROR3 OBJECT DOKU ID TX

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message BOM304 - Error during delete: of &1 records, &2 records were updated ?

  The SAP error message BOM304 typically occurs when there is an issue while trying to delete a Bill of Materials (BOM) record. The message indicates that while attempting to delete a certain number of records, some records were updated, which may prevent the deletion from being completed successfully.
  Cause:
  
  Data Integrity Issues: The records you are trying to delete may be linked to other data in the system, such as production orders, purchase orders, or other BOMs. If these links exist, the system will not allow the deletion to maintain data integrity.
  Authorization Issues: The user may not have the necessary authorizations to delete certain records.
  System Locking: The records may be locked by another user or process, preventing the deletion.
  Inconsistent Data: There may be inconsistencies in the data that need to be resolved before deletion can occur.
  
  Solution:
  
  Check Dependencies: Before attempting to delete a BOM, check for any dependencies or links to other objects. You can use transaction codes like CS03 (Display BOM) to view where the BOM is used.
  Remove Dependencies: If there are dependent objects (like production orders), you may need to delete or modify those first before you can delete the BOM.
  Authorization Check: Ensure that the user has the necessary authorizations to delete BOM records. This can be checked with the help of your SAP security team.
  Unlock Records: If the records are locked, you may need to wait for the lock to be released or contact the user who has locked the record.
  Use Transaction Codes: Use transaction codes like CS02 (Change BOM) to make necessary changes or CS05 (Delete BOM) to attempt deletion again after resolving issues.
  Check for Updates: If the system indicates that records were updated, check the logs or messages to understand what was updated and address those issues.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CS01 (Create BOM), CS02 (Change BOM), CS03 (Display BOM), and CS05 (Delete BOM).
  SAP Notes: Check SAP Notes for any known issues or patches related to BOM management.
  Documentation: Review SAP documentation for BOM management to understand the relationships and dependencies involved.
  Support: If the issue persists, consider reaching out to SAP support for further assistance.
  
  By following these steps, you should be able to identify the cause of the BOM304 error and take appropriate actions to resolve it.