HCM Base Services for Processes and Forms using Interactive Forms (F11)

Transcription

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

2 HCM Base for Processes & Forms using IF (F11): 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 for additional trademark information and notices. SAP AG Page 2 of 25

3 HCM Base for Processes & Forms using IF (F11): Configuration Guide Icons Icon Meaning Caution Example Note Recommendation Syntax Typographic Conventions Type Style Example text Example text EAMPLE TET Example text EAMPLE TET 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 25

4 HCM Base for Processes & Forms using IF (F11): Configuration Guide Content 1 Purpose Preparation Prerequisites Copying of SAP Standard Objects Configuration 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 and Assign to Users Object-Based Navigation SAP AG Page 4 of 25

5 HCM Base for Processes & Forms using IF (F11): Configuration Guide HCM Base for Processes and Forms using Interactive Forms: 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. 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 (transaction SWU3 - Automatic Workflow Customizing) and the Adobe document service. 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. 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. SAP AG Page 5 of 25

6 HCM Base for Processes & Forms using IF (F11): Configuration Guide For details on the roles configured to support this building block, see the Consultant and End User Security Guide. 3.1 Administrative Activate Business Functions Use As a prerequisite for configuring the application component 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 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, for example, 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_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. For further details on the technical prerequisites for HCM Processes and Forms, refer to the Quick Guide for this SAP 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. SAP AG Page 6 of 25

7 HCM Base for Processes & Forms using IF (F11): Configuration Guide 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. Such steps are not covered in this document as they do not form part of the scope of this rapid-deployment solution Perform Client Copy According to Piece List To use the sample processes provided with HCM Processes and Forms, it is necessary to copy the objects in the object list ASR_PROCCONTENT_VP from client 000 to 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 transport request created 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 to which the client copy should be made. 2. Access the transaction using one of the following navigation options: SCC1 Personnel Management Administrative Configuration of Forms/Processes Sample Process for HCM Processes and Forms Perform Client Copy According to Piece List 3. On the Copy by Transport Request screen, enter the following settings: We recommend running this step in simulation mode prior to execution. Field Name Source Client for Client Copy Transport Request Including Request Subtasks Test Run Entry Value Use the dropdown search to select 000, <descriptive name of appropriate client, e.g. RDFCLNT000> ASR_PROCCONTENT_VP 4. Select the Start Immediately button. 5. the system messageprogram ran successfully to ensure that the step can be completed without errors. If not, further analysis will be required before proceeding with the next step. 6. Once the program can be run successfully in simulation mode, deselect the Test Run checkbox and repeat steps 3-4 above. 7. In the Copy Confirmation dialog box, select YES to confirm the messagecopy clientspecific data from 000 to nnn. 8. the system messageprogram ran successfully to ensure that the step was completed without errors. 9. From the navigation menu, select Goto Log Display to open the Client Copy/Transport Log Analysis screen. SAP AG Page 7 of 25

8 HCM Base for Processes & Forms using IF (F11): Configuration Guide 10. Select the client copy run and select the Choose button; then use the Details and File Log utilities to analyze and validate the client copy run Perform Comparison Run Using Object List In this IMG activity, you start the Customizing Cross-System Viewer to compare the Customizing objects within object lists or transport requests in two logical systems. In this case, you have to compare the objects in the Customizing object list ASR_PROCCONTENT_VP that you copied from client 000 to the designated customer client, as described in the previous section. This activity is a manual step, even if automated content activation has been run. To run this comparison and make any necessary adjustments, RFC destinations must be created linking the configuration client with client 000. See the Quick Guide for further details. The authorizations required to perform this step are described in the Consultant and End User Security Guide. 1. Log onto the development system from which you want to run the comparison. 2. Access the transaction using one of the following navigation options: SCU0 Personnel Management Administrative Configuration of Forms/Processes Sample Process for HCM Processes and Forms Perform Comparison Run Using Object List 3. On the Customizing Cross-System Viewer screen, create a new comparison run based on the Customizing piece list/transport, as follows: Field Name Customizing piece list/ transport Entry Value 4. Select the Create icon to display the Selection by: Transport Request screen. 5. In the Selection by: Transport Request dialog box, enter the piece list item you would like to compare: Field Name Piece List/Transport Entry Value ASR_PROCCONTENT_VP 6. Select Continue (Enter) to proceed to the Selection by: Transport Request screen and proceed as indicated below: Field Name Comparison run ID Description Client specific Cross-client Entry Value N/A. A Comparison run ID is automatically generated by the system and entered in this field. Optional; a free-text description can be entered here, if required; otherwise leave blank. R/3 connection RFC connection for your comparison system, for example, RDFCLNT Select Total comparison to generate a comparison list, which is displayed on the Customizing Cross-System Viewer: Change mode screen. SAP AG Page 8 of 25

