cancel
Showing results for 
Search instead for 
Did you mean: 

Succession Planning 3.0 SP1: Analytics not working

Former Member
0 Kudos

Hi,

We're on Succession Planning 3.0 SP1.

Our Analytics aren't working. All fields have the same error: Index:0, Size:0. This happens to every single field in the Analytics.

Does any know what causes this? Here's the log file:


23399. at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:447)
23400. at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:264)
23401. at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
23402. at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
23403. at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
23404. at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:315)
23405. 
23406. 14 Mar 2011 15:10:08 ERROR com.nakisa.Logger - SAP_Dashboard_SuccessionPlanning : Requested Table(Name:Successionplanning) not found in the DataSet.
23407. 14 Mar 2011 15:10:08 ERROR com.nakisa.Logger - Dashboard_SPTalentPerOrgRatioRep : java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
23408. 14 Mar 2011 15:10:08 ERROR com.nakisa.Logger - java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
23409. at java.util.ArrayList.RangeCheck(ArrayList.java:547)
23410. at java.util.ArrayList.get(ArrayList.java:322)
23411. at com.nakisa.framework.data.DataSet.getTable(DataSet.java:138)
23412. at com.nakisa.framework.webelement.report.KPIReportProcessor.process(KPIReportProcessor.java:71)
23413. at com.nakisa.framework.webelement.ReportElement.process(ReportElement.java:95)
23414. at com.nakisa.framework.webelement.ReportElement.process(ReportElement.java:46)
23415. at com.nakisa.troll.webelement.DetailAppProfile.processReport(DetailAppProfile.java:177)
23416. at com.nakisa.framework.webelement.DetailApp.a(DetailApp.java:1046)
23417. at com.nakisa.framework.webelement.DetailApp.processDetailsContent(DetailApp.java:177)
23418. at com.nakisa.troll.webelement.DetailAppProfile.process(DetailAppProfile.java:58)
23419. at com.nakisa.troll.application.profiles.ProfilesAppEventProcessor.renderDashboard(ProfilesAppEventProcessor.java:501)
23420. at com.nakisa.troll.application.profiles.ProfilesAppEventProcessor.initializeProfileDashboard(ProfilesAppEventProcessor.java:408)
23421. at com.nakisa.troll.application.profiles.ProfilesAppEventProcessor.refreshHCMDashboard(ProfilesAppEventProcessor.java:216)
23422. at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
23423. at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

Accepted Solutions (0)

Answers (2)

Answers (2)

lukemarson
Active Contributor
0 Kudos

My initial thoughts are that the downloadSchema or data element configuration is not correct, but it could be a bug in SP1 becuase, as Stephen says, it is not in general availability and is still under BETA testing.

Former Member
0 Kudos

Hi,

ABAP Add-on were upgraded. I contacted them, they say they are looking into it.

Regards,

Former Member
0 Kudos

Hi,

We obtained a newer SP1 build and this is solved.

Regards,

StephenBurr
Active Contributor
0 Kudos

Have you installed or upgraded your Add On since you applied SP1?

I presume Nakisa are supporting you heavily on this since SP1 is not in General Availability yet ... what have they said?