Migration of SAP BW BEx Analyzer 3.x to BEx Analyzer 7.x

1. Migration of BEx Analyzer 3.x to BEx Analyzer 7.x
Skip to end of metadata
 Page restrictions apply
 Attachments:3
 Added by Deepak Kumar Shah,lastedited by Oliver Stelzer on Apr 27, 2015 (view change)
Go to startof metadata
Important:
 SAP BW 3.5 Frontend is not available as standard in SAP GUI 730/740. See note 1410878.
 SAP BW 3.5 BEx tools (= Business Explorer 3.x) cannot be used w ith BW 7.4 (and higher) - see note 1932461.
 Please review our frontend w ikipage: BEx Front-End Installation and Update.
1 - Workbook Migration
 It is not possible to open an already migrated w orkbook in BEx Analyzer 3.x again. This w orkbook is only available in BEx
Analyzer 7.0 after the migration.
 The easiest w ay to determine w hether a w orkbook has been migrated or not, is that you cannot open the migrated
w orkbooks w ith BEx Analyzer 3.x anymore.
 If you w ant to assign the authorization to upgrade from 3x w orkbooks to 7x w orkbooks (saving under the same name) to
selected users only, You can use authorization as per note 1226980 in order to restrict the upgrade behavior.
1.1 - Workbook Migration of locally saved 3x Workbooks
 Opening a locally saved 3x w orkbook that contains VBA code in BEx Analyzer 7x can leads to a non w orking BEx Toolbar.
 Please go through note 1459484 to solve this issue.
2 - Variants
As the variants of BEx Analyzer 7x are stored in a different storage than BEx Analyzer 3.x, the variants are no longer visible
in the BEx Analyzer 7.x.
Migration:
 You can find more information in note 1003481 about the procedures to upgrade the BEx Analyzer 3x variants to the BEx
Analyzer 7.0 concept:
 The report RSR_VARIANT_XPRA converts/transfers old 3x variants into tables RSRVARIANTDIR, RSRVARIANT,
RSRVARIANTTXT w hich is the pre-requisite for the report RSR_MIGRATE_VARIANTS.
 The report RSR_MIGRATE_VARIANTS migrates into 7x tables RSRPARAMETRIZA,RSRPARAMETRIZAT.
 Migrated variants are global/cross user variants. The technical name of the 7x variant is unique.
 The name of 3x variants is not unique.
 While migration the report checks if the name of current processed 3x variant already exists in RSRPARAMETRIZA. In this
case the technical name of new 7x variant is concatenated: "<variant name>_<technical name of query>". The maximum
length of 7x variant name is 30 digits (the rest is cutted).
 Umlauts are replaced w ith an underscore.
Please note:

2.  3x variants are allw ays 'query variants'.
 7x variants are available for queries, w orkbooks, w ebtemplates, planning functions and planning sequence - they are stored
in tables RSRPARAMETRIZA,RSRPARAMETRIZAT.
 If you copy a query A to copy B, then w ith query B you have no access to query variants of query A.
 If you migrate a 3x query A and save it as a new query B then you need to create new variants for query B.
 If a migrated w orkbook has mutliple data providers then you w ill not see the migrated variants by default. Please read note
1726090 to get detailed information about that including the solution to get access to the migrated variants.
3 - Missing functionalities in BEx Analyzer 7x
 Please also review KBA note 1754753 Limitation of BEx Analyzer 7x.
3.1 - Delete Query Result
 In BEx Analyzer 3.x w e had the option to delete Query Result w hen saving a w orkbook. This allow ed us to display no result
data at the time of saving the w orkbook.
 Delete Query Results option is not available for BEx Analyzer 7x.
3.2 - Different BW Systems
It w ill not be possible to use queries from 2 different BW systems in a single w orkbook. See Note: 1547454
3.3 - Exception Control
 In BEx Analyzer 3x w orkbook it w as possible to activate/diactivate the exception via context menu.
 In migrated 7x w orkbook the context menu option for exception is not available.
 Exceptions can only be activated/deactivated by using the BEx Item Exception w hich is offered in the design features of BEx
