www.nicx.co.uk

Page 1 of 29

ABAP Web Dynpro Forms

Background You can migrate from Adobe into Web Dynpro ABAP forms. You create the Web Dynpro ABAP form and all the existing configuration can be inherited. You might need to make some changes to workflow but other than this, the other configuration remains the same. Two sample forms, Change of Working Time which can be launched from ESS and Special Payment which can be launched from MSS, are delivered. Once Web Dynpro ABAP forms have been created, they can be used from ESS and MSS. The service layer opens up the whole framework. The Generate a PDF utility enables you to create an Adobe-based template. The data is transferred from the Web Dynpro ABAP form to the Adobe-based form and the form can be generated as a PDF and printed. Additional Information:

Release Information Note for HR Renewal: Refer to SAP Note 1701634.

SAP Library: Roadmap Form (Application Help from SAP Library): http://help.sap.com/erp_hcm_ias_2013_02/helpdata/en/8e/d3dc53b5ef424de10000000a174cb4/content.htm?current_toc=/en/b9/d3dc53b5ef424de10000000a174cb4/plain.htm&show_children=true

Developing an Infotype in Personnel Administration: http://help.sap.com/saphelp_erp60_sp/helpdata/en/4f/d52552575e11d189270000e8322f96/content.htm

Migrating an Infotype (Application Help from SAP Library): http://help.sap.com/saphelp_afs64/helpdata/en/43/a75f72bc4f1bbce10000000a1553f7/content.htm

Blogg: http://scn.sap.com/community/erp/hcm/blog/2013/05/07/hr-renewal-10-hcm-pf-a-basic-fpm-

form-in-fifteen-minutes

Technical Requirements:

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.

Business Functions (go to transaction code SFW5):

www.nicx.co.uk

Page 2 of 29

Activate Business Functions: HCM_ASR_CI_1 to 5. Read the documentation associated with each one.

Roadmap Form Activation: Business Function: HCM_PAO_CI_3

Assign Roles (Transaction code PFCG): SAP_ASR_HRADMIN_SR_HCM_CI_4. Parameter Configuration

Customizing settings for HR Administrative Services are entered as parameter and parameter values on table T5ASRSETTINGS.To configure these parameters and parameter IDs, in Customizing choose: Personnel Management → HR Administrative Services → Node text not found → Settings for HCM Processes and Forms Creating a Form

Transaction Code: HRASR_DT

When creating a form you have the following choices. You can use multiple types in one form as shown in the diagram above:

Form – You use this when you want to display data using a form.

List – You use this when you want to display fields of a single infotype record. E.g. Salary History (as

above)

List Complex – You use this when you want to display or perform operations on multiple records of a

single infotype.

Composite – You use this to group multiple UIBBs within a single UIBB.

Roadmap - You use this when you want to create a sequence of infotypes

Action - You use this when you want to run a Personnel Action e.g. Hiring

Procedure To Create a 'Form':

Tip: Reference the sample forms to provide you with examples.

Go to transaction code HRASR_DT

Process: HR_PA_XX_CHANGE_WORKINGTIME_1_WD

www.nicx.co.uk

Page 3 of 29

Copy the standard form: Menu Path: Process > Copy with Dependent Objects

Change: Process name, Process Description, Form Scenario 'FPM', new form scenario and click on [enter]:

Now select the form:

Select Fields: E.G. Time Status

www.nicx.co.uk

Page 4 of 29

[Save]:

Create the Form:

FPM Configuration = Form

Configuration: ZXX_XXXX & description of your choice

Click on the [Create] button.

The following screen will appear:

www.nicx.co.uk

Page 5 of 29

Click on the 'Add Group' button [+ Group]:

Enter a title e.g. 'Adrian's Change of Working Time'

Click on the attributes button at top of screen:

www.nicx.co.uk

Page 6 of 29

Click on [Element] > Add Element

Select the field 'Time Management Status':

The field appears on the form:

www.nicx.co.uk

Page 7 of 29

Click on the [Attributes] button to display more details of the field:

Adding Buttons to a Form

Click Repositories. The Repositories panel is displayed on the left.

