Issue in ESS Portal

After upgrade to EHP 4, we have an issue with portal where initally the Personnel data screen was not modifiable ie Read Only....But now the users are able to edit their information without any error message.
Kindly suggest..how we can make the fields for users of US to be made as Display only for Infotype 2.
and what settings should we do for restricting the users to edit Personnel data.
Awaiting early reply...

Please check the following tables:
V_T7XSSPERBIZFLD
V_T7XSSPERBIZFLC
T588MFPROPC
T588MFPROPS

Similar Messages

ESS Portal Issue

ESS Gurus,
We have a typical ESS issue at one of our cliens in the live system:
The landscape details are as mentioned below:
SAP ECC 6.0 with EHP4
SAP Enterprise Portal 7.0 with JEE:-SP15 & JEECOR:- SP13
We recently upgraded the SAP ECC 6.0 with EHP4 and we have not upgraded the Portal.
Post the upgrade to backend ECC system with EHP4, in the ESS Portal 7.0 we are facing a typical issue while accessing "Personnel Details" as mentioned below:
"Critical Error"
A critical error has occured. Processing the service has to be terminated. Unsaved data has been lost. Please contact your system administrator.
com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:107)
     at com.sap.xss.per.fc.persinfo.FcPersInfo.initPernr(FcPersInfo.java:376)
     at com.sap.xss.per.fc.persinfo.wdp.InternalFcPersInfo.initPernr(InternalFcPersInfo.java:762)
     at com.sap.xss.per.fc.persinfo.FcPersInfoInterface.initPernr(FcPersInfoInterface.java:166)
     at com.sap.xss.per.fc.persinfo.wdp.InternalFcPersInfoInterface.initPernr(InternalFcPersInfoInterface.java:267)
     at com.sap.xss.per.fc.persinfo.wdp.InternalFcPersInfoInterface$External.initPernr(InternalFcPersInfoInterface.java:427)
     at com.sap.xss.hr.per.in.personal.overview.VcPerPersonalINOverview.onInit(VcPerPersonalINOverview.java:295)
     at com.sap.xss.hr.per.in.personal.overview.wdp.InternalVcPerPersonalINOverview.onInit(InternalVcPerPersonalINOverview.java:290)
     at com.sap.xss.hr.per.in.personal.overview.VcPerPersonalINOverviewInterface.onInit(VcPerPersonalINOverviewInterface.java:163)
     at com.sap.xss.hr.per.in.personal.overview.wdp.InternalVcPerPersonalINOverviewInterface.onInit(InternalVcPerPersonalINOverviewInterface.java:144)
     at com.sap.xss.hr.per.in.personal.overview.wdp.InternalVcPerPersonalINOverviewInterface$External.onInit(InternalVcPerPersonalINOverviewInterface.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:748)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:283)
     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:1246)
     at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:547)
     at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:591)
     at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:822)
     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.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: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.tc.webdynpro.services.exceptions.WDRuntimeException: com.sap.xss.per.model.mac.Hrxss_Data_Sharing_Info
Found in negative cache
Loader Info -
ClassLoader name: [sap.com/ess~per]
Parent loader name: [Frame ClassLoader]
References:
   common:service:http;service:servlet_jsp
   service:ejb
   common:service:iiop;service:naming;service:p4;service:ts
   service:jmsconnector
   library:jsse
   library:servlet
   common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl
   library:ejb20
   library:j2eeca
   library:jms
   library:opensql
   common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore
   interface:resourcecontext_api
   interface:webservices
   interface:cross
   interface:ejbserialization
   sap.com/pcui_gp~xssutils
   sap.com/tcwddispwda
   sap.com/pcui_gp~xssfpm
   sap.com/tcwdcorecomp
   service:webdynpro
   service:sld
   library:tcddicddicservices
   library:com.sap.aii.proxy.framework
   library:tcgraphicsigs
   library:com.sap.mw.jco
   library:com.sap.lcr.api.cimclient
   library:sapxmltoolkit
   library:com.sap.aii.util.rb
   library:com.sap.util.monitor.jarm
   library:tcddicddicruntime
   library:com.sap.aii.util.xml
   library:com.sap.aii.util.misc
   library:tc~cmi
