Schedule PC after Job

I scheduled PC after Job. It ran fine for only one day. I want to run PC daily after certain Job. How to achieve this?
Thanks in advance

Raj, I think you will need to change the Start variant of your Process Chain to start "After event". When you do this, you will see the Periodic Flag check-box.
Then create an ABAP program to trigger the event.
See this link:
How-to trigger a process chain using ABAP?
Next, in your job, add a step at the end to call this ABAP program so that when the job finishes, it will trigger your Process Chain will start.
Hope this helps, and sorry for the confusion

Similar Messages

Scheduling a program in background with after job condition

Hi experts,
Is there a way to schedule a background job wherein it will be run every after another job? I've tried defining it on sm36 > start condition> After job> I stated the job name >check start status dependent. But it only run once even if the job which it is dependent on is scheduled everyday.
Thank you in advance!

This is (or was) a well known issue, the option "after job" cannot be set to periodic. Theres lots of threads about this and several alternatives solutions.
Please search before posting
Regards
Juan

Want to schedule a Job (Strt Cond after JOB which should be periodically !!

Transactions : SM36 SM37 SM37C SM62 S64 SE38
Requirement
JOBA should execute program PROG1 with variant VARPROG1 in background everyday @ 10 AM.
JOBB should execute program PROG2 with variant VARPROG2 in background after JOBA
JOBC should execute program PROG3 with variant VARPROG3 in background after JOBB
JOBD should execute program PROG4 with variant VARPROG4 in background after JOBC.
When i schedule the above jobs for one day ..It works fine !!
We Require when JOBA scheduled daily / JOBB / JOBC / JOBD should should follows,
which will not happen with a option : "Start Condition : After a JOB"
irrespective technical i scheduled 1st job daily and JOBB / JOBC / JOBD as mentioned above. Result : !st dya all jobs got executed and 2nd day only 1st job got released ans got executed.
How can we acheive this ??
Rgds

Hi,
You follow the below process.
1) Define a BG job in your system with Daily Frequency and have four variants in that jobs such a way.
Step-1 ---program PROG1 with variant VARPROG1
Step -2 ---program PROG2 with variant VARPROG2
Step-3 - program PROG3 with variant VARPROG3
Step -4 program PROG4 with variant VARPROG4
If you define the job in this way, this will ensure that Prog -2 will only start when Prog -1 will be over and similarly other will also follow the sequence and in this way you achieve the Daily frequency also.
With Regards,
Saurabh

Scheduling jobs with condition-after job programatically

Hi,
Could anybody please tell me how can we schedule jobs from programs(prgramatically) with condition-start after job(after a particular job completed) like we have the same option in sm36.
Thanks,
Rahul.

Hello Rahul,
Check the following Link Page Number 41.
"Sample Program: Wait for Predecessor Job with
JOB_CLOSE"
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCDWBLIB/BCDWBLIB.pdf
Regards,
Abhishek Jolly

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

Schedule a background job

Hi All,
I have an urgent query here regarding the Bakcground job.
Let's say I need to schedule a background job on hourly basis to fetch the data.
If first job runs more than 60 minutes, then will the second job will fetch the data.
What will happen in this scenario?
Thanks
Neeraj Manocha

My question is............
Let's say, I have a SAP standard table. In which our transactional data stores. I have also maintained my our database and build a program (i.e. Ztest) to fetch the data from the SAP standard table and store into my own database.
So I schedule a background job for the program (Ztest) to fetch the data. I schedule this job on hourly basis.
once first job will be runnig it will create one more instance to run after one hour.
Here my question is...
What if first job schedule on 1pm and runs for more than 60 mins (let's say it takes 90 mins to complete)?
Till what time it will fetch data (either till 1pm or 1pm +90 mins)?
If it fetch the data till 1pm +90 mins, then when second job will start and from what time it will start to fetch the data.
Hope this clears.
Thanks
Neeraj Manocha

How to schedule a background Job based on events

Hi,
We are on 4.6 C.
We have a background job that has two ABAP programs.
We need to start the 2nd ABAP program only after the first one has run successfully.
If the second ABAP program does not run, the the job should have a status "FINISHED".
Help appreciated.
Thanks
Mala

Hi,
How to schedule a background Job based on events,please refer to the follow SAP help:
You can use events that have already been defined, or you can create new events for scheduling background jobs.
If you wish to use new events, do the following to implement the event scheduling:
Define and transport the event as a user event with transaction SM62.
You must define only event IDs; event arguments are not defined in the R/3 System. Instead, you specify event arguments when you schedule a job to wait for an event and when you trigger the event.
If you define a new event, you must also transport it to your production systems. The event transaction does not have a connection to the transport system. Instead, you must create a transport request for the event yourself.
Do this to transport an event:
Create a transport request.
Start the editor in the transport request and enter the following:
R3TR TABU <table name> where table name is BTCSEV for a system event ID, BTCUEV for a user event ID.
Press F2 with the cursor on the table name to call up the screen for specifying the table entries to transport. In this screen, enter the event IDs that you have created.
Save and release the transport request. Ensure that it is imported into your production system(s).
To trigger an event, add:
the function module BP_EVENT_RAISE to your ABAP program, or
the program SAPEVT to your external script, batch file, or program.
When your programs execute these keywords, an event will be triggered in the R/3 background processing system. The event-based scheduler is started immediately. It in turn starts all jobs that were waiting upon the event, subject to normal background processing restrictions, such as the requirement that the job has been released to start.
Schedule the jobs that are to run when your events are triggered.
You can schedule jobs for one-time start or to be started whenever an event is triggered.
Regards,
collysun

How to schedule a background job using the Event concept..?

Hi Folks,
I have a requirement that, I need a schedule a background job.
Once after the previous job successful only, new job should get triggered. How to go ahead with this..?
For Eg, I am scheduling a job called ZTEST periodically for 1 minute. If the job is not get completing with in 1 minute, I dont want to start my new job. Only after the success of my old job, I want my new job to run.
Waiting for ur replies.
Regards,
Savi.

Hi,
You can use events that have already been defined, or you can create new events for scheduling background jobs.
If you wish to use new events, do the following to implement the event scheduling:
Define and transport the event as a user event with transaction SM62.
You must define only event IDs; event arguments are not defined in the R/3 System. Instead, you specify event arguments when you schedule a job to wait for an event and when you trigger the event.
If you define a new event, you must also transport it to your production systems. The event transaction does not have a connection to the transport system. Instead, you must create a transport request for the event yourself.
Do this to transport an event:
Create a transport request.
Start the editor in the transport request and enter the following:
R3TR TABU <table name> where table name is BTCSEV for a system event ID, BTCUEV for a user event ID.
Press F2 with the cursor on the table name to call up the screen for specifying the table entries to transport. In this screen, enter the event IDs that you have created.
Save and release the transport request. Ensure that it is imported into your production system(s).
To trigger an event, add:
the function module BP_EVENT_RAISE to your ABAP program, or
the program SAPEVT to your external script, batch file, or program.
When your programs execute these keywords, an event will be triggered in the R/3 background processing system. The event-based scheduler is started immediately. It in turn starts all jobs that were waiting upon the event, subject to normal background processing restrictions, such as the requirement that the job has been released to start.
Schedule the jobs that are to run when your events are triggered.
You can schedule jobs for one-time start or to be started whenever an event is triggered.
Regards,
Raj.

How to Schedule SAP background job at OS Level

Hi All,
Can Anyone tell me how to Schedule SAP background job at OS Level (unix).
Regards,
Anil

Hi Anil,
I donu2019t know your requirements, anyway itu2019s possible to setup your SAP job in order to start after an event, and after that you can get the event triggered from the Operating System in the following way:
- log into you Operating System with the SIDadm user id (at the Operating System level) and go to directory /usr/sap/SID/SYS/exe/run
- Run the SAPEVT executable as follows:
sapevt YOUR_EVENT -t pf=/usr/sap/SID/SYS/profile/DEV_DVEBMGS00_server001 nr=01
This will raise the event, and cause the job scheduled within SAP to execute.
You can periodically execute this job with crontab.
Thanks,
Federico Biavati

How to schedule the background job using current selection screen field val

Hello Friends,
How to schedule the background job using current selection screen field values.
after completion of the job the spool should be sent as a mail to SAP Inbox.
Is there any way to create the variant dynamically by reading the current selection screen values.
Thanks,
Ravi

Hi,
To get the variant details you can use teh following FM.
'RS_VARIANT_CONTENTS'.
Regards,
Ankur Parab

SM36/37: Specification "After Job" does not work for Daily "periodcity"

I reviewed http://help.sap.com/saphelp_nw04/helpdata/en/20/2d513897110872e10000009b38f889/content.htm, which states what I am trying to do should work, but it does not.
Here's the deal:
1. I have two jobs: "A" and "B".
2. "A" runs Daily.
3. I set-up job "B" to run "After job" "A" in my SM36 definition.
Job "B" will run the next day, but never runs again after that even though job "A" continues to run "Daily" as it should.
Further info:
1. We have "Event-triggered" jobs that run fine, but the "After Job" designation doesn't seem to work ongoingly.
2. I can review both jobs "A" and "B" for any "Predecessor" or "Successor" jobs, and, the first jobs to run after the initial set-up DO reference each other (in other words, let's say I schedule job "B" to run "After job" "A" on Tuesday. After Tuesday's run, Job "A" sees job "B" as it's "Successor" job and job "B" sees job "A" as it's "Predecessor" job), but the definition doesn't last into the next day ONLY FOR JOB "B" (as I mentioned, job "A" always runs fine).
3. I can't set the "periodcity" for job "B" because, once I flag it to run "After Job" "A", the "period" options disappear.
4. One final tidbit: the variant for job "B" has a "key date" specified so the date is dynamic for each day the job runs. I can set up job "B" to run "Daily" with this variant and it runs fine, but I wanted it to run AFTER job "A" so it never runs if job "A" doesn't run. (At this point, it's becoming a matter of principal!)
Here's my question:
Why won't job "B" continue to run "Daily" after job "A" (a "Daily" job) runs?
Thanks in advance,
Lara

