Error Deploying ESS/MSS ERP2005 WebDynpro Components for SP7

Hi,
I have been in process of trying to Patch up the J2EE stack in an attempt to turn on SAP Delivered Solution for ESS/MSS.
We are on EP7 with ECC6 Backend.
What I have done so far::
1. Updated J2EE with Netweaver SP stack 11.
2. Imported the business package for ESS/MSS into EP. I can confirm that the content is now available on PCD.
3. Then i tried to upload the WebDynpro Components for ESS/MSS. Files are PCUI_GP, ESS and MSS. they all have a named reference to 600 SP7. These are the ones available to download for self-services from mySAPERP components on service market place.
This step is now falling over. Deployment of these components fail when its trying to deploy the application component. I must add that once we loaded the Business packages for ESS/MSS (step 2), i then checked the delivered content and created a delta link to the AU/Address iView into my own content folder. I am not sure if this has anything to do with the Failure of deployment but this is the only thing that i did in between steps 2 and step 3.
I didn't think that it would have caused any issue as this was an iview while the component its trying to deploy is a webdynpro application, but i am not sure now.
Please see the trace below.
Message : Failed to deploy application 'sap.com/essauaddr' for deployment state listener 'com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook'.
[EXCEPTION]
com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to deploy the file 'C:\usr\sap\NBW\DVEBMGS21\j2ee\cluster\server0\.\temp\webdynpro\public\sap.com\essauaddr\webdynpro\Applications\com.sap.xss.hr.per.au.address.Per_Address_AU\Per_Address_AU.xml' into the database. Reason: Development Object 'sap.com/ess~au' contains already same repository content. Hint: fully qualified name of the repository VMO must be globally unique.
     at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.checkVMOsExistInOtherDC(RepositoryUpdateManager.java:504)
     at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.deployRepositoryContent(RepositoryUpdateManager.java:98)
     at com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook.onDeploy(RepositoryContainerHook.java:232)
     at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1007)
     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)
     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)
Severity : Error
Category : /System/UserInterface
Location : com.sap.engine.services.webdynpro.WebDynproContainer
Application :
Thread : SAPEngine_Application_Thread[impl:3]_8
Datasource : 1173687328333:C:\usr\sap\NBW\DVEBMGS21\j2ee\cluster\server0\log\defaultTrace.trc
Message ID : 001321C841EF0056000000030000110800042B7618DD7104
Source Name : com.sap.engine.services.webdynpro.WebDynproContainer
Argument Objs : sap.com/essauaddr,com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook,com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to deploy the file 'C:\usr\sap\NBW\DVEBMGS21\j2ee\cluster\server0\.\temp\webdynpro\public\sap.com\essauaddr\webdynpro\Applications\com.sap.xss.hr.per.au.address.Per_Address_AU\Per_Address_AU.xml' into the database. Reason: Development Object 'sap.com/ess~au' contains already same repository content. Hint: fully qualified name of the repository VMO must be globally unique.
     at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.checkVMOsExistInOtherDC(RepositoryUpdateManager.java:504)
     at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.deployRepositoryContent(RepositoryUpdateManager.java:98)
     at com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook.onDeploy(RepositoryContainerHook.java:232)
     at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1007)
     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)
     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)
Arguments : sap.com/essauaddr,com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook,com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to deploy the file 'C:\usr\sap\NBW\DVEBMGS21\j2ee\cluster\server0\.\temp\webdynpro\public\sap.com\essauaddr\webdynpro\Applications\com.sap.xss.hr.per.au.address.Per_Address_AU\Per_Address_AU.xml' into the database. Reason: Development Object 'sap.com/ess~au' contains already same repository content. Hint: fully qualified name of the repository VMO must be globally unique.
     at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.checkVMOsExistInOtherDC(RepositoryUpdateManager.java:504)
     at com.sap.tc.webdynpro.repository.deploy.RepositoryUpdateManager.deployRepositoryContent(RepositoryUpdateManager.java:98)
     at com.sap.tc.webdynpro.serverimpl.wdc.repository.RepositoryContainerHook.onDeploy(RepositoryContainerHook.java:232)
     at com.sap.engine.services.webdynpro.WebDynproContainer.deploy(WebDynproContainer.java:1007)
     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)
     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)
Dsr Component :
Dsr Transaction : 0b312900d06f11db9da1001321c841ef
Dsr User :
Indent : 0
Level : 0
Message Code :
Message Type : 1
Relatives : /System/UserInterface
Resource Bundlename :
Session : 4
Source : com.sap.engine.services.webdynpro.WebDynproContainer
ThreadObject : SAPEngine_Application_Thread[impl:3]_8
Transaction :
User : J2EE_ADMIN
Any thoughts and ideas would be greatly appreciated.

Hi Friends,
I got the same problem but not on ESS/MSS component. But the exception was exactly the same. The solution what i found is
1. Find the exception in the Default trace. By searching for DC Name.
2. Here you should find the one in which its mentioned below error
com.sap.tc.webdynpro.repository.RepositoryRuntimeException: Failed to deploy the file '/usr/sap/EPD/JC35/j2ee/cluster/server0/./temp/webdynpro/public/burton.com/portal~passwordchange/webdynpro/Components/com.burton.webshop.b2b.myprofile.EditPassword/EditPassword.xml' into the database. Reason: Development Object 'local/wdMyProfile' contains already same repository content. Hint: fully qualified name of the repository VMO must be globally unique.
3. Now go to the visual administrator -> deploy -> webdynpro and undeploy the local webdynpro with which the current DC is conflicting. (You should decide whehter you can undeploy or not)
4. Now try activate the activity or Deploy the DC you shouldnt get the problem.
Actually i got this problem when i created a WebDynpro DC by importing the local webdynpro project. So, when i try to activate the activity of DC created then its not getting deployed. When i check the logs, i had same exceptions as you ppl got. So after going thru default trace then i figured out that the local webdynpro is the reason for this conflicting. Then i undeployed that webynpro.
Hope this may be useful for you and others...
Thanks,
Raags

Similar Messages

  • What is the diff between ITS ESS/MSS and Webdynpro ESS/MSS

    Hi all,
    Could anybody tell me the differences between ITS ESS/MSS and Webdynpro ESS/MSS?
    Presently we have ITS based ESS/MSS in our landscape and customer wants to go for Webdynpro ESS/MSS. and Webdynpro ESS/MSS is already installed in the sandbox system where ITS based ESS/MSS is already there.
    my doubt is can we install both ESS/MSS in the same server? if it is installed we may get any problems?

    Karunakar,
    check the compatibility of frontend and backend levels
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/profile/marcio+leoni
    try to restart the portal and check
    Thanks
    Bala Duvvuri

  • ESS/MSS latest business packages for EP 7.0

    Hi,
    Installed EP 7.0 - ehp1
    Need to configure the system for ESS/MSS
    Please guidel me for the latest business packages and navigation at Service market place
    Are the business packages related with ABAP system HR support package level
    Thanks in advance

    Daniel,
    ESS/MSS depends on your ECC patch also.  You need to download versions compatible to ECC and Portal versions.
    Refer to below links on version compatibility
    http://wiki.sdn.sap.com/wiki/display/EP/DownloadinganddeployESSand+MSS
    https://wiki.sdn.sap.com/wiki/display/ERPHCM/HOWTOGETRIDOFSPSTACKMISMATCHISSUES
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20faaa02-7521-2e10-d598-8b03c91c4213?QuickLink=index&overridelayout=true

  • Error on ESS/MSS WebDynPros

    Hi
    We are struggling with ess/mss. Portal is ep6sp9 WAS640. Business packages (ess/mss )have been deployed in the portal and the ess50/mss50/pcui_gp50 components were deployed on WAS.
    The SLD SERVER on the portal pc. The WAS is set to upload its sld information to the portal sld.
    JCO connections(SAP r/3 HumanResources & SAP r/3 HumanResources Metadata) are on WAS and it tests successfully.
    1. Is this the recommended architecture/landscape or should the ess mss pcuigp components be deployed on the portal?
    2. Should we upgrade the ess/mss/pcuigp components to 5.1 or 6.0?
    3. We get an error on the ess/mss webdynpros :
    WDTypeNotFoundException caused by sap.dictionary.
    4. When we use the ess/mss/pcuigp 6.0 version, we get a WDRuntimeException caused by 'There is no such method'.
    Please help..
    Rakhee

    Hi Armin
    Thannk you for your reply.
    Below is the complete stack trace :
    An error has occurred:
    "Failed to process the request."
    Please contact your system administrator.
    Hide details
    Web Dynpro client:
    HTML Client
    Web Dynpro client capabilities:
    User agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1), version: null, DOM version: null, client type: msie6, client type profile: ie6, ActiveX: enabled, Cookies: enabled, Frames: enabled, Java applets: enabled, JavaScript: enabled, Tables: enabled, VB Script: enabled
    Web Dynpro runtime:
    Vendor: SAP, Build ID: 6.4009.00.0000.20041104173322.0000 (release=630_REL, buildtime=2004-11-18:22:17:10[UTC], changelist=298578, host=PWDFM027)
    Web Dynpro code generators of DC sap.com/mss~ewa:
    SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:41[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:28:58[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:03[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapWebDynproGenerationCTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:17:08[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:25[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:21:50[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:14[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:44[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:46[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    Web Dynpro code generators of DC sap.com/pcui_gp~xssutils:
    SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:41[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:28:58[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:03[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapWebDynproGenerationCTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:17:08[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:25[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:21:50[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:14[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:44[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:46[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    Web Dynpro code generators of DC sap.com/tcwddispwda:
    No information available
    Web Dynpro code generators of DC sap.com/pcui_gp~xssfpm:
    SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:41[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:28:58[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:03[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapWebDynproGenerationCTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:17:08[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:25[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:21:50[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:14[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:44[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:46[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    Web Dynpro code generators of DC sap.com/mss~finutils:
    SapDictionaryGenerationCore: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:41[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    SapMetamodelWebDynpro: 6.4009.00.0000.20040910102423.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:28:58[UTC], changelist=280539, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCore: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:03[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapWebDynproGenerationCTemplates: 6.4009.00.0000.20040929105448.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:46:16[UTC], changelist=286523, host=PWDFM026)
    SapGenerationFrameworkCore: 6.4009.00.0000.20040910102127.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:17:08[UTC], changelist=280527, host=PWDFM026.wdf.sap.corp)
    SapIdeWebDynproCheckLayer: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:25[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapMetamodelDictionary: 6.4009.00.0000.20040609163924.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:21:50[UTC], changelist=253570, host=PWDFM026.wdf.sap.corp)
    SapMetamodelCommon: 6.4009.00.0000.20040730142052.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:18:14[UTC], changelist=269100, host=PWDFM026.wdf.sap.corp)
    SapWebDynproGenerationCore: 6.4009.00.0000.20040910102318.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:33:44[UTC], changelist=280536, host=PWDFM026.wdf.sap.corp)
    SapDictionaryGenerationTemplates: 6.4009.00.0000.20040910101802.0000 (release=630_VAL_REL, buildtime=2004-09-29:21:24:46[UTC], changelist=280522, host=PWDFM026.wdf.sap.corp)
    Web Dynpro code generators of DC sap.com/tcwdcorecomp:
    No information available
    J2EE Engine:
    6.40 patchlevel 87289.311
    Java VM:
    Java HotSpot(TM) Server VM, version: 1.4.2_07-b05, vendor: Sun Microsystems Inc.
    Operating system:
    Windows 2003, version: 5.2, architecture: x86
    Error stacktrace:
    com.sap.tc.webdynpro.services.exceptions.WDTypeNotFoundException: type com.sap.pcuigp.xssfpm.wd.model.types.Ext_Service could not be loaded: com.sap.dictionary.runtime.DdException:
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:242)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:205)
         at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:471)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.initAttributes(NodeInfo.java:771)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:756)
         at com.sap.tc.webdynpro.progmodel.context.NodeInfo.init(NodeInfo.java:761)
         at com.sap.tc.webdynpro.progmodel.context.Context.init(Context.java:40)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:199)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getCustomControllerInternal(Component.java:433)
         at com.sap.tc.webdynpro.progmodel.controller.Component.getController(Component.java:362)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.getPublicInterface(DelegatingComponent.java:142)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetBackendConnectionsController(InternalFPMComponent.java:199)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:171)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:105)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:95)
         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:346)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:352)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:593)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:249)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
         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:385)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:263)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:340)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:318)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:821)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:239)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
         at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
         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:94)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
    Caused by: com.sap.dictionary.runtime.DdException:
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:89)
         at com.sap.dictionary.runtime.ProviderFactory.internalResolveLogicalNameToJCODestination(ProviderFactory.java:408)
         at com.sap.dictionary.runtime.ProviderFactory.resolveLogicalNameToJCODestination(ProviderFactory.java:354)
         at com.sap.dictionary.runtime.ProviderFactory.internalGetProvider(ProviderFactory.java:215)
         at com.sap.dictionary.runtime.ProviderFactory.getProvider(ProviderFactory.java:180)
         at com.sap.dictionary.runtime.DdDictionaryPool.getProvider(DdDictionaryPool.java:78)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:64)
         at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:39)
         at com.sap.dictionary.runtime.DdBroker.getDataType(DdBroker.java:149)
         at com.sap.dictionary.runtime.DdBroker.getSimpleType(DdBroker.java:170)
         at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getSimpleType(DataTypeBroker.java:234)
         ... 40 more

  • EP,ESS/MSS  and webdynpro for java interview questions.

    I am an ep and ESS?MSS consultant and work on webdynpro for java.I have also worked on PDK like customization of masthead and logon page.I would like to know how to prepare for an interview? I mean what should I read ? and what topics should I cover?

    HI Anzar
    Instead of posting this here, you could have googled it. There are no. of sites for the same thing.
    Since you wrote, so just curious... EP & ESS/MSS Consultant... what does that mean?
    If I am not taking it wrong, by that sentence you are trying to tell that you have worked on ESS / MSS modeule. Right?
    See, if you are an EP Consultant, you must know all the below atleast -
    1. PORTAL SIDE
    a. Different types of iView configuration
    b. User Management
    c. Internal / External Portal Configuration
    d. Content development
    e. UWL
    f. Portal bottlenecks (I mean portal related issues, like slow responding etc.)
    g. Display & Desktop Configuration
    h. System Landscape Directory
    i. NWDI
    2. WEB DYNPRO SIDE
    a. Calling iviews from wd applications
    b. RFC/ BAPI calls
    c. JCO Connections
    d. SC/DC Concept
    e. Import/Export Parameters
    f. Scenario Based Answering (like... if your imported BAPI import parameters are changed by BASIS, what will you do to make it work for you.... etc)
    g. Singleton/Non-Singleton nodes
    h. Controllers
    i. Interfaces
    j. Multi-lingual Applications
    k. EJBs
    l. PDK applications
    This is the basic list, it can contain many more items... This is the list which I faced for my interview. As an EP consultant, you must be good in both Portal as well as WD end.
    1 more thing, every interview is different from other, so no point in just mugging them out. Go through with there concepts. That way, you can answer twisted & scenario based questions.
    Hope this will help.
    Best Regards
    Chander Kararia
    if question solved, close the thread after marking it answered.
    Best Regards
    Chander Kararia

  • Deploying ESS/MSS

    Hi,
    We are having some issues with regards to Self Services. We have done a EP7.01 deployment and updated the J2EE Core components. We also installed the XSS Business Packages. All this was done using JSPM and is visible under deployed components.
    Now the issue arose when a apps consultant noticed an error:
       com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name essuspdata
    I have had a look at these forums to prevent wasting people's valuable time
    Re: ESS IVIEW not working
    Re: PortalRuntimeException: Failed in WD JNDI lookup
    Re: Error in the Standard MSS iview?
    Now it seems that if the XSS services were deployed then they would be visible in Visual Administrator under the "deploy" service ->webdynpro along with the big list there is already. Now i cannot find this "essuspdata" or any other ESS/MSS service there, which suggests that it may not be installed or deployed or started. Now correct me if i am wrong, all deployment should be done via JSPM not SDM? I had a look in SDM for curious reasons and saw ESS/MSS and other Business Packages there in the list under SDM repository but it does not say if it is deployed/installed/started.
    Can someone please guide me where i have gone wrong, as i am new to Enterprise Portal?
    thanks in advance!
    Mani

    thanks for your reply.
    he has said there is nothing he hasn't forgot to look into and tried.
    I had a look into the SAP logviewer and saw some errors come up at the time i tried to start the essuspdata
    the application that is causing this is: Application : sap.com/tcwddispwda
    i am not sure if this is dependant on other applications/services that are supposed to be started
    (sorry for the huge dump of information and badly formatted reply)
    in 1st order of error occuring
    Exception occured during processing of Web Dynpro application sap.com/pb/PageBuilder. The causing exception is nested.
    [EXCEPTION]
    com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to load page
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:529)
         at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:193)
         at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
         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)
    Caused by: javax.naming.NamingException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name essuspdata [Root exception is com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name essuspdata]
         at com.sapportals.portal.pcd.gl.JndiProxy.getObjectInstance(JndiProxy.java:51)
         at com.sapportals.portal.pcd.gl.PcdGlContext.getSemanticObject(PcdGlContext.java:929)
         at com.sapportals.portal.pcd.gl.PcdGlContext.getSemanticObject(PcdGlContext.java:702)
         at com.sapportals.portal.pcd.gl.PcdGlContext.lookup(PcdGlContext.java:73)
         at com.sapportals.portal.pcd.gl.PcdURLContext.lookup(PcdURLContext.java:238)
         at javax.naming.InitialContext.lookup(InitialContext.java:347)
         at com.sap.portal.pb.data.PcdManager.doInit(PcdManager.java:72)
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:527)
         ... 31 more
    Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name essuspdata
         at com.sap.portal.pcm.iview.admin.AdminBaseiView.createAttrSetLayersList(AdminBaseiView.java:357)
         at com.sap.portal.pcm.iview.admin.AdminBaseiView.getAttrSetLayersList(AdminBaseiView.java:205)
         at com.sap.portal.pcm.iview.admin.AdminBaseiView.getCustomImplementation(AdminBaseiView.java:148)
         at com.sap.portal.pcm.admin.PcmAdminBase.getImplementation(PcmAdminBase.java:530)
         at com.sapportals.portal.ivs.iviews.IviewServiceObjectFactory.getObjectInstance(IviewServiceObjectFactory.java:430)
         at com.sapportals.portal.prt.jndisupport.DirectoryManager.getObjectInstance(DirectoryManager.java:56)
         at com.sapportals.portal.pcd.gl.JndiProxy.getObjectInstance(JndiProxy.java:47)
         ... 38 more
    2nd
    application [webdynpro/dispatcher] Processing HTTP request to servlet [dispatcher] finished with error.
    The error is: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to load page
    Exception id: [0017085D3F2500700000000600001ADC000488AAF4368BB8]
    not sure why it is giving this error, as it seems like a general issue but i can't put my finger on it.
    I had a check for other errors which i have rectified myself and its looking slightly cleaner than before.
    again i have looked all over google, SDN, OSS notes and nothing. Not sure if this is a new problem or am i missing some config somewhere. did find one note which said to apply the latest java component patches which i have but its not sorted anything. My only concern is why i can't see essuspdata or any other ess/mss under  Content Administration -> Webdynpro -> under deployed content -> sap.com which only indicates its not deployed but from here onwards i am truly lost as to why
    Any ideas,
    Mani

  • Error in ESS/MSS application accessing in Portal : URGENT

    Hi Experts ,
    I am getting the following error , when logged in to the portal using one user and click on the Leave request in ESS/MSS.
    Can any body let me know how to resolve this error.
    com.sap.xss.config.FPMConfigurationException: Read of object with ID portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.lea/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.LeaveRequest failed.
         at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObjectInternal(PcdObjectBroker.java:92)
         at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObject(PcdObjectBroker.java:47)
         at com.sap.xss.config.domain.PersistentObjectManager.retrieveObjectInternal(PersistentObjectManager.java:106)
         at com.sap.xss.config.domain.PersistentObjectManager.retrieveObject(PersistentObjectManager.java:80)
         at com.sap.xss.config.FPMRepository.retrieveObjectInternal(FPMRepository.java:83)
         at com.sap.xss.config.FPMRepository.retrieveObject(FPMRepository.java:66)
         at com.sap.pcuigp.xssutils.ccpcd.FcXssPcd.initializeConfiguration(FcXssPcd.java:816)
         at com.sap.pcuigp.xssutils.ccpcd.FcXssPcd.loadConfiguration(FcXssPcd.java:250)
         at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcd.loadConfiguration(InternalFcXssPcd.java:178)
         at com.sap.pcuigp.xssutils.ccpcd.FcXssPcdInterface.loadConfiguration(FcXssPcdInterface.java:138)
         at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcdInterface.loadConfiguration(InternalFcXssPcdInterface.java:148)
         at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalFcXssPcdInterface$External.loadConfiguration(InternalFcXssPcdInterface.java:240)
         at com.sap.pcuigp.xssutils.ccpcd.CcXssPcd.loadConfiguration(CcXssPcd.java:282)
         at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcd.loadConfiguration(InternalCcXssPcd.java:184)
         at com.sap.pcuigp.xssutils.ccpcd.CcXssPcdInterface.loadConfiguration(CcXssPcdInterface.java:115)
         at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcdInterface.loadConfiguration(InternalCcXssPcdInterface.java:124)
         at com.sap.pcuigp.xssutils.ccpcd.wdp.InternalCcXssPcdInterface$External.loadConfiguration(InternalCcXssPcdInterface.java:184)
         at com.sap.pcuigp.xssutils.ccxss.CcXss.loadConfiguration(CcXss.java:205)
         at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXss.loadConfiguration(InternalCcXss.java:153)
         at com.sap.pcuigp.xssutils.ccxss.CcXssInterface.loadConfiguration(CcXssInterface.java:112)
         at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface.loadConfiguration(InternalCcXssInterface.java:124)
         at com.sap.pcuigp.xssutils.ccxss.wdp.InternalCcXssInterface$External.loadConfiguration(InternalCcXssInterface.java:184)
         at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:172)
         at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
         at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
         at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
         at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:748)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:283)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:733)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:668)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:860)
         at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:220)
         at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1246)
         at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:354)
         at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:547)
         at com.sap.portal.pb.PageBuilder.wdDoRefresh(PageBuilder.java:591)
         at com.sap.portal.pb.PageBuilder$1.doPhase(PageBuilder.java:822)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processPhaseListener(WindowPhaseModel.java:755)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doPortalDispatch(WindowPhaseModel.java:717)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:136)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:313)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:684)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Caused by: com.sapportals.portal.pcd.gl.PermissionControlException: Access denied (Object(s): portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.ess.employee_self_service/com.sap.pct.erp.srvconfig.lea/com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.LeaveRequest)
         at com.sapportals.portal.pcd.gl.PcdFilterContext.filterLookup(PcdFilterContext.java:422)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1248)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.basicContextLookup(PcdProxyContext.java:1254)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookupLink(PcdProxyContext.java:1353)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.proxyLookup(PcdProxyContext.java:1300)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.lookup(PcdProxyContext.java:1067)
         at com.sapportals.portal.pcd.gl.PcdGlContext.lookup(PcdGlContext.java:68)
         at com.sapportals.portal.pcd.gl.PcdProxyContext.lookup(PcdProxyContext.java:1060)
         at com.sap.xss.config.pcd.PcdObjectBroker.getPcdContext(PcdObjectBroker.java:305)
         at com.sap.xss.config.pcd.PcdObjectBroker.retrieveObjectInternal(PcdObjectBroker.java:53)
         ... 69 more

    Hi ,
    Check the below thread and try options wihtin that.
    all the best as the below thread is not resolved.
    Manager Self Service Content are not showing up
    Koti Reddy

  • ESS/MSS 1.31 version for download

    Hi where can I find the downloads for the version ess/mss 1.3,HR admin 1.1,talent developement,simplified reporting etc.. for NW2004s?
    Thanks
    KK

    You would have to connect to SAP Service Market Place @ http://service.sap.com/swdc and then follow the following path.
    In the left hand side go to
    SAP Software Distribution Center -> Download -> Support Packages and Patches -> Search for Support Packages and Patches
    and then in the RHS
    Support Packages and Patches - Entry by Application Group -> SAP Application Components -> SAP ERP ->SAP ERP ENHANCE PACKAGE -> SAP ENH PACK 3 FOR SAP ERP 6.0 -> Entry by Component ->Portal Content
    Over there you will get
    1 - BP ERP05 ESS 1.31
    2 - BP ERP05 HR ADMINISTRATOR 1.11
    3 - BP ERP05 COMMON PARTS 1.31
    4 - BP ERP05 MSS 1.31
    And the XSS Components you will get at
    Support Packages and Patches - Entry by Application Group -> SAP Application Components -> SAP ERP ->SAP ERP ENHANCE PACKAGE -> SAP ENH PACK 3 FOR SAP ERP 6.0 -> Entry by Component ->SAP XSS (Self Services)
    Thanks,
    GLM
    Edited by: GLM on Sep 2, 2009 1:16 PM
    Edited by: GLM on Sep 2, 2009 1:18 PM

  • Error in ESS/MSS

    Hi, everyone:
    When I installed the Business Package with ESS/MSS and with the assigned HR manager login(I tested the back-end SAP and ITS were already integrated) .I have errors with the screen in the HR manager interface, every iView show me same error:
    Portal Runtime Error
    Thanks again!
    Huaishu Li

    You need to give set correct permission to execute this iView.
    1. Navigate to System Administration->Permissions.
    2. Click on Security Zones->com.sap.portal.ep50->ep50_safety
    3. Right Click on edit and select edit permission
    4. Add user or user group and give them the read permission.
    Save it and test it with concerned user.
    This should help.
    Rgds

  • ESS / MSS - ERP2005

    hi gurus,
    can any one help me with some documents for ESS / MSS configuration for the standard services.
    please provide some ideas on how to implement custom services in ECC6.
    My mail id : [email protected]
    Thanks in Advance
    Maximum points assured.

    Please find the links to know more on
    ESS refer the following link
    <http://help.sap.com/saphelp_erp2005/helpdata/en/5b/76a6d7fd3a4e91bfb422405bf3e04d/frameset.htm>
    for MSS:
    <http://help.sap.com/saphelp_erp2005/helpdata/en/29/d7844205625551e10000000a1550b0/frameset.htm>

  • How to Integrate ESS/MSS to Webdynpro Application?

    Hi All,
    I am New to Webdynpros.
    I Want to Develop Application on Webdynpro and integrate to ESS/MSS.
    How to Start and what to do?
    Plz Reply ASAP.
    Thanks and Regards
    Kiran

    Most of the application in ESS have used the FPM (http://help.sap.com/saphelp_erp2005/helpdata/en/3f/20888224c544a2a01d9fe618902ae5/frameset.htm) to develop new self service applications.
    You may start developing applications as described in the help link and then integrate it with ESS. You will have to maintain some setting under Homepage Framework in SPRO. There are plenty of threads describing this. Do  search
    Thanks,
    GLM

  • Appraisals in ESS/MSS ERP2005

    Hi,
    I hope someone can help my confusion.
    It is true that in ERP2005 (ECC6), there is no standard apprasial functionality for employees?
    Is the MSS Appraisal Functionality under Personnel Development or Performance Management (Maintain Performance Documents)?
    Thanks in advance
    Paul

    Hello Paul,
    In every release of performance management there is standard appraisal functionality available for the employee; be it directly in R/3 or in the web.
    There is no ESS scenario available. Instead you can include pages of BSP application HAP_DOCUMENT to an iview and assign that to the employee. This allows performance management to run in the portal as well as stand-alone in the web.
    The same concept can be used for the manager. Besides this we deliver also an MSS status overview.
    Regards and Groetjes,
    Maurice

  • Portal Runtime Error  in ESS MSS Pages

    Hi All,
    We are getting following run time error from standard ESS transaction page. It is standard ESS iView and data showing correctly but this message is giving in the bottom of the page content area. We are using EP SP12 with 4.6c backend R/3 system.
    Any help or suggestions will be greatly appreciated.
    Portal Runtime Error
    An exception occurred while processing a request for :
    iView
    Cannot assign a java.lang.String object of length 1,342 to host variable 1 which has JDBC type VARCHAR(1,333)..
    Exception id: 10:59_21/08/05_0008_1396450
    See the details for the exception ID in the log file
    Thanks,
    Laxma

    Hi Laxma,
    Change the objectids to something short.
    For now create a new folder structure with Object IDs shorter and move the content in the old folders to the new folders. For each object the name space is too long and is causing the path to exceed the defined limit.
    Regards
    -Venkat Malempati

  • Do we need to install SAP Portal for implementation of ESS & MSS

    Hi All,
    We are implementing SAP (ECC 6.0) for one of our client, Due to some contractual limitations, we do not want to implement SAP portal though it is a part of standard delivery, I want to know that is it absolutely necessary to install and implement SAP portal for implementation of ESS & MSS.
    What i know and understand is that with the new architecture ESS & MSS can be deployed and accessed as a stand alone application on an internet browser by (Web dynpro client) without any need of enterprise portal. While ESS & MSS application can be hosted on Web application server.
    Please validate my understanding if it is correct, Also does the new Web dynpro based client support all the functionality and authorization related issues for ESS & MSS ??
    Regards
    Amit Ajmera

    Hi Amit,
    Yes, you can run ESS/MSS as WebDynpro application without having to deploy on Portal. However, the look and feel and user accessibility is much better when deployed as Portal page. For WebDynpro, you will still need to publish the individual URL link to application somewhere...
    Another point is that on portal you can deploy standard Business package specific to ESS and MSS which contains lots of readymade iviews/page/roles etc so it can reduce your development cost dramatically.
    But, at the end it all depends on your individual requirement and project scope.
    Cheers !!
    Satya.
    PS: Points always encourage me to reply...:-)

  • BP ERP05 COMMON PARTS 1.0 required for ESS/MSS?

    Is BP ERP05 COMMON PARTS 1.0 required for ESS/MSS 603? the link below talked about how to deploy ESS/MSS, it does not mentino BP for common parts
    http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=31476
    but in the linke that talks about how to get rid of mismatch for ESS/MSS, it has BP for common part listed https://wiki.sdn.sap.com/wiki/display/ERPHCM/HOWTOGETRIDOFSPSTACKMISMATCHISSUES
    I looked at online help for this BP, it says it is for system asministrators, but looks like it also have business functions listed in the iview. http://help.sap.com/erp2005_ehp_03/helpdata/EN/eb/bd8a42f802a01ae10000000a155106/frameset.htm
    I'm confused - to use ESS/MSS 603, do I really need BP ERP05 COMMON PARTS 1.0?
    Thanks,
    Jane Zhou

    The MSS business package uses objects from other business packages. These objects are listed in the Shared Objects in This Business Package section. If you want to use these objects, you must also implement the relevant business package.
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/29/d7844205625551e10000000a1550b0/frameset.htm
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/c1/85b17cc78246258b85dd69af5ece17/frameset.htm
    If you are planning to use any of the shared objects - then you will need the BP for Commom Parts as well.
    Also, the BP for common parts connects different shared services between ESS and MSS - for you to be able to use both of them in conjunction.
    Without installing the BP for common parts, some components might not work properly.
    Hence It is recommended to install this BP along with ESS and MSS.
    Hope that helps !!
    Thanks,
    Shanti

Maybe you are looking for