SAP Cloud for Customer integration with SAP ERP: Software and Delivery Requirements

Transcription

1 SAP Cloud for 1502 March 2015 English SAP Cloud for integration with SAP ERP: Software and Delivery Requirements SAP SE Dietmar-Hopp-Allee Walldorf Germany Document Revisions Date

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 10

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 10

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

5 1 Purpose of the Document This document contains all 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) 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 Infrastructure team can respond to requests quickly enough e.g. CSS notes, patches, user requests, authorization changes and transports User interfaces agreed e.g. SAPGUI, NetWeaver Business Client, Silverlight or HTML 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 Solution Manager will be used.solution Manager set up with any relevant templates. Tool for project repository and collaboration agreed Test management tool agreed Responsibility 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: SAP SE Public Page 5 of 10

6 Product Product Version Component Comments SAP CLOUD FOR CUSTOMER 1502 SAP CLOUD FOR CUSTOMER 1502 Not applicable SAP ERP SAP ERP 6.0 SAP_APPL SAP ERP is connected to Cloud for system using SAP HCI and works as a back-end system. Ensure you at least have ERP 6.0, EHP 0, Support Package15 (SAP_APPL), SAP BASIS 7.0, Support Package 18 (SAP_BASIS) If you want to view the related: Sales order in accounts, you will need ERP 6.0 EHP2 Sales order in opportunity, you will need ERP 6.0 EHP3 Quotes and sales order as PDF in an opportunity, you will need ERP 6.0 EHP4 Exchange rate for currencies, you will need one of the following: ERP 6.0 EHP 2 SP 13, ERP 6.0 EHP 3 SP 12, ERP 6.0 EHP 4 SP 14, or ERP 6.0 EHP 5 SP11. Automatic configuration of code list mapping, you will need SP 13. SAP CLOUD CUST ERP INTEGR 2.0 SAP CLOUD CUST ERP INTEGR 2.0 SAP CODERINT 600 Latest Support Pack COD_ERP_INT 6.00 Add on CODERINT to be implemented in SAP ERP system. SAP HCI SAP HANA CLOUD INTEGR.(PI) Not applicable SAP HCI is used as an integration technology for integrating SAP ERP and SAP Cloud for. This is required if you are integrating SAP ERP using SAP HCI. SAP GUI for SAP GUI 7.30 or Not applicable Required for system SAP SE Public Page 6 of 10

7 Microsoft Windows higher administration functions and maintaining application Customizing. 3.2 SAP Notes The following SAP Notes need to be considered: SAP Note No Content Comments Relevance SAP Cloud for Integration with SAP ERP V Package specific note. Always check the SAP Note of the SAP Best Practices package for updates on the implementation Web service for Print Preview in Cloud for No orders are created IDoc XML-HTTP SOAP: Problem with SOAP class IDoc communication with SAP Business ByDesign SOA: Rounding error in net value ERP Customizing for Integration of SalesOnDemand Error message SFB 701 in service ECC_CUSTOMERQUOTE006QR Sales documents that are non-numeric are not selected ERP Customizing for Integration of SalesOnDemand SOAP: Dump HTTP_NO_MEMORY when sending IDocs Division determination in Sales Order Pricing Document flow: Quote and SalesOrder Basic ESOA: Too many reference documents displayed BAdI for BAPI SAP SE Public Page 7 of 10

8 Division determination in Quote/Sales Order Request Receiver Determination Address IDocs MATMAS: EOIO support for IDoc-SOAP communication Partner functions get partly deleted in SAP Cloud for Sales Unexpected element IDoc Type There are several processing issues in ERP inbound for ADRUPD and ADR3UPD IDoc types White List for SOAP Processor & IDoc SOAP Application We recommend that you restrict the list of IDoc types that may be processed by the inbound SOAP Processor C4C to ERP last contact not deleted Error "Person no. not found - function module CUSTOMER_GET_ADDR1_KEY_ERROR error Fill mandatory sales area specific fields when transferring accounts from C4C to ERP BC replication from ERP to "Cloud for " BC replication from ERP to "Cloud for " Code List Mapping issues Code List Mapping issues 3.3 SAP Solution Manager and SAP Solution Manager Content Add-On 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 SP18 or higher Or SAP Solution Manager 7.1 If using SAP Solution Manager 7.0 with SP below 24, see SAP Note SAP SE Public Page 8 of 10

9 SP01 or higher Or SAP Solution Manager 7.1 on HANA (ST 712) SP00 or higher 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 and SAP Note 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 Solution Package Name(s) RDS_CFCINT1502V1- SAP RDS for SAP Cloud for Integration_V1 SAP RDS for SAP Cloud for Integration_V1 3.4 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: Product Business Function Configuration or Data required ERP LOG_SD_SIMP_02 Planned Status of this business function should be ON Relevance All ERP Integration Scope Items Sales & Distribution Simplification 2 (Order-to- Cash). This is required to enable PDF Generation of Sales Order from Opportunity. SAP SE Public Page 9 of 10

10 3.5 Software Landscape Diagram This diagram is an abstract and business-oriented view of the technical system landscape. It is not a specification which, describes all the technical details of the real system landscape. In addition to the information, you can refer to the Technical Connectivity guide for generic connectivity issues. The diagram illustrates a typical setup for secure communication between the Cloud network and the on-premise network. Communication between the Cloud solution and the SAP ERP system must be secured by transport layer security (TLS) in both directions using the https protocol. SAP SE Public Page 10 of 10