Interrupt Process in Process chain.. pls help

[Former Member]

Hi All,

I have a Process Chain BI, which contains setps A, B, C, D & E.

I have added an interrupt process after step D to wait for an event.

I want to raise the event every day after midnight using SM37 job.

So, my question is:

On Day 1, the event has been raised by SM37 job and it is waiting for the Interrupt Process step.

If the Process Chain fails on Day 1 at step B. and if someone ran the steps C, D & E manually....

In that case, the event will wait till next day?

And, if the process chains runs again on Day 2... will it just pick-up the event which has been waiting from Day 1?

Thanks for your help

Nisha

[Former Member]

Found this solution as I encountered the same issue:

http://scn.sap.com/docs/DOC-45784

Uzma

[balajee_sivakumar]

Hi Nisha,

Please refer to the followign link for more details on Interrupt process,

Regards,

Balajee

[Former Member]

Hi Balajee,

Thanks for your reply.

But, if you see.. my question is very specific to a scenario.

If we have raised an event, which is supposed to trigger an interrupt process.

If that chain hasn't been run in the Day 1, will that event expire by day 2?

Or, when the chain runs on Day 2... will it pick up the event which has been waiting from Day 1 and carry-on the other steps?

thanks,

Nisha

Edited by: Nisha N on Dec 9, 2010 5:51 AM

[former_member186445]

an event will trigger an imediate action when triggered. if for any reason it is not possible to trigger the action, the event is obsolete and needs to be raised again to trigger a (new) action

M.

[Former Member]

Hi M,

Thanks for your reply.

I have tried to raise the event 1st and the interrupt step has waited for couple of hrs and it seems to be working fine.

My question is, will it wait for a day or not?

ta

Nisha

[former_member186445]

not sure, but i don't think there's a difference between a couple of hours or a day. but i believe that when the event is raised again on the second day, the first event is obsote. so whatever action you want to perform, it will not be triggered twice

M.

[Former Member]

OK, let me explain why we are using the interrupt process.

There are few steps in the Process Chain, which we deffly want to be triggered after 3 AM for example.

In that case, if the event from last night has been waiting and if the process chain has come to that stage of interrupt process at 2 AM, it will use the event from last night. Where as, ideally, it should wait till 3 AM for the current day's event.

You see what i mean?

ta

Nisha

[former_member186445]

ok, then, to be on the sure side, you can add a decision step to check that it's after 3am. only if the condition is true the subsequent steps will be executed

M.

[Former Member]

OK, if i have a decission step, and if it is 2 AM... it will not carryon with the steps.

But, thats not what we exactly want!!

We want to do the steps, after 3 AM.

[purvang_zinzuwadia]

Hi,

I wonder why dont you use another interrupt process based on time that waits until its 3:00 AM and then control goes to your next interrupt process that waits for specific event.

Hope this helps,

Purvang

[Former Member]

the event will be triggered and at that time if the process type is running this event will be triggered.

The event will not wait till the next day. You have to raise the event again the next day to trigger that particular process.

rgds, Ghuru

[Former Member]

Thanks for your reply Ghuru.

But, what will happen to the event which is waiting from yesterday?

Will it expire?

thanks,

Nisha

Edited by: Nisha N on Dec 9, 2010 5:51 AM

[balajee_sivakumar]

Hi Nisha,

The chain is started when the condition of the start process is filled. However, the interrupt process will interupt the processing of the chain (as long as its status is "active") up until the point at which the condition of the interrupt process is filled.

Should the start process condition be filled again before the interupt process condition is filled, the chain will start again and will only run up until the point of interruption. As soon as the interrupt process condition is filled, the system continues the last run of the chain only. The earlier runs remain unchanged.

Hope this solves your problem.

Regards,

Balajee