Delay in background job

Hi friends,
I have to schedule a back ground job in user-exit , that to i have to give 30 sec delay how i can i get it.
thanks and regards,
Jyoti.

DATA: job LIKE tbtcjob-jobname,
      jobcount LIKE tbtcjob-jobcount.
CLEAR: job,jobcount.
    job = 'ZBACK_MB1B'.
    JOBCOUNT = '14310400'.
CALL FUNCTION 'JOB_OPEN'
EXPORTING
    jobname                = JOB
IMPORTING
   JOBCOUNT               = JOBCOUNT
CHANGING
RET                    =
EXCEPTIONS
OTHERS                 = 4
DATA: authcknam LIKE tbtcjob-authcknam.
CLEAR: authcknam.
authcknam = sy-uname.
*params-primm = space.
CALL FUNCTION 'JOB_SUBMIT'
EXPORTING
ARCPARAMS                         =
   authcknam                         = AUTHCKNAM
    jobcount                          = JOBCOUNT
    jobname                           = JOB
LANGUAGE                          = SY-LANGU
PRIPARAMS                         = ' '
   REPORT                            = 'ZMSKA_JOB'.
DATA: sdlstrttm TYPE tbtcjob-sdlstrttm,
released LIKE btch0000-char1,
p_job_start_date type sy-datum.
sdlstrttm = sy-datum + 150.
sdlstrttm = sy-uzeit + 150.
CALL FUNCTION 'JOB_CLOSE'
EXPORTING
    jobcount                          = JOBCOUNT
    jobname                           = JOB
   SDLSTRTDT                         = p_job_start_date
   SDLSTRTTM                         = sdlstrttm
IMPORTING
JOB_WAS_RELEASED                  = RELEASED.
Is this correct plz check it out

Similar Messages

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

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.

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.

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

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

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®

BackGround Job's Spool Request is having "Waiting" "Frontend unavailable"

Hello Friends,
I am facing one problem related to Spool Request, which is generated through Scheduled Background Jobs (scheduled by funcional people).
The Background Job is having status "completed" when analyzing it. But, its associated Spool Request is showing "waiting" Status, with "Frontend unavailable" as Status Text.
Here is the brief status of that Spool Request.
28448     1      300 USER1 00:00 LP01 X_65_80      Frontend unavailable
in Detail:
Description          Value
Status:              Frontend unavailable
Last event:
Message:             Request on hold
Date:                01.07.2009
Time:                00:00:27
Job status:          On hold
Error class:         Delayed
Area:                Data transfer
Printout:            Not printed
The Setting of LP01 O/Device is as followed:
Output Device        LP01
Device Type        SWIN SWIN : Windows printing via SAPlpd
Device Class      Standard Printer
Host Spool Access Method       F F: Printing on Front End Computer
Host printer                     __DEFAULT
Moreover, the SAP User USER1 is allocated LP01 as Output Device with "Output Immediately" & "Delete After Output" checked status.
Some Background Jobs are showing the same status for this LP01.
I have a doubt on allocated O/P Device LP01.
Any Clue for this issue ?
Regards,
Bhavik G. Shroff

Hello Markus,
Here , in our Landscape , there is not Print Server. All are taking prints through, Networked Printer and their local connected Printers.
Can i configure "send to SAP Spooler for now" instead of "Print Immediately "in the Print Specification of those Background Jobs ?
Moreover, Some Background jobs are sending E-Mails with the processed Reports as an Attachments. They are showing sometime unexpected behavior, in sending emails, although there is no relation is with this Printing related issue.
When i am looking into "Overview of Send Orders" of SCOT, some Background Jobs are showing success for sending emails, and some are not showing success, even though All the recipients are same for the scheduled Background Jobs which are running on same time.
Regards,
Bhavik G. Shroff

CCMS Monitor to Pager for Failed Background Jobs

Hello Experts,
I am currently leveraging Central CCMS monitoring to alert us via email whenever a background job fails in production using the MTE Class R3BPServerSpecAbortedJobs.
I am trying to find a way that I can tweak the monitor to alert me ONLY when specific background jobs fail.
We want this alert to notify the oncall pager only when a handful of critical jobs fail. Does anyone know how I can delimit this MTE?
For example, we will be creating jobs that begin with Z_ALERT* that I will tie to an auto-react method that will email a pager.
Thanks in advance.
Bill

Hi Sundara.
From following link, you can download step by step setup information.
So please check following documents.
http://www.service.sap.com/bpm
=>Media Library=>Technical Information
=>1. Business Process Monitoring - Setup Roadmap
=>2. Setup Guide - Business Process Monitoring
Before you start setup, I recommend you to check
SAP Notes 521820 to ensure whether you already fulfill
prerequestions.
Basically what you have to do is following.
1. Describe your business process under following area.
   (T-CD DSWP =>Solution Landscape =>Solution landscape maintenance)
2. Setup BPMon session.
   (T-CD DSWP =>Operation Setup => Solution Monitoring =>
    Business Process Monitoring)
   in BPMon session, select job monitoring. And define background
   job that you want to monitor.
   In BPMon job monitoring, you can monitor, cancel, delay, duration,
   unexpected parallelization, also job log and so on.
I hope this information help you.
Best Regards
Keiji Mishima

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.).

TDMS background jobs

Dear experts,
I've met with following issue:
When processing the phase of "Determine Tables to be Excluded from the Export" in shell creation, the status of the job is always displayed as green flag (Blank), which should be shown as "execution successfully completed".
The actions I've taken:
1. I've checked the background job via SM37, related backgournd job is released, however, it's always been delayed. Well, I'm not quite sure about the reason of delay... So I deleted the job. However, the job is still shown as been scheduled in process tree.
2. Then, I executed the report CNV_TDMS_13_SHELL_EXPORT_EXCTB mannually in SE38.
3. After that, the status of job in process tree was shown as "execution successfully completed".
The question is, can I take the above steps to accellerate the export job process?
Besides, when I performed the next step "Export Exclude Tables", the same issue has been detected. However, job status cannot be shown as "execution successfully completed" in process tree after I've finished the mannual report execution.
Thanks, Jett

Hi Jett
It is not recommended to execute the underlying reports (for concerned activities) directly, except by SLO consultant. This is so because execution of an activity does not only executes the underlying report but also handles many other actions like status, log handling etc, which may not happen if the report is executed direcly.
General TDMS users are recommended to execute the activities from the process tree. Job being in the released state for long time may be system issue rather than a TDMS issue. So incase an activity is executed from the process tree but remains in the released state for long time without getting executed then we will recommend you to seek help from SAP support.
Regards
Pankaj.

Regarding Dead line monitoring & Background Job

Hi Dear PMs,
plz let me know regarding Deadline Monitoring (IP30) for Maint plan. Why it is requires? only for scheduling multiple plans at a time or is their any other reason?
What is the meaning of,
1. Interval for Call Objects
2. Rescheduling included
3. Immediate start for all in IP30 screen.
Why we need to run Back ground job? - only for scheduling open & save daily in background....or for any other reason?
requested you to giv in detail...
Thanks in Advance...
Amol.

In short, as the name suggest deadline monitoring is used to monitor deadlines so that any due activity could be done well in time. Deadline monitoring helps you to automatically schedule entries that are due within this period. With the help of Deadline Monitoring, you could schedule multiple Maintenance Plans at the same time from the same transaction with respect to Plant maintenance. For different modules it could used for different purposes. In MM/WM, it could be used for mass changing the batch status. It is also used in Workflows. W.r.t PM, Using IP10, you are able to schedule maintenance plans individually, so to reduce time delays and increase efficiency, Deadline Monitoring is used.
Using F1 help on each of these fields should be helpful.
Interval of Call Objects specify the duration for which you want to execute monitoring of due entries. For example, mentioning 1 mon here would show me all the maintenance plan due for the complete month.
Immediate start for all: You can use this indicator to show whether the maintenance plans that correspond with the selection criteria are to be scheduled immediately, or whether a list of the selected maintenance plans is to be displayed.
Rescheduling Inc: You can use the automatic deadline monitoring to schedule a maintenance plan again or for the first time. If you need to reschedule any maintenance plan after having scheduled it, this indicator must be checked:
The following link might help you understand:
http://help.sap.com/saphelp_erp60_sp/helpdata/EN/3c/abb350413911d1893d0000e8323c4f/frameset.htm
Executing in Background helps as it does not bother you to open up the ip30 screen and then print the document. The Document is printed automatically without you having to bother about it within the period u specify behind your background job settings. It could be monthly, daily, weekly, yearly etc. etc.
Edited by: Usman Kahoot on Apr 5, 2010 10:34 AM

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.

Delay in background job

Similar Messages

Maybe you are looking for