How To Fix CBGL00518 - Generation was started on &1 at &2

SAP Error Message - Details

• Message type: E = Error

• Message class: CBGL00 - GLM: Standard Messages

• Message number: 518

• Message text: Generation was started on &1 at &2

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 CBGL00518 - Generation was started on &1 at &2 ?

  The SAP error message CBGL00518 indicates that a generation process was started for a specific object (like a report or a program) at a certain time. This message typically appears in the context of the SAP Business Workflow or when dealing with the generation of certain objects in the SAP system.
  Cause:
  The error message CBGL00518 usually occurs when:
  
  A generation process is already in progress for the specified object, and a new request to generate the same object is made.
  There may be a lock on the object due to the ongoing generation process, preventing further actions until the current process is completed.
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check the Status of the Generation Process:
  
  Use transaction codes like SM37 (Job Monitoring) to check if there is an active job related to the generation process.
  Look for jobs that are currently running and see if they correspond to the object in question.
  
  
  
  Wait for Completion:
  
  If a generation process is indeed running, you may need to wait for it to complete before attempting to start a new generation.
  
  
  
  Cancel the Running Job:
  
  If the job is stuck or taking too long, you may consider canceling it. You can do this in SM37 by selecting the job and choosing the option to cancel it.
  
  
  
  Check for Locks:
  
  Use transaction SM12 to check for any locks on the object. If there are locks that are preventing the generation, you may need to release them.
  
  
  
  Review Logs:
  
  Check the application logs or system logs for any additional error messages or warnings that might provide more context about the issue.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific object type you are trying to generate for any known issues or additional troubleshooting steps.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  SM37: Job Monitoring
  SM12: Display and Delete Locks
  SLG1: Application Log
  
  
  SAP Notes: Check SAP Notes for any specific issues related to the error message CBGL00518, as there may be patches or updates that address this issue.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after following these steps, it may be beneficial to reach out to your SAP Basis team or SAP support for further assistance.