cancel
Showing results for 
Search instead for 
Did you mean: 

Why the process chain always run twice when triggered from R3?

Former Member
0 Kudos

I run a program from R3 by calling the remote function 'RSSM_EVENT_RAISE' on BW to trigger an event and in turn the event on BW bring up the running of a process chain. But whenever I run the program on R3 to bring up the running of the process chain, I find the process chain always run twice at the same time. Does anybody knows the answer?

And also I would like to know the functionalities of the two picture buttons "Activate" and "Activate and Schedule" in process chain. In which case the "Activate" button should be used and in which case, the "Activate and Schedule" button should be used? If we click the Start variant of a process chain, then click "Change Selections" button which bring up the window "Start Time" where the buttons "Immediate", "Date/Time", "After job", and "After event" are listed at the top. If we modify at any of the above buttons, then after save this modification, we will have to click "Activate and Schedule" button to make it work, right?

Thanks a lot and everyone's idea is greatly appreciated!

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Activate buttion is for checking/making the process chain is active.

Active and schedule- for activate and schedule the process chain as per the variants- selection options.

If you do modify any buttons in start variant you have to active the process chain otherwise the job will not schedule...

thanks,

mahantesh

Former Member
0 Kudos

mahantesh,

Can't catch what you mean. If I modify any of the buttons in start variant, then I have to click the button "Activate and Schedule" other than "Activate", right?

Thanks

Former Member
0 Kudos

Kevin, make sure there is only one job scehduled for the Start Process of your Process Chain. If you bring up the Process Chain (not the log view), right click on the Start Process and select "Displaying Scheduled Job(s)...". There should only be one scheduled job with name BI_PROCESS_TRIGGER. If there is more than one, then when triggered, it would execute more than once at the same time. If there is only one job, then maybe your R/3 program is triggering the event more than once?

As far as the Start conditions for the Start Process, it works off the same principals as a scheduled job. These start conditions determine when or how the Process Chain is to be executed. You also have control over frequency. These start conditions determine the scheduling of the Start Process of your Process Chain.

When you schedule a Process Chain, a separate scheduled job is created for "each" process in the Chain. BW controls the triggering of these jobs based upon how the processes in the Chain are linked. All the jobs associated with Process Chains have strict naming conventions and all begin with BI_PROCESS_... If you use SM37 to view all jobs that begin with BI_PROCESS_ you will find alot of scheduled jobs associated with your process chains. Each job represents one of the processes within your process chains.

Does this help?

Another tip might be to trigger the event manually in BW (use tx SM64). If the process chain executes twice again, then maybe there is a separate scheduled job in BW that triggers the process chain that is triggered by the same event as the start process of the process chain.

Message was edited by: George Shannon

Former Member
0 Kudos

hello George,

Thanks for your detailed input! I follow what you wrote below by selecting "Displaying Scheduledd Job(s)", find there is only one job BI_PROCESS_TRIGGER listed with the status as Released. Still don't know the answer why the log view show the process chain always run twice at the same time.

One hint is that in the log view, I can see the LAST_CHANGED and LAST_ACTIVATED also occured at the same time, maybe when I modified/saved/activated and scheduled the Process Chain, it enable it to run twice. I do run R3 program every time once to trigger an event on BW and in turn the event bring up the Chain run only once, but confused why the Process Chain log view show it always run twice. Any further consideration?

Thanks

Former Member
0 Kudos

Kevin, let me see if I can follow your logic. If you go into the log view of your Process Chain, you will see entries where the Log ID is:

CREATED username

LAST_CHANGED username

LAST_ACTIVATED username

3YNN4Z....

3YPQ7X....

where the 3Yxxxx are jobs that ran at the same time?

A suggestion, if you do not have many process chains, I would go into SM37 and look for all "Scheduled" and "Released" jobs that begin with BI_PROCESS_TRIGGER*, and check the Start condition of each one. There may be a job left out there from prior to your changes. If you find a duplicate job with the same start condition of your current Process Chain, you can delete the duplicate job.

How do you find out which one is which? Look at the "Step" for both jobs. The GOOD one will have the same "Parameters" as the Step of the job which you saw when you looked using "Displaying Scheduled Job(s)..."

My only other suggestion is to "Remove from Schedule" (from the Process Chain maintenance screen). Then check to make sure there are no "outstanding" jobs from your Process Chain, then "Activate and Schedule".

Good luck!

Former Member
0 Kudos

hi George,

In log view, for the four lines you mentioned above:

LAST_CHANGED username

LAST_ACTIVATED username

3YNN4Z....

3YPQ7X....

Yeh, no problem for 1st two lines, but the log ID for the 3rd line and 4th line or the two processes are totally the same. That's why I say that I've always got two processes running at the same time. In your case, 3rd line and 4th line sounds different, at least from their log IDs. And yes, these two jobs are running at exactly the same time!

Goto SM37, all status are "Complete" other than what you want for "Scheduled" and "Released". And the jobs that begin with BI_PROCESS_TRIGGER* occurs only once each time I run the trigger from R3, that's right. Besides the BI_PROCESS_TRIGGER process, most of other processes are BI_PROCESS_LOADING.

I am really appreciated your detailed inputs, even if the problem has not resolved, but I still want to give you full points for resolving the problem. And at the same time, everyone else idea is greatly appreciated!

Former Member
0 Kudos

hi George,

An update! This time when I run SM37, on the selection screen, I use the option after event and input the event that bring up the process chain running, then hit enter, and get two BI_PROCESS_TRIGGERCone status is complete with the time expected, the other one status is Released without any time. Maybe we go ahead to delete the Released one to avoid the duplicated running?

Thanks

Former Member
0 Kudos

Hi Kevin,

Don't delete the Released one otherwise you will not be able to run it from R/3 as one job with released status should be there.

Regards,

RB

Former Member
0 Kudos

RB is right. DO NOT DELETE the released BI_PROCESS_TRIGGER job. This job is the Start Process of your Process Chain. If you delete it, your Process Chain will never run. If you only have one BI_PROCESS_TRIGGER job in a "Released" status, then when you execute your R/3 program to trigger the event defined in your Start Process, the Process Chain should only execute once. I find it interesting from your previous note that the Job ID's were identical. I didn't think that could happen.

It would be interesting to see if you trigger the event to start your Process Chain now, whether the Process Chain would execute twice.

If it still executes twice, then I would "Remove from Schedule" and then reactivate and schedule the Process Chain again.

Best of luck!

Message was edited by: George Shannon

Former Member
0 Kudos

hi George,

This morning, I found there are two BI_PROCESS_TRIGGER with Release status. One is triggered after an event that I want. The other one is schduled to run daily at 10:38:05 starting from today, I don't remember how this one is generated, I need to delete this scheduled one?

Thanks

Former Member
0 Kudos

First, I assume that you have only one Process Chain in your system. I don't want you to delete a job that is triggering another Process Chain. That said, it sounds like the job scheduled daily at 10:38:05 is a "left over" job. Maybe you originally scheduled your Process Chain to run immediately and hit the "Periodic Job" on your start condition? Then changed your start condition to be "After Event" and rescheduled your Process Chain?

To do it the right way, I would select the option to "Remove from Schedule". This is done in the Process Chain maintenance screen. Bring up your Process Chain and at the top click on <u></u>P<u></u>rocess Chain, then "Remove from Schedule".

After doing this, I would go back into SM37 to see if there are any BI_PROCESS_TRIGGER jobs still in a released status.

If not, then go back to your Process Chain, double-click on your Start process, verify your start conditions, and save your Start process. Then Activate and Schedule your Process Chain. Once that is complete, go back into SM37 and verify that there is only one BI_PROCESS_TRIGGER job in a released status.

You should be all set after that.

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi Shannon,

Even if u reschedule ur chain also.. u will get two jobs in the log view.. I guess that there should be some settings where we have to change. But I'm not sure about that.

Regards-

MM

Former Member
0 Kudos

Hi Kevin,

If u have both the job names as same then the approach given by the Shannon wont work here..

As I said that this wont have any impact on the loads. So u can ignore this and continue to work with ur PC..

Its better if u close ur previous threads if it fullfills ur requirement..

Regards-

MM

Message was edited by: vishnuC

Former Member
0 Kudos

Hi Kevin,

Let me know did u got the different Job names at the same time when u enter into the Log view of the process chain as Shannon specified..?

Regards-

MM

Former Member
0 Kudos

MM,

The two log IDs are the same.

Former Member
0 Kudos

Hi Kevin,

In our production system also we encountered the same problem but it doesnt have any affect on ur loads.. So u can ignore this and continue to work with the PC as it will run fine..

When ever if u scheduled a PC then u will get the last changed and last Activated in the Log View through that u can see which user has scheduled the PC.

Regards-

MM

Assign points if it helps