cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Entry 70 still missing

Former Member
0 Likes
2,737

Hello Experts,

I have browsed these forums on the matter at hand, but was unable to find a solution to my problem, hence my post.

We are retreiving data from our XI system. This is done via Web Service (Push) adapter (data is being pushed to BI from XI).

While launching a test packages into BI, we have come across a strange situation: the data is being saved to PSA (and is physically present there) almost instantly but the process, when checked in the monitor, is still "Yellow" and a message

Data Package 1 : arrived in BW ; Processing : Processing not yet finished, entry 70 still missing

can be found in the Transfer (IDocs and TRFC) part of the Details tab of the process monitor.

I've read on SDN that this is because the process still continues due to large amount of data and I can let it roll and it should eventually complete (turn "Green') or I could manually set the status to "Green" myself - however - in our case, we are talking about 130 records taking... 18 days 20 hours to finish (sic!) - at least that's what the header of the process monitor is stating, and I don't see why it would lie

While I could understand that large volumes take some time to finish loading properly to BI, I am disoriented as to why it would take almost 3 weeks to load 130 (one hunder and thirty) records.

Could anyone point me in the direction of the probable cause of this situation? I would be deeply thankful.

Best regards,

Aleksander

Accepted Solutions (1)

Accepted Solutions (1)

MartinMaruskin
Active Contributor
0 Likes

HI Aleksander,

have you checked ABAP dumps on BW side? Might be some problem on DB level like deadlock detected...

BR

m./

Answers (5)

Answers (5)

former_member182196
Contributor
0 Likes

Hi,

Kindly Check the RFC connection,

1. By using this Tx SM58 check tRFC log in ECC and BW side it lof is there then push it manually.

2. By using this Tx BD87 check the Idoc status in ECC and BW side if is there any idoc sucked then      process manually. 

3. Check the partner profile setting in WE20 at ECC and bi side.

Thanks & Regards,

SM

Former Member
0 Likes

In case of loading a flat file:

This is due to the file name being too long for SAP to handle. Try shortening the string (folders plus filename) and put the file on another folder close to the root folder.

Former Member
0 Likes

Hi,

Same error message when loading from a file. In our case, this a 7 years process which always get success. In tCode st22 (ABAP Runtime Error), I see the error was related with an unstable index. Once the index has been fixed, the processing return to normal.

Regards,

Andre

Former Member
0 Likes

Whenever we deal with Million of records loading to cube, Always drop the index and recreate it after load completes.

Former Member
0 Likes

Hi,

Check if any trfc's are stuck in Source system.

Refer to http://scn.sap.com/docs/DOC-26591 for solution.

Regards,

Harish.

Former Member
0 Likes

This error usually happens when try to load a cube with the Index ON. You will need to drop the indexes in the F-table before you load or Usually this error comes up when ther multiple requests populating to an single data target.One requests restricts the entry of another into the data target.Wait for the present request to be updated and then re-run the next request.

To fix that error, try these steps:

- In the monitor (TA RSMO) select the "red" job in the left-hand frame.

- Go to the menu and select "Edit >>> Init. Update >>> Setting for further update".

- A dialog box will appear. Select the option "Packet should be processed in the background".

- Go to the menu again and select "Edit >>> Update/Reversal >>> Read everything in manually".

- A dialog box will appear with the message "Incorrect data packets are now updated again". Click on the green check-mark. This will submit a batch job in SM37 for each failed data packet.

- In SM37 the job name(s) will start with BI_BOOK.

- You can also monitor the status by selecting the "Details" tab and clicking the "Refresh Details" button.

OR

This could be problem of TRFC struck. TRFC's are struck due to some RFC connection problem between the source system and target system. To come up with this, go to the SM58 Screen, over there U may find some tRFC's having status " Transaction Recorded " (or) with some " Error " statement. Select that specific tRFC's 1 at a time and goto Edit in the Main Menu, there U will find the option Execute LUW( F6 ), just select that option, after that try and refresh the screen thru refresh button, U will not find that tRFC in the list. It will be succesfully posted to the Target system.

Hope this answers your issue...

-Vikram

Former Member
0 Likes

Hello all,

Thanks for your suggestions, however:

@Martin - no logs or short dumps are available either on BW or XI side (since - as I have said - the process does not terminate, merely takes unsually long to properly finish)

@Vikram - as I have said, the problem is realted to s PSA, no InfoCube. TRansaction SM58 (tRFC maintenance) contains no information and gives no help

I have managed to bypass this issue by creating a process chain and including a special step in it - "Close Request of Infopackage (RDA/Push)" - at the beginning. I have defined infopoackage from the discussed datasource in it and run it some time after the push has been done from the XI system - as I have said, physically the data is being present in the PSA in a matter of seconds / minutes, so it's only an issue with the technical processing of the package(s).

The problem with my solution is that I can never be 100% sure that the data is in BW, but by providing a long enough time window between pushing the data into BW and running the aforementioned chain, I can get sure enough to sue it.

Former Member
0 Likes

Hi ,

I am also facing the same issue.Could you please let me know the procedure for solving the issue if you would have already resolved it

Regards

Ram.

Former Member
0 Likes

Hello Ramakanth,

Please check my post above to see how I dealt with this issue (there's a slight typo at the end, it should read "I can get sure enough to use it").

Edited by: Aleksander Dyl on Feb 22, 2010 2:39 PM

Former Member
0 Likes

Hello Experts,

While loading data from a Flatfile to the DS through IP, I am getting the error “ Entry 70 still missing” and the load is getting stuck every time.

There are around 1 Million records that I need to load from the flatfile. I tried with lesses no. of records ( a few thousand ), but again the same problem.

I have tried the TA RSMO solution mentioned above but the option – “Update/Reversal >>> Read everything in manually” is disabled for me.

Any other suggestions to solve this problem? Please help.

Former Member
0 Likes

I believe you mean- whenever BI request data from ECC or XI it establish a connection first and then data transfer get started. In your case you were not getting the job completed confirmation for your source even after the job had completed in XI. We can check the issue with Status job.