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

Similar Messages

The 0co_om_opa_6 ip in the process chains takes long time to run

Hi experts,
The 0co_om_opa_6 ip in the process chains takes long time to run around 5 hours in production
I have checked the note 382329,
-> where the indexes 1 and 4 are active
-> index 4 was not "Index does not exist in database system ORACLE"- i have assgined to " Indexes on all database systems and ran the delta load in development system, but guess there are not much data in dev it took 2-1/2 hrs to run as it was taking earlier. so didnt find much differnce in performance.
As per the note Note 549552 - CO line item extractors: performance, i have checked in the table BWOM_SETTINGS these are the settings that are there in the ECC system.
-> OLTPSOURCE - is blank
   PARAM_NAME - OBJSELSIZE
   PARAM_VALUE- is blank
-> OLTPSOURCE - is blank
   PARAM_NAME - NOTSSELECT
   PARAM_VALUE- is blank
-> OLTPSOURCE- 0CO_OM_OPA_6
   PARAM_NAME - NOBLOCKING
   PARAM_VALUE- is blank.
Could you please check if any other settings needs to be done .
Also for the IP there is selction criteris for FISCALYEAR/PERIOD from 2004-2099, also an inti is done for the same period as a result it becoming difficult for me to load for a single year.
Please suggest.

The problem was the index 4 was not active in the database level..it was recommended by the SAP team to activate it in se14..however while doing so we face few issues se14 is a very sensitive transaction should be handled carefully ... it should be activate not created.
The OBJSELSIZE in the table BWOM_SETTINGS has to be Marked 'X' to improve the quality as well as the indexe 4 should be activate at the abap level i.e in the table COEP -> INDEXES-> INDEX 4 -> Select the u201Cindex on all database systemu201D in place of u201CNo database indexu201D, once it is activated in the table abap level you can activate the same indexes in the database level.
Be very carefull while you execute it in se14 best is to use db02 to do the same , basis tend to make less mistake there.
Thanks Hope this helps ..

Delete Index in Process Chain Takes long time after SAP BI 7.0 SP 27

After upgrading to SAP BI 7.0 SP 27 Delete index Process & Create index process in Process chain takes long time.
For example : Delete index for 0SD_C03 takes around 55 minutes.
Before SP upgrade it takes around 2 minutes to delete index from 0SD_C03.
Regards
Madhu P Menon

Hi,
Normally index creation or deletion can take long time in case your database statistics are not updated properly, so can check stat after your data loading is completed and index generation is done, Do creation of database statistics.
Then try to recheck ...
Regards,
Satya

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

Why LOOP AT XVBAP is triggering multiple times in user-exit in 1 item order

Hi,
Just curious,
I put the break point at LOOP AT XVBAP in user-exit of MV45A include of sales order transaction, then I created a sales order with ONLY one item(10) of 1 quantity (meaning, ONLY one schedule line)....then, Why my break-point(LOOP AT XVBAP) is triggering multiple times? even though there is ONLY one item/1 quantity? is supposed to trigger only 1 time(one iteration) right?
why mupltiple iterations are happening?
thank you

Hello ,
yeah thats true , that exit programs will called several types by SAP itself , so u need to find right FORM exits for ur requirements.
regards
Prabhu

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!

BPM Process chain takes long time to process

We have BI7, Netweaver 2004s on Oracle and SUN Solaris
There is a process chain (BPM) which pulls data from the CRM system into BW. The scheduled time to run this chain is 0034 hrs. This chain should ideally complete before / around 0830 Hrs. <b>Now the problem is that every alternate day this chain behaves normally and gets completed well before 0830 hrs but every alternate day this chain fails</b> there are almost 40 chains running daily. Some are event triggered (dependent with each other) or some run in parallel. In this, (BPM) process chain, usually there are 5 requests with 3 Delta and 2 full uploads (Master Data). The delta uploads finishes in 30 minutes without any issues with very few record transfers. The first full upload is from 0034 hrs to approximately 0130 hrs and the 2nd upload is from 0130 hrs to 0230 hrs. Now if the 1st upload gets delayed then the people who are initiating these chains, stop the 2nd full upload and continue it after all the process chains are completed. Now this entire BPM process chain sometimes takes 17 -18 hrs to complete!!!!!
No other loads in CRM or BW when these process chains are running
CRM has background jobs to push IDOCS to BW which run every 2 minutes which runs successfully
Yesterday this chain got completed successfully (well within stipulated time) with over 33,00,000 records transferred but sometimes it has failed to transfer even 12,00,000 records!!
Attaching a zip file, please refer the 21 to 26 Analysis screen shot.doc from the zip file
Within the zip file, attaching Normal timings of daily process chains.xls the name explains it.
Also within the zip file refer BPM Infoprovider and data source screen shot.doc please refer this file as the infopackage (page 2) which was used in the process chain is not displayed later on in page number 6 BUT CHAIN GOT SUCESSFULLY COMPLETED
We have analyzed:--
1)     The PSA data for BPM process chain for past few days
2)     The info providers for BPM process chain for past few days
3)     The ODS entries for BPM process chain for past few days
4)     The point of failure of BPM process chain for past few days
5)     The overall performance of all the process chains for past few days
6)     The number of requests in BW for this process chain
7)     The load on CRM system for past few days when this process chain ran on BW system
As per our analysis, there are couple of things which can be fixed in the BW system:--
1)     The partner agreement (transaction WE20) defined for the partner LS/BP3CLNT475 mentions both message types RSSEND and RSINFO: -- collect IDOCs and pack size = 1 Since the pack size = 1 will generate 1 TRFC call per IDOC, it should be changed to 10 so that less number of TRFCs will be generated thus less overhead for the BW server resulting in the increase in performance
2)     In the definition of destination for the concerned RFC in BW (SM59), the Technical Setting tab says the Load balancing option = No. We are planning to make it Yes
But we believe that though these changes will bring some increase in performance, this is not the root cause of the abnormal behavior of this chain as this chain runs successfully on every alternate day with approximately the same amount of load in it.
I was not able to attach the many screen shots or the info which I had gathered during my analysis. Please advice how do I attach these files
Best Regards,

Hi,
Normally index creation or deletion can take long time in case your database statistics are not updated properly, so can check stat after your data loading is completed and index generation is done, Do creation of database statistics.
Then try to recheck ...
Regards,
Satya

Process Chain changing start time?

hi guysm i have 76 process chains that run every day in BWD system, so i removed all the timings from the start variant and in the infopackages, but it seems some process chains are still running, i did do the following steps on chnaging the time from a particular time to immediate, Save, Check and activate, i didnt schedule it as i dont want it to load right away .
do i have to hit check , save , schedule once i change the time from a particular time to immediate load or activate will work as well.?
what else could be the cause of process chains still loading even there are no events, or time given to any process chains at all.
i went to sm 37 and i can see the bi process are all running at the time they were orignially set up on.
so any suggestions would help,
is there any way from sm 37 i can tell which process chain is triggered off?
thanks
Dante(devils never cry)

Dante, the start conditions on the infopackages do not affect when they run in process chains. The process chains have their own start job. If you want to change the start time of a process chain, then you need to go to maintain the process chain, right-click on the Start process and select Displaying Scheduled Job(s)... . Here you will see a job called BI_PROCESS_TRIGGER. Change the start conditions of this job.
The start job for all process chains is BI_PROCESS_TRIGGER, so using SM37 may be difficult to identify which BI_PROCESS_TRIGGER job is associated to a particular chain.
Also, to let you know, each process in a process chain has an associated job. All jobs called BI_PROCESS_xxxxx are jobs associated with a process chain.
Eg.
BI_PROCESS_LOADING is an infopackage.
BI_PROCESS_TRIGGER is the start job
Does this help?

Process Chain takes alonf time to run

Hello All,
We have a process chain which loads data for texts, attributes etc.
On certain days the process chain will run extremely fast and maybe take a couple of hours, other days the same process chain may take 24 hours to run. It appears to get stuck when extracting the data from our source system.
Is there any reason for these strange performance issues and does any body else have the same problem? Is there anything that can be done about it?
Thanks,
Nick.

Hi Nick,
This error normally occurs whenever BW encounters error and is not able to classify them. There could be multiple reasons for the same
Whenever we are loading the Master Data for the first time, it creates SIDs. If system is unable to create SIDs for the records in the Data packet, we can get this error message.
If the Indexes of the cube are not deleted, then it may happen that the system may give the caller 70 error.
Whenever we are trying to load the Transactional data which has master data as one of the Characteristics and the value does not exist in Master Data table we get this error. System can have difficultly in creating SIDs for the Master Data and also load the transactional data.
If ODS activation is taking place and at the same time there is another ODS activation running parallel then in that case it may happen that the system may classify the error as caller 70. As there were no processes free for that ODS Activation.
It also occurs whenever there is a Read/Write occurring in the Active Data Table of ODS. For example if activation is happening for an ODS and at the same time the data loading is also taking place to the same ODS, then system may classify the error as caller 70.
It is a system error which can be seen under the Status tab in the Job Over View.
Cheers
Raj

Process chain taking long time

Hi,
I developed a Process chain. In developemnt for Completion of the Update rules(Start routine) its taking 60m( for around 50,000 records).
After transporting the Process chain to Production for Start routine completion (For 1,70,000 records) its taking 7hrs and sometimes its failing as the "Process is Over due" and sometimes due to "Short dump".
How to handle this.........
Thanks

Hi js,
Check the ST22... Any dumps
Check out for the short dump in source system and try loading the delta again
then
I have got the problem when u have posted...but little later.Even I was about to post the issue.. Actually my issue was...
My PC is like this
1) Start Process
2) Delete index
3) Load IP
4) delete overlapping request
5) create Index
6) ABAP program
Process chain hangs at Overlapping requests process type but the status was yellow. And the previous step (3) was success. From there its not moving to next further steps.. But the Job in SM37 was canceled.
I saw Ur post and saw the note 833168 and which matches exactly our issue.
Like we run the PCs thru the TIDAL where due to some problems PC got triggered twice... I can see the two logs in the PC. (Log view) and two requests at RSMO.
Everything was recovered again thru manual steps. This is the first time we encountered... the note helped us ... We now are very cautious about the Tidal runs...
Now PC is running perfectly
we have instructed the Supported team to make the necessary changes or fix this issues in TIDAL...
i hope this is helpful to u
bye now
suresh

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

Trigger Process chain at set time or when an event is raised.

Hi All,
I have a requirement where a process chain should get scheduled at fix time, say at 1:00 AM. Also, it should get scheduled when an event is raised by one BSP application. So, its like Set time OR Event should trigger the chain. Can you please guide, how can i implement this without using a special SM37 job?
Thanks and Regards,
Harpal

Hi Gohil,
The steps to create an event is as follows:
1. Create the event with SM62.
2. In the process chain, maintain your Start process. In the change selections screen, choose the button 'After event'. On the bottom, select your event. Click also on 'Periodic job'.
3. Activate and schedule your process chain. It will then be visible in SM37, waiting for the event.
4. Then you may raise this event from any ABAP program with function module BP_EVENT_RAISE. Each time you raise the event the process chain will start. You can raise the event also manually with SM64.
If you want to fix a time i.e., at 1:00 A.M, you need to got RSPC tcode --> click on the chain --> right click on Start variant --> Click on maintain variant --> Change selections --> Click on Date/Time --> Give the date and time.
If you want to ru7n your chain daily or weekly like periodically, check Periodic Job and click on "Period Values" and select accordingly. Now save everything and click on start variant and activate and schedule your chain.
Also check below thread for more info on Event:
Triggering a Process Chain From R/3 pgm
Regards,
KK.

Scheduling process chain 3 specific times a day

Hi ,
my requirement is to schedule a process chain 3 times a day.
i have gone through the forum and got the solution EVENTS.
please provide me how to do this in detail like step by step.
how to create a event in SM64 and how we will define the time there.
and creating a ZPROGRAM with the function module (please provide step bystep).
thanks
Sridhar

You create user events in SM62. In SM62, next to "User even names", click on <b>Maintain</b> and press Enter. Click on the Create icon to create a new event (let's call it ZEVENT).
Next, in your process chain, change the Start variant to be scheduled "After event", and put in ZEVENT for the event name. Also, click on the "Periodic job" at the bottom. This will automatically reschedule the jobs for the process chain after it executes.
Next, create an ABAP program (let's call it Z_EVENT_RAISE) to call the function module BP_EVENT_RAISE. You're code can look like this:
REPORT Z_EVENT_RAISE.
PARAMETERS: P_EVENT LIKE TBTCO-EVENTID.
CALL FUNCTION 'BP_EVENT_RAISE'
EXPORTING
EVENTID = P_EVENT.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
This ABAP program will prompt for an event name, so you will need to create a variant (let's call it ZEVENT) which will save the value of the event name (also ZEVENT). You will need the variant name to be able to trigger the event in a batch job.
Now all you need is the batch job. Use tcode SM36 to create a batch job where you call the ABAP program (Z_EVENT_RAISE) using the variant (ZEVENT).
Note, SM64 only triggers an event manually.
Does this help?
Oh, and you can copy this job to schedule it three times a day.
Message was edited by:
Geo

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.

Process chain fails every time at "roll up of aggregates"

hi all,
A process is deffined in such a way that...                                        start
                                                                                i
                                                                                i
                                                        Delta loads to infocube1(load) deltaload to infocube2(load)       deltaload to infocube3(load)
                                                                        i                                                 i                                          i
                                                                        i                                                 i                                          i
                                                        delta load of aggregate(cube1)   delta load of aggregates(cube2)     delta load of aggregates
Every time when this process chain get executed,this fails at delta laod of aggregates step.If i repeat again it works fine.But repeating is not a solution for this.So,i want a permanent soltuion for this..
Please guide me what to do?and explain me why this happens.
Error message:-process rollup of filled aggregates/bia indexes,variant delta load of aggregates
Thanks( in advance)
Moushmi

Hi Moushmi,
Have you checked if the system has processes available while the chain is running? It could be that your system is overloaded and the aggregates wouldn't roll up because you have no processes or available memory.
Check with your Basis resource. Also, try changing your chain to do only 1 at a time. Do you have many aggregates to load, are they big, and most important are they being used.
Kathleen

Process Chain Triggers Multiple times

Similar Messages

Maybe you are looking for