MSS Report Error

[Former Member]

Hi Expert,

We are facing error when accessing report in MSS, we managed to get to then employee selection section but after that it give error warning "please see the log file"

Here is the log file:

#com.sap.tc.cbs.server.dao.PersistencyLayerException: Database Error:error while deleting log assemblies

Original Cause: [ibm][db2][jcc][10143][10845] Invalid parameter 4: Parameter is not set nor registered.

at com.sap.tc.cbs.server.db.impl.DBDelete.deleteLogAssemblies(DBDelete.java:819)

at com.sap.tc.cbs.server.db.impl.DBDelete.cleanupLogAssemblies(DBDelete.java:784)

at com.sap.tc.cbs.server.db.impl.AdminDB.cleanupBinaries(AdminDB.java:288)

at com.sap.tc.cbs.server.rt.impl.BinarySweeper.act(BinarySweeper.java:83)

at com.sap.tc.cbs.server.rt.impl.CourteousTimer.run(CourteousTimer.java:139)

at java.lang.Thread.run(Thread.java:838)

Caused by: com.ibm.db2.jcc.c.SqlException: [ibm][db2][jcc][10143][10845] Invalid parameter 4: Parameter is not set nor registered.

at com.ibm.db2.jcc.c.sh.pb(sh.java:3210)

Any ideas about this error? Many Thanks

[siddharthrajora · Accepted solution]

its an issue with backend system

I would like you first of all to try taking out this RCS_Backend value

and filling the field with the value SAP_LocalSystem so that we can

see if the issue gets resolved.

In addition to this, I would like to you to inform us in case you know

what this RCS_Backend system would be, and how it could have been

used to this iView. I've looked at the Floating Aliases image you

provided us in order to check about the existance of the alias

RCS_Backend, but could not find it.

[Former Member]

Hi,

Thank You problem is solved. The problem lies with the system alias, it refers to none existing aliases or system. I told my portal administrator your idea and he got it solve. Thanks again.

Best Regards,

Hendri Salim

[Former Member]

Hi Siddharth Rajora ,

First of all thank you for the support so far. But i have to ask what is RCS_Backend? i'm not familiar with this terms, would you be so kind to elaborate this further? Many thanks

Best Regards

Hendri salim

[Former Member]

Hi,

I already reconfig all the setting and use the standard rpt0. But the error still persist with different error log:

 
03:39_07/01/11_0202_4701750 
[EXCEPTION]
 com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.Access.ITS.protocol>://<System.Access.ITS.hostname>/sap<ESID>/bc/gui/sap/its/<IAC[SAP_ITS_NAMESPACE]>?sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&~DisconnectOnClose=0&~DesignBaseUrl=<LAF.BaseUrl[url_ENCODE]>&~design=<LAF.Theme[url_ENCODE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 121. Cannot process expression <System.client> because Invalid System Attribute:
 System:    'SAP_LocalSystem', 
Attribute: 'client'. 
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:540)
at java.security.AccessController.doPrivileged(AccessController.java:231)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:423)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
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(AccessController.java:207)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Best Regards

[siddharthrajora]

Objects is org structure, we need to check what output you get

most likely it can be a role or report category assigned

For example

Objects O 50000084

1) You can change the iview property 'Scenario' from RPT0 to your custom

scenario type. The iview is located under the following PCD path ( as

per standard delivery)

portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/co

m.sap.pct.erp.mss.iviews/com.sap.pct.erp.mss.hcm/com.sap

.pct.erp.mss.lpareporting

However, this solution has a weakness as reports of only your

custom scenario type would work.

2) The best possible solution is to convert the scenario type as RPT0 in

the backend reporting configuration . This way both the custom and

standard reports works from the portal.

tables

- T77MWBS (Manager#s Desktop Scenarios)

- T77MWBFCD (Function Code Definitions)

- T77MWBFCO (Object-dependent Function Codes)

- T77MWBBWS (BW Report System Data)

- T77MWBFCH (Function Code Hierarchies)

and conversion to LPA

PWPC_CONVERT_MDT_TO_LPA

[Former Member]

Hi,

Thanks for the reply. When executing PWPC_RPT_START_REPORT_TEST nothing happen. I use this parameters

Planversion : 01

Scenario: RPTO

Function Code : MSS_NODE_HIS

Start Date: 01.01.2010

End Date: 31.12.9999

Objects: Blank (i dont know what to insert here)

I already do the PWPC_CONV_MDT_TO_LPA and there is entries that succesfully converted such age, or birthday list.

I also login to the back end using user that have subordinate defined in OM. Any ideas?

Regards

[siddharthrajora]

can you check in the backend? refer here for the steps

http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=199820849

Mostly looks like a portal setting or role

you can try from content admin as well