How To Fix /ISDFPS/FDP368 - Job &1 does not exist in period &2-&3

SAP Error Message - Details

• Message type: E = Error

• Message class: /ISDFPS/FDP -

• Message number: 368

• Message text: Job &1 does not exist in period &2-&3

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 /ISDFPS/FDP368 - Job &1 does not exist in period &2-&3 ?

  The SAP error message /ISDFPS/FDP368 Job &1 does not exist in period &2-&3 typically occurs in the context of SAP's Demand Planning (DP) or similar modules where jobs are scheduled for processing data. This error indicates that the system is unable to find a specific job (denoted by &1) within the specified time period (from &2 to &3).
  
  Cause:
  
  Job Not Scheduled: The job you are trying to access or process has not been scheduled for the specified period.
  Job Deletion: The job may have been deleted or not created due to some prior error.
  Incorrect Period: The specified period may not align with the job's scheduled execution time.
  Authorization Issues: There may be authorization issues preventing access to the job.
  
  Configuration Issues: There could be configuration issues in the job scheduling settings.
  
  
  Solution:
  
  
  Check Job Scheduling:
  
  Go to the job scheduling transaction (e.g., SM37) and verify if the job exists for the specified period.
  If the job does not