9 HCM Base for Processes & Forms using IF (F11): Configuration Guide 8. Review the log to check that there are no differences between the logon and comparison clients. The entries in the two systems should be identical. If differences exist, they should be investigated and adjusted accordingly prior to continuing with subsequent activities. Comparisons and adjustments can be executed multiple times, as required, in order to achieve synchronization with the comparison client. Refer to the IMG documentation for further details Activate Event Coupling for Workflow Template of Sample Processes In this IMG 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. 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: ASR00_WFC_PROC_VP Personnel Management Administrative Configuration of Forms/Processes Sample Process for HCM Processes and Forms Activate Event Coupling for Workflow Template of Sample Processes 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 to create a transport request, as required. 7. Repeat step 4 until all statuses are set to Activated in the Activate/deactivate column 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 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. SAP AG Page 9 of 25

10 HCM Base for Processes & Forms using IF (F11): Configuration Guide Workflow Settings (Process Withdrawal) 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 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: ASR00_WFC_WITHD_VP Personnel Management 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 Workflow Settings (Draft for Process Start) 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: ASR00_WFC_DRAFT Personnel Management 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. SAP AG Page 10 of 25

11 HCM Base for Processes & Forms using IF (F11): Configuration Guide 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) 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. 1. Access the transaction using one of the following navigation options: ASR00_WFC_DRAFTERR Personnel Management 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 the Create request button to create a transport request, as required Workflow Settings (Exception Handling) 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 in your system for validation purposes only. SAP AG Page 11 of 25

12 HCM Base for Processes & Forms using IF (F11): Configuration Guide 1. Access the transaction using one of the following navigation options: ASR00_WFC_ECPTHND Personnel Management 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 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 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: SPRO Personnel Management 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. SAP AG Page 12 of 25

13 HCM Base for Processes & Forms using IF (F11): Configuration Guide 4. In the Enter R/3 Connection pop-up window, use the dropdown list to select the client to which the case types should 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_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, refer to the IMG documentation to make changes, as required. 5. Once the case types have been compared, make a further comparison 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 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, refer to the IMG documentation to make changes, as required. 8. Repeat steps 5-7 for case types H_PO and H_SO Process Objects, Profile for Case Search 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: SPRO Personnel Management Administrative Configuration of Forms/Processes Process Configuration Technical Settings Set up Process Object Copy Profile for Case Search SAP AG Page 13 of 25

14 HCM Base for Processes & Forms using IF (F11): Configuration Guide 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. If any differences do exist between the current logon client and the comparison client, refer to the IMG 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, refer to the IMG documentation to synchronize them as required. 8. Repeat steps 5-7 for profiles ASR_POBJ and ASR_SOBJ Configuration of Forms/Processes 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: ASR_DT Personnel Management 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). SAP AG Page 14 of 25

