ESS/MSS in ECC 6.0 are Abap or Java WebDynpro ?

Hi ,
We are on ECC5.0 and have ESS/MSS on Java WebDynpro . For ECC6.0 are ESS/MSS in ECC 6.0 are Abap or Java WebDynpro compoment ?
Any watch out when updrading from ECC5.0 to  ECC6.0  ?
Thank you .

in ECC 6.0, ESS/MSS are WebDynpro Java calling ABAP backend function modules. However, be careful, there is a switch that enables SOME ESS services as ABAP WebDynpro (Especially in the Travel management area). Unless you use that switch all services are WebDynpro Java.
when upgrading from ECC5.0 to ECC 6.0 you need to test again all ESS/MSS services. In ECC5.0, services are written as Portal iViews, so customizations you made to ESS in ECC5.0 may be lost.
let me know if you still have questions.
Tiberiu

Similar Messages

  • ABAP Vs JAVA WebDynpro

    Hi friends,
    I have 6yrs of experience in SAP ABAP/4. I am new to WebDynpro. I have a pretty small question.
    Among ABAP WebDynpro and JAVA WebDynpro, which one will have more demand in future wrt market requirement.
    Thanks in advance for the information.
    Rgds,
    AK

    Hi AK,
    I have worked on both and following is the difference:
    Web Dynpro for ABAP:
    Web Dynpro for ABAP or Web Dynpro for ABAP (WD4A, WDA) is the SAP standard UI technology for developing Web applications in the ABAP environment. It consists of a runtime environment and a graphical development environment with special Web Dynpro tools that are integrated in the ABAP Workbench (SE80).
    The use of declarative and graphical tools significantly reduces the implementation effort
    1) Web Dynpro supports a structured design process
    2) Strict separation between layout and business data
    3) Reuse and better maintainability by using components
    4) Automatic operation of the Web Dynpro application using the keyboard
    5) User interface accessibility is supported
    6) Full integration in the reliable ABAP development environment
    for more see this:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/77/3545415ea6f523e10000000a155106/frameset.htm
    Web Dynpro for Java:
    Web Dynpro is a client-independent programming model of the SAP NetWeaver technology platform for developing user interfaces for professional business applications. It is based on the model view controller paradim which ensures that the business logic is separated from the presentation logic. This architecture is visible in the Web Dynpro perspective of the SAP NetWeaver Developer Studio (NWDS).
    Web Dynpro helps you with the development of Web applications by:
    1) Ensuring platform-independence with the meta model approach
    2) Minimizing the implementation effort through declarative programming
    3) Supporting a structured design process by applying the model view controller paradigm
    4) Providing reuse and better maintainability by using components
    5) Providing graphical support with tools in the Web Dynpro perspective
    6) Providing the SAP NetWeaver Java Development Infrastructure (NWDI) which supports team work with different services such as source code versioning and the Central Build Service.
    for more see:
    http://help.sap.com/saphelp_nw2004s/helpdata/en/15/0d4f21c17c8044af4868130e9fea07/content.htm
    The concept of Web Dynpro ABAP is identical with Web Dynpro Java and offers more or less the same functions
    Hopw this will help you.
    Cheers,
    Darshna.

  • Ess Time Sheet and Attendance Web Dynpro - ABAP or JAVA

    We are determining the resources we will be needing for the HR - ESS Time Sheet and Attendance Module.   
    What is this module written in.  ABAP Web Dynpro or Java Web Dynpro.
    Many thanks, 
    Multiple replies welcome.
    Ken

    The ESSTimeSheet is now called Record Working Time & for now it is still in WebDynpro JAVA.. looking at how complex the whole application is, it will really take some beating to rewrite the same in WDA.
    ~Suresh

  • 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

  • Upgrade path for ESS/MSS business package while upgrading to ECC 6.0

    Hi All,
    We have a scenario where SAP Enterprise Portal 7.0 SP 18 is currently running with SAP ECC 4.6C. SAP ECC is being upgraded to SAP ECC 6.0 and consequently we have a requirement to upgrade to the latest ESS/MSS business package. In a scenario like this what is SAP recommended approach for ESS/MSS upgrade? My questions are
    1) Is a direct upgrade of ESS/MSS possible? If this is possible, then how will it be done on a production system with reduced or no downtime?
    2) Should ESS/MSS business package be deployed and configured afresh after removing/undeploying the existing version of ESS/MSS business package? If this is the case how would the earlier customizations be restored?
    3) Is there any other approach?
    Thanks in advance.

    Hi Suresh,
    In my openion, it will be good if you go for new implementation, reason being as you mentiond ECC versionyou are on is 4.6c all the ESS applications are ITS based now a days all the application/iView for ESS are Webdynpro for Java or WD for ABAP based.
    Till the time the new portal ready you can continue with your currect one (No down time require).
    Most of the people are using this way. (Check the SDN for more details).
    Also chcek this migration guide, which will give you the basic steps required.
    http://www.sdn.sap.com/irj/scn/events?rid=/library/uuid/5e1226c7-0601-0010-7d82-a8134e833150&overridelayout=true
    Regards,

  • SAP IDES ECC 6.0 configuration for ess/mss

    Hi,
    Iam new to sap . i want to practice various scenarios in ess/mss in my own pc which  is installed with ecc 6.0 . what are the configuration to be made in ecc 6.0 for maintaining about 10-20 users for  using ess/mss scenarios. i have a knowledge on webdynpro java and little knowledge on ep and using r/3 server. The 10-20  users created should be able to use ess/mss through portal .
    So, list the steps configuring for 10-20 users for using ess/mss in ecc ides 6.0 server.
    Thanks & regard
    prasad

    << Do not post the same question across a number of forums >>

  • ESS / MSS Implementation for ECC 5.0 (ERP2004)

    Hello,
    We are preparing to implement ESS/MSS for ERP2004.  We are using EP6.0 SP9.  The notes for both ESS and MSS business packages refer to OSS Note 761266 regarding the versioning of XSS components.  Are the patches for the XSS components supposed to be deployed to the portal environment, the ERP2004 environment, or both?  The three patches mentioned are:
    PCUI_GP05_1.sca 
    ESS05_1.sca
    MSS05_1.sca
    Should these be installed in the portal, ERP2004, or both?
    Thanks,
    -Matt
    Since the patches are stored under the ERP2004folder in the support packages area of Service.SAP.com, I assumed they would be applied to the ERP environment, but I want to confirm this.

    Thanks for the clarification James.  I thought the patches should be applied to WebAS for the ERP2004 environment, but the OSS note is vague about that fact.
    Chuckie, We are implementing ESS version 60.2.  ECC 5.0 refers to Enterprise Central Component 5.0, which is how SAP refers to the Core R/3 product in the ERP2004 suite.
    -Matt

  • ESS/MSS With Web dynpro ABAP.

    Hi Gurus,
    I would like to know whether we can customize ESS/MSS business packages thru web dynpro for ABAP.  OR it only supports web dynpro for JAVA?? please let me know some important links to acheive the ESS/MSS customization thru Web dynpro for ABAP.
    Your help is highly appreciated.
    Thanks,
    David.

    Hi David,
    You may refer to
    http://help.sap.com/saphelp_nw70/helpdata/en/c5/f4b9422e0fb911e10000000a1550b0/frameset.htm
    Hope it helps.
    Regards
    Kir Chern

  • ESS, MSS node not displaying in portal

    Hi,
    I am not able to view the ESS,MSS configuration nodes in SPRO. Even i have activated EA_HR component field in spro under Activation Switch for SAP R/3 Enterprise Extension Set node.
    But i am able to view the ESS customizing nodes through PTARQ t.code.
    Kindly guid me, why  i am not able to view the ESS, MSS nodes in spro.
    we are into ECC 5.0, EP 6, Patch level is 85.
    Regards,
    Devi.

    Devi,
    PTARQ will suffice the need to configure ESS & MSS.
    Still if you need to access through SPRO follow --> SPRO - Cross application components - Home Page framework.
    or SPRO - Personnel Management - ESS.
    Still if you dont find the nodes..check with BASIS n finally raise a ticket to SAP.

  • ESS MSS Configuration steps

    Hi,
    Can anyone share congiuration manual for ESS MSS. ECC 6.0 , EHP 5.
    I really appreciate Siddharth for sharing Wiki config manual for ESS but it for <= EHP4.

    Hi King,
    Use lpd_cust for launchpad cutomization
    1. How to add service for an existing sub area :
    Here we have to store everything in Folder so Directly go to folder where you want to create that service and create new application.
    2. how to position the service (1st, 2nd, 3rd etc) in sub area
    3. how to assign subarea to area
    N/A
    4. how to create new area
    N/A
    5. how to hide service etc
    Two ways  to Hide services 1) Using portal -Goto content admin->content provided by sap->endusercontent->ess->preview the overview  iview and hide the scrvice which you dont want there.
    2) using LPD_CUST---delete the service from the folder.
    Note: Always work in  the copy of standard Menu and Instance role.
    Regards,
    Trilochan

  • ESS/MSS configuration as a BASIS Admin

    Hi gurus
    Aa a Basis Consultant I installed EP 7.0 successfully on windows 2003 database Db2.
    What are the Configuration to be done for ESS/MSS.
    Thanks
    Rao.

    Hi,
    Have a look at this links,
    http://help.sap.com/saphelp_erp2004/helpdata/en/38/e8584c2a664547b60442646bee23b6/frameset.htm
    http://help.sap.com/saphelp_erp2004/helpdata/en/38/e8584c2a664547b60442646bee23b6/frameset.htm
    Refer thread: Re: ESS / MSS on ECC 5 install guide
    & similar recent thread: ESS  And MSS
    Thanks,
    krishna chaitanya.

  • Training and Event Managaement in  ESS/MSS Portal for ERP2004 version

    Hi SDNs,
    I am working for ESS/MSS for ERP2004 system to NW2004s system.Afer importing the business packages to portal, I got only the following roles for ESS and MSS.
    Employee Self-Service:
    Employee Search | Working Time | Benefits and Payment | Personal Information | Career and Job | Purchasing | Work Environment | Travel and Expenses | Life and Work Events
    MSS: MyStaff:
    Overview | Attendance | Personnel Change Request | Recruiting | Reporting | Headcount
    MyBudget:
    Overview | Monitors and Reports | Equipment | Planning
    According to the Worksets i got it, i couldn't find, Training and Development activity, Performance Mangement in both ESS and MSS.
    How do I achieve this?
    We also have a requirement of OH & S to be integrated to ESS.
    Please suggest me to integrate this activities.
    Your help will be appreciated.
    Thanks in advance,
    Sireesha.B.

    Hi,
    Training and Development, Performance Management are not available in the latest versions of ESS and MSS.
    You may have to use the old Business Packages to incorporate this, the only difference would be that those pages would be BSPs.
    Please refer to the following threads:
    ESS/MSS with my SAP ERP2005
    Are there Appraisal for ESS
    BSPs for Performance Management - Response Appreciated.
    Regards,
    Sunil
    PS: Reward points for helpful answers.

  • Language specific settings for ESS/MSS

    Hello Experts,
    I got a question on language specific settings on the portal:
    1) Suppose i have configured my ESS/MSS BP  and my settings are in English language. Now when i logged in to the portal and click, it is opened in English language only, but when i click on Leave Request page, this particular page is opened in some other language (i mean other than English), so what might be the problem and where are the settings needs to be done if i encounter these kind of errors.
    Cheers
    Vijay

    Hi Vijay
    There are so many things that could affect language here is the ones I am aware of
    1) IE locale
    2) JCO language setting
    3) Forced Language in Iview itself
    4) Missing translations in the translation cycle
    5) Java Dictionary bugs see 1082994
    6) WD JAVA runtime bugs see 1265969
    Best wishes
    Stuart

  • ESS MSS documents for EP

    Hi all
            Can any one tell me where can I find the documents for ESS MSS configurations in EP.
    thanks

    there are lots of documentation available and lots of posts also in this SDN forum...!
    http://help.sap.com/saphelp_erp2005/helpdata/en/f6/263359f8c14ef98384ae7a2becd156/frameset.htm
    http://help.sap.com/saphelp_nw04/helpdata/en/43/eed93f130f9115e10000000a155106/frameset.htm
    http://help.sap.com/saphelp_erp2004/helpdata/en/38/e8584c2a664547b60442646bee23b6/frameset.htm
    try to find out some time and browse, you can get lotz of documentation...!
    Vijay

  • ESS MSS Basic doubts

    I am new to ESS MSS. I was reading documentation on this and have following doubts. I would be glad if somebody can help me with this.
    1. What is self service homepage?
    2. i read that we cn implement self service home oage with buisiness pakage  employee self service and manager self service. But we need ECC 5 for that. Does it mean we cannot implement ESS MSS on ECC 6. I may sou d stupid but what does that mean. I want to implement ESS MSS on ECC 6.
    Please clarify.
    Thanks

    Homepage is place where you see all the services,
    And yes you can install ESS MSS on ESS 600, No issues
    Please refer this doc
    http://help.sap.com/bp_hcmv1600/BBLibrary/Documentation/N06_BB_ConfigGuide_EN_US.doc
    or help.sap.com

Maybe you are looking for