How To Fix 00835 - Batch input: No log available to archive

SAP Error Message - Details

• Message type: E = Error

• Message class: 00 -

• Message number: 835

• Message text: Batch input: No log available to archive

What causes this issue?

The logs selected for archiving do not have a session status "New" or
"Processed".

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?

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 00835 - Batch input: No log available to archive ?

  The SAP error message "00835 Batch input: No log available to archive" typically occurs when you are trying to archive batch input sessions, but there are no logs available for the sessions you are attempting to archive. This can happen for several reasons, and understanding the cause and potential solutions can help you resolve the issue.
  Cause:
  
  No Batch Input Sessions Created: There may not be any batch input sessions created that are eligible for archiving.
  Log Deletion: The logs for the batch input sessions may have already been deleted or not generated properly.
  Incorrect Archiving Configuration: The archiving configuration may not be set up correctly, leading to the absence of logs.
  Session Status: The batch input sessions may not be in a status that allows for archiving (e.g., they may be in a processed or error state).
  
  Solution:
  
  Check Batch Input Sessions: Verify if there are any batch input sessions available for archiving. You can do this by navigating to transaction code SM35 and checking the status of the sessions.
  Review Log Settings: Ensure that the logging settings for batch input sessions are correctly configured. You can check the settings in transaction SARA under the archiving object for batch input.
  Recreate Sessions: If necessary, recreate the batch input sessions and ensure that they are processed correctly to generate logs.
  Check for Errors: Look for any errors in the batch input sessions that may prevent them from being archived. Resolve any issues before attempting to archive again.
  Consult Documentation: Refer to SAP documentation or notes related to batch input and archiving for any specific configurations or known issues.
  
  Related Information:
  
  Transaction Codes:
  
  SM35: To manage batch input sessions.
  SARA: To manage archiving objects.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Batch Input Processing: Familiarize yourself with how batch input processing works in SAP, including session creation, processing, and archiving.
  
  If the issue persists after trying the above solutions, consider reaching out to your SAP Basis or technical support team for further assistance.