15 HCM Base for Processes & Forms using IF (F11): Configuration Guide 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). 7. From the list displayed, select the following forms that were defined as part of the respective roles ASRA (), ASRB (Manager), and ASRD () for this rapid-deployment solution: Form Scenario S_PA CHANGE_SAL1_ADMIN S_PA CHANGE_SAL1_MANAGER S_PA CHANGE_SAL2_ADMIN S_PA CHANGE_SAL2_MANAGER S PA CHWT_1 S PA TRANSFER_3 S PD_CHANGE_JOB_ATTRIBUTES S PD_CHANGE_JOB_NAME S PD_CHANGE_ORG_ATTRIBUTES S PD_CHANGE_ORG_UNIT_NAME S PD_CHANGE_POSITION_NAME S PD_CHANGE_POS_ATTRIBUTES S PD_CREATE_ORGANIZATION_UNIT S PD_CREATE_POSITION S PD_DELIMIT_POS_ASSIGNMENT Name Change Annual Salary Admin Change Annual Salary Manager Change Payscale admin Change Payscale Manager Change of Working Time () Transfer with Org. Management Change Job attributes Change Job Name Change Business attributes of Organizational Unit Change Organization Unit Name Change Position Name Change Business attributes of Position Create Organization Unit Create Position Delimit Assignment of Position to Org Unit 8. Select the Reconcile (Import from Remote System) button. 9. The Reconcile Form Scenarios? Dialog box is displayed with the system messageare 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. It is now necessary to repeat reconciliations for the process levels of the relevant scenarios. On the Design Time for Processes and Forms screen, use the dropdown list 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). SAP AG Page 15 of 25

16 HCM Base for Processes & Forms using IF (F11): Configuration Guide 17. The following processes, as defined by the scope of the rapid-deployment solution, must be reconciled with client 000 (for example, RDFCLNT000): Process _PA CHANGE_SALARY_1 _PA CHANGE_SALARY_2 _PA CHANGE_WORKINGTIME_1 _PA TRANSFER_3 _PD_CHANGE_JOB_ATTRIBUTES _PD_CHANGE_JOB_NAME _PD_CHANGE_ORG_UNIT_ATTRIBUTES _PD_CHANGE_ORG_UNIT_NAME _PD_CHANGE_POSITION_NAME _PD_CHANGE_POS_ATTRIBUTES _PD_CREATE_ORGANIZATION_UNIT _PD_CREATE_POSITION _PD_DELIMIT_POS_ASSIGNMENT Name Salary Change 1 () Salary Change 2 () Change in Working Time () Transfer with Org. Management Change Job's Business Attributes Change Job Name and Description Change Org Unit's Attributes Change Org. Unit Name and Description Change Position Name and Description Change Position's Business Attributes Create Organization Unit Create Position Delimit Assignment of Position to Org unit 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 messageare 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 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 The following IMG steps will enable specific forms for a particular end-user role; in this case, certain forms will be enabled for, Manager, and/or, based on their technical roles within HCM Processes and Forms. The initiator roles available within the context of this rapid-deployment solution are: ASRA ( ), ASRB (Manager), and ASRD (). SAP AG Page 16 of 25

17 HCM Base for Processes & Forms using IF (F11): Configuration Guide 1. Access the transaction using the following navigation option: SPRO Personnel Management 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 ASRA ( ) initiator role and select Continue (Enter). 3. In the New Design Time for Processes and Forms Available dialog box, select choose 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 _PA CHANGE_SAL ARY_1 Salary Change 1 () _PA CHANGE_SAL ARY_2 Salary Change 2 () _PA CHANGE_WO RKINGTIME_1 Change in Working Time () _PA TRANSFER_3 Transfer with Org. Management _PD_CHANGE_JOB_A TTRIBUTES Change Job's Business Attributes _PD_CHANGE_JOB_N AME Change Job Name and Description _PD_CHANGE_ORG_U NIT_ATTRIBUTES Change Org Unit's Attributes _PD_CHANGE_ORG_U NIT_NAME Change Org. Unit Name and Description _PD_CHANGE_POSITI ON_NAME Change Position Name and Description _PD_CHANGE_POS_A TTRIBUTES Change Position's Business Attributes _PD_CREATE_ORGANI ZATION_UNIT Create Organization Unit _PD_CREATE_POSITI ON Create Position _PD_DELIMIT_POS_AS SIGNMENT Delimit Assignment of Position to Org unit SAP AG Page 17 of 25

