EVDRE - Excel 2003 vs Excel 2007 performance

We run BPC 7.0 sp6 with a user population that has a mix of Office 2003 & Office 2007 on their client machines. We have several standard and non-standard evdre reports. Reports that are run in 2003 take 30 - 60 seconds to expand or refresh, the same reports run in 2007 take 3 - 10 minutes to expand or refresh.
Also, reports that are run consecutively only with different criteria in 2003 run fine, in 2007 each consecutive run adds 2 - 5 minutes per.
Does anyone know why?
Does anyone know how to fix office 2007 performance issues?
Any help would be appreciated

Hi Steven,
Have you installed System Driver Data Connectivity components on your application server (which is a prerequisite for running Excel 2007)? If not, then get it installed. This you can get from the Microsoft web site. You need to install all of the latest Microsoft Windows hotfixes prior to installing the Administration client. For information about which hotfixes to install, see http://www.microsoft.com/downloads/details.aspx?FamilyID=7554F536-8C28-4598-9B72-EF94E038C891&DisplayLang=en.
Hope this helps.
Regards,
Poonam

Similar Messages

Slow query performance in excel 2007 vs excel 2003

Hi,
Some of our clients recently did an upgrade towards BI 7.0 and also upgraded towards excel 2007.
They experience lots of performance problems when using the Bex analyser in excel 2007.
Refreshing queries, using 'simple' workbooks works till 10 times slower than before using excel 2003.
Has anyons experienced the same?
Any tips/tricks to solve that problem?
With regards,
Tom.

Hello all,
1) Please set the following parameters to X in transaction
    RS_FRONTEND_INIT and check the issue.
Parameters to be set are
ANA_USE_SIDGRIDDELTA
ANA_USE_SIDGRIDMASS
ANA_SINGLEDPREFRESH
ANA_CACHE_WORKBOOK
ANA_USE_OPTIMIZE_STG
ANA_USE_TABLE
2) Also refer to below KBA link which would help to resolve the issue.
   1570478 BW Report in Excel 2007 or Excel 2010 takes much more time than
3) In the workbook properties please set the flag
     - Use Compression When Saving Workbook
4) If you are working with big hierarchies please try to improve
performance with following setting directly in AnalysisGrid:
   - Properties of Analysis Grid - Dispay Hierarchy Icons
   - switch to "+/-"
Regards,
Arvind

Best practice for Smartview when upgrading from Excel 2003 to Excel 2007?

Does anyone know the best pratice for Smartview when upgrading from Excel 2003 to Excel 2007?
Current users have Microsoft Excel 2003 with Smartview 9.3.1.2.1.003.
Computers are being upgraded to Microsoft Excel 2007.
What is the best pratice for Smartview in this situation?
1. Do nothing with Smartview and just install Excel 2007.
2. Install Excel 2007 and then uninstall and reinstall Smartview
3. Uninstall Smartview, Install Excel 2007, and then install Smartview
4. Somthing else??
Thanks!

We went with option 1 and it worked out fine. Be aware that SV processes noticeably slower in Excel 2007 than 2003. Many users were/are unhappy with the switch. We haven't tested SV v11 yet, so I'm not sure if it has improved performance with Excel 2007 or not (hopefully it does).

Poor performance of BEx Analyzer in excel 2007

Hi all,
after upgrading my office to version 2007, BEx Analyzer runs very slowly. The query is executed fast at the server but the excel visualisation of data in the workbook takes a lot of time. There is no problem on other computers with office 2003.
I have gone through all the notes but couldn't find anu solution.
Do I have to disable something in excel?
The performance doesn't have anything to do with my system spec (IBM T61 with 3 gig of RAM).
Thanks for any help.
Jan

We are getting similar issues excel 2007 takes ages to visualise the results of the bw query compared to excel 2003.
It is particularly an issue on very large excel files 10MB+.
I dont think many business have gone for this combination so far, the response I have from SAP is that it is a microsoft issue.
No resolution so far other than to put users back to office 2003.
Nigel

Report created in SAP/ BEx 7.1 with Excel 2007 can't be opened by 2000/2003

Hi
We're currently in the process of migrating to Office 2007 from both 2000 & 2003 and we're finding in testing that staff who use BEx Analyser with SAP 7.1 to create queries and send embedded in reports to others can not be opened by recipients who are still on Excel 2000 or 2003. Staff who already using Excel 2007 can open the reports however not on earlier versions. We are ensuring the excel file is saved as the file type .xls so there's no reason we can see why it shouldn't open successfully.
Has anyone else experienced this?
Many thanks

