Steps to run a strucked Process in a Process Chain

Scenario(s):- 

1)      If a proces chain is stuck at a particular step and we want to restart it.  
2)      Data loading is successful, but the next step of the chain is not executed.. 
Reason :- The event that will register in the back end data base is not set properly or may go to hold state, so as a result will have to change the parameter manually.

 Solution:-

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>>>rspcprocesslog 
Enter the below details, 
Variant >>> variante 
Instance >>> instance 
Batch date >>> start date 
This will give a single entry in the table rspcprocesslog. 
Step 3:  Execute the function module  RSPC_PROCESS_FINISH  
 Enter the below details, 
Rspcprocesslog >>>instance >>> I_INSTANCE. 
Rspcprocesslog >>>variante>>> I_VARIANT 
Rspcprocesslog >>>logid>>>I_LOGID 
Rspcprocesslog >>> type >>>I_TYPE 
Enter 'G' 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.

The program that I was talking about to progress those ‘failed’ processes in the Process Chain that are not repeatable is RSPC_PROCESS_FINISH.

In SE38, when you type in the above program name and execute, you should see the below screen.

As an example, you know that the ZNOTIFICATN_ATTR InfoPackage failed yesterday, due to an ALEREMOTE lock. Right Clicking on this failed InfoPackage and then choose ‘Displaying Messages’ . Then go to the ‘Chain’ tab to the ‘Variant’ & ‘Instance’ of the process that failed.

After getting the ‘Variant’ & ‘Instance’, we need to go to the table RSPCPROCESSLOG and enter the ‘Variant’ & ‘Instance’ identified above in the corresponding fields of this table and click execute.

From this table, we would be able to get data for the fields LOGID & TYPE that are needed for the program RSPC_PROCESS_FINISH.

As you can see the selected Instance [which is usually the Request Number generated by the InfoPackage in the Data Target] has a STATE of ‘R’ [Ended with errors]

We now enter values for the fields LOGID, TYPE, VARIANT, INSTANCE in the program RSPC_PROCESS_FINISH and select the value of ‘G’ [Successfully Completed] for the field STATE as shown below.

Clicking on execute will send a message to the system that the entered ‘Instance’ of the ‘Variant’ [i.e. the InfoPackage] had completed successfully. The failed InfoPackage Process that ‘red’ would now turn to ‘green’ and the subsequent processes will be automatically kicked off.

Note: We must make sure that the manual process that is needed to correct the error [in this case running the InfoPackage for ZNOTIFICATN_ATTR manually] is successfully complete before we run the program RSPC_PROCESS_FINISH to progress to the subsequent steps in the Process Chain.

On a separate note, the processes like ODS Activation, Attribute Change Run, Index Deletion can be ‘Repeated’ when they fail due to some reason in a Process Chain. But as of now, we do not have the option to ‘Repeat’ an InfoPackage that has failed. I believe that we have to turn ‘ON’ a setting in RSPC to make the InfoPackage’s ‘Repeatable.

On entering into RSPC, click on any of the Process Chains and then select the ‘Process Type’ button.

 

In the following screen, choose Settings à Maintain Process Types

Choose the Process Type ‘Loading’ and click on ‘Details’.

As you can see in the below screen, the ‘Repeatable’ option has not been selected for the LOAD process.

This is the reason why a ‘Repeat’ option doesn’t show up when an InfoPackage fails in a Process Chain.

I have also shown below the settings for the DSO Activation & Attribute Change Run process where the ‘Repeatable’ option has been selected.

I believe making the InfoPackage process ‘Repeatable’ would help to save us some time and effort in case of a failure at the InfoPackage step as we just need to ‘Repeat’ the failed InfoPackage rather than running it manually and also that the subsequent steps are automatically trigerred.