SAP HCM ESS MSS Ui5 - Overview

Posted by G N May 19, 2015

Dear Friends,

Outlines of the document:

  • This document is intended to provide a brief summary of and an introduction of ESS/MSS Key functionalities in Ui5 technology
  • ESS / MSS Ui5 pre-requisite business components
  • Features and benefits of ESS MSS standard scenarios i.e Launchpad, My information, My services, My team, My team services and My reports etc.


Enjoy reading and welcome feedback.

What is ESS MSS - Ui5:

Employee Self-Service and Manager selfservice (SAPUI5) is an enhancement to the existing ESS and MSS solution based on Web Dynpro ABAP. With the release of ESS and MSS (SAPUI5), certain applications and functions are now available on SAPUI5, a new technological base.









I often hear back from customer when I ask “why do you want to implement the HCM Process and Forms”…....“I want my HR Process to move online and improve HR process” which is common answer I get from my customer’s.


So let us understand the real business objective of Implementing HCM Process and Forms.


The key factors which come’s to my mind is Increasing the Efficiency, Data Quality and Consistency.


Why Efficiency ?



Currently organizations are posing challenges especially who are still on paper based processes and as the usage of technology is changing rapidly, hence today Organizations are constantly looking for  increase in speed of data processing and improve their process efficiency ! For example getting an employee on-boarded or promotion’s completed in a timely manner is an obvious business imperative. The other aspect of process efficiency is the idea of taking less time from administrative staff, which ultimately results in labor cost savings.


Data Quality ?


Obviously improving data quality is a critical factor which will have direct impact on the HR administration cost’s. By configuring the business rules that are already configured for infotype processing within forms and process will ensure that quality of the data submitted would significantly enhanced. Data quality ensures driving accurate decision making and employee satisfaction.

This will also ensure that blame of missing paper work or human errors which can lead to legal actions for the employee’s.


Why Consistency?


Since the approval process is the part of the HCM Process and Forms framework, it helps organisations to adhere there policies are being followed with respect to the decisions made by the managers or HR administrations. Lack of consistency may lead to not meeting the legal standards especially in Public Sector or government organizations. Consistency will also ensure the tracking the progress over the course of time.

Corporate branding is very important and is visible all over the place across companies… Companies take pride in their brand and so their
corporate portal is no different.



With HR Renewal, SAP has revived the look and feel of the portal and to take one step further, we need to define the our own branded-background in the lanes.



Here is one quick and dirty way to brand your HR Renewal portal:



Transaction SE80 and click on MIME Repository. Then in the Name space area, navigate to the following location:


SAP > BC > BSP > SAP > ARSRVC_SUITE_PB > themes > bgimages




Under this location, you will find the images that are already provided by SAP. We will override these images. We need 2 images here- the thumbnail (*_thumbnail.jpg) and the background image (*.uxga.jpg)



Now before you upload any background and thumbnail image, make sure that the images are ready.


To Preparing the Image:


Thumbnail image should be 160 x 128 pixels and the background image should be 2600 x 1926 pixels. This is the same size as what is delivered
as standard by SAP.



Uploading images:


The easiest way would be to overwrite an existing image.



Right click on the *_thumbnail.jpg file and select Upload/Download > Upload and Replace






Select your image and click on Open button.



You have now uploaded the thumbnail image.



Repeat the same step for *_uxga.jpg file.


Go back to your browser and verify that the file is available for you to select as background. If you do not see the image at first time, go ahead and delete the cache, and restart your browser. You should see the newly uploaded image and set that as you background.



As an option, you can select this background as your personalization on the Page.



Good Luck.

Working with different clients, I noticed a common trend in ESS Requirements. Most of the clients I worked with, wanted to have some specific application visible for only a specific country or for a specific set of people such as store employees (for Retail organization), yardmasters (for railroads), executives (for banking organization) or certain services visible on specific conditions such as an ESS application link is visible only for employees above a specific band or level.


After doing a bit of research I found the use of SAP standard functionality - Dynamic rendering of Services.

This blog focuses on understanding this functionality given by SAP and its usability in different scenarios.


Let us understand this concept using an example.

Requirement - Enable one of the custom ESS applications only for store employees which can be mapped to organizational or personnel structure.


For a Retail Company, which has many frontline store employees, the requirement is to have the application Store Spending amount (Custom WD ABAP Application) enabled only for store employees. With this application, store employees can check the amounts they have spent at the store.  Here, the store employees are differentiated based on their specific organizational structure.

In standard configuration, ESS Application visibility access is controlled based on Country Grouping, but this requirement was to control based on personnel or organizational structure. So, for this scenario we considered the Organizational structure since the retail store employees were mapped to a personal sub area.  This should get determined dynamically based on user’s log in, his employee number and his organizational structure.

For such scenarios, Dynamic rendering of services functionality is being used.

This functionality makes use of standard BAdI’s given by SAP:


With the help of these BAdIs, the attributes of an application can be changed dynamically at runtime eg. Hide/show, enable/disable etc.

For the requirement stated above, I made use of the BAdI, HRESS_MENU.

When using this BAdI Implementation, Application Alias need to be defined in Launchpad Customizing under Advanced Parameters. The Application Aliases will control the dynamic processing of portal services. Application aliases are used as a key to control application attributes.




The step by step process to do this in system is described below:

Step 1 - Go to Launchpad Customization, LPD_CUST

pic 1.png

Step 2 - Select the specific Application and mention the Mandatory and option parameters.

pic 2.png

Step 3 - Provide the Application Alias as the personal sub area

For the eg taken above, personal sub areas ending with ‘06’ are for the retail store employees. This is used as a key to control the application attributes in the BAdI.

pic 3.png

Step 4 - Once you define the Application Alias as the personal sub area(06 – for store employees), the next step is to set the condition in the BAdI, HRESS_MENU such that, if the logged in employees personal sub area is not ending with ‘06’, then set the service attribute CV_ISVISIBLE to invisible for application where application alias = ‘06’


pic 4.png


pic 5.png

This will ensure that the employees, who are not from personal sub area ending with 06, do not see the custom application - Store Spending amounts.

The HRESS_COUNTRY_FILTER BAdI is active in standard SAP delivery and this implementation checks the COUNTRYGROPUNG parameter.

last pic.JPG

Few other scenarios where this functionality can be used is:



Enable Stock Options

Organizational Structure (Executives, VPs)

Enable Requisition related links

Role based (Recruiter, HR Admins)

Enable Tax related links

Country Grouping based (W4 for US, Form 16A for India)

Enable Time Card related links

Personnel Structure (for hourly employees, temporary employees)

The requirement was to filer the employees that manager could see in team view by criteria based on values in PA. Managers only wanted to see hourly paid employees.


Of course this would be problematic is an hourly paid employee was to hold a subordinate chief position as the whole structure below that employee would not be visible. In this case business rules wouldn’t allow that scenario to happen.




This blog hopefully guide though step by step of implementing a custom function module which drives the selection and configuring the team viewer to use it.


Step 1 – Create Copy of Function Module

At the lowest level, the selection is done by function module HRMSS_TARGET_EVAL_PATH. Take a copy of this function module and modify it to suit the business requirements.

Take a copy of the functional module used for selection by the object selection rule.

  • In the example of Object selection rule ‘MSS_BIZ_RULE5’, the function module is ‘HRMSS_TARGET_EVAL_PATH’
  • Change the function module to filter the selection as required


Step 2 – Create Copy of Object Selection Rule

     IMG: Personnel Management -> Manager Self-Service(WDA) -> Object and Data Provider -> Object Provider ->  Define Rules Object Selections

    • Change the Function Module to point at the copy created in the previous step


Step 3 – Create a Custom Object Selection


     IMG: Personnel Management -> Manager Self-Service(WDA) -> Object and Data Provider -> Object Provider ->  Define Object Selections

    • Make a copy of ‘MSS_BIZ_NOD’
    • Edit the rules for navigation objects to point at the custom rule


Step 4 – Create Custom Structure Rule(s)

     IMG: Personnel Management -> Manager Self-Service(WDA) -> Organisation Structure Views -> Define  Organisation Structure Views

    • Make a copy of  the rules being used in the Chart Config ’MSS_TMV_BIZ_xxx’
    • Edit the structure rules to point at the custom Object Selection


Step 5 - Customise Org Chart Visualisation

     IMG: Personnel Management -> Manager Self-Service(WDA) -> Team View -> Configure Organisational Chart visualisation.

    • If not already done so use the ‘Transfer Standard Organizational Configuration’ to Transfer ‘MSSBIZVIEW’
    • The use ‘Maintain Transferred Organizational Chart Configuration’ to activate the new Chart Config


    • Create a new Nav field view for the Structure which points at the custom Navigation Field Group:






Employee or job satisfaction plays a crucial role in the domain of employee retention. A happy worker is a productive worker. Or to put it the other way around, unhappiness among workers in the USA results in a whopping $300 billion loss in productivity per year. Some Western European countries do quite well, especially Denmark, Luxembourg, Finland and the Netherlands, but still, any improvement in this space brings significant business benefits.




This is clear for most HR managers, but what does it have to do with SAP and what is Fiori by the way?

Employee satisfaction is impacted by multiple factors including topics such as compensation, work-life balance, perceptions of management, flexibility, safety, etc. Considering how fast the amount of computer work is expanding in the work force, it is clear that the use of software has an increasing impact on employee satisfaction. This is where SAP Fiori comes into the picture.


Intro to SAP Fiori

One of the key priorities of SAP is to improve the user experience of their software. SAP Fiori is constantly growing collection of applications which have been created with the user experience enhancement in mind. They are simple, they don’t have all the possible buttons and functions on the screen only some users might need, but they focus on what is important for most customers. They are coherent, which makes jumping from one Fiori app to another a fluid experience. They are responsive, so they run on desktop, laptop, tablet and smartphone. They follow authentication and authorization principles you expect from SAP, so they can provide content based on user roles.




Investing into SAP Fiori is a smart move. It is estimated that $1 investment in user experience brings a return of $2 to $100. Employees become more productive by intuitive use of SAP anytime and anywhere, making less errors, they need less training and support, etc.

What can Fiori do?

SAP has created 300+ Fiori apps (as of today) across many lines of business and industries, you can find an overview here. Furthermore, the above mention design principles are applied to the whole SAP software portfolio, even to acquired cloud solutions such as SuccessFactors. Very important to know that SAP brings out new Fiori apps few times a year in so called Fiori waves.




Can Fiori be applied to specific business needs?

There many possibilities in this area. The out-of-the-box Fiori apps can be extended. SAP has released the Web IDE, which is a great tool available on the HANA Cloud Platform and soon on premise as well. This tool allows developers to make easy changes with drag&drop and deep and complex changes in a way which is future proof in terms of upgrades.


The Theme Designer tool makes it possible to adjust the look & feel including logos, images, colors, fonts, basically any element of the theme.


Even more important to know that SAP made the Fiori guidelines available and this opened up the possibility for customers to develop their own Fiori-style applications (using SAPUI5 and Gateway/OData) running on the Business Suite and/or on SAP HANA.


An important piece of the Fiori technology is the Fiori Launchpad, which can be seen as a shell around the Fiori apps. It provides navigation, personalization and configuration features. It is basically a central point of access for Fiori (and even some non-Fiori) apps combining transactional and analytical aspects.



Improving user experience of SAP solutions hasn’t been as easy as now. SAP has created Fiori applications for the most common scenarios, among them HR very prominently. In case the out-of-the-box applications are not sufficient, there are brand new web and cloud based tools available to make adjustments and even new developments possible in a future proof way.

Scenario:            Manager, able to Select or Search Position from Entire Organization Structure while creating requisition request. In Standard, Manager See only those Organizational units which Reports to his Organizational unit. If, requirement is Manager could be able to see Entire Organization Structure (from root Organization Structure) and select or search position from any org unit, we need to configure OADP ‘Organizational structure Views’.

Normally, in E-REC MSS Recruiter Raise requisition request and is able to see entire organizational structure. But Our requirement is Recruiter need not to raise requisition request. So HR Manager has to raise requisition request. So for HR manager system shows only reporting organizational units and thus not able to select position or search position from entire Organizational structure.


We have provided two custom View’s with which one can able to see entire Organizational Units and restrict these views for other managers through Web Dynpro application.


With below step by step OADP configuration we have added two custom Views i.e. for Position search and Select from Entire Organizational Units


  Position Selection.png


Go to: SIMG_SPORT Transaction


IMG PATH: Personnel Management --> Manager Self Service à Object and data provider --> Define Rules for Object Selection.

Rule: For Navigational Objects.

·        In this rule to get all the organizational units under root organizational unit in the Navigational area we need to use this Evaluation path with required Depth.





Rule: For Position Search

·        This rule we use in Object Selection that we need to passes to Parameter Group.




Rule: To fetch Root Organization Units

·        In standard process to get root object we use SAP_MANG evaluation path which returns current organizational unit. But our requirement is to display entire organizational structure so we can achieve this by using function module or custom evaluation path that returns Top most Root Organizational unit.


    This Function Module is copied from standard function module HRWPC_PATHROOTS and importing User name and returning Root Organization Unit for that Username.




Rule: (Target Objects) To fetch Positions against Organizational units.

·        Mainly we use this rule to get all the positions against the organizational unit and display the positions in Data Views.




IMG PATH: Personnel Management --> Manager Self Service --> Object and data provider --> Define Object Selection.

    Object Selection for ‘Select Position Search from Organizational Unit’.

·              In this Object selection we passes three rules i.e. SOHAR_ROOT, ZSOHAR_NAV, ZSOHAR_TGT.

SOHAR_ROOT- Returns the root organizational unit.

ZSOHAR_NAV- Returns the Organizational units under Root organizational unit.

ZSOHAR_TGT- Returns positions against organizational units.



Object Selection for ‘Position Search from Entire Organizational Unit’.

·        For position search we need to define two Object selection i.e. ZSOHAR_POS_SRCH and ZSOHAR_PS_PRM

ZSOHAR_POS_SRCH we pass to View (Position Search).

ZSOHAR_PS_PRM we pass to Parameter Group.


Object Selection for ‘Select Position Search from Organizational Unit’ passed to Parameters for Object search.

  • In this object selection we are using Rule: ZSOHAR_ROOT which returns the root organizational unit and ZSOHAR_POS_SRCH which returns staff assignments along with organizational structure (required for position search).
  • This Object Selection we pass to Parameter Group and that parameter group we will pass to Class that is defined in object selection for position search ZSOHAR_POS_SRCH.



IMG PATH: Personnel Management --> Manager Self Service --> Object and data provider --> Group Parameters for Object Search.

Here we have to give Object Selection which is having Root Objects and Target objects and this Parameter group, System will pass to class that we already mentioned in Object Selection ZSOHAR_POS_SRCH.



IMG PATH: Personnel Management --> Manager Self Service --> Object and data provider --> Define Organizational Structure View.


View: For Position Search


View: To Select Position from ‘Sohar Entire Organizational View’.



IMG PATH: Personnel Management --> Manager Self Service --> Object and data provider --> Group Organizational Structure View.

Here we have added two custom views to search and select position from entire organization unit.



Can provide help for any other scenarios related to OADP Configuration. Feel free to ask


Argh!!! I blurted, there are times when a developer hands are tied and he feels frustrated as he is unable meet some simple requirements. This blog is an outcome of my recent experiences with development of FPM based HCM P&F forms. This happens to be my 13th blog(so named it aptly ) and I wanted to be a critic here, but these are the things you need to watch out before you take a plunge into HCM PF using FPM architecture.


1. Form Printing - You dont have a direct option of printing HCM FPM forms, the direct web printing does not come out well and may not be accepted. The others option is to build Adobe forms and link it, this adds to your effort and you have to rely on  Live cycle designer to build the form and ADS to render the form which again would incur licensing costs.


2. Screen Manipulations/Good Layout Screens- If your form requires heavy screen manipulations like hiding, unhiding, color, text manipulations then FPM forms is not a fit, Adobe is miles ahead. For example, a customer requirement to highlight changed personal data on form cannot be met by FPM forms, there is no option to manipulate a input box to highlight in a different colour other than just hiding or making it input or read only. This can however be met by round about ways, but there is no clean solution. And many would have already noticed that the FLUID designer is a very difficult to handle workbench, and definetly slower compared to se80 or ADLC. Again if you are looking for beautiful layout screens like Adobe then you need to look somewhere else.


3. Reference Numbers - This may not be very common requirement, but some customer would definetly want to differentiate their processes using differnt alpha numeric prefixes, as far as I came to know there is no way you can identify the process inside the Badi, the Badi needs to be enhanced by SAP so that we can differentiate the processes.


4. Attachment in different Sections : In HCMPF you see the attachments on the top, but ofcourse you can personalize and make the attachments below or sideways. But if you have a requirement to have attachments in every sections so that you want to differentiate which attachment is for  which section then you hit a wall with HCM P&F.  Also added to this, there is not a way to sort the attachments based on requirements, there should have been a sequence numbering in the attachment configuration.


5. Very complex workflows - if you are in for complex workflows where in you will have to send tasks back and forth it can get very tricky vis-a-vis your custom forms since you have three different tasks and one task cannot manage all three things, I wonder why not make a single task and have a binding parameter signifying what is the stage, for example, approve, back to author etc.


6. Component reuses - Component reuse is a difficult proposition here, though you have the possibilites of composite UIBBs and detailed explanation of which you can find in Chris blogs. Data needs to be exchanged between UIBBS using singletons or other mechanisms, but sometimes the HCM PF just dont behave as you would want it to and can get you in troubled waters.


7. Editing in approval screens - This may not sound logical but customers have come with requirements of editing the form and as well as want to approve, with FPM forms the approval screen is just read only, even if you get a section editable by composite UIBB having a custom WDA you still will not able to send back the values to the ISR framework, it just rejects it.


8. Customized buttons/Work Item Texts/Customized message after submitting - If you need name your button text as per your wishes then the only option is to enhance the component and to rephrase work item texts you clone the task, I did not see another option to do this. And you will not find an option to have customized message on submission.


9. Tab out trigger - In Adobe the possibilites are immense, if you know javascript then you are your master. In WDA there isn't an option of tab out trigger, you specifically have to hit enter. This could be big draw back when calculation on form has to happen as soon as you tab because it is quite possible that user forgets to press enter, the remedy for this is to trigger events during check or send.


10. Hiding a  button/Comments as tabular display - I am not sure if I have left any stone unturned here, but honestly I did not find a way to hide a button which has led to embarrasing situations with customer where we had to design a link to act as a button. The button cannot be hidden but the link can be hidden. You do have option to hide button if it comes with the table. There is also no easy way to display the comments in a tabular format if you want to. I think the better design would be to have it like the history where you have a more neater display.


11. Data Manipulation in subsequent steps - For some strange reasons I found that you cannot default data in next stage data based on previous stage, you can still do it by removing that field in the initial form scenario stage and making it available in next form scenario stage, but you end up with some other issues later on. The framework just does not re-initialize the data if it was already present in previous step.


12. Performance - It is a common knowledge that adobe based HCM PF have severe performance issues when the form gets bigger and FPM based ones aimed to overcome this very problem which plagued adobe, but at the end of the day you still have unacceptable performance levels in FPM forms. We compared the performance with custom WDA forms which has 10 times more data than HCM PF, I am quite confident that our custom forms were 10 times faster in rendering, the problem could lie because of the generic framework or lack of optimization of the ISRs.


13. The ever present bugs - And lastly, dont be surprised if you are hit by multiple bugs in the course of your development. Fortunately, SAP was prompt enough to suggest the possible notes for resolution and save the day for us.


Deciding the right design can make or break a project, I hope these points which I have experience would be of some help to others and bail you out from cutting a sorry figure in front of the customer, it is good to understand the limitations of a framework before you commit anything. Thanks for reading, your suggestion/comments are welcome.




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.




Launchpad Customization


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:
    1. Go to transaction LPD_CUST ,select ‘New Launchpad’.



Enter following details on the next screen :
Role: ZMSS
Description: Custom Menu for MSS
Namespace: ZMSS
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







  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:


content admin_1.JPG



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




              View Sundeep Sethi's profile on LinkedIn    

    We undertook a project to migrate the ESS solution implemented in Web Dynpro Java to Business Package for Web Dynpro ABAP (1.5).

    I have shared my experience in working on Travel & Expense Implementation in the below blogs:


    Demystifying FPM for Travel & Expense (FITV_FPM)


    Demystifying POWL and Feeder Class in Travel Management


    In this blog I would share my project learning's on Adding custom field in Record Working Time and Applying dynamic filtering to links appearing in Launchpad.


    1) Adding custom field in Record Working Time application:

    The Record Working Time application can be found in the package "PAOC_CATS_ESS_WDA".

    Web Dynpro Component "HRESS_C_CATS" and Web Dynpro Application "HRESS_A_CATS_1".


    Challenge was to introduce a new column "Task Short Text" (Data Element LTXA1) in the Record Working Time application ALV table.

    First approach would be to utilize the fields "DISPTEXT1" or "DISPTEXT1" in structure "CATSFIELDS".SAP recommends in order to introduce custom fields on the Record Working Time Web Dynpro ABAP screen or CAT2 transaction we should make use of these two fields. By maintaining proper mapping in this structure your custom field can be displayed and it can be populated by using User-Exit "CATS0009-CATS: Customer-Specific Text Fields in Data Entry Section". You can read the documentation of this exit in transaction SMOD.


    However the main challenge arises if we have to introduce a third custom field. In my project we have already used the fields "CATSFIELDS-DISPTEXT1" and "CATSFIELDS-DISPTEXT2" to display Engagement Name and Client Name. Now we wanted to introduce a new column which would display Task Description.

    I wondered why should SAP restrict the customers to allow populating only two custom fields using the user exit "CATS0009". That is a million dollar question which only SAP can answer.

    Anyhow in order to add a third custom field follow the steps below:

    i- Add your custom field to the structure "CI_CATSDB". The fields can only be of TYPE CHAR or NUMC. Let's say we maintained ZZTASK_DSC in the structure "CI_CATSDB"



    ii.- Next go to txn SPRO and navigate to Create Customer fields and then select "Make field Assignment" in the pop up


    iii.-SAP allows to add upto 10 custom fields using this approach. Select field No. 1 and the corresponding CI_CATSDB field here



    iv.- Go Back and select option "Add customer fields to field selection" => "Data Entry Section" and set field "Additional field 1 i.e. CATS_ADDFI-FIELD1" to DISPLAY.



    v.-As a result the Task Short Text Column will be visible on the Record Working Time WD application.



    vi.-Now the tricky part, how to populate data in this column. If the requirement was to populate this field only in CAT2 transaction we could have done this using EXIT "CATS0002". But in order to populate this field on WD ABAP screen we have to implement an Enhancement to the WD ABAP component "HRESS_C_CATS". In my scenario I implemented a Overwrite Exit to the Method "BUILD_TSDATA" in the Component Controller. Append the following code after pasting the SAP code in the Overwrite Exit-

    **prior to this line paste the SAP code of BUILD_TSDATA method****

    ******Custom Code Starts here******

    DATA lv_vornr TYPE VORNR.

    DATA lv_engm TYPE AUFNR.

    DATA lv_task_desc TYPE LTXA1.

    DATA lt_f_et_return TYPE bapirettab.

    FIELD-SYMBOLS <ls_f_et_return> LIKE LINE OF lt_f_et_return.

    DATA lt_f_et_value_list_npact TYPE ptrv_web_activity_npact_t.

    FIELD-SYMBOLS <ls_f_et_value_list_npact> LIKE LINE OF lt_f_et_value_list_npact.

    FIELD-SYMBOLS <lv_desc> TYPE any.

    LOOP AT <dyn_table> ASSIGNING <dyn_wa>.


    lv_vornr = <dyn_fs>.


    lv_engm = <dyn_fs>.



    IF lv_engm IS NOT INITIAL AND lv_vornr IS NOT INITIAL.



           I_ORDERID                 = lv_engm

           I_ACTIVITY                = lv_vornr

    *      I_DESCRIPTION             =

    *      I_MAXROW                  = 150


           et_value_list_npact =             lt_f_et_value_list_npact

            et_return =                       lt_f_et_return


        LOOP AT lt_f_et_value_list_npact[] ASSIGNING <ls_f_et_value_list_npact>.

         ASSIGN COMPONENT 'DESCRIPTION' OF STRUCTURE <ls_f_et_value_list_npact> TO <lv_desc>.

         lv_task_desc = <lv_desc>.





       <dyn_fs> = lv_task_desc.

       MODIFY <dyn_table>  FROM <dyn_wa> .



    Crux of the Code: In this method the FIELD-SYMBOLS <dyn_table>, has the run time data which is displayed in the Working Time ALV table. We fetch the Task Description using FM " PTRM_WEB_ACTIVITY_NPACT" and set its value in the <dyn_table> structure for the custom column ZZTASK_DSC which we have added in step iii above.


    2) Applying dynamic filtering to links appearing in Launchpad

    Earlier in the Home Page Framework links were filtered by using Proxy Classes which were specified at the Service Level in SPRO Configuration.

    With the Launchpad the dynamic filtering is done by setting up Alias in the Launchpad Application and then putting the filtering logic for this alias in the HRESS_MENU BADI.

    I will try to explain the scenario by using example of Travel and Expense. In the home page framework the links for Travel and Expense were controlled through the Proxy Class "CL_TRAVEL_AREAPAGE". This class in turn called a standard FM " PTRM_WEB_TRIPS_WELCOME_SCREEN" which determined based on authorization of the logged in user, which links would be visible for the user.

    The implementation "PTRM_NEW_HRESS_MENU" of BADI "HRESS_MENU" takes care of filtering the Travel Plan links and does not apply filter on the links Create Travel Request, Create Expense Report etc. We had to apply custom filter on these links and other custom links based on authorization the user had.

    To implement this in the Launchpad follow the steps below:

    i- Create a custom implementation of BADI "HRESS_MENU" say "Z_PTRM_NEW_HRESS_MENU" in transaction SE19.

    ii.-Provide the Alias of the applications as Filter Values for this Badi Implementation e.g. if in Launchpad you have maintained alias "CreateExpenseReport" for the Create Expense link, provide that as a filter value.


    iii.Create implementation class say "ZCL_PTRM_NEW_HRESS_MENU" for this BADI implementation and ensure that the class implements the interfaces "IF_EX_HRESS_MENU" and "IF_BADI_INTERFACE" . In the method "IF_EX_HRESS_MENU~MODIFY_APPLICATION_ATTRIBUTES" write your custom code which will call the standard FM "PTRM_WEB_TRIPS_WELCOME_SCREEN" and hide or show the Create Request or Expense links.

    METHOD if_ex_hress_menu~modify_application_attributes.

       DATA: lv_trvof              TYPE office_find,

             ls_nwbc_context       TYPE cl_nwbc=>t_context,

             lv_client_environment TYPE i.


       DATA: l_employeenumber TYPE bapiempl-pernr,

             lt_www_links_ext TYPE ptrv_web_links_ext_t,

             lt_return        TYPE bapirettab.


       CLEAR lt_return.        REFRESH lt_return.

       CLEAR lt_www_links_ext. REFRESH lt_www_links_ext.



       DATA lv_pernr TYPE pernr_d.

       DATA i_name TYPE emnam.

       DATA lv_ccc_active TYPE xfeld.

       DATA lv_ccc_number_receipts TYPE i.

       DATA lv_request_active TYPE xfeld.

       DATA lv_plan_active TYPE xfeld.

       DATA lv_expense_active TYPE xfeld.

       DATA lv_own_trips_only TYPE xfeld VALUE 'X'.


    * Get employee number


       DATA: lr_emp_service TYPE REF TO cl_hress_employee_services.


           lr_emp_service = cl_hress_employee_services=>get_instance( ).

           lv_pernr = lr_emp_service->get_pernr( ).

         CATCH cx_hress.

           "DO NOTHING





           i_employeenumber      = lv_pernr


           e_ccc_active          = lv_ccc_active

           e_ccc_number_receipts = lv_ccc_number_receipts

           e_request_active      = lv_request_active

           e_plan_active         = lv_plan_active

           e_expense_active      = lv_expense_active

           e_own_trips_only      = lv_own_trips_only

           e_name                = i_name


           et_www_links_ext      = lt_www_links_ext

           et_return             = lt_return.

       CASE iv_application_alias.

         WHEN 'CallTravelRequest'.

           IF lv_request_active = 'X'.

             cv_isvisible = abap_true.


             cv_isvisible = abap_false.




         WHEN 'CallExpenseReport'.


           IF lv_expense_active = 'X'.

             cv_isvisible = abap_true.


             cv_isvisible = abap_false.



         WHEN 'CallTravelPlan'.


           IF lv_plan_active = 'X'.

             cv_isvisible = abap_true.


             cv_isvisible = abap_false.



         WHEN 'FindRouting'.

           cv_isvisible = abap_false.


         WHEN 'MaintainProfile'.

           cv_isvisible = abap_false.


         WHEN 'CallAssistantPOWL'.

           cv_isvisible = abap_false.


         WHEN 'CallExpressExpenses'.

           cv_isvisible = abap_false.




    In a similar way you can control visibility of any of the links in launchpad by maintaining its Alias in lpd_cust transaction, and including that alias as a filter value in a custom implementation of the BADI HRESS_MENU and making sure you handle the case of that alias in your custom code in the implementing class of the BADI implementation.

    This blog is intended for those planning to Implement HR Renewal 1.0 FP4 based on the below component versions:


    This information would be handy to start with the prerequisite setup/ configurations to be done for enabling HR Renewal services.


    Versions: Ehp7 SP2 for ERP 6.0 – HR Renewal FP4 is delivered

    Note: No Licence for neither HR Renewal nor SAP Netweaver GATEWAY services. There are few limitations

    • Below information is based on EA-HR 607 SP14

    Technical Prerequisites:

    Option 1

    • - NW 731 SP7
    • - NW UO SP01 with many addons (Basis can check)
    • - GATEWAY
      • GATEWAY SERVER CORE NW 703/ 731 SP04
      • GW_CORE 200
      • SAP IW FND 250
      • SAP WEB UIF731
    • - IW_PGW SP4 (This used for approvals on Manager Portal)
    • - LSOFE 607
    • - SAP_HR 604

    Option 2

    Deploy NW 740

    NW740, UI services and Gateway component objects are part of NW 740 (i.,e SAP_UI, SAP_GWFND components)

    No of components needs to Install in NW 740 is less (So you can check with the Clients IT department or Basis if there are no challenges from the them we would prefer this).


    • Some important SAP Notes:
    1.         1701634 - HR renewal 1.0: Release Information Note (This is master note for all Release Information)
    2.         1691232 - Installing SAP HR renewal 1.0 on ERP 6.0 EHP6
    3.         1691231 - Release strategy for the ABAP add-on SAP HR renewal 1.0
    4.         For Browser Compatibility:
    • 1903267 - Browser: Internet Explorer 11 Release Notes
    • 1708020 - Support of UI5 based on ABAP applications in the portal


    • Features : For features activate the below Business Switches


                  Required Business Function:


                   HCM, Employee Self-Service on SAPUI5 (HCM_ESS_UI5_1

                   HCM, Manager Self-Service on SAPUI5 (HCM_MSS_UI5_1)

                   HCM, Workforce Viewer 01 (HCM_PD_ORGVIS_1)

                   HCM, Personnel & Organization 03 (HCM_PAO_CI_3)

                   HCM, Personnel & Organization (HCM_PAO_CI_4) - Additional Versions for Chile, Spain, Hong Kong and New Zeland

                   HCM, Learning Solution 05 (HCM_LSO_CI_5)


    • Other ESS/ MSS Settings Checklist:

             1. The following settings has to be done to complete ESS  Settings

                 OData Services for lanes

                 OData Services for SAPUI5 applications

                 Customizing settings

             2. Payroll Control Center: The Payroll Control Center allows you to create and run your own business-specific master data and payroll checks

                                                    before and after payroll runs

                 Authorization Framework (HCM_LOC_CI_63) - This switch allows you to determine which employees are authorized to see which checks and which                                                                                         check results

                  HCM, Payroll Data Source Framework (HCM_LOC_CI_62)- The switch allows your business-specific checks and their results available on a single UI,                                                                                                        tailored to the needs of each payroll user.


    • Launchpad Settings:

              1. The launchpad role HRPAO instance BASIC_ACTIONS is for the actions lane and for combining with country-specific repository launchpads.

              2. For organizational management the instance used  BASIC_ACTIONS_ORGANIZATION .

              3. You can add the country-specific instances and BASIC_ACTIONS_ORGANIZATION to the BASIC_ACTIONS instance by using the feature Link to a                   Repository Application

              4. Country Specific Launchpad also available.





    This blog describes the steps to enhance standard infotypes for ESS Personal Profile (Details Screen). The purpose of this blog is to consolidate all steps required for enhancement of decoupled infotype and the subsequent changes in UI in ESS. This is just to make life easier for beginners and doesn't include too much of advance concept. It covers the following areas:

    1. Enhancing standard infotype 0006 for country US
    2. Screen Validation
    3. UI to infotype field Conversion
    4. Controlling field visibility according to subtype


    What it does not include:

    1. Enhancing the infotype screen in backend (Transaction PA30). Hence no screen validation and screen field conversion for PA30.


    Scenario: Add custom Mobile No. and a related fields in infotype 0006. This will be used for US employees. The field is subjected to format validation and display of field requires conversion. Finally, these fields should be hidden for certain subtypes.


    Lets Begin:


    Step 1: Enhance infotype 0006 structure


    We need to add field in CI include CI_P0006. So as you can see, I have added 2 fields: i) Mobile No. ii) Do not disturb (For not receiving text messages).




    Step 2: Enhance UI screen structure for infotype 0006


    Since we only want to use these fields for country US, we should only be enhancing only the US specific structure. It is assumed that already a US screen exists (as we are only enhancing) and you can check the same by opening Component Configuration:


    You can also create your own country specific screen from scratch and add the configuration here. Note that configuration key here allows us to configure screen based on MOLGA and Subtype for an infotype.


    Screen structure of IT0006 for US is HCMT_BSP_PA_US_R0006 which you can check in transaction GENIL_MODEL_EDITOR (or in view V_T588UICONVCLAS). So we add the fields in the customer include inside this structure (note that I have 4 screen fields for the above mentioned 2 database fields and hence require conversion):




    Step 3: Enhance the UI screen


    As we saw in step 2, there is already an FPM UIBB configuration HRESS_CC_PER_DTL_ADDRESS_US for US. So now we need to add our fields in the same. There are 2 ways to do that: i) Create Enhancement ii) Create Customization. I am going with the later one for no special reason. So we open the component configuration HRESS_CC_PER_DTL_ADDRESS_US and select 'Create Customizing' from additional function.




    As we added our fields in the UI structure, the custom field would automatically appear (courtesy feeder class CL_HRESS_PER_DETAIL) in the field list. So now we can add them to the screen. You can also make the necessary field attribute change here, e.g. show/hide label, display type and so on.




    That's all we have to do to enhance infotype with custom fields if there are no requirement of validations and conversions. Please note, in case of automatic conversion, you must keep the screen field name same as DB field. However, we want to go further by having UI screen conversion.


    Step 4: UI Conversion


    For this, you must implement BADI HRPAD00INFTYUI (with filter value for infotype we are implementing for). For our requirement we need to implement only 2 methods: INPUT_CONVERSION (convert screen structure to DB structure) and OUTPUT_CONVERSION (convert DB structure to screen structure). Take caution in using MOVE-CORRESPONDING here since this BADI is called after SAP standard UI conversion. So this statement may disturb the already converted structure. It is advised to touch only the required fields.


    Since my logic of conversion is similar to what SAP standard is for telephone number, I reused the standard class-method for INPUT_CONVERSION.




    For OUTPUT_CONVERSION, I am implementing only a little piece of standard code.




    Step 5: Business Logic check (validation)


    Now we want to put some validations around our custom fields e.g. mobile number should be only 10 digit in total. To do this we need to implement BADI HRPAD00INFTYBL. In our scenario, validations are only required for insert and modify operation. So we add the code inside INSERT_COMPUTATIONS and MODIFY_COMPUTATIONS. To throw an error, we can add message to import parameter for message handler.




    Remember that checks implemented using this BADI would not be performed in transaction PA30 subjected to condition. And the condition is: if the infotype is not fully decoupled. You can find this information by reading views V_T582ITVCLAS in parallel with V_T582ITD. However, this is good for only standard infotypes since all new custom infotypes that we create through PM01 are automatically built on decoupled framework.


    Step 6: Hide custom fields for particular subtype


    Now this requirement can be achieved in two ways:

    1. Create a different component configuration - As noted in step 2, with the use of configuration key, we can configuration different screen based on MOLGA and subtype. However, I wouldn't use this just for hiding a couple of fields. I would rather use this option when there are some other major screen differences.
    2. Enhance the feeder class and set the field property dynamically - I find this more appropriate in the current scenario.


    As mentioned earlier, feeder class CL_HRESS_PER_DETAIL provides all data to our UIBBs. So we'll enhance GET_DATA method by using implicit enhancement at the end of standard code.

    Points to note:

    • We want to ensure that our code should trigger only for infotype 0006 for US. So first we check that and then implement our code.
    • You can always get access to data (business data) using MO_ENTITY object.
    • Screen field meta data is container in table CT_FIELD_USAGE. You can make changes to field properties by updating values in this table. Also ensure that if you have done changes in this table, parameter EV_FIELD_USAGE_CHANGED should be set.




    If you want to hide fields at subtype level per country version, you can make use of views: V_T588MFPROPS and V_T588MFPROPC. However, above logic gives more control in terms of further conditions to base our field visibility.


    Thats it. We are done with customization. Now lets test.




    So we got our custom field on screen and also the validations are working. Now lets check other subtype for which we have hidden the checkbox:




    Yes, the check box is hidden !


    Hope its helpful for all those who are new to this area and find themselves tangled in too much information on infotype decoupled framework (as far as enhancing infotype is concerned) and ESS personal profile page.


    I would also recommend reading the excellent blog Summary of configuration options in ESS Personal Information scenario by Sagar (Keep it bookmarked ).



    Working on NWBC was an interesting and Learning experience with exploration into unknown areas. Analogous to the UWL in the Portal we have a similar concept of worklist with POWL in the NWBC HTML. POWL gives lot of flexibility in terms of changing the layout and also gives options for the user to define his own queries and manage his Worklist, but then you might need to educate every user on how to create a query and not everyone is tech savvy and would want to learn on how to do it.


    This particular requirement from the client to have different processes as different tabs switched on my research engine. First option of letting the user to configure thier own was ruled out, so we need to have a global setting which reflects at the role level for every user.


    One thing to bear in mind is in case of HCM P&F where generic tasks are used for processing and approvals we cannot make a distinction based on tasks so the only option let with us to distinguish the processes is through task text.


    So here are the simple few steps,


    1. Find out the application ids, for the manager inbox the application id used is usually MANAGER_MSS_INBOX_2, and for the HR Admin ASR_HRADMIN_INBOX.


    2. As the second step you need to define a query ID. Use the transaction code powl_cockpit, and use standard POWL.

    POWL_Pic 1.PNG

    3. Click on maintain query, go into change mode and add a new entry.



    4. Enter the query name, description and POWL type ID, use the same what the standard entry uses - MANAGER_MSS_INBOX_WI.


    5. Now set the Query Parameters. Click on the query parameters and entry a query criteria, I have entered a pattern search based on the task text.




    6. Once you have created the query, you need to register this query with the application. Select the application and click on register query.



    7. Enter the Query ID, the Category as MANAGER_MSS_WORKFLOW_TASKS, and the sequence nos for the tab and category.



    8. And now you are done.




    Hope this helps some one, and thanks for reading.



    Raghavendra Prabhu

    Before we start into the actual discussions there are few common questions which are often asked by the customers like as follows:


    How/ What/ Why - HR Renewal 1.0 ?


    HR Renewal is part of the HCM functionality which is aimed for delivering and increase the productiveness for the HR Professional role. This HR Renewal focuses mainly for the HR Professional Roles which includes -  Employee and Manager Self Service applications, Personnel/ Organization Administration.


    HR Renewal is available as an add-on for EhP6. With EhP7 SP2, contents are available in the standard content.


    Notable Improvements done in HR Renewal are:


    HR Renewal has many functional and User Interface improvements like additional HR Professional Role, and the new user interface option for (P&F) forms development based on WebDynpro for ABAP.


    I have been taking a lot on HR Professional Role - So what is it ?


    Here goes ...HR Professional Role is a part of HR Renewal with some features like

    • New navigation across OM and PA Search/ Structure functionalities
    • New blend of UI for  data changes, single activities, mass data changes
    • New end user productivity features like Save as Draft, Favorites, Recently used
    • New tools for Ad hoc reporting
    • Additional interfaces for HCM P&F which includes leveraging SAP FPM to develop WD ABAP forms
    • Role Specific start pages (Eg such as bookmarking important items for action, favorites etc..)
    • Collaboration - This feature allows users to communicate with other users about there tasks


    Implementation and Migration Consideration:


    This session may give you the insights of the considerations for Implementing or Migrating to HR Renewal


    Can we use HR Renewal on Enterprise Portal or NWBC ?


    Yes, HR Renewal can be used using deployment methodologies NetWeaver Business Client  or Enterprise Portal. Choice between NWBC and Portal may evaluated on many factors depending on the Customer requirements or Existing System etc. But in general NWBC is preferred if all the services are bult on WD ABAP technology. However customers who want to still the use of WD Java can then Enterprise Portal is the obvious choice (Off-course WD ABAP also is accommodated).


    What are the minimum requirements for implementing HR Renewal ?


    As a pre-requisite minimal requirement is ECC 6.0 and Ehp6 and above.


    The feature packs are support packages to Enhancement Packs 6 and 7. The mapping of the support packages to the feature packs for HR Renewal1.0 is as follows: (This info taken from SAP help)

    Support Package 03 = Feature Pack 1

    Support Package 05 = Feature Pack 2

    Support Package 10 = Feature Pack 3

    Support Package 14 = Feature Pack 4


    Is SAP NetWeaver Gateway configuration required for HR Renewal ?


    This is a tricky question,but obvious that it is not required if HR Professional Role and Landing Page are not used. But in future HTML5 Landing pages for ESS and MSS Gateway is required. SAP UI5 based Landing Page for HR Professional Role required NetWeaver Gateway.


    Off course no additional license required if you are using NetWeaver Gateway with SAP delivered HR Functionality


    WD ABAP Vs UI5 ?


    • Not all WDA ESS/ MSS services are available in UI5.
    • Most of the HR Professional services are on WDA.
    • UI5 services are mostly new one's.
    • For WD ABAP applications more customization or Personilization options for new fields available.
    • OData services used for UI5 applications.


    Roles and Security ?


    • Security roles built on WDA applications.
    • Revamp required for existing security roles and hence there is an impact to security.
    • New HR Professional role.


    Hope i helped few takeaways from this blog which can be helpful

    In this blog, I m going to enlist all the important links for upgrading or customizing EHP5, EHP6, EHP7, HR Renewal ,Fiori and others widely discussed topics.

    Before this you need to know and  decide are you sticking with JAVA WD (No more enhancement for HCM) or moving towards WebDynpro ABAP based ESS/MSS and UI5 Landing pages etc (recommended approach). Since you are doing Technical upgrade, its better to migrate to latest technology as in both cases testing would be involved and you can get much more out of testing when you plan to migrate.

    Please note once you plan to move away from JAVA WD to Newer WDA or UI5 based ESS/MSS, its a project in itself ie

    For customers not planning to use WDA ESS/MSS then :

    When you upgrade your Portal to NW 7.3 or 7.4 and need new BPs and doesnt want to upgrade ECC ie from EHP4 to EHP6/7, Please check below note

    SAP NOTE 1874939 - SAP Business Suite for SAP NetWeaver 7.4 hub systems

    you will find any dependency using UDA Tool http://service.sap.com/uda

    Need to use this new Business packages for new NW version

    BP ESS 1.41
    BP MSS 1.41

    SAP_ESS 633

    SAP PCUI_GP 633

    SAP_MSS 630

    To understand how the EA HR and SAP HR versions vary in each EHPs

    SAP versioning, part 2 (why EHP7 contains SAP APPL 6.17)



    Now if customers plans to upgrade or install new EHP5/6/7 HCM, They have two deployments options ie without using Portal or use NWBC

    Here are the options and benefits listed.


    Moving towards ESS WD ABAP from WD JAVA, would indeed be a reimplementation but customer can preserve their configuration in backend but not in portal if they choose to use new Iviews. If they want to run parallel both JAVA WD and ABAP WD Iviews it ll require two set of roles once they activate switches for ESS and MSS as listed in below notes and links.

    Please always familiarize with this new technology and switches, any new functionality in enhancement package is typically done through a switch, only once you activate this switch in SFW5, you ll see this option.

    All Business Switches are listed here and their Important documentaion ie what and which functionality each switch brings and also the roles.

    Each EHP release, brings its set of roles which you need to use :

    Important Notes to consider :

    1450179               ESS Based on Web Dynpro ABAP Available as of EHP5

    1701634               HR renewal 1.0: Release Information Note

    1685257               Portal Upload ie Business Package Deployment EHP6 above and beyond for WDA

    HCM, Employee Self-Service on SAP UI5 - Human Capital Management - SAP Library   EHP5 ESS (EA HR 605) Switch HCM_ESS_WDA_1

    Business Package for Employee Self-Service (WDA) 1.50 - SAP Library                        EHP6 ESS (EA HR 606)  HCM_ESS_WDA_2

    HCM, ESS on Web Dynpro ABAP 3 - Human Capital Management - SAP Library            Business Switches        

    ESS with UI5 Landing Pages ie HR Renewal, Now with HR Renewal we have provided functionality in Support package level as opposed to enhancement.

    Configuration guide can be obtained from here (please note this require S user id)




    Admin guides which provide information are listed here :


    HR renewal is a shipment name for quarterly shipments (also called feature packs ) in the HCM area that belong to the so-called In-Advance Shipments (IAS). With the HR renewal shipments, the software component EA-HR is shipped in advance to the next ERP enhancement package.



    Support Package 03 = Feature Pack 1

    Support Package 05 = Feature Pack 2

    Support Package 10 = Feature Pack 3

    Support Package 14 = Feature Pack 4   UI5 based Landing Pages for ESS/MSS and few services launched.

    Related blogs on this are :

    Steps to configure HR Renewal Landing Page

    Configuration of Suite Page Builder (UI5)

    HR Renewal 2.0 begins

    HR Renewal - Useful Information and important links

    HR Renewal 2.0 FP details :

    HR Renewal 2.0 FP1 Available

    An overview of latest functionality in HR Renewal 2.0 Feature Pack 1

    Roadmap Forms and Dynamic Processing Rules - enhanced data quality and higher system automation with HR renewal 2.0 Feature Pack 1


    In ESS WDA, Homepage customisation is replaced with launch pad customisaiton, You need to use LPD_CUST or PFCG for configuring links or hiding them etc apart from the BADI given in ESS, Refer below

    Tips & Recommendations for customizing ESS Menu (WD ABAP)

    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)



    SAP Note 1943809, to call custom role ie ZESS in your Application etc

    Important Customisation links Launchpad and Notes LPD_CUST, BADI Usage and Dynamic rendering

    Dynamic Rendering of the Menu (BAdI HRESS_MENU) - Business Package for Employee Self-Service (WDA) 1.50 - SAP Library

    Application Parameters - Business Package for Employee Self-Service (WDA) 1.50 - SAP Library

    How to hide Help Center, Personalization, Map, Directory and Index options from ESS Overview Screen



    Addition of custom infotypes or additional standard Infotypes in ESS

    Adding any Info Type IN ESS in EHP5/6 through WebDynpro Configuration

    Dummies Guide: Configuring Overview Screens in Personal Profile

    Exciting Enhacements to ESS Personal Information Profile in Enhancement pack 6



    You can check delta of functionality between different releases using the SAP Solution Browser

    For MSS we have  called MSS ADD ON

    1588625    Release information for Manager Self-Services Add-On 1.0

    1582553    Release strategy for the ABAP add-on EA-HR_MSS

    1582460      EA-HR_MSS: Overview note



    Check the help links here first to understand the functionality :

    SAP Library - Manager Self-Service (WDA)

    What's New in MSS HR Renewal 2.0



    Configuration of ZMSS role or calling custom role in MSS :


    Manager SelfService - How to customize team view application Hierarchy in NWBC HTML

    MSS Reports

    What happened to HR Reporting and Analytics in EHP6 and HR Renewal 1.0?

    Reporting on Operational Data Providers (ODP)



    Workforce Viewer


    HR Renewal 1.0 Feature Pack 4: New Org Chart functionality – The Workforce Viewer



    POWL or UWL

    Most often there is a confusion that POWL uses SWFVISU, It doesnt . Information on configuring POWL can ve accessed here

    To hide unnecessary queries from the POWL use trabnscation code POWL_COCKPIT and delete those queries from the inbox you are using.


    Leave request single level approval TS21500003 for WDA, This WF should be used

    Muliple level approval  configuration as of HR Renewal FP3 Configurations for enabling Multiple approvers for Leave Request

    SAP Notes for customisaiton of Leave request and Working time approval

    1773641     ESS LEA: Web Dynpro ABAP based Leave Request use in UWL

    1800335   CATS WDA: Web Dynpro ABAP based CATS use in UWL



    Fiori and HR Renewal


    Fiori apps are designed to work on desktop, tablet and smartphones using the same code and based on SAPUI5.

    SAP Fiori does not replace HCM UX renewal, which is an in-depth renovation across all HR processes. SAP Fiori focuses on simplification for the most broadly and frequently used business functions for enterprise users.  Fiori includes HR apps, but has a broad scope, including not only employee and manager but also purchasing agent and sales reps.  Fiori doesnt require extra licensing costs and is available free with software licenses



    What everyone in HR (or anywhere) should know a... | SCN


    Wave 7 FIORI Introduction:


    New Fiori Apps for HCM

    HCM Processes and Forms

    HCM Processes & Forms: My Blogs

    HCM Processes and Forms with new User Interface

    HR Renewal 1.0: HCM P&F – Creating a Basic FPM Form

    HCM Processes & Forms: Why pick ONE form UI?...we have OPTIONS!


    SAP_CORBU Theme


    New Visual Identity - Corbu Theme for ESS/MSS


    Application Parameters and URL Parameters - Reference - SAP Library

    ie WDTHEMEROOT to set SAP_CORBU theme in WD_GLOBAL_SETTING Web Dynpro ABAP application


    SAP Note 1679127 - Transfer style sheets (themes) to Web Dynpro applications

    Testing of ESS/MSS application in SE80:

    Want to access ESS/MSS WD applications without portal?

    Translation in ESS/MSS:

    ** TEAM FPM ** - All about Translation and Texts of FPM applications


    Filter Blog

    By author:
    By date:
    By tag: