MSS Reporting iview

[Former Member]

Hi Guys,

I am getting following error while I am accessing Reporting Iview in MSS.

Any help?

Thanks in advance

bye

Raj

Failed to process request. Please contact your system administrator.

[Hide]

Error Summary

While processing the current request, an exception occured which could not be handled by the application or the framework.

If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).

Root Cause

The initial exception that caused the request to fail, was:

com.sap.tc.webdynpro.progmodel.controller.MessageManager$AbortMessageManagerException: Role: MSS instance: REP NOT_FOUND

at com.sap.tc.webdynpro.progmodel.controller.MessageManager.raiseException(MessageManager.java:430)

at com.sap.xss.fin.lpa.reportlaunchpad.BLpaReportLaunchpadComp.LPAInit_Start(BLpaReportLaunchpadComp.java:684)

at com.sap.xss.fin.lpa.reportlaunchpad.wdp.InternalBLpaReportLaunchpadComp.LPAInit_Start(InternalBLpaReportLaunchpadComp.java:704)

at com.sap.xss.fin.lpa.reportlaunchpad.BLpaReportLaunchpadCompInterface.LPAInit_Start(BLpaReportLaunchpadCompInterface.java:217)

at com.sap.xss.fin.lpa.reportlaunchpad.wdp.InternalBLpaReportLaunchpadCompInterface.LPAInit_Start(InternalBLpaReportLaunchpadCompInterface.java:649)

... 61 more

Detailed Error Information

Detailed Exception Chain

com.sap.tc.webdynpro.progmodel.controller.MessageManager$AbortMessageManagerException: Role: MSS instance: REP NOT_FOUND

at com.sap.tc.webdynpro.progmodel.controller.MessageManager.raiseException(MessageManager.java:430)

at com.sap.xss.fin.lpa.reportlaunchpad.BLpaReportLaunchpadComp.LPAInit_Start(BLpaReportLaunchpadComp.java:684)

at com.sap.xss.fin.lpa.reportlaunchpad.wdp.InternalBLpaReportLaunchpadComp.LPAInit_Start(InternalBLpaReportLaunchpadComp.java:704)

at com.sap.xss.fin.lpa.reportlaunchpad.BLpaReportLaunchpadCompInterface.LPAInit_Start(BLpaReportLaunchpadCompInterface.java:217)

at com.sap.xss.fin.lpa.reportlaunchpad.wdp.InternalBLpaReportLaunchpadCompInterface.LPAInit_Start(InternalBLpaReportLaunchpadCompInterface.java:649)

at com.sap.xss.fin.lpa.reportlaunchpad.wdp.InternalBLpaReportLaunchpadCompInterface$External.LPAInit_Start(InternalBLpaReportLaunchpadCompInterface.java:761)

at com.sap.xss.fin.lpa.reportlaunchpad.CLpaReportLaunchpadPcdCompInterface.loadConfiguration(CLpaReportLaunchpadPcdCompInterface.java:139)

at com.sap.xss.fin.lpa.reportlaunchpad.wdp.InternalCLpaReportLaunchpadPcdCompInterface.loadConfiguration(InternalCLpaReportLaunchpadPcdCompInterface.java:127)

at com.sap.xss.fin.lpa.reportlaunchpad.wdp.InternalCLpaReportLaunchpadPcdCompInterface$External.loadConfiguration(InternalCLpaReportLaunchpadPcdCompInterface.java:214)

at com.sap.pcuigp.xssutils.ccxss.CcXss.loadConfiguration(CcXss.java:208)

at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXss.loadConfiguration(InternalCcXss.java:153)

at com.sap.pcuigp.xssutils.ccxss.CcXssInterface.loadConfiguration(CcXssInterface.java:112)

at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface.loadConfiguration(InternalCcXssInterface.java:124)

at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface$External.loadConfiguration(InternalCcXssInterface.java:184)

at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:190)

at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)

at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)

at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:429)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:345)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:668)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:268)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:725)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:661)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)

at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)

at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:739)

at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:208)

at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1240)

at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:340)

at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:538)

