Software and Delivery Requirements

Transcription

1 SAP Best Practices for SAP Cloud for Travel and Expense November 2014 English SAP Best Practices for SAP Cloud for Travel and Expense: Software and Delivery Requirements SAP SE Dietmar-Hopp-Allee Walldorf Germany Document Revisions Date 0 November SAP SE Public Page 1 of 13

2 Copyright 2014 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 13

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 13

4 Table of Contents 1 Purpose of the Document General Project Prerequisites Technical Requirements Software product versions SAP ERP SAP Cloud System Front-End Components SAP Notes System Landscape Authorizations Authorizations for configuration guide Authorizations for Test Script Checklist Security Requirement Certificate IP Range / Ports Other Questions Need to be Checked Appendix FAQ SAP SE Public Page 4 of 13

5 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 will list different kinds of requirements on package level if they are valid for all Scope 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 Quick Guide. 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 User interfaces agreed e.g. 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 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 ERP Notes: SAP SE Public Page 5 of 13

6 If your FI and HCM components don't reside in the same physical system, install the FI components in the FI system and the HCM components in the HCM system. Components are delivered on a quarterly basis. Make sure that you always install components from the same quarterly delivery; that is, do not install one component from Q1 and another component from Q3. You do not have to upgrade your ERP add-on components to the very latest support package (SP) with every SAP Cloud for Travel and Expense upgrade; but we do recommend that that you always use the latest available support packages to benefit from corrections and new functions. The following software products and versions are required: Product Product Version Components as tested Comments Relevance SAP Best Practices Solution Builder BP-SOLBLD 70Vx Always use the latest available version as outlined in SAP Note BP-SOLBLD Add-on for the implementation tool (only necessary to be implemented in a system where content activation shall be done using the Solution Builder (i.e. Sandbox or Development System). SAP NetWeaver ABAP 7.0 SP14 ABAP 7.01 SP0 ABAP 7.1 SP0 ABAP 7.2 SP0 ABAP 7.3 SP0 ABAP 7.31 SP0 ABAP 7.4 SP0 Web Service Run Time Basis requirement for Web Service Run Time to support message transfer. SAP NW V7.31 SPS07 is recommended. SAP Cloud for Travel and Expense Mandatory. SAP ERP HCM SAP ERP ECC 601 SP 8 SAP ERP ECC 602 SP 5 SAP ERP ECC 603 SP 4 SAP ERP ECC 604 SP SAP_APPL EA-HRGXX 600. ET1, ET4,ET5 SAP SE Public Page 6 of 13

7 2 SAP ERP ECC 605 SP 1 SAP ERP ECC 606 SP 1 SAP_BASIS 700 SP18 SAP_APPL 600 SP15 HR Support Package SAP ERP FI SAP ERP ECC 601 SP 8 SAP ERP ECC 602 SP 5 SAP ERP ECC 603 SP 4 SAP ERP ECC 604 SP 2 SAP ERP ECC 605 SP 1 SAP ERP ECC 606 SP 1 SAP_BASIS 700 SP18 SAP_APPL 600 SP15 ESA ECC-SE 602 or higher preferred version is ESA ECCSE SAP_APPL ECC-SE Mandatory. 604 SAP TRAVEL OD INTEGRAT ION 4.0 (for ERP HCM) ODTGEN 600 SP01 NWSEXTFW 600 SP11 TEMEXHCM 600 SP05 OTM_EXTR 100 SP06 ODTHCMER 600 or higher ODTGEN 600 NWS_EXT_FW 6.00 TEM_HCM_EXT_CN T 6.00 OTM_EXTR 100 ODTHCMER 600 Mandatory. ET1, ET4,ET5 SAP TRAVEL OD INTEGRAT ION 4.0 (for ERP FI) ODTGEN 600 SP01 NWSEXTFW 600 SP11 TEMEXFIN 600 SP05 ODTFINCO 600 SP06 ODTFINCC 600 SP06 DCFLPROC 600 SP01 TEMODFI 600 SP10 or higher ODTGEN 600 NWS_EXT_FW 6.00 TEM_FIN_EXT_CNT ODTFINCC 600 ODTFINCO 600 DCFLPROC 600 TEMODFI 600 Mandatory. SAP SE Public Page 7 of 13

8 SAP NetWeaver Process Integration SAP NetWeaver Process Integration SAP Cloud System Product Product Version Components as tested Comments Relevance SAP Cloud for Travel and Expense Mandatory Front-End Components Component Required Version Browsers Windows 8, Windows Vista (32bit), Windows 7 (32/64bit): o Internet Explorer 9.0 and higher o Firefox: Extended Support Release Cycle (recommended), minimum version 24.0 Rapid Release Cycle: Latest available version For more information, see SAP Note Firefox browsers for end users and administrators. o Chrome 30.0 and higher MAC OS X (10.6 and higher): o Safari 6.1 and higher Microsoft Silverlight 5 In general, we recommend for all users to use the HMTL5 client. The following users need Microsoft Silverlight: The initial user Travel administrator System administrator All users if Microsoft Silverlight is the preferred client. SAP SE Public Page 8 of 13

9 We strongly recommend that you always use the latest available versions, support packages, and patches of operating systems and browsers. Additionally, do not use a screen resolution of less than For a detailed overview of all supported operating systems, browsers, and office suites, have a look at the SAP ByDesign Business Center for cloud solutions from SAP at If you experience problems using Microsoft Silverlight 5 with Firefox, adjust your Firefox proxy settings. Use the same settings as for Microsoft Internet Explorer. 3.2 SAP Notes If issues become apparent after the shipment of this package (and hence of this document), the SAP Note SAP Best Practices for SAP Cloud for Travel and Expense V1.607 documents how to solve the issues. The following SAP Notes need to be considered: SAP Note No Content Comments Relevanc e SP Equivalence for update/upgrade to EHP 1 for SAP NW SP Equivalence for update/upgrade to EHP 2 for SAP NW SP Equivalence for update/upgrade to SAP EHP 3 for NW SP Equivalence for update/upgrade to SAP NW SP Equivalence for update/upgrade to SAP EHP 1 for NW SP Equivalence for update/upgrade to SAP NW 7.4 SAP_BASIS 701 requires SP 3 SAP_BASIS 702 requires SP 3 SAP_BASIS 703 requires SP 1 SAP_BASIS 730 requires SP 1 SAP_BASIS 731 requires SP 1 SAP_BASIS 740 requires SP Collective Note for the Integration of SAP ERP with SAP Cloud for Travel and Expense Make sure that you regularly check this SAP Note. It contains the required SAP Notes per software component and is updated on regular basis The enterprise service-oriented architecture (ESOA) service ExchangeRateByExchangeRate QueryResponse is unusable or returns unexpected results. No matter which version of ESA ECC- SE is used, you must make sure to have SAP Notes and installed in your SAP Business Suite System. SAP SE Public Page 9 of 13

10 In your table for exchange rates TCURR, you have maintained exchange rates for non-iso currency codes such as "USDN" or "EUR3". These are incorrectly treated as a separate currency and are included in the selection, but are then converted into the assigned ISO code (for example, "USDN" -> "USD") before the output. In this case, the system returns the exchange rate for "USD" twice. The service callers may rely on the uniqueness of the currency. No matter which version of ESA ECC- SE is used, you must make sure to have SAP Notes and installed in your SAP Business Suite System Service ExchangeRateByExchangeRate QueryResponse_In Overview: Notes on Add-On ECC-SE When you call the service "ExchangeRateByExchangeRateQuery Response_In", the following communication error occurs: CX_SOAP_CORE:CX_ST_GROUP_MI SSING_CASE:XSLT exception.element 'ID' This note provides an overview of all notes concerning the ECC-SE add-on (ESA FAST TRACK), which deal with the following subjects: New installations Delta upgrade (add-on upgrade) Switch upgrade Add-on Support Packages This SAP Note contains a list of all Release Information Notes for: SAP ERP Enhancement Package Releases SAP ERP Enhancement Package Support Package (SP) Stacks Corresponding or equivalent SAP ERP 6.0 Support Package Stacks If you have installed an SAP ERP enhancement package the following equivalent Support Package (SP) levels are relevant for you. You can find more details in SAP Note SAP_APPL 607 requires SP 1 (also for SAP_APPL 607 on HANA) SAP_APPL 606 requires SP 1 SAP_APPL 605 requires SP 1 SAP_APPL 604 requires SP 2 SAP_APPL 603 requires SP 4 SAP_APPL 602 requires SP 5 SAP_APPL 601 requires SP New user exit in the functn module PAYROLLTRAVELEXPNSESP OST If you want to send expense report or taxation data to your SAP HCM system, you need to install the appropriate HR Support Package as described in this SAP Note SAP SE Public Page 10 of 13

