Configuring Floor Plan Manager-Based Forms in the Workforce Viewer of HR Renewal 1.0 Feature Pack 4

  • by Rajkumar Shanmuganathan, SAP Lead Technical Consultant
  • April 30, 2015
Gain a quick and concise overview of the Workforce Viewer solution of HR Renewal 1.0 Feature Pack 4 (FP4), and how it relates to SAP HCM Processes and Forms.
Learning Objectives

Reading this article you will learn about:

  • Floorplan Manager (FPM)-based SAP HCM Processes and Forms
  • The Workforce Viewer in HR Renewal 1.0 Feature Pack 4 (FP4)
  • SAP-delivered HCM Processes and Forms
  • How to configure FPM-based SAP HCM Processes and Forms
Key Concept

Floorplan Manager (FPM) is a highly configurable user interface (UI) framework for easy and efficient application development and adaptations based on Web Dynpro ABAP. FPM allows you to easily integrate Web Dynpro ABAP UIs. The SAP HCM Processes and Forms framework adopts FPM to create the Web Dynpro ABAP UI-based forms, which are called FPM forms. FPM forms are released as a part of HR Renewal 1.0. The Workforce Viewer is a graphical, personalized interface for different SAP organizational structures that was developed using SAPUI5 technology.

Before the HR Renewal 1.0 Feature Pack 4 (FP4) release, SAP HCM Processes and Forms only used the Adobe interactive forms solution, integrated with Web Dynpro ABAP, for its user interface (UI). Floor Plan Manager (FPM)-based forms were added starting with the release of HR Renewal 1.0. SAP HCM forms can be initiated across the HR Renewal 1.0 (all releases) landing pages. (To learn more about HR Renewal landing pages and the users who can access them, read my other HR Expert article, “Learn How to Configure the Quick View Panel in the Search Lane and Workforce Viewer of HR Renewal 1.0 Feature Pack 4.”)

In standard HR Renewal 1.0 FP4, most of the HCM forms are configured with Adobe-based forms. I show how you can replace the Adobe-based forms with FPM-based forms through configuration. (The other types of forms—apart from Adobe or FPM—are Road Map forms and Mass forms; they both use Web Dynpro ABAP for their user interface. As these forms are already delivered with the Web Dynpro ABAP UI, there is no need for any conversion.)

We as an organization did some analysis on both SAP Interactive Forms software by Adobe and FPM forms before we implemented the SAP HCM Processes and Forms solution. Reading this article will help you understand the advantages of developing FPM-based forms over Adobe interactive forms. My company decided to go with FPM-based forms because of the following advantages:

  • There is no additional licensing required to develop the FPM-based forms.
  • Developing FPM-based forms does not require any additional technical skills. An existing SAP development team with Web Dynpro ABAP skills is sufficient for building FPM-based forms. Adobe interactive forms, on the other hand, require a high degree of client-side control via scripting.
  • FPM-based forms support multilingual forms. The advantage of using the multilingual forms is that the form can be displayed in multiple languages based on the language selected when the user logs on. The language text is maintained in SAP transaction code SOTR_EDIT.

Rajkumar Shanmuganathan

Rajkumar Shanmuganathan is a freelance SAP Lead Technical Consultant. He has worked in SAP for over 10 years, seven of which he focused on SAP HCM as a techno-functional consultant on several international projects. He is SAP-certified in ABAP, CRM, and SAP HANA, and currently is working projects that involve new SAP technologies, such as SAPUI5, SAP Gateway, and SAP Fiori. Rajkumar regularly shares his knowledge in the SAP SDN/SCN forum. You can view his blog posts by following this link: http://scn.sap.com/people/rajkumar.shanmuganathan3/content.

See more by this author


Comments

No comments have been submitted on this article. 


Please log in to post a comment.

To learn more about subscription access to premium content, click here.