To begin with, I am extremely excited to write my first ever blog..based on my understanding and work done in the projects.
The document aims to be a step by step guide for upgrading ESS/MSS on WDA.
On a high level, these are the steps that to be followed:
- Activate the relevant business functions
- Activate the needed services in Portal using SICF
- Launchpad Customization for the applications/services used
- Assignment of Custom Launchpad to WD Component/Application Config
- Adding Role and Instance to the Custom WD Component – in the App CC
- Adding the Custom Role (created in step 3) through PFCG
- Customize the Org Chart Visualization Object
- Importing the role in Portal
All these steps are discussed in greater detail below:
The attached screenshots are for MSS but same process is to be followed for ESS Upgrade as well
Turn on the Switches for EHP7 – MSS – using SFW5
As a first step, activate the relevant business functions using the T Code SFW5:
HCM, MSS on Web Dynpro ABAP (HCM_MSS_WDA_1) –
Use this business function to activate Manager Self-Service based completely on Web Dynpro ABAP technology for both deployment options for the Manager role:
- New SAP NetWeaver Portal role Business Package MSS Add-On 1.0
- Manager Self-Service for SAP NetWeaver Business Client
HCM, MSS on Web Dynpro ABAP 2 (HCM_MSS_WDA_2) –
You can use this business function to activate Manager Self-Service based completely on Web Dynpro ABAP technology for both deployment options for the Manager role:
- New SAP NetWeaver Portal role
- SAP NetWeaver Business Client
Refer to the link for more documentation on business functions for MSS on WDA – http://help.sap.com/erp_hcm_ias_2013_02/helpdata/en/d8/cb80a7bf06444ba9b2884c543dd5ac/frameset.htm
Activating the Services in SICF
The next important step is to activate the services which are needed in the Portal.
The below example shows the Custom WD Service created for ESS which has to be activated in the ESS Portal.
The activation can be done by selecting the service and doing a right click – and selecting Active or Deactivate Service.
Once, the services have been activated, the next step is to create a custom Launchpad. The details of the same are given in the Note – 1943809.
Below mentioned are the steps I followed to create custom Launchpad for my project and then assigned it to WDA Component.
- Create a custom Launchpad:
- Go to transaction LPD_CUST ,select ‘New Launchpad’.
Enter following details on the next screen :
Description: Custom Menu for MSS
LunchPad Type: FPM_UIBB
Right Click on ‘Custom Menu for MSS’, then select ‘New Folder’ to create new nodes like ‘MSS etc, then click on ‘Save’.
Once the Folders are created, you can drag and drop applications from the SAP standard launchpad to the custom one. You can add various types of objects in the launchpad like WebDynpro ABAP or Java Application, a SAP transaction, a URL page, a Portal Object etc.
Assign the custom Launchpad to FPM:
The next step is to assign the Custom Role created in the Launchpad to the Application Configuration:
Copy the standard HRMSS_HOMEPAGE to the Z Version and change the role:
Here, we can see that the custom Role ZXXX_MSS has been added to the Z Application Configuration
Adding the Custom Role through PFCG
Select the following IMG Path and change the standard Role to a Custom Role:
Copy the above role to Z role as below and then remove unwanted service and nodes.
Assign the z application configuration as below to the newly created Z Role:
Customize the Org Chart Visualization Object –
The next step is customizing the Org Chart Visualization
This can be done by updating the Role as below on the View – V_THVNAVLPEVENTS
SM30 – V_THVNAVLPEVENTS
Import the Z Role from Portal through Content Admin
The last step is to pull the Z role from Portal so that all the applications are visible in the Portal.
This can be done from the Content Admin.
Go to Content Admin and pull the Z Role from the backend the way shown below:
Import Custom PFCG Role to SAP NW Portal – http://help.sap.com/erp_hcm_ias_2013_02/helpdata/en/d8/cb80a7bf06444ba9b2884c543dd5ac/frameset.htm
SAP Note 1685257