SAP ESS Configuration Problem

Hello ,
   I have made a Leave request workflow. I tried to execute the "Leave Request : Check" which comes under the SPRO t-code
   { IMG -> Personnel Mgmt -> ESS -> Service Specific Setting -> Working Time -> Leave Request -> Processing Processess -> Define Report Variants and Bakgrnd Processing}.
After I execute my workflow , I want to see the requests made by certain holders , in "Leave Request : Check" . But I see the screen blank when I execute by entering a specific Personel number. am I missing a part in the ess configuration ? Please help ....

how did you create the leave for the employees ? By just triggering the workflow manually? Because that is not going to work. You have to trigger them from the portal or via the test application in transaction PTARQ

Similar Messages

  • ESS Configuration problem - Salary statement

    I have configured the ESS as per the documentations.
    We have ECC 6.0 with EA-HR SP03 and XSS SP6.
                The following JCO connections are all setup to ECC 6.0 back end and  are pinging and tested successfully, even though not all are required.
                SAP_R3_Financials_MetaData  
                SAP_R3_HumanResources  
                SAP_R3_HumanResources_Metadata  
                SAP_R3_SelfServiceGenerics
                SAP_R3_SelfServiceGenerics_MetaData 
                SAP_R3_SelfServiceGenerics_MetaDataFIN 
                SAP_R3_SelfServiceGenericsFIN 
                SAP_R3_Travel  
                SAP_R3_Travel_MetaData
               WD_MODELDATA_DEST
                WD_RFC_METADATA_DEST
                WD_RSDAS_MODELDATA_DEST 
            WD_RSDAS_RFC_METADATA_DEST.
    The System Aliases  SAP_ECC_HumanResources and SAP_WebDynpro_XSS are defined with WAS properties.
               There are no authorization issues as the user is SAP_ALL at ECC and superuser at the portal.
    Employee search and Maintain own data  services are working fine with default settings. 
    But while trying to view the Salary Statement (Paycheck Inquiry Service) the error below comes up.
    The full exception chain is as below.
    java.lang.ArrayIndexOutOfBoundsException: -1
            at com.sap.mw.jco.JCO$Record.getString(JCO.java:12623)
            at com.sap.aii.proxy.framework.core.JcoBaseTypeData.getElementValueAsString(JcoBaseTypeData.java:669)
            at com.sap.tc.webdynpro.modelimpl.dynamicrfc.DynamicRFCModelClass.getAttributeValueAsString(DynamicRFCModelClass.java:409)
            at com.sap.xss.hr.rep.model.rfwmodel.Hrxss_Ser_Rfw_Rfc_Get_Form_Output.getHeight(Hrxss_Ser_Rfw_Rfc_Get_Form_Output.java:179)
            at com.sap.xss.hr.rep.fcrfw.FcRepFramework.callRfcGetForm(FcRepFramework.java:395)
            at com.sap.xss.hr.rep.fcrfw.FcRepFramework.processFollowingActions(FcRepFramework.java:484)
            at com.sap.xss.hr.rep.fcrfw.FcRepFramework.callRfcExecAction(FcRepFramework.java:378)
            at com.sap.xss.hr.rep.fcrfw.FcRepFramework.initModel(FcRepFramework.java:292)
            at com.sap.xss.hr.rep.fcrfw.wdp.InternalFcRepFramework.initModel(InternalFcRepFramework.java:256)
            at com.sap.xss.hr.rep.fcrfw.FcRepFrameworkInterface.initModel(FcRepFrameworkInterface.java:136)
            at com.sap.xss.hr.rep.fcrfw.wdp.InternalFcRepFrameworkInterface.initModel(InternalFcRepFrameworkInterface.java:198)
            at com.sap.xss.hr.rep.fcrfw.wdp.InternalFcRepFrameworkInterface$External.initModel(InternalFcRepFrameworkInterface.java:258)
            at com.sap.xss.hr.rem2.selection.VcRem2Selection.onInit(VcRem2Selection.java:245)
            at com.sap.xss.hr.rem2.selection.wdp.InternalVcRem2Selection.onInit(InternalVcRem2Selection.java:249)
            at com.sap.xss.hr.rem2.selection.VcRem2SelectionInterface.onInit(VcRem2SelectionInterface.java:161)
            at com.sap.xss.hr.rem2.selection.wdp.InternalVcRem2SelectionInterface.onInit(InternalVcRem2SelectionInterface.java:144)
            at com.sap.xss.hr.rem2.selection.wdp.InternalVcRem2SelectionInterface$External.onInit(InternalVcRem2SelectionInterface.java:220)
            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:345)
            at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:668)
            at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:268)
            at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:725)
            at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:661)
            at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
            at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
            at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
            at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:739)
            at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:208)
            at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1240)
            at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:340)
            at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:538)
            at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:582)
            at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:811)
            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:137)
            at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:344)
            at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
            at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:298)
            at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:677)
            at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
            at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
            at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
            at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
            at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
            at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
            at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
            at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
            at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
            at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
            at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
            at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
            at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
            at java.security.AccessController.doPrivileged(Native Method)
            at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
            at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Could you please help me out.
    thanks & regards
    K. Muhammed Ali

    Mohammed,
    Did you ever get an answer to this ESS problem? We are having the same problem now.
    Thanks,
    Dave

  • SAP Recruitment configuration problem

    Hi all,
    I am working on an SAP recruitment project version 4.6C.
    I need to get some custom texts into applicant correspondance. For this, I got to see some documentation in the configuration explaining to create a new module pool program and so.
    now the problem is I couldnot figure out where to replace this custom program.
    I would be glad if anyone can take a look and let me know. At the location where i found this documentation there is no execute button for entries.
    Thanks in advance.
    regards,
    Bharat

    Hi
    Did anyone check it in SAP 4.6C system.Pts. guranteed.
    Regards
    Bharat

  • CMS import  for SAP ESS component(SP 15) fails with fatal error.

    Hi,
    We are working on EP 7.0 SP 15. We have a requirement for changes to be made to SAP delivered ESS codes. We have set up the NWDI and and from the checkin tabn of CMS, the components SAP-JEE (7.00 SP18 ), SAP_JTECHS(7.00 SP18 ), SAP_PCUI-GP(SP 18), EP_BUILDT (7.00 SP18 )and SAP_BUILDT (7.00 SP18 )have been imported successfully to the development tab. But when we try to import the SAP ESS 600(SP level 15) from Checkin tab to the Development tab, the import fails. The exception chain as checked by clicking Details button in teh Develepoment tab of CMS shows the details as:
    20090610145206 Info   :Starting Step Repository-check at 2009-06-10 14:52:06.0283 +5:00
    20090610145206 Info   :Component:sap.com/SAP_ESS
    20090610145206 Info   :Version  :MAIN_ERP05PAT_C.20090427083436
    20090610145206 Info   :1. propagation request is of type TCSSoftwareComponent
    20090610145206 Info   :Propagatable:d647b419330511de9f130030057116fe exists allready in the repository. No import necessary.
    20090610145232 Fatal  :VcmFailure received
    20090610145232 Fatal  :caused by Exception:com.tssap.dtr.client.lib.deltavlib.VcmFailure: Internal Server Error [(pre||post)-condition failed: Internal Server Error]:Internal Server Error [(pre||post)-condition failed: Internal Server Error]
    com.tssap.dtr.client.lib.deltavlib.VcmFailure: Internal Server Error [(pre||post)-condition failed: Internal Server Error]
         at com.tssap.dtr.client.lib.deltavlib.impl.AbstractCommand.checkedExecute(AbstractCommand.java:196)
         at com.tssap.dtr.client.lib.deltavlib.impl.VersionSet.integrate(VersionSet.java:160)
         at com.tssap.dtr.client.lib.deltavlib.impl.VersionSet.integrate(VersionSet.java:148)
         at com.sap.cms.tcs.client.DTRCommunicator.integrateChangelist(DTRCommunicator.java:544)
         at com.sap.cms.tcs.core.RepositoryImportTask.integrateResource(RepositoryImportTask.java:816)
         at com.sap.cms.tcs.core.RepositoryImportTask.processRepositoryImport(RepositoryImportTask.java:367)
         at com.sap.cms.tcs.core.RepositoryImportTask.process(RepositoryImportTask.java:651)
         at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
         at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
         at com.sap.cms.tcs.core.TCSManager.checkPropagationRequests(TCSManager.java:517)
         at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:179)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:500)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImportCheck(ImportQueueHandler.java:130)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImportCheck(CmsTransportProxyBean.java:720)
         at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImportCheck(LocalCmsTransportProxyLocalObjectImpl0_0.java:1844)
         at com.sap.cms.ui.wl.Custom1.ImportCheck(Custom1.java:9968)
         at com.sap.cms.ui.wl.wdp.InternalCustom1.wdInvokeEventHandler(InternalCustom1.java:3156)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingCustomController.invokeEventHandler(DelegatingCustomController.java:89)
         at com.sap.tc.webdynpro.clientserver.event.CustomEventProcessor.handleServerEvent(CustomEventProcessor.java:45)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleServiceEvent(WindowPhaseModel.java:361)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:128)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processPhaseLoop(WebDynproWindow.java:345)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:152)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    20090610145232 Fatal  :caused by 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:563)
         at com.sap.cms.tcs.core.RepositoryImportTask.integrateResource(RepositoryImportTask.java:816)
         at com.sap.cms.tcs.core.RepositoryImportTask.processRepositoryImport(RepositoryImportTask.java:367)
         at com.sap.cms.tcs.core.RepositoryImportTask.process(RepositoryImportTask.java:651)
         at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
         at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)
         at com.sap.cms.tcs.core.TCSManager.checkPropagationRequests(TCSManager.java:517)
         at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:179)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:500)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImportCheck(ImportQueueHandler.java:130)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImportCheck(CmsTransportProxyBean.java:720)
         at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImportCheck(LocalCmsTransportProxyLocalObjectImpl0_0.java:1844)
         at com.sap.cms.ui.wl.Custom1.ImportCheck(Custom1.java:9968)
         at com.sap.cms.ui.wl.wdp.InternalCustom1.wdInvokeEventHandler(InternalCustom1.java:3156)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingCustomController.invokeEventHandler(DelegatingCustomController.java:89)
         at com.sap.tc.webdynpro.clientserver.event.CustomEventProcessor.handleServerEvent(CustomEventProcessor.java:45)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleServiceEvent(WindowPhaseModel.java:361)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:128)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processPhaseLoop(WebDynproWindow.java:345)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:152)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
    20090610145232 Info   :Step Repository-check ended with result 'fatal error' ,stopping execution at 2009-06-10 14:52:32.0796 +5:00
    The above log is displayed when I click the import -check button on the development tab of CMS. The same error is displayes when the import button is clicked  with only the last sentence changed to:
    Step Repository-check ended with result 'fatal error'
    Can anyone help me on this.... ?
    Thanks,
    Sonali.
    Edited by: Sonali M S on Jun 10, 2009 1:16 PM

    Hi Bala,
    The problem still remails even after making changes in Visual Admin as per the thread Re: Assembly finished with errors
    Also from http://<server>:<port>/nwa we have run the configuration task for "Initial setup of functional unit Development Infrastructure (DI all-in-one)" and there we donot have the option for individual CBS, CMS and DTR installations as told in the thread.
    The other thread import into devlopment failed tells about the SAP note: 988010 iin which it is mentioned that this has been fixed in SP 11 for 7.00 version. We are already on SP 18. So it is assumable that this thing has already been fixed.
    Can there be any other reason for this?
    Thanks,
    Sonali.

  • SAP ESS Family Member/dependants   java.lang.NullPointerException error

    Hi
    We are have the following problem when trying to edit or add a new child dependent fro Family member dependents.  In the backend it works fine but on ess it dumps.  There is no st22.  we have looked all the notes and the previous sdn thread for this and applied the relevant patches as suggested in the notes.  Have any of you encounter this problem and how did you guys resolve it??
    The initial exception that caused the request to fail, was:
       java.lang.NullPointerException
        at com.sap.xss.per.vc.detailfooter.VcPersInfoDetailFooter.onBeforeOutput(VcPersInfoDetailFooter.java:229)
        at com.sap.xss.per.vc.detailfooter.wdp.InternalVcPersInfoDetailFooter.onBeforeOutput(InternalVcPersInfoDetailFooter.java:188)
        at com.sap.xss.per.vc.detailfooter.VcPersInfoDetailFooterInterface.onBeforeOutput(VcPersInfoDetailFooterInterface.java:144)
        at com.sap.xss.per.vc.detailfooter.wdp.InternalVcPersInfoDetailFooterInterface.onBeforeOutput(InternalVcPersInfoDetailFooterInterface.java:136)
        at com.sap.xss.per.vc.detailfooter.wdp.InternalVcPersInfoDetailFooterInterface$External.onBeforeOutput(InternalVcPersInfoDetailFooterInterface.java:212)
        ... 55 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; InfoPath.3; .NET CLR 1.1.4322)
    Version null
    DOM version null
    Client Type msie7
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0104.20090324111057.0000 (release=NW701_04_REL, buildtime=2009-06-12:08:35:57[UTC], changelist=58858, host=pwdfm106), build date: Mon Dec 07 22:38:32 GMT+02:00 2009
    J2EE Engine 7.01 PatchLevel 97888.
    Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_30-b04, vendor: Sun Microsystems Inc.
    Operating system Windows 2003, version: 5.2, architecture: amd64
    Session & Other
    Session Locale en_ZA
    Time of Failure Tue Jun 28 07:52:35 GMT+02:00 2011 (Java Time: 1309240355891)
    Web Dynpro Code Generation Infos
    sap.com/pb
    SapDictionaryGenerationCore 7.0108.20100922154735.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:22:16[UTC], changelist=96611, host=pwdfm319.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0108.20100922154735.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:22:20[UTC], changelist=96611, host=pwdfm319.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0108.20100922154919.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:16:25[UTC], changelist=96647, host=pwdfm319.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0108.20100922160824.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:26:26[UTC], changelist=96858, host=pwdfm319.wdf.sap.corp)
    SapMetamodelCommon 7.0108.20100922155425.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:17:08[UTC], changelist=96742, host=pwdfm319.wdf.sap.corp)
    SapMetamodelCore 7.0108.20100922155425.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:17:05[UTC], changelist=96742, host=pwdfm319.wdf.sap.corp)
    SapMetamodelDictionary 7.0108.20100922154738.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:20:28[UTC], changelist=96612, host=pwdfm319.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0108.20100922160830.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:24:08[UTC], changelist=96859, host=pwdfm319.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0108.20101115095814.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:31:20[UTC], changelist=99321, host=pwdfm319)
    SapWebDynproGenerationCore 7.0108.20100922160824.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:26:29[UTC], changelist=96858, host=pwdfm319.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0108.20101115095814.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:31:20[UTC], changelist=99321, host=pwdfm319)
    sap.com/tcwddispwda
    No information available null
    sap.com/pb_api
    SapDictionaryGenerationCore 7.0108.20100922154735.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:22:16[UTC], changelist=96611, host=pwdfm319.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0108.20100922154735.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:22:20[UTC], changelist=96611, host=pwdfm319.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0108.20100922154919.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:16:25[UTC], changelist=96647, host=pwdfm319.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0108.20100922160824.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:26:26[UTC], changelist=96858, host=pwdfm319.wdf.sap.corp)
    SapMetamodelCommon 7.0108.20100922155425.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:17:08[UTC], changelist=96742, host=pwdfm319.wdf.sap.corp)
    SapMetamodelCore 7.0108.20100922155425.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:17:05[UTC], changelist=96742, host=pwdfm319.wdf.sap.corp)
    SapMetamodelDictionary 7.0108.20100922154738.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:20:28[UTC], changelist=96612, host=pwdfm319.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0108.20100922160830.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:24:08[UTC], changelist=96859, host=pwdfm319.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0108.20101115095814.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:31:20[UTC], changelist=99321, host=pwdfm319)
    SapWebDynproGenerationCore 7.0108.20100922160824.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:26:29[UTC], changelist=96858, host=pwdfm319.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0108.20101115095814.0000 (release=NW701_08_REL, buildtime=2010-12-06:09:31:20[UTC], changelist=99321, host=pwdfm319)
    sap.com/tcwdcorecomp
    No information available null
    Detailed Error Information
    Detailed Exception Chain
    java.lang.NullPointerException
         at com.sap.xss.per.vc.detailfooter.VcPersInfoDetailFooter.onBeforeOutput(VcPersInfoDetailFooter.java:229)
         at com.sap.xss.per.vc.detailfooter.wdp.InternalVcPersInfoDetailFooter.onBeforeOutput(InternalVcPersInfoDetailFooter.java:188)
         at com.sap.xss.per.vc.detailfooter.VcPersInfoDetailFooterInterface.onBeforeOutput(VcPersInfoDetailFooterInterface.java:144)
         at com.sap.xss.per.vc.detailfooter.wdp.InternalVcPersInfoDetailFooterInterface.onBeforeOutput(InternalVcPersInfoDetailFooterInterface.java:136)
         at com.sap.xss.per.vc.detailfooter.wdp.InternalVcPersInfoDetailFooterInterface$External.onBeforeOutput(InternalVcPersInfoDetailFooterInterface.java:212)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.callOnBeforeOutput(FPMComponent.java:603)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doProcessEvent(FPMComponent.java:569)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.doEventLoop(FPMComponent.java:438)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.access$600(FPMComponent.java:78)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPM.raiseEvent(FPMComponent.java:938)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent$FPMProxy.raiseEvent(FPMComponent.java:1101)
         at com.sap.xss.per.vc.overview.VcPersInfoOverview.create(VcPersInfoOverview.java:225)
         at com.sap.xss.per.vc.overview.wdp.InternalVcPersInfoOverview.create(InternalVcPersInfoOverview.java:161)
         at com.sap.xss.per.vc.overview.BizCardsView.onActionNew(BizCardsView.java:164)
         at com.sap.xss.per.vc.overview.wdp.InternalBizCardsView.wdInvokeEventHandler(InternalBizCardsView.java:172)
         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:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869)
         at com.sap.tc.webdynpro.portal.pb.impl.localwd.LocalApplicationProxy.sendDataAndProcessAction(LocalApplicationProxy.java:77)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1363)
         at com.sap.portal.pb.PageBuilder.SendDataAndProcessAction(PageBuilder.java:327)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:873)
         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:321)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

    You need the latest SP for resolving this ie front end version. Please check what version you are on and accordingly you need
    to patch your system
    1. http://service.sap.com/
    2. SAP Support Portal    - > Software Download
    3. Download   > Support packages and patches   > Entry by application
       group
    4. SAP Application components
    5. SAP ERP
    6. SAP ERP ENHANCE PACKAGE
    7. EHP4 FOR SAP ERP 6.0 / NW7.01
    8. Entry by component
    9. SAP XSS (Self Services)
    10.SAP ESS 603 (# OS independent)
    download the below version-
    SAPESS06_8-20002355.SCA SP06 for SAP ESS 603
    Now extract the below file from the downloaded SAP_ESS .sca
    -ess~xx
    Now Logon to SDM,go to deployment tab and open the deployment
    configuration tab -
    choose the radio button
    -Update deployed SDA/SCA that have any version
    -deploy -ess~xx sda  files.
    It  will resolve the issue.
    Edited by: Siddharth Rajora on Jun 28, 2011 5:17 PM

  • Customizing SAP ESS Portal Role

    Hi,
    I need to customize the ESS portal screens.  For example, I need to view "Employee Search" tab but not the "Working Time" tab.  Is advisable to modify the ESS Worksets provided by SAP directly and remove the workesets, pages that I do not need? 
    The approach I took was to create a new role and workset and include the SAP pages I needed.  However, this gives me problems when I acess the iviews.  For example, when I click on the "Who's Who" link, nothing happens.
    Can anyone help?
    Thanks.

    Sudhir,
    You mentioned to "change the Role location of each resource in backend ESS configuration".  Which resources do I change. 
    For e.g.,  I created an "Employee Self-Service" role and an "Employee Self-Service" workset.  Now in my "Employee Self-Service" workset, I referenced SAP's "Employee Search" workset.  What do I need to change?
    Thanks,
    Basant
    > You need to copy standard role and then put
    > iviews/pages in concerned order/page.
    > moreover you ned to change Role location of each
    > resource in backend ESS configuration.
    >
    > Well removal of certain tabs can be achieved using
    > service/Subareas config in ESS. Please check IMG ESS
    > config node for more details.
    >
    > Hope this helps.
    > Regards,
    > Sudhir

  • Error in Deployment of SAP ESS 100 SP16 ess/au/addr

    Hello Gurus
    Greetings !..
    I am trying to Deploy SAP ESS 100 SP16 for Netweaver 2004s using SDM but getting error while i deploy in the phase ess/au/addr.
    Please check for the log below if any one can helpout soon....
    May 22, 2007 10:16:50... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:16:50... Info: Finished successfully: development component 'ess/at/fam'/'sap.com'/'MAIN_xss04VAL_C'/'680352'/'0', grouped by
    May 22, 2007 10:16:50... Info: Starting to save the repository
    May 22, 2007 10:16:52... Info: Finished saving the repository
    May 22, 2007 10:17:04... Info: Starting: Update: Selected development component 'ess/at/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'680388'/'0' updates currently deployed development component 'ess/at/pdata'/'sap.com'/'MAIN_ERP05VAL_C'/'766644'/'0'.
    May 22, 2007 10:17:04... Info: SDA to be deployed: E:\usr\sap\SND\JC01\SDM\root\origin\sap.com\ess\at\pdata\MAIN_xss04VAL_C\0\680388\sap.com_essatpdata.sda
    May 22, 2007 10:17:04... Info: Software type of SDA: J2EE
    May 22, 2007 10:17:04... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:17:06... Info: Begin of log messages of the target system:
    07/05/22 22:17:04 - ***********************************************************
    07/05/22 22:17:04 - Start updating EAR file...
    07/05/22 22:17:04 - start-up mode is lazy
    07/05/22 22:17:04 - EAR file updated successfully for 78ms.
    07/05/22 22:17:04 - Start updating...
    07/05/22 22:17:04 - EAR file uploaded to server for 219ms.
    07/05/22 22:17:05 - Successfully updated. Update took 734ms.
    07/05/22 22:17:05 - Deploy Service status:
    07/05/22 22:17:05 - Application : sap.com/essatpdata
    07/05/22 22:17:05 -
    07/05/22 22:17:05 - sap.com/essatpdata - WEBDYNPRO
    07/05/22 22:17:05 - ***********************************************************
    May 22, 2007 10:17:06... Info: End of log messages of the target system.
    May 22, 2007 10:17:06... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:17:06... Info: Finished successfully: development component 'ess/at/pdata'/'sap.com'/'MAIN_xss04VAL_C'/'680388'/'0', grouped by
    May 22, 2007 10:17:07... Info: Starting to save the repository
    May 22, 2007 10:17:08... Info: Finished saving the repository
    May 22, 2007 10:17:21... Info: Starting: Initial deployment: Selected development component 'ess/au'/'sap.com'/'MAIN_xss04VAL_C'/'681439'/'0' will be deployed.
    May 22, 2007 10:17:21... Info: SDA to be deployed: E:\usr\sap\SND\JC01\SDM\root\origin\sap.com\ess\au\MAIN_xss04VAL_C\0\681439\sap.com_ess~au.sda
    May 22, 2007 10:17:21... Info: Software type of SDA: J2EE
    May 22, 2007 10:17:21... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:17:25... Info: Begin of log messages of the target system:
    07/05/22 22:17:21 - ***********************************************************
    07/05/22 22:17:21 - Start updating EAR file...
    07/05/22 22:17:21 - start-up mode is lazy
    07/05/22 22:17:21 - EAR file updated successfully for 188ms.
    07/05/22 22:17:21 - Start deploying ...
    07/05/22 22:17:22 - EAR file uploaded to server for 859ms.
    07/05/22 22:17:24 - Successfully deployed. Deployment took 2547ms.
    07/05/22 22:17:24 - Application : sap.com/ess~au
    07/05/22 22:17:24 -
    07/05/22 22:17:24 - sap.com/ess~au - WEBDYNPRO
    07/05/22 22:17:24 - ***********************************************************
    May 22, 2007 10:17:25... Info: End of log messages of the target system.
    May 22, 2007 10:17:25... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:17:25... Info: Finished successfully: development component 'ess/au'/'sap.com'/'MAIN_xss04VAL_C'/'681439'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.11.0.20060117105520''/'0'
    May 22, 2007 10:17:25... Info: Starting to save the repository
    May 22, 2007 10:17:27... Info: Finished saving the repository
    May 22, 2007 10:17:39... Info: Starting: Initial deployment: Selected development component 'ess/au/addr'/'sap.com'/'MAIN_xss04VAL_C'/'681471'/'0' will be deployed.
    May 22, 2007 10:17:39... Info: SDA to be deployed: E:\usr\sap\SND\JC01\SDM\root\origin\sap.com\ess\au\addr\MAIN_xss04VAL_C\0\681471\sap.com_essauaddr.sda
    May 22, 2007 10:17:39... Info: Software type of SDA: J2EE
    May 22, 2007 10:17:39... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:17:40... Info: Begin of log messages of the target system:
    07/05/22 22:17:39 - ***********************************************************
    07/05/22 22:17:39 - Start updating EAR file...
    07/05/22 22:17:39 - start-up mode is lazy
    07/05/22 22:17:39 - EAR file updated successfully for 94ms.
    07/05/22 22:17:39 - Start deploying ...
    07/05/22 22:17:40 - EAR file uploaded to server for 297ms.
    07/05/22 22:17:40 - ERROR: Not deployed. Deploy Service returned ERROR:
    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?
    at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:567)
    at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
    at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
    at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
    at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
    at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
    at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
    at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
    at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sap.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?
    at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1016)
    at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606)
    at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:321)
    at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
    at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3184)
    at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:552)
    ... 10 more
    For detailed information see the log file of the Deploy Service.
    07/05/22 22:17:40 - ***********************************************************
    May 22, 2007 10:17:40... Info: End of log messages of the target system.
    May 22, 2007 10:17:40... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    May 22, 2007 10:17:40... Error: Aborted: development component 'ess/au/addr'/'sap.com'/'MAIN_xss04VAL_C'/'681471'/'0', grouped by software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.11.0.20060117105520''/'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)
    May 22, 2007 10:17:40... Info: Starting to save the repository
    May 22, 2007 10:17:42... Info: Finished saving the repository
    May 22, 2007 10:17:54... Info: Starting: Initial deployment: Selected software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.11.0.20060117105520''/'0' will be deployed.
    May 22, 2007 10:17:54... Error: Aborted: software component 'SAP_ESS'/'sap.com'/'MAIN_xss04VAL_C'/'1000.100.0.11.0.20060117105520''/'0':
    Failed deployment of SDAs:
    development component 'ess/au/addr'/'sap.com'/'MAIN_xss04VAL_C'/'681471'/'0' : aborted
    Please, look at error logs above for more information!
    Hope for a prompt response.
    Reply awaited urgently....
    Thanks in Advance
    Thanks & Best Regards
    Ashish

    Hello Gerard Christopher
    Yes i got the problem solved, actually SAP ESS 600 & SAP MSS 600 are the component we have to use. As we were on WAS 7.00 and ERP 2005 so
    SAP ESS 600
    SAP MSS 600
    SAP PSS 600
    SAP ASR 600
    SAP PCUI_GP 600
    Try with this you will able to solve.
    Thanks & best Regards
    Ashish

  • Integration Directory(Configuration) Problem

    Hi All,
    I am facing one Probelm. I am working one the client through Citrix. I am not able to open Integration Directory(Configuration Problem) . In onsite it's working fine. Reming all other applications(Integartion Repository and SLD and Runtime work bench) are working fine.
    if I open Integration Directory i am getting this messge.
    <jnlp spec="1.0+" codebase="http://filp55.group.upm-kymmene.com:50100/dir">
        <information>
            <title>Integration Builder</title>
            <vendor>SAP AG</vendor>
            <homepage href="http://www.sap.com" />
            <description type="one-line">Directory</description>
            <description type="short">Directory</description>
            <description type="tooltip">Directory</description>
            <icon hight="64" href="start/graphics/sap6464.gif" type="splash" width="64" />
            <icon hight="32" href="start/graphics/SAP3232.gif" width="32" />
        </information>
        <security>
            <all-permissions />
        </security>
        <resources>
            <j2se version="1.4+" initial-heap-size="32m" max-heap-size="1024m" />
            <jar href="directory/aii_ibdir_client.jar" />
            <jar href="directory/aii_ibdir_core.jar" />
            <jar href="directory/aii_ibdir_sbeans.jar" />
            <jar href="directory/aii_ibdir_rb.jar" />
            <jar href="directory/aii_ib_client.jar" />
            <jar href="directory/aii_ib_core.jar" />
            <jar href="directory/aii_ib_sbeans.jar" />
            <jar href="directory/aii_ib_rb.jar" />
            <jar href="directory/aii_util_icons.jar" />
            <jar href="directory/aii_util_swing.jar" />
            <jar href="directory/aii_util_xml.jar" />
            <jar href="directory/aii_util_xsd.jar" />
            <jar href="directory/aii_utilxi_misc.jar" />
            <jar href="directory/aii_util_rb.jar" />
            <jar href="directory/clientaii_ib_sbeans.jar" />
            <jar href="directory/clientaii_ibdir_sbeans.jar" />
            <jar href="directory/frog.jar" />
            <jar href="directory/focus14.jar" />
            <jar href="directory/sapxmltoolkit.jar" />
            <jar href="directory/jta.jar" />
            <jar href="directory/ejb20.jar" />
            <jar href="directory/exception.jar" />
            <jar href="directory/logging.jar" />
            <jar href="directory/guidgenerator.jar" />
            <jar href="directory/jperflib.jar" />
            <jar href="directory/sapni.jar" />
            <jar href="directory/sapj2eeclient.jar" />
            <property name="sap.theme" value="Streamline" />
            <property name="jnlp.log.initialConfiguration" value="FILE, SIMPLE" />
        <property name="jnlp.com.sap.aii.ib.client.properties" value="com.sap.aii.ib.client., com.sap.aii.ib.core., com.sap.aii.util.xml., com.sap.aii.connect., com.sap.aii.repository.mapping.additionaltypes, com.sap.aii.docu., com.sap.aii.ibrep.core., com.sap.aii.ibdir.core.*" /><property name="jnlp.com.sap.aii.connect.integrationserver.r3.sysnr" value="01" /><property name="jnlp.com.sap.aii.connect.landscape.contextroot" value="sld" /><property name="jnlp.com.sap.aii.connect.cr.name" value="filp40.group.upm-kymmene.com" /><property name="jnlp.com.sap.aii.ib.client.content.languages" value="EN,DE" /><property name="jnlp.com.sap.aii.connect.repository.contextroot" value="rep" /><property name="jnlp.com.sap.aii.ib.client.login.languages" value="EN,DE" /><property name="jnlp.com.sap.aii.connect.directory.rmiport" value="50104" /><property name="jnlp.com.sap.aii.connect.cr.contextroot" value="sld" /><property name="jnlp.com.sap.aii.connect.rwb.r3.client" value="790" /><property name="jnlp.com.sap.aii.connect.directory.contextroot" value="dir" /><property name="jnlp.com.sap.aii.connect.rwb.contextroot" value="rwb" /><property name="jnlp.com.sap.aii.connect.landscape.httpsport" value="@com.sap.aii.server.httpsport.lcr@" /><property name="jnlp.com.sap.aii.connect.repository.rmiport" value="50104" /><property name="jnlp.com.sap.aii.connect.repository.httpport" value="50100" /><property name="jnlp.com.sap.aii.connect.directory.name" value="filp55.group.upm-kymmene.com" /><property name="jnlp.com.sap.aii.connect.cr.httpsport" value="@com.sap.aii.server.httpsport.cr@" /><property name="jnlp.com.sap.aii.connect.repository.name" value="filp55.group.upm-kymmene.com" /><property name="jnlp.com.sap.aii.connect.integrationserver.contextroot" value="run" /><property name="jnlp.com.sap.aii.connect.integrationserver.name" value="filp55.group.upm-kymmene.com" /><property name="jnlp.com.sap.aii.connect.rwb.httpsport" value="@com.sap.aii.connect.rwb.httpsport@" /><property name="jnlp.com.sap.aii.connect.landscape.httpport" value="50000" /><property name="jnlp.com.sap.aii.docu.languages" value="null" /><property name="jnlp.com.sap.aii.ib.client.jnlp.j2se.initialheapsize" value="32m" /><property name="jnlp.com.sap.aii.util.xml.parserFactory" value="com.sap.engine.lib.jaxp.SAXParserFactoryImpl" /><property name="jnlp.com.sap.aii.connect.directory.httpport" value="50100" /><property name="jnlp.com.sap.aii.connect.directory.httpsport" value="@com.sap.aii.server.httpsport.directory@" /><property name="jnlp.com.sap.aii.connect.integrationserver.r3.httpport" value="8001" /><property name="jnlp.com.sap.aii.connect.rwb.name" value="filp55.group.upm-kymmene.com" /><property name="jnlp.com.sap.aii.connect.integrationserver.r3.client" value="790" /><property name="jnlp.com.sap.aii.connect.cr.httpport" value="50000" /><property name="jnlp.com.sap.aii.connect.landscape.name" value="filp40.group.upm-kymmene.com" /><property name="jnlp.SAPMYNAME" value="filp55_GTX_01" /><property name="jnlp.com.sap.aii.connect.rwb.httpport" value="50100" /><property name="jnlp.com.sap.aii.docu.url" value="null" /><property name="jnlp.com.sap.aii.ib.client.applicationname.directory" value="sap.com/com.sap.xi.directory/" /><property name="jnlp.com.sap.aii.util.xml.transformerFactory" value="com.sap.engine.lib.jaxp.TransformerFactoryImpl" /><property name="jnlp.com.sap.aii.ib.client.applicationname.repository" value="sap.com/com.sap.xi.repository/" /><property name="jnlp.com.sap.aii.ib.client.login.InitialContextFactory" value="com.sap.engine.services.jndi.InitialContextFactoryImpl" /><property name="jnlp.com.sap.aii.connect.integrationserver.httpport" value="50100" /><property name="jnlp.client" value="true" /><property name="jnlp.com.sap.aii.connect.repository.httpsport" value="@com.sap.aii.server.httpsport.repository@" /><property name="jnlp.com.sap.aii.ib.client.jnlp.j2se.maxheapsize" value="1024m" /><property name="jnlp.com.sap.aii.connect.integrationserver.httpsport" value="@com.sap.aii.connect.integrationserver.httpsport@" /><property name="jnlp.com.sap.aii.connect.integrationbuilder.startpage.url" value="rep/start/index.jsp" /><property name="jnlp.com.sap.aii.connect.integrationserver.r3.httpsport" value="@com.sap.aii.connect.integrationserver.r3.httpsport@" /><property name="jnlp.com.sap.aii.connect.rwb.r3.sysnr" value="01" /><property name="jnlp.com.sap.aii.util.xml.schemaValidator" value="com.sap.engine.lib.schema.validator.SchemaValidator" /><property name="jnlp.rc.release" value="7_00" /><property name="jnlp.rc.applname" value="DIRECTORY" /><property name="jnlp.rc.supportpackage" value="09" /><property name="jnlp.rc.synctime" value="${sync.time}" /></resources>
        <application-desc main-class="com.sap.aii.ibdir.gui.appl.ApplicationImpl">
            <argument>webstart</argument>
        </application-desc>
    </jnlp>
    Please help me on this..........
    Thanks in Advacne.
    Regards,
    Chandra

    Hello,
    1)
    May be the problem is a network connectivity issue. Do one thing copy the "cahce" folder from some other client PC(which has successfully opened IR and ID) to your client PC. The folder resides in "C:Documents and Settings<yourUserProfile>Application DataSunJavaDeploymentjavaws".
    Copy "cache" folder to your client PC under the above path.
    /people/shabarish.vijayakumar/blog/2006/02/13/unable-to-open-iresrid-xipipi-71-updated-for-pi-71-support
    https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1688 [original link is broken] [original link is broken] [original link is broken]
    2) Go to http://filp55.group.upm-kymmene.com:50100/rep/
    Click on Administration -> Java™ Web Start -> Java™ Web Start Administration ->
    Try
    1. Re-initialization (then try logging)
    2. Re-initialization and force-signing (then try logging)
    3. Delete lock (then try logging)
    Do this for IR and ID tabs.
    3) Check can be a firewall issue.
    4) Check wether sufficient roles have been assigned -> Tcode -> SU01 -> roles tab. These roles need to be assigned to your username
    SAP_BC_AI_LANDSCAPE_DB_RFC
    SAP_SLD_CONFIGURATOR
    SAP_SLD_DEVELOPER
    SAP_XI_BPE_CONFIGURATOR_ABAP
    SAP_XI_BPE_MONITOR_ABAP
    SAP_XI_DEVELOPER
    SAP_XI_DEVELOPER_ABAP
    SAP_XI_DEVELOPER_J2EE
    SAP_XI_MONITOR
    SAP_XI_MONITOR_ABAP
    SAP_XI_MONITOR_J2EE
    <b>*******************Reward,if found useful</b>
    Edited by: BVS on May 7, 2008 3:01 PM

  • Could not start the app due to a configuration problem - Launchpad issue

    Hi,
    When I try to launch a custom app from Fiori Launchpad I get an error could not start app due to configuration problem. Error 500- Internal Server Error.
    App works correctly when I try to execute via URL http://XXX/sap/bc/ui5_ui5/sap/zmyfioriui5_v11.
    Screenshot of Chrome debugging and lpd_cust attached.
    It seems problem with ResolveLink but unable to conclude.
    Any Suggestion how to proceed.
    Thanks,
    Mayank

    Hi Mayank,
    Few modifications :
    For additional information field : ".component" at the end is not required.
    Only keep : SAPUI5.Component=sap.ui.demo.myFiori
    Check this screenshot :
    Also, please don't keep Semantic object name and application alias as same name i.e. ymyfioriui5_v11. Its very confusing.
    If above doesn't solve, please confirm below :
    ZXXXLPD is your launchpad role in LPD_CUST tcode.
    Please use TRANSACTIONAL instead of transactional (might be case sensitive)
    Show your semantic object "ymyfioriui5_v11" created in /UI2/SEMOBJ
    Regards,
    Tejas

  • Advance output VAT configuration problem, FTXP

    I have a problem with configuration of outgoing down payment tax code.
    In transaction FTXP I've created tax code with following configuration:
    TAX TYPE ,       ACCT KEY,    %,    LEVEL, COND. TYPE,  ACCOUNT
    Output tax (VAT)      , MWS, 10 ,    140,      MWR1,        1960000
    OutputTax-DebitClear, ZUD,            ,    150,      MWR2,        9119000
    OutputTax-CredtClear, ZUK,            ,    160,      MWR3,        9010000
    Tax type - A,  Output tax
    Check - switched on
    EU Code, Target code, Tgt tax code: Output and Input   are   empty.
    When I try to post invoice (transaction FB01) in SAP R3 automaticaly generates additional line item for account 1960000 but no item generates for accounts 9119000 and 9010000 (i.e. for tax type ZUD & ZUK).
    Tax category for accounts 9119000 and 9010000 is set to + (only output tax allowed).
    Could you give me guidence what have I missed with tax configuation..
    Thanx.

    The problem has been solved.
    We have problem with 901-requirement witch used in tax calculation procedure. Accordingly to russian legislation requirements SAP deliver configured tax calculation procedure - taxru. To avoid error message FF 731 - "Tax code may only contain one rate" tax calculation procedure uses 901 requirement for zud and zuk. 901 requirement should has condition text (VOFM transaction -> menu requirements -> Pricing):
    check: ( sy-dynnr = '0312' and
                  sy-cprog = 'SAPMF05A' and
                  sy-tcode = 'FB01') or
      sy-cprog = 'RFUMSV25'  or
            sy-cprog = 'J_3RFUM25'.
            sy-subrc = 4.
    In my case this text was changed by some one and my calculation procedure did not work.
    Thank you all for assistance !!!!

  • Database configuring problem in setup of managed systems in SMD

    Hello,
    i'm doing the setup of a CRM 5.0 in SMD Abap+Java and the setup results returns following:
    "Database configuration problem"  with the exception:
    java.lang.NullPointerException
         at com.sap.smd.server.manager.SMDPluginProperties.setProperty(SMDPluginProperties.java:114)
         at com.sap.smd.agent.plugins.database.ConfigurationTask.configureCustomProperties(ConfigurationTask.java:242)
         at com.sap.smd.agent.plugins.database.ConfigurationTask.configureProperties(ConfigurationTask.java:370)
         at com.sap.smd.agent.plugins.database.ConfigurationTask.execute(ConfigurationTask.java:124)
         at com.sap.sup.admin.setup.AppCfgTasks.configureDbApp(AppCfgTasks.java:115)
         at com.sap.sup.admin.setup.SetupStep.execute(SetupStep.java:202)
         at com.sap.smd.agent.plugins.remotesetup.SapInstance.setup(SapInstance.java:217)
         at com.sap.sup.admin.setup.SapCluster.setup(SapCluster.java:461)
         at com.sap.sup.admin.setup.SapCluster.access$000(SapCluster.java:26)
         at com.sap.sup.admin.setup.SapCluster$SetupRunner.run(SapCluster.java:669)
         at java.lang.Thread.run(Thread.java:534)
    Anybody knows which can be the problem?
    Thanks a lot
    Carlos

    Hi Shriraj,
    ensure that the installation path is correct. I only put /urs/sap/<SID> and you must put /usr/sap/<SID>/DV***/.
    In my case with that the setup returns all in green.
    I hope it helps you
    Regards
    Carlos

  • SAP ESS and MSS

    Dear Forumers,
    I know that SAP ESS should be configured in SPRO -- Personnel management -- Employee Self-Service... But I don't see it there. Where should I activate ESS cinfiguration? in what IMG?
    Thanks in advance
    best regards,
    Eldar

    Hi
    In that case the ESS Node get hided i hope so,activate the node
    in the img-Enterprise Structure-settings.top node
    Regards
    Chandra

  • Error deploying SAP ESS and MSS

    Hello, I get the following error while I'm updating these BP with JSPM
    Versions are SAP ESS 633.0.0 and SAP MSS 630.0.0 both versions has been released recently, the day 2011-07-08.
    ... Error: Unresolved dependencies found for the following SDAs:
    1.: development component 'mss/exp/pla'/'sap.com'/'MAIN_ERP553VA_C'/'10472816'/'0'
    dependency:
    name: 'tc/aii/base/offline/facade'
    vendor: 'sap.com'
    There is no component either in SDM repository or in Deployment batch that resolves the dependency.
    dependency:
    name: 'tc/bl/exception/lib'
    vendor: 'sap.com'
    There is no component either in SDM repository or in Deployment batch that resolves the dependency.
    dependency:
    name: 'tc/ddic/runtime/facade'
    vendor: 'sap.com'
    There is no component either in SDM repository or in Deployment batch that resolves the dependency.
    dependency:
    name: 'tc/wd/api'
    vendor: 'sap.com'
    There is no component either in SDM repository or in Deployment batch that resolves the dependency.
    dependency:
    name: 'tc/bl/logging/api'
    vendor: 'sap.com'
    There is no component either in SDM repository or in Deployment batch that resolves the dependency.
    Which is this component that I'm missing?
    I got file SAPESS00_0-20006842.SCA for SAP ESS 633 and SAPMSS00_0-10009854.SCA for SAP MMS 630. and I placed both in the following path /usr/sap/trans/EPS/in and also they were the only ones that SWDC showed me when I was looking for.
    Thanks in advance.
    Edited by: Santiago Ruiz Ramos on Jul 18, 2011 9:42 AM

    Of course, these are the files
    SAPESS00_0-20006842.SCA corresponding with SP00 for SAP ESS 633
    SAPMSS00_0-10009854.SCA   -->                          SP00 for SAP MSS 630
    Also these othes files are present
    SP00 for SAP PCUI_GP 633             --> SAPPCUIGP00_0-20006843.SCA
    BP ERP05 ESS 1.41 BPERP5ESS09 --> BPERP5ESS09_0-10006126.SCA
    SP04 for BP ERP05 MSS 1.51         --> BPERP5MSS04P_1-10007670.SCA
    SP04 for BP ERP05 COMMON PARTS 1.51  --> BPERP5COM04_2-10007526.SCA
    But only with the first two I get dependency problems as you can see in my first writing. Thanks in advance.
    Edited by: Santiago Ruiz Ramos on Jul 26, 2011 7:08 AM

  • ESS Configuration for Homepage Framework

    I am an experienced web developer but new to SAP web Technologies and any info is much appreciated...
    I now have an understanding how the SAP IMG configuration affects the SAP Portal ESS interface but  ultimately what tells the ESS Portal to use the appropriate entry in the SAP IMG config
    My objective is to setup the ESS portal to use a complete new set of config entries.  Is there an easy way to do this?
    For example in the Define Area Group page, what tells the portal to use "SAPDEFAULTESS_ERP2005" and not my entry "MyEntrySAPDEFAULTESS_ERP2005".
    SAPDEFAULTESS
    SAPDEFAULTESS_ERP2005
    MyEntrySAPDEFAULTESS_ERP2005
    Thank you,
    James Pina

    The Iviews within the Portal ESS role tell the system what menus to use. The intial Overview iview has parameters for the Header and Area Key which come standard pointing to the standard SAP Config entries. Also, each subarea has an Iview in the Portal that points to the Header, AreaGroup and Area key which also point to the standard SAP config entries.
    To create your own menus, you will need to change the config in the IMG and then change the parameters within the Portal Iviews to point to your new config.
    This link will explain in detail.
    [XSS Menu Modification|http://help.sap.com/erp2005_ehp_04/helpdata/EN/c2/d343c938ae419197aa23e637f4fe0b/frameset.htm]
    Cheers,
    Mike

  • SAP ESS/MSS Functional Guide

    Hello Experts,
    I am new to ESS/MSS, so can anyone provide me with a proper Functional & Technical guide on ESS/MSS, also it would be great if you all provide me with a specific configuration guide on installing ESS/MSS. I have already searched some forums on this, but there was no concrete doc available.
    I already have ESS / MSS Configuration (SAP Best Practices for SAP HCM V2.600) (N06) Building Block Configuration Guide & ESS HELP CAESS .
    But if you have something more on this then please share.
    Thanks & Regards,
    Amit Naik

    Hi
    Maybe you can follow the following steps :
    1.you need to identify what is your requirement for the Employee and the Manager.
    2. you need to sit with your portal consultant to check out what views are available for the functionality required.
    3. You need to create a ess user (your basis consultant can help you to do that by running hruser)
    4. you can login onto the portal and check out whether the standard views have what you require or is there some change required.
    4. they you can go to the r/3 system and and use transaction simg_sport for getting to mss configuration quickly.
    5. Ess configuration you will find at under spro-> personnel management - > employee self service- > service specific settings...
    A guide to configure will be very generic and may not directly help. the documentation against each spro node is quite helpful. do write for any other specifics.
    all the best.

Maybe you are looking for