Launch of new NW2004s-BI Frontend from transaction rrmx

Question

Hi,
my customer has upggraded to NW2004s. <b>We are on Support Package 7. The NW2004s-BI Frontend is FEP701.</b>
When I enter <b>transaction <rrmx> the "old" BW 3.5 Bex Frontend launches.</b>
Is there a <b>way to have <rrmx> call the new NW2004s-BI frontend?</b>
I have been toggling the "Launch Legacy Version from RRMX" flag on and off in the new NW2004s BI Frontend but nothing but the 3.5 Analyzer lauches?
Can you help with that issue?
Thanks
Christian

Answer 1

Hi Christian! in this reply you could find your solution.
<u><b> but attached file is available only by OSS!
If you think this helps, don't forget give me points!</b></u>
<b>see note 933768</b>
<i>Symptom
Error in Business Explorer Components like Analyzer, Report Designer, Web Application Designer, Query Designer, Open/Save Dialog, Value Help Dialog
Other terms
Business Explorer, Frontend, BW, BI 7.0, BI, Hotfix, advance correction, Analyzer, Report Designer, Web Application Designer, Query Designer, Open/Save Dialog, Value Help Dialog, Selector, characteristic restriction, filter, filter value, variables
Reason and Prerequisites
You have installed NetWeaver 2004s BI Add-On Frontend Patch 700, and you need a hotfix (advance correction) for certain problems that are caused by the BI Add-On (frontend).
This note will be updated as solutions for newly detected problems are available. Hence you should check the actuality of this note, if you have already applied hotfixes for the patch level of your BI Add-On.
Solution
Attached to this note you will find frontend components (DLL files) that correct certain errors. You will find a list and descriptions of solved problems in the following. It is recommended to replace all respective DLLs in the setup directory of the BI Add-On with the attached DLLs. However, you can also selectively replace individual DLLs that are required for the solution of problems that you encountered. In the following it is described which DLLs are required to solve specific problems.
The Open/Save dialog and the Value Help dialog (selector) are components that are used by several SAP Business Explorer applications. Hence, if you encounter errors in one of those applications, please also check the dialogs sections below for a solution.
SAP Business Explorer Web Application Designer
SAP Business Explorer Analyzer and Variables Screen
New property to adjust the size of the Drop-down item added.
Known errors occuring, while entering the values in variable screen pop-up, have been corrected
SAP Business Explorer Query Designer
Corrected critical error at saving of reusable elements (especially evident with calculated key figures using variables). We strongly recommend to apply this hotfix.
If a presentation hierarchy is selected for a drilldown, it is not possible any more to restrict the characteristic to a hierarchy node from another hierarchy.
Refresh problem solved with repeated query execution in web browser.
Dimension preview is enabled again and allows scrolling.
Problems with query variable order presentation and editing are solved.
Structure member selections using calculated key figures display further calcuated key figure properties.
Error with characteristic value variables replaced by queries corrected.
Errors with structure member descriptions corrected.
There were too many characteristics offered as aggregation reference for formulas. Now only characteristics of the corresponding InfoProvider are listed.
Paste of multiple characteristics when restricting structure member selections is working again.
Error when creating structure member hierarchies with formulas is solved.
Copy and paste of a structure member without changing the focus was not possible. This is now enabled.
Variables could not be entered in the editors for conditions and exceptions. This is possible now. Also variables for key date can now be entered.
Error when adding attributes by drag and drop corrected.
Sorted display of query elements corrected.
Paste of a second reusable structure enabled again.
It is not allowed to restrict a structure member to a characteristic value if the other structure already contains a restriction of this characteristic. This check is now implemented.
Sometimes values for Zero Suppression were not correctly saved. This is corrected now (updated 04 May 2006)
Restricted and Calculated key figure folders did not display if the user started Query Designer more than once from Analyzer. (updated 04 May 2006)
It was not possible to delete a Characteristic from filter if a reusable filter contained this characteristic (updated 04 May 2006)
Paste of InfoObjects and reusable Elements was errorneously possible to Exception and Condition area. Is frobidden now. (updated 04 May 2006)
Text variables with repalcement path are now always not inputable (updated 04 May 2006)
Variables were not displayed correctly if the user started Query Designer more than once from Analyzer. (updated 04 May 2006)
There could be a runtime error (occasionally) in Anaylzer after user selected "Exit and use query" in Query Designer due to a still processed error check. (updated 04 May 2006)
There is now a check if a presentation hierarchy exists on server. If not, the user is informed by a warning (updated 04 May 2006)
New warning informs user about non existing presentation hierarchies (updated 15 May 2006)
Formula variables with replacement path "by attribute" offer now only numerical attributes. (updated 15 May 2006)
Empty formulas now cause an error message, not just a warning message, because queries with empty formulas are not executable. (updated 15 May 2006)
For compounded characteristics in InfoProvider tree the compound info was not displayed in all cases, this is corrected now (updated 15 May 2006)
Variables replaced by query result or by a replacement table can be just used in Filter. The user is informed by an error message if such variables are used anywhere else (updated 15 May 2006).
Queries with cell were sometimes saved with wrong coordinates for cells. Such queries are not executable. This is corrected now. Wrong queries are auto corrected, if they are loaded and saved with this corrected version (updated 15 May 2006).
Problem with "hanging" explorer during execution of a query in web solved (updated 15 May 2006).
Variable order setting is now also possible for new queries (updated 15 May 2006)
Empty structures cause now an error message, not just a warning message, because queries with empty structures are not executable. (updated 15 May 2006)
There were some cases where Text variables were not stred correctly and as a consequence not replaced. All known issues are now corrected. (updated 15 May 2006)
With this hotfix the Note 948374 should be also implemented in the backend system, it prevents some save prolems.
Small usability improvements in Varible-, Exception- and Condition editor (updated 23 May 2006)
Multiple keyfigures are not allowed in Filter, but it was possible to do this with copy and paste of multiselected keyfigures (updated 23 May 2006)
There were cases where users could create different components with same technical names, this is checked now (updated 23 May 2006)
Variables replaced by query result or by a replacement table reported an incorrect message if they were defined with "Input allowed = true", this is corrected (updated 23 May 2006)
SAP Exit variables were errorneously not allowed to be used in non content systems, this is corrected (updated 23 May 2006)
In variable editor for Formula variables replaced by attribute value there were not offered all possible numeric variables offered. This caused a runtime error if especially variables created with Query Designer 3.x were edited. This is corrected now (updated 23 May 2006)
Due to a program error any saved formula might have been saved incorrectly, if it is using any variables (formula or text variables). This is a critical error which might lead to not understandable error messages during query execution or missing text variable replacement for formulas. The error is corrected the was that any corrupt query can be loaded and after a save it is repaired. We strongly recommend to use this hotfix for all installations!
SAP Business Explorer Report Designer
Introduced Versioning and added Version checks. More recent versions of Report Designer are able to design reports with new features. If such a report is edited with an older version of Report Designer some design features might be lost in the report or loading the report might not be possible.
Images from Mime repository can be added to the report.
Sequence of Report Sections is saved and loaded in the right order.
Query Text Elements for more than one Dataprovider are correctly dsiplayed in the Report Item. Property Dialog shows the name of the Dataprovider of the selected Text Element.
Conditional Formatting for Hierarchy nodes enabled.
Open Dialog/Save Dialog
Value Help Dialog (Characteristics Restriction/Filter Selection)
Search can be performed by entering the search criteria in value help dialog and then by pressing the <Enter> keyboard button</i>
<b>or see note 929632</b>
<i>Symptom
There are errors in Business Explorer components such as Analyzer, Report Designer, Web Application Designer, BEx Query Designer, Open/Save dialog, input help dialog.
Other terms
Business Explorer, Front end, BW, BI 7.0, BI, Hotfix, advance correction, Analyzer, Report Designer, Web Application Designer, BEx Query Designer, Open/Save dialog, input help dialog, selector, characteristic restriction, filter value, variables
Reason and Prerequisites
You have installed NetWeaver 2004s BI Add-On Front End Patch 02 and you require advance corrections for certain problems that are caused by the BI Add-On (front end).
Solution
You can find front end components (DLLs) that correct the errors described below attached to this note. We recommend that you replace all attached DLLs in the setup directory of the BI Add-On. However, you can also replace only those DLLs required to correct a problem that occurred in your system. The following sections describe which DLLs correct which problems.
The Open/Save dialog and the input help dialog are components that are used by several SAP Business Explorer applications. Therefore, check whether the correction of a problem that occurred in one of the applications is described there.
SAP Business Explorer Web Application Designer
           Up to now, there are no advance corrections.
