How To Fix 3G658 - Runs for which no log exists were also selected

SAP Error Message - Details

• Message type: E = Error

• Message class: 3G - Payroll: International

• Message number: 658

• Message text: Runs for which no log exists were also selected

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 3G658 - Runs for which no log exists were also selected ?

  The SAP error message "3G658 Runs for which no log exists were also selected" typically occurs in the context of background job processing or when dealing with batch jobs in SAP. This error indicates that the system is trying to process or display information for jobs that do not have associated logs, which can happen for various reasons.
  Causes:
  
  Job Deletion: The job might have been deleted or canceled before the log could be created.
  Log Retention Settings: The system might be configured to delete logs after a certain period, and the logs for the selected jobs may have been purged.
  Job Execution Issues: The job may not have executed properly due to errors, leading to the absence of logs.
  Database Issues: There could be issues with the database that prevent the logs from being recorded or retrieved.
  
  Solutions:
  
  Check Job Status: Use transaction codes like SM37 to check the status of the jobs. Look for any jobs that are in a canceled or error state.
  Review Job Logs: If the job has run but does not have a log, check if there are any other related logs or messages that might provide insight into what happened.
  Adjust Log Retention Settings: If logs are being deleted too quickly, consider adjusting the log retention settings in the system configuration.
  Re-run the Job: If possible, try to re-run the job to see if it completes successfully and generates a log.
  Check for System Errors: Look for any system errors or issues that might have affected job processing. This can include checking system logs or using transaction SM21.
  Consult SAP Notes: Check the SAP Support Portal for any relevant notes or patches that might address this specific error.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SM37 (Job Monitoring), SM21 (System Log), and SLG1 (Application Log) for troubleshooting.
  SAP Documentation: Refer to SAP Help documentation for more details on job processing and error handling.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to reach out to your SAP Basis team or SAP support for further assistance.