Skip to Content

Implementing HR Renewal 1.0, Feature Pack 04

What Continental AG learned during the Customer Validation Process

This blog was co-written by Sherin Hanna of Continental AG and SAP’s John Macy and Carrie Lande.

With sales of €32.7 billion in 2012, Continental is among the leading automotive suppliers worldwide. As a supplier of brake systems, systems and components for powertrains and chassis, instrumentation, infotainment solutions, vehicle electronics, tires, and technical elastomers, Continental contributes to enhanced driving safety and global climate protection. Continental is also an expert partner in networked automobile communication. Continental currently has approximately 173,000 employees in 46 countries.

Continental engaged with SAP to perform a customer validation of HR Renewal 1.0, Feature Pack 4 (FP04) in June and July of this year.  It was an action-filled time, resulting in the successful installation and configuration of many of the enhancements of FP04 as well as some of the previous feature packs.  Highlights included configuring and testing the new landing page and SAP UI5 applications for Employee Self Service (ESS), Manager Self Service (MSS) and HR Professional.

The purpose of this customer validation is to provide a proof of concept for HR Renewal 1.0 FP04 prior to its release to customers.  SAP provided support throughout this process while Continental provided a test landscape, a test plan and resources to perform the testing.  In a customer validation, customers typically benefit by getting access to the latest functionality in their own environment and getting to explore the software, while reducing the cost and time if they choose to implement it.
In this blog, we share some of Continental’s key lessons and experiences. 


One of the compelling features of the landing page delivered with HR Renewal 1.0 SP04 is the ability for a user to perform various activities from multiple roles in one page.  Users no longer need to navigate to different pages or user interfaces to launch all of their business critical activities.  The new landing page for ESS, MSS and HR Professional provide a much-improved and delightful user experience. 
Landing Page.png
Some functionality won’t be available if you have not implemented the corresponding back-end functionality already.  For example, you cannot use all of the capabilities of the Analytics lane if you don’t have Business Objects and/or the Business Warehouse in place.  Other examples are Employee Time Administration, Learning Solution, Recruitment, Benefits and Performance Management, to name a few.
To get started, be sure to review all of the documentation up front to help you plan the implementation.  Note that there are multiple sources of documentation.  The provided documentation assumes that you have successfully implemented and tested the previous Feature Packs – if you have not, you may have to consult the documentation for the previous releases and make sure that you haven’t missed key steps.  There are lots of SAP Notes, so be sure to review and apply them. While some may have been included in the latest Feature Pack, there may still be some that need to be applied.
Expertise from different areas will be required to install and configure various aspects of HR Renewal:
  • Basis skills for installation, applying notes and transports, activating business functions, confirming component version requirements for support package stacks and assisting with component registration if required.
  • NetWeaver Gateway installation and OData services configuration – The SAP NetWeaver Gateway and the OData services available therein are used to provide data to the UI5 applications. 
  • User Interface customization and configuration – Various user interface technologies are called from the applications in FP04.  Configuration may be required for HTML5 (UI5), Web Dynpro ABAP, SAP GUI for HTML (Web GUI), SAP GUI or services in SICF.
  • Design of landing page – As mentioned above, users can now launch many functions from multiple roles in one user interface.  As a result, there is configuration in the launch pads, roles, and the IMG to support content in the context menus available in Search and other lanes.  This design and configuration needs to be understood and completed.
Some areas for improvement that we identified during our testing include:
  • Speeding up the performance of the landing page and the browser (particularly for Internet Explorer 9)
  • Addressing issues with personalization and browser cache
  • Fixing documentation and configuration issues



Documentation review

It is important to review all documentation from various sources ( , service marketplace, IMG, and others) before beginning installation and implementation.  Examples are:
  • SAP Administrator Guide
  • Business Functions documentation
  • IMG Node documents
  • NetWeaver Gateway documentation
  • SAP Notes
  • And more …..

Notes, Notes and more Notes!

For HR Renewal 1.0 through FP04, we applied approximately 65SAP Notes.  As a result of our testing, we identified issues that resulted in several new Notes being issued. Some of these may or may not have been included in the current FP04 release.  Our advice is to help your Basis team research and identify Note requirements. 

If you don’t start from Feature Pack 03 . . .

We moved all the way from EhP6 to EhP6 with HR Renewal 1.0 FP04 and necessarily performed configuration to support HR Renewal 1.0 Feature Packs 00, 01, 02, 03, and 04.  There are numerous Internet Communication Framework (SICF) services, Business Functions and OData services that need to be activated to support functionality across the Feature Packs.  Even with a thorough review of documentation from all Feature Packs in the course of implementation, you may find that you frequently encounter error messages instructing you to activate services that you may have missed.

Some required configuration is not delivered by SAP

For example, the HCM P&F processes delivered by SAP are samples and not to be used productively.  Configuration to support processes such as Task Gateway Service for Tasks requires table entries for workflow task IDs and step IDs.  These IDs can only come from the tasks which customers create when building their own processes.  This means that customers need to build the workflows to support their own processes and use the task IDs and step IDs from those workflows to configure the table. 
Technical Details

