How To Fix 60A057 - New request has been discarded

SAP Error Message - Details

• Message type: E = Error

• Message class: 60A - RE: Internet Application Components

• Message number: 057

• Message text: New request has been discarded

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 60A057 - New request has been discarded ?

  The SAP error message 60A057 ("New request has been discarded") typically occurs in the context of SAP's background processing or when dealing with batch jobs. This error indicates that a new request was not processed because it was discarded, often due to certain conditions not being met.
  Causes:
  
  Job Overlap: If a job is already running and a new request is submitted for the same job, the system may discard the new request to prevent conflicts.
  Job Scheduling Issues: The job may have been scheduled incorrectly or may have dependencies that are not met.
  Resource Constraints: The system may be under heavy load, leading to the rejection of new requests.
  Configuration Issues: There may be settings in the job scheduling or background processing configuration that are causing the request to be discarded.
  Authorization Issues: The user submitting the request may not have the necessary authorizations to execute the job.
  
  Solutions:
  
  Check Job Status: Use transaction codes like SM37 to check the status of background jobs. If a job is already running, you may need to wait for it to complete before submitting a new request.
  Review Job Scheduling: Ensure that the job is scheduled correctly and that all dependencies are met. Adjust the scheduling if necessary.
  Monitor System Load: Check system performance and resource usage. If the system is overloaded, consider optimizing performance or scheduling jobs during off-peak hours.
  Configuration Review: Review the configuration settings for background processing and job scheduling to ensure they are set up correctly.
  Authorization Check: Verify that the user has the necessary authorizations to submit the job. If not, work with your SAP security team to grant the required permissions.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM37 (Job Monitoring), SM36 (Job Scheduling), and SM21 (System Log) for troubleshooting.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP's support portal can provide additional insights.
  Documentation: Review SAP documentation on background processing and job scheduling for best practices and troubleshooting tips.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.