Hi All,
Clicking on a delta infopackage is giving MESSAGE_TYPE_X short dump, at program SAPLRSS1, and module name RSM1_CHECK_FOR_DELTAUPD.
Understand that this has got to do with the inconsistent delta information between the source system and BW system.
Here's the scenario:
In BW system:
Table RSSDLINIT contain an entry for this problematic infosource 0HR_PT_2, with request number REQU_4848.
In Source System:
Transaction RSA7 does not list down any relevant delta queue for this infosource.
Table ROOSPRMSC contains an entry for this datasource 0HR_PT_2, but for a different source system, and with a different request number.
What should I do now to fix this?
Thanks all.
Regards,
Pat
Hi ,
1. Once you log out from BI system
and login again
try to schedule the Same info package
if it dose not work follow this
2.we would suggest to create new InfoPackage
Choose the delta update and cickoff the infopackage
Pls update what is the status after doing this steps
also Cut paste the dump you got if above dosnt work.
Thanks
Hari
Edited by: Hari Gonuguntla on Aug 4, 2008 10:30 AM
Hi Hari,
Thanks for your reply. The short dump occurs when I try to open the infopackage, not when trying to schedule it. This mean I cannot even open the infopackage. Anyway, I have tried your suggestions and they didn't work.
Thanks.:)
Regards,
Pat
Hi,
Go to SE38 and run this program RSSM_OLTP_INIT_DELTA_UPDATE giving the required details.
we have to enter the value for the LOGSYS and DATASOURCE and then execute it.
It wont give any message. Then try to open your infopackage and do an fresh init and a delta as per your requirements.
It happens when some setup tables are run at the R/3 systems due to which the init of an delta gets deleted in the background.
Regards
Merlin.
Hi, thanks for the reply. What should I entered in the ALWAYS field? I tried Y, N, and X, but after running the program, I still hit the short dump when trying to open the infopackage.
Thanks.
Regards,
Pat
Hi,
The Always field is optional so we can leave it as blank.
It is mandatory to give LOGSYS and Datasource name.
Then execute it and it wont gave any indication or message after execution.
After that go to your respective infopackage and try to open it.
Regards
Merlin.
Hi Merlin,
Your reply for Short Dump issue was really helpful to me. It resolved my issue as well.
Thanks a Lot
Thanks Merlin. Solved my issue too.
Senthil
Thanks Marlin
Hi,
I have got the same error and in R/3 there are more no. of entries on R/3 side table ROOSPRMSC as compared to table RSSDLINIT (BW side).
Can you please suggest what the next steps we should try...
Do we have to delete from RSA7 or something else...
Thanking you,
Tarun Brijwani.
This error basically happens when RSSDLINIT table of BW is out of sync with ROOSPRMSC and ROOSPRMSF tables in R/3.
Merlin's method works when information is available in RSSDLINIT regarding delta init, which then copied to the above mentioned tables in R/3 using RSSM_OLTP_INIT_DELTA_UPDATE, but the reverse is not possible. i.e If the delta init information is available in R/3 but not the corresponding BW, then you have to reinit.
Opening of the infopackage is not possible in BW at all in the second case, until R/3 also forgets that there was such a delta......(Hope this gives you a hint regarding what to do..)
Edited by: SDX BI on Oct 13, 2008 7:31 PM
Hi,
I have got the same error and in R/3 there are more no. of entries on R/3 side table ROOSPRMSC as compared to table RSSDLINIT (BW side).
Can you please suggest what the next steps we should try...
Do we have to delete from RSA7 or something else...
Thanking you,
Tarun Brijwani.