Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
cancel
Showing results for 
Search instead for 
Did you mean: 
S_Strangfeld
Product and Topic Expert
Product and Topic Expert

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...) 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? :wink: - 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

sylvia.strangfeld@sap.com 

12 Comments