Requried few details on ESS & MSS.

HI Expertise,
i am working as Sr SAP WEBDYNPRO ABAP CONSULTANT .Now i am moving to ESS & MSS .So any one can guide me on this
ESS (STANDARD & CUSTOMIZING ) , MSS (STANDARD & CUSTOMIZING) WEBDYNPRO.
By giving the material with screen shots so that i can understand
THANKS & REGARDS.
KHANNA.

Bhushan,
Most of the screens in ESS and MSS are webdynpro for java except Travel Management and few others .
MSS 1.41 - http://help.sap.com/erp2005_ehp_04/helpdata/EN/20/e091d641c845e6b786b985fc2d10ce/frameset.htm
ESS 1.41 - http://help.sap.com/erp2005_ehp_04/helpdata/EN/f6/263359f8c14ef98384ae7a2becd156/frameset.htm
Thanks
Bala Duvvuri

Similar Messages

Upgrading to EHP 4.0 - Have few queries on ESS/MSS, Erecruitment.

Hi,
We are trying to upgrade our portal to EHP 5.0. We have ESS/MSS and few webdynpro java and webdynpro abap applications on the portal. These are the few queries I have
1) ESS services : employee search, personal data, LMS(Webdynpro Java) are on EHP 3 as of now. Will the applications remain the same even if we upgrade to EHP5?
2) ESS travel management(Webdynpro ABAP) are on EHP 2 as of now. Will this application remain the same even if we upgrade to EHP 5?
3) E Recruitment (BSP) is on EHP 3 Will this application remain the same even if we upgrade to EHP 5?
4) We have MSS services: ERec Manager and Appraisal. Will these services affect if we upgrade to EHP 5?
4) We have few custom applications in Webdynpro abap and webdypro java developed on portal. Will these effect if we upgrade to EHP 5?
Thanks.
Regards,
Priyanka.

Hi Eric,
Thanks for your prompt reply.
Can you let me know which version of ESS/MSS and E-Recruitment business packages are applicable for the above version? And are these versions of ESS/MSS available in market now? Otherwise we can suggest our client to go for a upgrade to EHP 4.
Appreciate your input.
Regards,
Priyanka

Ess / Mss Error while manager tries to open the workitem in UWL.....

Hi Experts,
    As I am trying to apply the Loan details in ESS / MSS, Workflow is triggerred and workitem is received in the Manager's UWL. But when the Manager tries to open the Workitem it is going for dump. "As follows"....
"    The initial exception that caused the request to fail, was:
java.lang.IndexOutOfBoundsException: Index: 2, Size: 2
    at java.util.ArrayList.RangeCheck(ArrayList.java:512)
    at java.util.ArrayList.get(ArrayList.java:329)
    at com.sap.aii.proxy.framework.core.JcoBaseList.get(JcoBaseList.java:272)
    at com.sap.aii.proxy.framework.core.AbstractList.get(AbstractList.java:230)
    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCList.get(DynamicRFCList.java:281)
    ... 47 more ".
Like this there are 47 errors continued...
What may be the cause? What should be configured...
Here I have configured the "SWFVISU" with my tasks 'TS18900024" which in workflow.
Kindly give me some solution to solve the issue..
Regards
Kannan

Dear Kannan,
I am also facing same error while opening the loan request from MSS-UWL.
500 - Internal Server Error
java.lang.IndexOutOfBoundsException: Index: 2, Size: 2
    at java.util.ArrayList.RangeCheck(ArrayList.java:512)
    at java.util.ArrayList.get(ArrayList.java:329)
    at com.sap.aii.proxy.framework.core.JcoBaseList.get(JcoBaseList.java:272)
    at com.sap.aii.proxy.framework.core.AbstractList.get(AbstractList.java:230)
    at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCList.get(DynamicRFCList.java:281)
    ... 47 more
If you have any solution, please share.
If any config docs please send across - [email protected]
Thanks & Regards
Ganesh

