Skip to Content

Hi Community,

On May, 14th the fourth feature pack (FP4) and few days ago, on August, 13th the fifth feature pack (FP5) for HR renewal 2.0 has been released.

But, what’s in for you here? Let me introduce to you the new functionalities we enabled for HR renewal 2.0.

With FP4 we concentrated on smaller, but important enhancements for many of our productive customers.

Extended Search Help for Positions and Organizational Units

With these enhancements the Search Helps for Position and Organizational unit input fields now offer a combination of text-based search, organizational hierarchy search and Favorite Organizational Units.

FP4_1_search_comb.jpg

Picture 1: Extended F4-Search Help with HR renewal 2.0 FP4

The extended search help is per default activated for the following instances when Business Function HCM_PAO_CI_8 (HCM, Personnel & Organization 08) is activated:

  • Roadmap Forms: initial step „General Process Data“, field „Position“
  • Various PA-Infotypes with fields OrgUnit or Position
  • OrgManagement: Managed OrgUnits (IT 1001/012)

Automatically active (after installing FP4) will be the usage of the new extended search help for the following standard FPM Forms:

  • Move Position (HRPAO_MOVE_POSITION) 4field “OrgUnit” within section “Destination Organizational Unit”
  • Move Org Unit (HRPAO_MOVE_ORGUNIT) 4field “OrgUnit” within section “Destination Organizational Unit”
  • Create Position (HRPAO_CREATE_POSITION) 4field “Managed Org. Unit”

The new extended Search help can also be used in customer specific FPM forms or customer specific infotypes!

With FP4 we additionally enabled the global info types 0017 “Travel Privileges”, 0128 “Notifications” and 0712 “Main Personnel Assignment” for the usage with HR renewal.

And – last but not least – we delivered the country versions with localized info type configurations for: Romania, Kazakhstan, Thailand and Ukraine.

HR Renewal 2.0 FP5 focuses on TCO enhancements to speed up the implementation of solutions for HR Professionals, as well as usability enhancements.

All enhancements were specific requests by productive customers and cover feedback from HR end users as well as system administrators. For FP5 you have to activate business function HCM_PAO_CI_9 (HCM, Personnel & Organization 09).

First enhancement of FP5 is that

General Process Data screen always editable in roadmap forms within the initial scenario step.

To give you some more insight in the reason of this enhancement I would like to describe one business case in more detail:

The General Process Data screen includes especially the “effective date” information. As end users confirmed in our discussions this date is often entered incorrectly or have to be changed during the process, so that it is necessary to correct the date after leaving the initial screen of a roadmap process.

But – so far – the initial screen could not be changed after the user has moved to the next step in the roadmap. This was a deliberate design decision since the parameters entered on General Process Data (e.g. organizational assignment information) often determine screen structures, default values, field attributes etc. of the subsequent infotype screens.

Productive users gave feedback that this handling is too rigid and not user friendly. Therefore we decided to change the behavior of the system here.

Second enhancement of FP5 is the

     Step-dependent infotype content / attributes in roadmap forms.

Also some more details on this enhancement:

Until FP5 it was not possible to provide different infotype content for different steps in roadmap forms. All users had the same set of infotypes available.
There was only the possibility to set the entire roadmap form to „read-only“, for approvers. But often it is not required to give all users all information, sometimes users will not even be allowed to see all information entered in a process.

Therefore now infotypes can be configured differently per scenario step within a roadmap form. These roadmap forms can also be used to kick-off change requests by a manager (who sees a limited set of infotypes) and have an HR expert complete further, more complex employee data.

FP5_1.jpg

Picture 2: Define step-dependent roadmap form with HR renewal 2.0 FP5

FP5_2.jpg
Picture 3: Define the attributes of the step-dependent infotypes – HR renewal 2.0 FP5

FP5_3.jpg

Picture 4: Result -step-dependent Roadmap form with HR renewal 2.0 FP5

The third enhancement of FP5 is

Generate HCM P&F Roadmap Forms based on Personnel Actions.

Because HR Renewal for HR Professionals is largely used by existing ERP HCM customers it was not a surprise, that these customer requested a tool to take over the configuration they already have in place to handle multi-infotype scenarios/employee contractual changes. For these scenarios like hiring, internal transfers, terminations etc. the customers are using „Personnel Actions“.

To lower TCO and reduce the manual effort to make these settings available as HCM Processes & Forms content – which is required for HR renewal – a new report helps customers to automate the creation of HCM P&F content for PA by generating processes and form scenarios of type „Roadmap Form“.

FP5_4.jpg

Picture 5: New IMG node for Generate Processes and Forms based on Personnel Actions with HR renewal 2.0 FP5

Excluded from this enhancement are settings for personnel actions via feature IGMOD – I know, I know!! 😐

Additionally only „Roadmap Forms“ are generated, so no other form type (like FPM forms, mass forms) is supported in this approach and it does not apply to PD infotypes.

The forth enhancement of FP5 I would like to point your attention to is

Context-dependent UI field control for infotypes.

Customers usually want to change the UI attributes of fields per infotype.

So far they could achieve this with different tools, but none of these tools seem to be as fast/efficient as classic options customers are used to from the SAPGUI world.

