Vous êtes sur la page 1sur 37

EHP6 for SAP ERP

6.0
January 2013
English

HCM Base Services for


Processes and Forms
using Web Dynpro ABAP
(F17)
Building Block Configuration Guide

SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

Copyright
© 2013 SAP AG or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the
express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational
purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for
errors or omissions with respect to the materials. The only warranties for SAP Group products and
services are those that are set forth in the express warranty statements accompanying such products
and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and other countries. Please see
http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark
information and notices.

© SAP AG Page 2 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

Icons

Icon Meaning
Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description


Example text Words or characters that appear on the screen. These include field
names, screen titles, buttons as well as menu names, paths and
options.
Cross-references to other documentation.
Example text Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT Names of elements in the system. These include report names,
program names, transaction codes, table names, and individual key
words of a programming language, when surrounded by body text, for
example, SELECT and INCLUDE.
Example text Screen output. This includes file and directory names and their paths,
messages, source code, names of variables and parameters as well as
names of installation, upgrade and database tools.
EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the
ENTER key.

Example text Exact user entry. These are words or characters that you enter in the
system exactly as they appear in the documentation.
<Example text> Variable user entry. Pointed brackets indicate that you replace these
words and characters with appropriate entries.

© SAP AG Page 3 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

Content
1 Purpose..................................................................................................... 5
2 Preparation................................................................................................ 5
2.1 Prerequisites ............................................................................................. 5
2.2 Copying of SAP Standard Objects ............................................................. 5
3 Configuration ............................................................................................. 6
3.1 HR Administrative Services ....................................................................... 6
3.1.1 Activate Business Functions ............................................................................. 6
3.1.2 Configuration of HCM Processes and Forms – Sample Processes.................... 7
3.1.3 Configuration of HCM Processes and Forms – Process Configuration, Workflow
Settings ..................................................................................................... 9
3.1.4 Configuration of HCM Processes and Forms – Process Configuration, Process
Objects.................................................................................................... 12
3.1.5 Configuration of Forms/Processes .................................................................. 14
3.1.6 Process Configuration, Set Up Processes....................................................... 16
3.1.7 Workflow: Task Type Maintenance ................................................................. 19
3.1.8 Create Role for HR Administrator and Assign to Users ................................... 20
3.1.9 Object-Based Navigation ................................................................................ 24
3.2 Assignment of PA Processes to the ESS Scenario .................................. 24
3.2.1 Start Process Configuration for Employee....................................................... 24
3.2.2 POWL Inbox Customizing for Administrator .................................................... 25
3.3 Assignment of PA Processes to the MSS Scenario .................................. 31
3.3.1 Start Process Configuration for Manager ........................................................ 31
3.3.2 POWL Inbox Customizing for Manager ........................................................... 32

© SAP AG Page 4 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

HCM Base Services for Processes and Forms


using Web Dynpro ABAP: Configuration Guide

1 Purpose
The purpose of this document is to describe the general configuration steps required to
manually set up the configuration within the system landscape that has already been installed
using the corresponding installation or configuration guides for installation.
If you prefer to install the solution automatically using BC Sets and other tools, refer to the
Quick Guide for your SAP rapid-deployment solution that is attached to the SAP Note.
This document supplements the existing Customizing documentation in the Implementation
Guide (IMG) and provides additional information where required.

The process start for the role HR Administrator is planned with the Q4 delivery of
SAP HR renewal 1.0. Please check the current road map of SAP HR renewal 1.0.
The configuration guide HCM Base Services for Processes and Forms using Web Dynpro
ABAP - Training Material / Cookbook (F18) provides a step-by-step description to create your
own customer specific processes based on the sample process Internal transfer.
The implementation is optional and requires the configuration of HCM Base Services for
Processes and Forms using Web Dynpro ABAP described in this document.

2 Preparation
2.1 Prerequisites
Before you start installing this scenario, you must install the prerequisite building blocks. For
more information, see the Building Block Prerequisites Matrix for the SAP Personnel
Administration and Organization Management rapid-deployment solution. You will find this
document in the content library attached to the Step-by-Step Guide.
In addition, the client’s Basis team must have set up the workflow runtime environment and
the Adobe document server.

2.2 Copying of SAP Standard Objects


Wherever possible, objects that belong to the standard SAP delivery have been copied for
this rapid-deployment solution. We do not recommend changing the standard SAP objects.
Copying the standard objects is a major implementation accelerator. You can immediately
make adjustments to the solution objects by copying objects. Changes to the standard SAP
objects will not affect the solution objects; changes to the copied objects will not be affected
this way. Changes to standard SAP objects affect objects that were copied as delta links.
These objects inherit changes from their parent objects. Detailed descriptions of the objects
and the copied objects can be found in the Configuration section.

© SAP AG Page 5 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

3 Configuration
The following section describes the complete settings for this building block. These settings
can be divided into two main groups:
Prerequisite settings that have to be checked and which were delivered by SAP (as
part of the standard delivery).
o The term Check refers to these prerequisite settings.
Additional settings that need to be made covered either by automation or manual
configuration (in the customer namespace).
o The term Create refers to these additional settings in the text.

For details on the roles configured to support this building block, see the
Consultant and End User Security Guide.

3.1 HR Administrative Services


3.1.1 Activate Business Functions
Use
As a prerequisite for configuring the application component HR Administrative Services,
including HCM Processes and Forms, it is important to check that the relevant business
functions have been activated.

Procedure
1. Access the transaction using one of the following navigation options:
Transaction Code SFW5
IMG Path SAP Customizing Implementation Guide Activate Business
Functions

On executing this IMG step, a secrity information system message is displayed


as follows: Caution! Only reversible business functions can be
deactivated. For this reason, activate only required
business functions. In case of doubt, read the corresponding
documentation. Select the Continue button to proceed with caution.
2. On the <System ID, e.g. RDF> - Switch Framework: Change Business Function Status
screen, choose ENTERPRISE_BUSINESS_FUNCTIONS and expand the tree for this
dialog structure.
3. Check the status of the following business functions is ‘Active’:
HCM_ASR_CI_1 (HCM, Administrative Services 01),
HCM_ASR_CI_2 (HCM, Administrative Services 02),
HCM_ASR_CI_3 (HCM, Administrative Services 03),
HCM_ASR_CI_4 (HCM, Administrative Services 04)
HCM_NWBC_ROLES (HCM, Roles for SAP NetWeaver Business Client).

If there are any issues, contact the basis team to ensure that the appropriate
functions are activated appropriately.

© SAP AG Page 6 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

For further details on the technical prerequisites for HCM Processes and Forms,
refer to the Quick Guide for this rapid-deployment solution, as stated earlier.

3.1.2 Configuration of HCM Processes and Forms – Sample


Processes
In HCM Processes and Forms, sample processes are delivered that support you in
configuring your own business processes and form scenarios. These sample processes are
intended for demonstration purposes and can be used in a test system only. The following
section describes the steps required to deploy the sample processes in the current
development/test client(s). The sample processes must not be used in a production system,
but may be copied and adapted as required.
Configuration steps and activities required to implement the sample processes are described
in the steps below. Additional steps may be required in order to copy, configure, and deploy
customer-specific forms. These steps are partially covered in the cookbook where it is
described how to build a sample process for the internal transfer to a new position.

3.1.2.1 Perform Activate Dependent BC Sets


Use
To use the sample processes provided with HCM Processes and Forms using Web Dynpro
ABAP, it is required to activate the dependent BC sets of switch HRASR_SFWS_UI_ENH_05
in the relevant development client. This activity is a manual step, even if automated content
activation has been run.

Note that entries in the target client are overwritten or deleted according to key
entries in the BC Sets activated as part of this step.

Authorizations required to perform this step are described in the Consultant and
End User Security Guide.

Procedure
1. Log onto the development system in which the dependent BC sets should be activated.
2. Access the transaction using one of the following navigation options:
Transaction Code SFW1
IMG Menu SAP Menu Tools ABAP Workbench Development
Switch Framework Switch
3. On the Switch: Init.Screen screen, enter the switch HRASR_SFWS_UI_ENH_05.
4. Select Display button.
5. To start the activation of the dependent BC Sets select Activate Dependent BC Sets
(Shift+F1) in the menu.
6. In the displayed Activation Options screen, select.
7. Continue with Enter.
8. In the following screen select the below options:
Option Select
Cascading BC Sets Only Logon Client
Non-Cascading BC Sets Activate in the Login Client
Cross-Client BC Sets Do Not Activate

