Mass Hiring Customization Cookbook Version 1.3 March, 2013 SAP HCM Core Renewal FP3 2013 SAP AG. All rights reserved. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, 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. Crossgate, m@gic EDDY, B2B 360, and B2B 360 Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate 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.
Document Version Date Description of Change 1.0 Feb 26 th, 2013 Initial version by Rao, Wei and Zhu, Samuel PWD: aihcm 1.1 Mar 6 th, 2013 Reviewed by Ehrler, Stefan and Simons, Susan 1.2 Mar 11 th, 2013 Add chapter 6.5 and 6.6 1.2.1 Mar 13 th, 2013 Chapter 7.5 added; small improvement on dev user account; handling of position 99999999 1.3 Mar 18 th, 2013 Adapt chapter 4.3 and 7.6
TABLE OF CONTENT 1. SCOPE OF THIS DOCUMENT... 4 2. TARGET AUDIENCE... 4 3. BUSINESS EXAMPLE... 4 4. TECHNICAL PREREQUISITES... 5 4.1 System & Clients... 5 4.2 Software Installed on Desktop... 5 4.3 Users & Roles... 5 4.4 Client Settings... 6 5. MASS HIRING CONFIGURATION... 6 5.1 Steps in Source Client... 6 5.1.1 Create a new Form... 7 5.1.2 Set Fields Attributes... 8 5.1.3 Generate FPM Component Configuration... 10 5.1.4 Enable Parallel Processing... 15 5.1.5 Utilities... 16 5.2 Steps in Target Client... 18 5.2.1 Import Configuration... 18 5.2.2 Register to Landing Page... 18 6. TIPS... 20 6.1 Personnel Number Generation... 20 6.2 Date Format in Excel... 20 6.3 Hide/Unhide Log Area... 21 6.4 Determine Mandatory Fields... 22 6.5 Example of User Event: Derive Personal Area and so on from Position... 22 6.6 Example of Getting Value help... 23 7. KNOW ISSUES... 24 7.1 Known Issue Performance of Value Help... 24 7.2 High Data for Mass Hiring... 24 7.3 View Completed Draft... 24 7.4 UI Issues... 24 7.5 Use of Position 99999999... 24 7.6 Miscellaneous... 25 8. REFERENCES... 26
1. Scope of this document The new mass hiring application is equipped with a modern, excel-like user interface which allows end users to enter and maintain large volume of master data in a user-centric approach. It also provides the end user with an easy template definition capability, support of excel import & export capabilities, save/load candidate (new hire) lists as drafts, effective view and editing options as well as a good and easy error handling function. This document will guild you through the process of creating a new form scenario for mass hiring application, e.g. seasonal hiring, campus hiring, part-time worker hiring, working students hiring 2. Target Audience The target audience of this document should be SAP HCM product team Solution owners HCM consultants HCM project implementation team of SAP Partners. 3. Business Example Suppose these infotypes are needed to conduct a mass campus hiring: Personnel Number: Internal Assignment will be used IT0001 - Organizational Assignment Field ABKRS BTRTL BUKRS PERSG PERSK PLANS WERKS Description Payroll area Personnel subarea Company Code Employee group Employee subgroup Position Personnel area IT0002 - Personal Data Field Description ANRED Form-of-address key FAMST Marital status GBDAT Date of Birth NACHN Last name NATIO Nationality SPRSL Communication Lang. VORNA First Name IT0006 - Addresses Field LAND1 Description Country Key
ORT01 PSTLZ STRAS TELNR City Postal Code Street Name Telephone Number 4. Technical Prerequisites This section describes system environment to customize the sample. 4.1 System & Clients Installed Software Component: Product Version: HCM Core Renewal 1.0 FP3 Software Component Layer: EA-HRGXX, 607, SP10 Clients (SAP standard recommendation on system landscape setup applies): Productive system / client: on which the End User may access HCM landing page. Quality system / client: to be used for testing purposes Development (Customizing) system / client: main customizing client. 4.2 Software Installed on Desktop. NWBC 4.0 PL0 or the above IE9 or Chrome with latest version MS Office EXCEL 2007 or the above 4.3 Users & Roles Productive System / Client: o Testing user with standard role SAP_PAO_HRPROFESSIONAL2 for HR Specialist assigned. For more information on the new role SAP_PAO_HRPROFESSIONAL_2, go to the Roles section of the SAP Library (on SAP Help Portal under http://help.sap.com/hr_renewal in the application help for SAP ERP -> SAP ERP Cross- Application Functions -> Roles -> Roles in Back-End System -> Single and Composite Roles (PFCG) -> Human Resources (HR) -> Human Capital Management o A user with same authorization on customizing client to make necessary configuration in HCM Launch Pad and Import configuration of mass processing scenario. Development (Customizing) Client: a developer s role with SAP_ALL or similar profile with enough authorization to create an ABAP WebDynpro component configuration should be assigned to the user for development. Note: o The user must firstly apply for a valid developer license in SAP Service Marketplace and register this license in the system. With links for your reference: User Administration - service.sap.com/user-admin License Application - service.sap.com/licensekey o To assign the ABAP role to the user, you may consider the standard ABAP role SAP_BC_DWB_ABAPDEVELOPER, which includes the required Authorization object S_DEVELOP (OBJTYPE = WDCC; ACTVT = 02) already.
4.4 Client Settings The steps in this section should be done on the development (customizing) system/client as well as the quality system/client and the productive system/client: Business Function Activation Business function HCM_PAO_MP_1 (HCM, Mass Processing for Personnel and Organization) and its dependent business functions are activated. You may check the status via transaction code SFW5 and ask system administrator to activate it if not. IMG Activities All Relevant Infotypes are configured in all clients via IMG Personnel Management > Infotypes All configurations are done for the dependent business function HCM_PAO_CI_1 (HCM, Personnel and Organization) System Basis Setting In case you want to enable asynchronies and parallel processing, make sure the inbound background RFC destination are is available in both clients with same name. View details in SAP help (see under help.sap.com): Personnel & Organization > Processes > International Mass Processing > Configuration of the Mass Hiring Web Application > Design Time for Mass Hiring Definition > of Asynchronous and Parallel Processing Testing Data Preperation Relevant testing data are ready, e.g. Org structure with a couple of open positions is created in the system. Mass Hiring Specific Setting View details in SAP help: Personnel & Organization > Processes > International Mass Processing > Configuration of the Mass Hiring Web Application > Integrating the Draft into the Landing Page 5. Mass Hiring Configuration This section gives an example to create a mass-hiring application. 5.1 Steps in Source Client The steps described in this section should be done on source client. Ensure that you have active the business function HCM_PAO_MP_1 that all customizing entries are available.
5.1.1 Create a new Form 1. Run transaction HRASR_DT, specify name, e.g. ZHRPAO_MASS_HIRING_SAMPLE in this case, of your new form scenario in the navigation window, click button Display. 2. System may detect the name doesn t exist and asks for more information. In the popup, input the description of the form scenario and specify form type as Mass Form. Take the default Back-End Service SAP_PA for mass-hiring Note For more information on Back-End Service, view details in SAP help: Design Time for Processes and Forms > Creation and Configuration of Form Scenarios > Configuration of Back-End Services
5.1.2 Set Fields Attributes 1. Click on node Fields, some fields are generated automatically, which are frequently used. For mass hiring. 2. You have to set the field attribute as following: PERNR: Fixed Field: Checked Field Sequence: 1 Field Attribute: Output Only Note: MASSN: o o Do not bind field PERNR of any infotypes, including 0001-Organizational Assignment to form fields. Do NOT remove or rename the field PERNR, as the name is used by most of mass-hiring applications, e.g. excel capabilities, re-hiring detection & resolving. Field Attribute: Invisible Default Value Origin of Default Value: Manually; Data Binding in Service/Default Value: 01 (The same code stored in the Action Type(MASSN) field in the Personnel Action Types (T529A) table for hiring) MASSG: Field Attribute: Invisible Tips:
Click on cell under column Field Attribute or Default Value to open the popup for attributes change: For more information on Back-End Service, view details in SAP help: Design Time for Processes and Forms > Creation and Configuration of Form Scenarios > Definition of Form Fields 3. Repeat these steps to add more infotypes fields, and then save the form scenario. IT0001 - Organizational Assignment IT0002 - Personal Data IT0006 Addresses When determine the Input Help, there re two ways: Manual Value Help: then you have to specify the list of fixed code and description under tab Manual Value Help Data Binding in Service 4. Then at the end, you may get a similar configuration as attached below. (See the same, also latest version in SAPNote 1835253). To use it in your configuration, you may create a form scenario with the
same name given in this example; save by making no change, then check-in the attached configuration by upload the file via menu button Import from XML file. ZHRPAO_MASS_HIRING_SAMPLE.xml Tips: When assign the same service field to multiple form fields, you must use Op. Exclusion (Exclude from Operation) indicator for all form fields except the first one. For example, you want to create two records of Basic Pay (0008) infotypes with different Wage Type in the same form scenario, you can define two form fields I0008_BETRG and I0008_BETRG_1, which are binding to the same service field BETRG in infotype Basic Pay (0008) infotypes. The Exclude from Operation indicator of form field I0008_BETRG_1must be checked on. See usage of Exclude from Operation indicator in SAP help: Design Time for Processes and Forms > Creation and Configuration of Form Scenarios > Configuration of Back-End Services > Settings for Back-End Service SAP_PA To determine whether the technical fields of an infotype are mandatory (or, the field s UI Attribute is Required Entry ) or not, see SAP note 1824040. 5.1.3 Generate FPM Component Configuration This section describes the steps to generate a FPM (Floor Plan Manager) component configuration for the end user web UI. Before start this step, please make sure the form scenario is in Change mode. 1. Click node Form, specify name of the new component configuration and description.
2. The FPM workbench will be opened automatically and ask for feeder class. Enter here the name of the following class: CL_HRMP_LISTVIEW_FEED 3. Check the form scenario name and version ID 4. A component configuration will be generated automatically by retrieving data from design time tool. Check afterwards the correct sequence of the fields in the FPM to ensure that they have the same as in the design time tool.
5. In the General Setting tab, uncheck Fit Columns to Table Width if too many fields are assigned to a form scenario 6. Check and adjust column attributes by open Navigation & Repositories. 7. Click Save
Tips In case you did a mistake and created a wrong FPM configuration and you would like to get rid of it please follow the steps listed below to remove an existing FPM Component Configuration object: 1. Start transaction SE80 2. Choose the Edit Object button 3. Choose the Advanced Options radio button 4. On the Web Objects tab page, Choose the FPM Component Configuration radio button and enter the configuration ID 5. Choose the Delete button
5.1.4 Enable Parallel Processing The mass-hiring application may use the Net Weaver background RFC technology to enable parallel processing, thus reduce the total processing time of validation and final data submission on UI. 1. Use F4 help of field Inbound Destination Name to find an available destination 2. Then specify the number of processes Then asynchronous processing will be enabled, when the number of candidates selected for execution exceeds 10. Note The destination name in source client MUST be the same in all clients If more than one inbound destination is maintained in the system, select the one listed in transaction code SBGRFCCONF. Here is an example:
5.1.5 Utilities Import/Export the configuration to XML Double click on root node of the form scenario, you may use buttons in the menu to export the configuration to XML, or Import the configuration of same name from XML File Download Template (Excel) In the node of Fields, click button Download Template to check the current layout of the Excel template after saving this scenario.
Create New Version Click button Create version in the context menu of the form scenario, you may create a new version. Test an Application Open a Web browser and input the following URL to test the Web UI: https://<host name>:<host port>/sap/bc/webdynpro/sap/hrmp_listview_main?sap-wd- CONFIGID=HRMP_LISTVIEW_MAIN_CONFIG&FORM_SCENARIO=<form scenario>&form_scen_vers=<form scenario version> In this case, the link is https://<host name>:<host port>/sap/bc/webdynpro/sap/hrmp_listview_main?sap-wd- CONFIGID=HRMP_LISTVIEW_MAIN_CONFIG&FORM_SCENARIO ZHRPAO_MASS_HIRING_SAMPLE&FORM_SCEN_VERS=0
5.2 Steps in Target Client 5.2.1 Import Configuration In target client, perform the following steps to import configuration: 1. Run transaction HRASR_DT, create a new scenario with same name in source client 2. Click button Import from XML file and upload the configuration exported from source client. 3. Click button Save 5.2.2 Register to Landing Page You use this function to integrate the Mass Hiring Web application into the Actions Lane in the HCM landing page. Launchpad Customizing 1. Execute TCode LPD_CUST 2. Edit the entry: Role = HRPAO and Instance = ACTIONS Create a New Folder (Optional) 1. Choose the New Folder button 2. Name the folder and define the attributes, if you want to group mass-hiring relevant actions in a separated section of expanded ACTIONS lane in HCM landing page.
Create a New Application 1. Select a destination folder 2. Choose the New Application button 3. Name the application and select Web Dynpro ABAP as the application type 4. Specify the parameters as follows: a. Namespace: sap b. Application: HRMP_LISTVIEW_MAIN c. System Alias: SAP_ECC_HumanResources d. Force local system if NWBC: Checked 5. Specify the advanced parameters as follows: a. Application cannot be removed from Launchpad: Unchecked b. Application Alias: Unchanged or change if necessary c. Target App. Parameters: SAP-WD- CONFIGID=HRMP_LISTVIEW_MAIN_CONFIG&FORM_SCENARIO=YOUR_MASS_FORM _NAME&FORM_SCEN_VERS=YOUR_MASS_FORM_VERSION Note: Replace YOUR_MASS_FORM_NAME and YOUR_MASS_FORM_VERSION with the actual values of your Mass Form. d. Configuration: HRMP_LISTVIEW_MAIN_CONFIG e. Suspend/Resume: Unchecked f. Icon Path: Give the path of the icon to identify your Mass Hiring action g. Proxy Class: Change when necessary h. Add Information: DISPLAY_IN=LANE i. FPM Event ID: Unchanged j. Navigation Mode: Headerless Portal Window k. Window Features: Change when necessary l. History Mode: Navigation Entry can Occur Once in History m. Parameter Forwarding: Get Parameters 6. Save and exit
6. Tips 6.1 Personnel Number Generation If the range of the personnel number for your system is set as External Assignment. The UI attribute of field PERNR should be Required Entry. Then the personnel number should be maintained by end user manually. For more information about the range of the personnel numbers, see Customizing for Number Range Intervals for Personnel Numbers under Personnel Management -> Personnel & Organization -> Basic Settings -> Number Ranges -> Number Ranges for Employees. The feature NUMKR determines the Number Range Intervals for personnel numbers of a country. 6.2 Date Format in Excel EXCEL does its own conversion on date type cell. Via these steps, you may know how it works: 1> Create new Excel, format a cell as following (You may change Location to any country). And input a VALID value, e.g. 3/14/2013 for my case 2> Save it. Change your system location to another value, e.g Germany in control panel. simulate the case that you forward the excel to someone in another country, then the one opened the file with his/her location setting.
3> Reopen excel, and you may see the actual value is 14.03.2013! It is because a CORRECT value in EXCEL is stored as integer (to indicate the number of days since 1900.01.01). If the initial value maintained in EXCEL doesn t follow the format, the conversion may NOT happen. When upload an excel to mass-hiring application, we convert the integer to SAP ABAP format. In the brief, the behavior of date type in mass-hiring application is: The DISPLAY of content in cells of an excel follows the location setting of OS The layout of webui follows the user specific setting in SAP system. 6.3 Hide/Unhide Log Area A FPM application support to show historical messages between actions, that is called Log of message. This function is disabled in standard delivery. To enable it, you may try with this way: 1. Run transaction SET80, find package PAOC_ASR_WD_MASS_PROCESS_ADV 2. Double click on WebDynpro application configuration HRMP_LISTVIEW_MAIN_CONFIG, click button Display Configuration 3. Click configuration name HRMP_LISTVIEW_MAIN_CC 4. Check Display Message Log in Message Settings section of General Settings tab The major difference of Current Message and Log is: The Current Message area shows the person specific message when select a row OR an aggregated message after validation/submit The Log message area buffers all UI messages between two transactions, e.g. validation/submit/ load draft. The historical messages will be cleared unless next action is triggered or use click button Reset Log explicitly. does NOT indicate message of the selected row. If switch from row to row, the messages belonging to previously selected row are still in the Log area
6.4 Determine Mandatory Fields To determine which technical fields of an infotype is mandatory (UI attribute as Required Entry ) or not, try with these steps: o Run transaction SE11, search content of table T588MFPROPS with search criteria infotype, infotypes version and subtype, check field MANDATORY. If the field FIXED is not checked, check table T588MFPROPC in addition. o Check out the country specific UI conversion class of an infotypes from table T588UICONVCLAS, check whether the field attribute is redefined. Example Take infotype 0002-Personal Data with country version: Germany as an example, the mandatory technical fields are: GBPAS, SPRSL. Means they MUST be added in the form and set UI attribute as Required Entry. View details and tools in SAPNote 1824040 6.5 Example of User Event: Derive Personal Area and so on from Position 1. Add backend service s_derive_position as the 1st service 2. Define user event DERIVE_POS_DATA
3. Assign the event to position column in FPM configuration. 6.6 Example of Getting Value help 1. Add user event INIT_FROM_HEADER_FIELDS 2. Assign event to Payroll area column
7. Know Issues 7.1 Known Issue Performance of Value Help The number of value help defined may impact runtime performance of excel capabilities, like downloading template, download candidates list. In case of such issue, you may choose to disable the value help of the corresponding fields or use fixed value help to avoid it. For an instance, use Manual Value Help as Input Help for value help relevant to T512W wage types. 7.2 High Data for Mass Hiring Based on the existing HCM infotype framework, the end date for the Organizational Assignment (IT0001) record must always be set to the high date (12/31/9999) in our Mass Hiring Web application. In case of any temporary hires with dedicated end date, for example, seasonal hires or contract hires, a separate termination action needs to be created using the transaction code PA40 after successful execution of the mass hire action. Also ensure that you set the effective date equal or greater than the BEGDA of IT0001 record in your data 7.3 View Completed Draft Due to a technical restriction, a Completed Draft will not be visible in the Task Lane of HCM Landing page. View details in SAPNote 1816640. 7.4 UI Issues When access the context menu by right clicking on an empty space, a dump may occur due to an issue in Floor Plan Manager. See SAP Note 1820925 for solution. 7.5 Use of Position 99999999 There is a known issue that when assign position 99999999 to a person, an error on UI may occur: "Entry 99999999 does not exist in T528B (check entry)", see an example below:
If you check table T528B one of the key fields is OTYPE. Apart from the field PLANS from the P0001 structure the field OTYPE is also passed from the P0001 structure to check for foreign keys. So if filed OTYPE is not defined or assigned with incorrect default value in your form scenario configuration, a foreign key check fails as no entry is found in table T528B by condition, e.g. OTYPE = '' AND PLANS = '99999999'. This is the reason for the error. To avoid this issue, please include the field OTYPE from IT0001 in the form scenario and set it with the manual default value S for example, this should resolve the problem. You can refer to the sample process HIRE_01 for example. 7.6 Miscellaneous The SAPNotes listed in this section were created to solve some programming errors detected in the final validation phase. It is recommended to apply all these notes to the system. Symptom: Dump when edit FPM component configuration in Display mode SAPNote 1831918: When try to create or change a FPM component configuration for a form scenario in Display mode, a dump may occur. Go to SAP Note system for details Symptom: Excel error when a new scenario is not saved SAPNote 1831239: If a scenario is newly created and not saved, an error appears when open the generated excel. Go to SAP Note system for details Symptom: Incorrect re-hiring detection due to data format conversion, e.g. convert SSN 222334444 to 222-33-4444 SAPNote 1834098: re-hiring detection and excel re-import doesn t work properly due to an automatic data conversion issue after validation, e.g. SSN (field PERID of IT0002-Personnal Information) of 222334444 will be converted to 222-33-4444 after validation.
8. References Business Function Via transaction code sfw5 you will find all relevant business function (HCM_PAO_MP_1), including release information and documentation IMG Activity Run transaction code SPRO in your system, navigate to IMG activity: Personnel & Organization > Processes > Mass Processing SAP help Content (help.sap.com) Mass Hiring Application: Personnel & Organization > Processes > International Mass Processing > Configuration of the Mass Hiring Web Application HCM Process & Form: Design Time for Processes and Forms > Creation and Configuration of Form Scenarios Ramp Up Knowledge Transfer Pages (RKT) Presentation on Mass Processing Customizing Step-by-Step Guide Live Expert Session Recording(s) Navigate through the path in SAP Service Market Place: SAP Business Suite > SAP ERP > SAP HR Renewal 1.0 > HR Renewal 1.0 FP3 SAPNote for Mass Hiring SAPNote 1835253 is the main note which contains the sample configuration, also links of other useful SAPNote regards to mass hiring.