MSS iview customization not WebDynpro

Hi Experts,
I need to add a new field to the General data iview of MSS package.For that we have created a new function Module (having the new field) in the Backend R/3 which calls the existing Function module.This is based on the Par file and not the Web Dynpro component.

Hi Eduardo,
This is a Portal component application and not a webDynpro.
Hi Krish,
We are very near to the solution.I will let you know if I got it.
Regards
Imran

Similar Messages

Portal iview Customization for Webdynpro Java CTRL+ Right Click in Preview

Hi Team,
I am able to hide some Web Dynpro UI elements from Portal Content Administration >> Web Dynpro iView >> Preview and by Pressing CTRL+RIGHT CLICK.
Here I need to understand the concept like how things work in this case. If we hide some UI in Web Dynpro Java iView customization will there not be any RFC/BAPI calls associated with that particular UI
For Example: Web Dynpro iView is made up of CompA and CompB and I am going to hide the UI associated with CompA. When I invoke the application will there not be any activity like invoking CompA calling associated RFC/BAPI etc related to CompA
Please help me in understand the concepts and performance implications on this.
Regards
Sudhir

Hi Sudhir,
Great Question! :-)... I am not 100% sure, but my guess would be that you would still see the associated BAPI/RFC calls since the "hiding" of the fields is purely a UI feature done using the Portal PCD.
However you can of course test this for your scenario, by running an RFC trace for your user in the ECC system and then run the WDJ application and see if you see the RFC calls or not (more or less depending on the hidden/visible status of your component).
Hope that helps,
Simon

Webdynpro iview Customization not reflecting to all users

Hi Forum,
In Webdynpro ivew, from Content Administration >> preview >> done some customization by CTRL+Right Click. But when we access that page assigned to a role, customization is reflecting to only that user but not for other users. But we want this customization to be reflected to all users who is accessing that role associated with that webdynpro ivew.
Please help us to resolve this issue
Regards
Sudhir

closing the thread

MSS iview Customization in SAP R/3 4.7

Hi
we are running on SAP R/3 4.7 version. and we had deployed the MSS Business package into our SAP Netweaver portal 7.0.
Now our requirement was to customize one field in the General Data iview. corresponding par file name is com.sap.pct.hcm.eeprofilegeneraldata.par
Is there any way (sequence of steps ) how can we customize the above iview.
Thanks
Prasad

Hi Joseph,
we have downloaded the par file into our local nwds, and we are not getting java files under src.api, src.core files.
Actually,a new function module was created, in which we have created new method. and we need to establish connection to
this function module through SAP Enterprise connector.
do you have any example or approach on this customizations
Thanks
Prasad

MSS iView - General Data

Hi All,
I copied the "General Data" iview from MSS biusiness package. I am on EP7.
When i view this page, i see "Contract Data", "Communications Data", "Organisational Assignment" and "Personnel Structure".
I want to remove "Communications Data" from the above iview.
How to achieve this ?
Your help is much appreciated as we are in a critical phase.
Thanks,
Sathya

Hi,
Can you help me regarding MSS iview customization (based on par and not webDynpro).There is one iview General data in which we have to add one new field.For that a new function Module is created in the Backend R/3 by ABAP persons.The New Function module wraps the old function Module + the new Field.Do you know How this filed can be shown in our iview.
Regards
Imran

MSS Team Viewer: WDPortalEventing.subscribe in custom iView does not work.

Dear all,
we are trying to integrate a custom Web Dynpro Java iView into the MSS environment. This iView should receive the portal event "selection_changed" as described in SAP note 1112733. Which does not happen. I have followed the description within the note and done the following:
- In WdDoInit() added: WDPortalEventing.subscribe("urn:com.sap.mss.employeesearch", "selection_changed", wdThis.wdGetGetEmployeeQualificationsAction());
- implemented action "onActionGetEmployeeQualifications(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent, java.lang.String dataObject, java.lang.String Namespace, java.lang.String Name )"
- created WD Java iView and added it to a new portal page which also contains the employee profile page
The result is: the action method never gets called. What am I missing here?
Any input on this topic would be greatly appreciated!
Kind regards,
Helga