© SAP AG Page 7 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

Option Select
Ignore Previous Actions
Ignore Table Delivery Class X
An information popup is displayed: Job SFW_ACTIVATE_BC was started in the
background.
9. Continue with Enter.

The activation of the dependent BC Sets can be executed multiple times, in this
case the option Ignore Previous Actions needs to be set to ‘X’.

3.1.2.2 Activate Event Coupling for Workflow Template of


Sample Processes
Use
In this activity, you activate the event linkage for the workflow template of the sample
processes. In this way, you ensure that the relevant workflow template reacts to the triggering
event if you start one of the sample processes. In the standard system, the event linkage is
not activated. This task, however, is delivered as an implementation accelerator as part of this
rapid-deployment solution.

Procedure
1. Access the transaction using one of the following navigation options:
Transaction Code SWETYPV
IMG Menu SAP Menu Tools Business Workflow Development
Definition tools Events Event Linkages Type Linkages
2. On the Change View “Event Type Linkages”: Overview screen, select Position at the
bottom of the screen
3. On the Another entry screen enter the following values:
Field Value
Object Category CL
Object Type CL_HRASR00_WF_PROCESS_OBJECT
Event TRIGGERED
Receiver Type WS33700017
4. Select Continue (Enter) to position on the table entry.
5. On the Change View “Event Type Linkages”: Overview screen again, select Details. The
details of the object are displayed.
6. To activate the type linkage between the event creator and the event receiver choose the
checkbox in front of Linkage Activated.
7. Save your entries.
8. The first time you activate an event linkage, a Prompt for Customizing request dialog box
is displayed.
9. Select Create request to create a transport request, as required.

© SAP AG Page 8 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

10. Repeat step 2 through 9 also for the following entry:


Field Value
Object Category CL
Object Type CL_HRASR00_WF_PROCESS_OBJECT
Event TRIGGERED
Receiver Type WS33700018

3.1.3 Configuration of HCM Processes and Forms – Process


Configuration, Workflow Settings
In this section, you make all the settings required to configure form scenarios and the
corresponding Internet Service Request (ISR) scenarios. ISR scenarios are used within the
HR Administrative Services component to control the user interface as part of a form-based
process. For further details, please refer to the IMG Help Documentation. In relation to the
settings required for this rapid-deployment solution, the configuration steps below describe
the necessary setup if this task was performed manually.

3.1.3.1 Workflow Settings (Process Withdrawal)


Use
In this IMG activity, you activate the workflow template that informs the initiator of a process
whenever a process processor withdraws (cancels) this process. At the same time, an HR
Administrator is informed about subsequent activities (for example, checking the process
object, correcting changes to data in the database that were made during the process) by the
same workflow template. The recipient receives a corresponding notification in the Business
Workplace inbox. If automated content has been run, this step may be used for validation
purposes only in your system.

Procedure
1. Access the transaction using one of the following navigation options:
Transaction Code HRASR00_WFC_WITHD_VP
IMG Menu SAP Customizing Implementation Guide Personnel
Management HR Administrative Services Configuration of
Forms/Processes Process Configuration Technical
Settings Settings for Standard Components and Workflows
Activate Workflow After Withdrawing Process
2. On the Task Customizing Overview screen, select Activate event linking in the Event
Linkage column to open the Event Linkage: Triggering events screen. A list of workflow
templates for HCM Processes and Forms is displayed.
3. Select the top level task/event and select the Expand all icon to display the triggering
event under each of the workflow templates, together with the current status in the
Activate/deactivate column.
4. Select the Deactivated button, which is a toggle button, to activate event linkage for each
workflow template.
5. The first time you might be prompted for a Customizing request in a separate dialog box.
6. Select Create request button to create a transport request, as required.
7. Repeat step 4 to set the status of both workflow template event linkages to Activated in
the Activate/deactivate column.

© SAP AG Page 9 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

3.1.3.2 Workflow Settings (Draft for Process Start)


Use
When a process is started in the front end, the user has the option of saving the entered data
with the status Draft. In this case, the Draft for Process Start workflow (ASRDraft) starts. In
doing so, a process object is created in which the provisional data is stored. The user
receives a work item in his or her work inbox. The user can recall the process using this work
item. The provisional data from the process object is then displayed again in the form. The
user can then change the data again and resubmit it. If automated content has been run, this
step may be used for validation purposes only in your system.

Procedure
1. Access the transaction using one of the following navigation options:
Transaction Code HRASR00_WFC_DRAFT
IMG Menu SAP Customizing Implementation Guide Personnel
Management HR Administrative Services Configuration of
Forms/Processes Process Configuration Technical
Settings Settings for Standard Components and Workflows
Workflow: Draft for Process Start
2. On the Task Customizing Overview screen, select Activate event linking in the Event
Linkage column to open the Event Linkage: Triggering events screen. A list of workflow
templates for HCM Processes and Forms is displayed.
3. Select the top level task/event and select the Expand all icon to display the triggering
event under the associated workflow template, together with the current status of the
event linkage in the Activate/deactivate column.
4. Select the Deactivated button, which is a toggle button, to activate the event linkage for
the relevant workflow template.
5. The first time you might be prompted for a Customizing request in a separate dialog box.
6. Select Create request to create a transport request, as required.
7. Repeat step 4 to set the status of both workflow template event linkages to Activated in
the Activate/deactivate column.

3.1.3.3 Workflow Settings - Draft for Process Start (Error


Case)
Use
When a process is started in the Portal, error messages may occur. The user can then send
the current form and its data to an expert to resolve the error. In this case, the Draft for
Process Start with Errors workflow (ASRDraftErr) starts. In doing so, a process object is
created in which the provisional data is stored. The expert receives a work item in his or her
work inbox. This contains the form and the data for the error to be resolved. The expert
resolves the error and returns the work item to the process initiator. The process initiator
receives the work item in his or her work inbox. The initiator recalls the form with the data
using the work item and changes the data if necessary. The initiator then restarts the process,
as required. If automated content has been run, this step may be used for validation purposes
only in your system.

© SAP AG Page 10 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

Procedure
1. Access the transaction using one of the following navigation options:
Transaction Code HRASR00_WFC_DRAFTERR
IMG Menu SAP Customizing Implementation Guide Personnel
Management HR Administrative Services Configuration of
Forms/Processes Process Configuration Technical
Settings Settings for Standard Components and Workflows
Workflow: Draft for Process Start (Error Case)
2. On the Task Customizing Overview screen, select Activate event linking in the Event
Linkage column to open the Event Linkage: Triggering events screen. A list of workflow
templates for HCM Processes and Forms is displayed.
3. Select the top level task/event and select the Expand all icon to display the triggering
event under the associated workflow template, together with the current status of the
event linkage in the Activate/deactivate column.
4. Select the Deactivated button, which is a toggle button, to activate the event linkage for
the relevant workflow template.
5. The first time you might be prompted for a Customizing request in a separate dialog box.
6. Select Create request button to create a transport request, as required.

3.1.3.4 Workflow Settings (Exception Handling)


Use
The data of a process is saved asynchronously to the database. Errors can occur when
saving the data. With the Exception Handling: Asynchronous Call workflow (ASRExeptHndl),
the relevant error processors (experts) are informed about the occurrence of the error.
Depending on the type of error data, various error processors (experts) receive a notification
in their work inbox. This notification contains information about the process instance involved
and the activities that are to be performed. If automated content has been run, this step may
be used for validation purposes only in your system.

Procedure
1. Access the transaction using one of the following navigation options:
Transaction Code HRASR00_WFC_EXCPTHND
IMG Menu SAP Customizing Implementation Guide Personnel
Management HR Administrative Services Configuration of
Forms/Processes Process Configuration Technical
Settings Settings for Standard Components and Workflows
Workflow for Exception Handling When Saving
Asynchronously
2. On the Task Customizing Overview screen, select Activate event linking in the Event
Linkage column to open the Event Linkage: Triggering events screen. A list of workflow
templates for HCM Processes and Forms is displayed.
3. Select the top level task/event and select the Expand all icon to display the triggering
event under the associated workflow template, together with the current status of the
event linkage in the Activate/deactivate column.
4. Select the Deactivated button, which is a toggle button, to activate the event linkage for
the relevant workflow template.
5. The first time you might be prompted for a Customizing request in a separate dialog box.
6. Select Create request to create a transport request, as required.

© SAP AG Page 11 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

3.1.4 Configuration of HCM Processes and Forms – Process


Configuration, Process Objects
Runtime data and process objects that are saved during execution of form-based workflow
steps are saved using the Case Management component. In Case Management, the data is
stored hierarchically in three levels, whereby each level is defined in Case Management as a
case type. For further details, refer to the IMG Help Documentation. Activities required in
relation to this rapid-deployment solution are described in the steps below.

3.1.4.1 Process Objects, Case Types


Use
In this IMG activity, you compare the three case types delivered by SAP in the standard
system for HCM Processes and Forms to ensure that the versions in your development client
are identical to the SAP delivery client 000. This activity is a manual step, even if automated
content activation has been run.

It is important that the case types you transfer are transferred unchanged.

SAP delivers the following case types in the standard system: Process (H_PO),
Scenario (H_FO), and Step (H_SO).

Procedure
1. Ensure you are logged onto the development system you want to compare with client
000.
2. Access the transaction using the following navigation option:
Transaction Code SPRO
IMG Menu SAP Customizing Implementation Guide Personnel
Management HR Administrative Services Configuration of
Forms/Processes Process Configuration Technical
Settings Set up Process Object Copy Case Types
3. On the Change View “Case Type Maintenance”: Overview screen, select the file path
Utilities Adjustment.
4. In the Enter R/3 Connection pop-up window, use the drop-down list to select the client to
which the case types should be compared (this will be the client 000 for your
implementation, e.g. RDFCLNT000) and select Choose (Enter) to display the Overview:
Adjustment screen.

If no differences exist, the Comparison: SCMGV_CASETYPE dialog box is


displayed with the system message: “View/table contents are
identical. Display comparison results?” Select NO to continue.

If any differences exist between the current logon client and the comparison
client, please refer to the IMG Help Documentation to make changes, as
required.
5. Once the case types have been compared, a further comparison should be made to
ensure that the Customizing settings for each case type object are also identical to those
in client 000. From the Change View “Case Type Maintenance”: Overview screen, select

© SAP AG Page 12 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

the first object type, for example H_FO, and double-click Customizing for Case Copy from
the left-hand dialog structure.
6. On the Change View: “Customizing for Case Copy”: Overview screen, select the file path
Utilities > Adjustment.
7. In the Change View “Customizing for Case Copy” Overview dialog box, use the dropdown
list to select the client to which the case types are to be compared (this will be client 000
for your implementation, for example, RDFCLNT000) and select Choose (Enter) to
display the Overview: Adjustment screen.

If no differences exist, the Comparison: SCMGV_COPYCASE dialog box is


displayed with the system message: “View/table contents are
identical. Display comparison results?” Select NO to continue.

If any differences exist between the current logon client and the comparison
client, please refer to the IMG Help Documentation to make changes, as
required.
8. Repeat steps 5 through 7 for case types H_PO and H_SO.

3.1.4.2 Process Objects, Profile for Case Search


Use
In this IMG activity, you copy/adjust the profiles for the case search delivered by SAP in the
standard system for HCM Processes and Forms from the delivery client 000 to the client
development system. This activity is a manual step, even if automated content activation has
been run.

SAP delivers the following profiles in the standard system: Process Search
(ASR_POBJ), Scenario Search (ASR_FOBJ), and Step Search (ASR_SOBJ).

Procedure
1. Ensure you are logged onto the development system you want to compare with client
000.
2. Access the transaction using the following navigation option:
Transaction Code SPRO
IMG Menu SAP Customizing Implementation Guide Personnel
Management HR Administrative Services Configuration of
Forms/Processes Process Configuration Technical
Settings Set up Process Object Copy Profile for Case
Search
3. On the Change View “Profile of Case Search”: Overview screen, select the profile types in
the note above and select the file path Utilities > Adjustment.
4. In the Enter R/3 Connection dialog box, use the dropdown list to select the client to which
the case types are to be compared (this will be the client 000 for your implementation, for
example, RDFCLNT000) and select Choose (Enter) to display the Overview: Adjustment
screen.

If no differences exist, the Comparison: SCMGV_LOCAPROFIL dialog box is


displayed with the system message: “View/table contents are
identical. Display comparison results?” Select NO to continue.

© SAP AG Page 13 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

If any differences do exist between the current logon client and the comparison
client, please refer to the IMG Help Documentation to synchronize them as
required.
5. Once the profiles have been compared, a further comparison should be made to ensure
that the selection fields for each profile are also identical to client 000. From the Change
View “Profile of Case Search”: Overview screen, select the first profile, for example
ASR_FOBJ, and double-click Selection Fields from the left-hand dialog structure.
6. On the Change View: “Selection Fields”: Overview screen, select the menu path Utilities >
Adjustment.
7. In the Change View “Selection Fields” Overview dialog box, use the dropdown list to
select the client to which the case types are to be compared (as previously, this will be
the client 000 for your implementation, for example, RDFCLNT000) and select Choose
(Enter) to display the Overview: Adjustment screen.

If no differences exist, the Comparison: SCMGV_LOCAFIELDS dialog box is


displayed with the system message: “View/table contents are
identical. Display comparison results?” Select NO to continue.

If any differences exist between the current logon client and the comparison
client, please refer to the IMG Help Documentation to synchronize them as
required.
8. Repeat steps 5 through 7 for profiles ASR_POBJ and ASR_SOBJ.

3.1.5 Configuration of Forms/Processes


Use
The following steps specify the configuration requirements for HCM Processes and Forms
that are required for this rapid-deployment solution. They should be performed in order to
ensure that all relevant forms are consistent at process and form scenario level. This activity
is a manual step, even if automated content activation has been run.

Procedure
1. Access the transaction using one of the following navigation options:
Transaction Code HRASR_DT
IMG Menu SAP Customizing Implementation Guide Personnel
Management HR Administrative Services Configuration of
Forms/Processes Design Time for Processes and Forms
2. On the Design Time for Processes and Forms screen, use the dropdown search to select
the Form Scenario option in the left-hand navigation window.
3. From the top level navigation menu, select Design Time > Reconcile Objects.
4. In the Reconcile Objects dialog box, select the Form Scenario radio button and Continue
(Enter).
5. On the Reconcile Form Scenarios screen, enter the RFC connection to the client 000
system, for example, RDFCLNT000, with which you wish to make the reconciliation.
6. Select the Display Form Scenarios of Remote System button to display the list of form
scenarios from client 000 (for example, RDFCLNT000).

© SAP AG Page 14 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

7. From the list displayed, select the following forms that were defined as part of the
respective roles HRASRA (Administrator), HRASRB (Manager), and HRASRD
(Employee) for this rapid-deployment solution:
Form Scenario Name
S_HR_PA_XX_CHWT_1_WD Change of Working Time (XX)
8. Select the Reconcile (Import from Remote System) button.
9. The Reconcile Form Scenarios? Dialog box is displayed with the system message “Are
You Sure You Want to Reconcile Selected Form Scenarios?” Select YES
to continue.
10. When prompted, create and save a new transport request for the forms that were
reconciled, as specified above.
11. When prompted again, select Continue (Enter). An overview screen shows the status of
reconciliation per form. Select Enter to continue.

On the Reconcile Form Scenarios screen, the status indicator will be displayed as
a Green Square; the status indicator for unchecked form scenarios will remain as
Gray Diamond which is as expected since reconciliation was not performed.
12. You have to repeat reconciliations for the process levels of the relevant scenarios. On the
Design Time for Processes and Forms screen, use the dropdown search to select the
process option from the left-hand navigation window.
13. From the top level navigation menu, select Design Time Reconcile Objects.
14. In the Reconcile Objects dialog box, select the Process radio button and the Continue
(Enter).
15. On the Reconcile Processes screen, enter the RFC connection, for example client 000,
from which you wish to make the reconciliation.
16. Select the Refresh Display Remote System Processes button to display the list of
processes from client 000 (for example, RDFCLNT000).
17. The following processes, as defined by the scope of the rapid-deployment solution, must
be reconciled with client 000 (for example, RDFCLNT000):
Process Name
HR_PA_XX_CHANGE_WORKINGTIME_1_WD Change in Working Time (XX) Web Dynpro
18. Select the Reconcile (Import from Remote System) button to start the reconciliation
process.
19. The Reconcile Processes? dialog box is displayed with the system message “Are You
Sure You Want to Reconcile Selected Processes?” Select YES to continue.
20. When prompted, create and save a new transport request for the forms that were
reconciled, as specified above.
21. When prompted to reconcile once again, select the Continue (Enter). An overview screen
shows the status of reconciliation per process. Select Enter to continue.

