How To Fix BOM618 - No suitable logs exist for today's date

SAP Error Message - Details

• Message type: E = Error

• Message class: BOM - BOMs (2)

• Message number: 618

• Message text: No suitable logs exist for today's date

What causes this issue?

You want to display the logs for today's BOM functions. However, you
have not carried out any functions for which the system creates a log.
The system only creates a log when you carry out one of the following
functions:
Fix order BOMs (single or multi-level)
Material replacement

System Response

The system checks whether a log exists with a corresponding internal
object identifier for your user name on today's date. If this is not
the case then the system does not show any log.

How to fix this error?

If you want to carry out a general log search, select <LS>Extras ->
Logs -> All logs</> (Transaction <ZH>SLG1</>).

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message BOM618 - No suitable logs exist for today's date ?

  The SAP error message BOM618 ("No suitable logs exist for today's date") typically occurs in the context of Bill of Materials (BOM) processing, particularly when trying to access logs related to BOM changes or evaluations. This error indicates that there are no logs available for the specified date, which can happen for several reasons.
  Causes:
  
  No Changes Made: If no changes were made to the BOM on the specified date, there will be no logs to display.
  Log Deletion: Logs may have been deleted or purged based on system settings or retention policies.
  Incorrect Date: The date being queried may not correspond to any activity in the system.
  Authorization Issues: The user may not have the necessary permissions to view the logs.
  System Configuration: The logging configuration may not be set up correctly, leading to no logs being generated.
  
  Solutions:
  
  Check for Changes: Verify if any changes were made to the BOM on the date in question. If not, this error is expected.
  Adjust Date: Ensure that you are querying the correct date. You may want to check logs for a different date where changes were made.
  Review Log Settings: Check the system configuration for logging settings. Ensure that logging is enabled for BOM changes.
  User Permissions: Confirm that the user has the necessary authorizations to view BOM logs. If not, contact your SAP administrator to adjust permissions.
  Consult System Administrator: If the issue persists, consult with your SAP Basis or system administrator to investigate further. They can check for any system issues or configurations that might be affecting log generation.
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like CS03 (Display BOM) or CS12 (BOM Comparison) to view BOM details and changes.
  Log Tables: Check relevant log tables in the SAP database, such as STPO (BOM items) or STPU (BOM usage), to see if any entries exist.
  SAP Notes: Look for SAP Notes related to BOM logging issues, as they may provide specific fixes or patches for known problems.
  
  If you continue to experience issues, consider reaching out to SAP support for further assistance.