Skip to Content
Author's profile photo Sylvia Strangfeld

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

Do you know that changing employee and organizational master data has never been easier than with the new Master Data Application for HR Professionals in HR Renewal? And do you know the newest feature of HR renewal for HR professionals? In this post my colleague Parvathy Sankar and I will explain that roadmap forms and dynamic processing rules enhance data quality and increase system automation to make the life of the user easier.

With HR renewal 1.0 initial shipment in 2012, SAP enhanced the usage of Processes & Forms (P&F) for an easy and intuitive maintenance of master data within the area of Personnel Administration and Organizational Management.

With doing this, we could use all the nice features of P&F like “Save as draft”, easy workflow enablement, no translation effort, flexible number of steps and users etc.,  to decrease the time a user needs to update master data and increase data consistency.

After the first shipment we got a lot of feedback from our customers and partners, that they like the P&F approach, but that they are missing another important functionality, which is often used in the backend to build comprehensive processes – personnel measures, very well known as transaction PA40.

After an intensive time reviewing the customer needs, we introduced the roadmap forms with Feature Pack 4 of HR Renewal .

Roadmap forms are an additional form type of P&F to easily build larger processes. The design is similar as it works in GUI transaction. The customer defines a sequence of info types the user has to proceed to finish a process.

roadmap form.JPG

Screen shot: pre-configured roadmap form for Hire in US

Benefits of the new roadmap forms are:

  • easier configuration with using HCM P&F design time
  • reuse of existing info type configuration
  • web-based info type scenarios…

And of course all the nice features of P&F are also used to make the life of the user easier working with roadmap forms


Screen shot: configuration of roadmap form “Hire an Employee (US)” in HCM P&F design time (TA HRASR_DT)

And the story continues:

With our latest feature pack, FP1 of HR renewal 2.0 the concept of roadmap forms was enhanced to also bring dynamic dependencies to the processes. In the GUI world it is known as “Dynamic Actions”. With HR renewal 2.0 FP1 we deliver Dynamic Processing Rules to configure info type dependencies within processes.

Many country regulations as well as corporate audit rules mandate that related data must be adapted depending on a certain field value users have changed in employee master data. For enhanced data quality and higher system automation, the solutions for HR Professionals for employee master data management can now be tied to a rich, configurable rules framework.

For example: During hiring process, the HR enters the number of children as one of the personal information.


Screen shot: roadmap form hire – increase number of children

When the next button is selected, the sequence of the steps to be processed would be altered with the same number of “Family members/dependents” info types as the number of children.


Screen shot: dynamically enhanced roadmap form hire – IT 0021 added twice

Thus dynamic processing rules enables you to provide rules to specify the type of information to be entered and the steps of info types to be followed based on the information entered.

The solution allows you to:

  • activate / deactivate your choice from SAP’s best-practice rules
  • create own rules, applying them either internationally, locally, for a number of countries
  • easily define country-specific overwriting of international rules, if other conditions apply in certain countries
  • build rules with conditions and target operations based on simple settings, with explicit field help to show possible options per info type/subtype
  • add in code-based logic if required as part of configuration (no modification)
  • run the Check Tool to find inconsistencies within your rule concept

Last but not least some words to clarify the delivery of roadmap forms and dynamic processing rules:


  • FPM forms were delivered with HR renewal 1.0 FP1 in September 2012.
  • Roadmap forms have been available since HR renewal 1.0 FP4 – RTC was July, 2013.
  • The Dynamic processing rules were delivered with HR renewal 2.0 FP1 in July 2014.

HR renewal 2.0 is based on EhP7. HR renewal 1.0 is based on EhP6.  A down port of the HR renewal 2.0 functionality to EhP6 is planned for November 2014 so all customers who have implemented HR renewal 1.0 based on EhP6 can also get the great new functionality of Dynamic Processing Rules in the near future.

As you can see – it’s easy to make your life easy 😉

Looking forward to your feedback.  And if you have any questions feel free to contact us.

Parvathy Sankar     and      Sylvia Strangfeld;

Assigned Tags

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

      Good job SAP and its nice to know that this functionality would be downported.



      Author's profile photo Former Member
      Former Member

      Pretty interesting feature ! I was just hoping to see a screenshot of "Dynamic Processing Rule Editor" 🙂 Either ways, I like to the list of points that can achieved through this new functionality. Just want to check if we can pass data across screens/infotypes i.e. if I say "Number of Children" as "2", can we inherit the same last name of employee to the two child screens(IT0021) ?

      Thanks for a wonderful blog ! Looks forward to implement this new functionality post Nov'14 🙂

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

      Hi Raja,

      Thanks for your comments...

      O.k. to give all here also an impression how the framework looks like to define the rules, I insert two pictures here.

      First one is a screenshot how to define the rules:


      Second one is the so called "rules manager" to check, activate and deactivate the rules:


      To your second question - Actually that is a functionality which is available in the GUI as well as in the DPRs. It is also possible to enhance rules with own coding, if a special behavior is required.

      Looking forward to hear from your implementation experiences in Dezember '14 😉

      Author's profile photo Former Member
      Former Member

      Thanks Sylvia,

      The screens look promising ! The backend screenshot somehow reminds me of "Dynamic Actions" 🙂 !

      Sure, you would definitely see a nice blog from me after our implementation.


      Raja Sekhar

      Author's profile photo Marco Jansen
      Marco Jansen

      Dear Sylvia,

      thanks for this great blog 🙂

      I hope you will arrange an deep dice expert session on this topic.

      Thanks & best regards


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

      Hi Marco,

      thanks for your reply.

      Yes, we will have a kind of deep dive. Due to the holliday season I guess we will fix a date End of September.

      Will announce the session here, but also of course via Mail and partner Edge...

      I'll keep you informed... 😉

      BR, Sylvia

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

      For all who are interested in the announced Downport to HR renewal 1.0:

      The downport is planned for HR renewal 1.0 SP31. RTC for this SP will be November, 13th, 2014.

      So only 22 days to go... 😉

      Author's profile photo Former Member
      Former Member

      Dear Sylvia

      what the Role i need to add it to PFCG to start Roadmap custom processes from business client (NWBC)



      Author's profile photo Former Member
      Former Member

      Dear Sylvia

      I cant start any roadmap processes(hrasr_dt) from landing page for inactive employee , i got the message employee does not exist ,

      even its work fine from 'hrasr_test_process' for the same emplyee

      please advise me how can i let any roadmap process start for inactive employee in landing page