On the Reconcile Processes screen, the status indicator will be displayed as a


Green square; the status indicator for unchecked processes will remain as a gray
Diamond, which is as expected since reconciliation was not performed.

© SAP AG Page 15 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

3.1.6 Process Configuration, Set Up Processes


In this activity, you specify which processes are available to the user on the user interface
depending on the role of the user. In addition, the display and behavior of the processes are
determined by further customizing settings, as described in the sections below.

3.1.6.1 Set Up Processes, Validity for Process Start


Use
The following IMG steps will enable specific forms for a particular end-user role; in this case,
certain forms will be enabled for Employee and/or Manager, based on their technical roles
within HCM Processes and Forms.

The process start for the role HR Administrator is planned with the Q4 delivery of
SAP HR renewal 1.0. Please check the current road map of SAP HR renewal 1.0.

The initiator roles available within the context of this rapid-deployment solution
and HCM Processes and Forms based on Web Dynpro ABAP are: HRASRB
(Manager) and HRASRD (Employee). The support of initiator role HRASRA (HR
Administrator) is planned with the Q4 delivery of SAP HR renewal 1.0.

Procedure
1. Access the transaction using the following navigation option:
Transaction Code SPRO
IMG Menu SAP Customizing Implementation Guide Personnel
Management HR Administrative Services Configuration of
Forms/Processes Process Configuration Set Up
Processes Validity for Process Start Specify Valid
Processes for Start Applications
2. In the Determine Work Area: Entry dialog box, use the dropdown search to choose the
HRASRB (Manager) initiator role and select Continue (Enter).
3. In the New Design Time for Processes and Forms Available dialog box, select the Cont.
button to continue without design time and open the Change View “Valid Processes for
Start Applications”: Overview screen.
4. Check or create table entries as specified in the table below:
User Initiator Role Process Process Name Valid
Action
Check Manager HR_PA_XX_CHANGE_WO Change in Working X
RKINGTIME_1_WD Time (XX) Web
Dynpro

Validity assignments for any processes other than those above should be
deselected as they are not relevant for this rapid-deployment solution.
5. Save your entries.
6. Return to the IMG menu and repeat step 1 above.
7. In the Determine Work Area: Entry dialog box, use the dropdown search to choose the
HRASRD (Employee) initiator role and select Continue (Enter).

© SAP AG Page 16 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

8. In the New Design Time for Processes and Forms Available dialog box, select the Cont.
button to continue without design time and open the Change View “Valid Processes for
Start Applications”: Overview screen.
9. Check or create table entries as specified in the table below:
User Initiator Role Process Process Name Valid
Action
Check Employee HR_PA_XX_CHANGE_WO Change in Working X
RKINGTIME_1_WD Time (XX) Web
Dynpro

Validity assignments for any processes other than those above should be
deselected as they are not relevant for this rapid-deployment solution.
10. Save your entries.
11. For initiator role HRASRB (Manager), define a group of processes for the start applications:
Access the transaction using the following navigation option:
Transaction Code SPRO
IMG Menu SAP Customizing Implementation Guide Personnel
Management HR Administrative Services Configuration of
Forms/Processes Process Configuration Set Up
Processes Process Groups Define Process Groups
12. On the Change View “Process Groups”: Overview screen, create the following new entry:
Field Name Entry Value
Proc.Grp. 99MG
Description Manager
13. Save your entry.
14. Access the transaction using the following navigation option:
Transaction Code SPRO
IMG Menu SAP Customizing Implementation Guide Personnel
Management HR Administrative Services Configuration of
Forms/Processes Process Configuration Set Up
Processes Process Groups Group Processes for UI
Control and Collision Check
15. In the New Design Time for Processes and Forms Available dialog box, select the Cont.
button to continue without design time and open the Change View “Group Processes for
UI Control and Collision Check”: Overview screen.
16. On the Change View “Group Processes for UI Control and Collision Check”: Overview
screen, create the following entry:
Field Name Entry Value
Proc.Grp. 99MG
Description Manager
Process HR_PA_XX_CHANGE_WORKINGTIME_1_WD
Process Name Change in Working Time (XX) Web Dynpro
Start Date 01/01/1800
End Date 12/31/9999

© SAP AG Page 17 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

Field Name Entry Value


Relev.UI X
Coll.Chk
17. To add entries select the New Entries button to display the New Entries: Overview of
Added Entries screen. Create new entry as specified above.
18. Save your entry.

3.1.6.2 Set Up Processes, Properties of Object Types


Use
The following IMG steps enable you to specify the object types available for specific
application types and the roles that can access them. This activity must be performed as a
manual step.

Procedure
1. Access the transaction using the following navigation option:
Transaction Code SPRO
IMG Menu SAP Customizing Implementation Guide Personnel
Management HR Administrative Services Configuration of
Forms/Processes Process Configuration Set Up
Processes Validity for Process Start Define Properties of
Object Types
2. On the Change View “Objects”: Overview screen from the Objects dialog structure,
create/check the following entries:
User Object Type Object type text Used in ASR Appl. Type
Action
Create C Job X Personnel Development
Create NB Requisition Recruitment
Create O Organizational X Personnel Development
unit
Create P Person X Personnel Administration
Create S Position X Personnel Development
3. Save your entries and assign to an appropriate transport request, when prompted.
4. A system message confirms data was saved.
5. On the Change View “Objects”: Overview screen, highlight Object Type C (Job) and
double-click Object Properties in the dialog structure to go to the Change View “Object
Properties”: Overview screen.
6. Check or create table entries for the selected object as specified in the table below:
User Object Object Agent Role Name Group of Is Skip
Action Type Type Organizational Visible?
Text Views
Check C Job HRASRA HR ASR_JOB_SEARC
Administrator H
7. To add entries select the New Entries button to display the New Entries: Overview of
Added Entries screen. Create new entries for the selected object as specified above.
8. Save your entries and select the Back (F3) button twice to return to the full table view on
the Change View “Objects”: Overview screen.

© SAP AG Page 18 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

9. Select Object Type O (Organizational unit) and double-click Object Properties in the
dialog structure to go to the Change View “Object Properties”: Overview screen.
10. Check or create table entries for the selected object as specified in the table below:
User Object Object Type Agent Name Group of Is Skip
Action Type Text Role Organizatio Visible?
nal Views
Check O Organizational HRASRA HR ASR_ORG_
unit Administrator SEARCH
Check O Organizational HRASRB Manager MSS_ASR_
unit ORG_SEL
11. To add entries select the New Entries button to display the New Entries: Overview of
Added Entries screen. Create new entries for the selected object as specified above.
12. Save your entries and select the Back (F3) button twice to return to the full table view on
the Change View “Objects”: Overview screen.
13. Select Object Type P (Person) and double-click Object Properties in the dialog structure
to go to the Change View “Object Properties”: Overview screen.
14. Check or create table entries for the selected object as specified in the table below:
User Object Object Agent Name Group of Is Skip
Action Type Type Role Organizational Views Visible?
Text
Check P Person HRASRB Manager MSS_ASR_TMV_EE
15. To add entries select the New Entries button to display the New Entries: Overview of
Added Entries screen. Create new entries for the selected object as specified above.
16. Save your entries and select the Back (F3) button twice to return to the full table view on
the Change View “Objects”: Overview screen.
17. Select Object Type S (Position) and double-click Object Properties in the dialog structure
to go to the Change View “Object Properties”: Overview screen.
18. Check or create table entries for the selected object as specified in the table below:
User Object Object Agent Name Group of Is Skip
Action Type Type Role Organizational Visible?
Text Views
Check S Position HRASRA HR ASR_POS_SEA
Administrator RCH
Check S Position HRASRB MSS_ASR_P MSS_ASR_PO
OS_SEL S_SEL
19. To add entries select the New Entries button to display the New Entries: Overview of
Added Entries screen. Create new entries for the selected object as specified above.
20. Save your entries.

