SAP Payroll Processing control center rapiddeployment

Software and Delivery Requirements Document Version: 1.0 July 2015 SAP Payroll Processing control center rapiddeployment solution

Typographic Conventions Type Style Example Description Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Textual cross-references to other documents. Example EXAMPLE Example Example <Example> Emphasized words or expressions. Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. EXAM PLE Keys on the keyboard, for example, F2 or EN TER. 2 2015 SAP SE or an SAP affiliate company. All rights reserved. Typographic Conventions

Table of Contents 1 Purpose of the Document... 5 2 General Project Prerequisites... 6 3 Technical Requirements... 7 3.1 Software Product Versions... 7 3.2 SAP Notes... 8 3.3 SAP Solution Manager and SAP Solution Manager Content Add-On (Optional)... 8 3.4 Required Content... 9 3.5 Active Business Functions Required... 10 3.6 Authorizations... 10 4 2015 SAP SE or an SAP affiliate company. All rights reserved. Table of Contents

1 Purpose of the Document This document contains all information to: Validate that key prerequisites such as software components and versions match the customer situation. Check that all prerequisites for a customer implementation are in place. Check that correct content, tools and skills are in place before the project starts. The document lists different kinds of requirements on package level that are valid for all scope items included in the package. In case there are requirements that are only valid for certain scope items, these scope items are mentioned explicitly. The document contains prerequisites only, not the procedures to meet them. For how-to information (for example, how to find the download area), refer to the Configuration Guide - Getting started (attached to the SAP Note). Purpose of the Document 2015 SAP SE or an SAP affiliate company. All rights reserved. 5

2 General Project Prerequisites The following prerequisites need to be in place before an implementation project can start. Prerequisite Kick off and workshop dates, location and attendees agreed team allocated with correct skills and training in place Project sponsors and stakeholder identified Hardware fully commissioned Software licenses in place Infrastructure team can respond to requests quickly enough, for example, to CSS notes, BW content, patches, user requests, authorization changes and transports User interfaces agreed, for example, SAPGUI, NetWeaver Business Client or Portal Remote access is in place for SAP consultants and SAP Active Global Support Decision made whether pre-assembled delivery will be used Decision made whether SAP Best Practices Solution Builder will be used to activate content Decision made whether SAP Solution Manager will be used. SAP Solution Manager set up with any relevant templates Tool for project repository and collaboration agreed Test management tool agreed Responsibility 6 2015 SAP SE or an SAP affiliate company. All rights reserved. General Project Prerequisites

3 Technical Requirements This section contains technical requirements in different areas. For each requirement, the relevance for scope items of the package is provided. 3.1 Software Product Versions The following software products and versions are required: Product Product Version Compone nts as Tested Solution Manager Component Comments Relevance SAP ERP EHP7 FOR SAP ERP 6.0 (SPS05) EA-HR; SAP_HR ERP60_EHP7_CENTRAL _APPLICATION Mandatory All scope items HR Renewal 2.0 EA-HR; SAP_HR (min. SP 0012) Mandatory In addition, SAP Note 2072859 All scope items SAP Best Practices solution builder BP- SOLBLD 70Vx Always use the latest available version as outlined in SAP Note 1301301. BP- SOLBLD None Add-on for the implementation tool (only necessary to be implemented in a system where content activation shall be done using the SAP Best Practices solution builder, for example, sandbox or development system). All scope items Note SAP Payroll Processing control center uses OData services for SAPUI5 applications. These services need to be activated in the SAP NetWeaver Gateway. With SAP NetWeaver 7.4, which is the base of EHP7 FOR SAP ERP 6.0, this is now embedded. This package is using the embedded Gateway. With a standalone SAP NetWeaver instance as Gateway, you have to create a trusted RFC connection between Gateway and SAP ERP and a corresponding system alias. This needs to be then used in the service setup instead of alias local. Technical Requirements 2015 SAP SE or an SAP affiliate company. All rights reserved. 7

