Skip to Content

In many situations while monitoring Process Chains, we find that the status of the chain is red indicating errors while data loading. We check and find that in the Process Chain, one of the steps has failed and the status is appearing in red colour. But in actual everything has loaded, in order, still the chain is not moving forward because of the error.

 Not to worry as there is a workaround to manually set it to a success/green status. But it requires us to understand how the chain works.

 Whenever we create a chain we create a sequence of variants which are associated with events. It’s the events, which when triggered, start a particular instance of variant and the step is completed.

 Each event is scheduled with relation to the previous step, so as soon as the previous step gets completed; it triggers the ensuing step, in the process, completing the chain.

 Therefore, if a particular step has failed inside the chain, or stuck even if the data has loaded correctly, and because of its stuck status it will not trigger the next event, which we will have to do manually.

 So the logical action would be to manually turn the status of this step, in the chain, to green, which will automatically trigger the next event then.

But, if only we knew what the variants were, the instance, the start date and time of the particular step of the chain which failed, we could have directly gone to the function module and would have executed using the details, to manually turn the chain status to green and trigger the following events. But alas! It’s not humanly possible to remember it everytime given the long BW technical names.

In order to obtain this information we go to the failed step of the process chain, right click it and select “Display Messages” and open the tab which reads “Chain”. Here we note down the values in the field “Variant” and “Instance”.

 Next we need to go to the table which stores information on process log entries for process chains – “RSPCPROCESSLOG”. We use transaction SE16 which takes us to Data Browser: Initial screen asking for the table name whose entries we want to check.

 Input RSPCPROCESSLOG and press F7 which displays the table content input fields. Enter the noted values for the particular instance and the variant run on a particular day and press F8 to execute. .

 This returns the entry for the failed step giving details which are needed for the subsequent use in Function module. We again take a note of the values returned under the fields; logid, type, variant, instance.

Lastly we go to SE38 transaction which opens the ABAP Editor: Initial Screen. Here enter RSPC_PROCESS_FINISH in the program field and press F8 which will execute this function module.

 Here enter the values jotted earlier namely; logid, type, variant, instance, Batch date, batch time. Here important thing to note is the field “STATE”. To turn it to green select option “G” which stands for successfully completed.

Execute the function module by pressing F8 and in the process chain that process step status will be turned to green, triggering the next step in the chain.

In a nutshell:-

A)    Go to the step where the process chain is stuck

  •          Right click on context menu to display messages
  •          Select tab chain
  •          Copy variant, instance & start date

B)  Enter Transaction Code SE16

  •          Enter table name RSPCPROCESSLOG
  •          Enter values for:
  •          Variant
  •          Instance
  •          Batch date.
  •          It will return a single row from table RSPCPROCESSLOG.           

C)  Execute the function module RSPC_PROCESS_FINISH & Enter the below details

  •          INSTANCE.
  •          VARIANT
  •          LOGID
  •          TYPE
  •          Enter ‘G’ for the field STATE and press execute (F8).
To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply