As most of us are aware that SAP has come up with a new UI buiding tool using Webdynpro ABAP as platform.Launch Pads though have been available for sometime now but with EhP 5 they enter into mainstream project development.SAP has added a Webdynpro ABAP flavour to SAP ESS with development of most of the services in WDA.Homepage Framework has been replaced with Launch Pad customization.
This blog will talk about how to use the existing SAP supplied launch pad for ESS and configure it to customer requirement.You must be on EhP5 and using ESS(WDA) role.
Navigate to Launch Pad Customizing using Tx LPD_CUST and select Role ESS Instance Menu.Open the role as make a copy by using Launchpad->Save as.(Very conventional 🙂 ) .Make sure you put a Custom namespace and a Custom role Name.
Now if you have used Homepage Framework in past then this might be a bit confusing because you actually do not need to do much.For adding New Area just add A New Folder; for creating Services use New Application;use Column Break for Segregating areas.You can hide services by dragging them into Inactive Application folder.For example i have hidden services Time Statement and added a new area Employee Search below.
The transport has to be triggered from the menu.In the launchpad you made the changes in, call from the menu ‘Launchpad’ -> ‘Transport’.Use a Z Package or a Standard one (which might be deleted on upgrade) to save the request.
Note:If you have issues in Transport check note 1584026.
And you are done with launch pad. 😉
Now you just need to point your Portal role to this Custom Role.And for that you need not log into portal 😕 .Since the application is hosted on ABAP stack ,so we can customize it from ABAP side.Employee Self Service uses Application HRESS_A_MENU Application Configuration HRESS_AC_MENU.You can make a Z copy of the same and make the changes(will not discuss how to do application configuration in detail here,may be another blog).
Open the Webdynpro Application config from ABAP Workbench Tx SE80 and Execute it in administrator mode (Shift+F8) .
Now go to Configure and provide the Custom Role Name you created earlier.
It will prompt you to create a request.Save in a custom package.Now you are truly done from ABAP side.Now if you have made a Z copy of the application configuration (You should !)than you have to use the same in the portal ESS role.Just change the highlighted properties accordingly.
And you are done.
Those who have worked with Homepage Framework will appreciate the simplicity,still Homepage Framework is supported and we can use it but then why should we 😛 .
Will talk more about application configuration and application integration in another blog.