interrupting the process chain

10
Generated by Jive on 2015-10-06+02:00 1 SAP Business Warehouse: Interrupting the Process chain Posted by Jyothi velpula  10 May, 2011  Scenario: Let’s say there are two Pr ocess chains A and B and C. A and B are the Master chains which extracts the data from different non sap source systems. All our BW chains are dependent on a non sap source system, when the jobs get completed on non sap systems, it’ll send a message to the third party system from where our BW jobs will get triggered an Event based. Note: Reason why the non sap system sends the message to third party triggering tool is because when ever there is failure in the non sap System; it will not raise an event to kick off the BW chain(s). we have to trigger them manually. To avoid this we use the third party triggering toll to trigger the chains at a time using an Event . Now C is dependent both on A and B, In other words C has to trigger only after A and B is completed. We can achieve this using the Interrupt Process type. For example, if Process chain A got completed and B is still running, then using the Interrupt we can make the Process chain C to wait until both the Chains got completed. Let’s see step by step.  Process Chain A and B  Process chain C Process chain C is dependent on both A and B chains, we use interrupts (A_interrupt, B_interrupt) which will wait till those chains got completed.

Upload: funandmore-forall

Post on 05-Jan-2016

255 views

Category:

Documents


0 download

DESCRIPTION

SAP Business Warehouse: Interrupting theProcess chain

TRANSCRIPT

Page 1: Interrupting the Process Chain

7/16/2019 Interrupting the Process Chain

http://slidepdf.com/reader/full/interrupting-the-process-chain 1/10

Generated by Jive on 2015-10-06+02:00

1

SAP Business Warehouse: Interrupting theProcess chain

Posted by Jyothi velpula  10 May, 2011 Scenario:

Let’s say there are two Process chains A and B and C. A and B are the Master chains which

extracts the data from different non sap source systems. All our BW chains are dependent on a

non sap source system, when the jobs get completed on non sap systems, it’ll send a message to

the third party system from where our BW jobs will get triggered an Event based.

Note: Reason why the non sap system sends the message to third party triggering tool is because when ever

there is failure in the non sap System; it will not raise an event to kick off the BW chain(s). we have to trigger

them manually. To avoid this we use the third party triggering toll to trigger the chains at a time using an Event .

Now C is dependent both on A and B, In other words C has to trigger only after A and B is completed.

We can achieve this using the Interrupt Process type.

For example, if Process chain A got completed and B is still running, then using the Interrupt we can make the

Process chain C to wait until both the Chains got completed.

Let’s see step by step.

 Process Chain A and B

 Process chain C

Process chain C is dependent on both A and B chains, we use interrupts (A_interrupt, B_interrupt) which will

wait till those chains got completed.

Page 2: Interrupting the Process Chain

7/16/2019 Interrupting the Process Chain

http://slidepdf.com/reader/full/interrupting-the-process-chain 2/10

SAP Business Warehouse: Interrupting the Process chain

Generated by Jive on 2015-10-06+02:00

2

Now let’s see how interrupt works

A_interrupt: Interrupting the PC C until PC A gets completed.

Page 3: Interrupting the Process Chain

7/16/2019 Interrupting the Process Chain

http://slidepdf.com/reader/full/interrupting-the-process-chain 3/10

SAP Business Warehouse: Interrupting the Process chain

Generated by Jive on 2015-10-06+02:00

3

Copy the highlighted Event and Parameters

Page 4: Interrupting the Process Chain

7/16/2019 Interrupting the Process Chain

http://slidepdf.com/reader/full/interrupting-the-process-chain 4/10

SAP Business Warehouse: Interrupting the Process chain

Generated by Jive on 2015-10-06+02:00

4

Enter the above copied Event and Parameter in the Interrupt Process type like below screen

Page 5: Interrupting the Process Chain

7/16/2019 Interrupting the Process Chain

http://slidepdf.com/reader/full/interrupting-the-process-chain 5/10

SAP Business Warehouse: Interrupting the Process chain

Generated by Jive on 2015-10-06+02:00

5

Activate and schedule all the three process chains.

Note: All the three process chains (A, B, C) get triggers on Event based.

When the process chain C is in Scheduling, you can see the job BI_INTERRUPT_WAIT in both A and B

chains like below screens.

Page 6: Interrupting the Process Chain

7/16/2019 Interrupting the Process Chain

http://slidepdf.com/reader/full/interrupting-the-process-chain 6/10

SAP Business Warehouse: Interrupting the Process chain

Generated by Jive on 2015-10-06+02:00

6

Three chains (A , B , C) got triggered by the same Event

<<img src="https://weblogs.sdn.sap.com/weblogs/images/251925283/Interrupt10.JPG" border="0" alt="image"

width="659" height="200" />

 

C will wait for both A and B like below.

Page 7: Interrupting the Process Chain

7/16/2019 Interrupting the Process Chain

http://slidepdf.com/reader/full/interrupting-the-process-chain 7/10

SAP Business Warehouse: Interrupting the Process chain

Generated by Jive on 2015-10-06+02:00

7

 

3076 Views

Loed Despuig in response to Pratik Tandel  on page 8 

30 Jan, 2014 4:55 PM

By the way, I am just curious, but this is not part of my requirements..

Where can I configure to run the process chain multiple times in a day?

Loed Despuig in response to Pratik Tandel  on page 8 

30 Jan, 2014 4:52 PM

So if I put the START PROCESS to run daily it will only run once a day (even if the PERIODIC in INTERRUPT

EVENT was ticked)? Is that right? Ok mate..Thanks for clarifying it..

 

Thank you!

Page 8: Interrupting the Process Chain

7/16/2019 Interrupting the Process Chain

http://slidepdf.com/reader/full/interrupting-the-process-chain 8/10

SAP Business Warehouse: Interrupting the Process chain

Generated by Jive on 2015-10-06+02:00

8

 

Loed

Pratik Tandel in response to Loed Despuig  on page 8 

30 Jan, 2014 3:48 PM

Loed -

SUB_PC will not run unless you have it periodically scheduled to run multiple times in a day.

 

How often SUB_PC runs, will depend on the periodic values of START_PROCESS of SUB_PC and not the

INTERRUPT_EVENT in SUB_PC.

 

Pratik.

Loed Despuig in response to Pratik Tandel  on page 8 

30 Jan, 2014 3:11 PM

Thanks mate..

 Will that happen everyday?

 

On your example, the MAIN_PC ran at 10AM so the ABAP PROGRAM will also ran at 10AM..What if the event

was triggered again at around 1PM same day? Will the chain re-run?

 

Thank you!

 

Loed

kodanda pani KV

29 Jan, 2014 3:03 PMHi,

 

Thanks for your post.

 

Thanks,

Phani.

Pratik Tandel in response to Loed Despuig  on page 9 

29 Jan, 2014 2:21 PM

Loed -

 In your case, ABAP Program in SUB_PC will run only after MAIN_PC is finished and after the scheduled start

time of SUB_PC, ie., 8 am).

 

If MAIN_PC finishes after 10 am, then SUB_PC will start after 10 am.

 

Hope this helps,

Page 9: Interrupting the Process Chain

7/16/2019 Interrupting the Process Chain

http://slidepdf.com/reader/full/interrupting-the-process-chain 9/10

SAP Business Warehouse: Interrupting the Process chain

Generated by Jive on 2015-10-06+02:00

9

Pratik.

Loed Despuig

29 Jan, 2014 8:30 AM

Hi,

 

I have a question..

 

What if I have two (2) chains:

 

MAIN_PC - executed daily every 3AM

SUB_PC - executed daily every 8AM

 

This is the diagram of my SUB_PC chain which starts every 8AM daily:

 

START

  |

  INTERRUPT

(based on AFTER EVENT - using the EVENT and PARAMETER of last process of MAIN_PC chain)

  |

  ABAP PROGRAM (to send report)

 

***NOTE:

The ABAP PROGRAM in SUB_PC chain must run later than 8AM and if MAIN_PC ran successfully..

 

Will the INTERRUPT process work before the ABAP PROGRAM in the SUB_PC chain if the MAIN_PC

ran before 8AM? How about if MAIN_PC ran around 10AM (because an error occurred during its run), will

SUB_PC still work?

 

Thank you!

 

Loed

Ganesh Bothe

29 Jan, 2014 8:17 AM

Useful information..thanks for sharing .

Jyothi velpula in response to Adonis P  on page 10 

30 Oct, 2012 7:21 AM

Sorry about that, will try

 

Thanks

Page 10: Interrupting the Process Chain

7/16/2019 Interrupting the Process Chain

http://slidepdf.com/reader/full/interrupting-the-process-chain 10/10

SAP Business Warehouse: Interrupting the Process chain

Generated by Jive on 2015-10-06+02:00

10

J

Adonis P

24 Oct, 2012 3:42 PM

Thanks for your post. But one of your image has broken, can you repair it? thanks!

Jyothi velpula in response to Pratik Tandel  on page 10 15 May, 2011 8:02 PM

Hi Pratik,

Scenario1:Yes, When A fails and B succeeds.. C will wait for A until it gets successfully completed.

Note:When a PC gets failed,we will rectify the issue to get it resolved and make the PC successful.otherwisewe'll miss that particular day data!

Scenario2:C will pick up both A's previous and current load.

Thank you.

J

Pratik Tandel

13 May, 2011 7:52 AM

Thanks for your post. I have a question though, what happens in this scenario.

Let's assume A fails and B succeeds. C will wait till both are finished, in which case it will not run that day.

Next day both A and B succeeds, will C pick up the data request ID from previous day for A or will it have both

data request IDs.

Also what does the Reset Interrupt do? Any insight will be helpful. Again thanks for the post and visualexplanation.