Error In ESS personal Data View

Dear All,
I am facing an Issue in ESS .
When I click on Personal Information Page--> Personal Data and click on the Edit button I am able to edit my own data.
When i Click on the Exit button present there, the current window is not returning back to the Personal Information Over View page.. Insetad a new window is opened displaying the Personal Information Page.
Kindly help me in solving this isse.
Thanks and Regards
Siva

Hi Shiv,
This issue of new window will occur not only in Personal Data , but in other ess services as well. There is a setting which you have to maintain called the Wworkprotect mode.
For a single user it is ,
click the personalise link in the right hand top corner after logging into the portal.You will find an option called 'Work protect mode' in the Left hand side of the 'personalize' window. choose any of the radio button suitable for you. In this case, choose 'open in the same window'. and save it.Relogin to the portal to see the change.
For all users, you can make a general setting
Go to Sysytem Adminstration -> System Configuration -> Service Configuration -> Expand Application -> Expand com.sap.portal.epcf.loader -> Exapnd Service -> open epcfloader.Change the property Workprotect.mode.default to 2.
Right Click com.sap.portal.epcf.loader -> click on Adminstrate -> Click on Restart.
You can also refer to note - 734861
Regards
Reshma

Similar Messages

ESS Error when updating personal data

Hi all,
I am running into a problem from ESS when I try to update the personal data I get the following error message:
Data record 010000150002 9999123119500601000 has grouping value "" instead of "10"
I can translate the values in the massage:
01000015 is the PERNR
0002 is the infotype being updated
the space represents the subtype (there is no subtype)
99991231 is the BEGDA
19500601 is the date of birth
I have no idea what the 000 are
This is US employee so the number 10 is the country code for the USA
The value in doble quotes shows that the country grouping must be empty, but I have no idea how to solve this.
I have checked the configuration and it has the country grouping 10 and the employee master record belongs to the US.
Any help will be really appreciated.

Hi,
This problem happens because of some inconsistensies . Please run the report 'RPUFIXDS' , specify the pernr which you are using,
then uncheck 'Test Run' Run the report after these settings are done.That should resolve your issue.
please refer note number : 783499
Regards,
Sharadha

Error while creating Personal data

Hi All,
I do not belong to SAP HR area , i was creating Personal data using PA30 ..here on entering First name & last name , on saving i get the below erro :
Entry does not exist - check your entry
Message no. 00 058
Diagnosis
Input values must be defined in Table V_T522G. The value or values ' ' are not specified in this table.
Procedure
Check whether the input is correct and correct if necessary.
Procedure for System Administration
If this is not an incorrect entry, check the system settings and change them if necessary.
If there is a connection to the Customizing system, you can maintain the system settings by choosing Maintain entries (F5)
I followed the error and have gone to view V_T522N_A and made some entries .. but still i get the same above error .
Note : I am getting the above error for a particular personnel area assigned to country code 29 ..
Provide some inputs on the above.
Regards
pushpa

Hi Pushpa,
This might be because of blank value in field P0002-ANRED. Field 'Title' in infotype 0002 for Argentina is mandatory, so it should not be hidden.
Anyway, as a workaround for your requirement, by creating a empty entry in T522G the issue should be solved.
e.g. create an entry just with Gender '1'. Once that entry is created, then modify it by deleting the gender value, therefore that entry is empty in all the fields.
Anyway, this is a workaround. It is not possible to hide Title field for Argentina.
Regards,
Li

Hide or remove delete button - ESS personal data iView

Hi, regarding for example ESS(50.4) personal data overview iView.
How to hide or remove delete button in the personal data overview iView screen(I know that this can be done on the ITS server side (web studio), but I want to do this in R3)
/Best Regards
Patrick

Achim was right on. Edit/Change the Internet Service in R/3. A few things to consider though....
(1) if using the original service, you may want to create a copy of theme 99 into your own theme (any number will do...99 is just the default theme). If doing so, be sure to change the service's service file (yeh, I always loved that about SAP's naming) to point the ~theme paramter to your new theme.
or
(2) Copy the entire service into your own "Z" service. Then modify the templates as you wish. You will need to point the iView to this "Z" service too.
Also, it is best to do it via SE80 vs. file level because then it will be part of a transport and follow the correct path through the landscape.
Now, if you really want to go back to R/3....find the function module or program the transaction code for your service actually calls, make a "Z" version of it, modify it, create your own "Z" t-code to call it, and THEN modify the internet service's service file (either the original SAP one or a custom version) to call your new "Z" t-code. Lot of work...yes, I know....but that's the way it's done if you gotta get back down to the ABAP level.
Hope this helps!
Message was edited by: Christopher Solomon

