Quick Guide eRec en XX

EhP5 for SAP ERP 6.0 April 2012 English

Quick Guide to Implementing the SAP E-Recruiting rapid-deployment solution

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany


© SAP AG Page 2 of 84

Copyright

© 2011 SAP AG. 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.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, 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.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. 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.



Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options. Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.



Content 1 Quick Guide to Implementing the SAP ERP Rapid-Deployment Solution for the HCM Accelerated E-Recruiting ....................................................................................................... 8 2 Solution Overview .......................................................................................................... 8 3 SAP System Requirements (Administrator) ..................................................................... 8

3.1 SAP Software Component Installation Check ........................................................ 9 3.1.1 SAP ERP Core Components 6.0 ...................................................................... 9 3.1.2 SAP NetWeaver Enterprise Portal Components .............................................. 10 3.1.3 SAP NetWeaver XI/PI ..................................................................................... 11 3.1.4 SAP Solution Manager ................................................................................... 11

3.2 SAP Enterprise Extensions Sets and Enterprise Business Functions .................. 11 3.3 SAP Notes and Messages .................................................................................. 13

4 System Preparation for Implementation (Administrator/Consultant) ............................... 14 4.1 Installation of the SAP Best Practices Add-On .................................................... 14 4.2 Installation of SAP Best Practices Solution Builder .............................................. 15 4.3 General Client Settings ....................................................................................... 15

4.3.1 Creating User for Activation of SAP Best Practices Content ............................ 15 4.3.2 Deselecting Activation Links in BC Sets .......................................................... 16 4.3.3 Maximum Work Process Run Time ................................................................. 17 4.3.4 SAP Scripting ................................................................................................. 17 4.3.5 Set Default Timeout for http and https Services .............................................. 18

4.4 Prepare System User for Content Activation ....................................................... 19 4.4.1 Activation Language ....................................................................................... 19 4.4.2 User Settings for Activation ............................................................................. 19 4.4.3 Deactivate Info Dialog Box on Dynpro Size Check .......................................... 19 4.4.4 SAP Software Change Registration (SSCR): Developer Key ........................... 19 4.4.5 Unicode Settings ............................................................................................ 20 4.4.6 Allow GUI Scripting......................................................................................... 20

5 Implementation of RDS Business Content .................................................................... 20 5.1 Selecting the SAP Solution Manager Template ................................................... 20 5.2 Adjust the Process Scope in SAP Solution Manager ........................................... 21 5.3 Automated Implementation Using SAP Best Practices Solution Builder ............... 22

5.3.1 Getting the Business Content for Activation .................................................... 22 5.3.2 Getting the Solution Scope File ....................................................................... 22 5.3.3 Getting the Installation Data Files ................................................................... 22 5.3.4 Creating a Folder for the SAP E-Recruiting rapid-deployment solution Activation 22 5.3.5 Import Solution Scope File .............................................................................. 23 5.3.6 Upload Installation Data .................................................................................. 23

5.4 Pre-Activation Activities ...................................................................................... 24 5.4.1 Check System Status ..................................................................................... 24 5.4.2 Configuration of RFC Connections .................................................................. 24 5.4.3 Set up the RFC Connection between HR and E-Recruiting ............................. 24 5.4.4 Local Administration in System Landscape Directory ...................................... 29 5.4.5 Integration Engine Configuration to PI............................................................. 30 5.4.6 Create Configuration Objects in SAP Integration Directory (PI) ....................... 31

5.4.6.1 Start Integration Directory ........................................................................... 31



5.4.6.2 Assign Business System for eRec-System ................................................. 31 5.4.6.3 Assign Business System for ERP HR-System ............................................ 31 5.4.6.4 Add Interfaces to Business System for e-Rec-System ................................ 32 5.4.6.5 Add Interfaces to Business System for ERP HR-System ............................. 32 5.4.6.6 Create XI Receiver Channel for Business System EREC ............................ 33 5.4.6.7 Create XI Receiver Channel for Business System ERP HR ........................ 33 5.4.6.8 Create Configuration Scenario PersonnelHiringCreateRequestProcedure ... 34

5.4.7 Client-Copy of Customizing tables .................................................................. 35 5.4.8 Set System Parameters for SAP E-Recruiting and SAP ERP .......................... 36 5.4.9 BadI Implementations ..................................................................................... 40 5.4.10 Set Up ALE Connection (separated architecture) ............................................ 41 5.4.11 Set Up Communication Interface .................................................................... 45 5.4.12 Preparing Roles and Users ............................................................................. 46

5.4.12.1 Create User Profiles ............................................................................... 46 5.4.12.2 Define and setup profiles for the following roles in HR ECC .................... 47 5.4.12.3 Create Special Users ............................................................................. 47

5.4.13 Verify SAP Business Partner Integration ......................................................... 52 5.4.14 Set Up Access to Documents ......................................................................... 53 5.4.15 Maintain Procedure in Services ...................................................................... 53

5.4.15.1 Set procedure to Required with Logon Data ........................................... 54 5.4.15.2 Set procedure to Standard ..................................................................... 55

5.4.16 Initialize KPro Directory Structure for SAP E-Recruiting .................................. 55 5.4.17 Clean Up Change Pointers ............................................................................. 55 5.4.18 Check the RFC connection to TREX (Text Retrieval and Information Extraction) 56 5.4.19 Workflow Customizing .................................................................................... 56

5.4.19.1 Automatic Workflow Customizing ........................................................... 56 5.4.19.2 Activate Workflow Services .................................................................... 59 5.4.19.3 Maintain WebFlow Service Handler ........................................................ 60 5.4.19.4 Activate Event Linkage for SAP E-Recruiting Workflows ......................... 60

5.4.20 SAP Search Engine Service Settings .............................................................. 61 5.4.20.1 Set Up Indices of SES Business Object .................................................. 61 5.4.20.2 Run Reports for Search Initialization....................................................... 62 5.4.20.3 Performing the First Full Index Run ........................................................ 62

5.4.20.3.1 Running the Full Index in the Foreground ........................................ 62 5.4.20.3.2 Running the Full Index in the Background ........................................ 63

5.4.20.4 Schedule Background Process for Periodic Services .............................. 64 5.4.20.5 SES Change Pointer .............................................................................. 65

5.5 Activating a Solution ........................................................................................... 65 5.6 Post-Activation Activities ..................................................................................... 69

5.6.1 SAP ERP Central Component (ECC) Integration ............................................ 69 5.6.1.1 Set Up Integration with SAP Organizational Management ........................... 69 5.6.1.2 Set Up Aliases in SAP Portal ...................................................................... 70

5.6.2 Client-Copy of Processes and Forms Customizing tables in HR system .......... 71 5.6.2.1 Required Customizing in HR System .......................................................... 73

5.6.2.1.1 RDS Specific Configuration in HR System ......................................... 73 5.6.2.1.1.1 Maintain Variables for RFC Destinations in the Workplace ...... 74 5.6.2.1.1.2 Assign E-Recruiting System Name .......................................... 74



5.6.2.1.1.3 Disable Recruitment Requisition Request (HR_MSSRCF_REQUISITION) ...................................................................... 75 5.6.2.1.1.4 Continue Without Design Time ................................................ 75 5.6.2.1.1.5 Define Processes .................................................................... 76 5.6.2.1.1.6 Configure Process Start .......................................................... 77 5.6.2.1.1.7 Specify Valid Processes for Start Application .......................... 78 5.6.2.1.1.8 Continue With Design Time ..................................................... 78 5.6.2.1.1.9 Assign Process Groups for SAP E-Recruiting rapid-deployment solution 79 5.6.2.1.1.10 Maintenance of Hire Process (PERS_HIRE_10) ...................... 79 5.6.2.1.1.11 Check Consistency of Processes ............................................ 80

5.6.2.1.2 Tips for known issues ........................................................................ 81 5.6.2.1.2.1 ADS ........................................................................................ 81 5.6.2.1.2.2 Data for Country Grouping and Working Hours........................ 81 5.6.2.1.2.3 Activate Services in SICF ........................................................ 81 5.6.2.1.2.4 Automate Work Item Distribution for Hire Process ................... 82

5.7 Error Handling: Installation Errors during activation ............................................. 83 5.7.1 Error Occurs During Activation of Automated Task ......................................... 83

Quick Guide to Implementing SAP E-Recruiting rapid-deployment solution


1 Quick Guide to Implementing the SAP ERP Rapid-Deployment Solution for the HCM Accelerated E-Recruiting

This Quick Guide provides step-by-step information you need to implement the SAP E-Recruiting rapid-deployment solutionusing the SAP Best Practices Solution Builder. Before proceeding with this document you must have

Defined the scope relevant for you Finalized technical prerequisites Have the required resources available (see involved roles)

This document does not provide a general overview and explanations of SAP Best Practices. For more information about content and positioning, see the SAP Best Practice documentation CD/DVD. This document is intended for

System administrators and basis consultants: System set up & preparation incl. troubleshooting

Activation consultants (can be also basis consultants): Activation of business content/scenarios

Business consultants: o Evaluate business content/scenarios incl. troubleshooting o FAQ and further information for extended usage of the package

2 Solution Overview SAP E-Recruiting rapid-deployment solution

Is based on SAP ERP 6.0 with Enhancement Package 5 Is based on SAP NetWeaver Enterprise Portal 7.0 Enhancement Package 2 Provides an accelerated deployment of the required configuration settings Provides managers and employees with an easy-to-use application for self-services

3 SAP System Requirements (Administrator) This chapter summarizes the prerequisites that are assumed to be delivered by the customer, i.e. in a phase preceding the actual implementation project.

Note that the setup of the system landscape is not part of the rapid-deployment solution delivery scope.

The customer will need to provide the system landscape, i.e. install the required software components, to enable the project team to implement and configure the scope of the SAP ERP Rapid-Deployment Solution for the HCM Accelerated E-Recruiting. During this phase SAP provides advice on aspects of the system landscape and the components required. In addition to the following information, the SAP rapid-deployment solution’s specific implementation methodology provides an installation related checklist covering additional aspects. Prior to installing and activating the SAP ERP Rapid-Deployment Solution for the HCM Accelerated E-Recruiting the target SAP Application Server (AS) must be installed with the Support Package Stack (SPS), specified in this section and the SAP Notes as specified in detail in section 3.7 SAP Notes and Messages in this guide.



3.1 SAP Software Component Installation Check Before the SAP E-Recruiting rapid-deployment solution content implementation activities can be executed, the SAP project team performs a check of the software installation based on the requirements provided in the following chapters of this guide. Based on the result the project team advises the customer on any missing steps to be performed. The deliverables of SAP E-Recruiting rapid-deployment solution were developed and tested in a system landscape with specific SPS (Support Package Stack) levels. If the SPS level in your system is different, there may be errors during the activation. You may be able to perform the activation activities manually using the configuration guides, but errors may still occur.

Make sure that your system meets the minimum SPS level requirements. In case your system has an exceptional SPS level compared to the rapid-deployment solution requirements, issues might occur. If you need a higher SPS level in your system, for example because of additional functionality, first import and activate the rapid-deployment solution SPS levels as mentioned below, then upgrade your system to the current SPS level.

The support package levels relevant for the rapid-deployment solution are listed together with the required components in the next sections. The rapid deployment solution supports the configuration of E-Recruiting in the one-system and separated system architecture. One-system means that SAP HCM and E-Recruiting are installed on the same instance, separated indicates that E-Recruiting and SAP HCM run on separate instances. Please be aware that if you run E-Recruiting and SAP HCM on separate instances, the rapid deployment solution requires a SAP ERP installation on the instance where E-Recruiting will be configured. The reason is that the content for the rapid deployment solution is being delivered through the SAP Best Practices Add-On BP-ERP which needs to be installed on an SAP ERP instance. Therefore a NetWeaver standalone implementation of E-Recruiting is not supported with the rapid deployment solution. The rapid deployment solution supports the Simple Basic Architecture as described in the Technical System Landscape which means that Front-End and Backend for Candidates are on one system. A separation of Front-End and Backend for candidate scenarios is therefore not part of the scope of this rapid deployment solution.

3.1.1 SAP ERP Core Components 6.0 The following software components are needed at their respective SPS levels for the SAP E-Recruiting rapid-deployment solution:

Software Component Release Support Package Level

Description System

SAP Basis 7.02 (SAP_BASIS)

702 0011 SAP Basis Component

HR ECC + E-Recruiting

SAP ABA 7.02 (SAP_ABA) 702 0011 Cross-Application Component


SAP APPL (SAP_APPL) 605 0008 Logistics and Accounting


PI Basis (PI_BASIS) 702 0011 Basis Plug-In HR ECC

SAP Web UIF 7.01 (WEBCUIF)

701 0008 SAP WEBCUIF 700

HR ECC

http://help.sap.com/erp2005_ehp_05/helpdata/EN/48/7862d889dd501ae10000000a42189b/content.htm

http://help.sap.com/erp2005_ehp_05/helpdata/EN/48/7862d889dd501ae10000000a42189b/content.htm



SAP BS Foundation 7.02 (SAP_BS_FND)

702 0009 SAP Business Suite Foundation

SAP_HR 604 0047 HR ECC

EA_HR 605 0024 HR ECC

ERECRUIT 605 0008 E-Recruiting E-Recruiting

TREX 710 0019 TREX HR ECC + E-Recruiting

ADOBE DOCUMENT SERVICES

702 0008 ADOBE DOCUMENT SERVICES

HR ECC

Usually required software components and SPS levels are downloaded using the Maintenance Optimizer of SAP Solution Manager. If you need to download manually from SAP's Software Distribution Center in Service Marketplace please follow below given path:

Installation: https://service.sap.com/swdc Installations and Upgrades Browse our download catalog SAP Application Components SAP ERP

Support Packages: https://service.sap.com/swdc SAP Software Distribution Center Download Support Packages and Patches Browse our Download Catalog SAP Application Components SAP ERP SAP ERP Enhance Package EhP5 for SAP ERP 6.0 Entry By Component Human Capital Management

As outlined in SAP Note 1064635, SPS levels for SAP ERP are synchronized throughout all enhancement package versions. Software components and add-ons not used within an Enhancement Package should have the SP level assigned to the concurrent SPS of SAP ECC 6.00. Attached to SAP note 1386389 SAP BAiO/BP: Stack Information/Explanation for Used Products, an overview of all software components and their support package levels combined in the various support package stacks is given.

3.1.2 SAP NetWeaver Enterprise Portal Components The following software components are needed at their respective SP levels for the SAP E-Recruiting rapid-deployment solution

Software Component Release SP Level Description

SAP_MSS 600 0020 MSS

SAP_ESS 603 0010 ESS

PCUI_GP 603 0009

BP_ERP5COM 1.51 0007 Business Package for ERP Common Parts

BPERPESSWDA 1.50 0005 Business Package for Employee Self-Service (Web Dynpro ABAP)

BP_ERP5MSS 1.51 0006 Business Package for Manager Self-Service

BP_ERP5ESS 1.41 0011 Business Package for Employee Self-Service (JAVA)

BP RECRUITER 1.51 n/a Business Package for Recruiter 1.51

https://service.sap.com/swdc

https://service.sap.com/swdc

http://service.sap.com/sap/support/notes/1386389

http://service.sap.com/sap/support/notes/1386389



BP RECRUIT ADMIN 1.51 n/a

Business Package for Recruiting Administrator 1.51

3.1.3 SAP NetWeaver XI/PI The following software components are needed at their respective SP levels for the SAP E-Recruiting rapid-deployment solution:

Software Component Release SP Level Description

SAP NetWeaver PI 7.11 or 7.3

SAP NetWeaver Process Integration

XI CONTENT ERECRUIT 605

605 08 XI CONTENT ERECRUIT 605 Database independent ERECRUIT60506_0-20004405.ZIP ERECRUIT60506

XI CONTENT EA-HR 605

605 24 XI CONTENT EA-HR 605 Database independent EAHR60516_0-20004234.ZIP EAHR60516

3.1.4 SAP Solution Manager For the implementation of the SAP ERP rapid-deployment edition, a SAP Solution Manager system is recommended. SAP Solution Manager in general is needed for installation and managing of maintenance certificates, Enhancement Packages and upgrades. In the context of SAP Rapid-Deployment solutions, implementation content is delivered via SAP Solution Manager templates. It is assumed that a productive SAP Solution Manager system (7.1 or higher) is available in the customer’s system landscape on the E-Recruiting system: if the customer is already using other SAP products (for example, SAP ERP) then the customer should already have SAP Solution Manager in the system landscape.

For more information about SAP Solution Manager, see the SAP Library documentation for SAP Solution Manager at http://help.sap.com SAP Solution Manager, or at http://service.sap.com/solutionmanager

3.2 SAP Enterprise Extensions Sets and Enterprise Business Functions

Use After installing SAP ERP, the following SAP ECC Extension Sets need to be activated before you start activation of SAP E-Recruiting rapid-deployment solution.

Activating Enterprise Extensions, business functions, and business function sets makes permanent changes to your system and cannot be undone. For more information about the impact, see the documentation of the related extension or business function.

Procedure 1. Run the following activity:

http://service.sap.com/solutionmanager



IMG Menu Activate SAP ECC Extensions

Transaction Code SFW5

2. On the Switch Framework: change Business Function Status screen, select each of the following

entries (by marking the column Planned Status) and then choose the Activate Changes button:

Enterprise Extensions

Planned Status

Remarks System

EA-HR

ON This generic business function provides you with generic functions such as the following for SAP ECC Enterprise Extension Human Capital Management

HR ECC

Enterprise Business Function

Planned Status

Remarks System

ERP_ALL_PDF_FORMS

ON With this business function you can provide your SAP ERP users with forms in output format PDF

HR ECC

ERP_ENTERPRISESEARCH

ON You can use this business function to implement a faster and safer search function for business objects in SAP ERP

HR ECC

HCM_TMC_CI_1

ON Required for PI-Integration

Prerequisite for HCM_HIRE_INT_CI_1


HCM_ASR_CI_1 ON Prerequisite for HCM_ASR_CI_3 HR ECC

HCM_ASR_CI_2 ON Prerequisite for HCM_ASR_CI_3

and HCM_HIRE_INT_CI_1 HR ECC

HCM_ASR_CI_3

ON You can use this business function to activate the functions for the HCM Processes and Forms component

HR ECC

HCM_ERC_CI_1

ON Prerequisite for HCM_ERC_CI_4 and HCM_ERC_SES_1 and HCM_MSS_ERC_CI_1

E-Recruiting

HCM_ERC_CI_2 ON Prerequisite for HCM_ERC_CI_4 E-Recruiting

HCM_ERC_CI_3 ON Prerequisite for HCM_ERC_CI_4 E-Recruiting

HCM_ERC_CI_4

ON You can use this business function to make the process of recruiting and hiring suitable applicants more efficient and to make it easier to work with SAP E-Recruiting.

E-Recruiting

HCM_ERC_SES_1 ON You can use this business

function to enhance the search E-Recruiting



applications in SAP E-Recruiting and thus to obtain more precise search results.

HCM_HIRE_INT_CI_1

ON You can use this business function during the hiring process to transfer the data of a successful candidate from SAP E-Recruiting to your system for SAP ERP Human Capital Management (SAP ERP HCM).


HCM_MSS_ERC_CI_1

ON You can use this business function to implement the Recruiting work center in Manager Self-Service (MSS).

HR ECC

HCM_NWBC_ROLES ON Required for NWBC HR ECC + E-Recruiting

3. The system displays an informational dialog box. Choose Continue. 4. Choose Back.

3.3 SAP Notes and Messages If issues become apparent after shipment of this rapid-deployment solution (and hence of this document), a SAP Note exists to document how to solve the issues.

All SAP Notes have to be applied to the system via the SAP Note Assistant. All SAP Notes mentioned below need to have the implementation status Completely implemented. Some SAP notes require manual action before you set the status to Completely Implemented. To avoid activation errors as a result of generating loads, you have to perform a mass generation using transaction SGEN as described in SAP Note 481548.

SAP Note # Description Remark System

0001654883 SAP E-Recruiting rapid-deployment solution

Always check the SAP Note for SAP E-Recruiting rapid-deployment solution for updates on the implementation

E-Recruiting

The following SAP Notes must be implemented (if not stated otherwise in the SAP Note mentioned above):

SAP Note # Description System

1151863 WRITE_CPOINTER_SES in OOHAP_BASIC E-Recruiting

1075650 New Design Tool for Processes and Forms HR ECC

669669 Updating the SAP Component Repository in the SLD PI




836200 Importing Process Integration Content PI

Please mind your system architecture: The following SAP Notes must be implemented (if not stated otherwise in the SAP Note mentioned above) if the SAP E-Recruiting runs on a different system than HR.


1609859 EREC: Future leaving action is not processed E-Recruiting

1643666 EREC: Candidate still "Internal" after leaving E-Recruiting

4 System Preparation for Implementation (Administrator/Consultant)

Before the consultant can start with the automated rapid-deployment solution content implementation the steps in the following chapter need to be performed.

4.1 Installation of the SAP Best Practices Add-On The following SAP Best Practices content add-on have to be installed in order to use the automated installation of the SAP E-Recruiting rapid-deployment solution: Software Component

Release Version System

BP-ERP 605Vx Always use the latest available version (605V3 at the time of writing) as outlined in SAP Note 1301301 (Release Strategy for SAP Best Practices Package ABAP Add-ons) (https://service.sap.com/sap/support/notes/1301301)

E-Recruiting

Use If possible, Business Configuration Sets (BC Sets) for maintaining customizing settings and Extended Computer Aided Test Tool procedures (eCATT) for master data creation are used for SAP Best Practices. This use automates the configuration of the SAP Best Practices scenarios. BC Sets and eCATTs were delivered as so-called add-on transport files with the SAP Best Practices ADD-ON BP-ERP 605V6. In addition the BP-ERP Add-on contains the SmartForms which are being used for correspondence in the E-Recruiting process. If you prefer to do a manual configuration instead of using the automation content you still need to install the BP-ERP Add-on to have the RDS SmartForms available into your system. Import SAP Best Practices ADD-ON into your ERP system, if you want to make use of the automated configuration and/or the pre-delivered SmartForms.

Procedure 1. Download the Add-on as described in note 1301301 from the Software Distribution center at

http://service.sap.com/swdc Installations and Upgrades Entry by Application Group SAP Rapid Deployment Solutions SAP E-Recruiting rapid-deployment solution

2. Import the SAR file using transaction SAINT into your SAP ERP system.

https://service.sap.com/sap/support/notes/1301301

http://service.sap.com/swdc



Result BC Sets and eCATTs are now available in your ERP system and can be used in combination with the SAP Best Practices Solution Builder for automated configuration of BP scenarios.

4.2 Installation of SAP Best Practices Solution Builder The following SAP Best Practices Add-ons have to be installed on SAP E-Recruiting in order to use the automated installation of the SAP E-Recruiting rapid-deployment solution:

Software Component

Release Version System

BP-SOLBLD

70Vx Always use the latest available version (70V5 at the time of writing) as outlined in SAP Note 1301301 (Release Strategy for SAP Best Practices Package ABAP Add-ons) (https://service.sap.com/sap/support/notes/1301301)

E-Recruiting

Use Use SAP Best Practices Solution Builder to easily install the selected scenarios in minimum time. SAP Best Practices Solution Builder is a tool that guides you step-by-step through the installation process directly in the system.

Procedure 2. Download the Add-on as described in note 1301301 from the Software Distribution center at

http://service.sap.com/swdc Installations and Upgrades Entry by Application Group SAP Rapid Deployment Solutions SAP E-Recruiting rapid-deployment solution

1. Import the SAR file using transaction SAINT into your SAP ERP system.

Result SAP Best Practices Solution Builder has been installed in your SAP ERP system. The use of Solution Builder is described in the section Installation of Business Content of this guide.

4.3 General Client Settings 4.3.1 Creating User for Activation of SAP Best Practices

Content

Use In this activity, you create a user in SAP E-Recruiting to run the activation of the related SAP Best Practices scope. The rapid-deployment-solution scope does not supply separate customizing or setup roles. Instead, you should use the functions provided in Role Maintenance (transaction PFCG). Here you can define a role corresponding to your individual implementation project with all the authorizations you need to access the corresponding Implementation Guide (IMG) activities required for the SAP Best Practices scope. For more information about building a role for a Customizing project, see the documentation for transaction PFCG.

Alternatively you can use the authorization profile SAP_ALL. If this authorization does not apply to your authorization concept, you should restrict the rights of the user according to your internal authorization guidelines. Without the profile SAP_ALL, issues during the activation may occur and need to be solved. You can use the transaction SU53 to get information on the missing authorizations and extend the authorization data as necessary.

https://service.sap.com/sap/support/notes/1301301

http://service.sap.com/swdc



Directly after activation of the SAP Best Practices content, remove the authorizations you have given to the system user that has performed the activation steps. This is for security reasons to avoid that the system user misuses the authorizations granted before.

Procedure 1. To carry out the activity, choose one of the following navigation options:

SAP Menu Tools Administration User Maintenance Users

Transaction Code SU01

2. On the User Maintenance: Initial Screen, in the User field, enter <User-ID> and choose Create. 3. Choose the Address tab. 4. Make the following entries:

Field name User action and values

Last name <Last name of the user>

First name <First name of the user>

5. Choose the Logon Data tab. 6. Make the following entries:


Password <initial password>

User type Dialog

7. Choose the Defaults tab. 8. Make the following entries:


Logon language EN

Decimal notation 1,234,567.89

Date format MM/DD/YYYY

9. Choose the Roles tab. 10. Enter the user role you created that contains the necessary authorization profile

Alternatively you can assign the profile SAP_ALL on the Profiles tab. Make sure that this corresponds to your internal security guidelines.

11. Save yur entries.

Result A user to activate SAP Best Practices content has been created.

4.3.2 Deselecting Activation Links in BC Sets We recommend that you turn off the creation of activation links in SAP E-Recruiting. By doing this, you can significantly increase activation speed and avoid errors.


SAP Menu Tools Customizing Business Configuration Sets Activation of BC Sets



Transaction Code SCPR20

2. On the Business Configuration Sets: Activation screen, choose Utilities System Settings. 3. Choose Change (Shift + F1). 4. In the Activation section, select the radio button for Do Not Create parameter. 5. Choose Enter on the information message. 6. Save your settings.

4.3.3 Maximum Work Process Run Time

Use Dynamic switchable profile parameters (indicated by a flag in the check box of the parameter) have to be checked in SAP E-Recruiting before activation. Therefore the following profile parameters must be checked and adapted.


Transaction Code RZ11

2. On the Maintain Profile Parameters screen, make the following entries

Field name Description User action and values

Param. Name Profile parameter name rdisp/max_wprun_time

3. Choose Display. 4. On the Display Profile Parameters Attributes screen, select Change values. 5. On the Change Parameter Value screen, make the following entries.

Parameter Name Description New value

Note

rdisp/max_wprun_time Max work process run time 3600 Check and adapt value if value is <3600

6. Choose Save.

When you save the change, the window closes and the value of the parameter is changed. This change only becomes effective when you log off and then log on to the system again.

If the parameter is set in RZ11, you lose the change when you restart the server.

This parameter value is only needed for activation of SAP Best Practices as there are some processes that need to be performed in dialog and last for more than 10 minutes. Switch back to the default value after activation of SAP Best Practices!

4.3.4 SAP Scripting

Use eCATTs are used to automate the activation of SAP Best Practices configuration settings. Prior to activation, you must allow eCATT processing in the SAP E-Recruiting system by setting the profile



parameter sapgui/user_scripting. The value for Enable or disable user scripting on the front-end must be set true.

Procedure 1. Start transaction RZ11. 2. On the Maintain Profile Parameters screen, make the following entries

Field name Description User action and values

Param. Name Profile parameter name sapgui/user_scripting

3. Choose Display. 4. On the Display Profile Parameters Attributes screen, select Change values. 5. On the Change Parameter Value screen, make the following entries.

Field name Description User action and values Note

New Value New Value for user scripting

TRUE Enable SAP Scripting

6. Choose Save.

When you save the change, the window closes and the current value of the parameter changes to TRUE. This change only becomes effective when you log on to the system again.

If the parameter is set in RZ11, you lose the change when you restart the server.

4.3.5 Set Default Timeout for http and https Services

Use We recommended that you set the following for both services TIMEOUT and PROCTIMEOUT to 300 or 600 (seconds) in SAP E-Recruiting. The default is 60.

The values are also set using system parameters (see below section Procedure): icm/server_port_<*> - Standard value for *: 0: http, 1 or 2: https

For example: icm/server_port_0 = PROT=HTTP, PORT=8000, PROCTIMEOUT=300, TIMEOUT=600 icm/server_port_2 = PROT=HTTPS, PORT=44300, PROCTIMEOUT=300, TIMEOUT=600

Procedure 1. Start transaction RZ10. 2. On the Edit Profiles screen, enter your instance profile. 3. In the Edit Profile box, select the radio button for Extended maintenance and choose Change. 4. On the Maintain Profile screen, make the following entries:

Parameter Name Description New value Note

icm/server_port_<*> Standard value for *: 0: http, 1 or 2: https

300 or 600 Set to 300 or 600 (seconds) for TIMEOUT and PROCTIMEOUT, the default is 60

5. Choose Back 6. Choose Save.



This adaptation of these profile parameters is only necessary if you are using SAP NetWeaver Business Client.

4.4 Prepare System User for Content Activation Perform the following activities in the E-Recruiting system.

4.4.1 Activation Language Make sure that your logon language is always English (and NOT your local language) for all activation activities.

4.4.2 User Settings for Activation

For activation, we recommend that only one User ID be used to activate the SAP Best Practices. It can be a tedious procedure to change ownership of the activation of the solution.

Make sure that you only have one single SAP GUI session running when you activate SAP Best Practices. If you run several SAP GUI sessions, some automated installation activities might run into errors.

4.4.3 Deactivate Info Dialog Box on Dynpro Size Check

Use The dialog box sizing conflicts may appear which may pop up during activation has to be deactivated.

Procedure 1. Log on with the user in the system. 2. From the standard tool bar, choose the Customizing of Local Layout button or type ALT + F12. 3. Select the menu item Options. 4. Open folder SAP Internal. 5. Choose option SAP Internal. 6. Deselect the Enable dialog box for dynpro size check checkbox. 7. Choose OK.

4.4.4 SAP Software Change Registration (SSCR): Developer Key

Use The user ID used for activation has to be registered as developer on SAP Service Marketplace (SAP Software Change Registration, SSCR). For more information, see SAP Note 86161. The SSCR developer key is needed, because the user ID used for SAP Best Practices activation creates and changes objects from the customer name range during the SAP Best Practices activation process. If the SAP Best Practices activation user is not registered as a developer, the automated SAP Best Practices activation incurs errors.

Procedure



1. Access the SAP Service Marketplace at http://service.sap.com/sscr. 2. On the SAP Software Change Registration (SSCR) start page, you get the detailed user

documentation on how to proceed to get the SSCR developer key.

An SSCR developer key is a 20 character combination of digits that is queried when an SAP ERP user tries to create or change an object from the customer name range FOR THE FIRST TIME. The prompting message for the developer key appears once for each SAP ERP user; if registration is successful, this SAP ERP user is no longer prompted to enter a developer key. The SSCR developer key is generated from the installation number of the affected installation and the SAP ERP user name.

4.4.5 Unicode Settings

Use Before each user logs on to the system for the first time, the user’s local GUI must be set to use the Unicode code page.

Procedure 1. From the SAP Logon pad, select your system ID. 2. Choose the Change Item button. 3. On the System Entry Properties dialog box, choose the Code Page tab. 4. On the Encoding dropdown, select Unicode (UTF-8). 5. Choose OK.

4.4.6 Allow GUI Scripting

Use Perform this activity so that eCATTs GUI scripts can by executed with your GUI.

Procedure 1. From the standard tool bar, choose the Customizing of Local Layout button or type ALT + F12. 2. Select the menu item Options. 3. Open folder Accessibility and Scripting. 4. Choose option Scripting. 5. Select the Enable scripting checkbox. 6. Deselect the checkboxes Notify When a Script Attaches to a Running GUI and Notify When a

Script opens a Connection. 7. Choose OK.

5 Implementation of RDS Business Content 5.1 Selecting the SAP Solution Manager Template

Perform the following activities in the E-Recruiting system. Templates in SAP Solution Manager assist you in performing predefined implementation projects. The template specific to the SAP E-Recruiting rapid-deployment solution contains the content for the ‘default’ implementation of the rapid-deployment. Familiarize yourself with the template with the help of the template description at http://service.sap.com/solutionpackages SAP E-Recruiting rapid-deployment solution Template

http://service.sap.com/sscr



Procedure To select the template, carry out the following steps in transaction SOLAR_PROJECT_ADMIN: 1. Navigate to the Scope tab. 2. Select the Template Selection view. 3. Search for the template SAP E-Recruiting rapid-deployment solution (technical name RDS_HCMTM_V01) 4. To select the template, mark the checkbox next to the relevant template. 5. Save your project. 6. In the pop-up window, check if your system landscape fits to the required system landscape of the

template. If the systems in your landscape are not maintained completely, in the Logical Component column, choose the F4 help for guidance in selecting the correct logical component.

For more information on the system landscape in SAP Solution Manager, see the SAP Solution Manager documentation in the SAP Help Portal at http://help.sap.com SAP Solution Manager SAP Solution Manager 7.0 EhP1 SP23 Language English Implementing and Upgrading SAP Solutions Project Administration Create/Change Project Specify Scope.

7. On the System Landscape tab, make sure the required system landscape for the selected template is assigned to your project.

For more information about using templates in a project, see the SAP Solution Manager documentation in the SAP Help Portal at http://help.sap.com SAP Solution Manager SAP Solution Manager 7.0 EhP1 SP23 Implementing and Upgrading SAP Solutions Roadmap and Using Templates.

5.2 Adjust the Process Scope in SAP Solution Manager Perform the following activities in the E-Recruiting system.

In the subsequent steps you adjust the scope of the solution where possible to fit business goals, and adjust the configuration settings in the systems accordingly. In SAP Solution Manager, adjust the scope of the business processes you would like to implement. In the SAP Easy Access menu, choose Business Blueprint (transaction SOLAR01). For more information on the rapid-deployment solution scope refer to the Template Description.

In the template, all business processes (scenarios) are self-contained, i.e. have all related content assigned. Therefore you do not need to select Master Data or Organizational Unit nodes or Interface Scenarios in the blueprint structure. We recommend deselecting these nodes to have a better overview during the configuration step later (transaction SOLAR02).

In transaction SOLAR01, you can also access the template description to check which processes are mandatory or optional for the rapid-deployment solution. To access the template description, in the structure on the left, select the column Templates. Then the system displays the name of the template selected for the project in the structure (if the template name is not shown scroll to the right until you can see the Templates column). By clicking on the template name displayed you can access the template description.

For more information about Business Blueprints in SAP Solution Manager, see the SAP Solution Manager documentation in the SAP Help Portal at http://help.sap.com SAP Solution Manager SAP Solution Manager 7.0 EhP1 SP23 Implementing and Upgrading SAP Solutions Business Blueprint.

http://help.sap.com/



5.3 Automated Implementation Using SAP Best Practices Solution Builder

5.3.1 Getting the Business Content for Activation

Perform the following steps Getting the Solution Scope File and Getting the Installation Data Files on the same day. If you download the files at different times, you may encounter errors due to mismatches.

5.3.2 Getting the Solution Scope File

Use The technical structure for each solution package (processes or scope items, building blocks and technical objects) is managed by a solution scope file.

Procedure 1. To download the solution scope file, first go to SAP Service Marketplace at

http://service.sap.com/bp-implcontent. 2. Choose the Solution files link and then the link for EHP5 for SAP ERP 6.0 3. Download the following solution scope .zip file:

SOL_RDS_ACC_ERECRUITING_ERP605V1_BP_ERP605V6.zip

5.3.3 Getting the Installation Data Files

Use The installation settings (configuration settings and master data) of the solution packages are managed by the installation data files.

Procedure 1. To download the installation data files, first go to SAP Service Marketplace at

http://service.sap.com/bp-implcontent. 2. Choose the Installation data file sets link and then the link for EHP5 for SAP ERP 6.0 3. Download the following installation data .zip file:

INST_FILES_EREC_XX_BP_ERP605V6.zip

5.3.4 Creating a Folder for the SAP E-Recruiting rapid-deployment solution Activation

1. Create a folder on a hard drive (for example, on your local hard drive) that can be accessed from within the SAP system where you want to activate the SAP E-Recruiting rapid-deployment solution. Ensure that the persons who will activate package have the necessary user rights to access this folder.

2. Extract the files from the ZIP files you downloaded in the previous task into the folder you created in step 1. You should have one solution scope file (*.xml), many variant files (*.TXT) and one bitmap file (smb40_leaf.bmp).

http://service.sap.com/bp-implcontent

http://service.sap.com/bp-implcontent



Perform the following activities in the E-Recruiting system.

5.3.5 Import Solution Scope File The relevant solution scope file (*.xml file), that is needed for the SAP E-Recruiting rapid-deployment solution, has been copied into the installation data directory (like described in section Creating a Folder for the SAP E-Recruiting rapid-deployment solution Activation).

Procedure To install the SAP E-Recruiting rapid-deployment solution, upload the relevant solution scope file as follows: 1. Start the SAP Best Practices Solution Builder with transaction /SMB/BBI Solution and

Implementation. 2. The Solution Editor screen displays, listing all solutions available in the system.

The solution list is empty the first time you enter the Solution Editor (if no other users have uploaded or created solutions in the system).

The button bar indicates the sequence of operation for end-users.

We recommend adding the transaction for the Solution Builder (/SMB/BBI) to the favorites of your SAP user menu.

3. In the Solution Builder – Solution Editor screen, choose Solution Import Solution (XML) from the menu.

4. In the Select the Solution Scope File (XML) dialog box, indicate the path to the installation directory, select the relevant solution scope file and choose Open.

5. Choose a Solution Scope file: RDS_ACC_ERECRUITING_ERP605V1.xml 6. After the solution is uploaded (depending on the size of the solution a few seconds up to one

minute), an information box about the uploaded scenarios and building blocks is displayed. Choose OK to confirm.

Result The uploaded solution is visible in the solution list and is marked as your favorite solution.

If the path to the installation data directory is too long, the system will display an error message. If you receive this error message, either rename directories in the path to shorten the file path, or copy the installation files to a directory being closer to the root folder of the hard drive.

5.3.6 Upload Installation Data

Procedure To upload the installation files, proceed as follows in Solution Builder: 1. Go to view Solution Builder – Solution Editor 2. From the menu, choose Goto Installation data Upload 3. Enter the installation directory created in previous step 4. Choose OK

Result



The installation data has been uploaded into Solution Builder.

5.4 Pre-Activation Activities

Use After installing SAP ERP and the other needed SAP components, applying the required SAP SP and SAP Notes, and importing the SAP Best Practices Add-on, you can prepare your system for activation. You can run SAP E-Recruiting as a standalone scenario on one instance or in an integrated scenario on different instances. In the integrated scenario, SAP E-Recruiting runs on the same system and client as SAP ERP Central Component (SAP ECC). (Software runs on one instance.) In the standalone scenario, only SAP E-Recruiting is active in the system; other active ERP components are installed on another system, separate from the SAP E-Recruiting system. This scenario also includes the case where SAP E-Recruiting runs on the same system as the ERP components, but in a different client. (Software runs on different instances.) The SAP E-Recruiting rapid-deployment solution is based on the integrated scenario on one instance. Before you configure your SAP E-Recruiting system, we recommend that you check your system's technical settings to ensure that the system will run properly. You should make the following checks.

5.4.1 Check System Status In your HR ECC system and your SAP E-Recruiting system choose System -> Status -> Component Information. Ensure that the components required have been installed. Check the kernel information as well, in particular, the patch level data.

5.4.2 Configuration of RFC Connections Use: In this IMG activity, you create the RFC connections that are required for the Rapid-Deployment-Solution.

For this activity consider your system landscape.

5.4.3 Set up the RFC Connection between HR and E-Recruiting In case of E-Recruiting and HR running on the same instance the RFC connection points to the own system. In case of separated systems perform this activity in both the E-Recruiting and the HR system, each connection pointing to the other system. That means when you perform the activity in the HR system you enter the name and server of the E-Recruiting system. In the E-Recruiting system you enter the name and server of the HR system.

1. Access the transaction using the following navigation path:



Transaction Code SM59

IMG Menu Integration with Other SAP.com Components Business Packages / Functional Packages Manager Self Services (mySAP ERP) Recruitment Create RFC Connection to E-Recruiting System

1. On the Configuration of RFC Connections screen, choose New Entries. 2. On the RFC Destination screen, enter the values shown below:

Field name User action and values Note

RFC Destination RFC server’s name Integrated architecture: own system name Separated architecture: opposite system name

For example RT5CLNT120

Connection Type Server Connection Type 3 (ABAP Connection)

Description 1 The description for the connection

For example RT5CLNT120

3. Navigate to tab Technical Settings and make the following entries:


Targe Host Enter the Target Host Integrated architecture: own server Separated architecture: opposite server

For example uxcirt5.wdf.sap.corp

System Number Enter the system number Integrated architecture: own system number Separated architecture: opposite system number

For example: 15

Save Database as Hostname

Hostname Enter the hostname Integrated architecture: own server Separated architecture: opposite server

For example uxcirt5.wdf.sap.corp

4. Navigate to tab Logon & Security and make the following entries:




Language EN

Client Enter the used client Integrated architecture: own client Separated architecture: opposite client

For example 120

Trust Relationship No

User Integrated architecture: *leave empty* Separated architecture: ALEUSER

Untick the selection Current User to activate the user entry field

Password Integrated architecture: *leave empty* Separated architecture: initial

Field is only active if Trust Relationship is set to No and Current User is not selected

5. Choose Save. 6. Choose Connection Test to test the setup. 7. Choose Back to return to screen Configuration of RFC Connections.

Setup the RFC connection from the E-Recruiting and from the HR system to the PI system Perform the following steps in your E-Recruiting system and then repeat them in the HR system.






RFC Destination RFC server’s name For example: PI_INTEGRATION_SERVER In case of separated system: use a slightly different name in the second system, e.g. PI_INTEGRATION_SERVER_RPI

Connection Type Server Connection Type H (HTTP Connection to ABAP System)


For example PI 7.0 Integration Server



Target Host Enter the Target Host For example vmw4163.wdf.sap.corp

Service No. Enter the service number For example: 50020

Path Prefix /sap/xi/engine/?type=entry



Logon with User SAP RFC Logon

Language EN

Client Enter the used client For example 120

User PIAPPLUSER

PW Enter a password for the user For example initial

Logon with Ticket Do not Send Logon Ticket

Status of Secure Protocol – SSL

Inactive

SSL Certificate DEFAULT SSL Client (Standard)

5. Choose Save. 6. Choose Connection Test to test the setup. 7. Repeat the steps 1 to 6 in your HR system.

Setup the RFC connection from the PI system to the E-Recruiting and to the HR system Logon to your PI system and create the connection to your E-Recruiting and to your HR system.






RFC Destination RFC server’s name For example: RT5CLNT120_H In case of separated system: after the RFC to the E-Recruiting system, create the RFC connection to the HR system in a second step, e.g. Q6GCLNT020_H



For example E-Recruiting system



Target Host Enter the Target Host For example vmw4163.wdf.sap.corp


Path Prefix /sap/xi/engine/?type=entry



Logon with User SAP RFC Logon

Language EN


User RFCSYSUSER

PW Enter a password for the user For example initial

Logon with Ticket Do not Send Logon Ticket

Status of Secure Protocol – SSL

Inactive

SSL Certificate DEFAULT SSL Client (Standard)

5. Choose Save. 6. Choose Connection Test to test the setup. 7. Repeat the steps 1 to 6 in your HR system.

Setup the RFC connection for the NetWeaver Business Client



For this activity consider your system frontend. If you use the SAP NetWeaver Business Client as frontend please create also an RFC connection type H as described below. If you use the SAP Portal this activity is not required.




RFC Destination RFC server’s name + HTTP ID For example RT5CLNT120_HTTP



For example RT5CLNT120_HTTP



Target Host Enter the Target Host For example uxcirt5.wdf.sap.corp




Language EN


5. Choose Save. 6. Choose Connection Test to test the setup.

Result: RFC connections have been created.

5.4.4 Local Administration in System Landscape Directory Use: In this IMG activity, you register the backend systems E-Recruiting and HR in the System Landscape Directory for PI.



For this activity consider your system landscape. In case of a separated system architecture perform this step in the E-Recruiting as well as in the HR system.


Transaction Code RZ70

2. On the System Landscape Directory: Local Administration make the following entries:


Transport Information Standard RFC Destination

SLD Bridge: Gateway Information Host

Enter the host of the PI server Example: vmw4163

3. Make sure that the entries for the gateway host and service are exactly the same as in the SLD Bridge. Avoid the usage of one gateway by more than one SLD bridge.

Scheduled Data Collection: 4. Enter the required amount of time in field Period of Minutes. It will determine how often

the data gathering transfer will take place. 5. Choose Schedule Background Job. 6. By default, the Schedule background job indicator is selected. If you deselect it, the data

about the system will be sent to the SLD only if you trigger the data collection programs manually.

7. In the Period in Minutes field, enter a time interval in minutes for collecting data. The default setting is 720 minutes (12 hours). This means that the data about the current system will be updated in the SLD twice a day.

8. Save these settings by choosing Schedule Background Job. 9. Choose Start SLD Data Collection Now. 10. A separate screen appears with a list of the executed programs and you are informed

whether the initial transfer of data by RFC has been successful. For more information,see SAP Note 584654.

11. Make sure all Data Collection Programs are activated and choose Activate Current Configuration (F8).

12. Choose Start Data Collection and Job Scheduling (F5). 13. Repeat steps 1 to 12 in your second system (in case of a separated architecture) and in the

PI system.

5.4.5 Integration Engine Configuration to PI

For this activity consider your system architecture. If E-Recruiting and HR run on different systems perform this activity in both of them. Otherwise the PI points only to one system.

Transaction Code SXMB_ADM

1. Go to Integration Engine Configuration. Choose Execute Function (F8).

2. In screen Integration Engine Configuration Data go to Edit Change Global Configuration Data.



3. Make the following entries:

Field name Value Comment

Role of Business System Application System

Corresponding Integ. Server

Enter the RFC connection type H to the PI system

Example: Dest://PI_INTEGRATION_SERVER

4. In case of a separated architecure repeat steps 1 to 3 for your second system.

5.4.6 Create Configuration Objects in SAP Integration Directory (PI)

5.4.6.1 Start Integration Directory

Procedure 1. Open SAP NetWeaver PI Landing Page:

PI Landing Page http://<pi_hostname>:<pi_http_port>/dir

2. In the PI Tools area, open SAP NetWeaver Integration Builder within Enterprise Service Repository (ESR) area by click on the link.

5.4.6.2 Assign Business System for eRec-System

Procedure 1. Create a new Business Component in the Integration Directory using Integration Builder:

Path In Integration Builder Communication Component Without Party Right-click on Business System Assign Business System…

2. In the input field Communication Component, enter EREC. 3. Click on Create. 4. Click on the Save button to save the Business Component. 5. In the Objects tree on the left, right-click on the Business Component and select Activate… from

the context menu to activate the Business Component.

5.4.6.3 Assign Business System for ERP HR-System

Procedure 1. Create a new Business Component in the Integration Directory using Integration Builder:

Path In Integration Builder Communication Component Without Party Right-click on Business System Assign Business System…

2. In the input field Communication Component, enter HR. 3. Click on Create. 4. Click on the Save button to save the Business Component.



5. In the Objects tree on the left, right-click on the Business Component and select Activate… from the context menu to activate the Business Component.

5.4.6.4 Add Interfaces to Business System for e-Rec-System

Procedure 1. Open the Business Component EREC assigned in the previous step in the Integration Directory

using Integration Builder:

Path In Integration Builder Communication Component Without Party Business System Double-click on EREC

2. Switch to the Edit mode. 3. In the tab Receiver under Inbound Interfaces click on the button Insert Line Below Selection (with

the green plus sign). 4. Click on the Value List… button in the column Name of the inserted line. 5. Select following inbound interfaces:

Inbound Interfaces PersonnelHiringERPCreateConfirmation_In

6. Click on Apply. 7. Switch to the Sender tab. 8. Click on the button Insert Line Below Selection (with the green plus sign). 9. Click on the Value List… button in the column Name of the inserted line. 10. Select following outbound interfaces:

Outbound Interfaces PersonnelHiringERPCreateRequest_Out

11. Click on Apply. 12. Click on the Save button to save the Business System. 13. In the Objects tree on the left, right-click on the Business System and select Activate… from the

context menu to activate the Business Component.

5.4.6.5 Add Interfaces to Business System for ERP HR-System

Procedure 1. Open the Business System HR assigned in the previous step in the Integration Directory using

Integration Builder:

Path In Integration Builder Communication Component Without Party Business System Double-click on HR

2. Switch to the Edit mode. 3. In the tab Receiver under Inbound Interfaces click on the button Insert Line Below Selection (with

the green plus sign). 4. Click on the Value List… button in the column Name of the inserted line. 5. Select following inbound interfaces:

Inbound Interfaces PersonnelHiringERPCreateRequest_In,

6. Click on Apply. 7. Switch to the Sender tab.



8. Click on the button Insert Line Below Selection (with the green plus sign). 9. Click on the Value List… button in the column Name of the inserted line. 10. Select following outbound interfaces:

Outbound Interfaces PersonnelHiringERPCreateConfirmation_Out

11. Click on Apply. 12. Click on the Save button to save the Business System. 13. In the Objects tree on the left, right-click on the Business System and select Activate… from the

context menu to activate the Business Component.

5.4.6.6 Create XI Receiver Channel for Business System EREC

Procedure 1. Create a new channel in the Integration Directory using Integration Builder:

Path In Integration Builder Communication Component Without Party Business System EREC Right-click on Communication Channel New…

8. In the Communication Channel input field, enter the name of the sender channel to be created

(e.g. XI_Receiver_EREC) 9. Leave the Party field empty (remove the * symbol) 10. Click on Create. 11. In the Parameters tab, select the Input help dialog button on the right side. 12. Choose XI as Adapter Type and press Apply. 13. Assign following data:

Transport Protocol HTTP 1.0

Message Protocol XI 3.0

Adapter Engine Integration Server

Addressing Type HTTP Destination

HTTP Destination <Destination defined in previous step for eRec System>

14. Select check box Transfer Hop List. 15. Click the Save button to save the channel. 16. In the Objects tree on the left, right-click on the Communication Channel and select Activate…

from the context menu to activate the Communication Channel.

5.4.6.7 Create XI Receiver Channel for Business System ERP HR

Procedure Create a new channel in the Integration Directory using Integration Builder:

Path In Integration Builder Communication Component Without Party Business System HR Right-click on Communication Channel New…

1. In the Communication Channel input field, enter the name of the sender channel to be created

(e.g. XI_Receiver_HR).



2. Leave the Party field empty (remove the * symbol) 3. Click on Create. 4. In the Parameters tab, select the Input help dialog button on the right side. 5. Choose XI as Adapter Type and press Apply. 6. Assign following data:

Transport Protocol HTTP 1.0

Message Protocol XI 3.0

Adapter Engine Integration Server

Addressing Type HTTP Destination

HTTP Destination <Destination defined in previous step for HR System>

7. Select check box Transfer Hop List. 8. Click the Save button to save the channel. 9. In the Objects tree on the left, right-click on the Communication Channel and select Activate…

from the context menu to activate the Communication Channel.

5.4.6.8 Create Configuration Scenario PersonnelHiringCreateRequestProcedure

Create a new Configuration Scenario in the Integration Directory using Integration Builder:

Path In Integration Builder Right-click on Configuration Scenario New…

1. Enter PersonnelHiringCreateRequest as Configuration Scenario. 2. Select Process Integration Scenario as Type of ES Repository Model. 3. Under ES Repository Model Reference(s) click on the Input Help… button. 4. Choose the PersonnelHiringCreateRequest (Namespace: http://sap.com/xi/EA-HR/Global2;

Software Component Version EA-HR 605) Process Integration Scenario from the list and click Apply.

5. Click on Create. 6. Click on Model Configurator. 7. For PI7.30: Select the check box Configuration for Advanced Adapter Engine on Java-only

environments (AEX). Skip this step for PI7.11 installation. 8. Select the ERecruiting component from the component view. 9. In section Assign Components for A2A Communication in the tab Assign Components on the

bottom, select the table cell Business System Components Component and click on the input help button.

10. Select the EREC Business System and click Apply. 11. Select the HR component from the component view. 12. In section Assign Components for B2B Communication in the tab Assign Components on the

bottom, select the table cell Communication Component and click on the input help button. 13. Select the HR Business System and click Apply. 14. Click on the Configure Connections… button. 15. Configure the connections of the scenario in the tab Connections from Component Assignment

on the bottom. Use the previously create communication channels. Use the Next Connection button to step through the connections of the scenario.

16. Click on Check Configurability to check if the configuration of the scenario is complete. 17. Click on the Model Configurator’s Save button to save your changes.



18. Click on the Create Configuration Objects… button. 19. Under Settings General select radio button Generation. 20. Click on Start and wait for the Generation Process to finish. 21. Close the Generation Log and click Apply in the Model Configurator. 22. Click on Save in the Edit Configuration Scenario view. 23. Switch to the Change Lists view, select your Standard change list, which contains the changes

made by the Model Configurator. Right-click on the change list and select Activate… from the context menu.

24. Click on Activate.

5.4.7 Client-Copy of Customizing tables Perform the following activities in the E-Recruiting system.

A sample Customizing is delivered for SAP E-Recruiting. The entries are only transported to client 000. Use the RHTTCP77 utility program (Copying client-dependent T77* tables from client 000). SAP E-Recruiting tables have the prefix 'T77RCF_'.

IMG Menu Tools -> Development -> ABAP Editor

Transaction Code SE38

1. Go to SE38, type in field Program RHTTCP77 . Execute.

2. Make the following entries and execute the report:

Field Entry Comment

Table name T77RCF_* This are all E-Recruiting Customizing tables

Target Client Xxx Custom client

Test mode, no DB update

Only add new entries X

Only compare changed entries

Transport X

Request Xxxxxx Enter the Request ID

3. In the following Popup there are listed all E-Recruiting-Customizing-Tables, T77RCF_ . Click on “Ok”-Button.

4. In the following screen you see the tables and the changes.

5. Go back to report start screen.


Field Entry Comment



Field Entry Comment

Table name T77RCF_* This are all E-Recruiting Customizing tables



Only add new entries

Only compare changed entries X

Transport X


7. In the following Popup there are listed all E-Recruiting-Customizing-Tables, T77RCF_ . Click

on “Ok”-Button.


5.4.8 Set System Parameters for SAP E-Recruiting and SAP ERP

For this activity consider your system landscape. In case of E-Recruiting running on another instance that HR please pay attention to the instructions in which system the settings are to be set. Some settings are architecure dependant. Please pay attention to the remarks. For each Personnel Number (P) in Personnel Management in an integrated system, a corresponding Candidate (NA) must exist in SAP E-Recruiting. For each employee, the Personnel Number (P) and Central Person (CP) objects must exist in Personnel Management. In addition, a Business Partner (BP) must exist for each Central Person (CP) if the (first) hiring date of the associated personnel number has been achieved. SAP E-Recruiting creates a Candidate (NA) for each Personnel Number (P) for which a Business Partner (BP) also exists. The HR master data for the personnel numbers is saved in PA infotypes. The data can be accessed using the classic or the decoupled infotype framework. The SAP E-Recruiting rapid-deployment solution is based on the classic infotype framework.

1. In your HR system use the following transaction:


2. Type V_T77S0 into field “Table/View” and click “Maintain”. 3. Verify that the following parameters are set accordingly.



Group Sem. Abbr. Value abbr.

Description

RECFA DTCBA *Logical system name*

- In a separated system enter the system name of your E-Recruiting system, e.g. RT5CLNT120 - If E-Recruiting runs on the same instance as HR enter the own system name

HRALX HRAC X This switch enables you to activate integration between HR Master Data and SAP Business Partner.

1. In your E-Recruiting system use the following transaction:


2. Type V_T77S0 into field “Table/View” and click “Maintain”. 3. Verify that the following parameters are set accordingly.


Description

CPERS PROLE BUP003

Determines the role that is assigned to an SAP Business Partner used in the system as an employee. Recommendation: SAP recommends you do not change this entry.

PLOGI PLOGI 01 Determines which plan version is active.

RECFA ACTPA X Specifies whether changes to the process assignments are possible via activities. The following switch settings are possible: - RECFA ACTPA = 'X' Changes to the process assignments via activities are possible. - RECFAACTPA = ' ' Changes to the process assignments via activities are not possible.

RECFA AGYRO RCFAGY

Determines the role that is assigned to an SAP Business Partner used in the system as an agency. Recommendation: SAP recommends you do not change this entry.

RECFA BGCDC 60 Duplicate Checking for Background Check Order Specifies in days the period in which repeated background checks are evaluated as duplicates. Example: The switch has the value 60 If another background check is performed for a candidate within 60 days of the previous background check, the system treats this new background check as a duplicate.




Description

RECFA BPCOU Country for Name Format of Business Partner Country for name format rule: The country for the name format rule is used together with the key for the name format rule to uniquely identify a format rule. Several name formats, each with different rules, can exist for one country.

RECFA BPNAM Name Format for Business Partner Name formatting: The name formatting determines the sequential order in which the various name parts are to be collected to display the name of a person in full form. A name format rule can be identified on the basis of a country key and a formatting key.

RECFA BRARO RCFBRA

Branch Rule in Business Partner Determines the role that is assigned to an SAP Business Partner used in the system as a branch. Recommendation: SAP recommends you do not change this entry.

RECFA CDCYL Formatting Mechanism of Assignment List The following switch settings are possible: -RECFA CDCYL = ' ' (default setting)

The system compiles entries in the lists at the time of the call (runtime) from the relevant data tables.

-RECFA CDCYL = 'DB' The system reads entries in the lists from buffered lists. The entries are therefore available immediately when the candidate lists are called.

RECFA DATAO Output Technology for Data Overviews Specifies the technology that the system uses to display the data overviews. The following switch settings are possible: - RECFA DATAO = ' ' Display using SAP Smart Forms (default setting) - RECFA DATAO = X Display using PDF-based forms

RECFA HIHIT 500 Maximum Number of Hits for All Search Requests

RECFA HRDAT No Maintenance of HR Data in E-Recruiting Specifies whether HR data can be changed on the candidate profile (for example, address data, communication data). The following switch settings are possible: - RECFA HRDAT = 'X' Data cannot be changed by the recruiter - RECFA HRDAT = ' ' Data can be changed by the recruiter




Description

RECFA HRQUA EREC_VIEW

Integration Switch for HR Qualifications Determines how qualifications for employees (in other words, internal candidates) can be maintained in the SAP E-Recruiting system and how they are included for recruitment purposes. Regardless of the setup of this switch, qualifications for external candidates can always be maintained in the E-Recruiting system. This only includes the qualification groups from the SAP qualifications catalog that are assigned to the SAP_ERECRUITING view for SAP E-Recruiting. You set up this view using the Customizing activity Restrict View of Qualifications Catalog. Depending on whether or not you distribute the qualifications for employees from your HR system to the SAP E-Recruiting system, you can make the following switch settings: - RECFA HRQUA = ' ' You do not distribute the qualifications for employees from your HR system in the SAP E-Recruiting system. This switch setting means that you can maintain the qualifications for internal candidates in the SAP E-Recruiting system. The system includes only the qualification groups from the SAP qualifications catalog that are assigned to the SAP_ERECRUITING view for SAP E-Recruiting. - RECFA HRQUA = 'X' You distribute the qualifications for employees from your HR system in the SAP E-Recruiting system. This switch setting means that you cannot maintain the qualifications for internal candidates in the SAP E-Recruiting system. The system takes into account the distributed qualifications overall. It is possible to distribute qualifications only if the qualifications are synchronized between Organizational Management and SAP E-Recruiting. To do this, the integration units 203 and 301 must be integrated in the Customizing activity Set Up Integration with SAP Organizational Management. - RECFA HRQUA = 'EREC_VIEW' You distribute the qualifications for employees from your HR system in the SAP E-Recruiting System. This switch setting means that you cannot maintain the qualifications for internal candidates in the SAP E-Recruiting system. The system takes into account only those distributed qualifications that are assigned to the 'SAP_ERECRUITING' view for SAP E-Recruiting. It is possible to distribute qualifications only if the qualifications are synchronized between Organizational Management and SAP E-Recruiting. To do this, the integration units 203 and 301 must be integrated in the Customizing activity Set Up Integration with SAP Organizational Management.




Description

RECFA HRRFC NONE / *System name*

SAP E-Recruiting and SAP ECC (SAP ERP Central Component) run on the same instance: As an RFC connection to the HR system is not required in this case, you must enter the value NONE for the switch.

Only relevant for separated scenario: - SAP E-Recruiting and SAP ECC (SAP ERP Central Component) run on different instances: This switch determines the RFC (Remote Function Call) connection to your HR system. To do so, enter the name of the RFC connection, e.g. RT5CLNT120.

RECFA HRXI X Determines that the data is not transferred from SAP E-Recruiting using an RFC (Remote Function Call) connection, but rather using SAP Exchange Infrastructure. Data is transferred from SAP E-Recruiting according to Set Up Data Transfer for New Employees. The following switch settings are possible: - RECFA HRXI = 'X' Data is transferred from SAP E-Recruiting using SAP Exchange Infrastructure. - RECFA HRXI = ' ' Data is not transferred from SAP E-Recruiting using SAP Exchange Infrastructure.

RECFA PBLSH Explicit Publications of Job Postings

RECFA PRODC 90 Period with Duplicates for Candidate Profiles

RECFA RECCE Concurrent Employment Active in E-Recruiting Syst.

RECFA VENRO RCFVEN

Role of Provider in Business Partner

4. Click on Save. The system will warn you to make any changes. 5. Click on Cancel and answer No if the system asks to discard the changes.

5.4.9 BadI Implementations

For this activity consider your system landscape.


If E-Recruiting runs on the same instance as HR please perform the following settings: 1. Activate the following Business Add-In Implementations (BAdI):

BAdI Implementation Status

HRSYNC_P CONV_HR_DATA_TO_EREC Active




HRALX_HRALXSYNC_BADI CHECK_INTER_NA_EXIST Active

HRPAD00INFTY HR_INTEGRATION_TO_B Active

HRPAD00INFTY HR_INTEGRAT_TO_EREC Active

HRBAS00INFTY HRRCF00_STORE_HRQUAL Active

2. Enter the BAdI Name in the corresponding input field and click Display. 3. In the menu click on Implementation Display and select the corresponding Implementation. 4. Go to Change mode and activate the Implementation. 5. Choose Save. 6. Create a transport request and save the entries.

If E-Recruiting runs another instance than HR please perform the following settings:


HRSYNC_P CONV_HR_DATA_TO_EREC Active

HRALE00INBOUND_IDOC HRRCF00_INBD_NEWMOD Active

HRALE00SPLIT_INBOUND HR_INTEGRATION_TO_B Inactive

HRALE00INBOUND_IDOC HRRCF00_DELETE_SPREL Inactive

7. In order to activate a BAdI Implementation proceed as described in steps 1. – 4. 8. In order to deactivate a BAdI Implementation enter the BAdI Name in the corresponding input

field and click Display. 9. In the menu click on Implementation Display and select the corresponding Implementation. 10. Go to Change mode and deactivate the Implementation. 11. Choose Save. 12. Create a transport request and save the entries.

5.4.10 Set Up ALE Connection (separated architecture)

For this activity consider your system landscape. Perform this activity only if E-Recruiting runs on a sparated server than the HR system.

1. In your SAP E-Recruiting System use the following transaction:

Transaction Code SALE

2. In screen Display IMG follow the following IMG menu path:



IMG Menu Idoc Interface / Application Link Enabling (ALE) Basic Settings Logical Systems Define Logical System

3. Choose New Entries. 4. In screen New Entries: Overview of Added Entries make the following entries:

Logical System Name

*enter the name of the RFC to your HR system, e.g. RT5CLNT120*

*Enter a name to identify your HR system*

5. Choose Save. 6. Create a transport request and choose Continue. 7. Repeat steps 1. to 6. In your HR system and enter the RFC connection to your E-Recruiting

system.

8. In your SAP E-Recruiting System use the following transaction and navigation path:


IMG Menu Idoc Interface / Application Link Enabling (ALE) Basic Settings Logical Systems Assign Logical System to Client

9. Choose New Entries. 10. In screen Change View “Clients”: Details make the following entries:

Field Name Value

Client *Enter a name to identify your client*

City *Enter a city*

Logical System *Enter the RFC name of the system and client your are logged in*

Client Role *Assign the appropriate status as client role*

Changes and Transports for Client-Specific Objects

Select: Automatic recording of changes

Cross-Client Object Changes Changes to Repository and cross-client Customizing allowed

Protection: Client Copier and Comparison Tool Protection level 0: No restriction

CATT and eCATT Restrictions eCATT and CATT Allowed

11. Choose Save. 12. Create a transport request and choose Continue. 13. Repeat steps 8. to 12. in your HR system.

14. In your SAP E-Recruiting System use the following transaction and navigation path:




IMG Menu Idoc Interface / Application Link Enabling (ALE) Communication Determine RFC Destinations for Method Calls

15. Select your system. 16. Choose Assign Standard BAPI destination (F5). 17. In the pop-up Assign RFC Destinations for Synchronization enter the RFC name of your HR

system. This ties your logical HR system to your ABAP connection. 18. Repeat steps 14. to 17. in your HR system and connect your logical E-Recruiting system to

your ABAP connection.

19. In your HR System use the following transaction and navigation path:

Transaction Code BD64

20. In the Display Distribution Model choose Switch between Display and Edit mode (F9). 21. Choose Create model view (Ctrl + F4). 22. In the pop-up Create model view enter a short text and a technical name. Choose Continue

(Enter). Choose Save. 23. Select your newly created model and choose Add message type. 24. In the pop-up Add message Type and enter the your HR system into the field Sender and your

E-Recruiting system in the field Receiver. As message type select HRMD_ABA. 25. Choose Save.

In the next step, the distribution model will be created and distributed to the E-Recruiting system.

26. In the screen Distribution Model Changed select your newly changed distribution model and expand all its nodes.

27. Double click on No filter set. 28. In the Change Filter pop-up choose Create Filter Group. 29. Expand all nodes. 30. Double click on Object Type. 31. In the pop-up Edit List of Values choose Insert Rows. 32. Make the following entries by creating a new filter group for each line:

Object P Infotype Subtype Type of related object

P 0000, 0001, 0002, 0003, 0006, 0024, 0105

O, S 1032 0010

S 1001 A003, A008, A012, B007

O 1001 A002, B002, B003, B012

O,S



Object P Infotype Subtype Type of related object

C, O, S 1000, 1002, 1028

C 1001 A007 S

33. Choose Save.

34. In the screen Distribution Model Changed select your newly changed distribution model and choose Environment Generate Partner Profiles.

35. In screen Generate Partner Profile enter your Partner System (-> E-Recruiting system). Choose Execute.

36. In the screen Generate Partner Profile the log confirms the generation.

37. In the screen Distribution Model Changed select your newly changed distribution model and choose Edit Model View Distribute. This places the distribution model in the receiving system.

38. In your E-Recruiting System use the following transaction:

Transaction Code BD64

39. In the screen Maintain Distribution Model select your now available distribution model and choose Environment Generate Partner Profiles.

40. In screen Generate Partner Profile enter your Partner System (-> HR system). Choose Execute.

41. In the screen Generate Partner Profile the log confirms the generation.

42. In your SAP HR System use the following transaction and navigation path:


IMG Menu Idoc Interface / Application Link Enabling (ALE) Modelling and Implementing Business Process Master Data Distribution Replication of Modified Data Activate Change Pointer - Generally

43. In the screen Activate Change Pointers Generally verify that the activation was successful.

In order to keep HR data updated in the E-Recruiting after the initial transfer (please refer to Configuration Guide F16), set up the following background job in your HR system.


1. On the Define Background Job screen, proceed as follows: 2. Choose Define Job using Wizard (Ctrl+F1). 3. On the Create a Job dialog box choose Continue.



4. On the General Job Information dialog box maintain the following entries:

Field Name Value

Job Name YN_HR_ALE_DATA

Job Class C – Low priority

Job Status Scheduled

Target Server

5. Choose Continue. 6. In the Job-Definition: Job step dialog box mark ABAP program step and choose Continue. 7. In the ABAP program step dialog box maintain the following entries:

Field Name Value

ABAP Program name RBDMIDOC

Variant

Execution language EN

8. Choose Continue. 9. In the Multi-step option dialog box choose Continue. 10. In the Job Definition: Start conditions screen choose Immediately. Then choose Continue. 11. In the Def. of start immediately dialog box check the box Period in the section Periodic jobs

and choose Continue. 12. On the Period definition dialog box choose None of the Above. 13. Select the button Other Periods. 14. In the pop-up Other Period schedule the service for every 10 -30 minutes. 15. Choose Create. 16. Choose Continue. 17. In the Set job pop-up choose Complete to finish the setup.

5.4.11 Set Up Communication Interface Perform the following activities in the E-Recruiting system.

1. Ensure that E-Mail connectivity is setup within the system.

Transaction Code SCOT and SM36

IMG Menu SAP E-Recruiting Technical Settings Set Up Communication Interface

2. Go to transaction SCOT.

Field Name Entry Value

SMTP Ensure that an SMTP server is designated and that a mail host and port are assigned.



3. Select SMTP and double-click on it. 4. Verifiy that the box “Node in use” is ticked. 5. In field “Mail Host” type in your company mail host (e.g. mailwdf.sap.corp). 6. In field “Mail Port” type in your Mail Port from which mails are to be sent (e.g. 25)

Field Name Entry Value

Job RSCONN01 Schedule mail send job RSCONN01 with variant SAP&CONNECTALL

7. In transaction SCOT select View Jobs. 8. If no other job is maintained go to Job Create. 9. Specify the name RSCONN01. 10. Choose the variant SAP&CONNECTALL by placing the cursor on it. 11. Choose Schedule. 12. Click on Schedule Periodically. 13. Select the period you wish to use (e.g. 5 minutes). 14. Click on Create.

5.4.12 Preparing Roles and Users E-Recruiting depends on communication and service users for the Content Server, Web interfaces, and other connectivity required. This section will show which of these are valid for our configuration.

Although there are standard roles delivered by SAP, it is recommended that you copy these to your customer namespace and setup profiles according to your organization’s security rules and guidelines.

5.4.12.1 Create User Profiles SAP delivers the following user profiles within the E-Recruiting installation. Create the profiles for the roles (or copy and /or change the roles depending on organizational requirements). 1. Define and setup profiles for the following roles in SAP E-Recruiting

IMG Menu SAP E-Recruiting Technical Settings User Administration Create User Profiles

Transaction Code PFCG

2. Go to transaction PFCG. 3. Select Tools and Mass Generation. 4. Select All Roles. 5. In field Roles type in SAP_RCF*. 6. Select Generate Automatically. 7. In the pop-up box select Online. 8. Validate the following roles.

Role Name Role Description

SAP_RCF_EXTERNAL_CANDIDATE External Candidate




SAP_RCF_INTERNAL_CANDIDATE Internal Candidate

SAP_RCF_UNREGISTERED_CANDIDATE Unregistered Candidate (Service User)

SAP_RCF_MANAGER Manager

SAP_MANAGER_MSS_NWBC Manager NWBC

SAP_RCF_RECRUITER_ERC_CI_2 Recruiter

SAP_RCF_RES_RECRUITER_ERC_CI_2 Restricted Recruiter

SAP_RCF_DATA_TYPIST_ERC_CI_2 Data Entry Clerk

SAP_RCF_REC_ADMIN_ERC_CI_2 Administrator

SAP_RCF_CONTENT_SERVER Search Engine Access

SAP_RCF_DATA_TYPIST_ERC_CI_2 Data Entry Clerk

SAP_RCF_ESS_SR_ERC_CI_4 E-Recruiting Services for ESS

SAP_RCF_MSS_SR_ERC_CI_4 E-Recruiting Services for MSS

SAP_RCF_MANAGER_SERVICE Manager Involvement

SAP_RCF_MSS_SR_ERC_CI_4 E-Recruiting Services for MSS

SAP_RCF_REC_ADMIN_SR_ERC_CI_4 Recruiting Administrator: NWBC

SAP_RCF_RECRUITER_SR_ERC_CI_4 Recruiter: NWBC

SAP_RCF_REQUISITION_REQUESTER Requester

5.4.12.2 Define and setup profiles for the following roles in HR ECC

Transaction Code PFCG

9. Define and setup profiles for the following roles in HR ECC:


SAP_ASR_EMPLOYEE HR Administrative Services : Employee

SAP_ASR_MANAGER HR Administrative Services : Manager

SAP_ASR_ADIMINISTRATOR HR Administrative Services : Administrator

SAP_ASR_HRADMIN_HCM_CI_3 HR Administrator NWBC Composite role

5.4.12.3 Create Special Users The following special users are required for various services in E-Recruiting:

Reference User Communication User Service User System User

Transaction Code SU01



IMG Menu SAP E-Recruiting Technical Settings User Administration Create Special Users

Users can be named according to your organization’s specifications. The names below are just examples, to be referred to in a later step.

Create reference users and assign the respective roles.

You create reference users to simplify authorization maintenance for users. To do so, you assign various roles to each reference user. When you then assign a reference user to a user, this user inherits all role attributes (authorization profiles) of the reference user.

1. Go to SU01, click on Create User. 2. Use the names provided in the table below. 3. Choose as User Type the entry L - Reference (Logon not possible). 4. Assign the appropriate user roles to the user (see table).

Reference User

Username

Role

Password

Name

YN_RCF_C_EXT SAP_RCF_EXTERNAL_CANDIDATE initial External candidate

YN_RCF_C_INT SAP_RCF_INTERNAL_CANDIDATE initial Internal candidate

YN_RCF_RECRU SAP_RCF_RECRUITER_ERC_CI_2 initial Recruiter

YN_RCF_RES_R SAP_RCF_RES_RECRUITER_ERC_CI_2 initial Restricted Recruiter

YN_RCF_ADMIN SAP_RCF_REC_ADMIN_ERC_CI_2 initial Administrator

YN_RCF_MANAG SAP_RCF_MANAGER initial Manager

YN_SAP_RCF_A SAP_RCF_MANAGER_ASSISTANT initial Manager Assistent

YN_RCF_DATA SAP_RCF_DATA_TYPIST_ERC_CI_2 initial Datatypist

5. Assign Reference Users to roles.

IMG Menu SAP E-Recruiting Technical Settings User Administration Roles in E-Recruiting Define Roles in E-Recruiting

Transaction Code SPRO



6. Verify/adjust the following entries:

Role

Name

Reference User

1 Candidate (internal) YN_RCF_C_INT

2 Manager YN_RCF_MANAG

4 Assistant Manager YN_SAP_RCF_A

5 Candidate (external) YN_RCF_C_EXT

6 Administrator YN_RCF_ADMIN

7 Recruiter YN_RCF_RECRU

9 Data Entry Clerk YN_RCF_DATA

13 Restricted Recruiter YN_RCF_RES_R

Create service users and assign the respective roles.

Some scenarios are accessible to registered users only, others are also accessible to unregistered users (registration, job postings, direct application). To enable an unregistered user to use these services, you must assign a service user to these services.

1. Go to SU01, click on Create User. 2. Use the name provided in the table below. 3. Choose as User Type the entry S – Service 4. Assign the appropriate user role to the user (see table).

Service User

Username

Role

Password

Name

E-Mail

YN_RCF_SERVI

SAP_RCF_UNREGISTERED_CANDIDATE initial

Not registered candidate

[email protected]

YN_MANSERV SAP_RCF_MANAGER_SERVICE initial1 MSS Scenario

Create communication users and assign the respective roles.

To enable documents of the document area to be accessed, create a user that is assigned to the service contentserver.



This user is a purely technical user that is only required for communication with the Web Application Server.

1. Go to SU01, click on Create User. 2. Use the name provided in the table below. 3. Choose as User Type the entry C-Communication Data 4. Assign the appropriate user role to the user (see table). Communication User

Username

Role

Password

Name

YN_RCF_CONTE SAP_RCF_CONTENT_SERVER initial Access to search engine

If E-Recruiting runs on a separated server from HR create also the following user in both SAP E-Recruiting and HR ECC system:

Username

Role

Password

Name

ALEUSER *assign a role that contains the authorization object B_ALE_RECV, e.g. SAP_PI_CCMS_SETUP*

initial ALE USER

Create system users and assign the respective roles.

In order to be able to use the workflow functionality, in standard a system user (e.g. WF-BATCH) has to be created. This user is automatically created via workflow-customizing. He must not be created manually. If the user doesn’t exist yet, please proceed with chapter “Automatic Workflow Customizing” first. In E-Recruiting it is also required to assign a candidate to this user.

1. Go to SU01, type in WF-Batch into user field. 2. Click on edit. 3. Flag the user as system user. 4. Assign the appropriate user role to the user (see table).

Also maintain printer and printing authorization profiles, especially the authorization for status changes in E-Recruiting objects (P_RCF_STAT). System User

Username

Role

Password

Name

WF-BATCH

SAP_RCF_EXTERNAL_CANDIDATE SAP_RCF_INTERNAL_CANDIDATE SAP_RCF_RECRUITER_ERC_CI_2 SAP_RCF_RES_RECRUITER_ERC_CI_2

initial Workflow User



SAP_RCF_REC_ADMIN_ERC_CI_2 SAP_RCF_MANAGER SAP_RCF_MANAGER_ASSISTANT SAP_RCF_DATA_TYPIST_ERC_CI_2

YN_RCF_SERVI SAP_RCF_UNREGISTERED_CANDIDATE initial Unregistered Candidate

5. Create a candidate for the user (WF-BATCH and YN_RCF_SERVI) 6. Use the report RCF_CREATE_USER in transaction SE38 to do so. This report also creates an E-

Mail Address.



7. Go to transaction SE38, type in field Program RCF_CREATE_USER. Execute. 8. Make the following entries and execute the report:

Field Entry Comment

First name Workflow Example

Last name System Example

User Name WF-BATCH

Personnel Number 99999999

Position 99999999

E-Mail Address [email protected] Enter an existing E-Mail

9. Repeat steps 5. – 8. with the following entries:

Field Entry Comment

First name YN_RCF_SERVI

Last name Not registered candidate

User Name YN_RCF_SERVI

Personnel Number 99999998

Position 99999998

E-Mail Address [email protected] Enter an existing E-Mail

Please note that in an integrated system the report RCF_CREATE_USER must not be used for the creation of any other user apart from WF-BATCH and YN_RCF_SERVI.



To enable communication between the SAP systems and PI, you have to create an RFC user. The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created. You have to maintain /check this step in SAP E-Recruiting and SAP ECC.

Procedure 1. Execute the following steps in E-Recruiting system. 2. Access the activity using one of the following navigation options:

SAP BW menu Tools Administration User Maintenance Users

Transaction code SU01

2. On the User Maintenance: Initial screen, enter the following data:

Field name Description User action and values Comment

User RFCDIAUSER

3. Choose Create. 4. On the Maintain User screen, enter the following data:

Address

Last Name RFCDIAUSER

Logon data

User type Communication

Password initial

Defaults

Logon Language EN

5. Choose Save. 6. Repeat the steps in the ECC system.

5.4.13 Verify SAP Business Partner Integration In E-Recruiting, the SAP Business Partner is used for both the personal data of all persons involved (such as candidates and employees) and for the addresses of the various branches of your company.

IMG Menu n/a


1. Verify that address type XXDEFAULT is existing in table TB009. 2. Verify titles for Ms./ Mr./ Company/ Mr. and Mrs. are maintained in V_TSAD3. 3. Verify the Academic Titles Dr./ Prof./ Prof. Dr./ B.A./ MBA/ Ph.D. in V_TSAD2.

IMG Menu SAP E-Recruiting Technical Settings SAP Business Partner Define Number Ranges

Transaction Code BUCF



4. Verify that the following number ranges are defined:

No. From Number To Number Current Number

Ext

01 0000000001 0999999999

AB A ZZZZZZZZZZ X

MD 9000000000 9999999999 X

IMG Menu SAP E-Recruiting Technical Settings SAP Business Partner Define Groupings And Assign Number Ranges


5. Verify one number range is flagged as “Internal Standard Grouping”: 0001 Int.no.assgnmnt Internal number assignment 01

5.4.14 Set Up Access to Documents Perform the following activities in the E-Recruiting system.

In this step, we will setup access to the Content Server.

IMG Menu SAP E-Recruiting Technical Settings Search Engine Set Up Access to Documents

Transaction Code SICF

1. In SICF choose Execute (F8), navigate to “Default Host sap bc contentserver” 2. In the “Logon Data” tab, enter in the user that you created as a communication user previously

and maintain the following fields:

Field Entry Comment

Procedure Required with Logon Data

Client Type in the client you are working in

User YN_RCF_CONTE See above

Password initial Same as given above

5.4.15 Maintain Procedure in Services Perform the following activities in the E-Recruiting system.



5.4.15.1 Set procedure to Required with Logon Data 1. Access the activity using one of the following navigation options:

IMG Menu n/a


2. On the Maintain service screen make the following entries:

Virtual Host Service Path

DEFAULT_HOST /sap/bc/erecruiting/password

3. Choose Apply Filter 4. Double cklick on the service 5. On the Create/Change a Service screen choose Change (Ctrl +F1) 6. Choose the tab strip Logon Data set the Procedure to Required with Logon Data and maintain the

following data:

Client User Password

<Your Client> YN_RCF_SERVI initial

7. Choose Store (Ctrl+S) to save your changes. 8. Repeat the steps 1 to 7with the following data:


DEFAULT_HOST /sap/bc/erecruiting/registration

DEFAULT_HOST /sap/bc/erecruiting/confirmation_e

DEFAULT_HOST /sap/bc/erecruiting/confirmation_i

DEFAULT_HOST /sap/bc/erecruiting/qa_email_e

DEFAULT_HOST /sap/bc/erecruiting/qa_email_i

DEFAULT_HOST /sap/bc/erecruiting/applwzd

DEFAULT_HOST /sap/bc/erecruiting/posting_apply

DEFAULT_HOST /sap/bc/erecruiting/startpage

DEFAULT_HOST /sap/bc/erecruiting/verification

DEFAULT_HOST /sap/bc/bsp/sap/hrrcf_wd_dovru

DEFAULT_HOST /sap/bc/webdynpro/sap/hrrcf_a_candidate_registration

DEFAULT_HOST /sap/bc/webdynpro/sap/hrrcf_a_posting_apply

DEFAULT_HOST /sap/bc/webdynpro/sap/hrrcf_a_pw_via_email_extern

DEFAULT_HOST /sap/bc/webdynpro/sap/hrrcf_a_pw_via_email_intern

DEFAULT_HOST /sap/bc/webdynpro/sap/hrrcf_a_unregemp_job_search

DEFAULT_HOST /sap/bc/webdynpro/sap/hrrcf_a_unreg_job_search



DEFAULT_HOST /sap/bc/webdynpro/sap/hrrcf_a_posting_apply_emp

DEFAULT_HOST /sap/bc/webdynpro/sap/ hrrcf_a_candidate_verification

DEFAULT_HOST /sap/bc/webdynpro/sap/hrrcf_a_new_verif_mail

DEFAULT_HOST /sap/bc/webdynpro/sap/hrrcf_a_emp_job_search

5.4.15.2 Set procedure to Standard 1. Access the activity using one of the following navigation options:

IMG Menu n/a


2. On the Maintian service screen make the following entries:


DEFAULT_HOST /sap/bc/webdynpro/sap/hrrcf_a_refcode_srch

3. Choose Apply Filter 4. Double cklick on the service 5. On the Create/Change a Service screen choose Change (Ctrl +F1) 6. Choose the tab strip Logon Data set the Procedure to Standard and maintain the following data:

Client User / Password Comment

<Your Client> YN_RCF_SERVI / initial Service User

7. Choose Store (Ctrl+S) to save your changes. 8. Repeat the steps 1 to 7 with the following data:


DEFAULT_HOST /sap/bc/webdynpro/sap/hrrcf_a_applwizard

DEFAULT_HOST /sap/bc/webdynpro/sap/hrrcf_a_refcode_srch_int

5.4.16 Initialize KPro Directory Structure for SAP E-Recruiting This sets up the content server structure.

Transaction Code OO_RCF_INIT_KPRO

IMG Menu SAP E-Recruiting Technical Settings Search Engine Initialize KPro Directory Structure for SAP E-Recruiting

A report will run that initializes the directory structure.

5.4.17 Clean Up Change Pointers This ensures that no change pointers exist when you perform your first (full) index.



Transaction Code OO_HRRCF_CPOINTER

IMG Menu SAP E-Recruiting Technical Settings Search Engine Clean Up Change Pointers

5.4.18 Check the RFC connection to TREX (Text Retrieval and Information Extraction)

Perform the following activities in the E-Recruiting system. To do so, in the Display and Maintenance of RFC Destinations view (transaction SM59), select the RFC destination IMSDEFAULT in the menu tree for RFC Destinations under TCP/IP Connection. Ensure that this RFC destination works properly.

5.4.19 Workflow Customizing

Perform the following activities in the E-Recruiting system.

5.4.19.1 Automatic Workflow Customizing In order to automatically generate and send correspondence to the candidate the workflows need to be activated.

Ensure that the RFC destinations and other customizing are setup correctly before activating.

Transaction Code SWU3

The transaction opens the window: Automatic Workflow Customizing The screen consists of a left area where a tree structure is shown containing 5 top node headlines for the corresponding sub-nodes that need to be activated. Each top node can be unfolded by left click on the “arrow” in front of the top node headline text. The right side of the screen show the documentation for each step – the documentation is shown when you place the cursor and left-click on the heading at the left side of the screen.

Not all of the steps can be automatically activated. And not all of the steps should be activated – it fully depends on the functionality required by the customer.

1. Unfold the structure of the first top node: Maintain Runtime Environment

a. Mark the node by placing the cursor upon this and left click. In the right side of the screen you will see the explanation for the chosen top node and a list of the sub-nodes that can be activated automatically.



2. Go to the menu bar and click the icon Perform automatic workflow customizing 3. Result: All the sub-nodes that can be automatically activated in the top node; Maintain

Runtime Environment is activated and get a green tick mark to show this.

Headline: Maintain Runtime Environment

Automatic Activated Step Configure RFC Destination

Automatic Activated Step Maintain Workflow System Administrator

Automatic Activated Step Maintain Active Plan Version

Automatic Activated Step Classify Decision Task as General

Automatic Activated Step Document Generation/Form Integration

Automatic Activated Step Schedule Background Job for Missed Deadline

Automatic Activated Step Schedule Background Job for Work Items with Errors

Automatic Activated Step Schedule Background Job for Condition Evaluation

Automatic Activated Step Schedule Background Job for Event Queue

Automatic Activated Step Schedule background job for clearing tasks

4. Go through the sub-nodes one by one by placing the cursor on the sub-node and press the

execute icon in the blue bar or press <F8>. Verify the setup as follows; 5. Choose the sub-node; Configure RFC Destination

a. Verify that the user is correct – if not change it accordingly. 6. Choose the sub-node; Maintain Workflow System Administrator

a. Verify that the user is correct – if not change it accordingly. 7. The sub-node; Maintain Active Plan Version, contains the setting from T77S0, this should be

accurate. 8. There should be no change needed to the sub-node; Classify Decision Task as General 9. There should be no change to needed to the sub-node; Document Generation/Form

Integration 10. Manual setup is needed within the sub-node; Maintain Time Units

a. For the Dimensions choose the value “(no dimensions)” in the selection box b. For ISO codes, standard values are provided, check the entries c. For Units of measurements standard values are provided, check the entries

11. There should be no change needed within the sub-node; Schedule Background Job for Missed Deadline

a. Verify the name of the job and the “Interval until next deadline check” and if necessary adjust it according to company requirement

12. There should be no change needed within the sub-node; Schedule Background Job for Work Items with Errors

a. Verify the name of the job and the “Interval until next rerun” as well as “Repeat counter for work items with errors” and if necessary adjust it according to company requirement

13. There should be no change needed within the sub-node; Schedule Background Job for Condition Evaluation

14. There should be no change needed within the sub-node; Schedule Background Job for Event Queue

a. Navigate to the tab “Basic data”; Verify the name of the Administrator b. Navigate to the tab “Background job”; Verify the

i. “Time interval between two read access”



ii. “Interval until event queue next checked” iii. To see the job name; Push the button “Display Background Job”

15. There should be no change needed within the sub-node; Schedule Background Job for clearing tasks

16. Mark the second top node: Maintain Definition Environment a. Mark the node by placing the cursor upon this and left click. In the right side of the

screen you will see the explanation for the chosen top node and a list of the sub-nodes that can be activated automatically.

17. There are none of the sub-nodes that can be activated automatically. 18. Go through the sub-nodes one by one by placing the cursor on the sub-node and press the

execute icon in the blue bar or press <F8>. Verify the setup as follow; 19. Choose the sub-node; Maintain Prefix numbers

a. Setup the Prefix numbers according to the instructions given on the right side of the screen. As an ex. This could be 900

20. Choose the sub-node; Check Number Ranges a. In case of number range errors follow the instructions given on the right side of the

screen. 21. Choose the sub-node; Check Entries from HR Control Table

a. Follow the instructions given on the right side of the screen. 22. Mark the third top node: Maintain Additional Settings and Services



Additional Settings and Services are activated and get a green tick mark to show this.

Headline: Maintain Additional Settings and Services

Automatic Activated Step Activate Send to Objects and HR Objects

Automatic Activated Step Maintain Demo and Verification Environment


execute icon in the blue bar or press <F8>. Verify the setup as follow; 26. Choose the sub-node; Maintain Web Server

a. This sub-node has to be manually configured if your Company wants to execute workflows that use WebFlow functions. When executing this sub node, click on creating a new Service for Webflow (Intranet), assign an Address for the web server (e.g. http://uxai2rt5.wdf.sap.corp:50015/) , specify the protocol. In the optional extensions you can enter e.g. SAP/BC/WORKFLOW_XML/?. Save your entries.

27. Chose the sub-node; Maintain Standard Domain for Internet Mail a. Setup the standard domain for the current system according to the instructions on the

right side of the screen. 28. There should be no change needed to the sub-node; Activate Send to Objects and HR

Objects a. This sub-node only has to be activated if your Company want the workflow system is

to send work items and mails to business objects and organizational objects (positions, organizational units, etc.) in the Business Workplace

29. There should be no change needed to the sub-node; Maintain Demo and Verification Environment

30. Mark the fourth top node: Classify Tasks as General

http://uxai2rt5.wdf.sap.corp:50015/






Headline: Classify Tasks as General

Automatic Activated Step Test Workflows

Automatic Activated Step Customizing with Workflow

Automatic Activated Step Unit Test

Automatic Activated Step IDoc Interface

Automatic Activated Step SAPphone

Automatic Activated Step Processing of Replies to Appointment Request

33. There should be no change needed within the sub-node listed above – Go through the sub-nodes one by one by placing the cursor on the sub-node and press the execute icon in the

blue bar or press <F8> to Verify the setup and get familiar with the settings. 34. Mark the fifth top node: Guided Procedures




Headline: Guided Procedures

Automatic Activated Step Maintain Generation of Standard Tasks

Automatic Activated Step Classify Generic Standard Tasks as General


execute icon in the blue bar or press <F8>. Verify the setup as follow; 38. Choose the sub-node; Maintain Guided Procedures Gateway

b. This sub-node has to manually be configured if your Company want to use guided procedures. See instructions on the right side of the screen.

39. There should be no change needed for the sub-node; Maintain Generation of Standard Tasks 40. There should be no change needed for the sub-node; Classify Generic Standard Tasks as

General

A simple verification workflow is delivered as part of the system, to verify that the system really is ready for workflow. Press the Start Verification Workflow (F5) icon in

the blue bar this configures and triggers a workflow in the background. A confirmation message is displayed to inform that the workflow has been triggered. Viewing the long text of this message, you will see instructions about what to do next. (You can use transaction SBWP to get to the Business Workplace).

5.4.19.2 Activate Workflow Services /sap/bc/sap/ , Services wshandler, webflow, workflow_xml




IMG Menu n/a

1. Go to services path /sap/bc/sap/ 2. Make sure the following services are activated:

a. wshandler b. webflow c. workflow_xml

5.4.19.3 Maintain WebFlow Service Handler Transaction Code WF_HANDCUST

IMG Menu n/a

1. Navigate through all the tabs individually and generate the Handlers and Dialogs automatically. 2. Save your entries.

5.4.19.4 Activate Event Linkage for SAP E-Recruiting Workflows

Transaction Code n/a

IMG Menu SAP E-Recruiting Technical Settings Workflow



1. Go to “Assign Requested Replacement Password (Workflow)” and execute it. 2. In column “Event Linkage” double-click on “Activate Event Linking”. 3. Select the events step-by-step and double click on the icon “Activate/deactivate”. 4. Tick the box in the pop-up “Event linkage activated”. 5. Save your entries. Perform steps 1-5 also for the following workflows:

Workflow After Candidate's Request to Delete Registration Workflow After Creating E-Recruiting Objects Send Requested Confirmation Mail (Workflow) Workflow After Status Changes to E-Recruiting Objects Workflow After Creating Activities Workflow After Data Entry Error

5.4.20 SAP Search Engine Service Settings Perform the following activities in the E-Recruiting system.

5.4.20.1 Set Up Indices of SES Business Object

Use The purpose of this activity is to set SES Index Monitor.

Procedure 1. Access the activity using one of the following navigation options:

ECC menu Tools Administration Monitor Search Engine SES Index Monitor

Transaction code SES_ADMIN

2. If you meet the message like RFC destination in table COM_SE_SEARCH is not defined.

3. Choose from menu: Goto -> Customzing -> System settings. On the Display View “Search Engine Service: System Settings”: Details Screen, choose Display -> Change, and then enter the values shown below.

Field name Description User action and values Note

RFC Destination RFC server’s name For example TREX_RD5_002

4. Choose Save and choose Back. 5. On the Search Engine Service: Admin screen, choose menu: Index Create/Activate Indexes. 6. Select the following Bus.Objects as below:

Business Object Object Type

AES_DOC 00000001

AES_DOC 00000100

ERC_CAND NA



ERC_CAND NA

ERC_CDCY NE

ERC_REQ NB

EXT_POST NC

INT_POER NC

7. Choose Continue (Enter) to create the business objects.

Ensure that each time you delete and recreate indexes (via SES_ADMIN) that you run RCF_SES_JOIN_INDEX_CREATE before performing the first full index run.

Result The SES Index was defined.

5.4.20.2 Run Reports for Search Initialization Transaction Code SE38

Run the following reports:

Report Name RCF_QA_UPDATE_CATEGORY RCF_SES_JOIN_INDEX_CREATE RCF_SES_TEMPLATES_ADAPT

5.4.20.3 Performing the First Full Index Run This index run will be the initial “Full” index run in foreground or background. Once this is performed, we will schedule a Delta indexing job to catch all of the changes.

5.4.20.3.1 Running the Full Index in the Foreground 1. Access the activity using one of the following navigation options:

ECC menu Tools Administration Monitor Search Engine SES Index Monitor

Transaction code SES_ADMIN

2. Select the following Bus.Object as below:


AES_DOC 00000001

3. Choose button Index Immediately. 4. Choose Full. 5. Repeat the steps 2 to 4 with the following entries:


AES_DOC 00000100



ERC_CAND NA

ERC_CAND NA

ERC_CDCY NE

ERC_REQ NB

EXT_POST NC

INT_POER NC

5.4.20.3.2 Running the Full Index in the Background


Run the report COM_SE_DISPATCHER

Report COM_SE_DISPATCHER

In COM_SE_DISPATCHER, we run each SES index individually in the background. These jobs can run in parallel.

Field Name Value

Business Object EXT_POST

Object Type NC

Indexing Type Full Index

Object Indexing X

Relation Indexing X

1. Choose “Program” “Execute in Background” 2. Define Printer (to create spool only) 3. Choose Immediate .

Progress can be monitored for this index via TCODE SES_ADMIN.

If there have been no documents created, the indexes will remain in the state of “initial”. If this is the case, ensure there are documents in the object type, and then restart.

4. Repeat the Procedure with the same parameters for the following Objects and Types:


EXT_POST NC

INT_POER NC

AES_DOC 00000100



ERC_CAND NA

ERC_CDCY NE

5.4.20.4 Schedule Background Process for Periodic Services Transaction Code SPRO

IMG Menu SAP E-Recruiting Technical Settings Periodic Services Schedule Background Process for Periodic Services

Periodical Services runs the delta indexing, as well as management of the Search Profiles. We schedule this to run every 10-30 minutes (depending on business requirements).


15. On the Define Background Job screen, proceed as follows: 16. Choose Define Job using Wizards (Ctrl+F1). 17. On the Create a Job dialog box choose Continue. 18. On the General Job Information dialog box maintain the following entries:

Field Name Value

Job Name RCF_PERIODICAL_SERVICES

Job Class C – Low priority

Job Status Scheduled

Target Server

19. Choose Continue. 20. In the Job-Definition: Job step dialog box mark ABAP program step and choose Continue. 21. In the ABAP program step dialog box maintain the following entries:

Field Name Value

ABAP Program name RCF_PERIODICAL_SERVICES

Variant

Execution language EN

22. Choose Continue. 23. In the Multi-step option dialog box choose Continue. 24. In the Job Definition: Start conditions screen choose Immediately. Then choose Continue. 25. In the Def. of start immediately dialog box check the box Period in the section Periodic jobs

and choose Continue. 26. On the Period definition dialog box choose None of the Above. 27. Select the button Other Periods. 28. In the pop-up Other Period schedule the service for every 10 -30 minutes. 29. Choose Create. 30. Choose Continue. 31. In the Set job pop-up choose Complete to finish the setup.



5.4.20.5 SES Change Pointer

In this IMG activity, you correct a missing entry in the SES. Please perform this activity in the SAP E-Recruiting system.

Please note that this activity can only be performed after questionnaires have been created via the frontend of the SAP E-Recruiting system.

Transaction Code PHAP_CATALOG

1. In the left side menu screen Category Group / Category / Template choose expand entry E-

Recruiting. 2. Choose Evaluable Information and double click on it. 3. On the right side in Category Group E-Recruiting and Category Evaluable Information

navigate to tab Enhancements. 4. In the right column Available choose entry Follow-Up Processing (Background) ->

WRITE_CPOINTER_SES and transport it to the column Selected. 5. Choose Save.

5.5 Activating a Solution Perform the following activities in the E-Recruiting system if you want to do the automated

configuration via Solution Builder. Due to the complexity or technology base the automated configuration still requires manual steps to be performed. For a manual configuration without Solution Builder please check the respective configuration guides.

Step 1: Import the Solution File 1. To run the SAP Best Practices solution builder, from the Command field, enter /n/smb/bbi and

press Enter. 2. On the Solution builder – solution editor screen, from the menu, choose Solution Import. 3. On the Select one format to import dialog box, choose the Import XML file button. 4. On the Select the XML file dialog box, browse to the location of your XML file (in the folder you

created during step Creating a Folder for the SAP Best Practices Activation, see above), select it, and choose Open.

5. Set the uploaded solution as the favorite solution: choose Solution Set Favorite.

Step 2: Set Document Path for Solution Builder

Use This activity sets the document path for information that may be useful during activation so that users can find details from the SAP Help Portal about the scenario being activated.

Procedure 1. From the SAP Best Practices solution builder menu, choose Goto User Settings. 2. Choose the External Documents tab. 3. Choose the Display <> Change button. 4. Choose the Insert Row button.




Parameter Value

DOCUMENTATION http://help.sap.com/saap/sap_bp/

6. Choose Save.

7. Choose Back.

Step 3: Upload the Installation Data The purpose of this step is to upload the installation data to the solution builder. This step is mandatory even if you do not want to personalize your solution. 1. From the SAP Best Practices solution builder main menu, choose Upload Installation Data (Ctrl +

F5). On the Upload installation data dialog box, browse to the location of your installation data files (in the folder you created during step Creating a Folder for the SAP Best Practices Activation, see above), select it, and choose Continue (Enter).

Step 4: Starting Activation 6. Ensure that your solution is set as a favorite solution. 7. From the menu, choose Goto Implementation Assistant (Ctrl + Shift + F3). 8. Select the top node of the solution, then choose the Activate button. 9. On the Activate solution dialog box, make the following entries:


Comments

Target language

EN You can also use target language EN only.

Supplemental data

<location of folder with graphic file smb40_leaf.bmp > e.g. Z:\sme\files

Use the folder that was created in step Creating a Folder for the SAP Best Practices Activation. In that folder the graphic file smb40_leaf.bmp is available. You can also select another folder if you ensure that the graphic file smb40_leaf.bmp is available in that folder.

You cannot use UNC paths (e.g. \\dwdf030\SME\...).

Always use a mapped network drive (e.g. Z:\SME ) Also it is not possible to use any root directory of your local drive (e.g. Z:\ or C:\)

Workbench <workbench request number>

By default this field and the Workbench Request button are not active because the Create Request checkbox is selected. The system will create the workbench request automatically when the Create Request checkbox is selected . If you would like to manually create or select an existing transport, deselect the Creat Request checkbox.

Customizing <customizing request number>

By default this field and the Customizing Request button are not active because the Create Request checkbox is selected. The system will




Comments

create the customizing request automatically when the Create Request checkbox is selected . If you would like to manually create or select an existing transport, deselect the Creat Request checkbox.

Skip this screen

Deselect If selected, the system will not display the Activate solution dialog box upon resumption of activation following an error or manual activity. If deselected, the Activate solution dialog box will display every time after resumption of activation.

With demo data

Select If selected, system executes activation steps that create demo data. If deselected, these steps are not executed.

Activation w/o demo data – What does this mean? If you want to activate the Baseline package without demo data, you can deselect the checkbox to turn off activation of demo data. After activation is completed, you will not be able to test the business scenarios. The scenario testing requires the presence of the demo data and related configuration settings. To test the business processes with customer demo data, you can create your own demo data. Proceed as follows: Select the business scenario you want to test Check the row in the Prerequisites Matrix file for this scenario to determine the

required prerequisite building blocks. Goto the Solution Builder Building Block Builder – Scenario Edit View. For all Building Blocks that belong to the scenario have a look at the steps that have

the check box activated in column De (Demo). Refer to the corresponding Configuration Guide and create the required configuration

and master data activities manually.

Errors occur during activation – Where can I find more information to solve the issue?

In case of any issues during activation always check chapter: Error Handling: Installation Errors during activation

10. Choose Continue.

Manual Step handling There are some manual steps that you will need to handle during activation. The solution builder will display a procedure dialog box with instructions for you to follow to process the step. The table below lists these manual steps as they are part of the default full scope activation:

Building Block Number

Building Block Title Step Name Manual requirement

F14 Configuration of E-Recruiting

Set-up Background Jobs Set up Background Jobs for SAP E-Recruiting rapid-deployment solution





F14 Configuration of E-Recruiting

BADi:Generate Reference Codes

Activate BAdI to Generate Reference Codes for SAP E-Recruiting rapid-deployment solution

F16 Master Data for E-Recruiting

Create organizational Structure

Create Create organizational structure for SAP E-Recruiting rapid-deployment solution


Creating Persons Creating persons for SAP ERP rapid deployment solution of E-Recruiting


Maintain Personnel Data Maintaining Personnel Data for SAP ERP rapid deployment solution of E-Recruiting


Maintain Qualifications Creating Qualifications for SAP E-Recruiting rapid-deployment solution


Assigning Qualifications Assigning Qualifications to the vacant position and to a person for SAP E-Recruiting rapid-deployment solution


Creating a support group Creating a Support Group for SAP E-Recruiting rapid-deployment solution


Creating as talent group Creating a Talent Group for SAP E-Recruiting rapid-deployment solution


Creating Questions Creating Questions for SAP E-Recruiting rapid-deployment solution


Creating Questionnaires Creating Questionnaires for SAP E-Recruiting rapid-deployment solution


Creating a Process Template

Creating a Process Template for SAP E-





Recruiting rapid-deployment solution


Creating Candidate for Talent Pool

Creating candidate for Talent Pool for SAP E-Recruiting rapid-deployment solution


Creating internal Candidate

Creating internal candidate for SAP E-Recruiting rapid-deployment solution

5.6 Post-Activation Activities 5.6.1 SAP ERP Central Component (ECC) Integration

5.6.1.1 Set Up Integration with SAP Organizational Management Perform the following activities in the E-Recruiting system.

In this IMG activity, you specify what data is to be synchronized in the context of the integration between Organizational Management and E-Recruiting.

This activity is needed whether you run SAP ECC (SAP ERP Central Component), Human Resources Extension (EA-HR) with the SAP E-Recruiting Add-On in the same system or in two separate SAP ECC systems.


IMG Menu SAP E-Recruiting Technical Settings SAP ERP Central Component (ECC) Integration Set Up Integration with SAP Organization Management

1. In the “Organizational Management Integration” screen activate the data you want to integrate

by setting the Integrated indicator. 2. Click on change. The system will warn you not to make any changes. 3. Click on Cancel and respond no if you want to discard the changes. Repeat these steps for all

the entries.

Integration Name Objecttype

Integrated Extractor Class

100 Description O X CL_HRRCF_OIX_DESCRIPTION

101 Account Assignment Features

O X CL_HRRCF_OIX_ACCOUNTING

102 Tasks O X CL_HRRCF_OIX_TASKS



Integration Name Objecttype

Integrated Extractor Class

103 Working Time O X CL_HRRCF_OIX_WORKINGTIME

200 Description S X CL_HRRCF_OIX_DESCRIPTION

201 Account Assignment Features

S X CL_HRRCF_OIX_ACCOUNTING

202 Employee Group and Subgroup

S X CL_HRRCF_OIX_EEGROUP

203 Requirements S X CL_HRRCF_OIX_REQUIREMENTS

204 Tasks S X CL_HRRCF_OIX_TASKS

205 Working Time S X CL_HRRCF_OIX_WORKINGTIME

206 Holder S X CL_HRRCF_OIX_HOLDERS

207 Vacancy S X

300 Description C X CL_HRRCF_OIX_DESCRIPTION

301 Requirements C X CL_HRRCF_OIX_REQUIREMENTS

302 Tasks C X CL_HRRCF_OIX_TASKS

5.6.1.2 Set Up Aliases in SAP Portal

The SAP NetWeaver Portal needs to be installed and user management and the system landscape needs to be setup for the connected backend systems (SAP ERP HCM, SAP E-Recruiting).

Prerequisites

To assign a system alias a system needs to be created first. The system defines a connect to a specific back-end application. For more information including installation and upgrade documentation, how-to guides, and a list of central SAP notes for the portal please check the SAP Service Marketplace at http://service.sap.com/nw70doc.

Use

In this activity, you specify the system alias for the applications.

Aliases are names that system administrators define for each system they create so that portal components can reference these systems. They are a means of retrieving the information stored on database servers without having to know the name of the server.

1. In the SAP Portal navigate to the tab System Administration

http://service.sap.com/nw70doc



Portal Menu System Administration System Configuration Detailed Navigation System Landscape Browse Portal Content

Systemlandscape

For this activity mind your system landscape. If your E-Recruiting runs on the same system as HR please continue as follows:

2. Choose your system. 3. Use the right mouse click, select Open System Aliases 4. Make the following entries by choose Add:

Default Alias Name

X SAP_ECC_ERecruiting

SAP_ECC_HumanResources

SAP_EREC_TalentManagement

If your E-Recruiting runs on another system than HR, please assign the Aliases accordingly:

5. Choose your HR system. 6. Use the right mouse click, select Open System Aliases 7. Make the following entries by choose Add:

Default Alias Name

X SAP_ECC_HumanResources

8. Choose your E-Recruiting system. 9. Use the right mouse click, select Open System Aliases 10. Make the following entries by choose Add:

Default Alias Name

X SAP_ECC_ERecruiting

SAP_EREC_TalentManagement

11. Choose Save.

5.6.2 Client-Copy of Processes and Forms Customizing tables in HR system

Perform the following activities in the HR system. A sample Customizing is delivered for SAP HR. The entries are only transported to client 000.



Use the RHTTCP77 utility program (Copying client-dependent T77* tables from client 000). SAP Processes and Forms tables have the prefix 'T5ASR*'.



1. Go to SE38, type in field Program RHTTCP77 . Execute.


Field Entry Comment

Table name T5ASR* This are all Processes and Forms Customizing tables



Only add new entries X

Only compare changed entries

Transport X


3. In the following Popup there are listed all Processes and Forms-Customizing-Tables, T5ASR*. Click on “Ok”-Button.


5. Go back to report start screen.


Field Entry Comment

Table name T5ASR* This are all Processes and Forms Customizing tables



Only add new entries

Only compare changed entries X

Transport X


7. In the following Popup there are listed all Processes and Forms-Customizing-Tables, T5ASR*.

Click on “Ok”-Button.




5.6.2.1 Required Customizing in HR System

Perform the following activities in the HR system.

The SAP E-Recruiting rapid-deployment-solution requires a fully customized HR system. This is not included in the scope of the SAP E-Recruiting rapid-deployment-solution but is considered as a prerequisit. Please follow the instructions in the IMG help of the corresponding activities.

The following sections are required:

Processes and Forms

IMG Menu Personnel Management HR Administrative Services Configuration of Forms / Processes

Workflows

IMG Menu SAP NetWeaver Application Server Business Management SAP Business Workflow

Manager Self-Service

IMG Menu Personnel Management Manager Self-Service (Web Dynpro ABAP) Recruiting

5.6.2.1.1 RDS Specific Configuration in HR System

The configuration of the HR system and Processes and Forms is considered as a prerequisit. The following configuration description concerns only the RDS E-Recruiting relevant process steps. For information beyond this please refer to the SAP configuration guide IMG.



5.6.2.1.1.1 Maintain Variables for RFC Destinations in the Workplace

For this activity consider your system frontend. This activity is only required if you use the NetWeaver Business Client. Use: The NetWeaver Business Client role SAP_MANAGER_MSS_NWBC is assigned to the manager in the HR system and requires to point the alias to the E-Recruiting system. In case of a separated system landscape the alias should be maintained in the HR system and should point to the E-Recruiting system. 1. Access the transaction using the following navigation path:

Transaction Code SM30_SSM_RFC

2. In the Change View “Variables for RFC Destinations in the Workplace” screen choose New Entries.


Variable RFC Destination

SAP_EREC_TALENTMANAG *Enter your E-Recruiting systems RFC connection *

4. Choose Save (Ctrl +S).

Result: The alias now points to the correct system.

5.6.2.1.1.2 Assign E-Recruiting System Name

For this activity consider your system landscape. In case of E-Recruiting and HR running on different servers perform this activity in the HR system. Use: In this activity you assign an E-Recruiting system name to enable you to access data in the E-Recruiting system.



IMG Menu Integration with Other SAP.com Components Business Packages / Functional Packages Manager Self Services (ERP) Recruitment

Assign E-Recruiting System Name

44. On the View T5UA0 screen, make the following entries:



Group RQ Sem. Abb

Semantic Abbreviation Value

Text

ERMSS LOGSY *Enter the E-Recruiting System name* e.g. RT5CLNT120

Logical System for RFC connection with ERecruiting

Result: The system name for the E-Recruiting has been assigned.

5.6.2.1.1.3 Disable Recruitment Requisition Request (HR_MSSRCF_REQUISITION)

Use

In this activity, you disable the standard process Recruitment Requisition Request (HR_MSSRCF_REQUISITION) to enable the SAP E-Recruiting rapid-deployment Processes and Forms process.

Transaction Code HRASR_DT

1. In the Design Time for Processes and Forms screen, enter Process and HR_MSSRCF_REQUISITION.

2. Choose Enter 3. Choose Expand All 4. Double click on Role Assignment. 5. In the section Roles That Can Start the Process delete the role HRASRB. 6. Choose Save (Ctrl+S)

Result:

The standard process Recruitment Requisition Request is now disabled in order to enable the SAP E-Recruiting rapid-deployment solution process.

5.6.2.1.1.4 Continue Without Design Time Use

In the following activity the dialog box New Design Time for Processes and Forms Available will be prompted. This content deployment continues with IMG activities only.

Procedure

1. On the dialog box New Design Time for Processes and Forms Available choose Info.

2. On the dialog box Help - New Design Time for Processes and Forms click on the red highlighted word here at the end of the sentence "If you do not want to display the message in the future, you can switch it off here."



3. On the dialog box Switch Off Message choose Yes

4. On the dialog box - Help - New Design Time for Processes and Forms choose Continue (Enter).

5. On the dialog box New Design Time for Processes and Forms Available choose Continue Without Design Time.

Result

The content deployment continues without Design Time using the IMG activity. If you want to use the New Design Time for Processes and Forms at a later time instead of the IMG activities you can switch to the New Design Time for Processes and Forms calling the transaction code HRASR_DT.

5.6.2.1.1.5 Define Processes Use In this IMG activity, you define the processes that you want to provide in HCM Processes and Forms.

For the Rapid-Deployment-Solution a modified copy of the standard process HR_MSSRCF_REQUISITION is used. Please follow the instructions to create the new process YNHR_MSSRCF_REQUISITION.


1. In the Design Time for Processes and Forms screen, enter HR_MSSRCF_REQUISITION in

the drop-down field below Process. Choose Enter. 2. Right click on the process name HR_MSSRCF_REQUISITION. Choose Copy (do NOT

choose copy with dependent objects). 3. Enter the new process name YNHR_MSSRCF_REQUISITION. 4. Go to the workflow node and in section Workflow in the field Workflow template specify

NO_WORKFLOW. 5. In the left menu section expand node Process Start. Dopple click on Role Assignment. 6. In the section Roles That Can Start the Process verify that role HRASRB is available. 7. Repeat step 1 and enter the new process name YNHR_MSSRCF_REQUISITION to continue

the set up. 8. In the left side menu expand Process Start and dopple click on Assignment to Process

Groups. In section Process can be seen/performed in start applications for the following groups check the following entries:

Group Name No Start Object

H1NB Recruitment X

9. In the left side menu dopple click on node (01.01.2005-31.12.9999) Validity Period and check

the following entries:

Field name Entry

Process YNHR_MSSRCF_REQUISITION



Field name Entry

Valid From 01.01.2005

Valid To 31.12.9999

Send Variant Do Not Tolerate Error Messages

Process Type Process without Start Object

Start Object Type NB

Start Object Type Additional *empty*

Application Type *empty*

Query for Mass Start *empty*


IMG Menu Personnel Management HR Administrative Services Configuration of Forms/Processes Process Configuration -> Set

up Processes Define Processes

10. In the Processes screen, make / check the following entry:

Process Process Name

YNHR_MSSRCF_REQUISITION Recruitment Requisition Request

Result: The process step Requisition Request in E-Recruiting Manager Self-Service is defined.

5.6.2.1.1.6 Configure Process Start Use In this IMG activity, you specify the start configuration for the processes that you want to use in HCM Processes and Forms.



up Processes Configure Process Start

1. In the Processes screen, make the following entry:

Field Name Entry

Process YNHR_MSSRCF_REQUISITION

Process Name Recruitment Requisition Request

Form Scenario S_HRMSSRCF_REQUISITION

Name Create Requisition



Field Name Entry

Version *empty*

Scenario Step REQUEST

Name Application

Workflow Template NO_WORKFLOW

Workflow Name -No Workflow Assigned -

Send Var. Do Not Tolerate Error Messages

ForwExpert *empty*

No Object X

Result: The process step Requisition Request in E-Recruiting Manager Self-Service is defined.

5.6.2.1.1.7 Specify Valid Processes for Start Application Use In this IMG activity, you determine which processes are to be provided on the user interface for a specific role.



up Processes Validity for Process Start Specify Valid Processes for Start Applications

2. In Work Area choose Role of Initiator HRASRB Manager. 3. In the Valid Processes for Start Applications screen, tick the the box valid for the following

process:

Process Process Name Valid

YNHR_MSSRCF_REQUISITION Recruitment Requisition Request X

Result: The process step Requisition Request can be initiated by the Manager in E-Recruiting.

5.6.2.1.1.8 Continue With Design Time Use

In the following activity the dialog box New Design Time for Processes and Forms Available will be prompted. This content deployment continues with the new Design Time.

Procedure

1. Access the transaction:

Transaction code: HRASR_DT

2. On the dialog box New Design Time for Processes and Forms Available choose Yes.



Result

The assigment to Process Group is done and the new Design Time is activated again.

5.6.2.1.1.9 Assign Process Groups for SAP E-Recruiting rapid-deployment solution

Use

In the following activity cou assing the Process Groups.

Procedure

1. Access the transaction: Transaction Code HRASR_DT

IMG Menu Tools -> ABAP Workbench -> Development -> ABAP Editor

2. On the dialog box New Design Time for Processes and Forms Available choose Yes.

4. On the Design Time for Processes and Forms screen, enter Process and YNHR_MSSRCF_REQUISITION.

5. Choose Enter 6. Choose Expand All 7. Double click on Assigment to Process Group. 8. On the Display Assigment to Process Group screen choose Display <-> Change (Ctrl + F1). 9. In the section Process can be seen/performed in start applications for the following process

groups enter the Group value H1NB. 10. Choose Save Ctrl +S .

Result

The assigment to Process Group is done.

5.6.2.1.1.10 Maintenance of Hire Process (PERS_HIRE_10) Use

In the following activity you activate the workflow link and specify the rule.

Procedure

3. Access the transaction:



4. If necessary: On the dialog box New Design Time for Processes and Forms Available choose Yes.



2. On the Design Time for Processes and Forms screen, enter Process and PERS_HIRE_10. 3. Choose Enter 4. Choose Expand All. 5. Double click on Workflow. 6. On the right side in section Workflow in line Event Type Linkage choose Generate Event Type

Linkage. Choose OK. 7. Choose Save Ctrl +S . 8. In Forms Scenarios expand SHU1 then Other Attributes. Double click on Rules. 9. Change to Change mode. Choose Yes we asked if you really want to change the form

scenario. 10. In section Rules make the following entries:

Rule Name Form

IS_MANAGER Payment Method = ‘HRASRB’

Result

The workflow link is activated and the form rule set.

5.6.2.1.1.11 Check Consistency of Processes Use

You can use the Check Consistency of Processes program (RPASR_CHECK_PROCESS) to check the Customizing settings that you stored when creating a process in HCM Processes and Forms and the workflow settings of the assigned workflow template. The program checks the consistency of the settings and displays the result in a check log.

Procedure




2. On the ABAP Editor: Initial Screen enter in Program the report RPASR_CHECK_PROCESS and choose Continue.

On the the New Design Time for Processes and Forms available choose Continue Without Design Time.

3. On the Check Consistency of Process screen enter the process YNHR_MSSRCF_REQUISITION.

4. Choose Continue (F8).

Result:



The check log is displayed.

5.6.2.1.2 Tips for known issues

The following customizing activities in the HR system provide guidance for the cause of known issues.

5.6.2.1.2.1 ADS

Use

ADS server should be connected. Use the report FP_PDF_TEST_00 to determine if ADS is running ok. For more options please see note 999998.

5.6.2.1.2.2 Data for Country Grouping and Working Hours

Use

In this step, you create the organizational data for country grouping and working hours. This data will be used for the hiring process.

1. Access the activity using the following navigation option:

Transaction Code PE03

2. In the Features: Initial Screen enter IVWID into the field Feature. 3. Select Decision Tree in the section Subobjects and choose Change. 4. Put the cursor on MOLGA and choose Create Nodes (Shift + F2). 5. Select the country groupings you want to use. Choose Copy. 6. Put the cursor on the country grouping and choose Create Nodes (Shift + F2). 7. Select Return value and specify the return value for this country grouping. 8. Choose Activate. 9. Save your entries. 10. Create as many country groupings as required.

Result

The organizational data can be used for the hiring process.

5.6.2.1.2.3 Activate Services in SICF E-Recruiting uses WebDynpro web pages to function properly. We must activate the proper pages in order to ensure proper operation. Activate the services needed for E-Recruiting and assign the service user using the transaction SICF.



1. Access the activity using one of the following navigation options:

IMG Menu n/a


2. On the Maintain service screen make the following entries:

Virtual Host Service Path Service

DEFAULT_HOST /sap/bc/gui/sap/its activate all services start with ASR

DEFAULT_HOST /sap/bc/webdynpro/sap activate all services start with ASR

3. Choose Apply Filter 4. Expand the lowest node 5. Mark the relevant services 6. Choose Activate Service from the context menu.

5.6.2.1.2.4 Automate Work Item Distribution for Hire Process This activity is used to automate the work item distribution to the responsible processor during the Hire process in the HR system.

Transaction Code PFTC

1. In screen Task:Maintain make the following entries:

Field Name Value Task Type Standard task

Task 17900129

2. Choose Display (F7). 3. Choose Additional Data Agent Assignment Maintain. 4. Select the process name and choose Create agent assignment… F(5). 5. In the pop-up Choose agent type select the type you want to assign, e.g. User. 6. In the than appearing pop-up enter the user name or ID of object type. 7. Choose Update Index (Shift + F1). 8. Repeat steps 1 to 7 with the following data.

Field Name Value Task Type Standard task

Task 17900113

Result

During the processing of the Hire process in the HR system the work items will automatically be directed to the entered processors.



5.7 Error Handling: Installation Errors during activation The following information helps you to solve problems that might occur during the installation process.

Before you start with detailed error analyzing and working through the error processing as described below proceed as follows: Activate your solution or the respective scenario in the solution builder implementation assistant again. It might be the case that error will not reappear. In this case no correctional activities are needed and the installation is proceeding.

5.7.1 Error Occurs During Activation of Automated Task

Use When an activation of an automated task runs into errors, the activation stops at the point of the error. No further implementation can be done until the error is resolved.

Procedure 1. On the Implementation Assistant – Solution View screen, select a task that has a red light in the

Current status column.

2. Expand the task and choose the log that is assigned to this task. Detailed information about the error is displayed in the Error List pane.

3. In the Error List pane choose Display Detailed Log. The detailed log information about an eCATT or BC set activation is displayed.

4. In this log information check entries with a red light to identify the reason for the error.

a. In case the error can be solved based on the log information, you can run the eCATT or BC set again.

In case the activation fails because of locked objects, make sure, that no objects are locked by any users. Then try to activate the activity again.

See the document SAP Best Practices Tools for details about the manual activation of eCATTs and BC sets. The document can be found in the documentation package in the section Intro Concepts accelerator SAP Best Practices Tools In case the log information is not sufficient to solve the problem you can proceed as follows:

b. Execute the task manually: use the description of the related section in the configuration guide for executing the task,

or

c. Open a customer message for this problem specifying the component SV-RDS-HCM

Do NOT delete solution builder scenarios ONCE they have been activated. If you delete scenarios, the activation history and the respective logs are lost and it is not possible to find possible error reasons with tenable efforts.

In such cases NO SAP SUPPORT CAN BE PROVIDED.

5. When you have solved the problem (either executed the task manually or a solution has been

provided via customer message), choose the Change button that is displayed in the Old Status column to the right of the task.



Do NOT proceed with installation if the problem has not been solved. If you continue without solving the problem, severe errors might result in the subsequent installation steps that cause incalculable efforts to fix.

In such cases NO SAP SUPPORT CAN BE PROVIDED.

6. Choose the Change button that is displayed in the Old Status column to the right of the task.

7. On the Confirmation dialog box, choose OK to manually change the status to successful.

8. On the Information dialog box, enter a reason for changing the status.

9. Choose Continue.

The information is saved in a log. To view details for a changed task, choose the red light in the Original Status column for that task. A dialog box displays the user who performed the change, the date of the change, and the reason for the change. Choose Continue to close the dialog box.

10. Choose Activate to continue with the installation.

Date post:	29-Dec-2015
Category:	Documents
Upload:	swamy-arava
View:	134 times
Download:	9 times