If customers e.g. change the setting field attributes for the user interfaces – which reside on the new infotype framework – via table T588MFPROPC there are some disadvantages:

These settings e.g. apply to all user interfaces that run on the decoupled infotype framework (so also to ESS), and only fields of P-structures are included. Additionally there is not F4 help available for input fields etc..

If customers decided to create an own FPM configuration they faced other disadvantages:

That they had to have someone with know-how of FPM, they had more effort to copy standard configuration, adapt it and then add the own configuration ID to the configuration of the master data application.

The new IMG activity allows customers to define field attributes per application context, e.g. specifically for HR Professional / Master Data Application + roadmap forms as well as for fields of UI structures.
All input fields are supported by F4 value helps to make only correct entries.

FP5_5.jpg

Picture 6: IMG node to define context-specific UI field properties with HR renwal 2.0 FP5

And the fifth enhancement of FP5 is

Navigation from infotype to related configuration settings.

There are certain customizing activities that can be called from the infotype UIs, e.g. current settings. Therefore, the user has to be able to navigate to these IMG activities quickly via ‘Further option’ link in the master data application. In addition, some values have to be defaulted when navigating to the IMG activities. Such kind of navigations can now be realized by configuration in LPD_CUST.

FP5_7combined.jpg

Picture 7: Configuration of quick navigation from infotype to configuration settings with HR renewal 2.0 FP5

For more information about the enhancements in HR renewal FP4 and FP5, or our deliveries with previous feature packs please visit our resources space (implementation information) on service market place.

Saying this I hope I could give you a good overview of our recent investments and – as always – we are very interested in your feedback!

Best regards,

Sylvia Strangfeld

sylvia.strangfeld@sap.com 

To report this post you need to login first.

11 Comments

You must be Logged on to comment or reply to a post.

  1. Imran Sajid

    Hi Sylvia,

    Thanks for sharing! I saw the documentation and read through the release notes for Feature Pack 4 and 5 when I saw them on the SAP site, but it is nice and more helpful to have screenshots and explanations!

    The “Generate HCM P&F Roadmap Forms based on Personnel Actions” functionality looks especially cool!

    Regards,

    Imran

    (0) 
  2. Christopher Solomon

    Interesting changes.Again…more and more focus/effort put into “roadmap” forms. Is this just more inline with a push to finally  put PA20/30/40 “out to pasture”? haha

    I am disappointed that I still …over all the many updates…have not seen much in the way of better optimization to the underlying HCM P&F engine/framework itself. There is still a lot of room for improvement! (ex. lots of duplicated round trips that are unnecessary). And still no word/guidance/direction on a SAPUI5 option…not even a “hint” of it coming….while several customers are developing their own from scratch and third parties are making “products” for it (just like companies that offered a ABAP Webdynpro option before FPM was available and only Adobe IF was “out of the box” from SAP). I appreciate the work on roadmap forms and dynamic processing rules, but just wish more was being done (or if it is, communicate it!) with the “other” parts of HCM P&F.

    (0) 
    1. Siddharth Rajora

      First of all,

      Sylvia thanks for sharing this information in such a lucid manner.

      I echo what Christopher is saying, We need a SAPUI5 option to make HCM P and F more appealing and easy to use and framework yes, we did have incremental changes and can be made better.

      When you say duplicated round trips, i think it was rectified? you can raise a message so our team can check if its causing performance issues?

      (0) 
      1. Christopher Solomon

        Oh Sid….”weird” looping is one of many issues I have with the “engine” haha I think the whole thing could be refactored. At least we are past the “good old days” when if you were on a scenario step down in workflow several steps into a process, it would loop back and “recreate” the entire trail up till your point. hahahahaha

        (0) 
    1. Sylvia Strangfeld Post author

      Hi Marc,

      thanks 🙂

      Actually jobs was on our roadmap, but there are no detailed customer requests regarding the integration of object C into the HR renewal UI. So there are no plans to work on this at the moment.

      Hope this helps,

      BR, Sylvia

      (0) 
      1. Christopher Solomon

        What do you mean by “no detailed customer requests”? I see org/job/position changed/used in HCM P&F processes all the time for employee processes. In fact, I see all manner of PD-PA integration issues because of customers doing related changes and am hoping the framework handles this better/easier in the future.

        (0) 
          1. Noriko Szilagy

            Dear Sylvia,

            My company is one of the customers who wish to have position creation (PD) in employee processes (PA).  So you can count us in your list.  😛   My users want to see everything in one screen and want the system to create a position in the background for hire forms.  We were told by SAP Support that because PA/PD use different buffers, forms would not work if they are mixed in one process.

            Ideally, I would like to see a complete integration from SuccessFactors (or any cloud application) to R/3 using HCM P&F like the way SAP did using e-Recruiting.  I think that SAP customers want a seamless integration from end to end with beautiful UI. HCM P&F offers a powerful framework but I feel SAP offers solutions piece by piece.  I could be wrong but that is how I feel. 😕

            Not to mention, we want a mobile version of HCM P&F.  We want to see SAPUI5 on the horizon for HCM P&F as well.  It is coming soon, I hope?

            Best regards,

            Noriko

            (0) 

Leave a Reply