Need information on ESS/MSS Roll-Out Project

Hi All
I have few questions on ESS/MSS as am new to ESS/MSS. please help me.
1.What is process of Roll-Out Project in ESS/MSS
2.Client is implemented ESS/MSS EHP5 in india, they want us to Roll-Out to china for the latest version EHP7.
Can i know what are the questions to be asked in initial meeting to the Client.??
2.They have provided the access for old system and ask us to check the configuration in the system
Can i know what are the important nodes to check in the system.??
3.if you have any config docs on EHP7.please can you forward to me.
Please help me in this.
Regards,
Rajesh

Google--- ESS MSS on EHP 7 and try all
Employee Self-Service - SAP Library
Setting Up the System Landscape - Business Package for Employee Self-Service (WDA) 1.50 - SAP Library
HCM EHP5, EHP6 and HR Renewal,Fiori Important links and documents
kindly ask ur basis consultant and portal consultant to upgrade ur system to latest business packages first and deploy all the necessary packages

Basic Information on ESS/MSS

Hello Guru's,
Kindly send me basic details about ESS/MSS.
Edited by: Prashanth Doggali on Nov 27, 2010 2:07 PM

Hi,
Please read this which is helpful....
ESS = Employee Self Service
It was designed to provide employees with a front-end user friendly way of maintaining their own details critical to HR operations
The idea was to reduce the amount of data entry which would need to be performed by HR (administrators or back office staff)
Employees could maintain or change their own details to ensure accuracy
The core components are
CA-ESS-WD
CA-ESS-ITS
PA-ESS-OCY/US/DE
PA-ESS-XX
These cover mainly the ESS screens for basic PA infotype updates and the back-end handling
ESS also provides a guided procedure application called Life and Work Events
Life and Work Events is a step by step workflow for employees particularly new employees (commonly known as My First Days) to maintain their details or document changes in their working life.
This is specifically for US customers however I believe customers can adapt it for their own countries
For further information see
Architecture of ESS
ESS environment consists of a front-end and a back-end system
The ECC system is the back-end R/3 system which contains HR master data and ESS related back-end code and customizing
The Portal is a J2EE server handling browser enquiries from front-end users - it provides the front-end environment for the end user
The front-end communicates with the back-end via a JCO connection JCO is a method of RFC communication between ABAP and JAVA
ESS is viewable via a browser (Internet Explorer etc)
The possibilities of usable browser versions depend on the Portal versions recommendations
A user is given a role which contains a workset, pages and iviews
An example of a role is the Employee Self Services tab in a Portal
An example of a workset is Overview tab in Portal
An example of a page would be the Overview Page
The layout of ESS is determined mostly by Homepage Framework (HpF) customizing in the Implementation Guide (IMG)
HpF is supported by component CA-GTF-TS-XSS
other things you need to configure like AREA GROUP PAGE , AREA PAGE , SUB AREAS, SERVICES, RESOURCES..
thanks
rafi

ESS & MSS related authorizations details..

Can someone help on whether ESS/MSS authorisation has something specific to be done other tan the pfcg in R/3. Could you give me more details on how is ESS/MSS authorizations are handled.. Is there any stand guide available which guides on setting this up.
Thanks,
Chetan Hinduja

Hi Chetan,
Among the deployed content of ESS and MSS in the Portal, you'll probably find roles in it that should be assigned to the users which are going to access those services.
Assigning these roles to the Portal users and the R/3 roles in PFCG should be enough.
Kind Regards,
Simone

Dependent's Details workflow in ESS MSS

Hello All ,
I am trying to create a workflow in ESS MSS which will be triggered from portal when employee will try to Add or change his dependent's details. Now my doubt is once employee is adding Dependent's details , it directly gets posted in Infotype - 0021 , Although My workflow is getting triggered after Posting but I want data to be posted once workflow is completed succesfully.

Hi,
How you are posting the change in dependent's details into IT0021 ? Is it through Custom RFC?
may be you need to change the process, You should create a task to post the data from portal to Infotype
using HR_INFOTYPE_OPERATION. This background task should get executed after final approval of the change.
There should not be automatic posting of the data.
Regards
Kedar

Help about ESS/MSS - Deploy error and landscape question

Hi.
I read a lot of post about this topic, but I continue something confuse about them.
I want to configure ESS and MSS.
My landscape is:
- J2EE 7.0 with Portal 7.0 (2004s) in a server A.
- ECC 5.0 ( with HR component SP05) in a server B.
Server B, has only stack Abap.
Server A is the latest version of Netweaver today. (stack j2ee and stack abap, BI, XI, Portal, etc)
I download and deploy in server A (J2EE 7.0), this components:
- BP ESS for erp2004
- BP MSS for erp2004
When I deploy the ESS BP, the deployment break raising this kind of error with the most of components, for example:

===========================================================================
Deployment started Tue Apr 10 12:01:57 ART 2007
===========================================================================
Starting Deployment of ess/au/addr
Aborted: development component 'ess/au/addr'/'sap.com'/'MAIN_xss04PAT_C'/'1178669'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04PAT_C'/'1000.100.0.15.1.20070309085432''/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy service:
java.rmi.RemoteException: Cannot deploy application sap.com/essauaddr.. Reason: Clusterwide exception: Failed to deploy application sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application sap.com/essauaddr. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment of ess/au/addr finished with Error (Duration 5187 ms)
Starting Deployment of SAP_ESS
Aborted: software component 'SAP_ESS'/'sap.com'/'MAIN_xss04PAT_C'/'1000.100.0.15.1.20070309085432''/'0':
Failed deployment of SDAs:
development component 'ess/au/addr'/'sap.com'/'MAIN_xss04PAT_C'/'1178669'/'0' : aborted
Please, look at error logs above for more information!
Deployment of SAP_ESS finished with Error (Duration 4781 ms)

Obviously, for this reason the most of iviews raise errors. A few of these works ok.
I assign role, and others configuration steps, this part I thinks that is OK
I configured the Jco, the role in Portal, the profile in ERP for ESS, etc.
My principal question is:
Can I use Portal 7.0 against ECC 5.0 in order tu use ESS/MSS based on webdynpro, without stack j2ee in ECC server (B) ?
Is necesary install J2ee stack in my server B ? or not?
Where I need to deploy the XSS 500 components ? in the J2EE 7.0 ?
Why when I deploy have this problem and the most of components cant deploy it?
For my landscape, which is the recommended setup ?
thanks in advance.!
Leandro.

My principal question is:
Can I use Portal 7.0 against ECC 5.0 in order tu use ESS/MSS based on webdynpro, without stack j2ee in ECC server (B) ?
You can use Portal 7.0 against ECC 5.0
Is necesary install J2ee stack in my server B ? or not?
You don't need to install J2EE stack on ECC system
Where I need to deploy the XSS 500 components ? in the J2EE 7.0 ?
Deploy XSS on Portal server not on ECC.
Why when I deploy have this problem and the most of components cant deploy it?
There won't be any issue. Go for ERP 2005
For my landscape, which is the recommended setup ?
As per the landscape mentioned by you, I will suggest go for ERP 2005 & XSS 600.
If you have further queries, mail me at [email protected]

Issue while accessing two web-dynpro application, ESS/MSS and Payroll

