cancel
Showing results for 
Search instead for 
Did you mean: 

Leave request Error

pbechani
Participant
0 Kudos

When I try to access the leave request on the ESS business package (BP ERP05 ESS 1.0) on the portal(7.0) I get the following error

com.sap.tc.webdynpro.progmodel.context.ContextConfigurationException: DataNodeInfo(FcForm.Orig_Request.Item_to_Check_Orig): structure field Umskd not found

at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:299)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:687)

at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:238)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:671)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)

at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:674)

at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)

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

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

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:940)

at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createComponent(ClientComponent.java:177)

at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponentInternal(ComponentUsage.java:149)

at com.sap.tc.webdynpro.progmodel.components.ComponentUsage.createComponent(ComponentUsage.java:141)

at com.sap.pcuigp.xssfpm.wd.FPMComponent$ComponentUsageManager.createBLCComponentUsage(FPMComponent.java:761)

at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920)

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.hr.lea.blockcale.VcBlockCale.onInit(VcBlockCale.java:254)

at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCale.onInit(InternalVcBlockCale.java:275)

at com.sap.xss.hr.lea.blockcale.VcBlockCaleInterface.onInit(VcBlockCaleInterface.java:163)

at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCaleInterface.onInit(InternalVcBlockCaleInterface.java:144)

at com.sap.xss.hr.lea.blockcale.wdp.InternalVcBlockCaleInterface$External.onInit(InternalVcBlockCaleInterface.java:220)

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.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.wdDoRefresh(PageBuilder.java:592)

at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:864)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)

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.doApplicationProcessing(ClientSession.java:684)

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(AccessController.java:215)

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

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

Is there anything I need to configure

Regards,

Accepted Solutions (0)

Answers (3)

Answers (3)

pbechani
Participant
0 Kudos

the problem was with Jco Connections

Former Member
0 Kudos

Hi

You should also look at the below Forum node

[]

Thanks,

SJ

dsharmak
Advisor
Advisor
0 Kudos

Dear Bechani,

Make sure that you upgrade your backend to HD23!

****************************************************************

Upgrading to ERP Stack-11 would mean upgrading the EA-HR 6.00 to Support

Package 22(i.e, SAPKGPHD22).

This might lead to error while accessing the ESS: Leave Request Scenario

because the ERP Stack-11 would have brought in the frontend changes and

not the backend changes. The error text will read as

"Webdynpro Context Configuration Exception:

Page 2

DataNodeInfo(FcForm.Orig_Request.Item_to_Check_Orig): structure field

Umskd not found".

Hence, it is mandatory to apply the .SAR file(Leave_Request_600.SAR)

attached with this note. Please apply this .SAR File ONLY after

upgrading to ERP Stack-11 so that the ESS: Leave Request Scenario runs

without any errors. This .SAR file has the backend changes of the

development mentioned above.

*************************************************************

DataNodeInfo(FcForm.Orig_Request.Item_to_Check_Orig): structure field

Umskd not found".

Hence, it is mandatory to apply the .SAR file(Leave_Request_600.SAR)

attached with this note. Please apply this .SAR File ONLY after

upgrading to ERP Stack-11 so that the ESS: Leave Request Scenario runs

without any errors. This .SAR file has the backend changes of the

development mentioned above.

*************************************************************

Ie You need to apply the Sar file for backend changes

after you have upgraded the front end package.

Also note that :

If you are already on the Support Package HD23 in backend (EA HR)

and front end is SP13, Then the application should work, Please

ensure you restart the Java engine and test the application again

This is a mandatory step to be performed.

Also please check the note 1058240 is this regard.

Hope this should help.

Best Regards,

Deepak...

pbechani
Participant
0 Kudos

Hi Deepak

Thank you for the information. We are currently implementing support stack upgrade. As soon as we are through, I will give you feedback

Regards