1: What does the Technical Job Repository do?
The Technical Job Repository in SAP S/4HANA was initially developed to support automatic (technical) background job scheduling in cloud-based SAP S/4HANA systems. SAP needed a mechanism to run certain recurring (=periodic)
background jobs automatically in every S/4HANA system, without the need for external intervention or monitoring.
2. What parameters are involved in the Technical Job Repository?
The parameter rdisp/job_repo_activate_time specifies the time cycle for the job repository activation. The job R_JR_BTCJOBS_GENERATOR runs based on the value specified in this parameter.
- 60M (60 minutes)
- 2H (2 hours)
- 0 (No activation)
This parameter works likewise as rdisp/btctime. If the aforementioned profile parameter rdisp/btctime has the value 0, the scheduler is never started.
3. How do you assign the step user for starting technical jobs with releases lower than 7.51 SP03?
There is only the option to create the stepuser manually in SU01 and assign it to the current client via report R_JR_UTIL_1. The relevant SAP Note is 2339022.
4. How do you assign the step user for starting technical jobs with releases higher than 7.51 SP03?
Note that from NW 7.51 onwards (i.e. with SAP S/4HANA On-Premise 1610), there exists a new transaction SJOBREPO_STEPUSER which allows in a user-friendly way to create and assign Default Step Users for Technical Job Repository (note 2449125).
5. How do you assign different stepuser for single job definitions in transaction SJOBREPO?
With release SAP_BASIS 7.56 and higher, it is possible to locally assign different stepusers for single Job Definitions in transaction SJOBREPO in addition to the default stepuser for all other Job Definitions.
6. How do you deactivate a job to not be started by the Technical Job Repository anymore?
Start transaction SJOBREPO and select the job that you want to deactivate.
e.g.:
SAP_REORG_APPLJOBS -> F7 (Deactivate technical job definition locally). The system prompts a message 'Do you really want to deactivate the Technical Job Definition(s) and unschedule the Background Job(s) in this client?'. By pressing 'Yes', the system prompts another message 'Do you want to record this change in a transport?'. The answer is based on the customer's internal process, if you don't want to record the change in transport, click 'No'.
Afterward, the column Custom./Deactiv. will be updated with a magic wand icon. The table STJR_JOBD_CUST will be updated with the client, technical job name, who has disabled the job, and column IS_DISABLED = X means if the technical job has been disabled.
If you would like to revert the technical job deactivation, follow the instructions below.
e.g.:
Select the job in SJOBREPO -> SAP_REORG_APPLLOG -> Shift + F4 (Revert changes to standard). The system promps a message 'Do you really want to reactivate the Technical Job Definition(s) and schedule the Background Job(s) in this client?' By pressing 'Yes', the system prompts another message 'Do you want to record this change in a transport?'. The answer is based on the customer's internal process, if you don't want to record the change in transport, click 'No'.
The entry in the table STJR_JOBD_CUST will be removed and the technical job will be triggered at the next scheduled time.
7. How do you use a different report variant for job scheduling in the Technical Job Repository?
Please follow the instructions as per SAP Note 2744380 - Technical Job Repository: Using a different report variant for job scheduling
8. What does the job status reason 'Not Relevant' mean?
In the transaction SJOBREPO whenever a job status is 'Not Relevant', double-click on the job name and check the tab Execution Terms.
Administration Client – Indicates if the job should run in administration client 000.
Business Client – Indicates if the job should run in business client 100 for customer-like systems, all clients <> 000 for internal systems.
If both checkboxes are checked, it means the job is relevant to be executed in all the clients in the system.
Programs that perform cross-client tasks usually run only in the Administration client, whereas programs that work exclusively on (application or customizing) data defined in the current client, run only in the Business
client. Some Job Definitions are designed to run in every client, for example some of the SAP_WORKFLOW* Job Definitions.
9. What does the job status reason 'Not In Scope' mean?
Job is scope-dependent: A job for a scope-dependent Job Definition will only be scheduled if an entry in table STJR_JOBD_SCOPE exists (containing the name of the current Job Definition) in the current client. This entry can be set in IMG (transaction S_YI3_39000188).
As of release SAP_BASIS 7.56, the Job Definition name and the scope state (on/off) must be set in table STJR_JOBD_SCOPE. In addition, a scope callback class can be defined by the responsible application. This class can define additional conditions which must be fulfilled for the job to be executed, for example, a certain number of entries in a specific table must be exceeded.
For further details, please check KBA 3085988 if you would to adjust the scope dependency.
10. What does the job status reason 'Inconsistency' mean?
Job Definition has a syntax error (check in SE80). There are notes that can be implemented in order to adjust the syntax, or the job definition has become obsolete on higher releases and should not be scheduled anymore.
11. What does the job status reason 'BTC User Error' mean?
In a few cases, a Job Definition is delivered with an explicit user set in field User Name in SE80 instead of (DEFAULT) and the user does not exist in the current client.
12.How do you analyze errors with regard to the Job Repository activation and report them to SAP?
You can use the transaction SLG1 and display the application logs generated by the program R_JR_BTCJOBS_GENERATOR, if there are errors recorded in the System Log attach them to the ticket.
Prior to S/4HANA 1909 FPSP02, the Technical Job Repository is active after an upgrade or update although it has been deactivated manually in the source release. How is it possible?
If you deactivate the Technical Job Repository manually with R_JR_UTIL_1, it will be activated by BTCTRNS2. As of S/4HANA 1909 FPSP02 this behavior has changed, you need to reactivate it manually after you have executed BTCTRNS2. Otherwise, the technical jobs will not be executed. More details in SAP Note 3152943.
13. How do you activate the Technical Job Repository deactivation history?
In your S/4H systems technical jobs are not executed or have not been executed for a period of time. This results in jobs not getting executed. To get an overview on where and for how long this has happened, you can check the content of the Technical Job Repository deactivation history table STJR_HISTORY. The Technical Job Repository deactivation history is available with SAP_BASIS 7.55 SP02 and SAP_BASIS 7.54 SP04.
For lower support packages, please perform the pre-implementation steps first and then implement the relevant correction instruction delivered in SAP Note 3013075.
14. How do you deactivate or reactivate a job definition in the Technical Job Repository in all clients?
The solution has been delivered as of SAP Basis 7.54 SP04 and 7.55 SP01 with SAP Note 3031444.
15. Where do I check the list of technical jobs delivered by SAP based on the S/4 HANA release?
The list of technical jobs delivered based on the S/4HANA release can be checked in the following SAP Notes:
3389524 - Jobs in the Technical Job Repository (SJOBREPO) in SAP S/4HANA 2023
3195909 - Jobs in the Technical Job Repository (SJOBREPO) in SAP S/4HANA 2022
2849364 - Jobs in the Technical Job Repository (SJOBREPO) in SAP S/4HANA 2021
2992214 - Jobs in the Technical Job Repository (SJOBREPO) in SAP S/4HANA 2020
2849402 - Jobs in the Technical Job Repository (SJOBREPO) in SAP S/4HANA 1909
2849337 - Jobs in the Technical Job Repository (SJOBREPO) in SAP S/4HANA 1809
S/4HANA 1709, S4/HANA 1610, and S4/HANA 1511 are available in the SAP Note:
2581518 - Jobs in the Technical Job Repository (SJOBREPO)