cancel
Showing results for 
Search instead for 
Did you mean: 

BPC 10.0 Input Schedule refresh : investigating performance issues on frontend side

Farid
Active Participant
0 Kudos

Hello,

We are running SAP BPC NW 10.0 SPS8.

We recieve a lot of complaints regarding performance issues.

More specifically BPC Input Schedule refresh takes ages (11 minutes actually)

I am a SAP Basis Administartor with some solid BW experience, but very linited BPC knowledge.

So raf we have tried the following :

* BPC Full and light ptmimize of the BPC Cubes.

* Updating Oracle Statistics

* Activating ABAP/SQL traces*

* Checking USJTAT Logs

Then it rutned out that the perfromance problems werre not caused by the backend SAP BW server (only 9 seconds of bakend  processing are displayed in UJSTAT).

The overwhelming majority of the processing is spent on the frontend side : on the computer of the user.

We really would like to know what is happening on BPC Frontend side, but are really lacking any investigative method .....

other that  checking memory/CPU usage o nthe frontend computer.

From your experience, is there any tool/method to allow to conduct some investigation on what is going on the frontend side, when a BPC Input Schedule is refreshed ?

Thank you for your attention.

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member186338
Active Contributor
0 Kudos

Hi Raoul,

Do you have any default.lgf script or write back badi in BPC?

Vadim

Farid
Active Participant
0 Kudos

Hello Vadim,

Yes, we indeed have Write-Back Badi in BPC.

Does it impact perfromances on the frontend side ?

Thanks

former_member186338
Active Contributor
0 Kudos

For test - remove badi filter and test input schedule without this badi (and without default.lgf). I don't think it's a frontend issue.

Vadim

former_member186338
Active Contributor
0 Kudos

P.S. And also check refresh time of the input schedule - just refresh, without sending...

Farid
Active Participant
0 Kudos

Hello Vadim,

Actually, I am only refreshing the schedule at the moment, I am not trying to save/send any data

The write back wouldn't come into play until trying to save, as far as I undersatnd it ?

former_member186338
Active Contributor
0 Kudos

Yes, if it's a huge refresh delay then check if you have members with dimension member formulas and not default cube measures!

Also I hope that we are talking about normal EPM reports without EPMRetrieveData functions (slow!)

Vadim

Farid
Active Participant
0 Kudos

Hello Vadim,

We still need to get confirmation from the external consultants who developed the BPC solution, but as far as I can understand it :

We do not use use member formulas

We are indeed talking about EPM (without EPMRetrieveData functions)

The perfromance  problems occur in DEV and QAS , after a restore of the BPC environment (backup from PRD)

We already had the problem in the past, but we never knew precisely how to solve it, it is as if there was some missing links between the restored BPC environment from PRD and the DEV/QAS system

One additional information, we checked the EPM CLient Log , and here are the errors displayed while refreshing the input schedule :

The thing is that I have no idea what it means ...

?FILE_TYPE:DAAA96DE-B0FB-4c6e-AF7B-A445F5BF9BE2

RECORD_SEPARATOR:35

COLUMN_SEPARATOR:124

COLUMNS:Time|Severity|Category|Method|User|DSRRootContextID|DSRTransactionID|DSRConnectionID|DSRCounter|Thread|Text

SEVERITY_MAP:DEBUG|Debug|INFO|Information|VERBOSE|Verbose|WARNING|Warning|ERROR|Error|FATAL|Fatal

HEADER_END

2014-04-18 08:41:17,446|ERROR|ReportManagement|FPMXLClient.Office.EPMExcelReportManagerRepository.GetReportManager|BPCUSER|||||1|Unable to get the Object property of the OLEObject class#

2014-04-18 08:41:18,613|ERROR|ReportManagement|FPMXLClient.Office.EPMExcelReportManagerRepository.GetReportManager|BPCUSER|||||1|Unable to get the Object property of the OLEObject class#

2014-04-18 08:41:18,630|ERROR|ReportManagement|FPMXLClient.Office.EPMExcelReportManagerRepository.GetReportManager|BPCUSER|||||1|Unable to get the Object property of the OLEObject class#

2014-04-18 08:41:18,648|ERROR|ReportManagement|FPMXLClient.Office.EPMExcelReportManagerRepository.GetReportManager|BPCUSER|||||1|Unable to get the Object property of the OLEObject class#

2014-04-18 08:41:18,731|ERROR|ReportManagement|FPMXLClient.Office.EPMExcelReportManagerRepository.GetReportManager|BPCUSER|||||1|Unable to get the Object property of the OLEObject class#

2014-04-18 08:41:37,171|ERROR|ReportManagement|FPMXLClient.ReportManagement.DynamicReport.Load|BPCUSER|||||1|bytes = 1#

2014-04-18 08:41:39,348|ERROR|ReportManagement|FPMXLClient.ReportManagement.DynamicReport.Load|BPCUSER|||||1|bytes = 0#

2014-04-18 08:41:39,474|ERROR|ReportManagement|FPMXLClient.ReportManagement.DynamicReport.Load|BPCUSER|||||1|bytes = 0#

2014-04-18 08:41:39,536|ERROR|ReportManagement|FPMXLClient.ReportManagement.DynamicReport.Load|BPCUSER|||||1|bytes = 0#

2014-04-18 08:41:39,597|ERROR|ReportManagement|FPMXLClient.ReportManagement.DynamicReport.Load|BPCUSER|||||1|bytes = 0#

2014-04-18 09:00:22,088|ERROR|Dataservice|FPMXLClient.BPCProxy.MetaData_Data.DataServiceHelper.ExecuteReportAsStream|BPCUSER|||||ServerCallThread_666f378d-d824-4a8a-bf38-0da8493e2382|An error has occured on the server#

2014-04-18 09:00:22,252|ERROR|BPC10Connection|FPMXLClient.Connection.RESTConnection.ExecuteReport|BPCUSER|||||ServerCallThread_666f378d-d824-4a8a-bf38-0da8493e2382|An error has occured on the server#

2014-04-18 09:00:22,268|ERROR|OfficeWrappers|FPMXLClient.Office.EPMReportManager.ExecuteReport|BPCUSER|||||1|An error has occured on the server#

2014-04-18 09:00:22,317|ERROR|OfficeWrappers|FPMXLClient.Office.EPMExcelReportManager.RefreshReports|BPCUSER|||||1|An error has occured on the server#

2014-04-18 09:00:22,447|ERROR|AnalyzerOne|FPMXLClient.AddIn.RefreshSheetWithScan|BPCUSER|||||1|Execution of Report Default Report failed : #

2014-04-18 09:00:22,537|ERROR|Automation|FPMXLClient.EPMAddInAutomation.RefreshActiveSheet|BPCUSER|||||1|Execution of Report Default Report failed : #

former_member186338
Active Contributor
0 Kudos

Hi Raoul,

Unfortunately client log is not very informative... Another issue can be that DEV and QAS servers are very slow due to hardware/resources  (we use virtual servers for DEV and QA)...

Vadim