18 HCM Base for Processes & Forms using IF (F11): Configuration Guide 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 and repeat step 1 above. 7. In the Determine Work Area: Entry dialog box, use the dropdown search to choose the ASRB (Manager) initiator role and select Continue (Enter). 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 Manager _PA CHANGE_SAL ARY_1 Salary Change 1 () Manager _PA TRANSFER_3 Transfer with Org. Management Manager _PD_CHANGE_ORG_U NIT_ATTRIBUTES Manager _PD_CHANGE_ORG_U NIT_NAME Manager _PD_CHANGE_POSITI ON_NAME Manager _PD_CHANGE_POS_A TTRIBUTES Manager _PD_CREATE_ORGANI ZATION_UNIT Manager _PD_CREATE_POSITI ON Manager _PD_DELIMIT_POS_AS SIGNMENT Create Manager _PA CHANGE_WO RKINGTIME_1 Change Org Unit's Attributes Change Position Name and Description Change Position Name and Description Change Position's Business Attributes Create Organization Unit Create Position Delimit Assignment of Position to Org unit Change in Working Time () 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. Return to the IMG and repeat step 1 above. 12. In the Determine Work Area: Entry dialog box, use the dropdown search to choose the ASRD () initiator role and select Continue (Enter). 13. 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. 14. or create table entries as specified in the table below: SAP AG Page 18 of 25

19 HCM Base for Processes & Forms using IF (F11): Configuration Guide User Action Initiator Role Process Process Name Valid _PA CHANGE_WO RKINGTIME_1 Change in Working Time () Validity assignments for any processes other than those above should be deselected as they are not relevant for this rapid-deployment solution. 15. Save your entries Set Up Processes, Properties of Object Types 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. 1. Access the transaction using the following navigation option: SPRO SAP Customizing Implementation Guide Personnel Management 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 Personnel Development Create NB Requisition Recruitment Create O Organizational unit Personnel Development Create P Person Personnel Administration Create S Position 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 ASRA Administrat or ASR_JOB_SEA RCH 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. SAP AG Page 19 of 25

20 HCM Base for Processes & Forms using IF (F11): Configuration Guide 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. 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 Organizational Views Is Skip Visible? O Organizational unit ASRA Administrat or ASR_ORG_SE ARCH O Organizational unit ASRB Manager MSS_ASR_OR G_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 ASRB Manager MSS_ASR_TM V_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 ASRA Administrat or ASR_POS_SEA RCH S Position ASRB Manager MSS_ASR_POS_S EL 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. SAP AG Page 20 of 25

21 HCM Base for Processes & Forms using IF (F11): Configuration Guide 1. Access the transaction using the following navigation option: PFTC 2. On the Task Maintain screen, enter the following values: Field Name Task type Entry Value 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 and Assign to Users The following steps describe the activities required to configure a role for an 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 ADM_PAOM_NWBC_S Description ADMIN NWBC Role (HCM RDS PA&OM) Single Role SAP_NBPR ADM_PAOM-S1 : NWBC role SAP AG Page 21 of 25

22 HCM Base for Processes & Forms using IF (F11): Configuration Guide The manual steps required to set up the roles (if the SAP Best Practices add-on is not installed) are as follows: 1. Access the transaction using one of the following navigation options: PFCG Administrative in SAP NetWeaver Business Client Assign Role to Users 2. On the Role Maintenance screen, create a new role by copying the standard SAP role as follows: Field Name Role Entry Value Use the dropdown search to locate the standard SAP composite role ESS role SAP_ASR_ADMIN_HCM_CI_3 3. Select Copy Role and specify a name in your namespace e.g. as follows: Field Name from role to role Entry Value SAP_ASR_ADMIN_HCM_CI_3 Y_NBPR ADM_PAOM_NWBC_S 4. Select Copy All. 5. A system message confirmscomposite 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 theenter target for single roles, enter names for the new single roles in your namespace, for example, as follows: Old role New Role SAP_ASR_ADMIN_SR_HCM_CI_3 Y_NBPR ADM_PAOM-S1 8. A system message confirmscomposite SAP_NBPR ADM_PAOM_NWBC_S role created. On the Role Maintenance screen, select Change to go to the Change Roles screen. 9. On the Description tab, enter the following: Field Name Description Long Text Entry Value ADMIN NWBC Role (HCM RDS PA&OM) This role is a copy of the SAP standard, composite role SAP_ASR_ADMIN_HCM_CI_3, together with the corresponding single role SAP_ASR_ADMIN_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 Interactive Forms. 10. On the Roles tab, the following single role should be specified as Active: Role Name Target Sys Active Y_NBPR ADM_PAOM-S1 : NWBC role user system SAP AG Page 22 of 25

23 HCM Base for Processes & Forms using IF (F11): Configuration Guide 11. On the Change Roles screen, Menu tab, select Other Node Details and check or change the following settings: User Action Folder Administ rator Sub- Folder1 Sub- Folder2 Transaction Web Dynpro Application Home Home Home IBO_WDA_INB O Change Change Text / Characteristic / Single Top Level Home / Default Page / Visible Home SWNWIE WF Notification: Edit Work Item / Invisible Work Overview Work Overview -Related -Related -Related -Related -Related -Related -Related -Related Organizati onal- Related Organizati onal- S_EH5_ ASR_PA_PD_P ROCESSES_DI SPLAY ASR_PROCES SES_DISPLAY ASR_PROCES S_EECUTE_F PM ASR_MASS_ST ART_PROCES S ASR_PROCES SES_DISPLAY ASR_PROCES S_EECUTE_F PM ASR_PA_PD_P ROCESSES_DI Work Overview Process Overview/ Default Page / Visible - Related Open Processes / Default Page Start Process for / Visible Start Process for Multiple s / Invisible Search Processes / Visible Process Data / Visible Execute Hiring / Invisible Organizational- Related Open Organizational SAP AG Page 23 of 25

24 HCM Base for Processes & Forms using IF (F11): Configuration Guide User Action Change Change Delete Folder Folder Sub- Folder1 Related Organizati onal- Related Organizati onal- Related Organizati onal- Related Informatio n Informatio n Informatio n Informatio n Informatio n Informatio n Informatio n Informatio n Informatio n Reports Sub- Folder2 Transaction S_EH5_ Web Dynpro Application SPLAY ASR_PROCES S_EECUTE_F PM ASR_SRCH_P D_PROCESS ASR_PROFILE S_SHOW ASR_PROCES SES_DISPLAY ASR_PROCES S_EECUTE_F PM ASR_LAUNCH PAD ASR_KEYWOR D_SEARCH ASR_PERSON NEL_FILE ASR_PROCES S_EECUTE_F PM Text / Characteristic Process / Visible Start Organizational Process / Visible Search Organizational Process / Visible Information Data / Visible Display Processes / Visible Start Processes / Visible Display Reports / Invisible Keyword Search / Visible Process Personnel File / Invisible Process Data / Visible Reports Inbox Execute Process / Invisible/ OBN Target ASR_PROCES Inbox Select SAP AG Page 24 of 25

25 HCM Base for Processes & Forms using IF (F11): Configuration Guide User Action Folder Sub- Folder1 Sub- Folder2 Transaction Web Dynpro Application Text / Characteristic S_SELECT Processes/ Invisible/ OBN Target ASR_CALL_ T_ATTCH OBN Display Attachments/ Invisible / OBN Target ASR_FORM_DI SPLAY OBN Display Form / Invisible / OBN Target ASR_FORM_DI SPLAY OBN Display Form Manager/ Invisible / OBN Target ASR_EEC _T_PASR_W OBN Start of Transaction PASR/ Invisible / OBN Target 12. Save your entries Object-Based Navigation 1. Access the transaction using one of the following navigation options: IMG Path LPD_CUST Personnel Management Administrative in SAP NetWeaver Business Client Adjust Object-Based Navigation of Role 2. On the Overview of Launchpads screen, check that the following settings exist: User Action Role Instance Description Repository ADM_NAV OBN OBN for Admin SAP AG Page 25 of 25