cancel
Showing results for 
Search instead for 
Did you mean: 

process chain step started twice

Former Member
0 Kudos

Hello,

I have an issue on my system (SAP BW 7.40 SP10 on HANA).

Into master data process chain, I have sometime one step which is started twice.

Depending the kind of the step, it raises an error or not.

For example, if it is a DTP step, I got an exception on one of the 2 starts, because the object is locked.

Do you have a clue about this behaviour?

Thx.

Nicolas

Accepted Solutions (0)

Answers (3)

Answers (3)

carlo_kok
Discoverer
0 Kudos

Hello Lhenri,

How did you solve this issue??

I have the same issue that some process chains in a meta chain are executed twice several hours apart without a appropiate trigger.

Please advice

Former Member
0 Kudos

Hello Carlo,

This issue is not solved yet.

I will explain here the way to fix it when I will have a solution.

Rgds.

Nicolas

RamanKorrapati
Active Contributor
0 Kudos

hi Lhenri,

is this full load?

if its full load then there is no issue.

Seems like your load might be triggered by twice or some one might be repeated your failed step.

So that's why it showing two steps(red and green) of same process.

Thanks.

Former Member
0 Kudos

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".

Former Member
0 Kudos

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.

Former Member
0 Kudos

Hello Raman,

Yes, most of the steps in these process chains are full loads.

We don't have any issue at this moment in reports but we have red lights in RSPCM when we control process chains ending.

We don't want to allow errors or warnings if there is no issue.

That's why we're looking for a reason to this behaviour.

Rgds.

Nicolas

RamanKorrapati
Active Contributor
0 Kudos

Hi Lhenri,

Error message you can find at respective process step-->right click-->display the message and see the error.

But as of now your error also solved and respective process was green.

at RSPCM, it shows red color because one step was failed  but thru repeat it was solved.this is common thing. nothing to worry about red status at RSPCM. if you see your chain logs in logs view it may shows as green.

on next run if your chain goes well then chain status will shows green.

Chain status  red or green not much considerable. as per the run all process steps in your chain need to be finished without stuck/failure.

Thanks

Former Member
0 Kudos

Hello Anand,

Thank you for your answer.

the strange fact comes from only one step could be start twice and not the all process chain.

And it's not always the same step every day, it changes.

Sometime one step, sometime another one.

I think I will send a message to OSS.

Rgds.

Nicolas

ccc_ccc
Active Contributor
0 Kudos

Hi Nicolas,

Check start process of your PC is scheduled twice same time.

Right click on Start process and check Display scheduled jobs.

Regards

Nanda

Former Member
0 Kudos

Hello Nanda,

The process chain is set as 'immediate start' and is launched by an extern scheduler (control M).

It uses prg RSPC_SYNCHRONOUS_RUN.

I don't think it is the cause of my issue.

Rgds.

Nicolas