Have you tried Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 file formats?
http://office.microsoft.com/en-us/support/microsoft-office-compatibility-pack-for-word-excel-and-powerpoint-2007-file-formats-HA010168676.aspx

Problem opening BEx Analyzer Workbook (saved in Excel 2007) in Excel 2003!!

Dear all:
I know there are threads about this issue and numerous support tickets have been provided, but we still can't get any Excel 2007 Query to be opened by Excel 2003.
I have tried to save Excel 2007 BEx Analyzer Query into 97-2003 XLS format. But when we reopened (by both Excel 03 and 07), it prompted the warning messages and broke down the query workbook into several sheets with scrambled data. What am I missing here...? According to the support ticket, it seemed pretty straightforward just by saving the format to 2003 XLS, but in reality it just doesn't work as "advertised"
Thank you...!!!
Brian

I have the solution for this.
It works to my environment.
Follow the steps :
1. you must open the xlsx workbook from Bex Analyzer.
2. Save As workbook locally to your PC for excel 97-2003
(Not "save as" from bex Toolbar but from excel)
3. Now save that workbook with Save As->Workbook from Bex Toolbar into your BI database.
Now go to detail properties of your workbook and there you can see the format xls for your workbook.
Good Luck

Can't open Excel 2007 workbooks on version 2003

Hi,
I saved a workbook using excel 2007 and now when someone using version 2003 try to open it, this error message appears: "Workbook format .xlsx is supported only from office excel 2007 version".
Does anyone know how to fix this without having to install office 2007?
Thanks in advance.
Best regards,
Rogério

Hi again,
I tried your advice and I get a new error message saying "The workbook is corrupt and cannot be loaded"..
Any other sugestions???? :s
Thanks!
BR,
Rogério

Start OutlookSoft 4.2 with Excel 2003 when Excel 2007 is also installed.

Does anyone know how to get OutlookSoft 4.2 to use Excel 2003 as the default u2013 when both Excel 2003 and 2007 are installed? Iu2019ll take any suggestions. Thanks.

Thanks, Joost and Sorin, for your responses! We will be considering both of them.
My name is Christine, and I work with Ellie (who originated the question).
Sorin, where do you insert the launch command described in your response?
Neither Ellie nor I are computer programmers. We have learned on the job as we go. So it's not obvious to us what to do with your command/path. I have changed the "Open With" property for Web Excel to use the exe file for Excel 2003, but the result is that Excel 2007 opens in compatibility mode, and not as Excel 2003.

BPC 7 : Excel 2003 and Excel 2007 Conflict

Hi Experts,
I have created a template in BPC 7 MS on my computer which has Excel 2003 version.
But when I try that template on another computer which has Excel 2007. The format (in the format Range) did'nt seem to work or it has diff effect on Excel 2007.
Is there really a conflict between them?? and cannot have different Microsoft Office version?? Or is there An Add-on that we have to Install so that Excel 2003 and Excel 2007 can be used at the same Time??
Thanks,
Bennie Jay

Sorin:
Situation
I also have the same issue with Excel formatting in Excel 2007, and I found a work-around specifically to my issue.
At the format section's CRITERIA, I have one entry: HEADING="New Budget" in the Column direction, apply certain color and number format to the cells of that column. However, I used Excel function CONCATENATE("HEADING=",EVDES("FINANCE",CATEGORY)) to come out with HEADING="New Budget", rather than just typing the string value.
With the above exercise, in Excel 2003 the format would apply no problem, but in Excel 2007, the entire formatting went wild and broke. After I dropped CONCATENATE() and just typed in HEADING="New Budget", the formatting applied OK in 2007.
Data
We are currently on BPC 5.1 SP5
The original report was built in Excel 2003
Question
Is there a setting in Excel that would allow me or bypass the restriction to use Excel functions to come out with CRITERIA definition?

Excel 2007 and Excel 2003 format

Hi all,
we have some problems with Excel file format on BPC 7.5NW SP06:
1- We save input schedules or reports woth Excel 2007 file format. Then when we try to open these report they are corrupted (we click on "Open" and nothing happens). We can download the report from UJFS. The xltx file is corrupted. We can change th file extension to xls. Then we can open the report again.
2- Is it possible to define the default extension when we save input schedules and reports? By default xltx is selected. We want to have xlt selected by default.
thanks for your help,
Romuald

