Monday, 1 April 2019

Background Jobs notes 1:Background job processing

This post deals with


1. what is use of background processing?
2.basically what kind of job we will do?
3. how to perform the background processing?
4.how to schedule the background jobs?
5. how to monitor the background jobs?

content:

  • As a BASIS consultant, all the long running program should be execute in background job in SAP system.
  • As an administrator, It is BASIS consultant job to schedule background job, monitor Background jobs, jobs are completing correctly or not.

Why Background jobs:


  •   if a program taking a long time, to complete, At a same time 10 long running program are schedule in Dialog mode then the server will freeze.
  • maximum ideal run time for each users are defined by using the below profile parameter:

    RZ11 -->rdisp/max_wprun_ time
          after the time exceeded, the session while exit, by show the error message as


                          maximum ideal time for session exceeded

  • modifications to the profile parameter: rdisp/max_wprun_ time, can be done only when all the users have problem in the standard T-codes.
  • even if the program is customized one, scheduling background job is possible.

based on hardware resources availability, can run multiple background jobs at a time.

  • one Background job can have multiple steps (programs) 
  1. A step can contain an ABAP program.
  2. An ABAP program with variant.
  3. An external command needs to be executes.
  4. An external program   needs to be executes.          

Priority: it is possible to schedule multiple background jobs at a time, based on priority, SAP software can understand which job need to execute first.


ex: class A job will executed first -->Next -->Class B -->class C, if all jobs are scheduled at same              time with different classes(A,B,C).

Priority:


priority 1: Class A job with target servers(group).
priority 2: Class A job without target server (group).
priority 3: Class B job with target server (group).
priority 4: Class B job without target server (group).
priority 5: Class C job with target server( group).
priority 6: Class C job without target server (group).


  • in some situation very long running Background jobs need to be schedule in "CLASS C"

Tip:After certain long period of time, to avoid inconsistency & priority of background jobs only one CUA administrator need to schedule this Background job.

if all members are allowed to schedule, the Background job every one will believes that their Background jobs are important. they all will schedule the all the jobs in Class A without any thinking of finance related or priority of business process.

 in some situations Different approves are required for Class A.
ex: Approval from project manager.





Background jobs can be classified in to 2 types:                                                                                        

1. time based
2. Event based.

HOW to schedule a Background job?


General notes:

procedure to schedule a BG job:

consists of 3 parts

1. general job specification.
2.Definition of job steps.
3.Definition of start conditions.




1.in general job specification:
need to specify details like job name,job class, exec Target.

2. Definition of Job steps:

1.what ABAP program need to execute.
                   the ABAP program running in BG job, with selection screen+varient  ---> output can be seen either spool or email.
2. what external program need to execute: External command is an operating system command or script which need to execute at operating system level, can save in operating system and call from SAP system.

3.what external command need to execute: External program is also operating system command which will execute at operating system level.


3.Definition of start condition:

At what time , date these BG need to schedule.



No comments:

Post a Comment