Process Chain delays

Process chain delay has default of 5 sec ,can that be reduced ??
is there any functional module,or program which can reduce this delays more??
thanks

Hi,
we are encountering problems within the Process Chains. we have created a series of process chains that start everyday after 6.00pm. They all start in a sequence, some are set to start at 6.00pm and some are to start 7.00, some at 7.30pm. The subsequent jobs or infopackages that are being called within the chain, takes time to process or there's a delay and because of this all the subsequent PC chains are getting delayed.
We are in 2004s, SP10.I didnt set any delay time between the process, I had tried
activating/recativating all the process chains. Nothing seems to help.
Please advise.
Rgds
Gopakumar

Similar Messages

Process Chain delayed to load

hi Experts,
am using BI 7.0(BW 7.0) my process chain is scheduled to run daily morning, it works fine, sometimes it gets delay in loading the data for even a longtime or stucks in the early start itself.Please help me in having a solution so that the process chain doesn't stuck or how to reduce the loadtime.
thanks
Sankaresh S

One reason could be the system resources are maximum utilized when this process chain was about to start. If it's the case you can change the schedule time.
You can check the Monitor screen - details tab for further information when it gets hanged and also check the job log / status of job in SM37 / any dumps recorded in ST22 ?

To set delay in process chain using a program

Hi all,
We have a requirement in which the loads from nearly 15 sources (DSO) gets loaded into the Cube thro 15 process chains. The source gets loaded from the PI interface. So it might happen that simultaneously 10 loads will be started and reach the cube.
In the cube we have delete overlapping request, so its gives a deadlock when the chains try to delete the prev. request at the same time.
What we have planned is if we can write a program that will set a delay depending on the lock entries present for that particular cube. But still we are not sure how far this will help.
If anyone has faced a similar issue or can anyone suggest on this would be much appreciated.
Thanks
Merlin

I believe in each of your 15 local chains you have the load to Cube process.Why dont you take the load to the Cube out of the local chains and in the meta chain you could sequence the loads from the 15 ODSs so that you can have a parallel processing upto the ODSs ( assuming the rest of the local chain is used to fetch from R3 ) and then sequential to Cube.
I dont think writing a program will help much here.

Set delay for process in process chain (BI7)

Hi gurus.
Can anybody advice me on how to set delay for a process in process chain in BI7
Thanks in advance

Hi,
If you right-click on a process in the Process Chain, there should be an option called Debug Loop. Here you can enter the number of seconds to delay a process.
The only difference between 3.5 and 7.0 is that Option Waiting Time in context menu of "any" process is replaced by Debug Loop.Here you can enter the # of seconds for which you want your process to be delayed.
See below:
Re: Start a Process Chain after every 15 mins
Hope this helps.
Regards
CSM Reddy

How to stop the process chain on every saturday and delay until sunday 6 am

Hi experts,
We have a maintanence window on every saturday until 6 am on sunday.
My question: I don't see any option in the start variant of the process chain under restriction to stop the process chain on saturday and delay the run until sunday 6 am. Any idea?
Please let me know the steps. Thank you in advance.
Sharat.

how to create a event for a process chain? please let me know step by step instructions.
Also I will schedule the regular process chain until friday and use the new variant to schedule it on sunday at 6:00 pm right?
Thanks in advance.
Sharat.

How to Delay an Event in a Process Chain

Hey,
We have a scenario in which we need to schedule a process chain in such a way that,the main chain contains the DSO load and the local chains contains the Cube load (One for NA and other for EU).
I want to schedule it in such a way that two local chains of the main chain should be triggered at different times.

