Do you have any question about this error?
Message type: E = Error
Message class: BL - Application Log
Message number: 268
Message text: &1 logs deleted in &2 background jobs
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
You chose the option "Schedule Background Jobs". The selected logs are
deleted using parallel background jobs whose name matches the pattern
DEL_APP_LOGS_<(><<)>date><(><<)>time>_<(><<)>run number>. All jobs are
executed at the time you define.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message BL268 indicates that logs for background jobs have been deleted. This message typically arises when the system has removed logs for background jobs that are no longer needed or have exceeded a certain retention period. Here’s a breakdown of the cause, potential solutions, and related information:
Cause:
- Log Retention Policy: SAP systems have a log retention policy that automatically deletes logs after a certain period or when the logs exceed a specific size.
- Manual Deletion: Logs may have been manually deleted by an administrator or through a scheduled job that cleans up old logs.
- System Configuration: The system may be configured to delete logs based on certain criteria, such as job completion status or age of the logs.
Solution:
- Check Log Retention Settings: Review the log retention settings in your SAP system. You can do this by navigating to the relevant configuration settings in transaction codes like
SM37
(for job monitoring) orSARA
(for archiving).- Adjust Retention Period: If the retention period is too short, consider extending it to retain logs for a longer duration. This can be done in the system settings.
- Review Deletion Jobs: Check if there are any scheduled jobs that are set to delete logs. You can find this in transaction
SM37
by filtering for jobs that might be responsible for log deletion.- Recreate Logs: If the logs are critical for auditing or troubleshooting, consider rerunning the background jobs to regenerate the logs if possible.
- Consult Documentation: Refer to SAP documentation or notes related to background job logging and retention policies for more detailed guidance.
Related Information:
SM37
: Monitor background jobs.SARA
: Archive administration.SLG1
: Application log display.If the issue persists or if you need further assistance, consider reaching out to your SAP Basis team or SAP support for more tailored help.
Get instant SAP help. Start your 7-day free trial now.
Feature | Free Access | Free Trial |
---|---|---|
Basic SAP error explanation | ![]() |
![]() |
Step-by-Step Usage Guide | ![]() |
![]() |
Interactive SAP Coach Assistance | ![]() |
![]() |
AI Troubleshooting for T-Code Errors | ![]() |
![]() |
BL267 Long run task detected; start/continue in background
What causes this issue? It can take a long time to delete a large number of app...
BL264 Cannot lock log &1 (deadlock)
What causes this issue? The current program, called using the ABAP statement SU...
BL269 Error &1 when scheduling the background jobs
Self-Explanatory Message Since SAP believes that this specific error message is ...
BL270 Background jobs created but not released
Self-Explanatory Message Since SAP believes that this specific error message is ...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.