Hi Kim,
I have recently worked in one such developement work related with MSS iView. Please see following link:
https://www.sdn.sap.com/irj/scn/wiki?path=/display/profile/how-toaddacustomWebDynproiViewtotheMSSEmployeeProfile%2528ECC+6.0%2529
https://wiki.sdn.sap.com/wiki/display/profile/HowtoreadinformationfromtheteamviewerinWeb+Dynpro
Using these links, you can create one WD Appl. In the application, when you will click on a particular employee, the employee no will be selected.
Once you are able to select the employee, you can play with it and execute other BAPIs.
Hope this will suffice.
I have used above links and created the WD Appl.
Regards,
Gary

Webdynpro for ABAP iView personalization not sticking?

We are currently on EP7 and are having a very odd issue with ABAP Webdynpro iView personalization.
For our Java Webdynpro iViews, we have used iView personalization quite a lot to change field labels, add text, change button text, etcc. all via portal content administration (ctrl+rightclick to make changes from iView preview). These changes would show as custom iView parameters settings on the Java Webdynpro iViews. Then we could put these iViews into our own portal packages and move them to other portals (QA, Production, etc).
However, this is not working quite right with our ABAP Webdynpro iViews. We personalized an iView on our DEV portal. The personalization changes showed just fine for all users (ie. changes to input field labels). However, no new parameter settings show for the iView for the personalization. Also, after packaging, exporting and then importing the iView into the other portals (like moving from DEV to QA), the personalization is gone. We had to manually recreate this on the QA system. However, we do NOT want to do this on the production portal of course nor do we want this to be the method/solution going forward.
So has anyone seen this? Is this some issue/difference between the ABAP and Java webdynpro iView templates?

If it is WebDynPro ABAP iview, if you do the personalization, then your personalization is persisted in ABAP stack. You need to transport it in ABAP i.e R/3 development system to R/3 Quality system. Transporting only iview is not enough.
Note : If you do the personalization for the ABAP iview, it will not be saved in the portal, it will be stored in the ABAP stack.
Thanks
Manoj K

MSS Iview error -Could not connect to the R/3 System

Hello All,
I've configured ESS BP in my Portal successfully and it's running perfectly fine. Now i've imported MSS also without any problems. Now the issue is when i'm launching the My Staff iViews it gives me a message "Could not connect to the R/3 System" . These iViews using the system object "SAP_R3_HumanResources" which has been used by the ESS iViews also. Now ESS iViews are working fine with the same system object but MSS iviews are giving me the error message.
My System landscape :
MSS BP Installed: BPMSS601_19-20001489
R3- 4.6C
Portal : EP6 Sp11
WAS: 6.40
Any help will be highly appreciated.

Hi Mahesh,
Thanks for your repley, I am using the "SAP_R3_HumanResources" as a default alias, The same alias is working fine for my ESS Configuration.
I tried to test connection for the "Connection Test for Connectors" i am getting following error.But Connection test is success for the "ITS Connection"
com.sap.mw.jco.JCO$Exceptionoccured->Connect to SAP gateway failed Connect_PM TYPE=A ASHOST=XXXX SYSNR=00 GWHOST=XXXX GWSERV=sapgw00 PCS=1 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR service '?' unknown TIME Wed Aug 30 16:42:35 2006 RELEASE 640 COMPONENT NI (network interface) VERSION 37 RC -3 COUNTER 11
my understand is , ESS is working fine for me because ,ESS iviews are IAC's based iviews which are running on ITS(ITS connection is working fine for me),
i think some problem with connectors(jco).....could you please suggest me.
Thanks
Aravinda

NW04 EP6 Sp13 & ECC5.0 - Problem previewing MSS iviews

We have just completed an install of NW06 EP6 SP13 & ECC5.0 at the back-end and are looking to implement ESS and MSS. In trying to preview an MSS iview, I am getting errors with the connection. A pre-requisite may be missing. This is our landscape:
ECC5.0
Abap Stack
EP6 SP13
Java Stack
latest versions of MSS and ESS BPs
The system connectivity, aliase, SAP Logon Tickets have been configured. The test connection is working. The userids in Portal and ECC5.0 are the same. LDAP is being used for initial Portal authentication.
With EP6 SP2, a back-end plug-in was required and we are unable to find one for ECC5.0. What do we need on the back-end for the front-end and the back-end to communicate and allow us the capability of previewing the ESS and MSS iviews?
Any help on this will be greatly appreciated.
Thanks in advance.
Regards, Neeta

