Process chain triggered twice

I have a triggeed a process chain twice.
The flow of the process chain is like this:
from PSA to ODS full load----
from ODS to Cube delta load.
There is selection criteria at infopackage to ODS with createdon.. ie for ex: if we run today, the from date is sy-datum-2 and to-date is sy-datum. We ran the process chain twice on the same day and the selection is same for the full load to ODS.
Please suggest is there any impact of this.
Req

Hi Swaroop,
Are you using the BI7.0 flow or BW3.x data flow?
What is the time duration in which the PC is triggered 2dn time?
How many times the PC runs in your system per day?
loading data till DSO with full load will not cause any issue as the DSo will over write the records, comming to delta load from DSO to IC -- first time the delta records will be updated and the next run if at all if there are any delta records then those records will be uploaded or else it will transfer 0 records.
I don;t thik there is any problem in your case.
Regards
KP

Similar Messages

Process Chain Triggered automatically when transported to test system

Hi All,
We modified several process chain and transported the process chain to Test system.
Few Process chain triggered automatically as the varient was set to immediate in development system.
Now we want to move the process chain to production. Do we need
1. new transport request with the variant to future date and discard the transport request which created issues
2. New transport request with the variant to future date and transport the new along with the old transport to production system
3. Change the start date in Test system and transport the same request to production
Kindly advice me on the action to be taken.

>
> Hi All,
>
> We modified several process chain and transported the process chain to Test system.
> Few Process chain triggered automatically as the varient was set to immediate in development system.
> Now we want to move the process chain to production. Do we need
>
> 1. new transport request with the variant to future date and discard the transport request which created issues
> 2. New transport request with the variant to future date and transport the new along with the old transport to production system
> 3. Change the start date in Test system and transport the same request to production
>
> Kindly advice me on the action to be taken.
Regarding 2: When the old transport is imported into production the start will be set to immediately and the process chain will execute. You should not use this option.
Regarding 3: Changing in Test system will not affect the content of the transport, it will still be the same as released from Dev.
We have avoided this annoying problem with process chains being executed when transports are imported by creating a "parent" process chain that simply triggers the process chain in question. This "parent" chain should not be transported. You then set the start option for the original process chain to "start by API/Event" then you can transport the original process chain whenever you want without any risk of the process chain being executed.
Regards,
Lars

Very Urgent-Pls help*Process chain triggered automatically when transported

Hi All,
We have got some issue.
We have a Process chain, started set to immediate becuase its used in meta chain.
When ever we transport the Chain, its getting triggerred in the Target Client automatically.
We can prevent this, by keeping the process chain starter as "Event Based". But, as its a local process chain, it must be set to Immediate.
Please help.
Cheers,
Nisha

Hi Siggi,
Thanks for this reply.
Scheduling the Local chain to run in future and then changing it after import, i think, is a work around.
Iam sure, there must be some thing to stop this trigger.
And, We have tried Changing the Chains to run Via Meta chain, but, the problem is after the Transport, the local chain can't be triggered on its own using "immediatly". If we try to change it, it'll prompt for a Transport.
Please help.
Cheers,
Nisha

Process Chain Running Twice

HI!!
I ran by error twice the same PC, now in the maintenance log, I found 2 logs, in the first one the Start step is in green and the others steps are in gray, in the second log the start step is in yellow. In the Displaying messages in found this:
This message means that step 001 is currently being started. The
additional parameters give further details on the step itself:
As far as I understand I have to delete the second log, but no idea how to do that.
Is this the solution? or anyone knows another way?
Thanks & Regards

Hi,
First and foremost let me advice you to be very careful while doing this.
You can start from SM37, find the process WID/PID then go to SM50 or SM51 and kill it. Once its done come back to RSMO and check the request, it should be red but again manually force to red and save by clicking on the total status button in the status tab. This shuld ensure that the process is killed properly.
The next step will be to go to targets that you were loading and remove the red requests from those targets.
Note: For source system loads you may have to check if the request is running in the source system and kill if needed and pull it again.
But for BW datamart delta loads u may have reset the datamarts in case u are going to pull the delta again.
Refer
Re: Kill a Job
Re: Killing a process chain.
Regards,
JituK

Process Chain Triggers Multiple times

