cancel
Showing results for 
Search instead for 
Did you mean: 

Automatically restart failed background job

Former Member
0 Kudos

Hi guys,

Do you know if there is any way in ECC 5.0 to automatically restart a failed background job. Ideally I know that you wouldn't want this as you want to fix the error which caused it to fail in the first place and then reporces the job. But wanted to know if there was some way to do this ?

regards, Vikram

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi

Background processing is also suitable for activities that are scheduled to run regularly, for example

database backups or financial evaluations.

A background job consists of one or more steps. A step can be:

An ABAP programŸ An external commandŸ An external program

A job can be triggered to run:

Ÿ At a predefined date and time Ÿ At the occurrence of a predefined event

The job scheduler (ABAP program SAPMSSY2) runs in a dialog work process every rdisp/btctime seconds.

The default time setting is 60 seconds

The job scheduler checks the job-scheduling table in the database for jobs that are ready to run.

Depending on their priorities, these jobs are allocated to free background work processes on the

current server.

To start transaction SM37 (monitor jobs), choose System -> Services -> Jobs -> Job overview

or Tools -> CCMS ->Jobs -> Maintenance.

The start conditions of a job can be time based or event based.

Time based:Ÿ ImmediateŸ At date/timeŸ On a chosen workday.

Parameter rdisp/btctime specifies the time interval of the job scheduler.

Event based:Ÿ After event (optional parameters can be used to further specify events)

These can be periodic. That is, the job can be triggered every time the event occurs.

Ÿ After job (this can depend on the status of the previous job)

Ÿ At change of operation mode (for example, between day and night)

Parameter rdisp/btcname specifies which application server handles events triggered from withinR/3

New events are defined by the system administrator in CCMS. Events are either SAP events or user

events. SAP events are internal to the R/3 System and you should not trigger or modify them.

Events can be triggered:

Ÿ For testing purposes, manually in the CCMS.

Ÿ From within ABAP programs, using function module BP_EVENT_RAISE.

Ÿ From outside R/3 at operating system level, using program sapevt.

The syntax for sapevt is:

sapevt <event> [ -p <parameter> ] [ -t ] <[pf = <profile>]> | <[name = <SID>] [nr = <instance>]>

Ÿ <event> : event name as defined in the CCMS (required)

Ÿ <parameter> : parameter specified (optional)

Ÿ -t : create tracefile (optional)

Ÿ <profile> : pathname to profile (optional)

Ÿ <SID> : R/3 System name (optional)

Ÿ <instance> : R/3 System instance number (optional)

Ÿ Example: sapevt gulp name=DEV nr=00

When an event is triggered, a parameter can be specified. You can define jobs that are triggered by

the occurrence of an event with a certain parameter

Thanks

Bharathi.Ch

Edited by: Bharathi Ch on Aug 7, 2009 9:10 AM

Former Member
0 Kudos

Hi Vikram,

Yes it will be possible.You can create an event as the failure of the job and when the job fails it will trigger the event which will start the job.

Check with your ABAPer and basis.

Regards

Ashok Dalai