RSPC how to get rid of unwanted process chain start in BW

[christoph_ostrop]

we do the BW process chain scheduling from our CPS system (NW 7.00 CPS = Job Scheduling by Redwood)

from CPS we schedule a batch job in our SAP-ERP (NW-7.01 ECC EHP4) system, running some steps and

then (from the ERP-system) starting a remote process chain => which starts a process chain in our BW-system (NW-7.01 BW).

but - since several days, we had a duplicate process chain running and we do not know,

why (in the BW-system) exists a released Job to start the BW-chain at the same time, as the CPS initiated Job => ERP => BW should run.

we recognized an unwanted job in the BW-system (released Job with interval daily) - how to get rid of this unwanted process chain start in BW,

because the BW process chain start should only initiated from CPS => ERP => BW.

first try:

in the BW-system, we can see in the context menü of the chain => show all jobs => SM37

a new released Job => we changed this job to planed => we deleted this job !!!

the next day, in the BW-system, we can see in the context menü of the chain => show all jobs => SM37

a new released Job => why ??

second try:

in RSPC - showing the process chain => Menu-option => remove from schedule

the next day, in the BW-system, we can see in the context menü of the chain => show all jobs => SM37

a new released Job => why ??

so - no more ideas:

how to get rid of these unwanted process chain start in BW

chris

[christoph_ostrop · Accepted solution]

for all users, who will find the BW scheduling of process-chains just as unlogical and confusing,

here are some explanations, which works as follows:


1) removing of periodical scheduling:

please proceed as follows:
- TA RSPC
- Choose a chain
- Click (right click - context menu) of the start process
- display variant
- Switch to change mode
- Change selection (of the variant)
- remove the 'job run periodically' checkbox-entry
- save or activate

after these steps, the periodic schedule is off, but .......
the chain itself, however, is still shown with a green background and is still
scheduled (has a released scheduling job)


2) action "remove from schedule"

please proceed as follows:
- TA RSPC
- choose a process chain
- menu bar execution => "remove from schedule"

here the name of the function could be misunderstood, because it did not remove the BW-chain from scheduling (in general)  but only "remove from the next scheduled run"
so, if you  do not do step 1, then the process chain will be scheduled for the next schedule run again

so, you have to do both steps

- remove from periodically scheduling (in the variant)

- remove from scheduling (the process chain, not the variant)  to cancel/delete the released job

hope, that helps.

best regards,

Chris.

[snitwipro]

Hi Chris

   Let me try to explain the scenarios one by one -

1. After changing the job from released to planned, next day could see a new released job: This happened because the chain had been scheduled as a recurring job. Therefore even if you are changing the job that you could see on that day to planned, next day a new job had been released by the system. Try removing the process chain from schedule and delete the existing job (NOT changing to planned). Also check if the start variant has any selection condition. To be 100% sure change the scheduling date and time to past date (in the variant) and activate the variant. So that even if the job is triggered, it will fail to start the PC as the start condition is in past dates!

2. I think the second point you raised is also related to the first point I told. You will have to delete the existing job at the same time you are removing the PC from schedule.

Hope this helps!

Cheers

Sourav

[christoph_ostrop]

Sourav Banerjee wrote:
Hi Chris
   Let me try to explain the scenarios one by one - 
1. After changing the job from released to planned, next day could see a new released job: This happened because the chain had been scheduled as a recurring job. Therefore even if you are changing the job that you could see on that day to planned, next day a new job had been released by the system. Try removing the process chain from schedule and delete the existing job (NOT changing to planned). Also check if the start variant has any selection condition. To be 100% sure change the scheduling date and time to past date (in the variant) and activate the variant. So that even if the job is triggered, it will fail to start the PC as the start condition is in past dates!
2. I think the second point you raised is also related to the first point I told. You will have to delete the existing job at the same time you are removing the PC from schedule.
Hope this helps!
Cheers
Sourav
 

the 2. point

when we choose the "remove from schedule" option, this action itself deletes the (before shown) released job to the PC.

so only already finished jobs are shown, no more released job to this PC (at this time)

but next day, a new release job is shown

so both options (1. delete the release job or 2. remove from schedule) did not work,

on the next day, a new released job to this PC is shown

[christoph_ostrop]

some additional info:

we recognized, that the mentioned process chain has some periodically attributes

shown in DB-Table RSPCTRIGGER , Attribute/column PERIODIC "X" and PRDDAYS "001"

what to do to avoid periodic execution?

[former_member188080]

Hi,

Just do one thing you need to go and delete the scheduled job from SM37 directly..

otherwise PC will not run but you will still see that job in SM37..

Thanks and regards

Kiran

[christoph_ostrop]

we do both,  changed the release job to planed and then delete the job,

so only already finished jobs are shown,

no more released job to this PC.

but next day, a new release job is shown in the "show all jobs to the PC" window

so only to delete the job is not the solution .......