Hi All,
I have Meta process chain say ZAAA which has multiple Local Chains example ZBBB , ZCCC and ZDDD. .This Local chain ZCCC trigger multiple times of in one day . we had a issues today with deactivation of Transformations and DTP in different levels because of that Local Process chain ZCCC is failed along with other process chains . when I reach to ZCCC started by repeat or repair ,before Local Chain ZCCC finished whole process ,ZCCC triggers second time .
Now first times triggered process chain ZCCC is in yellow , and second time triggered process chain ZCCC gone through all the way to gree , and Meta chain showes red.
what I have do make Meta chain green.
Regards
Hari

Hi Hari,
I wonder what you mean by below statement:
one of the sub pc still yellow first time trigger and went to red and second time trigger whole process is green. all Sub PC are green
For the sub pc mentioned above, you trigger it all over again? Or you repeat/repair the step failed?
If you trigger it the second times all over again it is a new run and the first run remain fail,ed so the meta chain will never get green, if you want to make the meta chain green, you need to repeat/repair the step failed in first run.
Regards
Bill

Setting of one process chain triggering by other?

Hi Friends,
we are having two process chains, PC1 and PC2.
Daily PC1 triggers PC2.
But i want to know where this setting is done in the system (PC1 triggers PC2)
Can any one please tell me?
Thanks..in advance
Tony

There are several ways to trigger the process chain from the another process chain.
Start variant,
Maintain the same start variant for all the process chain which u want to be trigerred by dependence, ie on executing the one prcess chain from group, all will be triggered.
Local process chain:
Insert the (secound) child process chain in a (first )parent chain. by this when u execute the parent process chain the child will be triggered.
Event:
For all process chain there will be event name. U can write code with this event as a reference so that completion of one process chain will triger the secound.
More.........

Monthly process chain ran twice

Hello Friends,
I have a scenario where I need to find the reason why a Monthly process chain which is supposed to run once a month ran twice on a particular month on the same day.
I have already checked the relevant process chain using the transaction ST13 or the program /SSA/BWT which provided me the information that the first run was not executed as a part of the relevant Meta chain which has pulled all the relevant records into the target and the chain was successful.
The chain ran for the second time as a part of its Meta chain as per the schedule which ended up with a failure due to the duplicate records.
Now if I view the log, I could view only the latest user (i.e) ALEREMOTE and not the predecessor user information to find out who has scheduled the chain or the chain has got executed automatically due to some other predecessor chains.
I hope, we can get the whole logs via SM37 / SLG1, but has anyone experienced?
Do we have any table or an other way by whihc we can identify the user?
Regards,
Vinoth V

Hi,
This might be a possibility - the process chain failed in a step, and the process link was set to move to the next step even in case of errors (link colour is red). Upon repeat, the already executed steps will be executed again.
Regards,
Rakesh

Single Process chain triggers with two different users

Hello all,
I have process chain which is triggering two times with R/3 user at 7 PM and same process chain with 9 PM by BW user. but in rspc i have given only with BW user.
how second R/3 Chain is triggering?
R/3 to PSA Full load daily. BI System.
Thanks,
Ranga

Are you using an event to trigger this process chain?
If yes then check in R/3, whether you are triggering that event in R/3.

Canceled Status in Job Detail, Process Chain triggering w/event

Hi All,
I have created event, PC and trigger event with SM64 or with ABAP, everything is ok
if I activate and Schedule PC, I see BI_PROCESS_TRIGGER job with released status, and when I trigger the event nothing is happened but when I checked the Job detail I see canceled status job.
I donu2019t understand why this problem occurs ?
I can trigger the event but before event trigger the PC, scheduled job detail directly turn to the chancel status.
if any one give me a clue to solve this problem I will appreciate
Note : No Job log !!!
Thanks
Ali

Ali,
Check authorizations.
Try to run process chain with out event(immediate) and check.
Srini

Process Chain - triggering sub chains at set time interval

Hi all,
Scenario:
I want to setup multiple process chains during the day (hourly intervals). I would like to have a main chain which would then trigger subsequent chains. the problem is that when i tried to setup the sub-chains to run at say, 10am. 11am etc, they don't fire off at those specified times (because they are part of the meta chain?). I currently have the individual chains running independently (i.e. first chain at 10am, 2nd chain at 11am...) - but i need to be able to stop the 2nd chain from running if there is a problem on the 1st chain (which is why i want to run them as part of a Meta chain).
Hope this makes sense - and any help/assistance is much appreciated! Thanks
M.

