SFSF EC to 3 rd party payroll Integration Software and Delivery Requirements

Transcription

1 SAP HCI(PI) August 2015 English SFSF EC to 3 rd party payroll Integration Software and Delivery Requirements SAP SE Dietmar-Hopp-Allee Walldorf Germany Document Revisions Date 0 November

2 Copyright 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. 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 7

3 Icons Icon Meaning Caution Note Recommendation Syntax External Process Business Process Alternative/Decision Choice Typographic Conventions Type Style Description 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. text EXAMPLE TEXT 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. text < 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 7

4 Table of Contents 1 Purpose of the Document General Project Prerequisites Technical Requirements Software Product Versions SAP Cloud Solution Front-End Components System Landscape Connectivity Authorizations Authorizations for step-by-step guide Checklist Certificate IP Range / Ports... 7 SAP SE Public Page 4 of 7

5 1 Purpose of the Document This document contains all of the following information: 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 ConfigGuide. 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 e.g. CSS notes, BW content, patches, user requests, authorization changes and transports Decision made whether pre-assembled delivery will be used 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 Responsibility 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 SAP Cloud Solution The following software products and versions are required: SAP SE Public Page 5 of 7

6 Product Product Version Components Comments Relevance SAP SuccessFactors Employee Central 1505 or later Mandatory. All Scope Items SAP HANA Cloud Integration Adapter SDK for SAP HANA Cloud Integration Designer for SAP HANA Cloud Integration Mandatory Operations for SAP HANA Cloud Integration Front-End Components Component Java JRE Eclipse Kepler SAP HANA Cloud Integration Add-on Required Version 1.6 or above Kepler 4.3 or above for Windows 64-bit Adapter SDK for SAP HANA Cloud Integration (Beta) or above Designer for SAP HANA Cloud Integration or above Operations for SAP HANA Cloud Integration or above We strongly recommend you that you always use the latest available versions, support packages. 3.2 System Landscape 3.3 Connectivity The following connections are required: 1. Connection between HCI and Success Factors. To enable the connection, please refer to section 2.4 of Step-by-Step Guide. SAP SE Public Page 6 of 7

7 2. Connection between HCI and SFTP server (optional) To enable the connection, please refer to section 2.5 of Step-by-Step Guide. 3.4 Authorizations The following authorizations are required: Authorizations for step-by-step guide 1. The authorization of provisioning account is needed to do provisioning settings for SF EC. 2. The authorization of system administration is needed to do basic configuration settings in SF EC. 3.5 Checklist Certificate For the security prerequisite for integration, certificates are required. 1. To connect to Success Factors system, the HTTPS certificate must be presented in HCI tenant s keystore. 2. Public Keys of HCI tenant and SFTP server. The connectivity is established by exchanging the public keys of the HCI tenant and SFTP server IP Range / Ports You need to check with your cloud service team about the IP Range/Ports information. SAP SE Public Page 7 of 7