SAP SuccessFactors Employee Central Integration to SAP ERP rapid-deployment solution V2.0 : Software and Delivery Requirements

Transcription

1 SAP Employee Central Integration to SAP ERP rapiddeployment solution V2.0 March 2016 English SAP Employee Central Integration to SAP ERP rapid-deployment solution V2.0 : Software and Delivery Requirements SAP SE Dietmar-Hopp-Allee Walldorf Germany

2 Copyright 2016 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. 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. Please see for additional trademark information and notices. 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 SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE 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. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE s or its affiliated companies strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions. SAP SE Public Page 2 of 9

3 Icons Icon Meaning Caution Example Note Recommendation Syntax External Process Business Process Alternative/Decision Choice 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 EXAMPLE TEXT Example text Emphasized words or phrases in body text, titles of graphics and tables. Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE. Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools. EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key. Example text <Example text> Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. SAP SE Public Page 3 of 9

4 Table of Contents Contents 1 Purpose of the Document General Project Prerequisites Technical Requirements Software Versions SAP Solution Manager and SAP Solution Manager Content Add-On Active Business Functions Software Landscape Diagram... 8 SAP SE Public Page 4 of 9

5 1 Purpose of the Document This document contains information to: Validate that key prerequisites such as software products 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 if they are valid for all scope items included in the package. For requirements valid for certain scope items only, these scope items are mentioned. The document contains pre-requisites only, not the procedures to meet them. For how-to information (e.g. how to find the download area) please refer to the configuration guides. 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 You have an SAP PI system at least on release 7.11 in place if you will choose Boomi and PI as middleware 1) Infrastructure team can respond to requests quickly enough e.g. CSS notes, BW content, patches, user requests, authorization changes and transports User interfaces agreed, for example, SAPGUI Employee Central: Responsibility 1) This solution package version has been tested with SAP PI system on release SAP PI 7.31 and SAP SE Public Page 5 of 9

6 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 Solution Manager will be used. Solution Manager set up with any relevant templates. Tool for project repository and collaboration agreed Test management tool agreed 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 Versions The following software products and versions are required: SAP BIZX Core Version BIZX core Components SFSF Employee Central SAP Solution Manager Logical Component Comments Cloud You will automatically receive a Dell Boomi account if Boomi will be used as middleware. Relevance All Scope Items SAP ERP SAP ERP 6.0 Integration addons for SAP ERP and EC EHP7 >= SP05 ODTFINCC 600, PA_SE_IN 100, XI CONTENT ODTFINCC 600, On Premise On Premise All scope items C2N C2O C2P XI CONTENT PA_SE_IN 100 SAP Process Integration SAP PI 7.31 SPS 12 or higher On Premise SAP NetWeaver C2N C2O SAP SE Public Page 6 of 9

7 SAP Process Integration SAP PI 7.40 SPS 06 or higher System Landscape Directory recommended the following minimum versions: C2P SAP Model Version: SAP CR Content Version: SAP_CR Integration addons for SAP ERP and EC ODTFINCC 600, SP10 PA_SE_IN 100, SP13 On Premise IP0 IP1 IP2 SAP HANA Cloud Integration IP0 IP1 IP2 3.2 SAP Solution Manager and SAP Solution Manager Content Add-On For the implementation of the solution package, SAP Solution Manager is recommended. Version SAP Solution Manager SAP Solution Manager 7.0 Enhancement Package 1 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 Comments If using SAP Solution Manager 7.0 with SP below 24, see SAP Note 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 support.sap.com/swdc. For more information about downloading and installing ST-RDS 100 content add-ons, see SAP Note and SAP Note respectively. In the ST-RDS 100 content add-on, access the template in the following way: SAP SE Public Page 7 of 9

8 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 Solution Package Name(s) RDS_EC_ERP_SFEC1210V2 - Employee Central Integr. to SAP ERP RDS_V2 Employee Central Integr. to SAP ERP RDS_V2 3.3 Active Business Functions Functionality in this solution package requires certain business functions to be active in the SAP landscape. These business functions need to be activated: ERP Employee Central Business Function Configuration or Data required Relevance Financials Cost Center Master Data For Cost Center Integration Personal Administration and Organizational Management Employee master data, organizational data, for example, dept., division, business unit, reporting line, job assignment, position assignment and cost center assignment Employee master data and organization data replication from Employee Central to SAP ERP Following business function needs to be deactivated in this solution package: Business Function Configuration or Data required Relevance PA_SE_IN HCM_SFEC_MDEC2HR Employee Master Data For Employee Master Data Replication 3.4 Software Landscape Diagram If you use Boomi as middleware: SAP ERP SAP NW PI Middleware DMZ Boomi Middlewar e Employee Central SAP SE Public Page 8 of 9

9 If you use HCI as middleware: This diagram is an abstract view of the system landscape, to explain where work is done in an implementation project. It is not a specification that describes all the technical details of a real system landscape. SAP SE Public Page 9 of 9