HCM Base Services for Processes and Forms using Web Dynpro ABAP (F17)

Transcription

1 EHP6 for SAP ERP 6.0 January 2013 English HCM Base for Processes and Forms using Web Dynpro ABAP (F17) Building Block Configuration Guide SAP AG Dietmar-Hopp-Allee Walldorf Germany

2 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 for additional trademark information and notices. SAP AG Page 2 of 37

3 Icons Icon Meaning Caution Example Note Recommendation Syntax Typographic Conventions Type Style Example text Example text EXAMPLE TEXT Example text EXAMPLE TEXT Example text <Example text> Description 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. Emphasized words or phrases in body text, titles of graphics and tables. 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. 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. Keys on the keyboard, for example, function keys (such as F2) or the ENTER key. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. SAP AG Page 3 of 37

4 Content 1 Purpose Preparation Prerequisites Copying of SAP Standard Objects Configuration HR Administrative Activate Business Functions Configuration of HCM Processes and Forms Sample Processes Configuration of HCM Processes and Forms Process Configuration, Workflow Settings Configuration of HCM Processes and Forms Process Configuration, Process Objects Configuration of Forms/Processes Process Configuration, Set Up Processes Workflow: Task Type Maintenance Create Role for HR Administrator and Assign to Users Object-Based Navigation Assignment of PA Processes to the ESS Scenario Start Process Configuration for Employee POWL Inbox Customizing for Administrator Assignment of PA Processes to the MSS Scenario Start Process Configuration for Manager POWL Inbox Customizing for Manager SAP AG Page 4 of 37

5 HCM Base 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 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 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

6 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 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 Activate Business Functions Use As a prerequisite for configuring the application component HR Administrative, including HCM Processes and Forms, it is important to check that the relevant business functions have been activated. 1. Access the transaction using one of the following navigation options: SFW5 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. the status of the following business functions is Active : HCM_ASR_CI_1 (HCM, Administrative 01), HCM_ASR_CI_2 (HCM, Administrative 02), HCM_ASR_CI_3 (HCM, Administrative 03), HCM_ASR_CI_4 (HCM, Administrative 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

7 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 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 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. 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: IMG Menu SFW1 SAP Menu Tools ABAP Workbench Development Switch Framework Switch 3. On the Switch: Init.Screen screen, enter the switch HRASR_SFWS_UI_ENH_ 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 Cascading BC Sets Non-Cascading BC Sets Cross-Client BC Sets Select Only Logon Client Activate in the Login Client Do Not Activate SAP AG Page 7 of 37

8 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 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. 1. Access the transaction using one of the following navigation options: IMG Menu SWETYPV 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: Object Category Object Type Event Receiver Type CL CL_HRASR00_WF_PROCESS_OBJECT TRIGGERED WS 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

9 10. Repeat step 2 through 9 also for the following entry: Object Category Object Type Event Receiver Type CL CL_HRASR00_WF_PROCESS_OBJECT TRIGGERED WS 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 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 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. 1. Access the transaction using one of the following navigation options: IMG Menu HRASR00_WFC_WITHD_VP SAP Customizing Implementation Guide Personnel Management HR Administrative 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

10 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. 1. Access the transaction using one of the following navigation options: IMG Menu HRASR00_WFC_DRAFT SAP Customizing Implementation Guide Personnel Management HR Administrative 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 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

11 1. Access the transaction using one of the following navigation options: IMG Menu HRASR00_WFC_DRAFTERR SAP Customizing Implementation Guide Personnel Management HR Administrative 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 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. 1. Access the transaction using one of the following navigation options: IMG Menu HRASR00_WFC_EXCPTHND SAP Customizing Implementation Guide Personnel Management HR Administrative 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

12 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 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). 1. Ensure you are logged onto the development system you want to compare with client Access the transaction using the following navigation option: IMG Menu SPRO SAP Customizing Implementation Guide Personnel Management HR Administrative 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

13 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 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). 1. Ensure you are logged onto the development system you want to compare with client Access the transaction using the following navigation option: IMG Menu SPRO SAP Customizing Implementation Guide Personnel Management HR Administrative 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

14 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 s from the left-hand dialog structure. 6. On the Change View: Selection s : Overview screen, select the menu path Utilities > Adjustment. 7. In the Change View Selection s 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 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. 1. Access the transaction using one of the following navigation options: IMG Menu HRASR_DT SAP Customizing Implementation Guide Personnel Management HR Administrative 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

15 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 S_HR_PA_XX_CHWT_1_WD Name 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 HR_PA_XX_CHANGE_WORKINGTIME_1_WD Name 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

16 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 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. IMG Menu SPRO SAP Customizing Implementation Guide Personnel Management HR Administrative 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. or create table entries as specified in the table below: User Action Initiator Role Process Process Name Valid Manager HR_PA_XX_CHANGE_WO RKINGTIME_1_WD Change in Working Time (XX) Web Dynpro X 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

17 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. or create table entries as specified in the table below: User Action Initiator Role Process Process Name Valid Employee HR_PA_XX_CHANGE_WO RKINGTIME_1_WD Change in Working Time (XX) Web Dynpro X 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: IMG Menu SPRO SAP Customizing Implementation Guide Personnel Management HR Administrative 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: Name Proc.Grp. Description Entry 99MG Manager 13. Save your entry. 14. Access the transaction using the following navigation option: IMG Menu SPRO SAP Customizing Implementation Guide Personnel Management HR Administrative Configuration of Forms/Processes Process Configuration Set Up Processes Process Groups Group Processes for UI Control and Collision 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 : Overview screen. 16. On the Change View Group Processes for UI Control and Collision : Overview screen, create the following entry: Name Proc.Grp. Description Process Process Name Entry 99MG Manager HR_PA_XX_CHANGE_WORKINGTIME_1_WD Change in Working Time (XX) Web Dynpro Start Date 01/01/1800 End Date 12/31/9999 SAP AG Page 17 of 37

18 Name Relev.UI Entry 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 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. IMG Menu SPRO SAP Customizing Implementation Guide Personnel Management HR Administrative 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 Action Object Type Object type text Used in ASR Appl. Type Create C Job X Personnel Development Create NB Requisition Recruitment Create O Organizational unit X Personnel Development 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. or create table entries for the selected object as specified in the table below: User Action Object Type Object Type Text Agent Role Name Group of Organizational Views Is Skip Visible? C Job HRASRA HR Administrator ASR_JOB_SEARC 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

19 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. or create table entries for the selected object as specified in the table below: User Action Object Type Object Type Text Agent Role Name Group of Organizatio nal Views Is Skip Visible? O Organizational unit HRASRA HR Administrator ASR_ORG_ SEARCH O Organizational unit HRASRB Manager MSS_ASR_ 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. or create table entries for the selected object as specified in the table below: User Action Object Type Object Type Text Agent Role Name Group of Organizational Views Is Skip Visible? 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. or create table entries for the selected object as specified in the table below: User Action Object Type Object Type Text Agent Role Name Group of Organizational Views Is Skip Visible? S Position HRASRA HR Administrator S Position HRASRB MSS_ASR_P OS_SEL ASR_POS_SEA RCH MSS_ASR_PO 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 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. PFTC 2. On the Task Maintain screen, enter the following values: SAP AG Page 19 of 37

20 Name Task type Entry Standard task Task 8-digit numeric identifier of the workflow task: 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 Approve Form Standard Task Form is edited again by Author Workflow Template Save Form with Error Handling Standard Task Process PD Form Standard Task Approve PD Form Standard Task PD Form is Edited Again by Author Standard Task Draft for PD Process Start Standard Task Forwarded because of Errors in PD Form 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 rapiddeployment solution. PFCG roles are delivered with the SAP Best Practices add-on, as described in the Quick Guide. Composite Role SAP_NBPR_XX_HRADM2_PAOM_NWBC_S Description 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

21 1. Access the transaction using one of the following navigation options: PFCG SAP Customizing Implementation Guide HR Administrative 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: Name Entry 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: Name from role to role Entry SAP_ASR_HRADMIN_HCM_CI_3 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: Name Description Long Text Entry HRADMIN NWBC Role (HCM RDS PA&OM) 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: NWBC role user system X SAP AG Page 21 of 37

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

23 User Action Change Change Delete Change Delete Folder Folder Sub- Folder1 Organizational -Related Organizational -Related Organizational -Related Employee Information Employee Information Employee Information Employee Information Employee Information Employee Information Employee Information Employee Information Employee Information Reports Sub-Folder2 Transaction Web Dynpro Application S_EH5_ ASR_PROCES S_EXECUTE_F PM ASR_SRCH_P D_PROCESS ASR_PROFILE S_SHOW ASR_PROCES SES_DISPLAY ASR_PROCES S_EXECUTE_F PM ASR_LAUNCH PAD ASR_KEYWOR D_SEARCH ASR_PERSON NEL_FILE ASR_PROCES S_EXECUTE_F PM ASR_PROCES S_SELECT HRASR_CALL_ TX_ATTCH Text / Characteristic Start Organizational Process / Invisible Search Organizational Process / Visible Employee Information Employee Data / Visible Display Processes / Visible Start Processes / Invisible Display Employee Reports / Visible Keyword Search / Visible Process Personnel File / Invisible Process Employee Data / Visible Reports Inbox Execute Process / Invisible/ OBN Target Inbox Select Processes/ Invisible/ OBN Target OBN Display Attachments/ Invisible / OBN Target ASR_FORM_DI OBN Display SAP AG Page 23 of 37

24 User Action Folder Sub- Folder1 Sub-Folder2 Transaction Web Dynpro Application Text / Characteristic SPLAY Form / Invisible / OBN Target ASR_FORM_DI SPLAY OBN Display Form Manager/ Invisible / OBN Target 13. Save your entries. HRASR_EXEC _TX_PASR_W OBN Start of Transaction PASR/ Invisible / OBN Target Object-Based Navigation 1. Access the transaction using one of the following navigation options: LPD_CUST SAP Customizing Implementation Guide Personnel Management HR Administrative 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 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 Start Process Configuration for Employee PFCG SAP Customizing Implementation Guide Personnel Management Employee Self-Service (Web Dynpro ABAP) General Settings ESS Menu for Menu for SAP NetWeaver Business Client for HTML Set up PFCG Menu* SAP AG Page 24 of 37

25 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: Name Role Entry 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 Action Folder Sub-Folder1 Sub-Folder2 Application Description of Change Change Working Time Employment Percentage Request a Change in Employment Percentage Change Parameters 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: Web Dynpro Application Application Configuration ASR_PROCESS_EXECUTE_OVP ASR_PROCESS_EXECUTE_OVP_CFG 7. On the list of parameters, correct the following entries: PROCESS INITIATOR_ROLE HR_PA_XX_CHANGE_WORKINGTIME_1_WD HRASRD 8. Save your entries. 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 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 Defining a new method for the BOR Object SWO1 SAP Menu Tools Business Workflow Development Definition tools Application Integration Business Object Builder SAP AG Page 25 of 37

26 2. On the Business Object Builder: Initial Screen, enter the following: 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 promptcreate with function moduleas template? 7. On the Change Object Type HRADMIN_WL screen, enter the following values: Method Name Description NAVIGATE_FORM_WD NAVIGATE_FORM_WD Navigate form WD 8. On the tabs General, Result type and ABAP, keep the standard entries: General tab: Dialog Synchronous X X Result parameter Instance-independent Result type tab: ABAP Dictionary X Reference table Reference field Search Help Object type Multiline ABAP tab: 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

27 Define Tasks and Actions Create or Change Actions SPRO 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 Define Action Properties SPRO 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 Proptery of Action 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