We are facing the below error on clicking New spouse / New child or any sub-type under IT0021 in ESS screen.
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException: Type conflict with ASSIGN in program CL_HRPA_UI_CONVERT_0021_US====CP ., error key: RFC_ERROR_SYSTEM_FAILURE
at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:101)
at com.sap.xss.hr.per.us.family.fc.FcPerFamilyUS.newRecord(FcPerFamilyUS.java:256)
at com.sap.xss.hr.per.us.family.fc.wdp.InternalFcPerFamilyUS.newRecord(InternalFcPerFamilyUS.java:823)
at com.sap.xss.hr.per.us.family.fc.FcPerFamilyUSInterface.newRecord(FcPerFamilyUSInterface.java:136)
at com.sap.xss.hr.per.us.family.fc.wdp.InternalFcPerFamilyUSInterface.newRecord(InternalFcPerFamilyUSInterface.java:255)
at com.sap.xss.hr.per.us.family.fc.wdp.InternalFcPerFamilyUSInterface$External.newRecord(InternalFcPerFamilyUSInterface.java:335)
at com.sap.xss.hr.per.us.family.detail.VcPerFamilyUSDetail.onBeforeOutput(VcPerFamilyUSDetail.java:203)
at com.sap.xss.hr.per.us.family.detail.wdp.InternalVcPerFamilyUSDetail.onBeforeOutput(InternalVcPerFamilyUSDetail.java:221)
at com.sap.xss.hr.per.us.family.detail.VcPerFamilyUSDetailInterface.onBeforeOutput(VcPerFamilyUSDetailInterface.java:134)
at com.sap.xss.hr.per.us.family.detail.wdp.InternalVcPerFamilyUSDetailInterface.onBeforeOutput(InternalVcPerFamilyUSDetailInterface.java:132)
at com.sap.xss.hr.per.us.family.detail.wdp.InternalVcPerFamilyUSDetailInterface$External.onBeforeOutput(InternalVcPerFamilyUSDetailInterface.java:208)
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.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.hr.per.us.family.overview.VcPerFamilyUSOverview.create(VcPerFamilyUSOverview.java:223)
at com.sap.xss.hr.per.us.family.overview.wdp.InternalVcPerFamilyUSOverview.create(InternalVcPerFamilyUSOverview.java:293)
at com.sap.xss.hr.per.us.family.overview.BizCardsView.onActionNew(BizCardsView.java:202)
at com.sap.xss.hr.per.us.family.overview.wdp.InternalBizCardsView.wdInvokeEventHandler(InternalBizCardsView.java:252)
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:333)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:192)
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:864)
at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1374)
at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:326)
at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:872)
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:333)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:192)
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:1060)
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:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
And when i check in back end i can see the below dump:
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not caught in procedure "HRXSS_PER_CLEANUP" "(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:
You attempted to use a 'NULL' object reference (points to 'nothing') access a component.
An object reference must point to an object (an instance of a class) before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the CLEAR statement.
Error in the ABAP Application Program
The current ABAP program "CL_HRPA_UI_CONVERT_0021_US====CP" had terminated because it has come across a statement that unfortunately cannot be executed.
In our system, ESSMSS is live for 5 different countries. They are using common ess/mss portal role and also common iviews.
But now we are going live for saudi arabia and as mentioned we had a problem with IT0021 and currently US iview is used, so can i use other country iview for this service. And if i can use some other country iview, then what pre-requisites need to check.
If you are using the USA to Saudi Arabia then you need specify that Saudi Arabia would be using the US structure. You can do this from Spro. ESS=>Service Specific Settings=>Own Data=>Reuse Country Specific Applications=>Assign Screen Structure to Infotype Versons
Assume that there is no data in ECC system for IT0021, then when i click on ESS --> Personal Information --> Family Member/Dependents --> New Spouse (or any subtype) the error is thrown.
Assume that IT0021 contains some data then when i click on ESS --> Personal Information --> Family Member/Dependents the error is thrown.
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
caught in
procedure "HRXSS_PER_CLEANUP" "(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:
You attempted to use a 'NULL' object reference (points to 'nothing')
access a component.
An object reference must point to an object (an instance of a class)
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using the
CLEAR statement.
Information on where terminated Termination occurred in the ABAP program "SAPLHRXSS_PER_MAC" - in "HRXSS_PER_CLEANUP". The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 13 of the (Include) program "LHRXSS_PER_MACU04". The termination is caused because exception "CX_SY_REF_IS_INITIAL" occurred in procedure "HRXSS_PER_CLEANUP" "(FUNCTION)", but it was neither handled locally nor declared in the RAISING clause of its signature.
The procedure is in program "SAPLHRXSS_PER_MAC "; its source code begins in line 1 of the (Include program "LHRXSS_PER_MACU04 ".
Type conflict with ASSIGN in program "CL_HRPA_UI_CONVERT_0021_US====CP".
Error in the ABAP Application Program
The current ABAP program "CL_HRPA_UI_CONVERT_0021_US====CP" had to be terminated because it has come across a statement that unfortunately cannot be executed.
Information on where terminated Termination occurred in the ABAP program "CL_HRPA_UI_CONVERT_0021_US====CP" - in "IF_HRPA_UI_CONVERT_STANDARD~OUTPUT_CONVERSION". The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 23 of the (Include) program "CL_HRPA_UI_CONVERT_0021_US====CM002".
Pls give us the screen shot of the exact code where its terminating as per this error:
termination occurred in the ABAP program "CL_HRPA_UI_CONVERT_0021_US====CP" -
in "IF_HRPA_UI_CONVERT_STANDARD~OUTPUT_CONVERSION".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 23 of the (Include) program "CL_HRPA_UI_CONVERT_0021_US====CM002".
There is some problem in output_conversion, double check it there, but a http break point and see whats going and when its dumping. You should be able to find this from st22 dump too.
In our case we have two screens for Famlily Members / Dependents( infotype 0021 ).
i.e.Primary (0021) and Secondary (3254) infotypes.
So, whenever the date is modified from portal end, there was a mismatch between the primary and secondary infotype dates and the system throws dump during modifcation of date for any sub-type of Family Members / Dependents infotype.
Modified "HRPAD00INFTYUI" Badi to resolve the issue.
We have roll-out our ESS/MSS applications to KSA, and in our case we have two screens for Famlily Members / Dependents( infotype 0021 ).
i.e.Primary (0021) and Secondary (3254) infotypes.
So, whenever the date is modified from portal end on Family Members / Dependents screen, the system throws an expection at HRPAD00INFTYUI Badi.
So, our ABAP consultant had modified HRPAD00INFTYUI badi to overwrite the date at secondary infotype and vice-versa after debugging the badi using various scenarios which solved our issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.