process chain start variant repaired in production

[AA3]

Hi

I took up tasks from our previous Bi team

I am told we have followed the regular process of DEV -- QA and PROD for all process chains

I see a strange observation in Production for a particular process chain in its start variant

It is shown to run as immediate in the start variant, in the detail view , but

it runs scheduled at a certain time every day, I can see the scheduled jobs released

I see that in production it is attached to a request in repaired status

process chain works fine and triggers regularly

I am unable to understand why it shows as immediate in the start variant and however runs on a regular schedule

[former_member188080 · Accepted solution]

Hi,

It seems there is differences in start variant in dev and qua and prd.

Normally we don't schedule the PC in dev and quality and hence start variant setting are totally different than production.

When you do any transport do it through Transport connection and don't select start variant. It should not affect your start variant in Production.

Secondly you can make changes in Production directly.

Reparing start variant should not affect anything but you have to ensure in SM37 that realeased job is not removed when you will move such changes and repair kind arning occurs.

Thanks and regards

Kiran

[Former Member]

Hi,

Check if there is any external tool which triggers the process chains in production system, in my project we have a system called TWS and that system triggers all the process chains in the BW system on predefined time.

But all the process chain in BW system are marked as start immediate only.

Regards,

Durgesh.

[AA3]

I see that the start variant name is the same as the main meta chani name, in the table RSPCCHAIN

I can see that there are two versions of the same chain (A and M) with the same background event values in Production.

what does this indicate..

If I transport this chain again from original system to PROD , will it get overwritten and show only the A active verison.

[Former Member]

Hi,

There is nothing strange about it this is normal behaviour of BI system and for every object there will be one active and one modified version.

Regards,

Durgesh.

[Former Member]

Hi

In BI system, for every object we will have active and modified versions and no issues with your process chain.

find how the other chains are triggering in your system check your project is using any tool to start the chains.

Regards,

Venkatesh

[AA3]

ok. There is no tool to trigger, there is another META chain, which has its time defined and its ticked as Periodic Job.

I noticed that the META chain ,that i was mentioning about was changed in production, I can see the start variant in a request in production.

but this is not clear enough to prove that the META chain is indeed being processed everyday at a certain time though its start variant is mentioned as Immediate.

[Former Member]

Hi

Check the periodic value of main chain (daily or weekly)

Open main chain in RSPC1 and check whether it has that PC as local chain.

can you share the start time your local chain for 7 days (previous one week)

Regards,

Venkatesh

Edited by: Venky1903 on Sep 15, 2011 3:45 PM

[AA3]

I am talking about the Main (META chain) only in all the contexts mentioned before in the thread.

The start variant of the META chain is showing up as Immediate, however it runs DAILY on schedule at 1:30 AM EST.

My only concern is

1) why does the start variant of this META chain show up as immediate, when it is actually running scheduled ?

2)Does the change directly in production, could have brought in this behaviour?

3) If , I re transport the whole META chain from DEV-QA --PRD , will the start variant change or will it cause trouble considering the fact that the start variant was repaired in PROD directly.

please help me answer this questions

[Former Member]

Hi

1) why does the start variant of this META chain show up as immediate, when it is actually running scheduled ?

are you able to see the chain in green color(scheduled state).

when you right click on start process chain step and you have option to select display scheduled job?..if yes check the start condition by double click on job.

2)Does the change directly in production, could have brought in this behavior?

We can change the start condition of process chain, when right click on start variant and select display variant..here you can see last changed name

3) If , I re transport the whole META chain from DEV-QA --PRD , will the start variant change or will it cause trouble considering the fact that the start variant was repaired in PROD directly.

No need to transport again, if you know the start condition of process chain, edit the same in prod and save it.

Regards,

Venkatesh

[AA3]

1) Yes the Meta chain is in green state, i can see the schduled job with its variant, it points to the required process chain

2) I can see the last change name, does it have to show the system users (bwremote or some else).

3)process chains are non modifiable in Prod, so can only be displayed.

[Former Member]

Hi

If start condition of process chain,definitely it won't have released job in SM37.Please check once again and check whether it is included as local chain in any other chain.

If you want to find out the main chain of a local chain, use table RSPCCHAIN

give the local chain name in variant filed and execute, you will main chain details

Regards,

Venkatesh.