How To Fix JOBREPO073 - JD &1 is deactivated.Check table STJR_JOBD_CUST.

JOBREPO073 - Overview

• Message type: E = Error

• Message class: JOBREPO - Messages for Job Repository

• Message number: 073

• Message text: JD &1 is deactivated.Check table STJR_JOBD_CUST.

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 JOBREPO073 - JD &1 is deactivated.Check table STJR_JOBD_CUST. ?

  The SAP error message JOBREPO073 indicates that a job definition (JD) is deactivated in the system. This typically occurs when a job that is scheduled to run is no longer active or has been deactivated in the job repository. The message suggests checking the table STJR_JOBD_CUST for more details about the job definition.
  
  Cause:
  
  Deactivation of Job Definition: The job definition may have been manually deactivated by a user or through a system process.
  Job Repository Issues: There may be inconsistencies or issues in the job repository that lead to the job being marked as deactivated.
  Configuration Changes: Changes in configuration or settings related to job scheduling may have affected the status of the job definition.
  
  
  Solution:
  
  
  Check Job Definition Status:
  
  Use transaction code SM37 to check the status of the job. Look for the job name and see if it is indeed deactivated.
  You can also check the job definition in the job repository using transaction SM36