In the Buttons section of Repositories panel, choose a button, and drag it onto the Preview panel.

Click Attributes. The Attributes panel is displayed below the Preview panel.

In the Attributes panel, set the attributes for the button, such as the position of the field on the form,

the label and display type.

Making Changes Using the Form UIBB Schema Panel

This panel outlines the structure of the form UIBB, and displays its UI elements. You can make the following

changes in the Form UIBB Schema panel:

Select a row containing an individual element of the UIBB and edit its attributes in the Attributes

panel.

www.nicx.co.uk

Page 8 of 29

Add additional, UIBB-specific elements to the UIBB by choosing buttons on the toolbar or by dragging

existing ones from the Repositories panel.

In the Attributes panel, set the attributes for the field, such as the position of the field on the form,

the label and display type.

Move individual elements within the schema by using the Up and Down buttons, or by dragging them

to a new location.

Add elements or buttons.

Select elements in the schema and edit their attributes in the Attributes panel.

Drag elements between the Repositories panel and the Schema panel.

www.nicx.co.uk

Page 9 of 29

Test the Form

Go to the 'Process' side of HRASR_DT

To make it easy to test, put 'NO_WORKFLOW' in the field below:

Menu Path: Process > Test

Select an example employee, role of the initiator and the 'Web Dynpro Screen' option:

The Form will appear as it would to the user:

www.nicx.co.uk

Page 10 of 29

Change the 'Time Management Status' and click on [Send] and check the change in PA30.

www.nicx.co.uk

Page 11 of 29

Other Types of Form

Let's have a look at the other types of forms:

List – You use this when you want to display or perform operations on repeat fields of a single

infotype record

List Complex – You use this when you want to display or perform operations on multiple records of a

single infotype.

Composite – You use this to group multiple UIBBs within a single UIBB.

Roadmap - You use this when you want to create a sequence of infotypes

Action - You use this when you want to run a Personnel Action e.g. Hiring

Below is an example form containing some of the

above:

List Forms

SAP Help: http://help.sap.com/erp_hcm_ias_2013_02/helpdata/en/62/82914917a54e7ba45bddce3732c01c/content.htm

Add the form type 'list' to your form and click on [create]:

www.nicx.co.uk

Page 12 of 29

Complex List

SAP HELP: http://help.sap.com/erp_hcm_ias_2013_02/helpdata/en/40/96f51796ca40479b7fee8dfcfafdb7/content.htm

Buttons: Add & Delete Rows

Test the form:

www.nicx.co.uk

Page 13 of 29

www.nicx.co.uk

Page 14 of 29

Composite Form

SAP Help: http://help.sap.com/erp_hcm_ias_2013_02/helpdata/en/ed/95f88fc8dd44569c607caa16355111/content.htm?frameset=/en/40/96f51796ca40479b7fee8dfcfafdb7/frameset.htm&current_toc=/en/b9/d3dc53b5ef424de10000000a174cb4/plain.htm&node_id=40

As above, add the form type 'composite' to your form and click on [create]

This type of form is similar to a screen in MSS. It can consist of Lists, input areas, searches and charts.

Test the Form e.g. 'Search Function' is below:

www.nicx.co.uk

Page 15 of 29

Roadmap Forms

Technical Rquirements

You will need to activate the Business Function HCM_PAO_CI_3

SAP Help for the Business Function: http://help.sap.com/erp_hcm_ias_2013_02/helpdata/EN/A9/364C50C3854443B27A2AF9605F2CF9/frameset.htm

There are two types of 'Roadmap Forms':

A sequence of infotypes

A sequence of infotypes in the form of a Personnel Action e.g. Hiring (as below):

SAP HELP on Roadmap Forms: o http://help.sap.com/erp_hcm_ias_2013_02/helpdata/en/ab/daa5519178245de10000000a4

4176d/content.htm?frameset=/en/ed/95f88fc8dd44569c607caa16355111/frameset.htm&current_toc=/en/b9/d3dc53b5ef424de10000000a174cb4/plain.htm&node_id=42&show_children=false

Creating a Roadmap Form

Go to transaction code HRASR_DT

