Background job Delay In ( sec)

Hi Experts ,
I submitted one job in background Via SM37 here i have one question.
Job is still in Active but it shows Delay ( sec ) 2,181.
Duration ( Sec) 1,999
what it means ?
Thnx .

Hi
refer the below Link:
http://help.sap.com/saphelp_nw70/helpdata/en/1d/ab3207b610e3408fff44d6b1de15e6/content.htm

Similar Messages

Background job delay due to 'ARFC' jobs running continously

Dear all,
As we are facing problem that,there is job starting with the 'ARFC'(example: ARFC:AC1F0C0D386B463CA88E8D10) which runs with all the users in the system.Thus the other background jobs even the sys monitoring jobs also goes for the delay for the longer time.This is happening from past 10 days.I m unable to trace what has got change in the system due to which ,I m facing this issue.I had checked in the job logs also, in which i didnt got any help.In that it is only mentioned owner of the job.Pls check this at the high priority as it is affecting my normal background jobs.
Thanks in advance.
Regards,
Akif

Hi akif,
jobs which are stuck at ARFC mode needs to trigger other event controlled jobs. since they are updating the Database, unless those jobs trigger this job cannot run forward so try to find what kind of jobs from the user who scheduled the job and then take the action if the jobs are related to support packages and releasing of change request then try to schedule RDD* jobs under user DDIC in 000 client
this is not due to instance consistency
regards,
kanthi

Background job delay

Hi Experts,
I have a problem. When saving production order, I need to schedule job, which runs 5 seconds after current time and changes some fields in production order.
Problem is, that this job is alwayse delayed. Sometimes it is only 10 seconds, sometimes one minute.
Can I ensure to start job in planned time without delay?
Thanks&regards,
Jirka

Hi Jirka,
While we configure the background job scheduling you must have given immediate start.Am I correct.When we specify it means that the action reaction is quick immediately.We know that the process execution within SAP is so vast that the process has to wait for a bit of time that is what the cause of the delay you can check while the process you trying to achieve in the mean time you can check SM51 or SM 50 both youo can see that the delay is just because of the work processor availabilty.To improve the performance of the process please do contact the basis team.
Hope your query resolves.
Have a best day ahead.

How to run a job in background programatically after 10 sec

Hi Forum,
Can anyone tell me How to run a job in background programatically after 10 sec..
Thanks in advance

Hi,
Here is the example code
*Submit report as job(i.e. in background)
data: jobname like tbtcjob-jobname value
                             ' TRANSFER TRANSLATION'.
data: jobcount like tbtcjob-jobcount,
      host like msxxlist-host.
data: begin of starttime.
        include structure tbtcstrt.
data: end of starttime.
data: starttimeimmediate like btch0000-char1.
* Job open
call function 'JOB_OPEN'
       exporting
            delanfrep        = ' '
            jobgroup         = ' '
            jobname          = jobname
            sdlstrtdt        = sy-datum    " You need to give the Date for execution the Job
            sdlstrttm        = sy-uzeit    " You need to give the Time for execution the Job
       importing
            jobcount         = jobcount
       exceptions
            cant_create_job = 01
            invalid_job_data = 02
            jobname_missing = 03.
if sy-subrc ne 0.
                                       "error processing
endif.
* Insert process into job
SUBMIT zreport and return
                with p_param1 = 'value'
                with p_param2 = 'value'
                user sy-uname
                via job jobname
                number jobcount.
if sy-subrc > 0.
                                       "error processing
endif.
* Close job
starttime-sdlstrtdt = sy-datum + 1.
starttime-sdlstrttm = '220000'.
call function 'JOB_CLOSE'
       exporting
            event_id             = starttime-eventid
            event_param          = starttime-eventparm
            event_periodic       = starttime-periodic
            jobcount             = jobcount
            jobname              = jobname
            laststrtdt           = starttime-laststrtdt
            laststrttm           = starttime-laststrttm
            prddays              = 1
            prdhours             = 0
            prdmins              = 0
            prdmonths            = 0
            prdweeks             = 0
            sdlstrtdt            = starttime-sdlstrtdt
            sdlstrttm            = starttime-sdlstrttm
            strtimmed            = starttimeimmediate
            targetsystem         = host
       exceptions
            cant_start_immediate = 01
            invalid_startdate    = 02
            jobname_missing      = 03
            job_close_failed     = 04
            job_nosteps          = 05
            job_notex            = 06
            lock_failed          = 07
            others               = 99.
if sy-subrc eq 0.
                                       "error processing
endif.
Regards
Sudheer

Delay in background jobs..Need some info

Hi experts,
We have a background job scheduled for every 2 hours in our system.But this job is going to delay state intermittently and not getting triggered at the right time.Could anyone tell the reason for the same and let me know the transactions I have to look in .
Regards,
Srikanth.

>
Thomas Zloch wrote:
> Oh I thought you were picking on me, so I picked back. Never mind if I got that one wrong
> Thomas
No pickiness intended. I simply meant that there may be some authorization issues with changing the priority of a job. But basis should be able to do it.
Rob

Long Delay Release Background Job

Dear Expert
We now use BI Netweaver 2004
many times background jobs have release status in long time,
so the jobs can not be active
if I change priority to A, the jobs can be active
Why I must change priority the job for active ?
How to solve this problem ?
really appreciate your help
Regards
Jeiming

1) See it in SM50 whether how many BGD processes are available (Status: Waiting) at the time of 'Release' job is waiting.
2) Suppose if you find more processes are in waiting status then check with your basis team to understand how many are available for priority A and remaining.
3) If you don't find many BGD processes then your job is waiting for availability of BGD process.
Thanks
Viswa

SIDadm locked ??? by Background job! not sure...?

Hi Folks,
We are curretnly running on SAP SCM 5.0.
<SID>adm user is getting locked by Kernel(KNL).
As per the locked time of the user, it is losked around 10 PM by KNL and there are NO users in the system yet.
As per our understanding it looks like <SID>adm is getting locked by some background job.
Any help in solving this problem is appreciated.
Thanks

Hei ....
After passing immediate start in job_close.....
In SM37 i have
Status as : canceled.
have start time
have start date.
duration as 567
delay as 60 secs.
which is better that what i have done previously....Now i get the duration time, start date, start time.
How can i escape from "canceled"?
thanks

Triggering background jobs

What is the best solution to trigger background jobs within user exits?
Currently the method I am using is quite cumbersome.
1. Create user event in SM62
2. Create background job attached to this user event.
3. Within user exit call function module BP_EVENT_RAISE using user event.
The problem I have with this approach is that in the program I have to add a 15 - 20 sec delay to handle record locking. Lets say I am in a user exit in MM02, triggering this event without the delay can lead to no records been processed.
What are other ways of implementing this solution?
Can I do a SUBMIT report VIA JOB
or CALL FUNCTION IN UPDATE TASK.

Try this way also.
In the userexit update a custom table with document number + flag (pending for process)
Create standalone program that to be scheduled like every 5 minutes (as you like ) search for this table and get all open documents (with flag eq space ) and process one by one.( Calling jobs)
This will reduced number of repetative background jobs
Say User A edit document 100 at 10.00 am and saves at 10.01 am and user B edit document 100 at 10.02 am and save it
10.03 am ( so every save if you trigger a backgound job, unncessary create jobs for same document number 10 )
a®

How to cancel the background job?

Hi,
I have schedule the backgroud job.How to cancel the background the job.
When i select the job and click on stop button, iam getting message "job is not active - cancellation not possiable".How to schedule the background job.
Regards,
T.suresh

goto sm37
SM36 Define Background Job
SM37 Background Job Overview
SM39 Job Analysis
U can Moniter the background Jobs through T code SM37
In the Simple Job Selection window enter the name of the Job and User of that Job and u can check the status of that Job like JobName, Job CreatedBy, Status, Start date, Start time Duration(sec.) Delay (sec.).

Background job status "Released"

Hi ,
I am executing standard SAP program in background and it shows the status as "Released" with "Delay" more than 3000 sec.
What is the reason I am not able to start the job with "Active" status?
Please help.
thanks & regards,
Yogita

>
Rob Burbank wrote:
> If it wre already running, the status would be active.
Rob,
Yes,Its really depends on how "Background job cofiguration" has been done in system by basis.
As i can also see the job status is only Realesed(Not active) once i ran it in background immidiately.
And once job finished it shows "Finished" status.No where "Active" status came
@Yogita:Your job is still running i guess since more than 3000Sec.so thats why it(Time) is showing in delay.
Once job is finished you will be able to see its status Finished.
I would also suggest you to Knock basis
Cheers,
Amit.

BackGround Job for Transaction VF06

Hi Experts,
We are having problems with the background Job for transaction VF06. We run this job every day except weekends but this job runs and takes only 0 sec without creating Invoices.
Allthough running this transaction Manually creates Invoice with same variant.
Kindly help me on this.
Thanks and Regards,
Neha Kapoor

Hi,
I have the seen the Log it tells:
Date       Time     Message text                                                                 Message class Message no. Message type
29.06.2008 22:00:48 Job started                                                                       00           516          S
29.06.2008 22:00:48 Step 001 started (program RV60SBAT, variant SOIE AUTO BILL, user ID GGBATCH)      00           550          S
29.06.2008 22:00:48 Job finished                                                                      00           517          S
But Invoices are not getting created.
Thanks and Regards,
Neha Kapoor

Background job executed as SAP*, need advice to change owner.

Hi all,
I'm facing an issue where my SAP background job currently has 2 job "SAP_CCMS_CPH_REORG" and "SAP_CCMS_CPH_HRCOLL" under the ownership of sap. I would like to move them away from SAP ID.
I have tried to recreate the job using sm36 (and using my ID with sap_all profile) in testing environment, but it not seem to work.
Highly appreciates any advices and/or pointers with regards to the above mention question.
Thank you.

Hi all,
Thank you for the reply but I have forgotten to add a few updates.
The issue is that I can change owner from SAP* to my ID with sap_all profile.
But, after execution,
Job with sap* owner ended successfully, with spool status marked as completed.
whereas
Job with my ID as owner ended successfully, but spool status marked as "waiting"
error mesage:
Description          Value
Status:              Frontend unavailable
Last event:
Message:             Request on hold
Date:                19.02.2009
Time:                11:57:28
Job status:          On hold
Error class:         Delayed
Area:                Data transfer
Printout:            Not printed
Apologies for the inconveniences caused.

Error when running SWN_SELSEN as background job.

Hello Gurus,
I am facing a typical problem these days.
The background job for program SWN_SELSEN is scheduled in every 5 mins. It has started to fail intermittently with the error message 'An instance of the report SWN_SELSEN is still active'. But the stange thing is that the program completes its execution in approx. 12 - 15 secs then why this kind of error it is throwing.
This error message should not come as the program completes itself in 12- 15 secs and it has more than 4 mins as free time.
Please help as this kind of failure is happenning quite frequently i.e. once in nearly every three times it executes. In a day around 100 times.
Please help.
Thanks in advance.
Neha

Hello,
I assume you've checked in SM37 to see how often it actually runs and whether perhaps two instances have been scheduled?
Also check the log in SLG1 to see if there is any clue there.
regards
Rick Bakker
Hanabi Technology

Start background Job when another is finished (NOT with the JobSteps)

Hi guys,
i need your help.
I've already searched here in forum, but i wasn't able to find a good solution.
I have this problem.
I have a program that create a background job with the FM FM JOB_OPEN.. SUBMIT report with parameters .. JOB_CLOSE.
I want that if i run this report again (20 secs after for example) it does:
- Check if there is an already running Job with the same name (means with state 'R') (This task is simply, with a select on TBTO table)
- If it's found, it have to create a new job with the same name that starts automatically AFTER the first running job is finished (don't care about the end-state of the first job).
I've already tried with pred_jobcount & PRED_JOBNAME parameters of the JOB_CLOSE FM but it doesen't works!
The JOB_CLOSE, creates a job in Planned state. But when the first Job is finished, the second job(Planned) doesen't start automatically.
In this scenario, i CANNOT use endless loops (wait until the first job is finished and then submit the second) Job-steps (one job that contains multiple steps) events (i have to start only one job after the predecessor is finished), because this report could be run many times and each job should be collected like a "stack" (only when the first job is finshed the second "registered" should be started and so on, until the aren't more planned jobs).
<REMOVED BY MODERATOR>
Thx a lot for your help.
Andrea
Edited by: Alvaro Tejada Galindo on Jun 12, 2008 12:19 PM

Hi Veda
i can tell u but ... some reward points are very appreciated ....
I'm joking (of course)
Here the question:
I have a program (called A) that submit a new program (called B) with the JOB_OPEN .. submit JOB_CLOSE. The program B should start only if another program B (called before for example) is finished.
Here the solution.
I add a parameter (with no-display clausole) to the program B. In this parameter i pass to the program, the job number returned by the JOB_OPEN function.
When i create the JOB with the function, the "jobname" parameter is set with value 'G_DELIVERY' (Here u can change the name of the job as u want : this is the jobname that u see in SM37 transaction).
In the start-of-selection of program B i put a "waiting" procedure like this :
First i save a timestamp of system-date and system-time (called for example r_date and r_time)
select from table TBTCO all the jobs called "G_DELIVERY" with jobnumber <> from the jobnumber parameter (that means exclude itselfs) with status running ('R') -> that have startdate /starttime less than the r_date and r_time <- (this is the key of the selection that solve the problem).
if it is found (means there is another running job started before this one).
wait up to 60 seconds. "for example
repeat the selection.
endif.
When the job called before ends, this one programs exits from the loop and continues. If u submit more programs "B", they'll works like a stack.
I should say to u just one thing.... I solved my problem in another way (because i've changed the logic so this problem was no more) so i didn't implemented that logic, but it should works very good.
Try it and tell me!
Bye
Andrea

Long time for execution for scheduled CIF background jobs

Hi,
we hv schedlued CIF background job to be run daily around 10.30 PST.
there is large variation for the time required for execution of this job.
on 26 Dec, it took approx 48000 seconds while regular average is 120 seconds only.
today, despite past of 6000 seconds, the job is still in ACTIVE stage.
can anyone know why such long delay for such jobs?
how can i reduce its execution time (as one of case in a week)?
rgds/Jay

Hi Jay,
A few obvious things to look for:
1. Multiple CIF activation jobs running at the same time
2. Large change in the master data, eg new plant, new Material Masters, new customers, etc etc.
3. Conflicts with other non CIF programs that may be going after the same data
4. Communication degradation between the OLTP and SCM clients
Normally you refer such questions to someone on your Basis team, or perhaps your DBA. They can turn on tracing tools that can track the changes in your environment that may be contributing to the changes in run time.
Regards,
DB49

Background job Delay In ( sec)

Similar Messages

Maybe you are looking for