3.1.7 Workflow: Task Type Maintenance


Manual steps need to be performed as follows to ensure that the relevant workflow tasks for
HCM Processes and Forms are specified correctly.

Procedure
1. Access the transaction using the following navigation option:
Transaction Code PFTC
2. On the Task Maintain screen, enter the following values:

© SAP AG Page 19 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

Field Name Entry Value


Task type Standard task
Task 8-digit numeric identifier of the workflow task: 17900100
Name Description of the Task: Process Form
3. Select Display to open the Standard Task: Display screen.
4. From the navigation menu, select Additional data Agent assignment Maintain to
open the Standard task: Maintain Agent Assignment screen.
5. Select the Attributes button to open the Task dialog box.
6. Ensure that the General Task radio button is selected and select Transfer to return to the
Standard task: Maintain Agent Assignment screen.
7. When prompted, create and save a new transport request for the task type change.
8. Select Update Index to complete the task.
9. A system message confirms that the index was generated.
10. Repeat from step 2 above for the following additional task types/tasks:
Task Type Task ID Name
Standard Task 17900101 Approve Form
Standard Task 17900102 Form is edited again by
Author
Workflow Template 17900260 Save Form with Error
Handling
Standard Task 04000018 Process PD Form
Standard Task 04000019 Approve PD Form
Standard Task 04000020 PD Form is Edited Again by
Author
Standard Task 04000021 Draft for PD Process Start
Standard Task 04000022 Forwarded because of
Errors in PD Form

3.1.8 Create Role for HR Administrator and Assign to Users


The following steps describe the activities required to configure a role for an HR Administrator
for use in the SAP NetWeaver Business Client (NWBC) for HTML. The configured role is
aligned with the personnel administration and organization management scope of the rapid-
deployment solution.

PFCG roles are delivered with the SAP Best Practices add-on, as described in
the Quick Guide.
Composite Role Description
SAP_NBPR_XX_HRADM2_PAOM_NWBC_S HRADMIN NWBC Role (HCM RDS
PA&OM)
Single Role
SAP_NBPR_XX_HRADM2_PAOM-S1 HR Administrator: NWBC role
The manual steps required to set up the roles (if the SAP Best Practices add-on
is not installed) are as follows:

© SAP AG Page 20 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

Procedure
1. Access the transaction using one of the following navigation options:
Transaction Code PFCG
IMG Path SAP Customizing Implementation Guide HR
Administrative Services HR Administrator in SAP
NetWeaver Business Client Assign HR Administrator Role
to Users
2. On the Role Maintenance screen, create a new role by copying the standard SAP role as
follows:
Field Name Entry Value
Role Use the dropdown search to locate the standard SAP
composite role ESS role SAP_ASR_HRADMIN_HCM_CI_3
3. Select Copy Role and specify a name in your namespace e.g. as follows:
Field Name Entry Value
from role SAP_ASR_HRADMIN_HCM_CI_3
to role Y_NBPR_XX_HRADM2_PAOM_NWBC_S
4. Select Copy All.
5. A system message confirms “Composite Role successfully copied with the
single roles”.
6. In the dialog box, choose YES to the prompt “Should the Single Roles be
Copied and Reentered?”
7. In the “Enter target for single roles”, enter names for the new single roles in
your namespace e.g. as follows:
Old role New Role
SAP_ASR_HRADMIN_SR_HCM_CI_3 Y_NBPR_XX_HRADM2_PAOM-S1
8. A system message confirms “Composite SAP_NBPR_XX_HRADM_PAOM_NWBC_S
role created”.
9. On the Role Maintenance screen, select Change to go to the Change Roles screen.
10. On the Description tab page, enter the following:
Field Name Entry Value
Description HRADMIN NWBC Role (HCM RDS PA&OM)
Long Text This role is a copy of the SAP standard, composite role
SAP_ASR_HRADMIN_HCM_CI_3, together with the
corresponding single role
SAP_ASR_HRADMIN_SR_HCM_CI_3. It is intended for use
as part of the SAP ERP HCM Rapid-Deployment Solution for
Personnel Administration and Organization Management
together with HCM Processes and Forms using Web Dynpro
ABAP.
11. On the Roles tab page, the following single role should be specified as Active:
Role Name Target Sys Active
Y_NBPR_XX_HRADM2_PAOM-S1 HR Administrator: user system X
NWBC role

© SAP AG Page 21 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

12. On the Change Roles screen, Menu tab, select Other Node Details and check or change
the following settings:
User Folder Sub- Sub-Folder2 Transaction Web Text /
Action Folder1 Dynpro Characteristic
Application
Check HR HR Administrator /
Administrator Single Top Level
Check Home Home
Check Home IBO_WDA_INB Home / Default
OX Page / Visible
Home SWNWIEX WF Notification:
Edit Work Item /
Invisible
Check Work Work Overview
Overview
Check Work ASR_PA_PD_P Process
Overview ROCESSES_DI Overview/ Default
SPLAY Page / Visible
Check Employee- Employee-Related
Related Services
Services
Check Employee- ASR_PROCES Open Employee
Related SES_DISPLAY Processes /
Services Default Page
Check Employee- Services Services
Related
Services
Change Employee- Services ASR_PROCES Start Process for
Related S_EXECUTE_F Employee /
Services PM Invisible
Change Employee- Services ASR_MASS_S Start Process for
Related TART_PROCE Multiple
Services SS Employees /
Invisible
Check Employee- Services ASR_PROCES Search Employee
Related SES_DISPLAY Processes /
Services Visible
Check Employee- Services S_EH5_010002 Process
Related 59 Employee Data /
Services Visible
Change Employee- Services ASR_PROCES Execute Hiring /
Related S_EXECUTE_F Invisible
Services PM
Check Organizational Organizational-
-Related Related Services
Services
Check Organizational ASR_PA_PD_P Open
-Related ROCESSES_DI Organizational
Services SPLAY Process / Visible

© SAP AG Page 22 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

User Folder Sub- Sub-Folder2 Transaction Web Text /


Action Folder1 Dynpro Characteristic
Application
Check Organizational Services Services
-Related
Services
Change Organizational Services ASR_PROCES Start
-Related S_EXECUTE_F Organizational
Services PM Process /
Invisible
Check Organizational Services ASR_SRCH_P Search
-Related D_PROCESS Organizational
Services Process / Visible
Check Employee Employee
Information Information
Check Employee ASR_PROFILE Employee Data /
Information S_SHOW Visible
Check Employee Services Services
Information
Check Employee Services ASR_PROCES Display Processes
Information SES_DISPLAY / Visible
Change Employee Services ASR_PROCES Start Processes /
Information S_EXECUTE_F Invisible
PM
Delete Employee Services ASR_LAUNCH Display Employee
Information PAD Reports / Visible
Check Employee Services ASR_KEYWOR Keyword Search /
Information D_SEARCH Visible
Change Employee Services ASR_PERSON Process
Information NEL_FILE Personnel File /
Invisible
Check Employee Services S_EH5_010002 Process
Information 59 Employee Data /
Visible
Delete Reports Reports
Folder
Check ASR_PROCES Inbox Execute
S_EXECUTE_F Process /
PM Invisible/ OBN
Target
Check ASR_PROCES Inbox Select
S_SELECT Processes/
Invisible/ OBN
Target
Check HRASR_CALL_ OBN Display
TX_ATTCH Attachments/
Invisible / OBN
Target
Check ASR_FORM_DI OBN Display

© SAP AG Page 23 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

User Folder Sub- Sub-Folder2 Transaction Web Text /


Action Folder1 Dynpro Characteristic
Application
SPLAY Form / Invisible /
OBN Target
Check ASR_FORM_DI OBN Display
SPLAY Form Manager/
Invisible / OBN
Target
Check HRASR_EXEC OBN Start of
_TX_PASR_W Transaction
PASR/ Invisible /
OBN Target
13. Save your entries.

3.1.9 Object-Based Navigation


