How To Fix PU035 - Header &1: Background job &2 is not scheduled in client &3

SAP Error Message - Details

• Message type: E = Error

• Message class: PU - Upgrade and Transport Log Messages

• Message number: 035

• Message text: Header &1: Background job &2 is not scheduled in client &3

What causes this issue?

The transport dispatcher program <DS:RE.RDDIMPDP>RDDIMPDP</> is not
scheduled as a background job in client &V2&.

System Response

You want to start programs in client &V2& as part of a transport. The
program RDDIMPDP normally starts these programs. RDDIMPDP needs to be
scheduled as background job &V1& in client &V2&. However, it has not
been scheduled.
The transport could not be completed.

How to fix this error?

Log on to client &V2& as user DDIC and execute the ABAP program
RDDNEWPP in the ABAP Editor (transaction SE38, or choose <LS>Tools</>
-> <LS>ABAP Workbench</> -> <LS>Development</> -> <LS>ABAP Editor </>).
This schedules the background job. The default password of user DDIC is
<LS>19920706</>.
Repeat the transport.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message PU035 - Header &1: Background job &2 is not scheduled in client &3 ?

  The SAP error message PU035 indicates that a background job is not scheduled in the specified client. This error typically arises in the context of background processing, particularly when dealing with payroll or other scheduled jobs in SAP.
  Cause:
  
  Job Not Scheduled: The background job referenced in the error message has not been scheduled in the specified client.
  Client-Specific Settings: The job may have been scheduled in a different client or not at all.
  Authorization Issues: The user may not have the necessary authorizations to view or execute the job in the specified client.
  Job Deletion: The job may have been deleted or not created due to configuration issues or errors in the job scheduling process.
  
  Solution:
  
  
  Check Job Scheduling:
  
  Go to transaction code SM37 (Job Monitoring) and check if the job is scheduled in the specified client.
  If the job is not found, you may need to schedule it again.
  
  
  
  Schedule the Job:
  
  If the job is not scheduled, you can create a new background job using transaction code SM36.
  Ensure that you specify the correct parameters and client when scheduling the job.
  
  
  
  Verify Client Settings:
  
  Make sure that the job is intended to run in the specified client. If it is meant for a different client, you may need to switch to that client to execute or monitor the job.
  
  
  
  Check Authorizations:
  
  Ensure that the user has the necessary authorizations to view and manage background jobs in the specified client. This may involve checking roles and authorizations in transaction PFCG.
  
  
  
  Consult Documentation:
  
  Review any relevant documentation or notes related to the specific job or process you are working with, as there may be specific requirements or configurations needed.
  
  
  
  Contact Support:
  
  If the issue persists after checking the above points, consider reaching out to your SAP Basis team or SAP support for further assistance.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM37: Job Monitoring
  SM36: Define Background Job
  PFCG: Role Maintenance
  
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to background job scheduling and the PU035 error.
  
  
  Documentation: Review SAP Help documentation for background processing and job scheduling for more detailed guidance.
  
  
  By following these steps, you should be able to identify the cause of the PU035 error and implement a solution to resolve it.