Customers and Consultants always have questions about possibilities and recommendations for adopting ESS Menu. This blog tries to address certain topics that will help to make decisions for best possible apporach that fits your requirements. This blog is not meant to give a step by step instructions since there are already few discussion/blogs on this forum regarding this.
First of all always read documentation:
http://help.sap.com/erp2005_ehp_05/helpdata/en/ae/f1788ae9084f0bb85c962b9e38c2ed/frameset.htm
Launchpad Role: Launchpad role/instance is required to visualize the ESS menu using WD ABAP application HRESS_A_MENU with configuraiton HRESS_AC_MENU. This application uses a WD Component that reads the lauchpad role/instance (ESS/MENU) and displays the UI.
PFCG Role: PFCG role is required for 2 purposes. The first purpose is very important since it is how the backend ABAP server decides the authorization profile for performing activities. Second purpose is for UI visualization if customer wants to use NWBC HTML or NWBC Desktop version instead of SAP Portal. This role acts as entry point for menu rendering. Standard SAP role is SAP_EMPLOYEE_ESS_WDA_1
ℹ Note: Even in case of NWBC HTML or Desktop version you can use the WD Application HRESS_A_MENU and instead of NWBC visualization you can use launchpad based menu. In case of NWBC It is recommended to use the default NWBC visualization since it is a lightweight stateless UI.
Portal Role: Portal role is required in case you use SAP Enterprise portal to provide an entry point. Portal role provided with Business Package for Employee Self-Service (WDA) 1.50. This is a lightweight role which just has few iViews. Most important iView contains menu application (HRESS_A_MENU) and few other iViews for navigation purpose (OBN).
In Summary:
For Portal customers you need: Launchpad role (UI Visualization), PFCG role (authorization), Portal role (entry point)
For NWBC customers you need: PFCG role (UI Visualization + authorization)
Most common misunderstanding is that standard role ESS/MENU must be copied. Customers are allowed to edit standard launchpad since SAP maintains a different version for SAP and customer. Even if SAP ships changes then customer version is not overwritten. At any point customer can see SAP delivered version even if they add/edit some entries in ESS/MENU. You can see a menu in LPD_CUST -> Extras -> Show SAP Version
:smile: Steps if you directly edit standard launchpad role ESS/MENU:
:cry: Steps if you copy standard role launchpad ESS/MENU:
Still wondering which way to proceed?
ℹ Note: For PFCG and Poral role customizing there are established practices so this blog will not discuss this point.
Most common requirement is that I have different set of services offered based on employee groups, regions and what not ....
There are 2 choices:
In this case you create only 1 launchpad role/instance (or PFCG role) and based on BAdI HRESS_MENU you decide which users get which links visible. In SAP standard implementation only COUNTRY is used decide which applications are visible per country of user
ℹ Note: Same BAdI works for PFCG based roles as well since NWBC processes the BAdI at runtime after PFCG tree is built
Steps:
Advantages:
The only disadvantage is you need ABAP programmer to do this BAdI but is that a real problem?
Steps:
Disadvantages:
Still wondering which way to proceed?
Many customers decide to go this way by creating static/dynamic custom HTML pages, portal content editing tools to create menu structures. This option is always available but more expensive to implement and long term maintenance.
Check these blogs which may help
Embedding WD ABAP Self Services in custom buit pages and external portals
Adding custom pages (HTML or simple text) in ESS Homepage/Areapages (WD ABAP)
As you can see there are lotsof configuration possibilities and Hope this information helps in making better informed decisions regarding which way to go.
Do let me know with your comments if there are more scenarios that you have faced which made you to go in a different solution direction!!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
11 | |
11 | |
10 | |
8 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |