BACKGROUND PROCESS

Importance of background process

Defining and scheduling background jobs

Monitoring the background jobs

Why we require background process

• To reducing the load on the Dialog work process

• To schedule regular activities without user intervention

• We can define the background work process in rz10 Rdisp/wp_no_btc = ##

background job can be scheduled using

• Each job requires a background process and a job may consist of one more steps

• You have to chose from the following

1)ABAP program/with or with variant

2)External command

3)External program

We can define a background job in T code SM 36

Types of job priorities

1) Class A job with target server

2) Class A job without target server

3) Class B job with target server

4) Class B job without target server

5) Class C job with target server

6) Class C job without target server

Where can we define the type of job ?

Type of job can be defined in T code RZ04 while defining the operation modesThe type of class A work process will handle only class A job.Even if it is in waiting status also it will not handle the any other job proper attention should be taken while configuring the

work process

How can we trigger background jobs

A background job can be triggered by

1) By Time

2) After the job

3) By Event

4) At operation mode

What is an event

An event is a signal stating that a predefined status in the system has been reached. The background processing system receives events and then starts the background job/jobs that is/are linked to an event.sap evt is the executable

Which will run the program .

Who triggers the process

• Every application will have a Background scheduler.which will trigger the jobs every 60sec by default.

• Where we can define it?

• Rdisp / btctime=60 sec in tcode rz 10

The background jobs are stored in the table called TBTCS & it can viewed from the T code SE11

Where do the background jobs are stored ?

ABAP PROGRAM

This is a report or a program which can be executed interactively or non-interactively . If it is interactive we need to identify interactive inputs and define them as variants

VARIANT

Variants are runtime input values which will be populated by the program.These are stored in the table TVARV.

HOW & where do we create a VARIANT

variants can be created in Tcode SA38 Specify the program name and executeSpecify the user inputs which needs to be populated during the runtimeSave the input as variant and Specify a meaningful name to the variant

EXTERNAL COMMAND

These commands are used to execute certain functionality in the system, these are executables like Br archiveBr backupBr restore etcThese can be defined in Tcode SM49 or SM69

EXTERNAL PROGRAM

When it requires a program in the external system we can use this facility. We need to specify the program, parameter and target host . Sap xpg is the executable which will run the external program

What are the standard jobs

STANDARD JOBSThe standard jobs are housekeeping jobs which needs to be performed to make the system consistent,to maintain the performance they are

sap_collector_for_job statistics : collects statistical data to analyze the average runtime of periodically scheduled jobs

sap_reorg_jobs : deletes all logs of successfully executed jobsSap_reorg_jobstatistic : reorganizes the runtime statistics of the

background jobssap_reorg_batch input : deletes process batch input session and their logs

as well as all logs for which session no longer existsap_reorg_spool : deletes outdated spool objectssap_reorg_abapdumps : deletes entries from runtime errorssap_reorg_priparams : reorganizes the print parameters

sap_ccms_moni_batch_db : system monitoring etc

HOW TO PAUSE A JOB ?

We can pause only scheduled jobs BTCTRNS 1 to pause the jobBTCTRNS 2 to resume the job

Use T code SE38 to pause and resume the jobs

BACKGROUND JOB MONITORING

By using the T-code SM37we can monitor the job status the of the process thy are(we have to select the job status in simple /extended job selection)

SCHEDULED: when we are defining the job the status will be scheduledRELEASED: The job is triggered by background schedulerREADY: The job is released from the table TBTCS and waiting for the work processACTIVE: When the job is active FINISHED: when the job is finished may be successfully or unsuccessfullyCANCELLED: when the job is cancelled

Reasons for cancelled/un successful jobs

The jobs may be cancelled for various reasons like

Programatical errorDisk overflowMax extents reachedFile not found/not readable/incorrect formatNo authorizationDependent jobs failed/events not triggered etc Click on job log to view the details of the job for the analysis