Posts

WIS 00504 You do not have the rights to access data returned by this universe

Error: WIS 00504  Message: You do not have the rights to access data returned by this universe. See your business objects administrator  Non si dispone dei diritti di accesso ai dati restituiti da questo universo. (WIS 00504) Environment SA BI 4.0 SP 8 In order to solve this issue on refreshing a WebI  report check  user permissions at user/folder/object level Check   the access rights for all the universes and universe connections in this case for assigning rights to the user for Universe and connections, Login to CMC and go to Universes.  Select the universe which you are using,right click and select user security,check if your user has rights on that universe if not then use Add principals and assign rights to the user you are using.  Then go to Connections in CMC and select the connection which your universe is using and follow the same thing as done for Universes.  Moreover  on the rights tab and for the user/group  on the Access Level drop down, ch

WIS 00005 Invalid Prompt definition

Invalid Prompt definition. See your Business Objects administrator. (Error: WIS 00005) Environment BI  4 SP 8 Cause The syntax in the prompt is not valid, or the prompt makes reference to an object that no longer exists in the universe. Action The universe designer can verify that the prompt syntax is correct, and check that all objects referenced in the prompt exist.

WIJ 20002 Error - WebI Rich Client XI R3.1

 WebI Rich Client XI R3.1 Environment XI R3.1 SP 4 When we try to open an imported reports  in Webi Rich Client, BO raises the following Error Code WIJ 20002 Error Workaround: Log in  Web Intelligence Rich Client. Go to Tools > Options Go to Locale (tab) and set "Interface locale" and "Formatting locale" to English (United States) > OK. Open a report in Web Intelligence Rich Client it runs ! See Also XI R 3.1 errors solutions

Information design Tool - How to refresh the structure of a universe

Image
In order to refresh the structure of the universe in the Information design Tool Open the Data Foundation  Click on detect button and select Refresh Structure as you can see in the following image See also Publishing Universe with IDT

Err QTJ 00511 - Circular references : check your @select and @where calls (QTJ 00511)

Circular references : check your @select and @where calls (QTJ 00511) Environment BI 4 SP 8 Cause An @Select or @Where call in the script refers to itself. This is not allowed. Action Check the declaration of the @Select and @Where calls and correct or modify the script. See also: Sap BI 4.0 errors list

Error UNV0023 - Parse Failed: Invalid Definition (UNV0023)

Parse Failed: Invalid Definition (UNV0023) Environment BI 4 SP 8 We are working with Universe Design Tool  on universes  that require the same tables so after inserting the tables in one universe and creating classes/objects/meta data, we copied the same classes and objects into other universes as the tables are  the same. But when we  parse the objects in the table after copying we got  following error: Parse Failed:Invalid definition (UNV0023).  The only way to solve the problem was to go into each object and copy, delete and then past the table object name. So the advise  that in similar cases is:  first  you have  to add the tables  and then you can add relative objects and  not viceversa! 2nd case We got the error  in another case For an object with the following select: CASE WHEN @Select(PromptList\....) IN @Prompt('Code:','N','PromptList\ CatCode' ,multi,constrained) THEN @Select(PromptLis\generic) ELSE (SELECT LTRIM(MA

BI 4 Error - Index is not ready. Please try again later (PSS 01004)

Index is not ready. Please try again later (PSS 01004) Environment BI 4.0 SP 8 When we tried to find a document name in the search field the error above has been raised. Resolution Go to CMC->Application-> Right Click 'Platform Search Application'->Properties Go down in the page and select the option "Rebuild Index" , save and close. Let the index rebuild  and Restart the SIA Check also the SAP NOTE http://service.sap.com/sap/support/notes/1634413 See also BI 4.0 errors list