Hi,
Note that I am running EP6 SP13 in NW04 and our backend is ECC5.0. The link I am trying to preview/run is, per Ketuls suggestion :
http://sapptdapp1:50800/webdynpro/dispatcher/sap.com/pcui_gp~xssutils/XssMenu
The error message I get is (rather long....):
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
Root Cause
The initial exception that caused the request to fail, was:
 com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCOClient name 'SAP_R3_SelfServiceGenerics_MetaData'. No such JCO destination is defined in the SLD
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:493)
 at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:247)
 at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:221)
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101)
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:144)
 ... 53 more
See full exception chain for details.
Correction Hints
Retrieving a JCO destination with name 'SAP_R3_SelfServiceGenerics_MetaData' from the System Landscape Directory (SLD) failed, as the destination could not be found in the SLD. The most probable reason for that is that the destination has not been maintained yet.
Use the preinstalled Web Dynpro Content Admin application to check/edit the destination. Use the Ping and Test functions of the Content Admin to verify that each destination is properly configured.
Additional information about the System Landscape Directory and the Web Dynpro Content Admin can be found in the SAP Developer Network (SDN) and in the Online Help for the SAP Web Application Server (installed with SAP NetWeaver Developer Studio and available online).
Note: the above hints are only a guess. They are automatically derived from the exception that occurred and therefore can't be guaranteed to address the original problem in all cases.
System Environment
Client
Web Dynpro Client Type HTML Client
User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)
Version
DOM version
Client Type msie6
Client Type Profile ie6
ActiveX enabled
Cookies enabled
Frames enabled
Java Applets enabled
JavaScript enabled
Tables enabled
VB Script enabled
Server
Web Dynpro Runtime Vendor: SAP, Build ID: 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-19:20:18:44[UTC], changelist=356134, host=PWDFM026)
J2EE Engine 6.40 patchlevel 95420.313
Java VM Java HotSpot(TM) 64-Bit Server VM, version:1.4.2_06-b03, vendor: Sun Microsystems Inc.
Operating system SunOS, version: 5.10, architecture: sparcv9
Other
Session Locale en_US
Time of Failure Wed Sep 28 08:42:46 EDT 2005 (Java Time: 1127911366734)
Web Dynpro Code Generation Infos
sap.com/pcui_gp~xssutils
SapDictionaryGenerationCore 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:08[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:19[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
SapGenerationFrameworkCore 6.4012.00.0000.20041104141254.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:52:59[UTC], changelist=298452, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:08:32[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:31[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:22[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary 6.4013.00.0000.20050606171352.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:59:38[UTC], changelist=351719, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro 6.4013.00.0000.20050609113138.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:05:19[UTC], changelist=352442, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
SapWebDynproGenerationCore 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:09:01[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
sap.com/tcwddispwda
No information available
sap.com/pcui_gp~xssfpm
SapDictionaryGenerationCore 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:08[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates 6.4013.00.0000.20050606171348.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:02:19[UTC], changelist=351717, host=PWDFM026.wdf.sap.corp)
SapGenerationFrameworkCore 6.4012.00.0000.20041104141254.0000 (release=630_VAL_REL, buildtime=2005-04-21:19:52:59[UTC], changelist=298452, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:08:32[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:31[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore 6.4013.00.0000.20050606171700.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:56:22[UTC], changelist=351724, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary 6.4013.00.0000.20050606171352.0000 (release=630_VAL_REL, buildtime=2005-07-04:19:59:38[UTC], changelist=351719, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro 6.4013.00.0000.20050609113138.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:05:19[UTC], changelist=352442, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
SapWebDynproGenerationCore 6.4013.00.0000.20050606172055.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:09:01[UTC], changelist=351729, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates 6.4013.00.0000.20050628104636.0000 (release=630_VAL_REL, buildtime=2005-07-04:20:19:30[UTC], changelist=356134, host=PWDFM026)
sap.com/tcwdcorecomp
No information available
Detailed Error Information
Detailed Exception Chain
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Error while obtaining JCO connection.
 at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:90)
 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:87)
 at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:73)
 at com.sap.dictionary.runtime.DdDictionaryPool.getDictionary(DdDictionaryPool.java:48)
 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:242)
 at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker.getDataType(DataTypeBroker.java:213)
 at com.sap.tc.webdynpro.progmodel.context.AttributeInfo.init(AttributeInfo.java:485)
 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:436)
 at com.sap.tc.webdynpro.progmodel.controller.Component.getController(Component.java:365)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.getPublicInterface(DelegatingComponent.java:142)
 at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdGetBackendConnectionsController(InternalFPMComponent.java:204)
 at com.sap.pcuigp.xssfpm.wd.FPMComponent.wdDoInit(FPMComponent.java:170)
 at com.sap.pcuigp.xssfpm.wd.wdp.InternalFPMComponent.wdDoInit(InternalFPMComponent.java:110)
 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:370)
 at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:608)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
 at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248)
 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.doGet(DispatcherServlet.java:48)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:159)
Caused by: com.sap.tc.webdynpro.services.sal.sl.api.WDSystemLandscapeException: Error while obtaining JCO connection.
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:146)
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnectionUnMapped(SystemLandscapeFactory.java:172)
 at com.sap.tc.webdynpro.services.sal.sl.core.SystemLandscapeInternal.getJCOClientConnectionUnMapped(SystemLandscapeInternal.java:83)
 at com.sap.tc.webdynpro.services.datatypes.core.DataTypeBroker$1.fillSldConnection(DataTypeBroker.java:77)
 ... 50 more
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to resolve JCOClient name 'SAP_R3_SelfServiceGenerics_MetaData'. No such JCO destination is defined in the SLD
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.resolveConnectionParameter(JCOClientConnection.java:493)
 at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.init(AbstractJCOClientConnection.java:247)
 at com.sap.tc.webdynpro.serverimpl.core.sl.AbstractJCOClientConnection.<init>(AbstractJCOClientConnection.java:221)
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.JCOClientConnection.<init>(JCOClientConnection.java:101)
 at com.sap.tc.webdynpro.serverimpl.wdc.sl.SystemLandscapeFactory.getJCOClientConnection(SystemLandscapeFactory.java:144)
 ... 53 more
