Maintaining Infotype 0655 in ESS

I wanted to findout the possibilities of maintaining the Infotype ''0655 - ESS Settings Remuneration Statement'' through ESS, to give an option to the employee to logon to ESS and OPT-OUT the paper statement.
- Do we have this functionality in ESS to pull the Infotype 0655 screen and have the interface with the infotype
- If not, what is the possibility of designing the screen in ESS and have the interface with the infotype ?
- Also please suggest me if there are any best process to handle this. Since, we want to do this through portal, we don't want any manual work on maintaining this infotype.
any suggestion is appreciated. Thanks!

Hi
Please let me know if you have any update on this query.
I am in need of this...
regards

Similar Messages

Getting infotype view in ESS

Dear Friends,
We are using SAP EP 6.0,my SAP ERP ESS 60.2. I would like to know how to get the infotype view in ESS. We would like to know how to get the view of a custom infotype in the personnel information section of ESS. We have created a transactional iview(PA20)and we would like to see only the infotype screen 2000 view instead of PA20 initial screen.
Our requirement is that, we should be able to get the infotype details of the employee who has logged in and not any other employees.
Awaiting your valuable inputs!!
Regards,
Mahesh

Hi Mahesh,
GO to PFCG transaction and look for SAP ESS role in R/3. Add the custom infotype no in the role.
For viewing only the particular user data in the portal, you have to maintain user mapping.
For this logon to portal and go to user administration -> Usermapping. Enter the portal user in the search box and choose user from the dropdown list and select go. The user is displayed. After this select the user and choose the R/3 system from the dropdown list and enter the ESS user name and password in the input box provided and save data.
Now when you logon with the portal user you will be able to view only the mapped user data alone and not other pernr details.
Regards
Arun

Maintaining Infotypes in PP01 for Central Person while already maintained n

Dear Team,
When we are using PP01 Transaction code by taking Object type Central Person system is showing is showing IT0001, IT0002, IT0006 and IT0009 etc. Please let us know the purpose of using all these infotypes as we have already maintained the same in PA30 u2013 Maintain master data
Could you please suggest us whether to update these infotypes here or not and what are implication of the same if we maintain them again here?
Kind Regards
Nagesh

Hi,
When you enter central person and click to see data it takes you to PA30 infotypes and this shows that there is CP-P relation and tells you that link exists from OM to PA for same.
It is sufficient to maintain infotypes in PA30 only as this just shows you linkage nothing more.
Thanks,
Ameet

Idoc - message type to maintain infotype

Hi.
Please, anyone knows the message type to maintain infotype?
Regard Angela

Hi.
How to implement HRMD_A? With an Event?
In other words, If a change in Infotype 0002, when the user save, the idoc start and in bw the infopackage load the data passed by idoc?
Regards
Angela

Maintain Infotype Text using BDC

Hello All,
How to maintain infotype text using BDC (Edit->maintain text).
Thanks,
Rushi

Hi,
First Manually try to do the same activity using SHDB transaction and give the coding part to ABAPER to follow the same to upload the text to infotypes.
Regards
Team Member.

Add Infotype 77 on ESS Screen

Hi,
I am supposed to create the Infotype 77 screeen in WD Java and add it under ESS Personal Info. I do have knowledge in Webdynpro Java but am not updated on FPM. Can some one let me know step by step procedure to accomplish this.
Also I believe there are some RFC's in backend which can be used...
HRXSS_PER_P0077_CA                   ESS PersInfo: Access infotype 0077 CA
HRXSS_PER_EDIT_P0077_CA           Select the given record for edit
HRXSS_PER_MODIFY_P0077_CA      Modify selected record with given record
HRXSS_PER_NEW_P0077_CA           Create new record of given infotype/subtype
HRXSS_PER_READ_P0077_CA          read all records of an infotype relevant for ESS Pers Info
will they all be required to develop each WD FPM screen??
regards
Justin K

Hi,
1st would be
You can develope this application by two ways ....i.e
Webdynpro Java and
Webdynpro ABAP
If you are doing form Webdynpro ABAP then you need to from SE80 ...then form there you need to create Webdynpro application
Then similary it would create the FM for the same ......
in that FM you need to give the following RFC's
HRXSS_PER_P0077_CA ESS PersInfo: Access infotype 0077 CA
HRXSS_PER_EDIT_P0077_CA Select the given record for edit
HRXSS_PER_MODIFY_P0077_CA Modify selected record with given record
HRXSS_PER_NEW_P0077_CA Create new record of given infotype/subtype
HRXSS_PER_READ_P0077_CA read all records of an infotype relevant for ESS Pers Info
Then it will work fine
for more information on ABAP Web Dy Pro you can get it in following ways
http://help.sap.com/saphelp_nw04s/helpdata/en/77/3545415ea6f523e10000000a155106/frameset.htm

Maintaining Infotype 582

Hi Folks,
I have maintained Infotype 582 with begin date as 01.04.2008,
Do we need to Maintain IT 582- subtype EDA, LTA, CEA for all the financial Year or maintaining it with go live year financial year is sufficient. Suppose i have maintaned IT 582 with date 01.04.2008 , i have same exemption this year also, do i need to change it as 01.04.2009. Experts Plz advice.
Rgds,
Sekar.

HI
When I maintain IT 582 subtype MDA, i can key in only start date and there is no end date, u mean to say, every financial year , i need to key in the start date of the financial year.
Rgds,
Sekar.

BAPI to maintain Infotype

Hi,
Does anyone knows what BAPI I can use to perform the same functionality as transaction PSO4 (Maintain Infotype)?
I need to maintain Infotype 1001 via a user exit and is trying to avoid a BDC.
Many thanks,
Lay Guan

Hi Deepika,
pass the FM parameters like this..you will not get the no authorization error..
CALL FUNCTION 'RH_CUT_INFTY_1001_EXT'
          EXPORTING
LOAD                          = 'X'
            GDATE                         = ipspar-begda
            HISTO                         = 'H'
DEL_SUCC                      = ' '
            VTASK                         = 'S'
ORDER_FLG                     = 'X'
COMMIT_FLG                    = 'X'
           AUTHY                         = ' '
PPPAR_IMP                     =
KEEP_LUPD                     =
WORKF_ACTV                    = 'X'
          TABLES
            INNNN                         = PPLOG_TAB
i am hang up here only..i am getting error_during cut...
regards,
Vamshi

How to maintain Employee photo in ESS who's who without sap_all and sap_new

Hi ALL,
Displaying Employee photo in ESS Who's who. it is working but with SAP_ALL and SAP_NEW user profiles.
My requirment is without SAP_ALL and SAP_NEW user profiles. how it is working where can i maintain authorizations for this issue.
The parameter i used are as follows:
Business obj: PREL
Doc type: HRICOLFOTO
Personal num: 00000094
Infotype: 0002
Photo type: .JPG
please help me.
Regaards
Satya.

Dear satya .
Please check the following
1. Trace with the t.code ST01 and check that object require.
2. The portal require the following obect:
S_SERVICE
S_RFC
P_PERNR
PLOG
P_ORGIN/ P_ORGINCON
P_HAP_DOC, if you work with Appraisal Document.
3. Check the table T77S0
P_PERNR, P_ORGIN, y P_ORGINGCON
4. Check that you have the roles need for ESS.
SAP_ESSUSER
SAP_ESSUSER_ERP05
SAP_EMPLOYEE_ERP05
SAP_EMPLOYEE_ERP_13
SAP_EMPLOYEE_ERP05_xx
SAP_EMPLOYEE_ERP_13_xx
5. Check the following notes:
SAP Note 857431 - ESS: Authorizations and roles for WD services in ERP 2005
SAP Note 844639 - MSS: Authorizations and roles for WD services in ERP 2005
SAP Note 1373177 - Back end authorization roles missing in EHP4
SAP Note 824757.
[ESS Quick Start|http://www.cogentibs.com/pdf/cogsap08/ESS.pdf]
Hope is help you.
Regards
consultor_ess_mss

Custom infotype display in ESS ERP 2004

Hi gurus,
The personal information infortype and address infotype of the system has custom fields. In ESS for ERP2004 how do I display these fields in the personal information and address iViews. I guess these do not come by default. Then how do we get them.
Like in IT0002 the clinet has a custom field fathers_name. I know this can be maintained in 0021 but as of now it is in 0002 (i dont know why), so in ESS when i displya personal information iview will this field be displayed automatically. More over this is mandidatory field.
Inputs are highly appreciated.
regards
Sammer

Hi,
Tell me exact fields in Address Infotype then i can tell you what can be done. Is it something you can see on PA30 screen and you dont see it on Address Web Dynpro??
Thanks
Santhosh

Infotypes and subtypes ESS WebDynpro

Hi,
How to find which infotype(and subtype) the specific ESS WebDynpro is storing(retrieving) information from?? There is not much information on ESS Business package or help.sap.com. There is not much on Service market place also....
I am also looking for information on all the WebDynpros of ESS Business Package.
Thanks

Hi Santhosh,
If you haven't already looked at it, there is some info available in <a href="http://help.sap.com/saphelp_erp2005/helpdata/en/6a/5bc8a009d54fcaa8e06c826a57253b/content.htm">SAP Help</a>
probably not exactly what you wanted..
Regards,
Suresh Datti

Maintain JCo Destination for ESS on EP 7.0

On Installling ESS Package on EP-7.0 and SAP ECC 6.0
i got following dump on ESS overview page
I have maintained all SAP_R3* JCo Destinations
but for 'SAP_R3_SelfServiceGenerics_MetaData' test and pinging is giving error
test: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
ping: Failed to get JCo destination 'SAP_R3_SelfServiceGenerics_MetaData': Error while obtaining JCO connection.
DUMP-Details--
com.sap.tc.webdynpro.services.exceptions.TypeNotFoundException: type com.sap.pcuigp.xssfpm.wd.model.types.Ext_Service could not be loaded: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
 at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:250)
 at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
 at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:318)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:670)
 at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:233)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:654)
 at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:657)
 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.progmodel.controller.Component.getCustomControllerInternal(Component.java:443)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getController(Component.java:372)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.getPublicInterface(DelegatingComponent.java:181)
 at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetBackendConnectionsController(InternalFPMComponent.java:219)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:208)
 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:429)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:345)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:668)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:268)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:725)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:661)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
 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:739)
 at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:208)
 at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1240)
 at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:340)
 at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:538)
 at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:177)
 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:429)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:345)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:668)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:268)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
 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:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 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.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
 at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:90)
 at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:408)
 at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:354)
 at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:215)
 at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:180)
 at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:87)
 at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:73)
 at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
 at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
 at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
 at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
 ... 62 more
Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:149)
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:175)
 at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:62)
 at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:77)
 ... 72 more
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve connection parameter for 'SAP_R3_SelfServiceGenerics_MetaData'
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:678)
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:508)
 at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:229)
 at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:214)
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:111)
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:147)
 ... 75 more
Caused by: java.lang.NullPointerException
 at java.util.Hashtable.put(Hashtable.java:395)
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter4MsgServerJCODestination(JCOClientConnection.java:588)
 ... 80 more

Message was edited by: Kapil Gupta

hi Kapil,
have you configured the SLD . or try testing the connection fromthe Webdynpro console to the sld.
Its seems that the systems are not accesible through your Jco destinations..
send me wat you have entered the metadata and application data jco detinations..
Regards,
Ramesh

Maintained infotypes for an employee

Hi
please fetch me the aprogramme or trasation code to find infotypes which are maintained toa employee
Thanks in advance
Sri

Hi Sr!^^,
You can check the Program HRPBSUSACTION.
Regards,
Shiv
Edited by: Shivram SAP on Oct 31, 2008 10:29 AM

RFC for Infotype 24 to ESS portal

I am facing one issue related to Qualification in ESS.
hi Experts
When I update Infotype 24 qualification it updates there but it does not update in ESS for only one employee but for others it is working.
Any solution please or can anyone tell me the RFC name for such
Thanks!
Best Regards
Utkarsh Parikh
Edited by: Utkarsh M parikh on Nov 23, 2010 6:17 PM

Hi Utkarsh,
try executing
HRCCE_XSS_SKL_GET_POSTS_REQS
RFC with the pernr of the concerned employee. After that try to see his qualification on ESS portal you must see the updated Info.
Thanks
Surender Dahiya

Infotype Education for ESS

Good afternoon
Does anyone know if there is a service at ESS where they can update the infotype 22 Education for ESS. And That can do?
The best Regards

There is none as of now.. you have to go in a for a custom iView via BSP/WDJ/WDA.. I would suggest you go in for WebDynpro ABAP..
~Suresh

Maintaining Infotype 0655 in ESS

Similar Messages

Maybe you are looking for