11 SAP NetWeaver Process Integration: Release Recommendation Error 'EA/728/SOAP_MSGID_PREFIX _INVALID' IDoc XML-HTTP SOAP: Problem with SOAP class IDoc communication with SAP Business ByDesign Idocs via SOAP are not started immediately White list for SOAP Processer & IDoc SOAP Application Web service security WSSProfile XML signature not applied IDoc issue IDoc issue IDoc issue IDoc issue IDoc issue PI relevant 3.3 System Landscape 3.4 Authorizations The following authorizations are required: Authorizations for configuration guide 1. You need the authorization of System Administrator or SAP_ALL to run the ECC steps in configuration guide. 2. The connection user which connects from CfTE to ERP should have following authorization to a minimum. SAP SE Public Page 11 of 13

12 SAP_TEMOD_FIN_INTEGRATION Receiving Travel OnDemand Expense Reports in Central ERP Financials SAP_TEMOD_FIN_INTEGRATION_2 Sending Status Notification from ERP Financials to Travel OnDemand 3. Completed all onboarding steps for SAP Cloud for Travel and Expense. You need the authorization of Business Role System Administrator to run CfTE finetuning steps in configuration guide Authorizations for Test Script Please refer to each Test Script for authorizations. 3.5 Checklist Security Requirement For the infrastructure prerequisite for integration to ECC, the minimum security requirement is SSL between SAP Cloud for Travel and Expense and ECC systems. The landscape setup of this could be any way your ECC security rules have been established within your company. SAP recommends terminating SSL on a Web Dispatcher in the DMZ. You can use the Technical Connectivity Guide (can be downloaded from Service Marketplace. Please check the path in Appendix for SAP Cloud for Travel to help setup your landscape if using Web Dispatcher Certificate For the infrastructure security prerequisite for integration to ECC, certificate(s) are required for authentication on the test/prod landscapes. The creation of an SSL Server PSE and the creation of a certificate request / import of a CA signed certificate response is the default procedure. You have three choices when you setup the recommended Web Dispatcher. 1) The server certificate used by the reverse proxy must be trusted by the SAP Cloud for Travel and Expense tenant. Therefore, it must be signed by one of the certification authorities listed in the Supported Certification Authorities chapter of the Technical Connectivity Guide for SAP Cloud for Travel. 2) You can use a self-signed certificate, which you would need to add it to the server PSE and the SAP Cloud for Travel and Expense tenant too (within Admin work center). 3) You can also generate a temporary server certificate for you test system, but this would only be valid for 8 weeks and this is not recommended. For more information on security recommendations, review the Technical Connectivity Guide for SAP Cloud for Travel IP Range / Ports You need to check with your cloud service team about the IP Range/Ports information Other Questions Need to be Checked 1. Do you have your own onsite SAP Basis administrator to help with SAP ERP back end configuration? 2. Do you have your own onsite SAP PI expert to help with SAP PI configuration? 3. Can you provide a high level schematic of the network landscape where your on premise systems are located? 4. Do you have your own onsite network expert to help with the Network Security Setting? 5. Do you have a publically accessible DNS? 6. Are all identified ports for internal / external communication unblocked and tested? 7. Are all identified ports for external communication unblocked and tested? 8. Do you install and enable the internet web service runtime for SAP NetWeaver Application Server? 9. Does your landscape support the PKCS#7 standard for message signing and/or decryption? SAP SE Public Page 12 of 13

13 10. Has SAP s Cryptographic Library been imported from the SAP Service Marketplace into your SAP ERP system? 11. Has your SAP ERP system connected to your PI system already? 12. Are all identified ports for external communication unblocked and tested for PI? 13. Did you already sign the necessary CAs for your SAP ERP system? 14. Did you import the necessary CAs, which has been added into SAP trust list already, into your SAP PI system? 15. Have the validity (dates) of CAs been checked? 16. Did you already exchange the necessary CAs between your SAP ERP system and PI system? 17. Did you already upgrade "SPAM" tool of your SAP ERP system into the latest one? Minimal level Appendix You can select relevant version to get the Technical Connectivity Guide via Installation & Upgrade Guides on SAP Service Marketplace: Cloud Solution from SAP SAP Cloud for Travel and Expense relevant version Technical Connectivity Guide 3.7 FAQ Q: Can I automate the configuration? A: Manual configuration is utilized. Q: How can a partner get access to the service enabled Step-by-Step guide? A: This is subject to the SAP Education Services Agreement. SAP SE Public Page 13 of 13