ESS/MSS webdynpro customization...........

Hi ,
I want to customize MSS WebDynpro iview in NW Developer Studio can anybody guide me for this ? How to perform this task ? If any Doc Available ?
Can i use Visual Composer also?
Thanks,
Smita

hi,
yes, FPM is the framework which all self service applications follow. Hence all the self service applications have same patterns. The thread I referred you in first reply, contains a gudd xplanation of FPM. Plus you can find the <a href="http://help.sap.com/saphelp_erp2005/helpdata/en/b4/139525380149a49c8402e22700e4ba/frameset.htm">documentation</a> of FPM helpful.
Its a framework which self service applications follow. hence no need to separately implement it.
Is ESS/MSS deployed and running in your portal?
But still you need to setup JDI for making any code changes to ESS/MSS applications.
~cheers
avadh

Similar Messages

Configuration and customization guides for ESS/MSS(webdynpro Java) in EP 7

Hi All,
Can anybody help me by providing the guides for Configuration and Customization of ESS/MSS(webdynpro java) in EP 7.0?
Thanks in advance.
Regards,
Shankar

Hi,
Please check the links for help
https://www.sdn.sap.com/irj/scn/wiki?path=/pages/viewpage.action%3fpageid=31476
Configuring ESS in SAP Enterprise Portal 6.0
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/21eb036a-0a01-0010-25a3-b2224432640a
General Settings for Self-Service Applications
Configuring MSS on Portal 6.0
Implementation and Configuration guide for ESS into Portal,Backend R/3 4.7C
Regards
Santosh

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

Best Practice for ESS/ MSS role customization

Hi ,
I would want to know the best practice for role customization for ESS / MSS business package . For eg if my company does not want to use someof the workset like working time , travel etc , what is the best practice for this scenario .
anEEZ

Hi Aneez,
This is the link for complete best practices on NetWeaver
http://help.sap.com/bp_epv260/EP_EN/index.htm
Browse the Busines scenarios, you will find what you are looking for.
Now, these ones is specific for ESS and MSS
http://help.sap.com/bp_epv260/EP_EN/html/EP/N26_ESS.htm
http://help.sap.com/bp_epv260/EP_EN/html/EP/N27_MSS.htm
Hope this helps,
Kumar
P.S Reward Points for useful answers.

Standard ESS-MSS Package Customization

HI,
I have to customize existing standard ESS-MSS packages.
I down load the packages to my NWDS from NWDI.But after down load,I am getting this error."The type AbstractStringBuilder is not visible".
Please suggest me how to resolve this error.
Regards
-Sandip

Hi,
Try Repair project structure and classpath.
Hope you have done the Organize imports....
Regards
Ayyapparaj

Customize the ESS in Webdynpro java

HI,
I am new to webdynpro for java.My requirement is to customize the ESS in Webdynpro java.Please give how to create in wd-java step by step document for the Payroll system event in ESS.How to upload the ess package in NWDS,how to mapp the FPM component to current component.Please provide me.
Thanking you,

Hi,
go through this thread:[thread|Customize/Change ESS MSS WebDynpro Applications (ECC 5.0);
check this doc too:[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/4598a190-0201-0010-a59f-820e3b31f854]
hpe it hlps u
Regards,
Khushboo

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

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

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

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

ESS & MSS Team Calendar Customization

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

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

Customize icons for ESS/MSS

Hello,
I need to customize the layout of the ESS/MSS web Dynpros and exchange the icons. What is the best way to do so? Basically I don't want to just replace the icons located in the PUBLIC/BC/Icons folder but tell the Web Dynpro to look in an custom folder. Is there a way to do so?
Best regards,
Dominik

Hi Dominik,
I think its possible, but not sure. Just try here like
1. Go to transaction SE80 and navigate to the MIME Repository
2. Create a folder in the MIME repository that will contain all the custom icons. Make sure the folder is created in correct directory ( generally for themes this is the directory path . /SAP/PUBLIC/BC/UR/<theme_name>.. so just check for images also
3. Go to the Repository browser in SE80 and select u201CProgramsu201D from the drop down list.
4. Enter BSP_UPDATE_MIMEREPOS in the input field and hit Enter
5. Execute the program and enter the MIME repository path to the folder that is to contain the custom icons.
Once you upload the icons in mime repository, you can access that icons like standard. I think
Regards
Srinivas
Edited by: sanasrinivas on Aug 4, 2011 7:14 AM

ESS/MSS customization

Hi,
We are planning customize ESS/MSS (version 600) on EP 7 SP9
we created new Track in NWDI as explained in the following blog
ESS/MSS Customization Make it Simple
Then we added software component ESS 600 and MSS 600 in our track and checked in
SAP-JEE 7.00, SAP_JTECHS 7.00, SAP_BUILDT 7.00, SAP_PCUI_GP 600 and SAP_ESS 600 file to track.
I could be able view source code in NWDS inactive dcs. But by creating a new project i got following error message
"some used DC's are not available locally. You have to sync used DC's for this project.
The point is that i couldn't able to view the software component SAP-JEE 7.00, SAP_JTECHS 7.00, SAP_BUILDT 7.00
and SAP_PCUI_GP 600 in active dcs.
Please suggest me.
Regards
Osman

dear saurabh,
check http://help.sap.com/saphelp_nw70/helpdata/en/44/60dc1943c2311ce10000000a155369/content.htm
regards,
Sujay
*reward points if u find this answer useful

Integration of webdynpro abap custom iview into standard ESS/MSS portal

Hello all,
Could anybody please throw light on how to integrate custom iview which is developed in Webdynpro ABAP into standard tab in MSS (Webdynpro java)
For example.I want to add few custom fields(which are mapped to infotype 0041) into general information link of MSS.these fields will be created in webdynpro abap.
or.
I want to create a new link under general information which pops up as a custom iview (which is create in webdynpro abap) .
please let me know how can i meet the above requirements.
Thanks in advance.

I am not really sure about your requirement. With my limited understanding of that , i think that you have few possibilities.
1. You can let the ess/mss application communicate with WDA application via a Poral event.
2. You can enhance the ESS WDJ component and use RFC destination to get the data from info type and build your own view in WDJ.

ESS/MSS Customizations

HI ESS/MSS Gurus,
During our discussions with the client regarding the inherent features of the standard ESS/MSS functionalities, several points were raised, namely:
1. The cumbersome nature of data/request entry - basically they just want all the request filing to occur in one screen. No need to skip screens to review and validate the request
2. No record id to document the request -> they want a means for the user and manager to monitor and track requests using a standardized request numbering system. I believe that the standard solution for ESS/MSS does not have this one in place
3. Ability to extract reports of histories of requests raised (for the employee) and requests reviewed (for the manager)
In our opinion, these items will require heavy customization on both the portal and back end side. We are basically considering a custom table which will store these information and depending on the status of the requests, a request column will be updated with the corresponding values. The request approvals, notifications, and postings are also to be done via ABAP
In designing this solution, we came across some stumbling blocks, specifically on updating the personal and team calendars for leave requests and the employee's schedule for the clock in/out corrections. Hence, we want to check if any of you guys have had experience with customizing the ESS/MSS interfaces (specifically the leave and clock in/out application and approval), and if so, can you help us identify which tables are being updated/read when a leave or clock in/out is created and approved. We already checked the FMs attached to the portal application and the they call several methods and functions; i.e. is there a table/set of tables that you can point us to instead?
Your immediate response is highly appreciated.
Regards,

1. The cumbersome nature of data/request entry - basically they just want all the request filing to occur in one screen. No need to skip screens to review and validate the request
-- Depending on your version less than or equal to ehp5,.. this is true in versions less then ehp5. then ahain until ehp4 any forms that need implementation will need some element of development work so in your particular case the element of develpment could be a little higher to make them all use a single entry screen that gets submitted.
2. No record id to document the request -> they want a means for the user and manager to monitor and track requests using a standardized request numbering system. I believe that the standard solution for ESS/MSS does not have this one in place
-- for any form or process that has workflow attached there is an automatic workflow-id assigned by the system and I believe you can report on these inthe back end... standard workflow fuctionality... why dont you explore this option with your workflo consultant?
3. Ability to extract reports of histories of requests raised (for the employee) and requests reviewed (for the manager)
-- refer to point 2 answer above...
In our opinion, these items will require heavy customization on both the portal and back end side. We are basically considering a custom table which will store these information and depending on the status of the requests, a request column will be updated with the corresponding values. The request approvals, notifications, and postings are also to be done via ABAP
-- I have seen this done previously,... it is not very cumbersome or difficult,. it is just replacing std sap workflow function of assigning identifiers with user specified number ranges... the only advantage here is you get to define specific number ranges for process to get ids from...
In designing this solution, we came across some stumbling blocks, specifically on updating the personal and team calendars for leave requests and the employee's schedule for the clock in/out corrections. Hence, we want to check if any of you guys have had experience with customizing the ESS/MSS interfaces (specifically the leave and clock in/out application and approval), and if so, can you help us identify which tables are being updated/read when a leave or clock in/out is created and approved. We already checked the FMs attached to the portal application and the they call several methods and functions; i.e. is there a table/set of tables that you can point us to instead?
-- I dont see any problems in the assignment of workflow ids to any requests related to leave requests or clockin-out scenarios,.. so unless you are more specific about the nature of errors am not sure anyone can help much...
cheers

Webdynpro Java and ESS/MSS

Hello,
It has been a rumour for a long time and now it seems that SAP will convert all ESS/MSS services into Webdynpro ABAP....so i want to know what's the plan for Webdynpro Java ...? what areas will it be used...? and what are the options for Webdynpro Java Developers....? ...one thing for sure is to learn Webdynpro ABAP...
Regards,
Anil

As far as I know, SAP has changed travel management and HR administraor from WDJ to WDA as of EhP1.
Do you have any ideas about any other BP?
Actually, I wonder SAP has been developed any new BP based on WDJ after EhP is introduced.

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

ESS/MSS webdynpro customization...........

Similar Messages

Maybe you are looking for