Do you know how long 1st PC will run ? will it finish before 11 am ?
If so, try following proess
Add Abap Program process(under General Services) to the end of the 1st PC and use program BTC_EVENT_RAISE and Enter Program variant = event and activate the PC
Now go to 2nd PC and schedule at 11 am periodically
Add another step Interrupt Process (u can find under General Services ) just after start process and enter event and schedule the pc
When 1st Pc completes sucessfully it will activate the event to trigger 2nd PC , though the event is activated the 2nd pc will start at 11am
Hope it's clear!

Process Chain triggers Automatically after the Transport

Hello There,
I have a Process chain setup to load Transaction Data and the infopackets are set to "Immediate Start"..
When I transport these to Test environment, they are getting executed immediately after the transport..
Just wondering ,, this is what it intended to do.. because I don't want to run them after the transport.. is it something I am missing anything here ??
Your comments are much appreciated..
Thanks
Mavi

Mavi,
Once you click delete and save. The schedule is deleted. You could view via Maintain Start Variant -> Direct Scheduling button.
You will noticed that there is nothing schedule i.e. all tabs (immediate, specific datetime, etc) are not scheduled.
Answering to your question on modifiable in Test and Production box :
All you have to do is go to RSA1 -> Transport Connection -> Object Changeability -> Change the Process Chain objects to Changeable -> Save.
And you are done i.e. you could change the scheduling of the RSPC in Test and Production.
Remember to assign the point to the solution provided...:-)
Thanks.
Regards,
Lye

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

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!

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

How to determine the source of Events triggered in a process chain

Hi ,
We have almost a 100 process chains, and of these approx 20-30 local process chains are triggered by events raised within other process chains. These events are raised via BP_EVENT_RAISE using the ABAP process type.
However, our problem is to identify the source of these event trigger - i.e. which process chain triggered this event ?
Looking at SM64, the event history does not display the source for these events.
Is there any table or program that we can use to determine the source of these events which are triggered.
Any help is much appreciated and points awarded.
thanks
BK

Hi,
do check in the program /SSA/BWT . or TCODE - ST13 -- enter BW-TOOLS and execute. -- Choose Process chains and execute --- Select the date and time for which you want to see the process chains and execute again.
This will give you the entire list of process chains triggered, status, timings(start, end, overall runtime). Once clicked on the process chains it will show you the steps in theprocess chains, data loaded in the data targets, source system, etc...
hope it helps.

Trigger Process chains only once in a day

Hi All,
I have a requirement where a process chain triggers on arrival of some files.Now I want this chain to trigger only once in a day even if file arrives before the start of next day.How can i acheive this.
Reagrds,
Raj

Hi,
Please use below:
REPORT ZCHECKPCNEW.
TABLES : RSPCLOGCHAIN.
DATA : IT_TAB TYPE TABLE OF RSPCLOGCHAIN,
WA_TAB TYPE RSPCLOGCHAIN.
FIELD-SYMBOLS <FS> LIKE LINE OF IT_TAB.
PARAMETERS :LV_CHAIN TYPE RSPCLOGCHAIN-CHAIN_ID.
SELECT * FROM RSPCLOGCHAIN INTO TABLE IT_TAB
WHERE CHAIN_ID = LV_CHAIN
AND DATUM = SY-DATUM.
SORT IT_TAB DESCENDING BY DATUM ZEIT.
READ TABLE IT_TAB INDEX 1 ASSIGNING <FS>.
IF SY-SUBRC = 0.
IF <FS>-ZEIT < SY-UZEIT.
MESSAGE E000(SABAPDOCU) WITH 'Error'.
ELSE.
MESSAGE I162(00) WITH 'Successful'.
ENDIF.
ELSE.
MESSAGE I162(00) WITH 'Successful'.
ENDIF.
-Vikram

Applying variable filter while executing a process chain

Hi,
I have a client requirement discussed below:
I have a process chain containing multiple DTPs. The user wants to have a filter variable for fiscal year period while executing the process chain(i.e fiscal period selection screen should come for him to enter fiscal period). And the entire process chain should run for that selected fiscal period.
Please help me with solutions of this dynamic process chain triggering.
Points will be assigned if helpful.
Regards,
Sourabh

Hi,
You can craete a variant with some set of value and through ABAP code you
can run the process chain according to your requirement.
Thanks,
Saveen Kumar

Process chain triggered twice

Similar Messages

Maybe you are looking for