3.2 SAP Notes The following SAP Notes need to be considered: SAP Note No Content Comments Relevance 2072859 This SAP Note delivers the Best Practices ABAP classes for the master data and payroll checks and is a prerequisite for the activation. 2025701 This SAP Note contains critical information for implementing the SAP Payroll Processing control center rapid-deployment solution. It needs to be installed via transaction SNOTE before the activation of the related SAP Best Practices scope is started. Before you start the activation of the related SAP Best Practices scope, check the latest versions of this SAP Note. All scope items All scope items Note Prerequisite for using SAP Payroll Processing control center: Declustering in HCM, Payroll. For more information about the declustering tools, see SAP Notes 1774918 and 1846500. 3.3 SAP Solution Manager and SAP Solution Manager Content Add-On (Optional) The below section is optional and only relevant if you intend to use SAP Solution Manager for the documentation of the solution lifecycle. For the implementation of the solution package, SAP Solution Manager is recommended. Product Product Version Comments SAP Solution Manager SAP Solution Manager 7.0 Enhancement Package 1 If using SAP Solution Manager 7.0 with SP below 24, see SAP Note 1579267. SP18 or higher - Or - SAP Solution Manager 7.1 SP01 or higher - Or - SAP Solution Manager 7.1 on HANA (ST 712) SP00 or higher 8 2015 SAP SE or an SAP affiliate company. All rights reserved. Technical Requirements

For SAP rapid-deployment solutions, implementation content is available in SAP Solution Manager templates. The SAP Solution Manager template for this solution package is in the ST-RDS 100 content add-on. You can download the latest available ST-RDS 100 content add-on from SAP Software Download Center on SAP Service Marketplace at service.sap.com/swdc. For more information about downloading and installing ST-RDS 100 content add-ons, see SAP Note 1726649 and SAP Note 1686668 respectively. In the ST-RDS 100 content add-on, access the template in the following way: If you have SAP Solution Manager 7.1 SP04 or lower, select the template ID and template name in the table below. If you have SAP Solution Manager 7.1 SP05 or higher, select the solution package name(s) in the table below. Template ID and Template Name Available as of SAP Solution Manager Content Add-on Release RDS_PY_CC_ERP607V1 SAP Payroll Processing Control Center RDS_V1 3.4 Required Content The following content is required: Product Product Version Components as Tested SAP Solution Manager Component Comments Relevance SAP Best Practices Configuration Content (for SAP ERP and SAP NetWeaver) BP-ERP 617Vx BP-CANW 740Vx Always use the latest available versions as outlined in SAP Note 1301301. BP-ERP BP-CANW None Add-ons containing configuration content (only necessary to be implemented in the system which is used for the initial content activation (for example, sandbox or development system). All scope items Technical Requirements 2015 SAP SE or an SAP affiliate company. All rights reserved. 9

3.5 Active Business Functions Required Functionality in this solution package requires certain business functions to be active in the SAP landscape. These business functions need to be activated: Product Business Function Configuration or Data Required Relevance ERP HCM Personnel Administration: Employee Master Data All scope items ERP Payroll Results All scope items ERP ERP Payroll: HCM Declustering Tools (HCM_LOC_CI_50) Payroll Data Source Framework (HCM_LOC_CI_62) Authorization Framework (HCM_LOC_CI_63) All scope items All scope items 3.6 Authorizations The following authorizations are required: Authorization Object Text Comment P_PYD_CLS Payroll Data Source Class Controls which tiles are displayed in the worklist for a user on the user interface. Each tile corresponds to one of the checking steps in the payroll process, for example, the master data checks in the preliminary payroll calculation activities or the payroll result checks after the payroll run. P_PYD_INST Payroll Data Source Instance Controls access to the check results that are displayed on the user interface, for example, the results for a check if any employees have retro-calculations, and allows the user to perform certain actions on these check results, such as changing the status. P_PYD_UV Payroll Data Source User Variant Maintenance Controls if a user is allowed to maintain user variants for other users. 10 2015 SAP SE or an SAP affiliate company. All rights reserved. Technical Requirements

Note For more detailed information about the authorization objects and their fields, refer to the system documentation that can be accessed, for example, by calling transaction Maintain Authorizations Object (SU21). To achieve that the user, in general, can execute OData services for SAPUI5 applications, you need to add other authorizations to your authorization profile. Technical Requirements 2015 SAP SE or an SAP affiliate company. All rights reserved. 11

www.sap.com/contactsap 2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. Please see www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices. Material Number: