Process chain stopping in middle

process chain stopping in middle , after a info-object present in the process chain has been manually set to green.Please advice me what to do????

Hi,
Please follow the below steps:
Step 1: At the step where the process chain is stuck
Go to display messages -chain- copy variant, instance & start date
Step 2: Go to se16, table rspcprocesslog  execute
Copy as below,
Variant-- variante
Instance instance
Batch datestart date
This will give a single entry in the table rspcprocesslog.
Step 3: Go to se37, input FM RSPC_PROCESS_FINISH and execute
Copy
Rspcprocesslog u2013 instance -
I_INSTANCE.
Rspcprocesslog u2013variante -
I_VARIANT
Rspcprocesslog u2013 logid----I_LOGID
Rspcprocesslog u2013 type ---I_TYPE
Enter u2018Gu2019 for parameter I_STATE and press execute (F8).
After executing the above FM, with the above stated parameters, the actual process will be set to green and the following process in the chain will be started and the chain can run to the end.
-Vikram

Similar Messages

Function module used to restart the process chain in the middle?

Hi all,
can anyone pls let me know the function module to restart the process chain in the middle of the process chain?
I need to run the process chain from the middle which can be done through a function module can anyone pls let me know!!
Thanks
pooja

what exactly your requirement is?
You can't trigger the process in the middle either it should be trigger by start variant or it's predessor.
If your chain failed in the middle - you can fix the prob and can do 'Repeat' option or you can also use FM 'RSPC_PROCESS_FINISH . (this FM will work only if the chain fails)

How to stop process chain job in middle

Hi,
I have designed process chain ,to trigger following sequence of jobs
Step 1 Switching from Transactional cube to Basic cube and Vice versa.
Step 2 Loading data from Transactional cube to basic cube.
Step 3 Buffering the Scorecards.
My question is From Step1.
where i am using one ABAP program as process type( ABAP program functinality is it will switch Transactional cube to Basic cube if there is any yellow request in Transactional cube,If there is no yellow request in the Transactional cube,it should stop from step 1 it self, but I wrote a code to throw error to stop the job, in that case in sm 37 I am able to see cancelled job of this process I don't want to see cancelled job in SM 37 since this prcess chain has been sheduled for every 1 hour, is there any way to stop this job to not to proceed successive process. please give me some input from ur side
Thanks in advance.
Best Regards
Shiva

Hi Shiva,
This is what we have done here:
1. Change the ABAP process type from "Process ends non-specifically" to "Process ends successful or incorrect" from Settings => Maintain Process Type.
2. Copy SE37 function "RSPC_ABAP_FINISH" to a Z-function. Add state as the input parameter and pass that to l_s_log-state and i_state (In Function Call).
3. Now in your program if you want to execute further step call this Z-function with status "F" else with "R" and give your ABAP Variant Name as the other input.
Let me know if you need more help.
Regards,
RB

Process chain stopped in the middle ?

I have a PC in production and its really strange that after the DTP step ,ODS activation step in the PC did not run and the chain status shows in the yellow color, I know if it fails in the activation step we need to see the error and fix it. But here neither its yellow which means running and not red, its just did not execute and the dtp is successful....and there are a lot of chains next to this chain. SO how to make it run, and what do i do ? there is no job running in the SM37 related to it. Please help.

Hi ,
Please perform the below steps, this will solve your issue.
Step 1: At the step where the process chain is stuck
Go to display messages -chain- copy variant, instance & start date
Step 2: Go to se16, table rspcprocesslog  execute
Copy as below,
Variant-- variante
Instance instance
Batch datestart date
This will give a single entry in the table rspcprocesslog.
Step 3: Go to se37, input FM RSPC_PROCESS_FINISH and execute
Copy
Rspcprocesslog u2013 instance -
I_INSTANCE.
Rspcprocesslog u2013variante -
I_VARIANT
Rspcprocesslog u2013 logid----I_LOGID
Rspcprocesslog u2013 type ---I_TYPE
Enter u2018Gu2019 for parameter I_STATE and press execute (F8).
After executing the above FM, with the above stated parameters, the actual process will be set to green and the following process in the chain will be started and the chain can run to the end.
You can also check this blog:
/people/siegfried.szameitat/blog/2006/02/26/restarting-processchains
-Vikram

Process chain stopped and unable to trigger next process

Hi all , i am working on process chains, today process completed at DTP and the next process at activation of dso process failed and the rest of the pc completed even though the activation process is red. after the completion of that , chain process stopped, next pc didnt started. plz help me wiht this, thanks in advance..

you can evaluate a local chain as 'green' even if one of the steps is 'red'. in the planning view of the process chain, go to process chain --> attributes --> process status valuation. flag the checkbox. this will enable the next pc to start even after a red status of the local chain...
detailed info:
Red Outcome Renders Chain Green If Process Is Red
If errors are raised for processes that have scheduled an event "With Errors" they are judged as successful for the determination of the overall status of the chain run.
Use
If this indicator is set, all the processes in this chain with errors are judged as successful with regard to the overall status of the run, if they have scheduled a successor process "With Errors" or "Always".
Dependencies
Mailing and alerting is not affected by this indicator. This is also triggered for processes with errors if this has a successor process "With Errors".
Example
You use this indicator in meta-chains to evaluate the run of a subchain as successful in spite of errors in "unimportant" processes. The successors to this process are "always" scheduled, while the successors to key processes are only scheduled "With Success".
Accordingly, successors in the subchain within the meta-chain are only scheduled "With Success"; however they do continue to run if errors have only occurred in the unimportant processes of the subchain.

Process chain stops - previous processes are green

Hi All,
We have a process chain that loads our master data each night. It chain is mostly made up of infopackages (mostly full loads) and the change run for those objects. We recently upgraded from 3.5 to BI7, SP16.
Since the upgrade, this chain, and a few others just seem to stop. They will start, and successfully complete some of the processes in the chain (all green), but then will not move on to the next process. The next process will not be yellow, it just won't start. The overall status of the chain is yellow.
I am 100 percent sure there are no other chains running during this time frame. This chain has been running for over 4 years in production, and we have never encountered this issue.
Last night, I removed the chain from the schedule, and then rescheduled. I'm not sure if that is going to prevent us from having this issue. I have also set the priority to high.
Should this prevent us from encountering this issue again? I have searched OSS and found some related notes, but we are on a higher support pack than what is in the notes, so they are already applied.
Any suggestions?
Thanks!
Charla

The first thing that I'd recommend is to look at the Start Process Variants for the Process/Local Chains that are not starting. Specifically, I would check to see if the scheduling in those Start Process Variants are set to Direct Scheduling with Immediate Start or set to Start Using Meta Chain or API. It is possible that the conversion from BW 3.x to BW 7.x change the parameters of the scheduling withing the Start Process Variants, even though they were not physically changed and transported.
My recollection is, when we upgraded Support Package Stacks, we had some Local Chains just change on their own where the Immediate Start checkbox mysteriously become unchecked.

Process Chain stops if no data

Hello,
My proccess chain stops if one of my infopackages doesn't return any data. How do I change the settings so no data returns a 'success' status??
Thanks
Sheena

Hi,
if there is no data then you process will be in yellow colour, and other process are waiting for this, we are also having the same problem and we change the status in monitor to green from yellow couple of times after that system automatically converts the status to green from yellow even though there is no data, i think you can try this option, which we used earlier and working fine now.
Regards
Sankar

Help with Process Chain - Stop remaining Processes if Package returns 0 rec

Hi, i have a Process Chain that starts with a single InfoPackage. Then it goes on to distribute the load to multiple DSO's and then onto DSO Activation. I would like the Process Chain to stop right after the InfoPackage if no records are loaded.
Is this possible using the decision variant somehow? Any details on how to achieve this are greatly appreciated!

Hi ,
The request is goin to red status when 0 records are pulled in. There is a option in info package so that even when 0 records come in the request status would be green.
Open your info package , then in the menu goto "Scheduler > Treatment of warnings > Select Green" so that in future even if the info package pulls 0 records the status would be green . then the activation step in the process chain would also be carried out smoothly.
In this way you need not manually change any request status to green . Saves you time.
regards
Venky

Process Chain Stopped in BI PRD

Data Loading Error :
Hi All,
In BI PRoduction, all the process Chains are stopped and while Checking the errors, it is giving the error message as
Errors while sending packages from OLTP to BI
Diagnosis
No IDocs could be sent to BI using RFC.
System Response
There are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of BI.
Further analysis:
Check the TRFC log.
You can access this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
Error handling:
If the TRFC is incorrect, check whether the source system is fully connected to BI. In particular, check the authorizations of the background user in the source system.
Morning, I have logged into BW Production, and saying BW Production is down. This is happening frequently.By the help of basis, the system is up.
Please help on this issue.
Thanks,
Jelina.

Thanks for the reply.
I have Checked in ST22 and found, Time Out error is there.
These are the error messages in ST22.
The program "SAPMSSY1" has exceeded the maximum permitted runtime without interruption and has therefore been terminated.
Error Analysis :
After a specific time, the program is terminated to make the work area available to other users who may be waiting.
This is to prevent a work area being blocked unnecessarily long by, for
example:
- Endless loops (DO, WHILE, ...),
- Database accesses with a large result set
- Database accesses without a suitable index (full table scan)
The maximum runtime of a program is limited by the system profile
parameter "rdisp/max_wprun_time". The current setting is 3600 seconds. If this time limit is exceeded, the system attempts to cancel any running SQL statement or signals the ABAP processor to stop the running program. Then the system waits another 60 seconds maximum. If the program is then still active,the work process is restarted.
How to correct the Error :
Programs with long runtime should generally be started as background jobs. If this is not possible, you can increase the system profile parameter "rdisp/max_wprun_time".
Depending on the cause of the error, you may have to take one of the following measures:
- Endless loop: Correct program;
- Dataset resulting from database access is too large:
Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table
(for example);
- Database has unsuitable index: Check index generation.
If the error occures in a non-modified SAP program, you may be able to find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following keywords:
"TIME_OUT" " "
"SAPMSSY1" or "SAPMSSY1"
"REMOTE_FUNCTION_CALL"
If you cannot solve the problem yourself and want to send an error notification to SAP, include the following information:
1. The description of the current problem (short dump)
   To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
   Display the system log by calling transaction SM21.
   Restrict the time interval to 10 minutes before and five minutes after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP program: The source code of the program
   In the editor, choose "Utilities->More Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
Thanks,
Ram
Edited by: Ram Siva on Jul 28, 2009 6:59 AM

Process chains stopped

Hi,
I am new to BI, my BI server got shotdown due to some reason and process chains are stopped. so how do it re run again? how do check which are stopped and how do re run manually ? any problem if we run manually ?can pls help any body. thanks in advance.
Sari. K.

Hi Sasi,
Plz find here one of our expert explanation..
How is it possible to restart a process chain at a failed step/request?
Sometimes, it doesn't help to just set a request to green status in order to run the process chain from that step on to the end.
You need to set the failed request/step to green in the database as well as you need to raise the event that will force the process chain to run to the end from the next request/step on.
Therefore you need to open the messages of a failed step by right clicking on it and selecting 'display messages'.
In the opened popup click on the tab 'Chain'.
In a parallel session goto transaction se16 for table rspcprocesslog and display the entries with the following selections:
1. copy the variant from the popup to the variante of table rspcprocesslog
2. copy the instance from the popup to the instance of table rspcprocesslog
3. copy the start date from the popup to the batch date of table rspcprocesslog
Press F8 to display the entries of table rspcprocesslog.
Now open another session and goto transaction se37. Enter RSPC_PROCESS_FINISH as the name of the function module and run the fm in test mode.
Now copy the entries of table rspcprocesslog to the input parameters of the function module like described as follows:
1. rspcprocesslog-log_id -> i_logid
2. rspcprocesslog-type -> i_type
3. rspcprocesslog-variante -> i_variant
4. rspcprocesslog-instance -> i_instance
5. enter 'G' for parameter i_state (sets the status to green).
Now press F8 to run the fm.
Now the actual process will be set to green and the following process in the chain will be started and the chain can run to the end.
Of course you can also set the state of a specific step in the chain to any other possible value like 'R' = ended with errors, 'F' = finished, 'X' = cancelled....
Check out the value help on field rspcprocesslog-state in transaction se16 for the possible values.
Regards.....KP

Process chain stops in infopackage with yellow status

Hi Gurus,
We are experiencing some difficulties regarding the use of process chains with warnings. Our SAP BI system is connected to an ETL server which feeds us with data from other systems. We have a query that has a push-button functionality that starts a process chain beginning with data extraction with an infopackage and ending in a infocube. The problem we have nowadays is that whenever the ETL workflow fails the infopackage status remains yellow, while our objective would be a red status. To try and solve this problem we forced a timeout in the infopackage. Once we check the log in the process chain it displays a message containing something like "status request modified , do you wish to add subsequent processes?", if we say yes it refreshes the status of the infopackage to red and it all goes ok. What we want is to get rid of this warning and that the status is automatically changed. We've checked other posts and we didn't reach any conclusion... Note 708480 gives us a possibility of automatic desicion but how could we integrate it in our process chains since it is based on shcedulling and not triggers?
Your help would be much appreciated,
Thank you
Bruno Rodrigues

Hi,
We have two connected links in the process, one to continue the process chain when process status is green and other link to red status. The problem is the process status remains yellow until our confirmation in pop-up.
The process chain should be started by user in web browser. So, it isn't possible run it in background.
Thank you,
Regards,
BR

Restarting Process chain from the middle

Hi all, I have a question about process chain in BW7.0.
When the error has occured in the process chain, is there any way to restart the process chain from where the error has occured?
One of the way I came up with was to set the process type into Repairable from Repeatable,but when I try to change the status,the warning message shows up and I can't change it.
Is this the right idea,or is there any other way to do it?
Can any one tell me?
Thanks in Advance,
Hiroshi Iwanaga

First of all, find out the rootcause of the failure of the process step that failed and finish it manually. Then, go to the process chain...
Open the messages of a failed step by right clicking on it and selecting 'display messages'.
In the opened popup click on the tab 'Chain'.
In a parallel session goto transaction se16 for table rspcprocesslog and display the entries with the following selections:
1. copy the variant from the popup to the variante of table rspcprocesslog
2. copy the instance from the popup to the instance of table rspcprocesslog
3. copy the start date from the popup to the batchdate of table rspcprocesslog
Press F8 to display the entries of table rspcprocesslog.
Now open another session and goto transaction se37. Enter RSPC_PROCESS_FINISH as the name of the function module and run the fm in test mode.
Now copy the entries of table rspcprocesslog to the input parameters of the function module like described as follows:
1. rspcprocesslog-log_id -> i_logid
2. rspcprocesslog-type -> i_type
3. rspcprocesslog-variante -> i_variant
4. rspcprocesslog-instance -> i_instance
5. enter 'G' for parameter i_state (sets the status to green).
Now press F8 to run the fm.
Now the actual process will be set to green and the following process in the chain will be started and the chain can run to the end.
Of course you can also set the state of a specific step in the chain to any other possible value like 'R' = ended with errors, 'F' = finished, 'X' = cancelled ....
Check out the value help on field rspcprocesslog-state in transaction se16 for the possible values.
Assigning points is the way of saying thanks in SDN.

How to stop a process chain after the current running process

Hi experts,
I try to stop a running process chain, but only at the end of the current process load.
I try to unscheduled process chain : the job of the current process is killed and the process stop
I try to execute the programm rspc_process_finsh : same result.
Actually, I aim at waiting of the current process completion and stop the chain.
Thanks and regards,
Bobby

Hi all,
Thanks for answer.
If I resume the situation :
- Click on Unschedule process chain stop the current process. We have to change the status of the process in Yellow to Red.
- Go to sm37 to kill the job change the statut in red.
So there is no way to stop the running of a process chain only after the good or bad end of the last runnning process ?
Example :
My chain is running. The process which is running is a DTP loading process. There are 50 packages to load. I decide to click on Unschedule process chain when the package 18 is running.
If I do that, the loading of package 19 will not start right ?
So is there a way to wait that the 50 packages are loaded before that the system stop the chain ?
Thanks in advance,
Bobby.

Process Chain Ended with Errors - cause unknown

I have had several instances of process chains stopping for no apparent reason. The stops occur between 2 master data infopackage loads. The last step is green and the next is grey. The PSA table has been updated successfully for the last step. All IDocs are in green status in both systems. The monitor for the last successful step does say "Ended with Errors" although no errors are evident. The process chain starts back up via Repeat at the next (grey) step and continues successfully. There were no system problems or connection interruptions that occurred during the time the process chains failed. There were no changes in the remote user profile.
This exact problem has occurred a half dozen times since our application of ECC Support Packs several months ago and had not occurred before. The infopackages are different each time. Two different process chains have had this problem. I have re-activated and re-scheduled the process chains without solving the problem.
Thanks for any ideas on why this may be occurring or what I can do to prevent it.
Patty Moffatt

Hi Des,
Here's my BW release info:
SAP_ABA        640       0019 SAPKA64019     Cross-Application
SAP_BASIS      640       0019 SAPKB64019     SAP Basis
PI_BASIS       2005_1_6400009 SAPKIPYJ69     Basis Plug-In
ST-PI          2005_1_6400008 SAPKITLQH8     SAP Solution Tools Plug-
SAP_BW         350       0019 SAPKW35019   SAP_BW
ECC SPs 13-21 were applied before the BW problem started:
SAP_BASIS      640       0021 SAPKB64021
SAP_ABA        640       0021 SAPKA64021
PI_BASIS       2005_1_6400012 SAPKIPYJ6C
ST-PI          2005_1_6400008 SAPKITLQH8
SAP_BW         350       0021 SAPKW35021
PI             2004_1_5000016 SAPKIPZI6G
The process chain step and the monitor load both are green. The Details tab shows all the processing is green, but the Process Chain itself is red with "Errors Occurred. There have been no runtime dumps.
Patty

Process chain doesn't even with errors in bacrground processes

Hi experts,
I need your help again.
My client is using a process chain to automate the consolidation process in SEM-BCS. This is done using variants of programs UCBATCH01 and UCBATCH11.
The problem now is that the process chain doesnu2019t stop even though the steps have errors. The validation tasks are the best example.
Do you know a way to make the process chain stop?
Best regards
João Arvanas,

Hi Marsy,
I'm having the same issue as discussed in this thread and since I am still very new in BCS I have some additional question
1. Is the status table for task that you are referring to = /1SEM/UCS001USV1 ?
2. I read in another source that status table only store the latest run log ? not historical ? is that true or would you might be aware of a historical table ?
3. The table split cons area task run status into each of the cons unit, so if one of them has error, basically the task error
Thank You,

Process chain stopping in middle

Similar Messages

Maybe you are looking for