Resources:
   /usr/sap/SGP/JC12/j2ee/cluster/server0/apps/sap.com/essper/webdynpro/public/lib/sap.comess~per.jar
   /usr/sap/SGP/JC12/j2ee/cluster/server0/apps/sap.com/ess~per/src.zip
Loading model: {parent,references,local}
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.createNewBaseTypeDescriptor(AiiModelClass.java:422)
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.descriptor(AiiModelClass.java:222)
     at com.sap.xss.per.model.mac.Hrxss_Per_Init_Pernr_Output.<init>(Hrxss_Per_Init_Pernr_Output.java:51)
     at com.sap.xss.per.model.mac.HRXSS_PER_MAC.hrxss_Per_Init_Pernr(HRXSS_PER_MAC.java:457)
     at com.sap.xss.per.model.mac.Hrxss_Per_Init_Pernr_Input.doExecute(Hrxss_Per_Init_Pernr_Input.java:137)
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:92)
     ... 60 more
Caused by: java.lang.ClassNotFoundException: com.sap.xss.per.model.mac.Hrxss_Data_Sharing_Info
Found in negative cache
Loader Info -
ClassLoader name: [sap.com/ess~per]
Parent loader name: [Frame ClassLoader]
References:
   common:service:http;service:servlet_jsp
   service:ejb
   common:service:iiop;service:naming;service:p4;service:ts
   service:jmsconnector
   library:jsse
   library:servlet
   common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl
   library:ejb20
   library:j2eeca
   library:jms
   library:opensql
   common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore
   interface:resourcecontext_api
   interface:webservices
   interface:cross
   interface:ejbserialization
   sap.com/pcui_gp~xssutils
   sap.com/tcwddispwda
   sap.com/pcui_gp~xssfpm
   sap.com/tcwdcorecomp
   service:webdynpro
   service:sld
   library:tcddicddicservices
   library:com.sap.aii.proxy.framework
   library:tcgraphicsigs
   library:com.sap.mw.jco
   library:com.sap.lcr.api.cimclient
   library:sapxmltoolkit
   library:com.sap.aii.util.rb
   library:com.sap.util.monitor.jarm
   library:tcddicddicruntime
   library:com.sap.aii.util.xml
   library:com.sap.aii.util.misc
   library:tc~cmi
Resources:
   /usr/sap/SGP/JC12/j2ee/cluster/server0/apps/sap.com/essper/webdynpro/public/lib/sap.comess~per.jar
   /usr/sap/SGP/JC12/j2ee/cluster/server0/apps/sap.com/ess~per/src.zip
Loading model: {parent,references,local}
     at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:360)
     at com.sap.tc.webdynpro.modelimpl.dynamicrfc.AiiModelClass.createNewBaseTypeDescriptor(AiiModelClass.java:409)
     ... 65 more
Please provide a solution.
Thanks

You have to upgrade your portal and backend to EHP4.
http://wiki.sdn.sap.com/wiki/display/ERPHCM/HOWTOGETRIDOFSPSTACKMISMATCHISSUES

Unable to access the Time Statements in ESS Portal

The user is getting a critical error(com.sap.pcuigp.xssfpm.java.FPMRuntimeException) when trying to access his time statements from ESS portal. The user recently moved to a different country and trying to access statement there. Are there any country specific paramaters that are needed to be changed or set when a employee is reallocated?
Please help me.

Hi Rafi,
We are also facing similar kind of issue.
When i select type of leave as annual it is giving an error message as
" Parameter missing in call of method BUILD_ACTOR_SELECT_CLAUSE in class CA_PT_REQ_ACTOR "
But when i select some other leave type and click review it is working fine, again if i click on previous step and change the leave type to annual it is working fine without giving any error message.
Please let us know how you have solved your issue?
Thanks.
-Suresh

Issue in ESS - Single Signon