In the object selection area, choose Form Scenario.

Enter the form scenario name.

In the object hierarchy area, choose the Roadmap node for the form scenario.

Configure the roadmap for the infotypes to be processed. The sequence number is generated

automatically. Perform the following:

o Enter the configuration ID of the infotype. The infotype version is filled out automatically.

o Enter a subtype if any.

o Enter a variable key if any.

www.nicx.co.uk

Page 16 of 29

o Select the operation to be performed from the dropdown list.

o Select the appropriate attribute for the infotype

The following fields are available to configure the sequence of infotypes for a roadmap form:

No. :This field displays the sequence number in which the single infotype configurations are offered to

the user in a roadmap process. Sequential numbers are issued automatically, according to the

sequence in which you enter the configuration IDs. You can change the order of the infotype

configurations with the Move Down and Move Up buttons as required.

Configuration ID: In this field, you enter a configuration ID that you have defined in Customizing for

Personnel & Organization under Infotypes Infotype UI Configurations for Master Data Application

Define Customer UI Configurations/Display Standard or Customer: Override UI Configurations .

Infotype Version: This field displays the version of an infotype configuration that is used during

process runtime. It is filled automatically, based on the infotype configuration ID that you enter for

the roadmap.

www.nicx.co.uk

Page 17 of 29

The infotype version that is defined on a form scenario level influences the configurations that you

can define in the roadmap. If you define on form scenario level that the form scenario is, for example,

only valid for the US, you will be able to select only US-specific or international configurations in the

roadmap of this form scenario. If the infotype version ID is not maintained on the form scenario level,

this field is hidden.

Subtype: With this field, you can restrict the infotype configuration for a subtype that you enter here.

Variable Key: In Customizing for Personnel & Organization, you can create different UI configurations

for an infotype configuration by using the variable key field. In this field, you can specify one of these

variable keys to tell the system to use the corresponding UI configurations at runtime.

Operation: In this field, you specify the following operations for the infotypes that you want to offer in

the roadmap:

o Create: When you specify this infotype operation, the system creates a new infotype record

valid as of the effective date.

o Change: When you specify this infotype operation, the system tries to retrieve an existing

infotype record for the effective date and offers it for editing.

o Copy: When you specify this infotype operation, the system tries to derive an existing

infotype record for the effective date. If such a record exists, the system copies it. If such a

record does not exist, the system automatically switches to the Create mode and creates a

new record.

o Delimit: If you specify this infotype operation, the infotype record valid at the effective date

is displayed. All fields will be in read-only mode, except for the ENDDA field of the validity

period, which is editable in order to delimit the infotype record. The ENDDA field is prefilled

with the value EFFECTIVE-DATE minus 1 (and can be changed to a different value).

Attribute: In this field, you specify whether an infotype is a required entry or optional at runtime in

the roadmap process.

o Mandatory: This attribute specifies that the infotype has to be maintained in the roadmap

process. It cannot be skipped, because otherwise the complete roadmap process cannot be

saved. It is possible to save a draft when mandatory infotypes have not been maintained yet.

o Standard: This attribute specifies that the infotype is optional and can be skipped.

Available Infotypes

You can view the standard infotype configurations for roadmap form scenarios in Customizing under

Personnel Management Personnel and Organization Infotypes Infotype UI Configurations for

Master Data Application Display Customer UI Configurations/Display Standard .

www.nicx.co.uk

Page 18 of 29

Please note that there is a BADI that can operate in a similar manner to the IGMOD feature.

Available Infotypes:

Action 'Roadmap':

www.nicx.co.uk

Page 19 of 29

This is an optional step when creating roadmap forms. You use this function to assign a personnel

action and an action reason to a roadmap process.

To assign personnel actions, you must define them in Customizing for Personnel & Organization under

Basic Settings Personnel Actions (or in Customizing for Personnel Administration under

Customizing Procedures Actions Set Up Personnel Actions ).

With the assignment of a roadmap form to a personnel action, you specify that the following

characteristics of the personnel action type are valid for the assigned roadmap process:

Activities

To assign an action to a form scenario, proceed as follows:

In the object selection area, choose Form Scenario.

Enter the form scenario name and choose Display.

In the object hierarchy area, choose the Action node for the form scenario.

To assign an action to a form scenario, select an action using the input help.

o This is an optional field. Other fields such as Action Reason and Action Reason Attribute are

disabled if you do not maintain the Action field.

Select an action reason if required.

Select the action reason attribute from the dropdown list.

Dynamic Actions

Blogg: http://scn.sap.com/community/erp/hcm/blog/2014/08/04/roadmap-forms-and-dynamic-processing-

rules--enhanced-data-quality-and-higher-system-automation-with-hr-renewal-20-feature-pack-1

Dynamic Actions can be configured are available in HR Renewal 2.0 Feature Pack 1. The example below uses

the example of an employee who has a number of children. When saving Infotype 0002, the 'Family/Related

Person' screen dynamically appears.

Enter a number in the 'number of children' field:

www.nicx.co.uk

Page 20 of 29

The 'Family/Related Person' screen dynamically appears

www.nicx.co.uk

Page 21 of 29

Configuration of Dynamic Actions

The screenshot below shows where rules are defined:

The screenshot below is called the "rules manager" where you can check, activate and deactivate the rules:

www.nicx.co.uk

Page 22 of 29

Printing Abap Web Dynpro Forms

Form Utilities enable users to print forms:

Prerequisites

You have made the following settings: You have activated the business Function HCM_ASR_CI_5.

You have maintained and activated the event linkage for DPF in transaction SWETYPV for processes

with the status Complete.

You have set entry GEN_PDF with the value 'X’ in the customizing activity for Settings Settings for

HCM Processes and Forms under HR Administrative Services

www.nicx.co.uk

Page 23 of 29

The system creates digital personnel files when the process status is set to Complete; it triggers an event which generates a PDF file with the data from the last step of the process.

A form template is required to generate a printable PDF format:

You can create a template in the Edit mode.

You have to define and manage the layout for the form template using the Form Builder application

(transaction SFP):

www.nicx.co.uk

Page 24 of 29

Adding a Form to the HR Administrator Launchpad

Transaction Code: LPD_CUST

Role: HRASR / Instance: PROCESSES

Note that the 'Target App. Parameters' are: PROCESS=Z_00_CHANGE_OF_WORKING_TIME&OTYPE=P

There are other ways of achieving this, for example, the form can be called through an iview.

Test the Form: Using PFCG to assign the role SAP_ASR_HRADMIN_SR_HCM_CI_4 to your user.

Log on to the HR Administrator Role using transaction code NWBC. Search for an employee. You will see the new process below:

www.nicx.co.uk

Page 25 of 29

The HR Administrator Application

Follow the instructions below to find the HR Administrator Application that is displayed above:

SE80 > Package > PAOC_ASR > Subpackages >PAOC_ASR_WD > Subpackages > PAOC_ASR_WD_PROC_EXECUTE_ALT > Webdynpro > FPM Applications > ASR_PROCESS_START_OVP > FPM Applications Configurations > ASR_PROCESS_START_OVP_CFG

Right-click > Test

www.nicx.co.uk

Page 26 of 29

Form Editor: PE51

SAP Help: http://help.sap.com/saphelp_dimp50/helpdata/EN/5e/af4aee901a11d2a6120000e83ddb11/content.htm?frameset=/EN/60/d8bd47576311d189270000e8322f96/frameset.htm&current_toc=/en/fa/38e0343734cf72e10000009b38f83b/plain.htm&node_id=3

Start by copying an example form:

Start with the Background:

www.nicx.co.uk

Page 27 of 29

Click on the [Next Page] button

Put in the single fields:

Click on the [Next Page] button:

Put in the windows:

Click on the [Next Page] button:

Define the line types:

www.nicx.co.uk

Page 28 of 29

Assign Wage Types and Line Types to Groups in the Window:

Try not to use individual wage types on the payslip, try using Evaluation Class 02 (e.g. **02):

www.nicx.co.uk

Page 29 of 29

Create 'Cumulation Wage Types':

Create text Modules:

Add the text modules on the single field screen: