process chain variables triggered multiple times

[former_member220449]

Hello Gurus,

After 7.31 update, the process chains in our Bw system are triggered multiple times like the screen shot below.

Do you have any idea why it's like that?

I already checked start variables in the local process chains and sm37 jobs. Everything seems as it should be

(start variable are set as "immediate start", jobs in sm37 are scheduled only 1 time).

But couldn't resolve the issue

If you can help me solve this issue, I 'll be very very appreciated.

[sriramvijay_ravidoss · Accepted solution]

Hi,

Please check the start condition for step - "FI DOVIZ KURLARI DELTA PC".

It seems it is being called twice. all other steps look ok.

-Sriram

[former_member220449 · Accepted solution]

I'm surprised because the start condition was like "Start using Meta Chain or Api".

I changed it to start immediately.

But this shouldn't be the root problem because I have similar problem in other process chains. And I checked that all start variables are in "immediate start" mode.

I'm analyzing other answers

[Former Member · Accepted solution]

Hi,

The other process chains in thismeta chain doesn't seems to have any problem.

Only because local chain FI DOVIZ KURLARI DELTA PC was triggered twice, all the following chains also executed twice due to 'successful' link.

-Nikhil

[former_member220449 · Accepted solution]

I'll check it tomorrown to see if we have the same problem.

I'll let you know....

Thanks.

[bmalyadri]

Hi ,

Please change the start  variant process of local chains to  "Start Using Meta Chain or API".

Regards

Malyadri

[former_member182429]

Right click on the process step that is always "repeatedly" triggered. There should be a menu entry that says "automatic repetition". You will want to uncheck/disable that setting.

Here is the OSS note number that describes this new feature (Point #1):

1915483 - Process chain enhancements

[former_member220449]

Hello.

I read the note, and activated the feature mentioned, because I couldn't see the "automatic repetition" function in the context menu.

Thanks a lot... How did you become aware of this new feature?

Our system is in 7.31 sp11. It can be the root reason why the chains get repeated.

I have similar problem, in all of my process chains... So, I will try to reactivate the chains.

I guess I should put as follows if I don't want any repetition:

0 second

0 Repetition

[former_member182429]

You just gotta keep an eye out for new OSS note developments at least once every month.

Hope this is the correct solution to your problem.

[venkatanareshkumar_chittu]

Hello Coskun,

Please check the planning view of the process chain and possible reason could be the PC: Kurlari Delta PC is triggered by success/failure of  predecessor PC : Kayit delta PC.

Due to the muliple status of the process chain this could be happened.

Check in RSPCPROCESSLOG giving the log id of the current run and check the field - Status of process, if has multiple status to confirm the above behaviour.

Thanks,

Venkata Naresh

[former_member220449]

Hello, I checked the the table. There is 3 records, one for start variable, the 2 other for local chain variable. The status of the start variable is F, the other two variables are G.

[bhaskar_v3]

Hi Coskun,

The second local chain FI AR MUNFERIT may be  failing .

As the link between 2nd and 3rd local chain is success or failure execute the next steps. So the 3rd local chain will be triggered.

Once you correct the error in 2nd local chain the status of 2nd local chain will change to green. Since the status is changed again the below chains will be triggered.

So first check the status of the link between 2nd and 3rd local chain.

Regards,

Bhaskar V

[Former Member]

Hi,

Please share the screenshot of start condition of local chain FI DOVIZ KURLARI DELTA PC.

Regards,

Nikhil

[former_member220449]

[Former Member]

Hi,

Goto RSPC, select chain that is triggered multiple times.Right click on the "Start" variant and select Display All Job(s). This will open up SM37, check for BI_PROCESS_TRIGGER ie job name for start variant. If you see them in "Released" status multiple times on the same day, you can change others to "Scheduled" or "Delete" state. I have seen this before.Hope this helps.

Thanks

[former_member220449]

Hello,

I just have one Released status job