How-to add a custom Web Dynpro iView to the MSS Employee Profile (ECC 6.0)Skip to end of metadata
Attachments:23 Added by Markus Klein, last edited by Tulasi Palnati on Sep 05, 2008 (view change) show comment
Go to start of metadata
1. #Introduction
2. #Developing a Floorplan Manager Web Dynpro Java Application
3. #Create a new FPM-View
4. #Add the custom FPM-View to the Standard FPM-Application "GeneralInformation"
5. #Create a Web Dynpro iView
6. #Add the custom iView to the Standard Page "GeneralInformation"
7. #Result
1. IntroductionThe following document will explain the steps required to enhance the Standard MSS Employee Profile with a custom Web
Dynpro iView.
It will not discuss in detail how to create a Floorplan Manager Web Dynpro Application. A more or less detailed and uptodate
documentation about the Floorplan Manager can be found here.
2. Developing a Floorplan Manager Web Dynpro Java ApplicationFirst of all you need to develop a Web Dnypro Java Application using the Floorplan Manager Framework in order to later
integrate it into the MSS Employee Profile.
Figure 1: Create a new Web Dynpro Development Component
To access the Floorplan Manager Framework the FPM Components pcui_gp/xssfpm and pcui_gp/xssutils have to be
added as used Development Components to the Project.
Figure 2: Add FPM Used Componentes
For my simple example i just have created one single Web Dynpro Component. FPM-vise speaking its a Visual Application
Component.
Figure 3: New Web Dynpro Component
As the newly created Web Dynpro Component is a Visual Application Component the Interface IVAC from the used
component pcui_gp/xssfpm has to be implemented. See figure 4.
With the Interface Implemenation a new Window IVACWindow is created. As the FPM will use this window, the default
window can be deleted. Its important to embed the own View to this new Window (see figure 5)
Figure 4: Implement Interface IVAC
Figure 5: Embed View to Window IVACWindow
At the MSS Employee Profile when a user selects a new object, e.g. a new employee (see figure 5) the custom Web Dynpro
application needs to be informed about the new object selection. This is done using server-side eventing with the FPM
framework. In order to receive the new event we have to access the Business Logic Component FcObjectSelection from the
componentpcui_gp/xssutils.
Figure 6: Object selection
Figure 7: Used Wed Dynpro Component FcObjectSelection
We now need to map the Context of the BLC FcObjectselection to our own Web Dynpro Component to receive the newly
selected object. E.g. the personal number. With the mapping done, the context attribute objid gets updated everytime a user
selects a new object (figure 5). With the new objid at hand you can do implement your business logic. In this example i have
just created a View to display the context attribute objid (figure 8).
Figure 8: Context-Mapping
Figure 9: Demo View
The used Component FcObjectSelection is a non-visible FPM Component (Business Logic Component) thus the reference
to this componet has to be prepared and enabled. (see figure 10)
Figure 10: Attach Component to usage
We finally need to create a new application. For a FPM application several application parameter have to be defined. Which
ones are required can be read at the SAP FPM Doku.
Of great importance is the application property sap.xss.BaseConfigurationID.
Quote: It is used to define the path to the application configuration in the Portal Content Directory (PCD). This entry points
to the technical name of the FPM Application as defined in the Enterprise Portal.
As we do want to enhance the MSS Employee Profile application we have to set the parameter to the following value:
portal_content/com.sap.pct/srvconfig/com.sap.pct.erp.srvconfig.mss/com.sap.pct.erp.srvconfig.eepro/
com.sap.pct.erp.srvconfig.fpmapplications/com.sap.pct.erp.srvconfig.GeneralInformation
Its the PCD location of the FPM-Application of the Employee Profile General Information.
If we now would start the WD application standalone, without further configuration in the portal, we would start the FPM
application GeneralInformation, where the application parametersap.xss.BaseConfigurationID does point to. (see figure
11)
Figure 11: Running the custom WD Application
To have our own application added to this FPM application as well, we have to perform some portal configuration steps.
3. Create a new FPM-ViewBefore we can start with the necessary FPM configuration we have to assign our user in the portal the role Self-Service
Administrator(pcd:portal_content/com.sap.pct/specialist/com.sap.pct.erp.srvadmin.bp_folder/
com.sap.pct.erp.srvadmin.roles/com.sap.pct.erp.srvadmin.SRVAdministrator)
Also make sure the Use_CustomerExit_ParameterProvider parameter of the AppIntegrator portal service has the value true.
See Configuring the AppIntegrator Portal Service.
With the new role assigned, we now have to create a new FPM-View for our Web Dynpro Component. (see figure 12 and
13)
Figure 12: Create new FPM-View
Figure 13: Create new FPM-View
4. Add the custom FPM-View to the Standard FPM-Application "GeneralInformation"
Figure 14: Add the FPM-View to the FPM-Application GeneralInformation
Figure 15 Add the FPM-View to the FPM-Application GeneralInformation
With our Web Dynpro Component added to the MSS Employee Profile FPM-Application we are pretty much done with the
configuration needed. If we start our Web Dynpro Application again standalone we will see our own Component added. In
order to have it added when startung the Application from the portal as well, we have to add it to the standard Portal page
for the MSS Employee Profile.
5. Create a Web Dynpro iViewThe iView we have to create has to point to the standard FPM-Application GeneralInformation and not to our custom Web
Dynpro application. The Web Dynpro Application behind the FPM-
Application GeneralInformation is sap.com/mss~eepro/GeneralInformation
In figure 18 we can see our FPM-View we have created at step 3 and added to the FPM-Application GeneralInformation at
step 4.
Figure 16: Create a Web Dynpro iView for sap.com/mss~eepro/GeneralInformation
Figure 17 Create a Web Dynpro iView for sap.com/mss~eepro/GeneralInformation
Figure 18 Create a Web Dynpro iView for sap.com/mss~eepro/GeneralInformation
6. Add the custom iView to the Standard Page "GeneralInformation"As last step we simply add our created iView to the standard MSS Employee Profofile GeneralInformation Page. (see figure
19)
Figure 19: Add our iView to the standard portal page
7. Result... seems working Now everytime a new object is selected, our custom Web Dynpro application gets notified and has full
access to the new object (e.g. personal number).
Figure 20: Result
Important links of FPM
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e534c990-0201-0010-a6b3-ce6ad5ce83a0
https://www.sdn.sap.com/irj/sdn/softwaredownload?download=/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/
business_packages/a1-8-4/teched-2006-sdn-day/SDNDay_ESS_HR.zip
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/10119 Webdynpro Abap
webdynpro
floorplanmanager
fpm
mss
mss_howto
4 Comments
1.
Guest
For simple infotype iviews, generic iview seems to be a good solution,it can connect to an infoset query in the backend.o May 19, 2007
2.
Guest
Hello Markus,
can you please tell me the following:
1. If I copy an FPM application from the SAP provided content to my project folder. How do I find the application in the Portal
Content, when I try to create an iview depending on this copied application.
2. We have a 3 systems landscape. So I have to transport my changes to the other systems. I think it is not good to add
custom specific iViews directly to the SAP Content. What will happen in case of an update? All development is gone?
3. So I think to create my own FPM applications as a copy of the SAP FPM application. Then add the custom specific iView.
Then create a new page in Portal Content depending on my FPM application and create iViews from the components.
Annetteo Nov 15, 2007
3.
Guest
Hello Markus,
Appreciate if you could point me to a thread/WIKI that explains a similar enhancement using ABAP WD.
Regards,
Karthik. o Dec 04, 2009
4.
Fabricio Pereira
Hello,
Does anyone know what would be the procedure to migrate this kind of application from NW Portal 7.0x / ECC EHP4 to NW
Portal 7.4 /ECC EHP4?
I'm having issues after I create the views and assign them to the General Information FPM application.
After restarting the Portal, the views will appear under mss~eepro/GeneralInformation WDJ. I created the page making a
copy of this WDJ and pasting in another folder. After performing a "Update PCD objects", I can see the iView under the
General Information page I had created but when I preview it. it show errors everywhere...
The error are like:
java.lang.ClassNotFoundException: com.sap.pcuigp.xssfpm.wd.interfaces.wdp.IExternalIVAC ------------------------- Loader
Info ------------------------- ClassLoader name:
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Could not get interface class for
generating proxy controller in Component(path=FPMComponent.Z_EmergencyContact/EmergencyContactComp,
class=com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent)
Caused by: java.lang.ClassNotFoundException: com.sap.pcuigp.xssfpm.wd.interfaces.wdp.IExternalIVAC
Z_EmergercyContact is the ID created for the view in the FPM application.
Any thoughts on this?