Dear All,
EP7.0 SP9, ECC5
We have an major issue in ESS, The problem is with single sign on.
Here are the scenario's we are using :-
1. We are using "training1" as EP login id and in PA30 in R/3 InfoType 105 and Sub Infotype 0001 The same ID "training1" (Same as EP log in), the portal is picking the data properly and working fine.
2. If we use training1 as EP loginID and in PA30 in R/3 InfoType 105 and Sub Infotype 0001 if we use exeibckk (R/3 ID created for each individual user as communication user),
we are getting error "User TRAINING1 does not exist in this period"
we need to go ahead with the Step2, since all the EP login users are LDAP configured and,it has more than 15 characters, we cannot use EP login ID in InfoType 105 and Sub Infotype 0001
since it is restricted to 12 Characters.
e.g:
EP user ID is - shivakumar_ks ( taken from LDAP)
where as his R/3 or ESS user ID is - P000000002
since the login ID and R/3 ID are different,The system is throwing the error mentioned above.
We map the Shivakumar_ks with P000000002 in the EP Personalize option. But it is
not picking up the mapping. It tried to find the Shivakumar_ks in R/3 and fails.
Even though we are giving the UIDPWD in the system Logon Method.
Can anyone please give me the solution on the above.
Thanks in advane
Ponnusamy P

I beleive you know how to map it ABAP UME - any how i enclose the details - may be useful to our friends
Update Host file on Portal server with information of ABAP IP & Host Name
Update Services file on Portal with entry sapms<SID> 36<NR>/tcp
Update Host file on ABAP server with information of Portal Server
Create User ABAP Client with SAP_ALL & record password
On Portal Server
============
Open Configtool from
<DRIVE>:\usr\sap\<SID>\JC<NR>\j2ee\configtool
Expand - Global Service Configuration
Expand - Services
Click - com.sap.security.core.ume.service
In Right Pane - Change the below things
==
1
==
UME_persistence.data_source_configuration
from : dataSourceConfiguration_database_only.xml (default)
to : dataSourceConfiguration_abap.xml
==
2
==
ume.logon.r3.master.adapterid
from : master
to : 001
==
3
==
ume.r3.connection.001.user
from : --
to : <ABAP SUPER USER CREATED>
==
4
==
ume.r3.connection.001.passwd
<PASSWORD OF ABAP USER>
==
5
==
ume.r3.connection.001.ashost
from : --
to : <ABAP SERVER HOSTNAME / FQDN>
==
6
==
ume.r3.connection.001.sysnr
from : --
to : <ABAP INSTANCE NUMBER>
==
7
==
ume.r3.connection.001.client
from : --
to : <ABAP CLIENT>
==
8
==
ume.r3.connection.001.group
from : --
to : <LOGON GROUP DEFAULT is SPACE or any You created >
==
9
==
ume.r3.connection.001.gwhost
from : --
to : <ABAP SERVER HOSTNAME / FQDN>
==
10
==
ume.r3.connection.001.gwserv
from : --
to : sapgw<NR>
==
11
==
ume.r3.connection.001.msghost
from : --
to : <ABAP SERVER HOSTNAME / FQDN>
==
12
==
ume.r3.connection.001.r3name
from : --
to : <ABAP SID>
====
Above Configs Cahnges done as per below link and Note
====
Useful Help Link :
http://help.sap.
com/saphelp_erp2005vp/helpdata/en/49/9dd53f779c4e21e10000000a1550b0/content.htm
Alos Look at Note : SAP Note 718383
Please mark the question answered
Good Luck - Cheers
PR

Error in ESS portal

Hi Gurus,
We have a situation where users are trying to login to ESS portal and we can find below dump at backend in ST22.
Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED_NO
Exception              CX_SY_REF_IS_INITIAL
Access via 'NULL' object reference not possible. The current ABAP program "SAPLHRXSS_PER_MAC" had to be terminated because it has come across a statement that unfortunately cannot be executed.
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.
Can you please throw some light what might be the cause for this error?
Regards,
kitchlu

Hello kitchlu
your issue is usually caused by some missing or improper customizing of backend table V_T7XSSPERSUBTYP.
Please refer to IMG activity below:
Personnel Management -> Employee Self-Service -> Service-Specific Settings -> Own Data -> Define Active Subtypes and Application Case (Maintenance view V_T7XSSPERSUBTYP). Use case for the relevant scenario has to be set to use case starting with A (i.e., use case A1, A2 or A3).
Please refer to the documentation of the field as well as below notes to make sure relevant entries are not missing. Please make sure that the value of them are correct according to above comments:
- 818957 ESS PersInfo: Guide for Configuration of Use Cases
- 818958 ESS PersInfo: Important configuration tables
Thanks and Kind Regards
Ramana

