Once you kicked of a critical load you may want to monitor the results closely. If you get the feeling that things are just not moving the following actions proved to be fruitful for me in the past.
Target system (BI)
- Check the load monitor in transaction RSA1 (or directly in RSMON) if there has been some movement and refresh regularly to see if your load got stuck.
- Check the jobs in the BI system via SM37 and the processes via SM50 maybe there are not enough processes and the job is not yet active. Make sure you have the split between dialog and background processes right as most automated loads would run in the background.
Source System
- Check the jobs (SM37) in the target system with the name ‘BIREQU*’ and the user you use for the RFC connection. Filter for everything, which is not finished. The job name is in the form of ‘BI’ + request ID from BI system. Check the job log for status and errors if you find the job. This way you should also find jobs which failed (status canceled). Check the logs for the canceled jobs as they may contain clues why the job failed.
- Also check SM50 in the source system if you have enough resources (background processes). SM66 would give you an idea of the memory consumption of the process (in case your extractor enhancement demands too much memory).
Communication between systems
- Check the iDocs in BD87 / WE05 in the source and target system. Check for the inbound queue in the source and the outbound queue in the target system. Look for iDocs with the name of RS* (RSINFO, RSRQST, RSSEND). You may have to process them manually if things got stuck.
- Check the tRFC packages in SM58 in the source system if they got stuck. Sometimes you have to process them manually (select the LUW and use F6). Check the error messages as system communication is sometimes broken for a reason (RFC connection not working, RFC user locked out, etc).
Please leave your comments if I have missed anything.
Leave a comment