at com.sap.portal.pb.PageBuilder.wdDoApplicationStateChange(PageBuilder.java:287)

at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoApplicationStateChange(InternalPageBuilder.java:197)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doApplicationStateChange(DelegatingComponent.java:139)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.doApplicationStateChange(ClientComponent.java:659)

at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doApplicationStateChange(ClientApplication.java:520)

at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:120)

at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:298)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659)

at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)

at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:40)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

[Former Member · Accepted solution]

Raj,

Are all the other MSS iviews working fine (ie is your connection to your R/3 backend working)?

Are you sure the MDT scenario you put it is correct?

If your getting the correct list of reports but when you run them you get this error, then I would check in the R/3 system for any dumps - or if the report exists.

[Former Member · Accepted solution]

Hi Chuckie,

All other iview working fine but yes I am getting shortdump in backend as well.

Runtime Errors UNCAUGHT_EXCEPTION

Exception CX_WDR_RR_EXCEPTION

Date and Time 02.05.2006 09:56:43

Short text

An exception occurred that was not caught.

What happened?

The exception 'CX_WDR_RR_EXCEPTION' was raised, but it was not caug

along

the call hierarchy.

Since exceptions represent error situations and this error was not

adequately responded to, the running ABAP program 'SAPLWDR_RUNTIME_

has to be

terminated.

Error analysis

An exception occurred which is explained in detail below.

The exception, which is assigned to class 'CX_WDR_RR_EXCEPTION', wa

and

therefore caused a runtime error.

The reason for the exception is:

Die Komponente ist nicht aktiv

How to correct the error

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yours

please use the following search criteria:

"SAPLWDR_RUNTIME_REPOSITORY" "UNCAUGHT_EXCEPTION"

If you cannot solve the problem yourself, please send the

following documents to SAP:

1. A hard copy print describing the problem.

To obtain this, select the "Print" function on the current scree

-

2. A suitable hardcopy prinout of the system log.

To obtain this, call the system log with Transaction SM21and select the "Print" function to print out th

part.

If the programs are your own programs or modifi

supply the source code.

To do this, you can either use the "PRINT" comm

print the programs using the report RSINCL00.

Details regarding the conditions under which th

or which actions and input led to the error.

[Former Member · Accepted solution]

Hi Raj

can u provide the Support Package information for R3 Ecc 5.0 ,Sap j2ee Engine and ESS MSS SP .

regards,

kaushal

[Former Member · Accepted solution]

Hi Guys

we have installed the MSS 6.1.18 version in EP. Some how, we are not seeing the report launchpad in the reporting iview. I assume that this is a configuration issue. Can any of you help me in setting this up in reporting?

Thanks

Kalyan

[Former Member · Accepted solution]

Have you updated the scenario in the iview properties to the scenario that you use in MDT?

Hope this helps

[Former Member · Accepted solution]

Chukie,

Thanks for the post. The scenario is setup correct. We are seeing the reports. My question is regarding the selection criteria iview of this workset. There is no option to select from the reports available. Sorry I didn't explain the problem clearly before.

Thanks

Kalyan

[Former Member · Accepted solution]

Chuckie,

Reframe my question. Do we have an option where we can select any reports of our interest from a drop down or something similar to that?

[Former Member · Accepted solution]

SAP standard content doesn't provide an option to select reports from Dropdown.But, You can Customize the iview and display reports in Dropdown..

Jojo

[former_member336426 · Accepted solution]

This reporting tool and its selectioin criteria iview will only display reports for selection based on the configured selection.

If you want to change the layout of the reports or add new reports, then you must do this through configuration in SAP. Basically it is how you show reports in what was manager desktop.

You cannot dynamically change the list of reports that can be run (ie the way you can run reports in transaction se38 or sa38).

Obviously you can create this functionality, but this would require development.

When you configure MDT you can have loads of different scenarios so managers could see one view of the reports available and employees another etc etc.

Hope this helps

[Former Member]

you can customize MSS Launchpad using transaction fpb_launchpad_cust.

This worked for us to solve the problem.

choose MSS and REP and add your reports..

Pascal Rijnart