Hello,
First you can try checking if you have configured your apset to work with xltx.
1. Open BPC web admin and select AppSet Parameters
2. Check ALLOW_EXTENSIONS and DEFAULT_EXTENSIONS if you have xltx there
3. If not, add and click on update
If this continues to happen, check note "1579344 - Office 2007 extensions not loading in BPC 7.5 SP6 for NW". This can be a program error, but note that it only happens for some templates.
Hope it helps
Debora

Excel 2007 and Smartview 11.1 file open slow

We are in the process of upgrading to HFM system 11.1 and smartview 11.1.1.3 and as part of this process we are starting to use Excel 2007. I am encountering an interesting problem when opening files in Excel 2007 using smartview 11.1 and I am wondering if any one else has seen this problem and found a solution.
First I converted an excel 2003 file to excel 2007 and saved the file as an xlsx file type. Then I am able to open the file and it would take about 30 seconds to open the file. The file has about 15,000 formulas on for spreadsheets. If I click on each spreadsheet individually and use the "Refersh" button I can save the file in about 10 seconds and then close the file. When I open the file again it will open in 30 seconds. Now using the same file I click "Refresh All" and the file processes fine. I am able to save and close the file in about 10 seconds. However, when I try to open the file again it takes about 20 minutes to open, and then 20 minutes to close.
This only happens with two or three files. I have another file that is 40 spreadsheets and about 3,000 formulas that is not affected when I click Refresh or Refresh All.
Any help would be apperciated.
Rich

Hi
On metalink i found some notes about this issure
"Background
SmartView communicates over HTTP using .NET. This just means that requests and responses are sent in a standard XML format that is tucked in the HTTP headers. The mechanism is the same as when your internet browser requests a file or submits a form (simplification). A standard Microsoft component that is part of Internet Explorer is used for this.
There are three components (four if you include the network) in a SmartView refresh:
-the client
-the web server
-the HFM application server
It is easiest to troubleshoot when they are on separate machines. (Running SmartView on the server to see whether it works better is a useful test to see what effect the network is having, but doesn't show any other bottlenecks.) If you run Task Manager on these 3 machines showing the Performance tab, you will see initial activity on the client as Excel clears the cells and the request is converted into XML. Then you see the web server get busy as it receives and parses the request. Then the application server is busy as it send the data, then the web server is busy as it compiles the results into XML again, and finally the client parses the XML, pushes the data into cells and runs an Excel calculation. This last stage is the longest of all. Overall, it is typical to see the client doing 90-95% of the work, so client performance is a very important factor. Look out for Excel's memory usage increasing and RAM becoming in short supply. Often, user dissatisfaction with refresh times can be alleviated by giving them more RAM or a faster PC.
The situation we are dealing with here, however, is when the chain of events described above is interrupted. In this case, you will see the client or the web server wait in vain for a response from the next machine in the chain. The case of invalid XML is similar, but the response is truncated so that the XML is not well-formed when it arrives. XML consists of matching pairs of tags and is not well-formed when a closing tag is missing. This can be caused by certain network settings such as packet size (see later). The end result in either case is the same: as Excel cleared the cells before sending the request, cells are left blank or with zeroes.
Your job now is to work out why the particular component is failing.
Client
Check the HTTP time out in the registry:
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]\
"ReceiveTimeout"=dword:00dbba00
"KeepAliveTimeout"=dword:002BF20
"ServerInfoTimeout"=dword:002BF20
The time-out limit is five minutes for versions 4.0 and 4.01 and is 60 minutes for versions 5.x and 6. Also, the time-out limit is 30 seconds for Windows Internet Explorer 7. To change the settings, add the above keys. The above values are hexadecimal, not decimal and correspond to 18000 milliseconds (3 minutes) and 240 minutes for the receive time-out. See
- http://support.microsoft.com/kb/813827
- http://support.microsoft.com/kb/181050
Once you make those changes, my recommendation is that you reboot the client machine.
Web server
Look for errors in logs showing that the web app didn't respond/disconnected or timed out waiting for another application (i.e. the HFM application server). Eliminate load balancers etc. during testing in order to isolate the problem and to ensure that the user always goes to the same web server otherwise, logs can be hard to interpret. See also the IIS Tuning Guide for IIS settings. We cannot recommend particular settings, as each client must establish the optimal settings for their own environment after performance testing. If necessary, engage the services of a suitably qualified consultant.
Application Server
HFM application server performance is very dependent on whether the data is already in RAM or not. One symptom, where the first refresh fails but the second one succeeds, is probably a sign that the cache needed to be populated and once that had been done (by the first refresh) it went faster. HFM loads whole subcubes (Scenario, Year, Value and Entity) into cache, so asking for lots of accounts in the same subcube is fast, but asking for lots of entities will inevitably slow things down as it runs out of RAM and starts unloading subcubes to make room for more. The HFM event log (HsvEventLog.log) shows this happening, but don't forget that the messages you see are a normal consequence of the way HFM works and are not a problem unless you see a hugely elevated number of them during the period the refresh occurs. Another sign would be page file thrashing.
If there are several servers in a cluster, use sticky sessions in HFM to make sure tests always go the same server, or hit one server directly rather than using the cluster.
Solutions here involve giving more RAM to the server (probably not possible because of the 2 GB limit) and changing the worksheet design to restrict the number of subcubes accessed. A separate consolidation server, so that reads are not competing with intensive consolidations and calculations, would be a good thing.
Network
To find out if packets get fragmented, use
ping -l size -f
to send a big packet with the 'don't fragment' flag. E.g.
Ping -l 1024 -f oracle.com
If you see a reply like Reply from 141.146.8.66: bytes=1024 time=200ms TTL=245 then the size you specified is below the packet limit of the network. But if you use, for example, 2000 in place of 1024, you get Packet needs to be fragmented but DF set, then you know you have exceeded the limit. Combine this investigation with a Fiddler trace (https://www.fiddler2.com/fiddler2/) to see what size data messages are being sent and received.
Troubleshooting Guidance
If you seriously want to go into this in more detail, then it will take a considerable effort on your and your IT Department's part. My general advice would be:
1. During this process, fix your environment so that it is predictable. Register a single HFM application server and connect to that. Use a single web server and don't go through Apache or any other redirector. Make sure we know which machine to go to for logs. This would be a temporary measure and it doesn't stop the other users using the full, load balanced system so long as it doesn't involve your server.
2. As far as possible keep other users from using it during testing, unless you are specifically testing for performance under load. We want to see what activity is due to SmartView and not random other jobs.
3. Use PerfMon on all three machines: client, web server and application server.
4. Clear Logs before testing and note the times of each test so the logs can be correlated.
5. Log CPU activity, memory usage, network throughput, page faults, thread count etc. I'm no expert on this so get advice from someone who is.
6. In addition to the performance logs, from the IIS Server get:
* HTTP.SYS Error Log - %windir%\System32\LogFiles\HTTPERR (Default location; configurable)
* IIS Website Log - %windir%\System32\LogFiles\W3SVC# (Default location; configurable)
* Event Log (both System and Application) in EVT and TXT (tab separated) formats
7. From HFM Application server get:
* HsvEventLog.log (in <HFM install>\Server working Folder)
* Event Log (both System and Application) in EVT and TXT (tab separated) formats
8. Be aware of all timeout settings in your environment (i.e. IIS & the network) and time your tests. This can show whether it is an ASP timeout, script timeout, client side timeout or whatever. Note that the Web Session Timeout setting for SmartView in HFM's Server and Web Configuration is a separate issue from IIS timeouts. Web Session Timeout controls the length of idle time before SmartView makes the user log in again. Default 20 mins.
9. Run Fiddler traces to directly observe the XML and check for HTTP failures.
Further resources
- Tuning IIS 6.0 for HFM
- SmartView Performance FAQ
Both are available from Support.
Author: Andrew Rowland
Version: 11.x (Fri, 30 October 2009)"
regards
Alexander

Smartview 11.1 - Excel 2007

Hi
We have just upgraded from Excel 2003 to Excel 2007, and are using Smartview 11.1 and HFM 9.3.1.
When refreshing on the Excel 2003 files it is extremely slow, are there any changes that are to be made?
Regards

In Excel 2007 the workbook calculation is set to Automatic by default.
Go to Excel Options | Formulas. Change Workbook Calculation to Manual and see if that improves the performance.

ALV download to EXCEL -- probs with SAPGUI 6.40 and EXCEL 2007

I have a method in an ALV grid which performs a dowload to excel
Here's the method
method download_to_excel.
field-symbols:
       <fs0> type standard table,
       <fs1> type standard table.
    assign g_outtab1->* to <fs0>.
    assign g_fldcat1->* to <fs1>.
       call function 'LVC_TRANSFER_TO_KKBLO'
      exporting
        it_fieldcat_lvc   = <fs1>
    is_layout_lvc     = m_cl_variant->ms_layout
         is_tech_complete = ' '
      importing
        es_layout_kkblo   = ls_layout
        et_fieldcat_kkblo = lt_fieldcat.
    loop at lt_fieldcat into lt_fieldcat_wa.
      clear lt_fieldcat_wa-tech_complete.
      if lt_fieldcat_wa-tabname is initial.
        lt_fieldcat_wa-tabname = '1'.
        modify lt_fieldcat from lt_fieldcat_wa.
      endif.
      l_tabname = lt_fieldcat_wa-tabname.
    endloop.
    call function 'ALV_XXL_CALL'
         exporting
              i_tabname           = l_tabname
              is_layout           = ls_layout
              it_fieldcat         = lt_fieldcat
              i_title             = sy-title
         tables
              it_outtab           = <fs0>
         exceptions
              fatal_error         = 1
              no_display_possible = 2
              others              = 3.
    if sy-subrc <> 0.
      message id sy-msgid type 'S' number sy-msgno
             with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    endif.
endmethod.
Basically the method converts the GRID table I'm displaying into the format requred for FMOD ALV_XXL_CALL' -- the field catalog is slightly different but no big deal here.
This works fine when downloading to EXCEL 2003 but short dumps when trying to do the same thing for EXCEL 2007.
Workstation is running Windows XP / SP2 build 2600 in both cases.
Any fixes etc or should I stick with EXCEL 2003 until forced to upgrade.
Cheers
jimbo

Hi all
Seems the problem disappeared after applying the latest patch to SAP_GUI 6.40.
I haven't tried SAP_GUI 7.0 yet.
Thanks anyway
Cheers
jimbo

Excel 2007 csv file formatting issue

Our users create .csv files for upload to SAP. Their habit is to include a number of blank lines in excel to make it more readable.
In Excel 2003, blank lines were handled as, literally, blank lines, and opening in a text editor shows exactly that, a blank line (with a CR-LF character to terminate the row).
In Excel 2007 however, the blank line consists of a number of commas equal to the no. of columns, followed by the CR-LF termination. Hope that makes sense.
While the 2003-generated .CSVs are fine, the 2007 versions cause SAP to throw an exception ("Session never created from RFBIBL00") and the upload fails. The question therefore is, has anyone ever come across anything similar, or is anyone aware of any remediation that might be possible? Haven't been able to find any documentation on this Excel 2003-2007 change sonot able to address the issue through Excel config.
Thanks!
Duncan

Hello
Please refer to the consulting note 76016 which will provide information on the performance of the standard program
RFBIBL00.
Regards.

Just switched to Excel 2007...a few questions

I just switched to Excel 2007 from Excel 2003 and am experiencing the zoom/delayed retrieval issues that many have spoken of in other threads.
We currently are running essbases 9.3.1.0
Many of my other co-workers are still using Excel 2003.
Our company has not yet upgraded to version 11 yet so what is the optimum version (update) of essbase I should be using so that I do not experience these zoom issues and will that impact the compatability of any of my spreadsheets with my co-workers who are using Excel 2003?
Do I need 9.3.1.3?
Thanks in Advance!
Edited by: [email protected] on Jun 18, 2010 9:21 AM

Hi,
9.3.1.3 client install should resolve your issues
Spreadsheet Add-in. Retrieving data using Spreadsheet Add-in with Microsoft Excel 2007 may result in slow performance. When the Formula Fill option is selected, zooming in on a member (whether using mouse actions or menu items) may result in slow retrieval performance and an error message indicating that the maximum number of rows has been exceeded.
When the Retain on Zoom option is selected, zooming out on a member (whether using mouse actions or menu items) may result in slow retrieval performance.
The Formula Fill and Retain on Zoom options are on the Mode tab of the Essbase Options dialog box. [6695282, 7019497, 7019501]
More information in the readme :- http://download.oracle.com/docs/cd/E10530_01/doc/epm.931/esb_93130_readme.pdf
Different client installation files can be downloaded from My Oracle Support under patches.
Cheers
John
http://john-goodwin.blogspot.com/

EVDRE - Excel 2003 vs Excel 2007 performance

Similar Messages

Maybe you are looking for