Question:
Hi Everybody,
WE use BW 3.0b. Database Oracle 8.1.7. Patches applied for BASIS,ABAP and BW. This is new installation.
When I try to get data from IDES for Material data. The following is the error message after scheduling the data.
------------------------------------------------------------------------
Request still running
Diagnosis
No errors could be found. The current process has probably not finished yet.
System response
The ALE inbox of the SAP BW is identical to the ALE outbox of the source system
and/or
the maximum wait time for this request has not yet run out
and/or
the batch job in the source system has not yet ended.
Current status
No Idocs arrived from the source system.
I checked SM59, connection is ok. We have done the settings through SALE. Kindly help me in detial to solve this problem..
TIA.
-Rajan.
Answer:
Use R/3 tcode: RSA3 and check for your extractor, if there are records in source system.
Answer:
Also check SM21/ST22 in the source system.....
I have seen issues where the source system (R/3) dumped out w/o properly reporting that failure to the BW system.
Answer:
We had a similar problem a month ago, and the problems was that the IDOC's didn't come through from R/3 to BW
So you might check transaction BD87 in R/3. If you see IDOC's with status 64 of the type RSRQST, you have to process them manually
Answer:
Hi Suji/Bobcot,
RSA3 is working fine. it shows 60 records in the selection. system log i do not see any errors related to this. any other ideas please.
I checked BD87 also. there are no idocs with status 64.
TIA
-Rajan
Answer:
I'm out....
Answer:
From the monitor, just check the Job status in the source system..
Did your job run or is it just sitting as released?
Anton
Answer:
Did anybody suggest checking the RFC connection, partner profiles etc. etc., or am I being dense as usual?
_________________
Keep smiling
Answer:
Please check the data in the Data Targets if records have been loaded even though request is still running.
Answer:
Rajan,
It happens because system ran out of processes, There is an OSS note on this, Apply that.
EC
Answer:
Hi SR,
Can you elaborate on partner profiles and how to check them. Also, RFC connection where to check.
Thanks
- Gary
Answer:
Hi SR,
Can you elaborate on partner profiles and how to check them. Also, RFC connection where to check.
Thanks
- Gary
Partner profiles: we20 & we21. There should be an entry for the partner (R/3 in case of BW and vice versa) and the logsysnames should be correct.
RFC: sm59. You should try a remote login to one system from the other. If setup correctly, you should NOT get a dialog (login) screen. If you do, then the password for the ALEREMOTE is buggered (changed by somebody else).
There is one more thing which gets screwed up every time you have a system refresh w/o post processing. And this too affects the RFC transfers of IDOCs. The partner should be in the active status in table EDPP1
_________________
Keep smiling
Answer:
Hi Rajan
Can you please throw me what are the resolutions for this?
Thanks
Diane
Answer:
Hi Rajan,
for which extractor data is not coming..?
check the data is there intially in source R / 3 tables
have u did the V1 update before.
in source R/ 3 if extractor picking records ( RSA3 ) check ALE connection is ok or not.
Welcome for any inputs.
Thanks and Regards.
Martin Leo