Thanks, Neeta

MSS Homepage Customization

Hi All,
We have a requirement where in MSS Homepage customization is required.Portal version in use is EP5.0 and we have SAP 4.6C as R/3.
Customization through Homepage Framework concept is not there in SAP 4.6 C it seems.And help is this regard with be highly appreciated.
Regards,
Richa Sinha

It sounds like your "Home Page" is actually a Workset Map iView, as there is no Homepage configuration in 4.6C.
You should just be able to create a new iView/Page and link it to the Workset at the same level as the other pages that appear in the menu. The Workset Map iView should then pick up the new page and display it.
You can enter descriptive text and specify a pictogram (graphic) in the properties of the new page.
Regards,
John
PS - if you upgrade your portal to EP7, the pictures become "clickable".

Modifying ESS/MSS iViews

Hi,
Can someone please guide me to how I can modify standard ESS/MSS iViews, for example, to remove unwanted UI elements etc. The portal version is EP6. Also, I understand that with EP7 most iViews are Web Dynpro Java/ABAP, can these be modified also? Is there any docs or how to guides which will show me how to do this? Are there any Weblogs out there that anyone knows of? I've been searching and searching but have had no such luck thus far. All help will be very appreciated.
Thanks
Tony.

The "cookbook" for ESS is available via service.sap.com (the specific OSS note is attached too can be found with a search on here....sorry, don't know it right off). The cookbook does apply for EP6 and ESS ECC5.0. Basicaly, it steps you through setting up NWDI(JDI), creating your "project", pulling the needed Webdynpro into your NW Dev Studio, modifying it and re-deploying to NWDI and onto the portal.
An even better way....there is an online class available from SAP (it is part of the ERP2004 training) that covers ESS/MSS in-depth as well as modifying the files. The entire course (of which ESS/MSS is a small part) is $500 USD last time I checked....well worth it.
The new ESS/MSS/self-service WebDynpros are based on the Floor Plan Manager framework which can be tricky to understand....the class above helps cover that too...has material I have found no where else but in the class.
Hope this helps.

MSS Iview error - Any body help me - Very urgent

Hello All,
I've configured ESS BP in my Portal successfully and it's running perfectly fine. Now i've imported MSS also without any problems. Now the issue is when i'm launching the My Staff iViews it gives me a message "Could not connect to the R/3 System" . These iViews using the system object "SAP_R3_HumanResources" which has been used by the ESS iViews also. Now ESS iViews are working fine with the same system object but MSS iviews are giving me the error message.
My System landscape :
MSS BP Installed: BPMSS601_19-20001489
R3- 4.6C
Portal : EP6 Sp11
WAS: 6.40
Any help will be highly appreciated.

Hello All,
I've configured ESS BP in my Portal successfully and it's running perfectly fine. Now i've imported MSS also without any problems. Now the issue is when i'm launching the My Staff iViews it gives me a message "Could not connect to the R/3 System" . These iViews using the system object "SAP_R3_HumanResources" which has been used by the ESS iViews also. Now ESS iViews are working fine with the same system object but MSS iviews are giving me the error message.
My System landscape :
MSS BP Installed: BPMSS601_19-20001489
R3- 4.6C
Portal : EP6 Sp11
WAS: 6.40
Any help will be highly appreciated.

Error in the Standard MSS iview?

Hi,
I am using "startprocess" mss iview from Content Provided By Sap,when click on preview it shows bellow error.But same iview is working in my Development System.
Error
com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name mss~hras
    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:442)
    ... 40 more
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to load page
     at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:528)
     at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:192)
     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:756)
     at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:291)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
     at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
     at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: javax.naming.NamingException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name msshras [Root exception is com.sapportals.portal.prt.runtime.PortalRuntimeException: Failed in WD JNDI lookup. javax.naming.NameNotFoundException: No child found in WebDynproContext with name msshras]
     at com.sapportals.portal.pcd.gl.JndiProxy.getObjectInstance(JndiProxy.java:51)
     at com.sapportals.portal.pcd.gl.PcdGlContext.getSemanticObject(PcdGlContext.java:919)
     at com.sapportals.portal.pcd.gl.PcdGlContext.getSemanticObject(PcdGlContext.java:692)
     at com.sapportals.portal.pcd.gl.PcdGlContext.lookup(PcdGlContext.java:69)
     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:526)
     ... 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 mss~hras
     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:442)
     at com.sapportals.portal.prt.jndisupport.DirectoryManager.getObjectInstance(DirectoryManager.java:56)
     at com.sapportals.portal.pcd.gl.JndiProxy.getObjectInstance(JndiProxy.java:47)
     ... 38 more
Please guide me to solve the problem
Thanks
Srikanth

No child found in WebDynproContext with name "mss~hras "
check the code where you define that.
see the thhread below which is similar issue
Description attribute of PCD element
Points are welcome if it is helpful
Koti Reddy

HR iViews are not getting displayed and showing "Page can not be found".

Hello,
I am facing an issue in the EP 7 wherein all the standard HR iViews are not getting displayed and showing "Page can not be found".
We have added S_SERVICE autorisation object to user used for the relative JCO as well by looking at other similar forums but that did not help.
I have attached last part of log from file application.log under "F:\usr\sap\EP1\JC01\j2ee\cluster\server0\log"
#0002A537D2A6006A0000027300001C4C00046E3590936E5F#1247076244733#/Applications/WebApplications#sap.com/irj#com.sap.engine.services.servlets_jsp.server.runtime.context.ServletContextImpl#Administrator#12374##n/a##b7291b106be911de8d8a0002a537d2a6#SAPEngine_Application_Thread[impl:3]_27##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.runtime.context.ServletContextImpl#Plain###application [irj] prt: init#
#1.5 #0002A537D2A6007A0000001200001C4C00046E35AAA74D33#1247076682222#/Applications/WebApplications##com.sap.engine.services.servlets_jsp.server.runtime.context.ServletContextImpl#Guest#0##n/a##cf997d306af811dec69d0002a537d2a6#Thread[Finalizer,8,system]##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.runtime.context.ServletContextImpl#Plain###application [irj] prt: destroy#
#1.5 #0002A537D2A6005F0000026C00001C4C00046E35C2814813#1247077082383#/Applications/WebApplications#sap.com/irj#com.sap.engine.services.servlets_jsp.server.runtime.context.ServletContextImpl#SKhatkale#12460##n/a##a7cb51e06beb11de8bd70002a537d2a6#SAPEngine_Application_Thread[impl:3]_6##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.runtime.context.ServletContextImpl#Plain###application [irj] prt: init#
#1.5 #0002A537D2A60075000002BD00001C4C00046E35C3AD4359#1247077102039#/Applications/Xss#sap.com/tcwddispwda#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#SKhatkale#12464##rrisep1p01_EP1_14481150#SKhatkale#b6d348006beb11deb9780002a537d2a6#SAPEngine_Application_Thread[impl:3]_31##0#0#Fatal#1#com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent#Plain###You do not have the authorization to start service sap.com/pcui_gp~xssutils/XssMenu.#
#1.5 #0002A537D2A6007A0000001300001C4C00046E35DDE07029#1247077541575#/Applications/WebApplications##com.sap.engine.services.servlets_jsp.server.runtime.context.ServletContextImpl#Guest#0##n/a##cf997d306af811dec69d0002a537d2a6#Thread[Finalizer,8,system]##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.runtime.context.ServletContextImpl#Plain###application [irj] prt: destroy#
#1.5 #0002A537D2A600650000024600001C4C00046E36B6DBE4D0#1247081181950#/Applications/WebApplications#sap.com/irj#com.sap.engine.services.servlets_jsp.server.runtime.context.ServletContextImpl#Administrator#12873##n/a##37e186606bf511de8bf20002a537d2a6#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.engine.services.servlets_jsp.server.runtime.context.ServletContextImpl#Plain###application [irj] prt: init#
Please let me know if anybody has come across such scenario before.
Thanks
Suhas
Edited by: Suhas Khatkale on Jul 8, 2009 10:09 PM

Hi,
This issue is now resolved. We followed up with SAP and they suggested to update the component EP-PSERV to latest patch which was earlier to patch 1. Later on we upgraded it to patch 4 and this resolved the issue.
Thanks
Suhas

Portal Runtime Error for MSS Iviews

Hi all,
Though this topis has been discussed several times in our forum, i could not make anything from it.
Portal Runtime Error

An exception occurred while processing a request for :
iView : pcd:portal_content/com.ssmcehr.ssmcehr/com.ssmc.pct.ehr.mss.folder.mss/com.ssmc.pct.ehr.mss.folder.roles/com.ssmc.pct.ehr.mss.role.mss_mgrs/com.ssmc.pct.ehr.mss.workset.manager_self_service/manager_self_service/com.ssmc.pct.ehr.mss.worksets.employee_information/com.ssmc.pct.ehr.mss.page.employee_career/com.ssmc.pct.ehr.mss.iview.pay_actions
Component Name : com.sap.pct.hcm.eeprofilegenericiviewtable.default
The exception was logged. Inform your system administrator..
Exception id: 09:51_08/12/06_0067_101532150
See the details for the exception ID in the log file

and the error log file ...

#1.5#00142216FF7C00640000003F000022F80004240E23838D08#1165543050906#com.sap.security#sap.com/irj#com.sap.security.logToFile#Guest#19####76b39fa0865f11db815c00142216ff7c#SAPEngine_Application_Thread[impl:3]_16##0#0#Error#1#/System/Security/Audit#Plain###Guest | LOGIN.ERROR | NONE = null | | Login Method=[default], UserID=[jothi], IP Address=[137.55.161.180], Reason=[Access Denied.]#
#1.5#00142216FF7C006100000031000022F80004240E23BE4303#1165543054765#com.sap.portal.ivs.semantic.systemLandscape#sap.com/irj#com.sap.portal.ivs.semantic.systemLandscape#Guest#19####790075d0865f11dba82400142216ff7c#SAPEngine_Application_Thread[impl:3]_15##0#0#Error#1#/System/Server#Java###Failed to get alias mappers sub context in the Portal Registry##

This occurs only for the LDAP users,if we create user in EP(manually) it's working fine..
Thanks in Advance,
Jothi.P

It got resolved by itself after restarting the Java server.

MSS iview customization not WebDynpro

Similar Messages

Maybe you are looking for