I migrated few reports from R2 to R3.
When I refresh some Deski reports that was migrated from R2, it gives “Set Prompts Failed” error after supplying all the prompts.
Does any one encountered this issue while migration, please let me know.
Hi Chris,
I hope your links would help, though some of them I had referred to it already.
First of all, I am facing Connection or SQL sentence error : (DA0005)
Exception : Data source name not found and no default driver specifies state when I try to open the report in Deski. No issues for other users. How can I fix this first?
The thing is, if I open the report in R2Deski, I can do it. The R3 Deski reports are also pointing to the same Datasource as R3 Reports. How do i fix this? Then I will able to take each of the reports and change the universe name manually (import, reselect universe, export) and see if that works.
Thanks Chris for the Links.
My situation is different here.
I have both R2 and R3 deski / deski reports in my PC, both points to same datasource. R2 reports works fine but not R3 reports and I believe it has nothing to do with DSN’s. Some where else…probably with permissions etc.,
Thanks…
not a problem … i had the same error after we used the migration tool … it turned out we changed the universe name internally, but the tool didn’t pick that up … i’d focus on getting it running correctly on R3 deski, everything should flow from there … i’d also do an integrity check on the universe, especially if you ran it thru the import tool.
The issue is resolved and the issue is with the filter condition syntax for a object
@Select(Period\Period Name) IN @Prompt('Select Period(s)','A','Period\Period Name',MULTI,CONSTRAINED)
There should not be any single quotes for Multi and Constrained in R3 universe. After I remove those, export the universe, open the Deski report, parse the SQL, export it back to Infoview and then the Migrated Deski report in R3 works fine.
The question now is, does SAP require every filter condition object to modify in R3 universe. Do they release a product like this where a modification is required like this to make the migrated Deski report from R2 to R3 to work fine. Any ideas / comments?
Thanks…
I think the migration wizard treats @PROMPTS just like regular text fields … i.e., they don’t migrate them … agree, sad and frustrating, but the only option is to change them all manually.
(BOB member since 2007-06-25)
(BOB member since 2002-06-18)