Hi All,
We are facing one Critical Server Issue in our systems. Following is the scenerio:-
Our Portal system was having one Application known as German Payroll application. Before last two week one more application of ESS/MSS i.e. Time Management has been deployed to our system.
Now the user has two application with two different roles in the portal.
When user try to navigate from Time Management Application to German Payroll application or German Payroll Application to Time Management Application then they are facing Critical Server Error issue.
But once the user try to refresh using CTRL+F5 then the problem got resolved.
========================================================================
German Payroll applications back end server details:P95.
Time Management Application back end server details: P23
Steps to reproduce the issue:
1-login to portalgot to Employee self service tab-wait for 3-5mins
& than navigate to german payroll applications----& faced crtical
server errors:
Log from deafult trace:-
=======================================================
1.#0021280FECEE0028000000A400005A4B0004A2FA644F345C#1305096215265#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#sap.com/tcwddispwda#com.sap.tc.webdyn
pro.progmodel.generation.DelegatingComponent#km048893#2758##n/a##fa2a61757b9911e08e660021280fecee#SAPEngine_Application_Thread[impl:3]
_9##0#0#Fatal#1#/Applications/Xss#
Java###null
[EXCEPTION]
#1#com.sap.tc.webdynpro.modelimpl.dynamicrfc.WDDynamicRFCExecuteException
at
com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClassExecutable.execute(DynamicRFCModelClassExecutable.java:107)
at com.sap.xss.ser.xssmenu.fc.ModelHandler.onInit
(ModelHandler.java:205)
at com.sap.xss.ser.xssmenu.fc.wdp.InternalModelHandler.onInit
(InternalModelHandler.java:428)
at com.sap.xss.ser.xssmenu.fc.FcXssMenu.setPersonnelNumber
(FcXssMenu.java:570)
at com.sap.xss.ser.xssmenu.fc.FcXssMenu.onInit
(FcXssMenu.java:292)
at com.sap.xss.ser.xssmenu.fc.wdp.InternalFcXssMenu.onInit
(InternalFcXssMenu.java:455)
at com.sap.xss.ser.xssmenu.fc.FcXssMenuInterface.onInit
(FcXssMenuInterface.java:165)
System 'P95' is not possible because RFC Metadata was retrieved using
System 'P23'. Please assure you have configured the RFC Connections
properly. A Server restart may
be necessary!#
==============================================================
here is the catch....When user is trying to navigate from ESS tab(using
custom jcos for Backend system P23) to German payroll(backend system
P95) after 3 mins ---getting crtical error...Still its using the
data/metadat jcos connection information of ESS applications from
cache...that you can see in default trace.
PS: Standards Jcos are configured for P23 systems:
====================================================
SAP_R3_HumanResources----created with P23
SAP_R3_HumanResources_MetaData----been created with P23
SAP_R3_SelfServiceGenerics----been created with P23
SAP_R3_SelfServiceGenerics_MetaData----been created with P23
=====================================================
P95----Germman payroll
P23---ESS/MSS
Name of Cutsomn Jcos created for bakcend P95 i.e. german payroll
A-P95
=======================================================
SAP_R3_HumanResources:D95
SAP_R3_HumanResources_MetaData:D95
SAP_R3_SelfServiceGenerics:D95
SAP_R3_SelfServiceGenerics_MetaData:D95 configured with sap-wd-arfc-
useSys.
Name of cutom jcos created for backend ESS/MSS P23
B-P23
=========================================================
SAP_R3_HumanResources_MetaData:X23
SAP_R3_HumanResources:X23
SAP_R3_SelfServiceGenerics:X23
SAP_R3_SelfServiceGenerics_MetaData:X23 configured with sap-wd-arfc-
useSys.
========================================================
Jcos parameter of P23 backend:
JCo Pool Configuration
Maximum Pool Size: 50
Maximum Connections: 100
Connection Timeout (msec.): 10000
Maximum Waiting Time (msec.): 30000
Jcos parameter of P95 backend:
JCo Pool Configuration :
Maximum Pool Size: 5
Maximum Connections: 10
Connection Timeout (msec.): 10000
Maximum Waiting Time (msec.): 30000
===================================================================
After more analyzing the situation we found that one web dynrpo component i.e. pcui_gp~xssutils is common to both the application and it is configured to standard JCO i.e.
SAP_R3_HumanResources
SAP_R3_HumanResources_MetaData
SAP_R3_SelfServiceGenerics
SAP_R3_SelfServiceGenerics_MetaData
My thinking is that this component is giving us the problem.
Please provide your comments and solution to rectify this issue.
Also, let me know in case you need more information.
Thanks in Advance
Kuldeep Verma