hi...
I think its getting pretty complex....instead of writing programs..use simle metachain thing which will solve your issue with simple process chain design.
You have :
Main Chain
{Dso load
Local Chain A(Eu) Local Chain B(Na)
Now what you want is on the first run the main chain should trigger and only Local Chain A trigger.
While on second run
Main chain + Local chain B trigger.
the simplest soultion
Create 2 Metachains like below:
PC1.
Main Chain X
{Dso Load
Local Chain A(Eu)
PC2.
Main chain Y
{Dso Load
Local Chain B(Na)
Now create metachain to combine
Main Chain
{PC1
PC2
So PC2 will start only when the PC1 has finished.
Let me know if it is feasible for you.
Regards,
RK

E-mail delay using "Event Data Change" in process chain

Hi Experts.
I can´t figure out why my process chain is taking so long to deliver a simple e-mail.
The BEx Broadcast Configuration is working fine. When I run it manually, the e-mail comes instantly. But when I use process chain (Event Data Change), it takes hours to receive the e-mail. The option to run after the infoprovider data change is set for this configuration.
Is there any additional configuration I have to check?
All answers are welcome!
Kind Regards,
TP

Hi Arvind. Thanks for your repply.
I was already checking the SOST and also SCOT and RSBATCH to see if the jobs are running fine, and no problems so far.
How can I check the IDOC´s?
Thanks in advance.
TP

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 excessive run time

Hi all
Would like to know if any of you have experienced what we are experiencing.
We have a process chain that runs every night. It is running the same master data which usually only takes seconds.
However, on occassions, the same amount of data is taking over 18 hours to load.
When we look on monitor in the detail tab, it shows that it has only taken seconds but the header tab is showing 18 hours. This then delays any other subsequent process chains from being kicked off.
We are investigating as to why this is happening but any comments would be appreciated.
thanks in advance
Sandra

Hi Sandra,
I can suggest you few things which may help u...
1) Increase the parallel processing during extraction
2) Selective loading.
3) Every job will be having a priority (A, B, C A being the highest and C being the lowest), choose this based on your scenario.
4) Check with basis for the sizing of your server.
5) You can increase the number of background processes during data loads. This can be done by making dialog processes as Background processes.
For this you need basis inputs. (This is done in some profile settings by making the system behave differently during loads. (something like day mode/night mode))
6) There are some maintenance jobs that should run regularly in any SAP box to ensure proper functioning.
7) Use of start routines is preferred instead of update routines.
Assign points if these help u...
Regards,
KK.

Process chain taking long time to complete

Hi,
I am having following issues in the process chain daily loads
1) The PSA deletion is taking very long time on fridays only (nearly 3 hrs). Other days it gets deleted in 1 hr max.
2) Just to load 381 records via dtp from DSO to cube takes nearly 2 hrs(Delta load). No major routines are written in the transformation.
How to analyse a process in process chain which does not fail, but takes very long time to complete. Is there any tool or transaction in BW which can help us to analyse why the process chain takes so long time to complete in different days. One day it completes in 8 hrs, another day it takes 12 hrs.
None of the transactions, SM37, SM50, SLG1, LOGS etc are giving me any help to analyse this issue.
If it fails we have error logs to check and analyse, but without failing how we can analyse and fix the delay and reduce the time of loading data. Please guide me.
Thanks in advance.
Vishwanath

