How To Fix 5M358 - No new file has been created for which results can be received

SAP Error Message - Details

• Message type: E = Error

• Message class: 5M - Error Messages for Denmark

• Message number: 358

• Message text: No new file has been created for which results can be received

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 5M358 - No new file has been created for which results can be received ?

  The SAP error message 5M358, which states "No new file has been created for which results can be received," typically occurs in the context of data processing or file handling within SAP systems, particularly when dealing with batch jobs or data extraction processes.
  Cause:
  
  No Data to Process: The most common cause of this error is that there is no new data available for processing. This can happen if the data extraction job is run but there are no new records that meet the criteria for extraction.
  File Creation Issues: There may be issues with the file creation process itself, such as permissions, file path errors, or configuration issues that prevent the system from generating the expected output file.
  Job Scheduling Issues: If the job that is supposed to create the file has not been scheduled correctly or has failed to run, this can lead to the absence of the expected output file.
  Configuration Errors: Incorrect configuration settings in the job or process that generates the file can also lead to this error.
  
  Solution:
  
  Check Data Availability: Verify that there is indeed new data available for processing. You can do this by checking the relevant tables or data sources to ensure that there are records that meet the criteria for extraction.
  Review Job Logs: Check the logs of the job that is supposed to create the file. Look for any errors or warnings that might indicate why the file was not created.
  File Path and Permissions: Ensure that the file path where the output file is supposed to be created is correct and that the necessary permissions are in place for the SAP system to write to that location.
  Re-run the Job: If the job did not run successfully, try re-running it after addressing any identified issues.
  Configuration Review: Review the configuration settings for the job or process to ensure that they are set up correctly. This includes checking parameters, selection criteria, and output settings.
  Consult Documentation: Refer to SAP documentation or support notes related to the specific transaction or process you are working with for additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: Depending on the context, you may be using specific transaction codes (e.g., SM37 for job monitoring) to check job statuses and logs.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional troubleshooting steps.
  Community Forums: Consider checking SAP community forums or discussion boards for similar issues faced by other users and potential solutions they have found.
  
  If the issue persists after following these steps, it may be beneficial to engage with your SAP Basis team or SAP support for further assistance.