Procedure
1. Access the transaction using one of the following navigation options:
Transaction Code LPD_CUST
IMG Path SAP Customizing Implementation Guide Personnel
Management HR Administrative Services HR Administrator
in SAP NetWeaver Business Client Adjust Object-Based
Navigation of HR Administrator Role
2. On the Overview of Launchpads screen, check that the following settings exist:
User Action Role Instance Description Repository
Check HRADM_NAV OBN OBN for HR Admin

For the HCM Processes & Forms based on Web Dynpro ABAP some of the
underlying ESS/MSS menus must be changed to enable this. This is achieved by
the following configuration, which must be performed as manual steps in each
SAP client, such as QA and Production, as part of the client preparation activities.

3.2 Assignment of PA Processes to the ESS Scenario


This section describes how to assign a process that uses a form scenario based on Web
Dynpro ABAP to the ESS PFCG role.

3.2.1 Start Process Configuration for Employee


Procedure
1. Access the transaction using the following navigation option:
Transaction Code PFCG
IMG Path SAP Customizing Implementation Guide Personnel
Management Employee Self-Service (Web Dynpro ABAP)
General Settings ESS Menu for Services Menu for SAP
NetWeaver Business Client for HTML Set up PFCG Menu*

© SAP AG Page 24 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

This is not an executable IMG step, but can be referenced for relevant
documentation. ESS NWBC roles must be configured directly using transaction
PFCG.
2. On the Role Maintenance screen enter the RDS ESS composite role using the drop-down
search for example:
Field Name Entry Value
Role Y_NBPR_XX_ESS_PAOM_NWBC_S
3. Select Change to go to the Change Roles screen.
4. On the Change Roles screen, Menu tab, select ‘Other Node Details and locate the below
menu entry :
User Folder Sub-Folder1 Sub-Folder2 Application Description of
Action Change
Change Working Time Employment Request a Change
Percentage Change in Parameters
Employment
Percentage
5. Do a right-mouse click on Request a Change in Employment Percentage, to select
Details and to see the technical settings.
6. On the Web Dynpro Application screen, enter the following:
Field Value
Web Dynpro Application ASR_PROCESS_EXECUTE_OVP
Application Configuration ASR_PROCESS_EXECUTE_OVP_CFG
7. On the list of parameters, correct the following entries:
Field Value
PROCESS HR_PA_XX_CHANGE_WORKINGTIME_1_WD
INITIATOR_ROLE HRASRD

Processes based on Web Dynpro ABAP are now called via new Web Dynpro
Application and Configuration: ASR_PROCESS_EXECUTE_OVP /
ASR_PROCESS_EXECUTE_OVP_CFG.
8. Save your entries.

3.2.2 POWL Inbox Customizing for Administrator


The following section describes the additional manual configuration which needs to be done
to launch a new form scenario based on Web Dynpro ABAP from the POWL inbox.

3.2.2.1 Defining a new method for the BOR Object


Procedure
1. Access the transaction using the following navigation option:
Transaction Code SWO1
IMG Path SAP Menu Tools Business Workflow Development
Definition tools Application Integration Business Object
Builder

© SAP AG Page 25 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

2. On the Business Object Builder: Initial Screen, enter the following:


Field Value
Object/Interface Type HRADMIN_WL
3. Choose Change to define a new method for this BOR objects.
4. On the Change Object Type HRADMIN_WL screen, collapse the existing methods.
5. From the navigation menu, select Create (F5).
6. In the dialog box Create method, choose NO to the prompt Create with function
module as template?
7. On the Change Object Type HRADMIN_WL screen, enter the following values:
Field Value
Method NAVIGATE_FORM_WD
Name NAVIGATE_FORM_WD
Description Navigate form WD
8. On the tabs General, Result type and ABAP, keep the standard entries:
General tab:
Field Value
Dialog X
Synchronous X
Result parameter
Instance-independent
Result type tab:
Field Value
ABAP Dictionary X
Reference table
Reference field
Search Help
Object type
Multiline
ABAP tab:
Field Value
Functional module
API function
Transaction
Dialog module
Report
Other X
Name
9. Choose Continue (Enter).
10. Save your changes.

© SAP AG Page 26 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

3.2.2.2 Define Tasks and Actions


3.2.2.2.1 Create or Change Actions
Procedure
1. Access the transaction using the following navigation option:
Transaction Code SPRO
IMG Path SAP Customizing Implementation Guide Cross-Application
Components Processes and Tools for Enterprise Applications
Inbox Define Tasks and Actions
2. Choose Create or Change Actions on the Choose Activity menu popup.
3. On executing this IMG step, an information message is displayed: Individual
entries cannot be put into the change request. Confirm this message with
Continue (Enter).
4. Create table entries as specified in the table below:
Application Action Name Action Type for Action
ASR_HRADMIN_INBOX EXECUTETASKWD OBJECTNAVIGATIONLAUNCHER
5. Save your entries.

3.2.2.2.2 Define Action Properties


Procedure
1. Access the transaction using the following navigation option:
Transaction Code SPRO
IMG Path SAP Customizing Implementation Guide Cross-Application
Components Processes and Tools for Enterprise Applications
Inbox Define Tasks and Actions
2. Choose Define Action Properties on the Choose Activity menu popup.
3. On executing this IMG step, an information message is displayed: Individual
entries cannot be put into the change request. Confirm this message with
Continue (Enter).
4. Create table entries as specified in the table below:
Application Action Name Name of Action Value of Action
Proptery Property
ASR_HRADMIN_INBOX EXECUTETASKWD OBJECTNAME HRADMIN_WL
ASR_HRADMIN_INBOX EXECUTETASKWD OBJECTVALUE WI_ID=${ITEM.EXTE
RNALID}
ASR_HRADMIN_INBOX EXECUTETASKWD OPERATION NAVIGATE_FORM_
WD
5. Save your entries.

© SAP AG Page 27 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

3.2.2.2.3 Define Task Properties


Procedure
1. Access the transaction using the following navigation option:
Transaction Code SPRO
IMG Path SAP Customizing Implementation Guide Cross-Application
Components Processes and Tools for Enterprise Applications
Inbox Define Tasks and Actions
2. Choose Define Task Properties on the Choose Activity menu popup.
3. On executing this IMG step, an information message is displayed: Individual
entries cannot be put into the change request. Confirm this message with
Continue (Enter).
4. Create table entries as specified in the table below:
Application Workflow Task Task Compl Action Name
ID
ASR_HRADMIN_INBOX TS33700021 EXECUTETASKWD
ASR_HRADMIN_INBOX TS33700022 EXECUTETASKWD
ASR_HRADMIN_INBOX TS17900100 EXECUTETASKWD
ASR_HRADMIN_INBOX TS17900101 EXECUTETASKWD
5. If you have created your own workflow tasks for approval and processing please create
additional entries for applications ASR_HRADMIN_INBOX.
6. Save your entries.

3.2.2.2.4 Assign Actions to Tasks


1. Access the transaction using the following navigation option:
Transaction Code SPRO
IMG Path SAP Customizing Implementation Guide Cross-Application
Components Processes and Tools for Enterprise Applications
Inbox Define Tasks and Actions
2. Choose Assign Actions to Tasks on the Choose Activity menu popup.
3. On executing this IMG step, an information message is displayed: Individual
entries cannot be put into the change request. Confirm this message with
Continue (Enter).
4. Create table entries as specified in the table below:
Application Workflow Task Task Compl Action Name
ID
ASR_HRADMIN_INBOX TS33700021 EXECUTETASKWD
ASR_HRADMIN_INBOX TS33700022 EXECUTETASKWD
ASR_HRADMIN_INBOX TS17900100 EXECUTETASKWD
ASR_HRADMIN_INBOX TS17900101 EXECUTETASKWD

5. If you have created your own workflow tasks for approval and processing please create
additional entries for application ASR_HRADMIN_INBOX.
6. Save your entries.

© SAP AG Page 28 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

3.2.2.3 Assign Task IDs to POWL Types


Procedure
1. Access the transaction using the following navigation option:
Transaction Code SM30
IMG Path SAP Easy Access Menu System Services Table
Maintenance Extended Table Maintenance
2. On the Maintain Table Views: Initial Screen screen enter the below value:
Field Value
Table/View IBO_V_WF_TA_P_TY
3. Choose Display to review the SAP delivered content.
4. Check if the below entries exists in the table:
Application POWL Type ID Workflow Task ID
ASR_HRADMIN_INBOX ASR_HRADMIN_INBOX_WI TS33700021
ASR_HRADMIN_INBOX ASR_HRADMIN_INBOX_WI TS33700022
ASR_HRADMIN_INBOX ASR_HRADMIN_INBOX_WI TS17900100
ASR_HRADMIN_INBOX ASR_HRADMIN_INBOX_WI TS17900101
5. If entries are missing please add these to the customer specific table. To do so access
the transaction using the following navigation option:
Transaction Code SPRO
IMG Path SAP Customizing Implementation Guide Cross-Application
Components Processes and Tools for Enterprise Applications
Inbox Assign Task IDs to POWL Types
6. On the Change View “Assignment of Task IDs to POWL Types”: Overview screen select
Assign additonal Task IDs in the Dialog Structure navigation.
7. Add only the missing entries from the table specified in step 4.
8. Or if you have created your own workflow tasks for approval and processing please also
create these entries for application ASR_HRADMIN_INBOX and POWL type
ASR_HRADMIN_INBOX_WI.
9. Save your entries.

3.2.2.4 PFCG Role Changes


Procedure
1. Access the transaction using the following navigation option:
Transaction Code PFCG
IMG Path SAP Customizing Implementation Guide Personnel
Management Manager Self-Service (Web Dynpro ABAP)
Manager Self-Service in SAP NetWeaver Business Client
Create Role for Manager Self-Service and Assign to Users
2. On the Role Maintenance screen, enter the RDS HR Admin composite role using the
drop-down search for example:
Field Name Entry Value
Role Y_NBPR_XX_HRADM2_PAOM_NWBC_S

© SAP AG Page 29 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

3. Select Change to go to the Change Roles screen.


4. On the Change Roles screen, Menu tab, select ‘Other Node Details and locate the below
menu entry :
User Folder Sub- Sub-Folder2 Application Description of
Action Folder1 Change
Change HR Inbox Change
Administrator Execute Parameters
Process
5. Right-click on Inbox Execute Process to select Details and to see the technical settings.
6. On the Web Dynpro Application screen, enter the following:
Field Value
Web Dynpro Application ASR_PROCESS_EXECUTE_OVP
Application Configuration ASR_PROCESS_EXECUTE_OVP_CFG
7. The list of parameters stays unchanged:
Field Value
WDSUPPORTSFULLHEIGHT 2
8. Choose Continue (Enter).
9. To implement the method NAVIGATE_FORM_WD of the business object HRADMIN_WL
select the method below Object-Based Navigation below other node details.
10. Choose Remove Method.
11. To add the new implementation method NAVIGATE_FORM_WD choose Insert Method.
12. Enter the values as specified in the table below:
Field Value
Obj. Type HRADMIN_WL
Object Type Name HRADMIN_WL
Method ID NAVIGATE_FORM_WD
Method Name Navigate form WD
13. Select OK (Enter) to proceed.
14. On the Parameter Assignment screen, create the following entries in the Parameter
Assignment table:
Field Value
WI_ID {WI_ID}
Portal_bo_alias SAP_ERP_HumanResources
15. Choose OK (Enter) and save your entries.

© SAP AG Page 30 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

3.3 Assignment of PA Processes to the MSS Scenario


The following steps describe the activities required to configure a role for a manager to start
and execute form scenarios based on Web Dynpro ABAP using in SAP NetWeaver Business
Client (NWBC) for HTML.

3.3.1 Start Process Configuration for Manager


Procedure
1. Access the transaction using the following navigation option:
Transaction Code PFCG
IMG Path SAP Customizing Implementation Guide Personnel
Management Manager Self-Service (Web Dynpro ABAP)
Manager Self-Service in SAP NetWeaver Business Client
Create Role for Manager Self-Service and Assign to Users
2. On the Role Maintenance screen enter the RDS MSS composite role using the drop-
down search for example:
Field Name Entry Value
Role Y_NBPR_XX_MSS_PAOM_NWBC_M
3. Select Change to go to the Change Roles screen.
4. On the Change Roles screen, Menu tab, select ‘Other Node Details and change the
following settings:
User Folder Sub-Folder1 Sub-Folder2 Web Text /
Action Dynpro Characteristic
Application
Change Team Processes ASR_PROC Processes for
for ESS_EXEC Employees /
Employees UTE_FPM Invisible
Change Organization Organization ASR_PROC Start
al Services ESS_EXEC Organizational
UTE_FPM Process /
Invisible
5. Open Launchpad Customizing using one of the following navigation options:
Transaction Code LPD_CUST
IMG Path SAP Customizing Implementation Guide Personnel
Management Manager Self-Service (Web Dynpro ABAP)
Object-Based Navigation Adjust Object-Based Navigation
for Manager Self-Service
6. To adapt the process start on the employee context menu in the MSS, select the Role
‘MSS and the Instance EMPLOYEE_MENU on the Overview of Launchpads screen and
select the Change icon.
7. From the Change Launchpad Role: MSS Instance: EMPLOYEE_MENU screen, change
the below entry:
User Menu Folder Application Applica-tion Description
Action Type Desc. of Change
Change Employee Start Change WebDynpro Change
Processes on Requests ABAP Parameters
Behalf of

© SAP AG Page 31 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

Employee
8. Click Show Advanced Parameters and enter the following values:
Application Parameters:
Field Value
Application ASR_PROCESS_EXECUTE_OVP
Application-Related Parameters:
Field Value
Target App. Parameters PERNR_MEM_ID&SUBST_CLASSIFICATION=NO_CLA
SS&PROCESS_GROUP=99MG&INITIATOR_ROLE=HR
ASRB
Configuration ASR_PROCESS_EXECUTE_OVP_CFG

Processes based on Web Dynpro ABAP are now called via new Web Dynpro
Application and Configuration: ASR_PROCESS_EXECUTE_OVP /
ASR_PROCESS_EXECUTE_OVP_CFG. For more information regarding the
assignment of a process to PFCG Roles please see also the SAP
Documentation.
9. Save your entries.

3.3.2 POWL Inbox Customizing for Manager


The following section describes the additional manual configuration which needs to be done
to launch a new form scenario based on Web Dynpro ABAP from the POWL inbox.

3.3.2.1 Defining a new method for the BOR Object


Procedure
1. Access the transaction using the following navigation option:
Transaction Code SWO1
IMG Path SAP Menu Tools Business Workflow Development
Definition tools Application Integration Business Object
Builder
2. On the Business Object Builder: Initial Screen, enter the following:
Field Value
Object/Interface Type MSS_WL
3. Choose Change to define a new method for this BOR objects.
4. On the Change Object Type MSS_WL screen, collapse the existing methods.
5. From the navigation menu, select Create (F5).
6. In the dialog box Create method, choose NO to the prompt Create with function
module as template?
7. On the Change Object Type MSS_WL screen, enter the following values:
Field Value
Method NAVIGATE_FORM_WD
Name NAVIGATE_FORM_WD
Description Navigate form WD

© SAP AG Page 32 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

8. On the tabs General, Result type and ABAP, keep the standard entries:
General tab:
Field Value
Dialog X
Synchronous X
Result parameter
Instance-independent
Result type tab:
Field Value
ABAP Dictionary X
Reference table
Reference field
Search Help
Object type
Multiline
ABAP tab:
Field Value
Functional module
API function
Transaction
Dialog module
Report
Other X
Name
9. Choose Continue (Enter).
10. Save your changes.

3.3.2.2 Define Tasks and Actions


3.3.2.2.1 Create or Change Actions
Procedure
1. Access the transaction using the following navigation option:
Transaction Code SPRO
IMG Path SAP Customizing Implementation Guide Cross-Application
Components Processes and Tools for Enterprise Applications
Inbox Define Tasks and Actions
2. Choose Create or Change Actions on the Choose Activity menu popup.
3. On executing this IMG step, an information message is displayed: Individual
entries cannot be put into the change request. Confirm this message with
Continue (Enter).

© SAP AG Page 33 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

4. Create table entries as specified in the table below:


Application Action Name Action Type for Action
MANAGER_MSS_INBOX EXECUTETASKWD OBJECTNAVIGATIONLAUNCHER
MANAGER_MSS_INBOX_2 EXECUTETASKWD OBJECTNAVIGATIONLAUNCHER
5. Save your entries.

