How To Fix /PM0/FPP100 - Run was not found

SAP Error Message - Details

• Message type: E = Error

• Message class: /PM0/FPP -

• Message number: 100

• Message text: Run was not found

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 /PM0/FPP100 - Run was not found ?

  The SAP error message /PM0/FPP100 Run was not found typically occurs in the context of the SAP Production Planning (PP) module, particularly when dealing with the Forecasting and Planning functions. This error indicates that the system is unable to find a specific run or job that was expected to be present in the system.
  Causes:
  
  Missing Run ID: The run ID that you are trying to access may not exist in the database. This can happen if the run was deleted or never created.
  Incorrect Parameters: The parameters used to call the run may be incorrect, leading the system to look for a non-existent run.
  Authorization Issues: The user may not have the necessary authorizations to view or access the run.
  Data Consistency Issues: There may be inconsistencies in the database that prevent the system from locating the run.
  System Configuration: The system may not be properly configured to handle the specific type of run you are trying to access.
  
  Solutions:
  
  Verify Run ID: Check if the run ID you are trying to access is correct. You can do this by navigating to the relevant transaction or report where the run was created.
  Check Job Status: Use transaction codes like SM37 to check the status of background jobs. Ensure that the job related to the run was executed successfully.
  Review Parameters: Double-check the parameters you are using to call the run. Ensure they match the expected values.
  User Authorizations: Ensure that the user has the necessary authorizations to access the run. You may need to consult with your SAP security team.
  Database Consistency: If you suspect data consistency issues, you may need to run consistency checks or consult with your SAP Basis team to investigate further.
  Recreate the Run: If the run was deleted or never created, you may need to recreate it by executing the relevant planning or forecasting transaction again.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as MD61 (Create Forecast), MD62 (Change Forecast), and MD63 (Display Forecast) for managing forecasts.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for specific notes using the SAP Support Portal.
  Documentation: Review SAP documentation related to the specific module you are working with, as it may provide insights into common issues and their resolutions.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.