CATS Screen dumps when navigating between prev and foll weeks in ESS portal

The medical leave absence type MEDICAL LEAVE @1/2 PAY(13) is the only allowed by time administrators to enter through transaction CAT2 and not through ESS. Once entered,this appears in your time entry in ESS as a disabled entry. However once you navigate between the previous or the following weeks, after this entry appears in your screen, the screen dumps.
SAP allows this functionality where time entries can be maintained for an employee through CAT2 on ERP side with an absence type not available in ESS portal.
The following is the dump analysis from ST22.
An exception occurred that is explained in detail below. |
The exception, which is assigned to class 'CX_SY_RANGE_OUT_OF_BOUNDS', was not
caught in
procedure "PROCESS_TIMESHEET" "(METHOD)", 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:
In the running program "CL_XSS_CAT_RFC_COMMAND_TOOLS==CP", part of a string was
about to be accessed
with an explicitly specified length.
However, this length (4) exceeded the current length of the string
(3).
| This kind of access is illegal.
Kindly suggest.

The latest note released by SAP to solve this issue is 1559416 CATS WD: Dump if Attendance/Absence type is deactivated .It works !

Require Flexi Benefit Pay for India in ESS Portal

Dear All,
We need Flexi Benefit Pay option in ESS portal for India.
We tried a lot for the same but could not get any break through....
We found Salary Packaging option in R3 under the Tcode P16B_admin...this is wrking fine in R3 but we want this option in portal so that employees can choose their own salary structure.
We tried to pull this tcode thru Iview but the R3 screen is giving an option for employee to input pernr no. ...so now any employee can input anybodys pernr no. and modify the salary structure.
also please letme know if this is a standard feature or we have to go for standard development.
Thanks & Regards,
JJ.

Dear All,
Please give me some clue on this issue as we are stuck on this...
is this a standard functionality available in ess portal???
or
do we have to go for custom development??
Thanks & Regards,
Jignesh Joshi.

Customization of ESS portal !

Hi Experts,
I am working on Customization of ESS portal.
We have jdk1.4.2_22 installed on server.
Using NWDS7.0 sp18 with jdk1.4.2_22 build fails below error:
Settings\vanithakulkarni_s\.dtc\1\t\0C7CA564EC73CE1F904CE681D8F104EE\gen_wdp\packages\com\sap\xss\hr\per\us\bank\cc\CcPerBankInterface.java:20: cannot access com.sap.xss.per.helpers.CcHelper
     [javac] ERROR: bad class file: C:\Documents and Settings\vanithakulkarni_s\.dtc\1\DCs\sap.com\ess\per\_comp\gen\default\public\InternationalPersInfo\lib\java\sap.comessper~InternationalPersInfo.jar(com/sap/xss/per/helpers/CcHelper.class)
     [javac] ERROR: class file has wrong version 49.0, should be 48.0
     [javac] ERROR: Please remove or make sure it appears in the correct subdirectory of the classpath.
     [javac] ERROR: import com.sap.xss.per.helpers.CcHelper;
     [javac] ERROR:                                ^
     [javac] 1 error
Using NWDS7.0 sp18 with jdk1.5.0_18.
I am able to build and deploy application successfully . But getting Unsupported major.minor version 49.0 exception on the portal.
PFB Exception details.
   java.lang.UnsupportedClassVersionError: com/sap/xss/hr/per/us/address/overview/wdp/InternalVcPerAddressUSOverview (Unsupported major.minor version 49.0)
    at java.lang.ClassLoader.defineClass0(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
    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.ResourceLoader.loadClass(ResourceLoader.java:127)
    ... 59 more
From sdn came to know UnsupportedClassVersionError is generally for version mismatch. But with matching jdku2019s not able to build the application, to resolve that used the higher version of jdk.
Can anyone help me in solving this issue.
Thanks in advance. Any pointer related to this will be highly appreciated.
Edited by: Shrushti on Sep 25, 2009 8:20 PM

Hi All ,
Solution for the above problem is resolved by using higher verion jdk@NWDS side.
I am able build and deploy successfully by using JDK1.5.0_18.
Regards,
vanita k

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

Conflict on ESS Portal

Hi
When employee apply or try to aprrove leaves on ESS portal conflict erro with other absence or attendace type is coming. this process working fine on R3 System but not on portal.
IT 0007 status os 0- No time evaluation.

Hi Vikrant,
The issue is because, the employee has applied for the leaves on portal and before it is approved, that particular date is updated via backend in IT2001.
To resolve this issue, you will have to delete the leaves that are still in the sent status in the portal buffer area.
You will have to use the reports RPTARQDBVIEW and RPTARQDBDEL using tcode SA38.
Run the first report by selecting upto today option and then check the leave request in sent status that are already updated in backend in IT2001 then using the second report, select upto date option and uncheck the test run field and delete those request that you identified from the first report. This will resolve ur issue.
Cheers,
Ayyaps

ESS Portal - Timesheet not displaying for one user

Hello, I have a user who has always been able to access their timesheet via the ESS Portal but now when he clicks on the link for his timesheet all that returns is a blank web page. There are no errors, and it's not a browser issue because no one else is experiencing this issue and we've tried various browsers, all with the same result.
We have single sign on set up for the ESS Portal, and there is a role assigned to the user in core for them to access their timesheet via the portal.
This role has not been changed, and if it was, it would seem that all users would have been affected.
Does anyone know what I can check on the backend (HR master data, payroll, etc.) that would effect the timesheet for a specific user?
As well, is there anything I should check on the portal for this user which would affect the timesheet being displayed?
Thank you.

1. Review if his timesheet is being generated in the back-end (transaction PT61). If the time statement is generated in this transaction, the problem lies in the portal display.
2. If the time statement is not generated in this transaction, run transaction PT_ERL00 to review if there are any time evaluation errors for this employee. This report will show all error messages generated for each personnel number.
3. After reviewing errors, grab hold of a time management consultant and have him/her run time evaluation for this employee. Repeat from step 1 again.

Issue with ESS/MSS Business package 1.41

Hi All
I had an issue with ESS/MSS recently we deployed Business package 1.41 it contains HCM Forms and Process also,
and we assigned the standard Manager-self-service role & Employee-self-service-role to test user but when the user is trying to access the standard application he is getting Portal runtime error.
   Is there any configuration is need from HRFunctional side and Basis side
if any body have an idea please let me know ASAP.
For every MSS standard applications like :work overview ,Recruiting,Team,Talent Management,Budjet,Projects,Planning ,Organization, leave
I am getting like below error.
Portal runtime error.
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID: 02:17_13/04/11_0031_116801250
Refer to the log file for details about this exception.
Thanks
Renu.

Hi All
    Here I am giving logs detail I got two logs so giving both logs , can anybody help on this issue , if any configuration need please suggest.
Full Message Text
03:19_13/04/11_0045_116801250
[EXCEPTION]
com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<ProducerInfo>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System:    &#39;SAP_LocalSystem&#39;,
Attribute: &#39;client&#39;.
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
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)
Next One
Full Message Text
Exception ID:03:19_13/04/11_0045_116801250
[EXCEPTION]
com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/com.sap.pct/line_manager/com.sap.pct.erp.mss.bp_folder/com.sap.pct.erp.mss.14.bp_folder/com.sap.pct.erp.mss.14.roles/com.sap.pct.erp.mss.manager_self_service/com.sap.pct.erp.mss.manager/overview/com.sap.pct.erp.mss.work_overview/com.sap.pct.erp.mss.workoverview/com.sap.pct.erp.common.key_figure_monitor
Component class : com.sapportals.portal.sapapplication.SAPApplicationIntegratorComponent
User : P00000531
at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:343)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
at java.security.AccessController.doPrivileged(AccessController.java:246)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
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: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception in SAP Application Integrator occured: Unable to parse template '<System.Access.WAS.protocol>://<System.Access.WAS.hostname>/sap/bc/webdynpro/<WebDynproNamespace>/<WebDynproApplication>/;sap-ext-sid=<ESID[url_ENCODE]>?sap-ep-iviewhandle=007<ESID[HASH]>&sap-wd-configId=<WebDynproConfiguration>&sap-ep-iviewid=<IView.ShortID>&sap-ep-pcdunit=<IView.PCDUnit.ShortID>&sap-client=<System.client>&sap-language=<Request.Language>&sap-accessibility=<User.Accessibility[SAP_BOOL]>&sap-rtl=<LAF.RightToLeft[SAP_BOOL]>&sap-ep-version=<Portal.Version[url_ENCODE]>&sap-wd-tstamp=<$TimeStamp>&<ProducerInfo>&sap-explanation=<User.Explanation[SAP_BOOL]>&<StylesheetIntegration[IF_true PROCESS_RECURSIVE]>&<Authentication>&<DynamicParameter[PROCESS_RECURSIVE]>&<ForwardParameters[QUERYSTRING]>&<ApplicationParameter[PROCESS_RECURSIVE]>'; the problem occured at position 310. Cannot process expression <System.client> because Invalid System Attribute:
System:    &#39;SAP_LocalSystem&#39;,
Attribute: &#39;client&#39;.
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContentPass(AbstractIntegratorComponent.java:125)
at com.sapportals.portal.appintegrator.AbstractIntegratorComponent.doContent(AbstractIntegratorComponent.java:98)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
... 29 more

Single Sign Issue in Ess

Dear All,
EP7.0 SP9, ECC5
We have an major issue in ESS, The problem is with single sign on.
Here are the scenario's we are using :-
1. We are using "training1" as EP login id and in PA30 in R/3 InfoType 105 and Sub Infotype 0001 The same ID "training1" (Same as EP log in), the portal is picking the data properly and working fine.
2. If we use training1 as EP loginID and in PA30 in R/3 InfoType 105 and Sub Infotype 0001 if we use exeibckk (R/3 ID created for each individual user as communication user),
we are getting error "User TRAINING1 does not exist in this period"
we need to go ahead with the Step2, since all the EP login users are LDAP configured and,it has more than 15 characters, we cannot use EP login ID in InfoType 105 and Sub Infotype 0001
since it is restricted to 12 Characters.
e.g:
EP user ID is - shivakumar_ks ( taken from LDAP)
where as his R/3 or ESS user ID is - P000000002
since the login ID and R/3 ID are different,The system is throwing the error mentioned above.
We map the Shivakumar_ks with P000000002 in the EP Personalize option. But it is
not picking up the mapping. It tried to find the Shivakumar_ks in R/3 and fails.
Even though we are giving the UIDPWD in the system Logon Method.
Can anyone please give me the solution on the above.
Thanks in advane
Ponnusamy P

Hi,
As correctly mentioned here by debasish, most of the iviews in ESS and MSS use JCo Connections but there are some iviews which are IACs.
In this case, you need to configure both JCo connections as well as user mapping. Incase of PA30, which could be an IAC or a transaction iview, <b>you may just focus on User Mapping</b>. But for the webdynpro applications, you would need JCo Connections.
The link provided by Antonio clearly explains the steps. In brief, these are the steps involved:
1) Create System and an alias. Make sure that you use the logon method UIDPW.
2) Using the Personalization link, select a system and give the backend username and password. Save it.
Log off and test if it works.
Hope this helps.
Regards,
Sunil
PS: Reward points for helpful answers.

Error while selecting the Leave type in ESS portal

Dear Team,
One of the employee is trying to select a type of leave in ESS portal, system is giving error message as "Access is Denied" at the left hand corner of the screen. When i am checking it in Quality it is working fine.
Can anybody suggest me on this.
Kind Regards
Nag

Hi,
Please check whether that emplloyee has got authorization for this function in production system. Thanking you.

How to create a holiday calendar link on ESS portal

Hi,
Can anybody help me how to go about having holiday calendar link on ESS portal.
Regards,
Prasad

Why do you need the whole Holiday Caledar in ESS?
You can create the Iview of th Tcode SCAL

Issue in ESS Portal

Similar Messages

Maybe you are looking for