This action might not be possible to undo. Are you sure you want to continue?
Document Version / Détails : 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
FSS BW Operation
instead there may be other reasons as well. Enter below details: Connection Type: Custom Application server Description: GRP Application server: 155.0/15-April-2011 Page 2 of 14 .Scope of Document: This document helps us to understand that the red status in the chains does not necessarily mean only failure.189 (we can use from 187 to 194) System ID: GRP Client: 400 Step 2: Enter user name and password.111. The issue behind this problem is that the information or data has not arrived from the source system to the BW yet. PM-03-04 Ver 2.150. Sample Error Message: Idocs missing: No selection information arrived from the source system. Step1: Log in the SAP. we discuss upon such an instance caused by the delay in loading the data from the source system to BW. In this document.
Step 3: Run the transaction SA38.0/15-April-2011 Page 3 of 14 . PM-03-04 Ver 2. Step4: Run the program /SSA/BWT.
After execution all process chains for the given time and date selection range will appear. Below screen will appear. Click on execute.0/15-April-2011 Page 4 of 14 . Step6: Next. Click on Execute button again. below screen will appear. Check the Process Chain Analysis radio button. click on Process Chains. Enter the time and date for process chain runs. PM-03-04 Ver 2.Step 5: After clicking Execute.
which has turned to red. rather proceed further to investigate the reasons. Step 8: From the below screenshot. But let us not conclude on this.Step 7: In the below screenshot. PM-03-04 Ver 2. it seems that the info package that loads data from the A5P source system has failed. 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.0/15-April-2011 Page 5 of 14 . Click on Log –id of the process chain to view in detail.
and click on Displaying Messages.0/15-April-2011 Page 6 of 14 . PM-03-04 Ver 2.Step 9: Right Click on Failed Load data step. It will open the logs for the process chain step and display the exact cause of the failure.
The message clearly depicts that the no information has reached the BW system from the source system.0/15-April-2011 Page 7 of 14 . PM-03-04 Ver 2. 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. Now. So Click on Process monitor tab.Step 10: Click on the Process Tab and check the messages being displayed.
0/15-April-2011 Page 8 of 14 . The steps to be carried out to view the short dump if any in the source system are briefed clearly in the messages displayed. it seems that there might be a short dump occurred in the source system. PM-03-04 Ver 2.Step 11: Also from the messages displayed.
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 12: To check the short dump in the source system.
Then click on start button to view the short dump.0/15-April-2011 Page 10 of 14 .Step 13: Log on to the source system using the credentials. Step 14: The ABAP run time error screen shows up. PM-03-04 Ver 2. Enter the appropriate date and time selections of the chain as shown below.
0/15-April-2011 Page 11 of 14 . then the next step would be to check its job status in the source system. you can proceed to resolve the short dump failure by following the steps described. Here.Step 15: If any short dump exists. when we click on the start button of the run time error screen. But in the other case. In such case. it would show the related information. 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. where there seems to be no short dump.
In the source system.0/15-April-2011 Page 12 of 14 . PM-03-04 Ver 2. go to the Environment tab on the top of the monitor – Job overview . For that. Step 17: Log on to the source system using the credentials. the next step would be to check its job status in the source system.Step 16: As pointed above.
Step 18: Enter the appropriate date and time details to see the job status. PM-03-04 Ver 2.0/15-April-2011 Page 13 of 14 . Then click on Execute.
even though the job in the R/3 side is still active. Here the cross (X) mark under the active status explains that the job is still active and has not failed yet.Step 19: Now the job status can be identified by checking out the cross (X) mark. Similarly in this case. So later when the active job in the R/3 is finished. Normally when the process in the BW side takes more than 3 hours to complete. Thus this explains the fact that even if the status of the chain seems to be red. PM-03-04 Ver 2. the status in the BW side turned red as the data loading exceeded the time frame of 3 hours. the status of that process automatically turns red. we would find the same chain status returning to yellow and then finally to green after successful completion.The status went red because the info package was taking a long time to load the data than expected. it need not be failure all the time.0/15-April-2011 Page 14 of 14 .