Hi.......
1) This might be due to the poor performance of the system ..there wont be enoughwork processes avilabe in teh system .- What needs to be done if it does not have enough work processes available. Though I can find that lots of dialog processes were free during these jobs as well some Background processes were also free.?
Look to increase Work Process.......................u can do two things..............U can cancel some Job...........which r not progressing...........or which r not very important for the time being..........
Or if possible........u can increase number of servers..........
Look When a Job will start...............first it will run in background.............u can start in in Dialog also..........but for Dialogue after some time ..load will go to time out.................now many Child jobs will be created for a single background jobs..............they may run in Dialogue..........u can monitor them through SM66............
2) Check ST04 for lock waits and dead locks ..if the same lock persist for long then check with basis team.
What needs to be conveyed to the basis team when these locks happen?
generally these will be temporary Locks.............after some time locks will be realeased..............if they persist for a long time...........then u can contact Basis people..........Or if u can understand that which job is creating the lock.............like if u double click on the job >> click on Job details...............from there u will find the PID................copy that.............and check in ST04..........whether they matches or not..............now suppose it match.............and u know that job is not very important............then u can cancel the job.............
Check also the table space availba in St04 . the usuage should nt be more than 90%
What needs to be conveyed to the basis team if the usage is more than 90%.?
U can ask them to increase the Table space........
Check the sm37 >> delay column it should nt be high
What needs to be done if delay column is high. Actually it is high for these jobs (PSA deletion and load from DSO to Cube visa DTP (Delta load)?
If Delay is more.............it means ...........that there is no free work process...jobs r going to Release state............solution I had already given u.......
Check the PID refeclting in lock waits in sm66 wether they are progressing or nt ..
If they are not progressing what action needs to be taken?
Actually...........suppose one Dialogue job is running............it may change..........ie that Dialogue job will go to Stop status.........some other job will start............anyways if it does'nt progress............u can cacel the JOb.........
Check OS07 for DB if the idle time is less then 20% then its a problem ..
If the Idle time is less than 20% what action needs to be taken?
U can contact the Basis people.......
Check sm21 and RFC connection with other source systems in sm59 ..
What needs to be checked in SM21 and SM59 specifically? What parameter i need to check?
In SM21.............if red status is there............check the Log beside that..............may be it will be some Terminal disconnected.......
In SM59...........clck on test connection..........
if the problem is occuring due to only one source system then check the performance of that system ..
How to check the performance of these systems? Any tools available in R/3 system to check its performance?
No.....in this way u can check performance for all the source system...........go to SM59............double click on the desired source system>> click on test connection......
If All these are persisting then its a performance problem and check with basis team ..
Is there any special settings which needs to be maintained to achieve better performance of Process chain loads?
U can Improve the performance of process chain by Parallel Processing..........ie split the loads by giving selections...........and execute thenm in parallel..........
Regards,
Debjani........

Alerts not updated / still grey in BPMON BI Process Chain

Hi All,
We have Solution manager 7.1 SP08. We configured BPMON for BI PRocess chains.
We are unable to get any alerts for process failures. All the alerts are Grey.
This is what we have observerd:
1. We get alerts for failure to start if I mention "Not Started On Time (marked for 14:00)" and "Start Delay" alone.
2. No alerts are generated for the Status of the chain. I have provided Yellow for Status J and Red for R,X or J.
3. The BW Process Chain Identification - Start Procedure is set to "User chain start condition".
4. The Alert for STart Delay seems to get triggered only at midnight of everyday (00:00). Is this normal?
When I check the rspcm logs, the chain we have configured seems to have errors at 00:37 and every one hour from then.
The BI and Solman systems are in different time zones in SAP System level.
I have checked note 1436853 and all are in order. None of the notes can be implemented in the satellite system.
I have provided full authorization for both the user id logged in to BPMON as well as the connection user to the BI system.
Can you please suggest what we missed in the configuration?
I had configured Purchase requisition monitoring for ECC system, Background job monitoring for the BI system also. These seem to work fine.
Only the BI Process chain status and related montioring seem to be grey all the time.
Thanks and regards,
Raghavan

Hi,
BW process chain alerts are purely depends on the start procedure you define during the alert configuration.
Moreover if you wont get any alerts if the bw proces chain not started or it started before the configured time, in such case you can use "not started on time" with tentative starting time of the process, or you can use "out of time window" to set the time slot where the chain didnt run.
please check https://websmp101.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700006137532006E page number 76
Thanks
Jansi

How to identify what are all the errors appears in process chain,

Hi all,
i have a process chain running, but i want to find out what are all the errors that the process chain has thrown
thanks
pooja

Hi Pooja,
Errors in monitoring:
SID error
Reason: If the corresponding master data is missing for the particular transaction data.
         1. Check for the load timing for the respective master data, if it less than an hour then make the request red and repeat the ip.
         2. If the data is loaded to PSA then you have to delete the request from target and manually push the data to from PSA.
         3. If we are required for selective update then note down the info source from header and find it in RSA1,select the one with Single as postfix.
         4. Goto data selection tab and change the range.
Tip: change the last 4 digits for from to 0000and the last 4 digit for to     9999.
        5. Repeat the ip.
         6. In case only of failure in one target goto RSA1 find the PSA, put he request no. and reschedule it.
Note: IF PSA is present never make the request red rather delete it.
Replication error
Reason: Data source replication Failed.
         1. In order to handle this error you should be known to IP, info source and source system.
         2. Goto RSA1, find the data source in the source sys tab.
         3. Right click on the data source and replicate it.
         4. Since all the transformation rules pertaining to this data source need to be reactivated so go to SE38 and execute rs_transtru_activat_all, data source and sys name.
         5. Delete the red request from the target.
Update R not supported
Reason: The corresponding initialization flag for the ip is lost.
         1. Goto header click on the ip and goto schedule tab and click initialize in the source system, whatever screen appears delete the only request present(the initialization flag).
         2. Goto RSA1, find the ip in the info source (one with the Adhoc initialize flag).
         3. Goto update tab and select Initialize delta process try going for with data transfer.
         4. Reschedule the IP.
Duplicate Record Error
Reason: Duplicate error records for the loaded master data.
         1. Goto info package via header or via RSA1.
         2. Goto processing tab and change the ip setting, selecting only PSA and ignore duplicate records and re run the ip.
         3. Do remember to change the ip settings back to the original once after the second step.
ODS activation failure
Reason: Prerequisites for ODs activation not satisfied i.e. unique key.
         1. Goto maintain variant.
         2. Check for the QM status of the requests in the target they should be green.
         3. Then click the ODS activation tab.
         4. In the screen which appears put the requests for which ODS activation failed.
         5. Activate these and keep on refreshing them until status reverts from green,
Remember to refresh these requests one at a time.
         6. If requests are red then delete them from target.
         7. Reschedule the IP.
Note: Never Try activating ODS manually if it is Y1.
Aggregate Rollup error
Reason: No aggregate found for the respective rollup.
         1. Click on the variant in which the error occurred.
         2. Goto chain tab and copy the variant and instance.
         3. Run the nestle provided program YBW05.
         4. Put in info in there and put the status as g green.
         5. Execute and refresh the status.
Lock issue
Reason: The same ip is been locked by other user or may be used by other process chain.
         1. We can see the locked entries and in the transaction SM12.
         2. Wait for the other process to get complete once the ip loads to target in that process then there is no need for running it for the process.
         3. In other case make the request red, when PSA is present then goto environment tab ->schedule->initiate update.
         4. In the box appears select update in the background.
         5. And the manually update the failed IPs by selecting manual update in the context menu.
Alfa confirming value error, Time conversion error, Chain didnt start, Delay due to long running job, Poor system performance,Heirarchy node exist in duplicate.
Reasons:
Alfa confirming error: Data format mismatch.
Time conversion error: Date, time format mismatch.
Chain didnt start: A scheduled chain didnt triggered at the prescribed timing.
-For all the above error we have to raise a ticket.
Idoc or TRFC error
Reason: An Idoc is been stuck somewhere.
         1. Reload the Master Data manually again from Info-package at RSA1.
         2. Release the Idoc.
         3. In the source system level got environment->transaction->Transaction RFC or Data ware housing level.
         4. In the Screen if the status is Transaction Recorded it means its stuck goto edit and click Execute LUW or press F6.
         5. If status is Transaction executing then it means its fine wait.
         6. Or raise ticket.
Error Due to short Dump
Reason: Error due to Short dump could be due to many reasons i.e. memory, table space, lock, error record, page allocation, failed change run.
Process terminated in the Source system.
           Reason: Sometimes we face that a load has failed due to job Termination at Source System.
      This happens due to unavailability of the source system or some connectivity problem between source and target systems.
1.      Make the request red.
2.      Delete the request from the data target.
3.      Reschedule the ip.
4.      If still the job fails raise the ticket.
And also check in following links:
Process Chain Errors
/people/mona.kapur/blog/2008/01/14/process-chain-errors
Common Process chain errors
For Data Load Errors check this blog:
/people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
Pls assign points if it helps u,
Thanks & Regards,
Madhu

Info Package failing in Process chain

Hi,
One delta load InfoPackage fail every time in process chain with error message "Last Delta upload not yet completed".
Actually this infopackage load data in cube but in procuress chain log, it turn red and in the display message window, under tab "Chain" the request id is not the one which loaded data but different one.
This issue is delaying the upgrade and URGENT in nature.
PLEASE HELP....
Regards,
Anil

Hi Anil
You are trying to complete a delta load while the previous one is not finished. Please check the monitor for the previous load. You can use the manage tab to set a load to completed, or you can delete the load.
If its hung (yellow) or in red goto the QM status in monitor and mark the QM status red. Then goto the data target and delete red request.
Go back to the delta infopackage and schedule the job again. this time it'll prompt you for a repeat delta. Click OK and the delta load will start again. This'll bring the data for the old failed delta as well as any changes or new records as well.
Hope this Helps
Anand Raj

Problem with triggering process chain

Hi
We have a remote process chain that calls a process chain in another system.The process chain in the other system is not getting triggered with the remote chain.
We have 3 such remote chains and we are facing such a problem with only one of them.
The process chain in the other system has a start variant which gets triggered( i suppose) and gives an instance id...the next step in the process chain is to load data into a ODS.Now this step remains yellow forever.When i manually try to schedule this step it gives me records and the request in the monitor screen turns green.But the process chain step continues to remain yellow.
What can be a way out for triggering the process chain or where could the problem be?
Please help
Thanks,
Suchi

Hi Suchitra,
Even though ur process seems to be in yellow your data loading may be completed and the reason for it may be the delay in activation of ODs by ur PC.
For your information please go through the below infm provided in SAp Library
Note when loading into an ODS object and for the subsequent, event-controlled update:
If you switched on the automatic activation in the ODS maintenance or administration, the monitor status for the request remains yellow after the load was successfully completed. Nevertheless, the subsequent processing for the InfoPackage is started, because the loading process is successfully completed.
[http://help.sap.com/saphelp_nw04/helpdata/en/65/163d3873130057e10000009b38f842/content.htm]
I hope ur doubt is clear.
Regards,
Rajkandula

Raise event from within process chain

Is there some way to easily raise an event from within a process chain? The only way I know to do this is to run an ABAP program that raises the event.

Hi Shashank,
sorry for the delay: I didn't notice your question. Try this way.
1 - define ABAP Report Z_EVENT_RAISER (see sample code below)
2 - define a variant for this Report (Event Name mandatory)
3 - Call ABAP Report Z_EVENT_RAISER from within your Proces Chain.
This should work
Hope it helps
GFV
*====================================================
*& Report Z_EVENT_RAISER                                              *
REPORT Z_EVENT_RAISER                          .
selection-screen begin of block parametri with frame.
parameters:
EVENT like BTCH1250-EVENTID obligatory,
PARAM like BTCH1250-PARAMETER.
selection-screen skip.
selection-screen end of block parametri.
CALL FUNCTION 'BP_EVENT_RAISE'
EXPORTING
    eventid                      = EVENT
    EVENTPARM                    = PARAM
TARGET_INSTANCE              = ' '
EXCEPTIONS
BAD_EVENTID                  = 1
EVENTID_DOES_NOT_EXIST       = 2
EVENTID_MISSING              = 3
RAISE_FAILED                 = 4
OTHERS                       = 5
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
*====================================================

Process Chain delays

Similar Messages

Maybe you are looking for