Skip to Content
Author's profile photo Sylvia Strangfeld

Whatโ€™s new in HR renewal 2.0 feature pack 3 for professional users?

Hi Community,

On February, 19th the third feature pack (FP3) for HR renewal 2.0 has been released.

But, what’s in for you here?

In a summery you will get:

  • a Converter for Dynamic Actions into DPRs
  • an Employee Recognition dialog
  • Possibility for an External Personnel Number Assignment
  • an Employee History Tab in Master Data Application
  • Read-only-Functionality of roadmap form
  • Possibility to set a Default Date Range
  • New Payroll Control Center
  • Additional Country Enablement
  • Enablement of additional Global Info Types

But, let me introduce to you the new functionalities we enabled for HR renewal 2.0 in more detail.

As you will probably recall (and if not, here is my blog Roadmap Forms and Dynamic Processing Rules – enhanced data quality and higher system automation with HR renewal 2.0 Feature Pack 1) we provided the Dynamic processing rules (DPRs) with HR renewal 2.0 FP1.

These DPRs enhance the concept of roadmap form processes to configure info type dependencies within these processes.

This is a functionality lots of customers asked for and we got really good feedback after it was released.

But – and there is always a ‘but’, right? ๐Ÿ˜‰ – As soon as customers recognized that there is a new rule framework to configure the DPRs in HR renewal these customers wonder, how to bring the former dynamic actions to HR Renewal. Of course they do not want to create all rules twice. 

So we used the last development cycle to build a Converter for Dynamic Actions into DPRs.

The solution we deliver with FP3 supports the conversion of the configurable content of the dynamic actions into Dynamic Processing Rules. Exceptions are the customer-own function calls and ABAP-based parts. These must be converted manually by creating a matching class for the new framework.

When launching the conversion tool you are able to select existing dynamic actions you would like to covert. After starting a preview of the conversion into dynamic processing rules, you may adjust certain values manually and then finally confirm the conversion.


Picture 1: HR renewal 2.0 FP3 – Report to convert Dynamic Actions into DPRs

The dynamic actions will then appear in the customizing tables of dynamic processing rules. Here you can do further adjustments, run consistency checks and complete your configurations. A dedicated conversion status shows which dynamic processing rules are actually converted dynamic actions.


Picture 2: HR renewal 2.0 FP3 HR renewal 2.0 FP3 – Rule Manager with converted Dynamic Actions

The Employee Recognition dialog is another important investment for FP3 which lots of customers asked for especially in the context of Concurrent Employment and Management of Global Employment, but also for improving data quality.

The users shall be supported in determining whether an employee is

  • a new hire, i.e. employee receives a new personnel number
  • a rehire, i.e. currently in inactive employment relationship, whose personnel number remains and whose employment status only gets re-activated
  • an additional contract within the same legal entity as part of the Concurrent Employment concept
  • an additional global assignment in another legal entity as part of the Management of Global Employees concept

With the Employee Recognition dialog the system provides a list of people that matches the criteria entered for hiring purposes beforehand. The HR Professional user is now supported to decide if there is really a new hire necessary or whether the person already exists.

Example 1: If there are no employees that match the criteria like
employee name or birth date entered in the dialog previously, a new hire needs
to be performed.

Example 2: An employee matches the criteria entered in the dialog
previously, but this employee has an inactive employment status. This employee should
being rehired.

These examples show use cases for customers not using Concurrent Employment (CE) or Global Employment Management (GE) but with a high need to improve data quality.

