Background job within another background job

Hello Experts,
I have a BDC program (for BW tcode OLI7BW) which executes by scheduling a number of background jobs. This report works fine when run manually. But doesn't work if it is scheduled as a background job through SM36. The status of the job is shown as finished, but the data is not uploaded.
Is it not possible to execute a background job within another background job?
If it's possible, what could be the possible cause of error?
Thanks In Advance
Radhika

Hi Radhika,
If you are trying to upload data from a file on ur desktop to Internal table, then background job doesn't work. Always remember GUI means ur front end and all background jobs are run on application server and they dont run w.r.t ur desktop.
Kindly check it and get back to me incase of any queries.
Dont forget to reward points, if found useful.
Thanks and Regards,
Satyesh

Similar Messages

Scheduling one background job inside another

Hi All,
Is it possible to Scheduling one background job inside another.? i.e In my Z program I am calling job_open, job_submit, job_close and to execute one standard report in background. And after that I am executing my Z program itself from SE38 as Program->Execute->Background->Execute Immediately. Is this logically correct? I am asking this because I am not getting the desired result
Thanks & Regards,
Neethu.

HI,
Check the job steps in SM36.
First schedule the Standard job and in the job steps schedule the z report.
Schedule job in chain

A background job creating/instantiating another background job

Hi,
Is there any possibility in SAP, that, a background job can create/instantiate another background job ?
I have one suce requirement, and not sure if this is possible. Any inputs..
-DK

yes you can
when you create a job using SM36,there is a option for start condition
in that there is an option for After Job
just give the job name and when that job completes,this job will trigger off
http://help.sap.com/saphelp_nw04/helpdata/EN/c4/3a7fae505211d189550000e829fbbd/frameset.htm
Rohit

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

Periodic Background Jobs after another Job finishes

Hi
I have to schedule a job 'B' to run after job 'A' finishes.
When i schedule job 'B' to run after job A , it runs only once , while i need the job B to run periodically after job A finishes.
1) I cannt make job B as step 2 of job A , because job A is not scheduled by me and i cannt change that.
Can anyone tell me how to i trigger the job B periodicaly after job A finishes .
Any solution or hint would be appreciated.
Looking forward to some helpful replies from the gurus of SAP.
Regards
Purva

Dear Team,
Job ES_RPTMC_CREATE_CHANGEPOINT_AUTH ran only once where as SEC:INDX_UPDATE_FOR_STRUCT_AUTHS ran daily.
CAUSE:
“The start condition "Start after job" is internally mapped by means of "Start after event SAP_END_OF_JOB with the parameter <Jobname><Jobcount> of the predecessor". The pair <Jobname><Jobcount> is the unique key for a job.
If a job is executed periodically, the SAP_END_OF_JOB event is always triggered with different parameters.
The successor in turn waits for SAP_END_OF_JOB with just one particular parameter (this is the parameter with <Jobname><Jobcount> from the first predecessor). When the successor is rescheduled, the key fields from the next predecessor must therefore always be known in advance, something which is not always technically possible.”
SOLUTION:
This task can be completed with the new ABAP program Program BTC_EVENT_RAISE.
The program is delivered by Support Package for Basis Releases 640 and 700, and is included in the standard system in all subsequent releases.
The program is used to trigger a batch event. Existing programs do not therefore have to be changed. The BTC_EVENT_RAISE program has several parameters in the selection screen, including the event (and parameters) that is to be triggered.
PROCESS:
 Go To SM64
 Click on Create
 Create two events.
Our Case:
We created Z_ES_CP_AUTH and Z_SEC_AUTHS
 Go to SE38
 Give the event name as BTC_EVENT_RAISE
 Select Variants and click on Display
 Give the variant name as the one you created.
Our Case:
Z_ES_CP_AUTH
 Click on Create
 Give in the details for variants
 Click on attributes and give the details for attributes
 Go to the job which needs to be run first
• Select the job in released status
• Job->Change
• Step
• Add BTC_EVENT_RAISE as the last step of the job with the parameter as the variant created
Our Case:
Step: BTC_EVENT_RAISE, Parameter: Z_ES_CP_AUTH
 Go to the job which needs to be run next
• Select the job in released status
• Job->Change
• Start Condition -> After Event.
• Give the BTC_EVENT_RAISE parameter of the first job as the event of the second job.
Our Case:
After Event: Z_ES_CP_AUTH
 Save the changes.
 The jobs will start running one after the other with the given frequency.
Thanks
Joginadham U

Background Processing? how schedule job for "System Error" Message .

Hello everyone,
in sap help i have read.
http://help.sap.com/saphelp_nw04/helpdata/en/5a/f72040599a8f5ce10000000a155106/frameset.htm
PCK> Monitoring>Message Monitoring-->Background Processing
you can schedule jobs for various background processing:
●     Archiving of messages processed successfully
●     Deletion of messages that are not to be archived
●     Restarting of messages with errors
●     Rescheduling of lost messages
can anyone understand this docu?
give me some introduction, how can i define and schedule these jobs ?
thx in advance!!
best regards
Yaning

Background Processing
Prerequisites
You have started the message monitor on the initial screen of the PCK and are in Background Processing.
Features
Archiving
You require two archiving sessions to archive messages:
●     One session to write the messages to the archive
●     One session to delete the persisted messages that have been archived
To do this, you schedule an archiving job, which implicitly schedules the sessions to write to the archive and delete the archived messages.
You can define one or more rules for each archiving job; these rules contain conditions that a message must meet in order to be archived by the job. At least one of the defined rules must be met for archiving to take place.
All information that is displayed for a message in message monitoring is archived, in addition to the audit log for each message.
Deleting
A standard delete job is created automatically. It runs once a day. You can schedule additional delete jobs; however, you cannot define rules for them.
Restarting
Instead of restarting messages with errors manually with message monitoring, you can schedule a job to automatically restart these messages. This is possible for all messages for which the number of defined restart attempts has been exceeded (messages with the system error status).
You can define one or more rules for each job to restart messages; these rules contain conditions that a message must meet in order to be restarted by the job. At least one of the defined rules must be met for archiving to take place.
Rescheduling
A standard job to reschedule messages is created automatically. The job runs once a day and ensures that messages lost as a result of database failure, for example, are rescheduled. You can schedule additional rescheduling jobs; however, you cannot define rules for them.
Thx Aamir.
But I mean the messages with errors in Adapter Engine , not in Intergrations Engine.
the situation is like Naveen Pandrangi's WebLog
II. Errors in Adapter Engine [XI : How to Re-Process failed XI Messages Automatically|XI : How to Re-Process failed XI Messages Automatically]
I
Till now we have seen how to resubmit/restart message that failed in Integration Engine. One a message makes it from Integration Engine to Adapter Engine, the message is flagged as checked in Integration Engine. The status of the message in Adapter engine does not effect the processed state in Integration Engine. Now if this message was asynchronous, XI will by default try to restart the message 3 times at intervals of 5 minutes before the status of the message is changed from Waiting to System Error .
*how can i schedule a job to automatically restart these messages with errors?
best regards
Yaning
Edited by: Yaning Liu on Aug 18, 2008 1:43 PM

How to get the status of Job scheduled in Background.

Hi,
I wanted to know the status of job scheduled in Background.
I am using below FM.
BP_JOB_STATUS_GET
but what value will it reutrn after completion of the job.
That the status is complete.

Use the Table
TBTCO
to know the status
or else call the FUNCTION
BP_JOB_SELECT

Difference: Job run in foreground, job run in background and batch job

Hi Gurus,
Can you please help me to know what are the differences between job run in foreground, job run in background and batch job? Do jobs in foreground run in presentation server? Do jobs in background or batch jobs run in application server?
Thanks,
Kumar

foreground job running may cause job running crash or failed if it is too big or server is busy and it take too long time. meantime it will take one sap session.
background job will run base on request server status. and it will not take your sap session. and it will not failed normally.
and you can get the result by SM37.
my experience show that big report run in background normally faster than in foreground.
Edited by: JiQing Zhao on Sep 3, 2010 4:13 AM

How to terminate the next job step in Background job?

Hi,
I have the requirement from the user that want to terminate the next job step in the background job that currently running (Status Active).
For example, Background Job A, contains 5 job step, once the background is running, we would like Job A not run thru job step 4 and 5, just run up to job step 3.
Anyone have any idea how can I do that?
Thanks
Nattawat S.

Hi,
Try to delete instead of cancel in SM37.
To cancel and active job, select the job from SM37 and Click on STOP button in application toolbar. You can refer to your other thread for more info.
Regards

Job scheduled in background but not executed

Dear Expert, above is section of code through which i am scheduling a program to run in background. through this a job is created and is schedule(it show schedule using sm37) but it's not executed (generate output ).
Edited by: shekharamit on Jul 14, 2010 1:09 PM

See what is the status now it is showing ,
if it is canceeled see why it got cancelled?it can be because of job closed or like.
it can aslo be like there are more jobs in queue , so giver it as high priority .
Try withthis
Rajendra

HT201250 When Time Machine starts backingup, It popsup a small window that stays up the whole time it is backingup. How can I make it do its job in the background without the popup?

When Time Machine starts backingup, It popsup a small window that stays up the whole time it is backingup. How can I make it do its job in the background without the popup?

just let it do it for the first time. actually you might want to option click the little symbol next to the time representing timemachine then click verify bacups
Message was edited by: Carlo TD

Can U set breakpoint within a batch job and look at variables?

Hello friends,
I am trying to solve a problem that occurs within a program / transaction which can only be executed in background. The transaction in question is FPCOPARA and apparently this program cannot be executed in foreground.
If I understand well, we cannot set breakpoints within a background job and as a result we cannot inspect variable etc. during job execution. So the question is how to achieve the same goal within a batch job? How did you do it? As this is a standard SAP transacrtion, no program modification can be applied.
Your help is greatly appreciated.

Hi......
After u have executed ur batch job..
go to sm37 >>select ur job using checkbox>>enter 'JDBG' in transaction box and press enter
now debugger will start ..initial it will go through system code..after after a while the debugger will reach to your code and den you can debug the remaining report....
all the best
regards
vivek

Monitoring of jobs within SAP

Hi,
Can anyone tell me the ways of monitoring jobs within SAP. Please provide me some details..
Thanks..
Swetha.

Hi ,
In SM36, Background jobs can be created.
These Jobs can be monitored in SM37.
Pl.reward if useful.
Thanks,
USR

We have to stop one job when another job is running

Hi,
I have a new Requirement. There are two jobs running in background one is delta load and another one is Full load. Delta load runs for every two hours( Daily 12 loads) and full load runs on sundays(weekly only one load) for 6hrs. Now what happening is Full load and delta load are running on same time i.e when the full load is running, delta loads are also running on the same time, Full load runs for 6 hrs and 3 Delta loads runs on same time. Now we have a requirement to stop the delta loads when full load is running. Is there any posibility how to stop the delta load.
Rgds
Kishor

hi Kishor,
check this
Re: How to Cancel a ACTIVE background Job scheduled in SM37.
hope it will help you.
thanks
Sachin

How can I drag and drop a Tidal job into another group?

How can I drag and drop a Tidal job into another group? In Tidal Help, it says-
In the Jobs pane, press and hold the Ctrl key and at the same time right-click and either individually select individual jobs within a job group or drag your mouse cursor over a block of jobs that you wish to select. You can only move multiple jobs between job groups if the jobs being moved are on the same level.
Keeping the right mouse button depressed, drag the cursor to the job group that you wish to move the jobs to and release the mouse button.
When moving jobs from one job group to another, you must decide if the moved jobs keep their original job group attributes or assume the calendar and agent characteristics of its new job group.
A confirmation dialog, offers three inheritance options for the jobs moved to the "new" job group parent. Select one of the following options:
However, when I attempt to follow those instructions, it doesn't work at all and there is no indication that it's even trying (i.e., I don't see the selected job following my cursor at all and all I get is the normal menu when you right click anywhere on the screen.)
Is there another way to do this or is there a master setting that needs to be changed so that ability is enabled?
Thanks.

Go into edit mode for the job group group and just manually edit the section for Parent job/Group.
Cheers

Background job within another background job

Similar Messages

Maybe you are looking for