on 11-08-2007 4:49 PM
Hello everyone:
I am trying to update my personal data through ESS. I can retrieve the data successfully. But I was not able to update data. Do I have missing any in JCO destination or any where else.?
Please help me.
Thanks
-Ozzie
Here is the dump message from the portal:
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: The current application triggered a termination with a short dump., error key: RFC_ERROR_SYSTEM_FAILURE
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
at com.sap.xss.hr.cod.FcCodBusinessLogicComp.callRFCSaveDetails(FcCodBusinessLogicComp.java:386)
at com.sap.xss.hr.cod.FcCodBusinessLogicComp.saveEmployeeData(FcCodBusinessLogicComp.java:268)
at com.sap.xss.hr.cod.wdp.InternalFcCodBusinessLogicComp.saveEmployeeData(InternalFcCodBusinessLogicComp.java:378)
at com.sap.xss.hr.cod.FcCodBusinessLogicCompInterface.saveEmployeeData(FcCodBusinessLogicCompInterface.java:146)
at com.sap.xss.hr.cod.wdp.InternalFcCodBusinessLogicCompInterface.saveEmployeeData(InternalFcCodBusinessLogicCompInterface.java:159)
at com.sap.xss.hr.cod.wdp.InternalFcCodBusinessLogicCompInterface$External.saveEmployeeData(InternalFcCodBusinessLogicCompInterface.java:227)
at com.sap.xss.hr.cod.displaynavigation.VcCodDisplayNavigationComp.onEvent(VcCodDisplayNavigationComp.java:271)
at com.sap.xss.hr.cod.displaynavigation.wdp.InternalVcCodDisplayNavigationComp.onEvent(InternalVcCodDisplayNavigationComp.java:181)
at com.sap.xss.hr.cod.displaynavigation.VcCodDisplayNavigationCompInterface.onEvent(VcCodDisplayNavigationCompInterface.java:115)
at com.sap.xss.hr.cod.displaynavigation.wdp.InternalVcCodDisplayNavigationCompInterface.onEvent(InternalVcCodDisplayNavigationCompInterface.java:124)
at com.sap.xss.hr.cod.displaynavigation.wdp.InternalVcCodDisplayNavigationCompInterface$External.onEvent(InternalVcCodDisplayNavigationCompInterface.java:200)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:533)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:437)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.access$600(FPMComponent.java:78)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.raiseSaveEvent(FPMComponent.java:951)
at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.raiseSaveEvent(FPMComponent.java:1114)
at com.sap.xss.hr.cod.displaynavigation.VcCodDisplayNavigationComp.toSave(VcCodDisplayNavigationComp.java:306)
at com.sap.xss.hr.cod.displaynavigation.wdp.InternalVcCodDisplayNavigationComp.toSave(InternalVcCodDisplayNavigationComp.java:193)
at com.sap.xss.hr.cod.displaynavigation.DisplayNavigationView.onActionSave(DisplayNavigationView.java:153)
at com.sap.xss.hr.cod.displaynavigation.wdp.InternalDisplayNavigationView.wdInvokeEventHandler(InternalDisplayNavigationView.java:183)
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:313)
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.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1257)
at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:325)
at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:826)
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:313)
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:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.aii.proxy.framework.core.BaseProxyException: The current application triggered a termination with a short dump., error key: RFC_ERROR_SYSTEM_FAILURE
at com.sap.aii.proxy.framework.core.AbstractProxy.send$(AbstractProxy.java:150)
at com.sap.xss.hr.cod.model.CodModel.hrxss_Cod_Save_Details(CodModel.java:246)
at com.sap.xss.hr.cod.model.Hrxss_Cod_Save_Details_Input.doExecute(Hrxss_Cod_Save_Details_Input.java:137)
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
... 65 more
goto R/3 and run st22 and send the dump asap please.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Barin,
I am also facing the same issue. Following is the short dump. Please let me know what to do resolve the issue.
Runtime Errors UNCAUGHT_EXCEPTION
Exception CX_HRPA_INVALID_SUBTYPE
Date and Time 01/10/2008 09:44:24
Short text
An exception occurred that was not caught.
What happened?
The exception 'CX_HRPA_INVALID_SUBTYPE' was raised, but it was not caught
anywhere along
the call hierarchy.
Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program
'CL_HRPA_READ_TIMECONSTRAINT===CP' has to be
terminated.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_HRPA_INVALID_SUBTYPE', was not
caught in
procedure "HRXSS_COD_SAVE_PERSONAL_DATA" "(FUNCTION)", nor was it propagated by
a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
Subtype 0005 Not Permitted for Infotype 0105 &TCLAS&
How to correct the error
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"UNCAUGHT_EXCEPTION" "CX_HRPA_INVALID_SUBTYPE"
"CL_HRPA_READ_TIMECONSTRAINT===CP" or "CL_HRPA_READ_TIMECONSTRAINT===CM002"
"IF_HRPA_READ_TIMECONSTRAINT~COMPUTE_TIMECONSTRAINT"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
The exception must either be prevented, caught within proedure
"HRXSS_COD_SAVE_PERSONAL_DATA" "(FUNCTION)", or its possible occurrence must be
declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
System environment
SAP-Release 700
Application server... "dr3-da-1"
Network address...... "10.130.83.52"
Operating system..... "HP-UX"
Release.............. "B.11.23"
Hardware type........ "ia64"
Character length.... 8 Bits
Pointer length....... 64 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... "dr3-da-1"
Database type..... "ORACLE"
Database name..... "DS2"
Database user ID.. "SAPR3"
Char.set.... "en_US.iso88591"
SAP kernel....... 700
created (date)... "Jun 10 2007 21:34:50"
create on........ "HP-UX B.11.23 U ia64"
Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 114
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "HP-UX B.11"
User | Count |
---|---|
100 | |
12 | |
11 | |
6 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.