Please close this thread since you posted the same question here:
[SM36/37: Specification "After Job" does not work for Daily "periodcity"|SM36/37: Specification "After Job" does not work for Daily "periodcity";

Scheduling job2 after completing job1 both periodically

I have a problem in scheduling second job2 after completing the first job1. Both the jobs have to be scheduled / executed periodically.
In the After job step only first time job2 is executing after first job1 is executed. There is no option to execute second job periodically. Second time when first job1 executes, second job2 is not executing second time.
In the After event step, there is an option to execute second job2 periodically.
I am not sure which event to fire. But by going through the F4 (possible list of) values, I thought "SAP_END_OF_JOB" event may suit for my requirement.
But I could not find where to attach my job1, job2 to the event SAP_END_OF_JOB in the JOB Overview screen.
Job1 creates a batch input session in background in SM35.
Job2 has to be executed after completing the processing of session created by Job1.
Any help is great and appreciated.
Thanks in advance.

Hi Chakra,
Please explain your requirement further.
1. A program creates SM35 sessions. A periodic job is defined for that.
2. Another program or a person processes those sessions.
3. A third one should be scheduled to run right after that.
If my assumption is true, I have some questions about it. How are the sessions processed? Are they manually processed or are they scheduled in batch processing?
I have a couple of scenarios in mind.
<u>Scenario 1.</u>
1. One program creates the sessions and also processes them by using RSBDCSUB program. This program will be scheduled as step 1 of the job.
2. Program 2 will be scheduled as step 2 of the job.
<u>Scenario 2.</u>
1. One program creates the sessions. This will be step 1 of the job.
2. RSBDCSUB will be scheduled as step 2.
3. Program 2 will be scheduled as step 3.
<u>Scenario 3.</u>
1. One program takes of creating the sessions, then submitting the RSBDCSUB to process and then submits the program2. You can then schedule one job for this one program.
If you can give more details of your requirement may be I can help.
Regards,
Srinivas

Scheduler - Event Based Jobs

Hi,
I've been trying to create an event based job dependent on multiple jobs. I tried queuing, but it seems like it can only hand one Job at a time. Also, chains were recommended to me, but I want the Job to run on the dependence on the Job that ran on specific program at the specific time. I currently know that chains can only handle, programs, other chains and/or events.
In my mind chains wouldn't work, because If I wanted to run Job3 dependent on the outcome of Job1 running Program1 and Job2 running Program2, chains wouldn't be able to accomdate that. For it to happen in chains I would have to attach Program1 and Program2 to the new chain Job and that is not exactly what I would want.
Can anyone help/clarify this situation for me. Thank you.
Tony

Hi Tony,
So the requirement is to run a job after 2 prior jobs have completed.
There are two ways I can think of to do this, both using events. In both cases you need to set job A and job B to raise events on completion (succeeded, failed or stopped) and setup an agent for the Scheduler event queue in the schema in which you are working
dbms_scheduler.add_event_queue_subscriber('myagent')
In order to get Job C to start after jobs A and B have completed there are 2 options.
1) Let job C point to a chain and start running whenever job A has completed. The chain will have 2 steps, one event step waiting on B and one that runs your task C. An event step does nothing but wait for a particular event and complete successfully when the event is received. The second step will run when the event step waiting on job B has completed.
So your chain would look something like
begin
dbms_scheduler.create_chain('chain1');
dbms_scheduler.define_chain_event_step('chain1','stepB',
'tab.user_data.object_name = ''JOB_B'' and
tab.user_data.event_type IN(''JOB_SUCCEEDED'',''JOB_FAILED'',''JOB_STOPPED''',
'sys.scheduler$_event_queue,myagent');
dbms_scheduler.define_chain_step('chain1','stepC','finalTaskProg');
dbms_scheduler.define_chain_rule('chain1','true','start stepB');
dbms_scheduler.define_chain_rule('chain1', 'stepB completed', 'start stepC');
dbms_scheduler.define_chain_rule('chain1', 'stepC completed', 'end');
dbms_scheduler.enable('chain1');
end;
And your job would point to the chain and run whenever job_A completes (similar condition and queue_spec). It would keep waiting till job_B runs and then the final task would run and it would complete.
2) The second way is to require job_A to insert a row into a table somewhere. Rule conditions can access table data so you could have job_C have an event condition which checks for a completion event for job_B and checks the table to see whether job_A has completed. Then the code you run should then remove the row in the table
e.g.
queue_spec=>'sys.scheduler$_event_queue,myagent'
event_condition=>'tab.user_data.object_name = ''JOB_B'' and
tab.user_data.event_type IN(''JOB_SUCCEEDED'',''JOB_FAILED'',''JOB_STOPPED''' and
(select count(*) from mytab where col='job_A')>0'
Then when running C do - delete from mytab where col='job_a';
Both of these assume that job_A always completes before job_B but both of these will then run job_C after job_B completes. Modifying either of these so that either job A or B runs first is also possible by having another job that waits on A rather than B.
Hope this helps, if you have any more questions, let me know.
-Ravi

Exact Steps to schedule a background job a specific time daily :

Dear All,
Please let me know the whole process involved in schedule a background job a specific time daily. what is calender id. I could not understand what it has given in SM36.
Thanks in advance.
Rgds
Prem.

Hi prem
this is complte procedure for ur requirment.
Scheduling Background Jobs
Use
You can define and schedule background jobs in two ways from the Job Overview:
Directly from Transaction SM36. This is best for users already familiar with background job scheduling.
The Job Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use the Job Wizard, start from Transaction SM36, and either select Goto ® Wizard version or simply use the Job Wizard button.
Procedure
Call Transaction SM36 or choose CCMS ® Jobs ® Definition .
Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.
Set the jobu2019s priority, or "Job Class":
High priority: Class A
Medium priority: Class B
Low priority: Class C
In the Target server field, indicate whether to use system load balancing.
For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.
To use a particular application server to run the job, enter a specific target server.
If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.
Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.
Define the jobu2019s steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.
Save the fully defined job to submit it to the background processing system.
When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll manage jobs from the Job Overview.
pls give points if it is usefull
Regards
Saimedha

Retaining the old schedule lines after the ATP check in the sales order....

Hi Experts,
I would like to retain the old schedule lines after the ATP/GATP check in the sales order for certain conditions.
I don't want to change XVBEP,IVBEP,VBEP contents in the user-exit..
Is there any standard sub-routine or function module to reatain old schedule lines in the sales order so that the schedule lines will not update with the new values after the ATP check ?
Thanks
Rayudu

In Include LV03VFMM, you have:
* Userexit availability
PERFORM USEREXIT_AVAILABILITY_IN USING DA_ATPPR.
There may be an option to implement some logic in here. However, I tried changing the value of MVERF_POS-EINTEIL[1]-VFPKZ to initial. This will ensure that when FM AVAILABILITY_CHECK_CONTROLLER is called that the following IF statement is untrue:
CHECK NOT P_ATPCSX[] IS INITIAL.
as P_ATPCSX[] Table[0x648].....
However, this will just mean that the 2nd confirmed schedule line (assuming we have > 1 schedule lines) will have a confirmed quantity to zero.
EXIT_SAPLATPC_001 could also be used. However, when I removed the "X" from CHKFLG, I get the same result; the 2nd schedule line will revert to zero.
They were the only tests I tried; I cannot think of any other ways around this....

Schedule PC after Job

Similar Messages

Maybe you are looking for