ESS/MSS Multiclient Szenario

Hello,
The scenario we want to build is:
- Have one portal
- Have one J2EE Engine
- Have one backend with TWO clients (e.g. 100 and 200)
- Have ESS/MSS running and connect to both clients (multiclient szenario)
What has been done so far:
1) Copied folder for ESS or MSS with iViews, Pages, Roles etc. to connect those to client 200
2) Create new backend client and added to system landscape
3) Create new JCo connection    (New JCo Connection for new client). We have done that with extension CL2 and adding to iView application paramter sap-wd-arfc-wd-usesys for redirecting the JCo connection of WebDynpro - that works)
4) Change PCD location of one Service (e.g. Who is Who for testing) on backend <b>client 200</b> with Transaction SPRO - changed key EMPLOYEE_WHOISWHO_SERVICE05 - to the PCD location of copied iView from step 1.
5) System aliases are defined for client 200 at time
Status:
- We have a set of copied iViews where JCo is redirected to client 200. Redirection of JCo Connections works
- The original set of ESS iviews is not modified, JCo Connections established to connect to client 100
Problem faced: On ESS overview page iView (for example) we cannot divide the iViews to be called.
- On copied Client 200 Overview iView if we click "Who is Who" for example, the copied "client 200" 'Who is Who'  iView starts.
- On original Client 100 Overview also client 200 Who is Who is started (!!!)
-> As System Aliases all point to 200 we assume both getting information from Client 200 (?) over System Alias (?)
What we assume:
- We need to create a second set of System Aliases - keep the original to point to 100, make a new set to point to 200
- Problem: we can't have two System Aliases with the same name
So how can we get the second copied set of ESS/MSS to work with different System aliases? Or do we miss out here something else?
Frank

Hi Frank,
You have to copy services and resources as well.
The service you are calling from home page framework, has a resource associated with it. Whos who link that you can see on the overview page, will in turn refer to the resource for PCD location. Now check this PCD location is correct or not.
After associating correct resource_200 to service_200, please make sure its assinged to an area_200 and this area is mentioned in Home page framework iView as an application parameter.
Say for employee seach,
sap.xss.menuarea=EMPLOYEE_SEARCH&sap.xss.menuargrp=SAPDEFAULTESS&sap.xss.menuhdr=SAPDEFAULT
Make sure this menu area points to your client 200 area.
I am not sure if u have copied areas and area grp pages as well.
Make a copy of area grp and name it SAPDEFAULTESS_200. Similarly copy all the areas and assing it to area grp (for client 200).
Note that, all area pages are different services. you will have to copy them as well.
After this, make changes to your iView on portal.
goto content delivered by SAP -> end user content -> ESS
and modify your Overview iView as well as Area iViews. Mention correct areas and area grp in the iView.
Cheers!!
Ashutosh

Similar Messages

  • ESS/MSS in multiclient szenario

    Hello,
    we want to use on one portal two ESS/MSS (Erp2005) szenarios pointing to different backend clients. What we did so far:
    1. Copy the Business Portal in portal to a second folder
    2. Redirect the JCo Connections of copied iViews to new client
    3. Define new JCo connections
    If we start with the overview page, we can see the new page for new client. But if we click on a service, lets say "Who is Who" this does not call the copied iView for new client but still the old one in original location.
    Where is this piece of information hidden, that say when I click on a service, open a specific iView? From looking in the code of the PCUI components I did not find any... I believe its somewhere in the R/3??
    Best regards,
    Frank

    Hi Frank,
    I'm confused how you have managed to configure ESS to connect to two different backend SAP clients at the same time from within one portal using the ESS webdynpro development components and JCo Connections.
    I didn't think this was possible as the webdynpro components use one JCo connection that links into exactly one client. Can you please expand upon how you managed to achieve this as we want to do the same thing.
    Did you make copies of the ESS webdynpro development components or modify them somehow to point at a different JCo connection that points at a different backend client?
    regards,
    Sean

  • NetWeaver Portal and ERP 6.0: BI, ESS/MSS and full Portal on one machine

    Hello,
    with ERP 6.0 you need a EP Core Portal for BI Java. An other EP Core Portal for HCM ECC/MSS. The iViews from this portal you integrate in the main portal via federated portal. But in this scenario i need to much portals and have a lot of maintenance costs (administration overhead for evry portal). For a small Customer i will build one Portal for all. It is possible e.g. to use the BI Portal with ESS/MSS and as full portal?
    Best regards,
    Patrick

    Hi,
    So you would like one BI installation with both the ABAP and the Java-stack with the full BI-functionallity and additionally the XSS-component and set it up to work against the ECC ABAP-only system ?
    I think the scenario would actually work, but:
    1) You might get future problems if you want to upgrade your BI-system and not the ECC-system.
    Is it possible to run the old XSS-components in the new java-stack ?
    2) You might get future problems if you want to upgrade your ECC-system and not the BI-system.
    What if the new version of the XSS-component demands certain java-components which the BI-system do not have.
    So my recommendation is still to run the java-stack on both systems.
    ECC with the XSS-java-components and BI with the Bi-java-components.
    This way you do not lock yourself into a corner and each system can be upgrade independent of the other.

  • Backend R/3 connectivity for ESS MSS from portal

    Hi,
    We are currently in development cycle for ESS/MSS based on portal EP 6.0 SP16 and ERP 2004 in backend. We are trying to find out how the ESS/MSS business package on portal works with backend ESS functionality in ERP 2004. It is more of a connectivity question. We want to know if we expose our portal to internet so that users can login to ESS/MSS from internet, do we need to put backend ERP (ECC 5.0) system also in DMZ? Do we need to open ports between portal and R/3 so that ESS/MSS can work? Or the communication happens using JCO connections and we need not to expose R/3 system.
    Also one more specific question? If someone knows how ESS/MSS talks to backend system. At SAP application layer level or database level? I am asking this question to check if I need to open a port to talk to database or I can very well keep 2-3 SAP application server in DMZ and work.
    PK

    You need to look at the specific business package. For example, ESS for mySAP ERP 2004 says that the technology is Java / Web dynpro, which says that the Java engine uses RFCc to get the data from the backend.
    Othe businesss packages may use ITS, which then needs another connection from the user to the ITS server.
    Cheers

  • Creating NWDI track for ESS/MSS

    Hi,
    I am trying to implement ESS/MSS (600 SP7). For customization I need to import the package on the track in CMS. Import of JEE, JTECHS, BUILDT and PCUIG were successful. When i tried importing ESS and MSS, import is failing. Check-In of both the components are successful but while importing the component under Development tab, its failing. Import of MSS in DTR is successful but CMS is failing.
    Below is the log for ESS:
    Info:Starting Step Repository-import at 2007-04-10 12:46:13.0591 +5:00
    Info:Component:sap.com/SAP_ESS
    Info:Version  :MAIN_ERP05PAT_C.20070314050106
    Info:1. PR is of type TCSSoftwareComponent
    Info:propagatable is known in repository, it is not necessary to write the workspacecontent to the DTR
    Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]:communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
    com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailure received: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
         at com.sap.cms.tcs.client.DTRCommunicator.integrateChangelist(DTRCommunicator.java:393)
         at com.sap.cms.tcs.core.RepositoryImportTask.processRepositoryImport(RepositoryImportTask.java:335)
         at com.sap.cms.tcs.core.RepositoryImportTask.process(RepositoryImportTask.java:578)
         at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
         at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:197)
         at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:376)
         at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:227)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:634)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:103)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:584)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:560)
         at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImport(LocalCmsTransportProxyLocalObjectImpl0_0.java:1252)
         at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1198)
         at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2215)
         at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:881)
         at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2390)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:752)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:705)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
         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:160)
         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:207)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Info:Step Repository-import ended with result 'fatal error' ,stopping execution at 2007-04-10 12:47:49.0198 +5:00
    Regards,
    Piyush.
    ps: points will be awarded to all helpful answers. )

    Hi Bharath
    How r u? Hope fine.
    I have specified the version above. I am using (ESS 600 SP 7 [P11] & MSS 600 SP 7 [P4]).
    Is there anything i can do to resolve the issue in JDBC etc? Whats this AFAIK?
    Can u suggest something, a work around, to solve this issue?
    Regards,
    Piyush.
    ps: u can directly mail to my ID, will grant u points for helpful answers. )

  • Function modules or BAPIs for ESS MSS

    Hi Experts,
    I am new to HR (ESS/MSS & who's who). I am looking for standard BAPI's and Function Modules that would give me information about an employee's upper level's and lower levels (reporting).
    My requirement is to build an Webdynpro Application with taking employee id as user input and display his uplevel's and downlevel's. Also, hyperlink on employee should help me to further navigate to the corresponding employee's information.
    Note: I tried to search this forum, but unable to narrow down the required business functions that i require.
    Thanks,
    Gaurav.

    https://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=190743879
    RH_GET_MANAGER_ASSIGNMENT

  • 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.

  • ESS/MSS Installation to R/3 4.7 Enterprise

    Goodday Guru's,
    I've just received a requirement to install and configure ESS/MSS. Backend system is on R/3 4.7 and Portal is on EP 6.0. I have downloaded ESS 50.4 and MSS 60.1_19 for this requirement. There would not be any development work, only out of the box standard ESS/MSS configuration. I believe that most of you out htere have succesfully implemented such a requirement. Would you mind sharing your experience with me? Any step-by-step guide would be very appreciated.
    P.S:- Just a quick check. For this requirement, do i need to  download ESS/MSS/PCUI for WebDynpro component? I know that it is needed for ERP2004 (ECC 5.0).
    Regards,
    Johan

    Hi Johan
    the following is procedure that u need.
    if u have all DVD/CD for installation than go by following.
    if ur os is win2000 -- SP4 needed or use WIN2003 server
    install J2SDK 1.4.2_08 or _09 don't use above.
    set JAVA_HOME variable in win2000 enviorenment variable.
    set path c:\j2sdk1.4.2_08\bin;
    install oracle with no database (do not create any databse during oracle installation, look oracle installation documentation)
    apply oracle patch.
    set ORACLE_HOME under win2000 enviorenment variable.
    set ORACLE_SID under win2000 enviorenment variable.
    where sid is ur sap system id i.e EPD
    install j2ee server.
    install portal.
    install CM if u want.
    install ITS 6.20 on same system or Other win2000/2003 system (IIS required. look installation document)
    create system  i.e R3,ITS in portal according to document that i send,
    import Buisness package for ESS/MSS into portal,
    assign the ESS/MSS role to user in portal.
    By default ther is no role for ESS with standard BP's create ur own role and Add tha workset using delta link,
    u can find the import content under migrated content-> EP 5.0
    regards,
    kaushal

  • 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 Team Calendar Customization

    Hi Team,
    We are implemented ESS & MSS &  configured Team Calendar  but in that we are facing bellow issues
    Can we do customization Team calendar? If it is possible how?
    Reporting structure showing wrongly displaying.
        please help me
    Regards,
    Ajay

    Hi Mithun & Jwala,
    Thanks for reply, here i am sharing my screen shots please check
    We required direct report employees list only should display MSS  Team workset
        Emp: Direct report employees only 44 to that manager but in MSS team workset nearly 90 employees
                are displying
    I am client side functional consultant, my ESS & MSS project done by other company
    Now they left the company  I had no much knowledge on the ESS& MSS Team calendar just I had knowledge functional side so please guide me to close my issue
    Thanks,
    Ajay

  • ESS / MSS - is there a way to view Histories of FORMs submitted and processed?

    Hi,
    We're implementing the ESS / MSS RDS  EP 6 (version 3.606 SAP Enterprise Portal scenario).
    The project also includes the custom development of a number of Forms that will be integrated into ESS / MSS via iViews.
    The customer requires a "HISTORY View" of FORMs for the ESS and MSS users.
    It is the historic  FORMs themselves that they want to be able to display - or as much of the Key information from the Forms that they can identify specific Form submissions  (and not the related Workflows for these forms).
    I'm told that there is no HISTORY view for Forms.   The history functions for Workflows (in the UWL) is not really suitable for users but only for more technical analysis of workflows.
    Does anyone know of a way of getting these history views of Forms without resorting to a custom development?  e.g. is there a standard Report or a way of enabling Histories to be maintained and accessible?
    Kind Regards
    Alan

    Hi Alan,
    I think the best we could get is Process Browser application.
    Can you refer this link and see if this helps.
    Also try the WD Application - ASR_PROCESSES_DISPLAY.
    Thanks
    Raja Sekhar

  • Error while accessing services of ESS/MSS tabs - URGENT

    Hi,
    When i am accessing the services under ESS, MSS tabs ie, Leave request, My expenses etc.... i am getting the following error. 
    A critical error has occured. Processing of the service had to be terminated. Unsaved data has been lost.
    Please contact your system administrator.
    User XYZ does not exist in this period:
    com.sap.pcuigp.xssfpm.java.FPMRuntimeException: User XYZ does not exist in this period
         at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:111)
         at com.sap.pcuigp.xssfpm.java.MessageManager.raiseException(MessageManager.java:121)
         at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.initPernr(FcEmployeeServices.java:257)
         at com.sap.pcuigp.xssutils.pernr.FcEmployeeServices.onInit(FcEmployeeServices.java:220)
         at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServices.onInit(InternalFcEmployeeServices.java:249)
         at com.sap.pcuigp.xssutils.pernr.FcEmployeeServicesInterface.onInit(FcEmployeeServicesInterface.java:135)
         at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface.onInit(InternalFcEmployeeServicesInterface.java:183)
         at com.sap.pcuigp.xssutils.pernr.wdp.InternalFcEmployeeServicesInterface$External.onInit(InternalFcEmployeeServicesInterface.java:243)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:889)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1082)
         at com.sap.xss.tra.fc.utils.FcTraUtils.onInit(FcTraUtils.java:264)
         at com.sap.xss.tra.fc.utils.wdp.InternalFcTraUtils.onInit(InternalFcTraUtils.java:297)
         at com.sap.xss.tra.fc.utils.FcTraUtilsInterface.onInit(FcTraUtilsInterface.java:122)
         at com.sap.xss.tra.fc.utils.wdp.InternalFcTraUtilsInterface.onInit(InternalFcTraUtilsInterface.java:212)
         at com.sap.xss.tra.fc.utils.wdp.InternalFcTraUtilsInterface$External.onInit(InternalFcTraUtilsInterface.java:428)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:889)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1082)
         at com.sap.xss.tra.fc.allmytrips.FcTraAllMyTrips.onInit(FcTraAllMyTrips.java:247)
         at com.sap.xss.tra.fc.allmytrips.wdp.InternalFcTraAllMyTrips.onInit(InternalFcTraAllMyTrips.java:543)
         at com.sap.xss.tra.fc.allmytrips.FcTraAllMyTripsInterface.onInit(FcTraAllMyTripsInterface.java:115)
         at com.sap.xss.tra.fc.allmytrips.wdp.InternalFcTraAllMyTripsInterface.onInit(InternalFcTraAllMyTripsInterface.java:348)
         at com.sap.xss.tra.fc.allmytrips.wdp.InternalFcTraAllMyTripsInterface$External.onInit(InternalFcTraAllMyTripsInterface.java:420)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:920)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.attachComponentToUsage(FPMComponent.java:889)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.attachComponentToUsage(FPMComponent.java:1082)
         at com.sap.xss.tra.vc.allmytrips.VcTraAllMyTripsInterface.onInit(VcTraAllMyTripsInterface.java:164)
         at com.sap.xss.tra.vc.allmytrips.wdp.InternalVcTraAllMyTripsInterface.onInit(InternalVcTraAllMyTripsInterface.java:205)
         at com.sap.xss.tra.vc.allmytrips.wdp.InternalVcTraAllMyTripsInterface$External.onInit(InternalVcTraAllMyTripsInterface.java:399)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:563)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:437)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:195)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:429)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:700)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:269)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:772)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:707)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
         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:1248)
         at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:353)
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:551)
         at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:595)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:826)
         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:299)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:723)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:261)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:154)
         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:160)
         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)
    I am able to access in QAS but not in DEV or Prod.

    VV,
    This could be case when the payroll for the user XYZ has not be updated till the current period, in which you are trying to access the ESS or MSS tabs.
    You can try this.
    1. Go to the transaction - PC00_mxy_CLSTR
    where xy refers to the MOLGA or the country coding for which the payroll is run.
    Observe there till which period for the user XYZ the payroll has been run.
    2. If the payroll has not been run for the current period.
    Go to transaction PC00_mxy_CALC and by entering the parameters, run the payroll and try doing the same.
    Hope this helps!
    Regards.
    Sandeep Tudumu

  • 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.

  • What is the roles of technical and functional consultants in ESS/MSS area?

    Gurus,
    What is the roles of technical consultants in ESS/MSS area?
    What is the roles of functional consultants in ESS/MSS area?
    Please help me see the differences.
    Thanks,

    Hi Thaman,
    Responsibility of functional consultant in ESS/MSS:- Functional configuration under SPRO > Employee self service and manager self service, then preparation of Functional specification design (FSD) if any deviation from standard SAP, Unit test plan preparation and all functionailty testing
    Responsibility of Technical consultant:- Preparation of Technical specification design document (TSD), activation of work flow and creation of workflow if additional is required. Creatio of form like vacancy requisition form, new position creation form etc.
    Also some kind of technical configuration is there in SPRO for workflow and form
    Regards,
    Purnima

  • Dropdown buttons not working in Portal (UWL, ESS & MSS)

    Hi,
    I am having this problem in the portal. When a user clicks on any dropdown button in Webdynpro applications such as UWL, ESS & MSS in the portal, an error message 'Error: Access is Denied' appears in the left bottom corner of Internet Explorer 6.0, with a yellow triangle sign. The dropdown buttons then appears disabled and nothing happens when they are selected. I will appreciate if you can provide suggestions as to why this is happening and how to solve it.
    Thanks
    John

    Hi John
    Please ensure you have the latest patch for your JTECHS and JTECHF SP level
    If this does not resolve the issue please ensure you have the correct Netweaver stack (including JTECHS and JTECHF) for you ESS/MSS SP levels - see the following wiki for help identifying which Netweaver SP levels are recommended for each ESS/MSS SP level
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/profile/marcio+leoni
    --->HOW TO GET RID OF SP STACK MISMATCH ISSUES
    If the issue continues please ensure you browser client and version is suitable for this version of ESS/MSS
    via the PAM www.service.sap.com/swdc
    Best wishes
    Stuart

Maybe you are looking for