Error in "Maintain Performance Documents" Iview

Hi,
I have a Iview in MSS - "Maintain performance documents".
When I open the Iview(Status Overview) through MSS it shows the documents link.But when I click on the links in Status Overview I am getting the following error.
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 01:13_06/09/10_0031_8961850
Refer to the log file for details about this exception.
After checkign the portal log I can see teh error as follows
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/<CustomerNamespace><ESID>/bc/bsp/<Namespace>/<Application>/<PageId>?<UseNoCookie[IF_true]>sap-client=<System.client>&sap-language=<Request.Language>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&sap_ep_version=<Portal.Version[url_ENCODE]>&sap_ep_baseurl=<Portal.BaseURL[url_ENCODE]>&<Authentication>&<DynamicParameter[PARAMETER_MAPPING PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 161. Cannot process expression <System.client> because Invalid System Attribute:
System: &#39;SAP_LocalSystem&#39;,
Attribute: &#39;client&#39;.
Which system attribute it is talking about? Not getting from where its showing SAP_Localsystem..I checked the system object used in Iview.It is working fine.
There are no authorization errors also.
When I chekced the iview being opened after clicking on link in "Status Overview",
it is pointing to standard iview.How do I make it point to customized iview pointing to my client at R/3.
Please suggest what might be the solution.
Thanks and Regards,
Sumangala
Edited by: Sumangala Byali on Sep 6, 2010 10:04 AM

Hi Suman ,
Have you performed the connection tests for your system object ? Please share the results . Make sure that you are pointing to the correct client in your backend .
I hope you are using system alias name in the property of the iview . To me it looks that there is something wrong with system object or may be an improper configuration .
Regards
Mayank

Similar Messages

Error in Maintain Performance Documents under Team in MSS

Getting below error when i click Maintain Performance Documents under Team in MSS
java.lang.NullPointerException
     at com.sap.xss.hr.mbo.blc.BMboStatusComp.resetGlobalMboR3Data(BMboStatusComp.java:260)
     at com.sap.xss.hr.mbo.blc.wdp.InternalBMboStatusComp.resetGlobalMboR3Data(InternalBMboStatusComp.java:195)
     at com.sap.xss.hr.mbo.blc.BMboStatusCompInterface.resetGlobalMboR3Data(BMboStatusCompInterface.java:150)
     at com.sap.xss.hr.mbo.blc.wdp.InternalBMboStatusCompInterface.resetGlobalMboR3Data(InternalBMboStatusCompInterface.java:168)
     at com.sap.xss.hr.mbo.blc.wdp.InternalBMboStatusCompInterface$External.resetGlobalMboR3Data(InternalBMboStatusCompInterface.java:224)
     at com.sap.xss.hr.mbo.vac.VMboStatusComp.onBeforeOutput(VMboStatusComp.java:227)
     at com.sap.xss.hr.mbo.vac.wdp.InternalVMboStatusComp.onBeforeOutput(InternalVMboStatusComp.java:187)
     at com.sap.xss.hr.mbo.vac.VMboStatusCompInterface.onBeforeOutput(VMboStatusCompInterface.java:143)
     at com.sap.xss.hr.mbo.vac.wdp.InternalVMboStatusCompInterface.onBeforeOutput(InternalVMboStatusCompInterface.java:136)
     at com.sap.xss.hr.mbo.vac.wdp.InternalVMboStatusCompInterface$External.onBeforeOutput(InternalVMboStatusCompInterface.java:212)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.callOnBeforeOutput(FPMComponent.java:603)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:569)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
     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:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     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:860)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1288)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:355)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:548)
     at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:192)
     at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
     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:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:756)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     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(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Regards
Karthi D

Hi Karthi,
Did u check below thread?
check the notes mentioned in that and suggested steps as it applies to your issue also
Re: MSS - Maintain Performance Document iView
Koti Reddy

Maintain Performance Documents

Hello Everyone,
The 'Maintain Performance Documents' iView appears, but nothing shows inside. I gave the users SAP_ALL and SAP_NEW and I believe all the required permissions on the portal content are set.
What can be causing this?
Regards,
Motaz

Hi,
There may two type of error. One from Portal Content and 2nd from backend content. Please check whether everything is fine from portal end. IF it is fine then check the backend role. At the time of execution of the activity please on the transaction ST01 in backend this will help you to check the authorization in backend. After finishing the activity execute transaction SU53 in backend.Check whether any error thre or not.
If everything is fine then you can ask some ABAPer to debugg the code.
Hope this will help you.
Thanks & Regards,
Sandip Biswas.

Authorization object to view Maintain Performance Documents on MSS

Hi Experts,
Would like to know which authorization object would require to view Maintain Performance Documents on MSS. Currently, we removed SAP_ALL access from MSS user and not able to peform Maintain Performance Documents.We are on EP 7 and ECC 6.
It gives following error :
java.lang.NullPointerException
     at com.sap.xss.hr.mbo.blc.BMboStatusComp.resetGlobalMboR3Data(BMboStatusComp.java:260)
     at com.sap.xss.hr.mbo.blc.wdp.InternalBMboStatusComp.resetGlobalMboR3Data(InternalBMboStatusComp.java:195)
     at com.sap.xss.hr.mbo.blc.BMboStatusCompInterface.resetGlobalMboR3Data(BMboStatusCompInterface.java:150)
     at com.sap.xss.hr.mbo.blc.wdp.InternalBMboStatusCompInterface.resetGlobalMboR3Data(InternalBMboStatusCompInterface.java:168)
     at com.sap.xss.hr.mbo.blc.wdp.InternalBMboStatusCompInterface$External.resetGlobalMboR3Data(InternalBMboStatusCompInterface.java:224)
     at com.sap.xss.hr.mbo.vac.VMboStatusComp.onBeforeOutput(VMboStatusComp.java:227)
     at com.sap.xss.hr.mbo.vac.wdp.InternalVMboStatusComp.onBeforeOutput(InternalVMboStatusComp.java:185)
     at com.sap.xss.hr.mbo.vac.VMboStatusCompInterface.onBeforeOutput(VMboStatusCompInterface.java:143)
     at com.sap.xss.hr.mbo.vac.wdp.InternalVMboStatusCompInterface.onBeforeOutput(InternalVMboStatusCompInterface.java:136)
     at com.sap.xss.hr.mbo.vac.wdp.InternalVMboStatusCompInterface$External.onBeforeOutput(InternalVMboStatusCompInterface.java:212)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.callOnBeforeOutput(FPMComponent.java:603)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:569)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:196)
     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:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     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:860)
     at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1288)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:355)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:548)
     at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:192)
     at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
     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:430)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:754)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:289)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     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(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Would appreciate kind guidance to resolve issue.
Thanks in advance.
Aashish

I am closing this thread as opened at wrong place.
Thanks,
Aashish

MSS - Team - Performance Management - Maintain Performance Documents

Hi,
When I click on the Maintain Performance Documents the page opens and shows only one iView - 'Status Overview'. As I understand it, this page is supposed to have two iViews on it, but the other iView 'Performance Management Document' is missing. So I can see my list of employees, but when I click on them, nothing happens. Anyone else run into this problem?

Hello Kenneth,
As sujan said is right, When you click on Maintain performance Document it opens Status Overview Iview
its display list of employees , initial if you have no appraisal its display blank cell In preparation colume,
if you have appraisal it display Performance Maintain Document iView(BSP) is App - HAP_DOCUMENT with all list of option for approval.
You can also create appraisal in Create Appraisal Document in ESS.
Please points if helpful.
Please close thread if problem solved
Thankyou
Regards
Vijai

MSS: Maintain Performance Documents

I am trying to implement MSS for ERP. When I click on 'Team->Maintain Performance Documents' the 'Status Overview' window opens. But when I click on the hyperlink under 'In preparation' so I can create a new appraisal, nothing happens. Anyone know why the hyperlink is not working?

Hi Kenneth,
Have you checked the Data provider under OADP in SPRO to see what service key is the 'In Planning' column mapped to. I suggest check the behavior of the service key if it has been modified.
Hope it helps,
Prathamesh

MSS - Team - Maintain Performance Document

Hello
In Manager self service -> Team -> Maintain performcance document ,in Show option drop down can we change the hirerarchy of the options getting displayed.
for example we are having two templates X & Y and by default we are getting X can we change that to Y.Please suggest how to do this.
Regards
Vishnu Priya
Edited by: priyav on Aug 25, 2010 10:39 AM

yes you can change the ordering of the templates
ie
You have made all necessary settings in Customizing for the Performance Management (Objective Setting and Appraisals) application component.
http://help.sap.com/erp2005_ehp_04/helpdata/EN/2e/5a5d45d9f24fbdb06be2ff53651c3e/frameset.htm

Status overview iView not refreshed for performance documents on MSS

Hi Experts,
We are using the standard portal business package for Manager Self Service. However, recently, we found out that one iView was working before suddenly stopped working. This is the Status Overview iView for Maintain Performance Documents. When searching for the performance appraisal documents for a group of direct report employees, the status overviewtable is not refreshed. Although we do have the appraisal documents in
R/3, the iView shows 0 results.
we use MSS 600 SP 8 BP
Please help.
Thanks.

Hi
Can anyone please provide an input on this.
Regards
Sasha.

Performance Document Status Overview

We have implemented ESS/MSS on EP7.0 on ECC6.0 and for MSS --> Maintain Performance Documents, we have used a custom BSP Application. Eveything is working fine except the 'status overview' doesn't show status info under correct column for old appraisals. But it shows relevant appraisal status under correct column if we choose 2008 appraisal. By default the portal shows 2006 Performance Appraisal in the drop down but dates are showing 01/01/2010 to 31/12/2010. We've changed the date from 01/01/2006 to 31/12/2006 but still employees appraisal status are not showing under correct column. All 2006 appraisal has "Close Approved" but for all them its showing under "In Preparation" column. But when we select 2008 Performance Appraisal, they work fine.
Any ideas how to fix that? We first thought we need to upgrade to higher SP level and we applied SP12. But still the status for 2006 or any other old appraisal is not pulling right.
Can anyone help?
Thank you,

""" On the portal "Status Overview" I-View for MSS --> Maintain Performance Documents, there is a property for employee evaluation period which needs to be set to "Yes". ""
how to change this property?
under content admin????
Thanks in advance.

Reg:- Custom Error Message for 404 error in KM Document iView

Hi All,
We have a requirement to display a custom error page instead of the standard"404 - The requested resource is not available" displayed in KM document iView, when the resource in question doesn't exist.
Is it possible to display custom error message? If so, how can we achieve this functionality? What are the settings to be made?
Appreicate your help.
Thanks and Regards,
Pavithra

Hi Ravi,
Thank you for the reply.
But the scenario what I am talking about is different from the one mentioned in the link.
I am using a KM Document iView. In the iView parameter, Path to Document, I have given the path to a document which does not exist in KM.
For example, Path to Document - /documents/Test Folder/abc.html.
There is no document by the name abc.html in KM.
In this case, I get an error called "404 - The requested resource is not available." How can I get rid of this message and show a custom message instead?
Please note that, this message appears at the iView level (and not page level as mentioned in the link)
Appreciate your help.
Regards,
Pavithra

Error on KM Document iView path

Hi Experts,
I just created a KM Document iView to contain a document stored in KM. The path for my document in KM is:
/root/documents/Folder/doc
When clicking on the Preview button on the iView I keep getting and 404 error.
Does anyone have a suggestion about this error?
Thanks in advance,
Neil

in the path to document property
instead of using the path
/root/documents/Folder/doc(wrong)
use below path
/documents/Folder/doc(correct)
This will solve your problem
also check that you have atelast read permission to that document in KM content.
Raghu

KM Document iView error

Hi,
I created one km document iView. I can see the uploaded document in the portal.But in the preview of the iView the uploaded document not displaying.I am getting the error like 404
The requested resource is not available.
I given the path of the document like
E:\ Name of the document.
Is it right way to give the path of the document?
Can someone help me for the above issue?
Thanks,
Kundan

Hi Kundan
Open a KM document iView
http://forums.sdn.sap.com/message.jspa?messageID=8840060
Using Parameters with KM document iView
http://forums.sdn.sap.com/message.jspa?messageID=8558460
KM Documents iView
http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/cf14bcd42911d5994400508b6b8b11/frameset.htm
Hope it helps
Regards
Arun

KM Document Iview Error in 7.3

Hi All,
    We have an External Link in our KM.We are usign KM Document iView pointing to this External link means in the Path to the document property we have given path of the external link.
-We use the same in 7.0 portal it works
-In 7.3 instead of external link if i give any doc,xls or image then it works
- Its not working for the External link alone in the 7.3
Anybody faced this issue?Anything changed with the KM document iview in 7.3?Please throw some light on this issue.
Naga

Hi Lorcan,
    Thanks for your time,
so can you give us more details as to how exactly you have set this up?
    Actually i have created a external lin in the KM using the option new->external link.i am usign this external link in the KM Document iVIew(Path to the document =path of the external link).
What is the name of the External Link? What is the path you specified in the KM Document iview?
    I am usign the NWA of another federated system as a external link.I have specified the same path in the KM document iView.The same path we used in 7.0 there it was fine so i am very sure about the path.And also the permission of the particular KM folder and external link has been provided with everyone read.
What happens when you try it, are you getting an error?
        When i try to preview the iView or when i use the iview in any role/page/workcenter its throwing error.
403
The requested operation is forbidden for this resource.
stack trace
com.sapportals.wcm.protocol.webdav.server.WDServletException
     at com.sapportals.wcm.protocol.webdav.server.WDGetHandler.handleRedirectCase(WDGetHandler.java:860)
     at com.sapportals.wcm.protocol.webdav.server.WDGetHandler.internalHandle(WDGetHandler.java:355)
     at com.sapportals.wcm.protocol.webdav.server.WDGetHandler.handle(WDGetHandler.java:280)
     at com.sapportals.wcm.protocol.webdav.server.WDServlet.doGet(WDServlet.java:846)
     at com.sapportals.wcm.protocol.webdav.server.WDServlet.service(WDServlet.java:523)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
     at com.sapportals.wcm.portal.proxy.PCProxyServlet.service(PCProxyServlet.java:344)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
     at com.sap.portal.prt.broker.ServletComponentItem$ServletWrapperComponent.doContent
Have you tried using different links?
    I tried with the different external link but all in vain.same issue i am facing.More over i tried with the URL iview pointing to the external link that too causing the same problem.
Is there anything in your landscape which could be preventing access to this external link from the portal?
We are not sure about that,recently we have upgraded the portal from 7.0 to 7.3.After that only we are facign this issue.before that this scenario was fine.Moreover we have upgraded the producer system too.In producer system we tried the same there we could use the external link both in KM document iView and URL iView.
Naga

PortalRuntimeException in Business Object document iview No portal component associated with the following context

Hi all,
We are stumped with a problem in our QA Enterprise Portal (7.3.1 Sp7) that throws a portal runtime error when we preview a Business Objects document iview. The Business Objects Server versions are 4.0 SP5 and/or 4.1 SP3.
The error is caught in the the defaultTrace file, /usr/sap/QNW/J00/j2ee/cluster/server0/log
[EXCEPTION]
com.sapportals.portal.prt.runtime.PortalRuntimeException: There is no portal component associated with the following context:
pcd:portal_content/com.summit.SES_BI/com.summit.iviews/Daily_Margin
at com.sap.portal.prt.component.PortalComponentContext.<init>(PortalComponentContext.java:93)
Here is what we have tried
* Confirmed the iviews exist in the PCD, by browsing to the content folders and right lick, preview on the iview.
* Our PRD and DEV systems work correctly and are on same versions of EP Runtime and java. 7.3.1.7.0.201..
* Occurs with all Businessobjects iviews from the QA portal and all doc types, webis, dashboards. Tried creating new iview.
* Reapplied the com.sap.businessobjects.iviews.templates.epa to the Portal from t he BI 4.1 SP3 distribution
* Deleted and recreated the BI portal system connector using the SAP BOBJ system template set path to http://bi-qas:8080/BOE
* Set the embed key value in the BI system connector property and in the custom global.properties file, restarted tomcat and SIA services
* Set permissions for everyone end user on the content folders and the BI system connector
* Confirmed Single sign on configured correctly between BI and Portal
* Confirmed that the QA BI server is configured correctly by directing the working DEV Portal to the QA BI server.
* Performed actions in note 1709737
We are certainly stuck and the defaultTrace file is not very informative. Any suggestions are greatly appreciated
Lee Lewis

This is resolve with note 1615838 - SAP Netweaver Enterprise Portal 7.3 iView creation with BI 4.0 results in exceptions.
The note includes a file portalapp.xml that need to be inserted into com.sap.businessobjects.iviews.par that is included in the BI server distribution.
Then deploy the ear file.....
Odd thing is that the note mentions 4.0 and we are on 4.1 SP3...
Environment
SAP BusinessObjects BI Platform 4.0 SP02 Patch 4 or lower
SAP Netweaver Enterprise Portal 7.3
Lee Lewis

Error on update of document stored in content server

Error on update of document stored in content server
On a regular basis (but not reproducible) we find that after updating a document, it is deleted from content server (or at least it cannot be retrieved). These problems have only been experienced since we switched to using content server as our storage repository, as opposed to R/3.
We create and maintain documents through a bespoke transaction, which calls standard SAP functions BDS_BUSINESSDOCUMENT_CREA_TAB and cl_bds_document_set=>update_with_table.
Whilst the errored documents are listed in the BDS via transaction OAOR (business document navigator), an error is received when you try to display it (in our case an MS-Word error indicating file/pathname invalid).
We are satisfied that file/pathname are valid and find that this occurs occasionally when a document has been updated. It appears that the document has been deleted.
This bespoke transaction has been running successfully for almost two years, and these problems have only been experienced after switching to content server as a storage repository (as opposed to R3 previously). Has anyone else experienced these problems?
We are running :
R/3 Enterprise 620,
SAP HTTP Content Server Version 6.30 Patch 13
SAPDB version 7.3.0.54

Hi Sonny,
To check the connectivity between your content server and Workstation and SAP Server.
Pls goto the command prompt of your workstation
give the command like this example.
C:\>Ping 117.123.45.201
you will get the reply from the server. here 117.123.45.201 is your content server IP.
If you are getting the reply then it means that your contentserver and workstation are connected propely.
Like that pls check the connectivity between your systems.
Pls check the hosts file of your systems also.
If the hosts file entry is not maintained, you can check-out file from content server but you cannot check-in the original.
Pls let me know what kind of error Message you are getting?
From where you are trying to check-in the Original? From the DIR screen or from CAD Desktop screen?
Regards,
MRK
(reward points if useful)

Error in "Maintain Performance Documents" Iview

Similar Messages

Maybe you are looking for