Analyzer 7x. You can insert the functionality into the w orkbook by adding this BEx Item to your w orkbook. A list of
exceptions w ill appear for the Data Provider the BEx Item is assigned to. The item offers the functionality required for
activating/deactivating Exceptions of one Data Provider.
4 - Options for BEx Analyzer 3x Workbook Migration
 It is very important to follow the below recommendations before the migration is started.
 When BEx Analyzer 3x w orkbooks are migrated in BexAnalyzer 7x some behavior/settings are not migrated correspondingly
due to architectural differences.
4.1 - Allow Refresh of Single Query
 The w orkbook property to allow refresh of single queries is alw ays unchecked w hile migration.
 Please review w ikipage Single Data Provider Refresh to find detail information about the new /corresponding 7x functionality.
4.2 Text & Navigation Elements
 For each text element row in the BexAnalyzer 3x w orkbook an ow n text element is created in the migrated BEx Analyzer 7x
w orkbook.

3.  For each navigation row in the BexAnalyzer 3x w orkbook an ow n navigation pane is created in the migrated BEx Analyzer
7x w orkbook.
Before starting the migration, create the follow ing registry keys as String Values under key
“HKEY_CURRENT_USERSoftw areSAPBExAnalyzer”:
1. ApplySingleQueryRefreshOnUpgrade: <True | False>
If the value is “True” single query refresh w ill be activated w hereas refresh on open w ill be deactivated. As a prerequisite
single query refresh has to be activated on the server according to note 1287179.
2. MergeTextElementsOnUpgrade: <True | False>
3. MergeNavPanesOnUpgrade: <True | False>
 If the value is True all text elements/navigation elements belonging to one data provider w ill be merged into one
BexAnalyzer 7x item. The range of this item is defined by the range of the first element in the BexAnalyzer 3x w orkbook. If
not all elements in the BexAnalyzer 3x w orkbook are in one coherent range this may cause overlapping items as side
effect.The above is also described in the note 1418556.
 For using value True please use at least Frontendpatch FEP400 for SAP GUI 730 as described in note 1826134.
 Follow ing picture show s the registry entries w ith TRUE value:
4.3 Formatting / Styles
 BEx Analyzer 7x uses different formatting options for its items if compared to BEx Analyzer 3x. If you used standard BEx
Analyzer 3x formats they w ill be kept in the migrated BEx Analyzer 7x w orkbook. But, if you used custom formats, the BEx
Analyzer 7x ignores them during the migration and applies the standard BEx Analyzer 7x formats. Therefore if you w ant to
avoid the loss of the custom formats w hile the migration, you need to implement the note 1366182 before the
migration. Before starting the migration, create the follow ing registry keys as String Value under key
“HKEY_CURRENT_USERSoftw areSAPBExAnalyzer”:
1. ApplyGridFormatOnUpgrade: <True | False>
If the value is “True” new formatting w ill be applied to the grid items in the migrated w orkbook. If the value is “False” the
formatting of the grid items w ill not be changed after the migration.
2. ApplyNavPaneFormatOnUpgrade: <True | False>
If the value is “True” new formatting w ill be applied to the navigation block items in the migrated w orkbook. If the value is
“False” the formatting of the navigation block items w ill not be changed after the migration.
 Follow ing picture show s the registry entries w ith FALSE value:

4.  In BEx Analyzer 3x the hierarchies use the style "SAPBEXstdItem" but the BEx Analyzer 7x uses different styles to indicate
the hierarchy level( "SAPBEXHLevel0" for Level 0, "SAPBEXHLevel1" for level 1, "SAPBEXHLevel2" for level 2 and
"SAPBEXHLevel3" for rest). This can leads to unw anted GridItem formatting. In this case please change the properties for
the new "SAPBEXHLevel?" styles and save the definition as theme in the BEx Analyzer Workbook Settings on TAB
Themes. Apply these steps after w orkbook migration. Use the new created Theme in the Workbook:
 save current styles to a theme:
1. set sapbex* styles via Excel
2. go to w orkbook settings, tab themes
3. press button "New " to create a new theme
4. press button "Apply"
5. press button "Save"
6. cancel w orkbook settings
 use styles from an existing theme:
