How To Fix 3G657 - No application log was written for the selected runs

SAP Error Message - Details

• Message type: E = Error

• Message class: 3G - Payroll: International

• Message number: 657

• Message text: No application log was written for the selected runs

What causes this issue?

You attempted to select the application log for the selected run.
However, the run has the incorrect status.
When posting the payroll results to accounting, the application log is
generated only for runs with the status 41 (document transfer failed),
65 (reversal failed), or 91 (deleted) and therefore could not be
transferred to accounting successfully.

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 3G657 - No application log was written for the selected runs ?

  The SAP error message "3G657 No application log was written for the selected runs" typically indicates that there are no application logs available for the specific runs you are trying to access. This can occur in various scenarios, such as during batch job processing or when executing certain transactions.
  Causes:
  
  No Logs Generated: The application did not generate any logs for the selected runs. This can happen if the process completed without any issues or if logging was not enabled for that particular process.
  Log Deletion: The logs may have been deleted or archived, making them unavailable for the selected runs.
  Authorization Issues: The user may not have the necessary authorizations to view the application logs.
  Incorrect Selection: The selection criteria used to retrieve the logs may not match any existing logs.
  Technical Issues: There could be underlying technical issues with the logging mechanism in SAP.
  
  Solutions:
  
  Check Process Completion: Verify if the process you are checking for actually completed successfully and whether it was supposed to generate logs.
  Review Selection Criteria: Ensure that the selection criteria you are using to retrieve the logs are correct. Double-check the date, time, and other parameters.
  Check Authorizations: Make sure that you have the necessary authorizations to view application logs. You may need to consult with your SAP security team.
  Look for Archived Logs: If logs have been archived, check the archive storage to see if the logs can be retrieved from there.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error message or provide additional troubleshooting steps.
  Technical Support: If the issue persists, consider reaching out to your SAP Basis team or SAP support for further investigation.
  
  Related Information:
  
  Transaction Codes: You can use transaction codes like SLG1 (Application Log) to view logs, but ensure that you have the correct selection criteria.
  Logging Configuration: Review the logging configuration for the specific application or process to ensure that logging is enabled.
  SAP Documentation: Refer to SAP documentation for more details on application logging and troubleshooting related issues.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.