Data loading delays in R/3 making the chain status red

Document Version / Dtails : Ver 2.0 / 15-Apr.-2011

Record Of Release

Version No. 1.0 2.0

Created/Modified By Gayathri.R Gayathri.R

Reviewed By Pawan Chaturvedi Pawan Chaturvedi

Release Date 14/04/2011 15/04/2011

Modifications Done Initial Detailed Conclusion

Project ID:

E6806

Project Name:

FSS BW Operation

Scope of Document: This document helps us to understand that the red status in the chains does not necessarily mean only failure; instead there may be other reasons as well. In this document, we discuss upon such an instance caused by the delay in loading the data from the source system to BW. Sample Error Message: Idocs missing: No selection information arrived from the source system. The issue behind this problem is that the information or data has not arrived from the source system to the BW yet. 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.

PM-03-04 Ver 2.0/15-April-2011

Page 2 of 14

Step 3: Run the transaction SA38.

Step4: Run the program /SSA/BWT.

PM-03-04 Ver 2.0/15-April-2011

Page 3 of 14

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

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.

PM-03-04 Ver 2.0/15-April-2011

Page 4 of 14

Step 7: In the below screenshot, in the process chain MSA_0CO_OM_OPA_6 the chain seems to be completely failed as it is visible in the status and steps indicator, which has turned to red. Click on Log id of the process chain to view in detail.

Step 8: From the below screenshot, it seems that the info package that loads data from the A5P source system has failed. But let us not conclude on this; rather proceed further to investigate the reasons.

PM-03-04 Ver 2.0/15-April-2011

Page 5 of 14

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

PM-03-04 Ver 2.0/15-April-2011

Page 6 of 14

Step 10: Click on the Process Tab and check the messages being displayed. The message clearly depicts that the no information has reached the BW system from the source system. Now, the next step would be to check what happened in the source system as a result of which data has not arrived from the source system. So Click on Process monitor tab.

PM-03-04 Ver 2.0/15-April-2011

Page 7 of 14

Step 11: Also from the messages displayed, it seems that there might be a short dump occurred in the source system. The steps to be carried out to view the short dump if any in the source system are briefed clearly in the messages displayed.

PM-03-04 Ver 2.0/15-April-2011

Page 8 of 14

Step 12: To check the short dump in the source system, go to the Environment tab on the top of the monitor Short dump-In the source system.

PM-03-04 Ver 2.0/15-April-2011

Page 9 of 14

Step 13: Log on to the source system using the credentials.

Step 14: The ABAP run time error screen shows up. Enter the appropriate date and time selections of the chain as shown below. Then click on start button to view the short dump.

PM-03-04 Ver 2.0/15-April-2011

Page 10 of 14

Step 15: If any short dump exists, it would show the related information. In such case, you can proceed to resolve the short dump failure by following the steps described. But in the other case, where there seems to be no short dump, then the next step would be to check its job status in the source system. Here, when we click on the start button of the run time error screen, it displays a message saying that None of the selected short dump exists which means there is no short dump failure.

PM-03-04 Ver 2.0/15-April-2011

Page 11 of 14

Step 16: As pointed above, the next step would be to check its job status in the source system. For that, go to the Environment tab on the top of the monitor Job overview - In the source system.

Step 17: Log on to the source system using the credentials.

PM-03-04 Ver 2.0/15-April-2011

Page 12 of 14

Step 18: Enter the appropriate date and time details to see the job status. Then click on Execute.

PM-03-04 Ver 2.0/15-April-2011

Page 13 of 14

Step 19: Now the job status can be identified by checking out the cross (X) mark. Here the cross (X) mark under the active status explains that the job is still active and has not failed yet.

Thus this explains the fact that even if the status of the chain seems to be red, it need not be failure all the time.The status went red because the info package was taking a long time to load the data than expected. Normally when the process in the BW side takes more than 3 hours to complete, the status of that process automatically turns red. Similarly in this case, even though the job in the R/3 side is still active, the status in the BW side turned red as the data loading exceeded the time frame of 3 hours. So later when the active job in the R/3 is finished, we would find the same chain status returning to yellow and then finally to green after successful completion.

PM-03-04 Ver 2.0/15-April-2011

Page 14 of 14