Browser considerations

The landing page application performs best when using Chrome, followed by Firefox then Internet Explorer 10.  The poorest performance was experienced using IE9.  Consider revisiting corporate standards for browsers as appropriate. 

Multiple UI technologies

As suggested above, HR Renewal 1.0 FP04 leverages functionality from prior feature packs and enhancement packs.  When calling applications from the landing page, the actual functionality called may be based on HTML5 (UI5), Web Dynpro ABAP, SAP GUI for HTML (Web GUI), or SAP GUI.  Customers will need to be able to complete required customization and configuration within the context of each UI technology used. 

NetWeaver Gateway connectivity to SAP data sources

The SAP NetWeaver Gateway and the OData services provide data to the UI5 applications.  This constitutes an additional layer of configuration beyond that which was required for Web Dynpro ABAP applications. Make sure that you have resources on your project that can help with this.

Our Observations Regarding the New Functionality

Improved User Interface

The landing page UI is a great leap forward for SAP.  It’s obvious that it can work well across multiple devices, mobile or not.  It has a modern look and feel, comparable to other cutting edge user interface designs. 

Multiple role functionality available in a single landing page

In other words, since a manager is also an employee, they can perform their ESS and MSS tasks from within the same interface.  An HR professional can access their ESS tasks from within their HR Professional landing page. In particular, this capability is available in the context menus in Search and  Org Visualization (org chart).   


SAP product development, management and marketing have embraced extensive end-user personalization capability as an important functionality in this product. While we see potential benefits of this, there are different schools of thought regarding the desirability of personalization.
  • At Continental, we have made a point to disable end-user personalization in other self-service applications, because users have mistakenly hidden important functionality resulting in usability issues and numerous calls to the helpdesk.   
  • In the landing page, it is frequently necessary for end-users or system administration on behalf of all end- users to delete all end-user personalization so that security changes, catalog changes, and so on will be visible to end-users.  In our testing, we learned that when this occurs, the end-users must re-create the personalization which they previously had. We are concerned that this might be a source of confusion or frustration for our end-users.
  • In the current version, users must perform personalization upon initial logon to set up their landing page.  Because of this constraint, it is not feasible to disable personalization in the current version.
Our recommendations to SAP:
1.    Allow disabling of some if not all personalization system wide
2.    Provide settings to configure default personalization upon end-users’ initial logon
3.    Provide ability for administrators to make changes without requiring the deletion of end-users’ personalization


We are excited to have had the opportunity to test this great new functionality.  We think our users, even those who have never touched SAP, will embrace this new application.  We see excellent improvement in available functionality demonstrating potential solutions to existing Continental’s business challenges.  The new user interface is a vast improvement over prior releases.  We believe that the new HTML5 landing page and SAP UI5-based applications will make it easier for employees, managers and HR professionals to use SAP, changing our users’ experience and making their lives easier.
While we did encounter some moments of frustration during this process, it was a success.  We want to thank our colleagues at SAP for their assistance and for listening to our feedback.  In particular, development support from India which was provided as part of this customer validation was critical.  We appreciate their patience, expertise and the long hours that they worked to support us.  We are planning to roll this out over the next year and believe that we will see a lot of benefit from HR Renewal.  We are also excited to see what comes next!
Follow SAP ERP HCM on Twitter: @SAPHCM
Landing Page.png
You must be Logged on to comment or reply to a post.
  • Thanks for this, some great learnings.

    Think the whole re-alignment of browser tech might be challenging for enterprises. How does this go down with other areas of the business - or are they all using solutions that are happy to run on Chrome?

    I'm especially interested on options for how UI5 personalisation would/could be stored/managed. Hopefully I should have some time shortly to play with this too!

    Thanks for sharing.



    • Hi Chris,

      IE 9 / 10 browsers use only 4 to 6 threads. FF has a capability to use 8 threads. So, most website / webapps run better on these newer browsers. Chrome has the best capability to render HTML5.

      Having said the above, most enterprises use IE. HCM Renewal is fully certified on IE9 and above. We are looking to make more performance improvements that is going to be be coming soon.

      UI5 personalizations are stored in name.value pairs in the "properties bag" in the PERF scope of the user. Enabling / disabling of personalization is being discussed internally.



    • Speeding up the performance of the landing page
      and the browser (particularly for Internet Explorer 9)
      • This is being actively looked at. By the next SP of NW UI – in 1 month’s time – this would be significantly improved. A note is also being prepared for page-by-page loads and improvements in the cache-buster.
    • Addressing issues with personalization and
      browser cache
      • This has been addressed to the NW teams. I am hoping that once the system stabilizes – this should not be an issue – especially when using the NWBC Shell.
    • Fixing documentation and configuration issues
      • A decision was taken today that Dev will be providing a Step-by-step with screenshots doc in SCN.
        This will cover installation, configuration, BF switching and BADIs. We will
        start work on this next week.
    • Allow disabling of some if not all personalization
      system wide
      • This is being taken up in NW UI SP06/7. Has been asked by multiple customers.
    • Provide settings to configure default personalization upon end-users’ initial logon
      • This is also being taken up in NW UI SP06/7. There will now be a possibility to deliver default configured pages.
    • Provide ability for administrators to make changes without requiring the deletion of end-users’ personalization
      • Technical feasibility study underway. Our current design does not permit this...
      • A decision was taken today that Dev will be providing a Step-by-step with screenshots doc in SCN.
        This will cover installation, configuration, BF switching and BADIs. We will
        start work on this next week.

      Hi Alex!

      Has this document been finished?

      Could you please provide a link


    • Hi Alex,

      I'm also very interested in this Kind of Documentation:

                                  Alex Mathew
      • Fixing documentation and configuration issues
      • A decision was taken today that Dev will be providing a Step-by-step with screenshots doc in SCN.
        This will cover installation, configuration, BF switching and BADIs. We will
        start work on this next week.

  • Hi thanks for this, a Very Nice Blog.

    Quick question have you deployed EHP6 with HR Renewal via SAP Portal or is it standalone ?

    If so were there any issues deploying it via the portal other than the obvious ones mentioned !

    Many thanks


    • Hi James,

      At Continental, we've already been operating on EHP6 so we had simply installed HR Renewal 1.0 Feature Pack 04.  You can launch it via the portal or NWBC shell.  EHP6 is a pre-requisite for HR Renewal.



      • Hi Sherin, thanks for that we currently run ESS/MSS WDA for about 6000 employees, not quite your scale..... via SAP EP, technically is do your employees use SAP EP as a first point or contact for the HR area or are you a NWBC site out of interest, as we would be looking to deploy via the EP

  • Thank you all for putting this together.  We are about to start a project and the information here will be helpful.

    Great job in such a condensed timeframe.  It looks great.

    Take care,


  • For those of you who are interested, the RIN (“Release
    Information Note”)
    is 1701634 for HCM Renewal 1.0Feature Pack 4 (SP14)

  • Thanks for the blog Carrie.  We installed EHP6 earlier this year and are considering HR Renewal along with a fresh install of P&F to replace our aging PCR process.  This is great info.

    We (Graybar Electric) would love to compare notes with anyone else considering similar things.


    Chuck Koelling

  • Thanks for the post.  Appreciate the information on pitfalls such as performance issues.  I look forward to hearing on your experience in rolling it out.

  • Carrie, Sherin,

    Thanks for the information - we are in the process of implementing FP4 on HR Renewal and this helps.

    On equestion I have is, I see the rendering is great when landing page is called via URL in IE or Chrome, but when called via NWBC I see some rendering issues.

    I am working with our BASIS team, but curious if you know about it - did we miss something or perhaps a note on this? When we were doing R&D with FP3, this was not the case - it looked great on NWBC.



    • Hi Nakul,

      The NWBC runtime in the BASIS (URL = /default_host/sap/bc/nwbc) now has a successor as /default_host/sap/bc/UI2/nwbc and was released as part of NW UI SP06. Please also check -
      -> SAP NetWeaver -> User Interface Add-On for SAP NetWeaver  ->
      document: UI Add-On for SAP NetWeaver Documentation SPS 04  ->
      chapter: “Using the Server Runtime for UI Services With NWBC 4.0 for Desktop”



  • Many thanks for sharing your experiences!

    One question regarding the ui5 based services:

    Is there a possibility to enhance or modificate the user interface of these services? Like the enhancement concept of web dynpro abap for example...


  • Dear Carrie, dear Alex,

    you posted in July that the following issues will come with SP06/07:

    -  system-wide personalisation options

    - disable some personalisation options

    Are there any News an that?

    thanks & regards


  • It's been some time since I posted anything here, but thought that this audience might be interested in knowing about the following notes that help with performance, from my colleagues in development:

    The following notes have been delivered that will significantly improve
    the performance of the lanes including the expanded lane for HR Renewal for ESS/MSS -

    2067906 - Performance improvements for Employee Self-Service Landing

    2067436 - My Time Sheet Lane - Corrections for performance issues ß This is only applicable if you have installed HR Renewal 2.0 FP1

    2072489 - Fixes for My Services Expanded Lane and

    2072986 - Fixes for My Team and My Team Services Expanded Lane

  • Hi,

    I am accessing HR Renewal(HRR) 1.0 SP4 Landing page from Portal 7.31. It takes 16-30 seconds to see the Home Page( HRR Landing Page) depends on the role. Most of the time taken to load the UI5 files into the browser(75% of total time).

    I want to preload HR Renewal 1.0 UI5 files, but don't see any Component.js in the files in the HRR 1.0. Can I use Component-preload.js even though there is no Component.js exists in the files.

    Any tips to preload HRR UI5 files?