Example 3 for customers using CE or GE: An employee matches the criteria entered in the dialog previously and this employee has an active employment status. HR Professional users will then additionally be supported with the decision, if an already existing person should get a new contract with the same legal entity (CE) or with another legal entity (GE.


Picture 3: HR renewal 2.0 FP3 HR renewal 2.0 FP3 – Screenshot of Employee Recognition dialog

Summarized this means, customers will benefit from the Employee Recognition dialog no matter whether they are using CE/GE or not.

External Personnel Number Assignment is another FP3 feature, we enabled for Roadmap Forms, especially for hiring scenarios.

If customers decide to use internal and external number assignment (or external number assignment only) a section for maintaining the Personnel Number is displayed in the Roadmap Forms. This applies for all Roadmap Forms where a new personnel number assignment is to be created.

When users are asked to enter an external personnel number (this might depend on the organizational data assignment of the person to be hired) the system validates this number against the range for external number assignment defined in Customizing.

When internal numbers are being used (depending on the organizational data assignment of the person to be hired) the Personnel Number field is read only and contains the information that the system generates this number automatically.


Picture 4: HR renewal 2.0 FP3 HR renewal 2.0 FP3 –External number assignment in Roadmap Form

Let’s now talk about Employee History in Master Data Application.

A lot of changes to employee data lead to an entry created in info type 0000 (Actions), e.g. Change in Pay, Organizational Reassignment, Hiring, and so on.

If there is a need to create an additional action for the same employee on the same day, these data are recorded in info type 0302 (Additional Actions).

With FP3 the HR Professional users can now smoothly navigate to the Employee Profile for checking whether the corresponding actions have been created based on processes being performed beforehand.

Therefore we created an “Employee History” tab in the Master Data Application providing an overview of the info type 0000 and 0302 records created so far for the corresponding employee. The information is a combined display of both info types.


Picture 5: HR renewal 2.0 FP3 HR renewal 2.0 FP3 –Employee History tab in Employee Profile page of Master data application

And last but not least two smaller but very important enhancements:

Read only of roadmap form in multiple step processes is necessary for e.g. approval processes, where the manager only gets a read only version to accept or reject the whole process.

Default Date Range is meant to improve the usability in the Search Dialogues of the Master Data Application and Landing Page.

With defining a default date range it is now possible for a user to search for objects within a specific time period (e.g. “today plus 3 month” – If the user is looking for employees hired in future e.g. effective date within the next 3 months)

In this context we also improved the Date Handling in the Quick View of the Search Lane. This feature enables the user to launch the quick view also for objects which ended in the past or will start in the future. Until now it was only possible to show the quick view of an object  valid today (System Date) .


Picture 6: HR renewal 2.0 FP3 HR renewal 2.0 FP3 –Default date range in search dialogue of master data application

Additionally to the features mentioned before FP3 also contains enhancements for the Payroll Control Center. To get a great overview of these
innovations, I would absolutely recommend the blog of my colleague Frans Smolders “
SAP Payroll control center add-on: the payroll evolution
continues in Feature Pack 3

Also included in FP3 are the country versions for: Japan, Italy, Belgium, Portugal, Norway, Denmark, Qatar, Kuwait and NPO.

And, we enabled the global info types 0030 “Powers of Attorney”, 0034 “Corporate Function” and 0035 “Company Instructions” for the usage with HR renewal.

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!

If you have any questions please feel free to reach out to me.

Best regards,

Sylvia Strangfeld 

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Siddharth Rajora
      Siddharth Rajora

      Excellent Preview of the new functionality.  We need to add Employee Service Letters also in HR renewal, as being asked quiet often ie where employees can generate Salary or other Company attested letters.

      Author's profile photo Former Member
      Former Member

      Thanks for the great preview Sylvia. Looks like the system is maturing quite a bit.

      Author's profile photo Christopher Solomon
      Christopher Solomon

      Great summary, Sylva! Thanks for the info!

      Quick question....can/is the Employee Recognition dialog tied into HCM Processes & Forms (can we use it in our own processes to trigger a new hire/rehire correctly) ? I am sure at the end of the day, we could write our own custom WDA app to launch it, then make the decision and trigger/start our own process accordingly (using the new "process execute" RFC) but it would be nice to have something "standard" of course.

      Thanks again for the update! Oddly enough, I had just updated my old blog ( HCM Processes & Forms: Clearing the confusion of Feature Packs, what's new and when! ) to include the newer FP information. haha ๐Ÿ˜‰

      Author's profile photo Sylvia Strangfeld
      Sylvia Strangfeld
      Blog Post Author

      Hi all,

      thanks for the positive feedback. It's very appreciated ๐Ÿ˜‰

      Regarding Christophers question:

      The EE recognition dialog can be launched by the HCM P&F form types FPM, Adobe and roadmap forms or "stand alone". Means, it can be triggered by a process or be the trigger of a process...

      But: The data entered into the EE recognition dialog are being transfered ONLY into the corresponding fields of the form type roadmap form. The transfer is out of the box not supported for the other two form types.

      Technically this should not be such a big deal. We use the class CL_HRASR00_SET_HIRE_DATA to temporary store the data of the EE recognition dialog and then get the data to fill in the corresponding fields o the roadmap form. Acutally I do not see a reason why this should not work at least for FPM forms.

      Hope this helps...

      Cheers, Sylvia

      Author's profile photo Former Member
      Former Member

      Thanks A lot for this information, I try to use the recognition but when I used my process with ORG_REASSIGNMENT(from feature actce) SAP doesn't create a new contract but create new records. And when I use ADDITIONAL_ASSIGNMENT a dump  occurs ๐Ÿ™ .

      Can you help me please?

      Thanks a lot.

      Author's profile photo Former Member
      Former Member

      I have fingered out.


      Author's profile photo Former Member
      Former Member

      Can you please tell us how you resolved your issue?

      It would be appreciated ๐Ÿ˜‰

      Author's profile photo Guillaume GARCIA
      Guillaume GARCIA


      Just to make sure I haven't mistundertood something regarding DPR.

      1. Dynamic actions require to be converted into DPR if you want them to kick in your HCM Processes & Forms, right?
      2. Are they then triggerred only in the context of HCM Processes & Forms or also in SAP Gui?

      Thanks in advance.

      Best regards,


      Author's profile photo Christopher Solomon
      Christopher Solomon

      (1) yes. If you want to use them in HCM P&F, yes, they must be converted. And then, they are ONLY usable in "roadmap" forms at the moment.

      (2) When you say "also in the SAP GUI"? Where/how do you mean? The usage/implementation of DPRs is pretty limited at the moment.

      Author's profile photo Sylvia Strangfeld
      Sylvia Strangfeld
      Blog Post Author

      Hi Guillaume,

      I guess your question is more refering of using HR renewal and GUI in parallel and if DPRs you defined in the new framework also act as Dynamic actions in the GUI world, right?

      If this is your question, than the answer would be - no.

      You have to maintain these actions in customizing table T588Z too to make them work in GUI processes of e.g. PA40.

      To avoid double work and keep both functionalities synchronous it would be recommended to maintain the rules in the "old" world and use the converter to bring them into the new world.

      Unfortunately than the new and easy maintenance of the rules via the new framework is lost... ๐Ÿ™

      Cheers, Sylvia

      Author's profile photo Guillaume GARCIA
      Guillaume GARCIA

      Thanks to both of you, it is crystal clear now!

      Author's profile photo Former Member
      Former Member

      Hi Sylvia,

      Can the Employee Recognition dialog only be used by HR Professional users, or is there a way for HR Administrators to use it through the roadmap forms? We are not using the HR Professional roles, just the HR Administrator role in NWBC.

      We have MGE activated and we are implementing Roadmap forms for the personnel actions, and the Employee Recognition is required.

      We are actually in FP5.

      Thanks in advance.