3.3.2.2.2 Define Action Properties


Procedure
1. Access the transaction using the following navigation option:
Transaction Code SPRO
IMG Path SAP Customizing Implementation Guide Cross-Application
Components Processes and Tools for Enterprise Applications
Inbox Define Tasks and Actions
2. Choose Define Action Properties on the Choose Activity menu popup.
3. On executing this IMG step, an information message is displayed: Individual
entries cannot be put into the change request. Confirm this message with
Continue (Enter).
4. Create table entries as specified in the table below:
Application Action Name Name of Action Value of Action
Proptery Property
MANAGER_MSS_IN EXECUTETASKWD OBJECTNAME MSS_WL
BOX
MANAGER_MSS_IN EXECUTETASKWD OBJECTVALUE WI_ID=${ITEM.EXTE
BOX RNALID}
MANAGER_MSS_IN EXECUTETASKWD OPERATION NAVIGATE_FORM_
BOX WD
MANAGER_MSS_IN EXECUTETASKWD OBJECTNAME MSS_WL
BOX_2
MANAGER_MSS_IN EXECUTETASKWD OBJECTVALUE WI_ID=${ITEM.EXTE
BOX_2 RNALID}
MANAGER_MSS_IN EXECUTETASKWD OPERATION NAVIGATE_FORM_
BOX_2 WD
5. Save your entries.

3.3.2.2.3 Define Task Properties


Procedure
1. Access the transaction using the following navigation option:
Transaction Code SPRO
IMG Path SAP Customizing Implementation Guide Cross-Application
Components Processes and Tools for Enterprise Applications
Inbox Define Tasks and Actions
2. Choose Define Task Properties on the Choose Activity menu popup.

© SAP AG Page 34 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

3. On executing this IMG step, an information message is displayed: Individual


entries cannot be put into the change request. Confirm this message with
Continue (Enter).
4. Create table entries as specified in the table below:
Application Workflow Task Task Compl Action Name
ID
MANAGER_MSS_INBOX TS33700021 EXECUTETASKWD
MANAGER_MSS_INBOX TS33700022 EXECUTETASKWD
MANAGER_MSS_INBOX TS17900100 EXECUTETASKWD
MANAGER_MSS_INBOX TS17900101 EXECUTETASKWD
MANAGER_MSS_INBOX_2 TS33700021 EXECUTETASKWD
MANAGER_MSS_INBOX_2 TS33700022 EXECUTETASKWD
MANAGER_MSS_INBOX_2 TS17900100 EXECUTETASKWD
MANAGER_MSS_INBOX_2 TS17900101 EXECUTETASKWD

5. If you have created your own workflow tasks for approval and processing please create
additional entries for applications MANAGER_MSS_INBOX / MANAGER_MSS_INBOX_2.
6. Save your entries.

3.3.2.2.4 Assign Actions to Tasks


1. Access the transaction using the following navigation option:
Transaction Code SPRO
IMG Path SAP Customizing Implementation Guide Cross-Application
Components Processes and Tools for Enterprise Applications
Inbox Define Tasks and Actions
2. Choose Assign Actions to Tasks on the Choose Activity menu popup.
3. On executing this IMG step, an information message is displayed: Individual
entries cannot be put into the change request. Confirm this message with
Continue (Enter).
4. Create table entries as specified in the table below:
Application Workflow Task Task Compl Action Name
ID
MANAGER_MSS_INBOX TS33700021 EXECUTETASKWD
MANAGER_MSS_INBOX TS33700022 EXECUTETASKWD
MANAGER_MSS_INBOX TS17900100 EXECUTETASKWD
MANAGER_MSS_INBOX TS17900101 EXECUTETASKWD
MANAGER_MSS_INBOX_2 TS33700021 EXECUTETASKWD
MANAGER_MSS_INBOX_2 TS33700022 EXECUTETASKWD
MANAGER_MSS_INBOX_2 TS17900100 EXECUTETASKWD
MANAGER_MSS_INBOX_2 TS17900101 EXECUTETASKWD

5. If you have created your own workflow tasks for approval and processing please create
additional entries for applications MANAGER_MSS_INBOX / MANAGER_MSS_INBOX_2.
6. Save your entries.

© SAP AG Page 35 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

3.3.2.3 Assign Task IDs to POWL Types


Procedure
1. Access the transaction using the following navigation option:
Transaction Code SM30
IMG Path SAP Easy Access Menu System Services Table
Maintenance Extended Table Maintenance
2. On the Maintain Table Views: Initial Screen screen enter the below value:
Field Value
Table/View IBO_V_WF_TA_P_TY
3. Choose Display to review the SAP delivered content.
4. Check if the below entries exists in the table:
Application POWL Type ID Workflow Task ID
MANAGER_MSS_INBOX MANAGER_MSS_INBOX_WI TS33700021
MANAGER_MSS_INBOX MANAGER_MSS_INBOX_WI TS33700022
MANAGER_MSS_INBOX MANAGER_MSS_INBOX_WI TS17900100
MANAGER_MSS_INBOX MANAGER_MSS_INBOX_WI TS17900101
MANAGER_MSS_INBOX_2 MANAGER_MSS_INBOX_WI TS33700021
MANAGER_MSS_INBOX_2 MANAGER_MSS_INBOX_WI TS33700022
MANAGER_MSS_INBOX_2 MANAGER_MSS_INBOX_WI TS17900100
MANAGER_MSS_INBOX_2 MANAGER_MSS_INBOX_WI TS17900101
5. If entries are missing please add these to the customer specific table. To do so access
the transaction using the following navigation option:
Transaction Code SPRO
IMG Path SAP Customizing Implementation Guide Cross-Application
Components Processes and Tools for Enterprise Applications
Inbox Assign Task IDs to POWL Types
6. On the Change View “Assignment of Task IDs to POWL Types”: Overview screen select
Assign additonal Task IDs in the Dialog Structure navigation.
7. Add only the missing entries from the table specified in step 4.
8. Or if you have created your own workflow tasks for approval and processing please also
create these entries for application MANAGER_MSS_INBOX /
MANAGER_MSS_INBOX_2 and POWL type MANAGER_MSS_INBOX_WI.
9. Save your entries.

3.3.2.4 PFCG Role Changes


Procedure
1. Access the transaction using the following navigation option:
Transaction Code PFCG
IMG Path SAP Customizing Implementation Guide Personnel
Management Manager Self-Service (Web Dynpro ABAP)
Manager Self-Service in SAP NetWeaver Business Client
Create Role for Manager Self-Service and Assign to Users

© SAP AG Page 36 of 37
SAP Best Practices HCM Base Services for Processes & Forms (F17): Configuration Guide

2. On the Role Maintenance screen, enter the RDS Manager composite role using the drop-
down search for example:
Field Name Entry Value
Role Y_NBPR_XX_MSS_PAOM_NWBC_M
3. Select Change to go to the Change Roles screen.
4. On the Change Roles screen, Menu tab, select ‘Other Node Details and locate the below
menu entry :
User Folder Sub- Sub-Folder2 Application Description of
Action Folder1 Change
Change Manager Work Inbox: Change
Self-Service Overview Execute Parameters
Process
5. Right- click on Inbox Execute Process to select Details and to see the technical settings.
6. On the Web Dynpro Application screen, enter the following:
Field Value
Web Dynpro Application ASR_PROCESS_EXECUTE_OVP
Application Configuration ASR_PROCESS_EXECUTE_OVP_CFG
7. The list of parameters stays unchanged:
Field Value
WDSUPPORTSFULLHEIGHT 2
8. Choose Continue (Enter).
9. To implement the method NAVIGATE_FORM_WD of the business object MSS_WL select
the method below Object-Based Navigation below other node details.
10. Choose Remove Method.
11. To add the new implementation method NAVIGATE_FORM_WD choose Insert Method.
12. Enter the values as specified in the table below:
Field Value
Obj. Type MSS_WL
Object Type Name MSS_WL
Method ID NAVIGATE_FORM_WD
Method Name Navigate form WD
13. Select OK (Enter) to proceed.
14. On the Parameter Assignment screen, create the following entries in the Parameter
Assignment table:
Field Value
WI_ID {WI_ID}
Portal_bo_alias SAP_ERP_HumanResources
15. Choose OK (Enter) and save your entries.

© SAP AG Page 37 of 37