Changes to the ESS Personal Data iview

Hi There
With regard to the 'Personal Data' iview on ESS.
I have a scenario where fields marked as REQUIRED are DISABLED.
How do i enable them ?
When trying to change the field configuration by previewing the Personal Data iview and then doing 'control + right click' on the relevant disabled field the changes DO NOT take effect.
When changing an enabled field the change take effect.
Any ideas as to what may be causing this ?
Any advice with regard to resolving this issue will be appreciated.

Hi,
The ESS/MSS fields can be enabled/disabled from spro settings at the backend.
Please check with HR consultant to see the status of that field.
The pathmay be:
>Personnel Management > personnel administration > own data > personal data
Thanks
Muthukumar

US employee getting error in ESS when accessing 'view my benefits'

Hello All,
We are facing a problem with Benefits on ESS. An employee was divorced so he removed his spouse from benefits coverage. Infotype 21, subtype 1 (spouse) record was delimited as of 4/30/2011 and infotype 21, subtype 10 (ex spouse) was created effective 5/1/2011. New infotype 167 records were created effective 5/1/2011 and the spouse was not covered.
Now the employee is getting an error when trying to access the 'view my benefits' app. The first line indicates a problem determining the infotype 21, subtype 1. If I extended the infotype 21, subtype 1 record to the end of time (instead of being delimited), it resolved the error. However, we don't want that record to be valid to the end of time because then the system allows the 'spouse' to be convered by the employee's insurance even though they are divorced.
Further, this issue is being faced only for this employee. I have checked all the settings and have found nothing different.
The Error on the portal is as:
"A critical error has occured. Processing of the service has been terminated. Unsaved data has been lost.
Please contact your system administrator.
Details cannot be determined for related person 1/ "
Please help.
-Amitesh
Edited by: Amitesh Asthana on May 23, 2011 4:47 PM

I checked ST22 but found no dumps.
The error log is as below.
com.sap.pcuigp.xssfpm.java.FPMRuntimeException: Details cannot be determined for related person 1/
                at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:112)
                at com.sap.xss.hr.ben.FcBenefits.reportRFCError(FcBenefits.java:1374)
                at com.sap.xss.hr.ben.FcBenefits.reportRFCError(FcBenefits.java:1340)
                at com.sap.xss.hr.ben.FcBenefits.callRFCParticipation(FcBenefits.java:1135)
                at com.sap.xss.hr.ben.FcBenefits.readParticipation(FcBenefits.java:609)
                at com.sap.xss.hr.ben.wdp.InternalFcBenefits.readParticipation(InternalFcBenefits.java:3552)
                at com.sap.xss.hr.ben.FcBenefitsInterface.readParticipation(FcBenefitsInterface.java:392)
                at com.sap.xss.hr.ben.wdp.InternalFcBenefitsInterface.readParticipation(InternalFcBenefitsInterface.java:1121)
                at com.sap.xss.hr.ben.wdp.InternalFcBenefitsInterface$External.readParticipation(InternalFcBenefitsInterface.java:1317)
                at com.sap.xss.hr.ben.participation.VcBenefitsParticipation.onBeforeOutput(VcBenefitsParticipation.java:205)
                at com.sap.xss.hr.ben.participation.wdp.InternalVcBenefitsParticipation.onBeforeOutput(InternalVcBenefitsParticipation.java:264)
                at com.sap.xss.hr.ben.participation.VcBenefitsParticipationInterface.onBeforeOutput(VcBenefitsParticipationInterface.java:129)
                at com.sap.xss.hr.ben.participation.wdp.InternalVcBenefitsParticipationInterface.onBeforeOutput(InternalVcBenefitsParticipationInterface.java:132)
                at com.sap.xss.hr.ben.participation.wdp.InternalVcBenefitsParticipationInterface$External.onBeforeOutput(InternalVcBenefitsParticipationInterface.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.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:783)
                at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
                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: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:869)
                at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229)
                at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1346)
                at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
                at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
                at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:193)
                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:783)
                at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
                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:149)
                at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
                at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doGet(DispatcherServlet.java:46)
                at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
                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)
                at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Thank you.
-Amitesh
Edited by: Amitesh Asthana on May 23, 2011 4:57 PM

Error in ESS Personal information on deployment of ess/per.ear

Dear Gurus,
we have configure NWDI on our development server. we successfully checkout ess/in/bank application and made changes to a lable UI element to notice it on our server. since it refers to ess/per application, we check-out that too and deployed by right click--> deploy on the sandbox server(not dev server by normal route of check-in).
after successful deployment all personal information services address, bank e.t.c are not working properly.
Please suggest what to do.
shall I copy the ess/per.ear file from dev to sandbox ?
regards,
Ankur

Detailed error log is:
Exception occured during processing of Web Dynpro application sap.com/essinfam/Per_Family_IN. The causing exception is nested.
[EXCEPTION]
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create delegate for component com.sap.xss.hr.per.in.family.overview.VcPerFamilyINOverview. (Hint: Is the corresponding DC deployed correctly? Does the DC contain the component?)
at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:110)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.<init>(DelegatingComponent.java:51)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:382)
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.createVACComponentUsage(FPMComponent.java:747)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:563)
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:783)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
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: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:869)
at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1346)
at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:595)
at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:867)
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.doApplicationProcessing(ClientSession.java:712)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
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:219)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:80)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:44)
at java.lang.reflect.Constructor.newInstance(Constructor.java:315)
at com.sap.tc.webdynpro.progmodel.generation.ControllerHelper.createDelegate(ControllerHelper.java:74)
... 57 more
Caused by: java.lang.UnsupportedClassVersionError: (com/sap/xss/per/model/mac/Hrxss_Per_Subtype_Info) bad major version at offset=6
at java.lang.ClassLoader.defineClassImpl(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:254)
at com.sap.engine.services.deploy.server.ApplicationLoader.defineClassWithInterception(ApplicationLoader.java:168)
at com.sap.engine.services.deploy.server.ApplicationLoader.loadLocalClass(ApplicationLoader.java:140)
at com.sap.engine.frame.core.load.ReferencedLoader.loadRefClass(ReferencedLoader.java:573)
at com.sap.engine.core.classload.impl0.LoaderInfo.loadClassByReference(LoaderInfo.java:34)
at com.sap.engine.frame.core.load.ReferencedLoader.loadClassByReference(ReferencedLoader.java:301)
at com.sap.engine.frame.core.load.ResourceLoader.loadClass(ResourceLoader.java:119)
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:365)
at java.lang.Class.forNameImpl(Native Method)
at java.lang.Class.forName(Class.java:119)
at com.sap.xss.hr.per.in.family.overview.wdp.InternalVcPerFamilyINOverview.<init>(InternalVcPerFamilyINOverview.java:47)
... 62 more

Error in ESS Personal Information

Hi ALL,
When I click on Address Tab under personal Information, I am getting this exception
com.sap.dictionary.runtime.DdException: Type com.sap.xss.per.model.mac.types.Hrxss_Per_Subtype_Allowed does not exist
Please provide your inputs
Thanks
Rishi

Goto SPRO -> Personnel Management -> ESS -> Owndata -> Change Application Case and Subtype and set the UseCase for Subtypes of the Infotypes...Let me know if it helps..

Error when create Personal data

Hi Experts,
I am creating Personnal in HR and using T.Code PA30. When i save it then having issue below.
Error in the ABAP Application Program
The current ABAP program "SAPLHRP3" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "/1PAPA/FEAT000PINCH " in
include "/1PAPA/FEAT000PINCH " in
line 0:
"The program "/1PAPA/FEAT000PINCH" is not Unicode-compatible, according"
" to its program attributes."
The include has been created and last changed by:
Created by: "DDIC "
Last changed by: "DDIC "
please tell me How to solves it.
Thanks very much.
Dungnv

Hi,
Check the consistency of feature PINCH using PE03 by displaying it first and then pressing Cntrl+F2 and if it is error free then activate it.
cheers
Ajay

COBRAS Data Viewer error 3709

Hey guys --
I am currently getting an error while running COBRAS Data Viewer, as soon as I run the application and select the database that I exported, I get the following error:
(error): 3709 (The connection cannot be used to perform this operation. It is either closed or invalid in this context.) in procedure listHandlers_Click of From frmMain
I have to click 'OK' couple times to clear the message. Then everytime I select a subscriber, the same error appears.
Any thoughts?
Thanks,
Ohamien

hmmm... I'm running build 25 as well and I just opened several 7.1(3) backups I have - no problems. Can you select the "Backup Details" option
and post for me the details it kicks out for your backup? i'm guessing the backup was made with an older version of Export and a column name it's expecting to be there in the backup is not - i'll need to add logic so "if version is less than X" it doesn't attempt to fish that value.

Validation in Personal Data application of standard ESS

Hi expert,
I want put some validation on standard ESS personal data application.I have imported the DC and create project with the it.
But now I am unable to understand how to implement the validation. I want to put validation on First Name & Last Name as it is accepting Nos also.
I want this to accept only Characters.
Please teel me where and how to put the validation.
Please answer me as early as possible.
Thanks & Regards,
Aniruddha Bhattacharya.

Hi,
Thanks for your reply.
I have the code. My problem is not with the code. I am not able to understand where in standard code in Personal data application I need to write the validation code for First Name or Last Name.
Please suggest me where I need to put the code. Or Is it possible to do the validation part from BADI HRPAD00INFTYUI.
please help me.
Regards
Aniruddha

Bringing additional field in "Personal Data" iView

Hi All,
This problem might have been discussed on SDN, but I could not locate any concrete solution so posting new question.
We are implementing ESS for multiple countries including US, UK , Japan. Language is english only.
For ESS > Personal Data application, we would like to have Suffix field avaialble on the iView.
There is a field for Suffix in Infotype 0002, but there is no field on the iView.
Questions are :
(1) How this can be brought in the iView?
(2) Can this be done using any configuration or need customization using NWDI ?
(3) Does a single process or config will make it available in iViews of all countries?
Thanking in anticipation.
Regards,
Rajesh

Hi Rajesh
Each ESS service is country specific therefore it has to be customizied by country
Regarding adding fields you would normally do this by "Inserting a child" into the relevant views transparent container
- modifying by NWDS is only part of the customization - you still need to ensure the model recognises the
field and passes values to and from the Portal with the correct business logic
I also found the following which may be of interest -->
https://wiki.sdn.sap.com/wiki/pages/viewpage.action?spaceKey=profile&title=ESSPersonalInformationUIenhancementwithoutmodification&decorator=printable
Best wishes
Stuart

Personal Data - Field value PERID deleted when saving

Hi,
When the user updates the personal data view in ESS the field Social Security - PERID gets updated with blank value (i.e. if you only change nationality or any other field). I'm not sure what is causing this, I'm not getting the same problem when updating the infotype directly in the backend.
Does anyone know what might be causing this?
BR Olof

Exactly!!! This was it.
Thanks for helping out.
Br Olof

Error in Editing the ESS Spain Personal Data

Hello,
We have an ESS global application and which Editing the Personal Information for Spain, we get a dump as given below. we have used the standard SAP implementation for Spain.
Error Description :
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
     at java.util.ArrayList.RangeCheck(ArrayList.java:507)
     at java.util.ArrayList.get(ArrayList.java:324)
     at com.sap.tc.webdynpro.progmodel.context.Node$ElementList.getElement(Node.java:2028)
     at com.sap.tc.webdynpro.progmodel.context.Node.getElementAtInternal(Node.java:621)
     at com.sap.tc.webdynpro.progmodel.context.Node.getElementAt(Node.java:628)
     at com.sap.xss.per.fc.persinfo.FcPersInfo.getSubtypevalue(FcPersInfo.java:2210)
     at com.sap.xss.per.fc.persinfo.wdp.InternalFcPersInfo.getSubtypevalue(InternalFcPersInfo.java:968)
     at com.sap.xss.per.fc.persinfo.FcPersInfoInterface.getSubtypevalue(FcPersInfoInterface.java:388)
     at com.sap.xss.per.fc.persinfo.wdp.InternalFcPersInfoInterface.getSubtypevalue(InternalFcPersInfoInterface.java:357)
     at com.sap.xss.per.fc.persinfo.wdp.InternalFcPersInfoInterface$External.getSubtypevalue(InternalFcPersInfoInterface.java:593)
     at com.sap.xss.hr.per.es.personal.overview.VcPerPersonalESOverview.onEvent(VcPerPersonalESOverview.java:208)
     at com.sap.xss.hr.per.es.personal.overview.wdp.InternalVcPerPersonalESOverview.onEvent(InternalVcPerPersonalESOverview.java:245)
     at com.sap.xss.hr.per.es.personal.overview.VcPerPersonalESOverviewInterface.onEvent(VcPerPersonalESOverviewInterface.java:115)
     at com.sap.xss.hr.per.es.personal.overview.wdp.InternalVcPerPersonalESOverviewInterface.onEvent(InternalVcPerPersonalESOverviewInterface.java:124)
     at com.sap.xss.hr.per.es.personal.overview.wdp.InternalVcPerPersonalESOverviewInterface$External.onEvent(InternalVcPerPersonalESOverviewInterface.java:200)
     at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:534)
     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.es.personal.overview.VcPerPersonalESOverview.edit(VcPerPersonalESOverview.java:248)
     at com.sap.xss.hr.per.es.personal.overview.wdp.InternalVcPerPersonalESOverview.edit(InternalVcPerPersonalESOverview.java:257)
     at com.sap.xss.hr.per.es.personal.overview.BizCardsView.onActionEdit(BizCardsView.java:181)
     at com.sap.xss.hr.per.es.personal.overview.wdp.InternalBizCardsView.wdInvokeEventHandler(InternalBizCardsView.java:220)
     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:332)
     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: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:869)
     at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
     at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1356)
     at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:327)
     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:869)
     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:332)
     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: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:104)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Kindly assist.
Thanks!
Prasanna
Edited by: Prasanna Joshi on May 20, 2011 12:32 AM

Hi Prasanna,
This one is the front end Web Dynpro Java defect. So there wont be anything in the ST22.
Here is the problem you are facing. As its Personal Data application i.e. IT0002, it doesnu2019t have any subtypes. But the code is trying to read the subtypes and its not able to find the records. (Its trying to read the subtypes node, as there is no subtype for PData, you are getting java.lang.IndexOutOfBoundsException: Index: 0, Size: 0)
This is quiet common error, I have seen it couple of times. There should be SAP note for this or raise the ticket to SAP they will fix it.
Itu2019s a simple issue we too can fix it but the correct process is to get it addressed by SAP.
Regards
Yugandhar Reddy

Personal Data and Address for Country Grouping 99 - error on ESS

Hello All,
I have configured personal data and address infotypes in ESS for the country grouping 99.
I have done the following config
1. Assign Screen Structure to Infotype Versions
2. Define Active Subtypes and Use Case
3. Define Country-Specific Applications
4. Created a Z service and then assigned this service to subarea.
I made use of US service and copied to z.
after the config when i log on to the portal and check the personal data or address links am getting the error:
An exception occurred that was not caught., error key: RFC_ERROR_SYSTEM_FAILURE
the st22 dump is
Runtime Errors OBJECTS_OBJREF_NOT_ASSIGNED_NO
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.
I searched in the forum but still am unable to figure it out where i am wrong or missing any config or any other technical error.
Can any one pls help me

http://wiki.sdn.sap.com/wiki/display/ERPHCM/HowtoReuseCountryspecificapplicationsforMolga99
check the steps in above link
and also please check with some standard country like india 40 or usa 10 what use cases and time constraints have been set
INFTY - Now specifies the infotype.
USECASE - Corresponds to the value in the table V_T7XSSPERSUBTYP.
ZEITB - Corresponds to the value in the table V_T591A (V_T582A).
Page 2
SUBTYPE_TAB - Here, you will find a list of the subtypes that have
already been checked and that are correct.
You then find the subtype in METADATA-SUBTY. However, you must move up
one subroutine in the call hierarchy in advance to do this.
This data makes it easy for you to identify the infotype and the subtype
and correct the inconsistency by making entries in the tables mentioned.
ie
T_cd:SE24 >>CL_HRPA_PERNR_INFTY_XSS >> CHECK_USECASE_WITH_CONSTRAINT >>
for
usecase = A1, A4, B1, B4 (table V_T7XSSPERSUBTYP)
you need to have
zeitb = '1' OR zeitb = '2' (table V_T591A)
for
usecase = A2, A3, A5, B2, B3, B5
you need to have
zeitb = '2'
for
usecase = A6, B3
you need to have
Zeitb = '3'

Error In ESS personal Data View

Similar Messages

Maybe you are looking for