Hi
First try a very simple application with nothing in it just one text saying Hello World
Run it and see what happens.
Also check if your url uses FQDN name. something like https:
company.name.co:50000\.......
If you do not use the FQDN it will always show a script error on the bottom and some functions will not work e.g
dropdowns.
regards
Yuval.

Creation Of Track For ESS/MSS

Hi,
Could anybody send me the steps in brief or any document which gives step by step procude exactly what needs to be done in NWDI to create a track for ESS/MSS.
I have gone thru some of the sdn posts but i didnt get exactly what steps need to be done....like apart from importing predefined SCA's.
Please help me out...
Regards
Sireesha.

Hi Sreesha,
Process: Creating Track for ESS/MSS Application.
1) open the NWDI URL.
2)click on "Change Management Service" link and login.
3)After logging you will be in "Transport Studio" link. Shift to "Landscape Configurator" link click on that, there you will see tract related page.
4)In the middle of the page there are differnet options(buttons) like Change,New,Save,Save As,e.t.c..
5)Click on New button then you will get new track related fields. After giving required details bottom of that there are some more options(buttons) like ADD Sc,Delete,e.t.c.., clcik on ADD Sc and add the SCs related to ESS/MSS and click on SAVE button which is present on top of window.
6)With these steps required track will be created...
Any queries revert back.....
Regards,
Anil.

Objective setting appraisal (OSA) queries related to ESS/MSS

Hello All,
I am currently working in OSA. I have few queries related to this.
My client wants to implement OSA without linking it to the SAP ESS/MSS. They have their own intranet portal which is not a part of SAP. But they are using it for applying leave etc which has been linked to SAP R/3. So they also want to use the the same portal for appraisal also.
Hence my query is whether is it possible to link OSA with their own inhouse intranet portal ? And if it is possible then how and will I be able to get all those functionalites which are available in standard ESS/MSS for OSA?
Please guide.
Regards,
Daniel

Hi Daniel
If you can call SAP Portal in your local intrenet.
In one of my clients they were using MOSS as thier frame work (SAP portal is called inside moss)
Thanks
Rajdeep

Portal runtime error, when click on ESS MSS

Dear Gurus,
Whenever I click on any link of MSS, it gives me runtime error. Please see the screenshot.
Portal runtime error
An exception occurred while processing your request. Send the exception ID to your portal administrator.
Exception ID 03:38_14/05/14_0019_13493050
See log file for details about this exception
Screen shot
- SSO steps configured
- ESS/MSS roles given in both of ABAP and JAVA side
ITS, connector and WEB AS test successfully (screen shot maintaned below)
Only Alias defined : SAP_R3_HumanResources
Detalied Error Log;
Failed to invalidate cached entry for user a368ecb2db6411e3a030000000cde33a Exception:java.rmi.RemoteException: Cannot clear ICM server cache by [a368ecb2db6411e3a030000000cde33a] etag.; nested exception is:
com.sap.bc.proj.jstartup.icmadm.IcmAdmException: interface disabled
[EXCEPTION]
java.rmi.RemoteException: Cannot clear ICM server cache by [a368ecb2db6411e3a030000000cde33a] etag.; nested exception is:
com.sap.bc.proj.jstartup.icmadm.IcmAdmException: interface disabled
at com.sap.engine.services.httpserver.server.CacheManagementInterfaceImpl.clearCacheByEtag(CacheManagementInterfaceImpl.java:33)
at com.sap.netweaver.rtmf.serverimpl.users.RTMFUser.clearICMCache(RTMFUser.java:231)
at com.sap.netweaver.rtmf.serverimpl.users.RTMFUser.doLogout(RTMFUser.java:296)
at com.sap.netweaver.rtmf.serverimpl.users.UserList.removeUser(UserList.java:123)
at com.sap.netweaver.rtmf.serverimpl.services.UserManagerService.doLogout(UserManagerService.java:590)
at com.sap.netweaver.rtmf.serverimpl.services.UserManagerService.activeActionMethod(UserManagerService.java:100)
at com.sap.netweaver.rtmf.serverimpl.services.UserManagerService.onMessageArrived(UserManagerService.java:71)
at com.sap.netweaver.rtmf.serverimpl.services.UserManagerService.onUserMessageArrived(UserManagerService.java:698)
at com.sap.netweaver.rtmf.messagingimpl.messages.RTMFMessageDispatcher.sendMessageToService(RTMFMessageDispatcher.java:45)
at com.sap.netweaver.rtmf.serverimpl.core.MessageDispatcher.sendMessageToService(MessageDispatcher.java:46)
at com.sap.netweaver.rtmf.serverimpl.core.MessageDispatcher.handleRequest(MessageDispatcher.java:72)
at com.sap.netweaver.rtmf.serverimpl.core.dispatch.dispatchers.SendDispatcher.dispatch(SendDispatcher.java:37)
at com.sap.netweaver.rtmf.serverimpl.core.RTMFCore.handleSendRequest(RTMFCore.java:190)
at com.sap.netweaver.rtmf.serverimpl.core.RTMFCore.handleRequest(RTMFCore.java:154)
at com.sap.netweaver.rtmf.serverimpl.server.RTMFServer.handleRequest(RTMFServer.java:89)
at com.sap.netweaver.rtmf.servlet.ServletWrapper.doPost(ServletWrapper.java:54)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: com.sap.bc.proj.jstartup.icmadm.IcmAdmException: interface disabled
at com.sap.bc.proj.jstartup.icmadm.IcmAdm.getInstance(IcmAdm.java:77)
at com.sap.engine.lib.http.cache.CacheAdmin.getInstance(CacheAdmin.java:53)
at com.sap.engine.lib.http.cache.CacheAdmin.invalidateCacheEntries(CacheAdmin.java:30)
at com.sap.engine.services.httpserver.server.CacheManagementInterfaceImpl.clearCacheByEtag(CacheManagementInterfaceImpl.java:29)
... 56 more
LOG OVERVIEW

After implementing the PCUI_GP , ESS is not empty anoymore but it is giving error like this ;
Detailed Error ;
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exception was thrown in preprocessing phase of application session O8h94DN06FMAxZD*frJ44w--szntRnBBZbpD5Fsc0H8XnA--/pcd:portal_content/com.sap.pct/every_user/com.sap.pct.erp.ess.bp_folder/com.sap.pct.erp.ess.roles/com.sap.pct.erp.ess.employee_self_service/com.sap.pct.erp.ess.employee_self_service/com.sap.pct.erp.ess.areagroup_overview/com.sap.pct.erp.ess.overview/sap.com/pcui_gp~xssutils/XssMenu/base/. The causing exception is nested. RID=50ba7f52dc4311e3bf72000000cde33a
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:663)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:349)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:325)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:62)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.service(DispatchHandlerForRequestManager.java:39)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.service(DispatchHandlerForRequestManager.java:46)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:270)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToAppContext(ExecutionContextDispatcher.java:68)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:53)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:244)
at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$Runner.callRequestManager(JavaApplicationProxy.java:1244)
at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$Runner.callEmbeddedApplication(JavaApplicationProxy.java:1122)
at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$StartCommand.doExecute(JavaApplicationProxy.java:1575)
at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$AbstractCommand.execute(JavaApplicationProxy.java:1488)
at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy$Runner.execute(JavaApplicationProxy.java:1028)
at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy.execute(JavaApplicationProxy.java:859)
at com.sap.tc.webdynpro.clientserver.embedding.JavaApplicationProxy.start1(JavaApplicationProxy.java:637)
at com.sap.tc.webdynpro.portal.pb.impl.JavaApplicationProxyAdapter.create(JavaApplicationProxyAdapter.java:166)
at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1661)
at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:408)
at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:638)
at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:1087)
at com.sap.portal.pb.PageBuilder$PhaseListenerImpl.doPhase(PageBuilder.java:2091)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:251)
at com.sap.tc.webdynpro.clientserver.phases.PortalDispatchPhase.execute(PortalDispatchPhase.java:50)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequestPartly(WindowPhaseModel.java:162)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doProcessRequest(WindowPhaseModel.java:110)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:97)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:515)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:58)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doExecute(ClientApplication.java:1671)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doProcessing(ClientApplication.java:1485)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doApplicationProcessing(ApplicationSession.java:894)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:357)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:325)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.wdc.DispatcherServlet.doContent(DispatcherServlet.java:89)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doPost(AbstractDispatcherServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:152)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:38)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:457)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:276)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Caused by: com.sap.tc.webdynpro.services.exceptions.ApplicationFaultException: wdDoInit: exception thrown in this user coding area
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:164)
at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:227)
at com.sap.tc.webdynpro.progmodel.components.Component.initController(Component.java:258)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:206)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:590)
at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.doPreprocessing(ClientApplication.java:1457)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doPreprocessing(ApplicationSession.java:660)
... 78 more
Caused by: com.sap.tc.webdynpro.progmodel.context.DictionaryException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler.getScalarType(DictionaryHandler.java:378)
at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler.getDataType(DictionaryHandler.java:126)
at com.sap.tc.webdynpro.progmodel.context.DataAttributeInfo.init(DataAttributeInfo.java:438)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initUnmappedAttributes(NodeInfo.java:1002)
at com.sap.tc.webdynpro.progmodel.context.DataNodeInfo.doInit(DataNodeInfo.java:294)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:974)
at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:978)
at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:67)
at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:205)
at com.sap.tc.webdynpro.progmodel.components.Component.getCustomControllerInternal(Component.java:668)
at com.sap.tc.webdynpro.progmodel.components.Component.getController(Component.java:597)
at com.sap.tc.webdynpro.progmodel.components.Component.getController(Component.java:552)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.getPublicInterface(DelegatingComponent.java:275)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetBackendConnectionsController(InternalFPMComponent.java:190)
at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:204)
at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:105)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:161)
... 84 more
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.DictionarySetup$1.fillSldConnection(DictionarySetup.java:51)
at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:437)
at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:361)
at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:198)
at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:161)
at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:96)
at com.sap.dictionary.runtime.DdDictionaryPool.makeDictionary(DdDictionaryPool.java:75)
at com.sap.dictionary.runtime.DdDictionaryPool.makeDictionary(DdDictionaryPool.java:63)
at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:230)
at com.sap.tc.webdynpro.progmodel.context.DictionaryHandler.getScalarType(DictionaryHandler.java:370)
... 100 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.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:153)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:161)
at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:64)
at com.sap.tc.webdynpro.services.datatypes.core.DictionarySetup$1.fillSldConnection(DictionarySetup.java:32)
... 109 more
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to load client to connect to SLD. Please check your SLD connection settings using the Visual Admin.
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory$1.run(SystemLandscapeFactory.java:626)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getClient(SystemLandscapeFactory.java:619)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.readJCODestinationFromSLD(JCOClientConnection.java:458)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:396)
at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:237)
at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:222)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:84)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:151)
... 112 more
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Getting CIMClient failed: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.. Please check that destination SLD_Client is maintained correctly.
at com.sap.sldserv.SldApplicationService.getCimClient(SldApplicationService.java:93)
at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory$1.run(SystemLandscapeFactory.java:623)
... 120 more
Caused by: com.sap.sldserv.exception.SldServiceRuntimeException: Destination SLD_Client not found. Destinations are defined in the Destination service.
at com.sap.sldserv.SldApplicationService.getCimClient(SldApplicationService.java:75)
... 121 more

Push buttons doesn't show up in Appraisal template-(ESS,MSS)

Hi SAP friends,
I have template created with few sub-statuses and thus have created few push buttons to control the flow in ESS and MSS portal.
However I do not see any pushbuttons (or radio buttons) in ESS/MSS. Appreciate if you can guide me what all areas I was missing? Do we need to do anything in portal or Iviews? I read somewhere in forum that we need to do some thing in Iviews, but I was not convinced with it. Appreciate your speedy suggestions as we are in critical stage of project.
I have substatus created in In-Planning.
I'm not using In-planning status but using sub-status. Here is how I have mapped
Status flow at template level:
Outbout status - "In-PLanning"
Outbout substatus : Enter Objectives & Goals(Employee level)
PUSH BUTTON - Submit for Mgr review
Person Authorized - Aprraises
Target status : In- PLanning
Target substus - Manager Review

Hi
I think u are trying to go to previous status from sub status. From In Preparation you can come to In planning or the sub status of in planning.
Thanks & regards,
Vikas

Approve link not working in ESS/MSS UWL portal

Hi experts,
we are using portal 7.3 with ess/mss.
in mss when user is approving a leave request, he is not ale to proceed
after few steps as one link "pprove another request" is not working.
this i a standrd portal scren in UWL. please suggest.
Thanks a lot in advance.

Hello,
This should be possible with some UWL configuration. Please check the following forum post: http://forums.sdn.sap.com/thread.jspa?threadID=1677777
Kr,
Julien

ESS/MSS leave approve view is diaplaying as error

Hi All,
We are using ESS/MSS for leave request and approval process.
We did neccessary configuration for the same. I have created leave request in ESS successfully and the same request displayed as item in UWL/Task. When try to approve, by clicking the link, it throws an error.
The error details are : 503 Service not available
Error: -6
Version: 7000
Component: J2EE Server
Date/Time: Mon Jan 16 14:31:49 2012
Module: http_j2ee_mt.c
Line: 820
Server: eppilot_KHE_11
Error Tag:
Detail: Cannot reach external Application Server on eppilot:51111
When i try to preview the Iview 'leave reuqest approval' as a stand alone(from Content administration), its shows the approval view perfectly . even i tried to approve from their , its approving perfectly. But the Leave request approval view is not displaying when manager click the link to approve in UWL/Task.
Kindly help.
Thanks,
Venkat

Hi Andy,
Thanks for your reply.
As per the SAP Note 779075,
I have changed in SWFVISU same as below.
TS12300097 WebDynpro Java
                APPLICATION LeaveRequestApprover
                DYNPARAM    wi_id=${item.externalId}
                PACKAGE     sap.com/ess~lea
TS12300116 WebDynpro Java
                APPLICATION LeaveRequest
                DYNPARAM    wi_id=${item.externalId}
                PACKAGE     sap.com/ess~lea
The application "LeaveRequestAdmin" is not released. Use transaction SWFVISU to delete the following entry:
TS12300104 WebDynpro Java
                APPLICATION LeaveRequestAdmin
                PACKAGE     sap.com/ess~lea
1.After that , in Universal Worklist configuration, I have selected the row..system alias 'SAP_WedDYnpro_XSS' Connector type 'Web flow connector, clicked the re-register button. I got the folowing message :
Item type registration was successful for the following systems:
- SAP_WebDynpro_XSS (WebFlowConnector
2. After that i have cleared the cache.
But still i am getting the same error message, when i click the leave request item. Kindly help.
Thanks in advance.

Requried few details on ESS & MSS.

Similar Messages

Maybe you are looking for