1. load w orkbook
2. go to w orkbook settings, tab themes
3. select theme
4. set radio button "Reapply Theme Before Rendering"
5. press button "OK"
4.4 Sheet Protection
 When migrating w orkbook from 3.x to 7.x, the w orkbook and its sheets should not be in the protected mode.
 During migration some shapes are created BExAnalyzer 7.x and thus BExAnalyzer should have access to the w orkbook and
its sheet.
4.5. Variables in Workbook
 In BEx Analyzer 3x w orkbooks for each data provider the property "Save and reuse variable values" can be set to true or
false.
 While migration the corresponding BEx Analyzer 7x w orkbook property "Process Variables" is alw ays set to true.
 As reference please review note 1730320.
5 - Adapting the published APIs for the BexAnalyzer 3.x to the BexAnalyzer 7x
 Not supported APIs in BexAnalyzer 7x
1. Public Sub SAPBEXpauseOn()
2. Public Sub SAPBEXpauseOff()
3. Public Function SAPBEXcopyFilterValue(fromCell As Range, Optional atCell As Range) As Integer
4. Public Function SAPBEXfireCommand(fCode As String, Optional atCell As Range) As Integer
5. Public Function SAPBEXcheckContext(fCode As String, Optional atCell As Range) As Integer
6. Public Function SAPBEXshow TextElements(Optional selectGroup As String, Optional atCell As Range) As Integer

5. 7. Public Function SAPBEXjumpInitial(queryID As String, jumpType As String, jumpTarget As String) As String
8. Public Function SAPBEXjump(jumpType As String, jumpTarget As String, Optional atCell As Range) As Integer
9. Public Function SAPBEXgetResultRange_ResultArea() As Range
10. Public Function SAPBEXgetResultRange(ByRef resultArea As Range, dataOnly As Boolean, Optional atCell As Range) As
Boolean -> Not a published 3.x API
11. Public Function SAPBEXembedQuery(genUID As String, Optional atActive-Cell As Boolean) As String
12. Public Sub SAPBEXunattended()
13. Public Sub SAPBEXtoolbar()
 Supported APIs in BexAnalyzer 7x
1. Function SAPBEXgetErrorText() As String
2. Function SAPBEXrefresh(allQueries As Boolean, Optional atCell As Range) As Integer
 In the BexAnalyzer 7x, ALL the items in the w orkbook can be refreshed, but refreshing a query individually is not supported
3. Function SAPBEXsetDrillState(new State As Integer, Optional atCell As Range) As Integer
4. Function SAPBEXgetDrillState_CurrentState() As Integer
5. Function SAPBEXgetDrillState(currentState As Integer, Optional atCell As Range) As Integer
6. Function SAPBEXsetFilterValue(intValue As String, Optional hierValue As String, Optional atCell As Range) As Integer
7. Function SAPBEXgetFilterValue_IntValue() As String: SAPBEXgetFilter-Value_IntValue =
g_SAPBEXgetFilterValue_IntValue: End Function
8. Function SAPBEXgetFilterValue_HierValue() As String: SAPBEXgetFilter-Value_HierValue =
g_SAPBEXgetFilterValue_HierValue: End Function
9. Public Function SAPBEXgetFilterValue(intValue As String, hierValue As String, Optional atCell As Range) As Integer
10. Public Function SAPBEXgetResultRangeByID(ByVal queryID As String, Optional ByVal charName As String) As Range
11. Public Function SAPBEXsaveWorkbook(Optional w bName As String) As Integer
 Not possible to save programmatically w ithout the Open Save Dialog coming up hence determine if it is in precalc mode
12. Public Function SAPBEXreadWorkbook(w bID As String) As String
13. Public Function SAPBEXgetWorkbookID(w bName As String) As String
14. Public Sub OpenWorkbook(iWorkbookID As String)
 Please consider these changes:

In 3x Analyzer In 7x Analyzer
In w orkbook setting->Dataprovider, find the Dataprovider
name (eg DP_1)
6 - Avoid Performance Issues
Because of architectural differences betw een BEx Analyzer 3x and BEx Analyzer 7x, the below described notes need to be
implemented, in order to avoid possible performance issues after the upgrade:
 Make sure your upgraded w orkbook does not contain unused shapes and names. Check the Number of Shapes and Names
in the Workbook.

6. To check if there are unused shapes and names w ithin your migrated BexAnalyzer 7x w orkbook, open the VBA Editor
(Alt+F11) and paste the below macro in the VB project of your w orkbook:
If one of the numbers you receive is more then 1000, run the w orkbook in Repair Mode and check if the number of shapes
and names reduced afterw ards.

 To run the w orkbook in repair mode follow the steps:
1. Before opening the w orkbook, go to the Global Settings dialog, set the flag “Repair Workbook During Execution” (See image
below ).
2.
3. Close the dialog, open the w orkbook and refresh it.
4. Once the w orkbook is refreshed, save it back to the BW server.
The most common reason for a large number of shapes in one w orkbook can be the usage of hierarchies w ithin the result.
In these cases, do the follow ing test:
 In the Grid Properties dialog(s), check the option set for the property "Display Hierarchy Icons".
 If the option set is "Display Icons", change it and set the option to "+/-".
 Now , check if this change made the performance better.

7. Problem:
 A critical program error occurred. The program has to close. Please refer to the trace for further information.
 Application has generated an exception that could not be handled.Process id=0x7b8(1976), Thread id =0x3d4Click
OK to terminate application.
click CANCEL to debug the application.
 marshaling .NET type System.Byte[] to RFCTYPE_BYTE error
 I am trying to execute a query through BEx Analyzer and i am getting the error:”System Exception thrown while
marshaling RFCTYPE_CHAR to .NET type“, error occured while communicating with the BI server. As a result, the
system has been disconnected from the BI Server.I was able to execute the same query through Query Designer
and also see the output. Output had around 2000 pages. And i executed it through RSRT also, without any
problems.
 A critical error has occured while opening workbook. The issue is that the same workbook is opening in some one
machine but not in others.The following Dialog box is poping out when tried to open workbook:”A critical program
error has occured.The Program will now terminate.Please refer to trace for further information.”
However,i did the full updation of service pack3 of MS Excel 2003 on my machine and the same version as on that
particular machine(on which workbook is opening). The problem is still there.Please provide some solution.
 I have designed a query in BI 7.0 which on checking shows Query is correct, but when I am trying to see the report
in Analyzer “critical program error…..follow trace…..system had to close” thuis error comes.I don’t understand
where I have made a mistake.How can I find out the error. where to see error trace o r log.please help.It’s urgent.
 We have recently upgraged the SAP GUI to 710 Patch 6
Excel on Excel 2003 SP2
BW is on SAP_BW at 700 and Support pack level 15
When we open workbooks for upgrade some workbooks upgrade without any errors and some workbooks give me an
error “A CRITICAL PROGRAM ERROR OCCURRED. The program has to close.Please refer to the for further
information”.
We dont have any information of ST01 trace and ST22 short dumps
We are trying to open the workbooks with authorization profiles SAP_ALL
 Hello. I saw several posts with a “Critical program error” message in new BEx Analyzer 7.0 when try to run query ir
workbook, but have not seen any answers to them.
 When I look into the trace file BexAnalyzerTrace_<session_id>.txt (attached) in my temp directory, I see following:
System.IO.FileNotFoundException: File or assembly name BExCompression, or one of its dependencies,
was not found.
File name: “BExCompression” at
com.sap.bi.et.analyzer.api.BExApplication.DeSerializeApplication(String iString)
at com.sap.bi.et.analyzer.addin.BExExcelApplication..ctor(String iWorkbookName).
But I cannot find any further reference to BExCompression.
Solution:
I was facing with this problem too.
After lots of messaging with OSS .I take a note number. 1179647
Apply this note. And than I suggest you installing latest SAP Gui 7.10 with BI addon 8.x and Office 2003
with KB907417. If you don’t want to apply note. Don’t upgrade gui up to, bi710sp04p_401-
10004472.exe So you will always face this problem.