DSO Activation Failure due to one of the background process termination

Document Version / Dtails : Ver 1.0 / 14-Feb-2011

Record Of Release

Version No. 1.0

Created/Modified By Sanjay / Saurabh

Reviewed By Kush Kashyap

Release Date 14/02/2011

Modifications Done Initial

Project ID:

E6806

Project Name:

FSS BW Operation

Friday, August 02, 2013 L&T Infotech Proprietary Page 1 of 12

Scope of Document: This document helps us to understand the steps to be followed in case of DSO Activation Failure due to one of the background process termination. Sample Error Message: Background process BCTL_3E3ZFGRQ2S8GHZGIE8HJYUV27 terminated due to missing confirmation The issue behind this problem is, during parallel activation, the child jobs acknowledge the parent job about status. If the child job takes long time to read data from active data table, then it times out and fails. Step1: Log in the SAP. Enter below details: Connection Type: Custom Application server Description: GRP Application server: 155.111.150.189 (we can use from 187 to 194) System ID: GRP Client: 400

Step 2: Enter user name and password.

Friday, August 02, 2013 L&T Infotech Proprietary Page 2 of 12

Step 3: Run the transaction SA38.

Step4: Run the program /SSA/BWT.

Step 5: After clicking Execute, below screen will appear. Check the Process Chain Analysis radio button. Click on Execute button again.

Friday, August 02, 2013 L&T Infotech Proprietary Page 3 of 12

Step6: Next, click on Process Chains. Below screen will appear. Enter the time and date for process chain runs. Click on execute. After execution all process chains for the given time and date selection range will appear.

Step 7: In the below screenshot, in the process chain GAP_GWFDAP01_GAPC0012 one of the steps has failed, as it is visible in the steps indicator, which has turned to red. Click on Log id of the process chain to view in detail.

Friday, August 02, 2013 L&T Infotech Proprietary Page 4 of 12

Step 8: Local Chain has turned to red, indicating that a step has failed inside it.

Step 9: Right Click on the failed local process chain, and then Click on Process Monitor.

Friday, August 02, 2013 L&T Infotech Proprietary Page 5 of 12

Step 10: Process Monitor is showing DSO Activation Failure.

Friday, August 02, 2013 L&T Infotech Proprietary Page 6 of 12

Step 11: Right Click on Failed DSO step, and click on Displaying Messages. It will open the logs for the process chain step and display the exact cause of DSO failure.

Step 12: Click on the Background Tab and check the messages being displayed. In this example the failure is due to one of the background process getting terminated due to missing confirmation.

Friday, August 02, 2013 L&T Infotech Proprietary Page 7 of 12

Step 13: On double clicking on the message, we are able to see the detailed description of the failure.

Step 14: There is also one more method to check the error during the DSO activation. Right click on Failed DSO step and then click on the Process Monitor option.

Friday, August 02, 2013 L&T Infotech Proprietary Page 8 of 12

Step 15 : It is clear from the error analysis that the DSO activation was terminated because of a background process getting terminated. This is probably related to the system perfromance and it is safe to repeat the DSO Activation process again.

Friday, August 02, 2013 L&T Infotech Proprietary Page 9 of 12

To do so, Right click on the failed DSO step and then click on the Repeat option.

Step 16: Next a debug loop popup will come. Only use this function to debug a process run. Specify how long (in seconds) you want the delay to be between one event being triggered and the next process starting. You can capture the process in the debugger by using transaction SM37 (Job Overview) or SM50 (Process Overview).

Step 17: The below screenshot shows that the repeat job is in progress.

Friday, August 02, 2013 L&T Infotech Proprietary Page 10 of 12

Step 18: You can confirm that whether repeat job has actually started by clicking on the Administer Data Target.

Friday, August 02, 2013 L&T Infotech Proprietary Page 11 of 12

Step 19: Here under the request tab it is clearly showing the request status of DSO is Green in color, means its activated.

Step 20: If the DSO activation fails again on the repeat attempts then escalate the issue to the Performance Team through an incident.

Friday, August 02, 2013 L&T Infotech Proprietary Page 12 of 12