Skip to Content
avatar image
Former Member

ESS Travel Exception after Portal Patching

Hello Everyone,

We have recently upgraded the portal from SP14 to SP17. So, this resulted in Various Software components like ESS are patched as well. But, in our old ESS track we have done lot of customisation to the Travel iViews. So, when we have patched ESS, it is really annoying that we have to make all the customisation manually again in the new ESS track. We have followed the "NWDI Cookbook for XSS/ESS" after patching as well. But, it is of no use.

Now, we have done all the customisation manually again to the new track and the strangest thing is we are getting a completely irrelevant Exception as given below. We have not even touched that DC and it is throwing an exception. We are very surpised with all these complexeties. Can anyone help me in resolving these two questions? I am completely fed up searching on SDN to resolve these 2 issues and have given up now.

com.sap.tc.webdynpro.progmodel.context.ContextConfigurationException: MappedAttributeInfo(FcTreReceipts.Customizing.E_Jurcodes_External): mapped attribute E_Jurcodes_External not found
	at com.sap.tc.webdynpro.progmodel.context.MappedAttributeInfo.initNodeMapping(MappedAttributeInfo.java:377)
	at com.sap.tc.webdynpro.progmodel.context.MappedAttributeInfo.init(MappedAttributeInfo.java:281)
	at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initMappedAttributes(NodeInfo.java:699)
	at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAfterCompletedMapping(NodeInfo.java:705)
	at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:87)
	at com.sap.tc.webdynpro.progmodel.context.MappingInfo.getDataNode(MappingInfo.java:69)
	at com.sap.tc.webdynpro.progmodel.context.Node.getDataNode(Node.java:1684)
	at com.sap.tc.webdynpro.progmodel.context.Node.isValid(Node.java:368)
	at com.sap.tc.webdynpro.progmodel.context.Node.getElementList(Node.java:344)
	at com.sap.tc.webdynpro.progmodel.context.Node.getElements(Node.java:333)
	at com.sap.tc.webdynpro.progmodel.context.Node.getElementAtInternal(Node.java:615)
	at com.sap.tc.webdynpro.progmodel.context.Node.getCurrentElementInternal(Node.java:868)
	at com.sap.tc.webdynpro.progmodel.context.Node.getCurrentElement(Node.java:875)
	at com.sap.xss.tra.tre.fc.receipts.wdp.IPublicFcTreReceipts$IContextNode.currentCustomizingElement(IPublicFcTreReceipts.java:2274)
	at com.sap.xss.tra.tre.fc.receipts.FcTreReceipts.onEventCustomizingChanged(FcTreReceipts.java:1406)
	at com.sap.xss.tra.tre.fc.receipts.FcTreReceipts.onInit(FcTreReceipts.java:475)
	at com.sap.xss.tra.tre.fc.receipts.wdp.InternalFcTreReceipts.onInit(InternalFcTreReceipts.java:3322)
	at com.sap.xss.tra.tre.fc.receipts.FcTreReceiptsInterface.onInit(FcTreReceiptsInterface.java:161)
	at com.sap.xss.tra.tre.fc.receipts.wdp.InternalFcTreReceiptsInterface.onInit(InternalFcTreReceiptsInterface.java:299)
	at com.sap.xss.tra.tre.fc.receipts.wdp.InternalFcTreReceiptsInterface$External.onInit(InternalFcTreReceiptsInterface.java:427)
	at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:922)
	at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:891)
	at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1084)
	at com.sap.xss.tra.tre.vc.receipts.VcTreReceipts.onInit(VcTreReceipts.java:255)
	at com.sap.xss.tra.tre.vc.receipts.wdp.InternalVcTreReceipts.onInit(InternalVcTreReceipts.java:412)
	at com.sap.xss.tra.tre.vc.receipts.VcTreReceiptsInterface.onInit(VcTreReceiptsInterface.java:122)
	at com.sap.xss.tra.tre.vc.receipts.wdp.InternalVcTreReceiptsInterface.onInit(InternalVcTreReceiptsInterface.java:124)
	at com.sap.xss.tra.tre.vc.receipts.wdp.InternalVcTreReceiptsInterface$External.onInit(InternalVcTreReceiptsInterface.java:200)
	at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:564)
	at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
	at com.sap.pcuigp.xssfpm.wd.FPMComponent.access$600(FPMComponent.java:78)
	at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.raiseEvent(FPMComponent.java:938)
	at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.raiseEvent(FPMComponent.java:1101)
	at com.sap.xss.tra.tre.vc.generaldata.VcTreGeneralData.raiseFPMEvent(VcTreGeneralData.java:463)
	at com.sap.xss.tra.tre.vc.generaldata.wdp.InternalVcTreGeneralData.raiseFPMEvent(InternalVcTreGeneralData.java:589)
	at com.sap.xss.tra.tre.vc.generaldata.GeneralDataView.onActionNextStep(GeneralDataView.java:673)
	at com.sap.xss.tra.tre.vc.generaldata.wdp.InternalGeneralDataView.wdInvokeEventHandler(InternalGeneralDataView.java:674)
	at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
	at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
	at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
	at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
	at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
	at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
	at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
	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)

I would be very thankful if someone could help me in resolving this issue. I would appreciate your help.

Regards,

Gopal.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Mar 20, 2009 at 06:03 AM

    Hello Gopal

    It seems and clear that context mapping is broken.

    1.Do the reimport of all the models/ services for the concerned DC.

    2.Open contexts one by one, find X(red marks) mark for which the mapping is broken.

    It happen that structure field not found, or data type mismatch or some new added field or deleted field etc

    Do these check let us know

    Best Regards

    Satish Kumar

    Add comment
    10|10000 characters needed characters exceeded