SAP Business Explorer Analyzer and variable screen
           To correct the problems in the Analyzer and the variable screenthat are described here, the files BExApi.dll, BExAddin.dll, BExAnalyzer.xla, BExVariableScreen.dll, BExLocalFormulaParser.dll, BExQueryDesigner.dll, BExSelectorAPI.dll and BExSelectorDialog.dll are required.
In the variable screen, the formats for the calendar year and calendar month characteristics have not been transferred correctly to the server. As a result, error messages occurred during the check.
When deleting an item in design mode, the system did not remove the displayed data of the item in analysis mode, rather it still displayed this data.
The display of the checkbox item and the radio button item has been corrected.
Errors occurred when you saved variants on the variable screen. All known errors have been corrected.
The security certificate for the Analyzer has expired and the advance corrections contain a new security certificate.
SAP Business Explorer Query Designer
            To correct the problems in the Query Designer that are described here, the files BExQueryDesigner.dll, BExSelectorAPI.dll and BExSelectorDialog.dll are required.
Executing in the Web no longer opens different browser windows, rather the system always uses the same one.
In certain cases, queries that contain attributes were not saved correctly and as a result, they could not be loaded. This problem has been corrected in all known the cases.
In certain cases, queries that contain cells were not saved correctly and as a result, they could not be loaded. This problem has been corrected in all known the cases.
If queries are saved incorrectly (for example with incorrect attributes or incorrect cells), the system issues messages for all cells that are incorrect and it refers to a possible solution. Currently, all text messages are in English and they will be translated in Support Package Stack 8.
You can now insert and resort attributes at any position. You can do this using drag and drop or cut and paste.
Formula variables with replacement path now also permit the setting of the dimension.
If you edited attributes for an object and you then saved your changes immediately without exiting the field, the system did not save the change in this field. This problem has now been corrected.
Texts of attributes are now displayed correctly after you load the query again (up to now, the system displayed only technical names).
Constant selection was not displayed correctly in the context menu of a selection. Now, the system displays a checkmark to indicate that constant selection is activated.
Attributes of display hierarchies are now displayed and saved correctly.
The system no longer displays operators twice in technical names in formulas. Up to now, [+] + was displayed.
The system no longer displays UIDs as technical names for structure items and cells in formulas.
Structures with hierarchical structure items: In certain cases, structure elements disappeared during the hierarchical setup. However, these were saved and they caused an endless loop on the server. This problem has been corrected. You can use the BEx Query Designer to open queries that were saved with these "vanished" structure elements and the "vanished" structure elements are displayed again.
Errors and terminations on the server now cause a message in the message window of the BEx Query Designer telling you to close and to restart the BEx Query Designer.
For variables with replacement path, the system displayed too many characteristics (some technical characteristics) for the replacement characteristic. This problem has been corrected.
Further consistency checks have been implemented and the corresponding messages are displayed in the message list. The system now checks not only queries but it also checks restricted and calculated key figures, variables, and cells.
If you change a reusable element, the system does not save it automatically. An information message is displayed telling the user that saving the element may affect other queries. You can save the element normally using a save function in the context menu. If the element is used in the query, it is always saved with the query.
When you exit the BEx Query Designer, the system checks which reusable elements have not yet been saved. The system displays a list containing all unsaved elements and it asks the user whether these elements should be saved.
There is a new menu function "Save All" that saves all changed reusable elements.
When you select text variables, the system now displays the correct variable type "Text variable" in the selection.
You were able to use cut and paste for conditions and exceptions, but this always caused a runtime error. The functions have been deactivated for the moment to avoid program terminations.
You can now define variables with a replacement from an attribute.
You can now also display only posted values in the value help (read mode D).
For text and formula variables with replacement path, you can no longer create on the technical characteristic 1TEXT or 1FORMULA. Any existing variables (that were created with earlier versions) are reported as incorrect and you should delete them.
For restricted or calculated key figures or for variables, if you made changes and you saved these changes online and confirmed with OK, the system sometimes issued message "Not saved - object is not changeable". This problem has been corrected.
When creating new reusable elements, the system only checked if the user was authorized to create new elements for this InfoProvider, but it did not check whether the user was authorized to create elements with the given technical name. This problem has been corrected.
You can now move and copy cells using cut and paste and copy and paste. Unfortunately, you still cannot use drag and drop.
In formulas, multiline headers of structure elements are correctly displayed in single lines and no longer in several lines.
In certain cases, hierarchy node variables were saved without a corresponding hierarchy assignment and you could not use them in the report that was being executed.
After each time you saved data, the context menu of the currently selected object was incorrect. This problem has been corrected.
You could not delete filter values directly in the BEx Query Designer, rather you had to do this in the filter dialog.
You could not change characteristics of attributes.
The system now issues a corresponding success message after each successful saving process.
SAP Business ExplorerReport Designer
           Up to now, there are no advance corrections.
Open dialog/Save dialog
           Up to now, there are no advance corrections.
Input help dialog (characteristic value restriction/filter selection)
           To correct the problems in the value help dialog that are described here, the files BExQueryDesigner.dll, BExSelectorAPI.dll and BExSelectorDialog.dll are required.
You can now edit variables in the value help for all variable types and not only for characteristic value variables.
You can now create variables in the value help for all variable types and not only for characteristic value variables.
When changing an offset, negative offsets are displayed as -5 and no longer as 5-. Variable offsets are displayed directly in the right area of the value help.
Variables as the to-value of intervals no longer cause terminations.
In the value range editor, the value you entered manually was not transferred if you directly chose the transfer arrow.
In the value help for reference characteristics, the system did not display the variables for basic characteristics and therefore there were usually fewer variables than in the BEx Query Designer.
When you select the hierarchy, the system now correctly displays the date and version variables and no longer hierarchy variables as was incorrectly the case before.
When you call the value help from the variable entry screen, the system sometimes displayed all master data values (read mode "M") even though it should only display posted values (read mode "D"). This problem has been corrected.</i>