Software and Delivery Requirements

Transcription

1 EHP3 for SCM 7.0 March 2015 English Demand and Supply Network Planning rapiddeployment solution: Software and Delivery Requirements SE Dietmar-Hopp-Allee Walldorf Germany Document Revisions Date

2 Copyright 2015 SE or an 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 SE or an affiliate company. and other products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SE (or an affiliate company) in Germany and other countries. Please see for additional trademark information and notices. Some software products marketed by SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SE or an affiliate company for informational purposes only, without representation or warranty of any kind, and SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SE or 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, 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 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 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. SE Public Page 2 of 12

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. SE Public Page 3 of 12

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

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) 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 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. GUI, Netweaver Business Client or Portal Remote access is in place for consultants and Active Global Support Decision made whether pre-assembled delivery will be used Decision made whether 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 Responsibility SE Public Page 5 of 12

6 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 Component s Solution Manager Logical Component Comments Relevance Supply Chain Managem ent enhancement package 3 for Supply Chain Management 7.0 SCM 7.13 SPS03 LC/LCAPPS 10.0 SP 010 or above BI CONT ADDON 7.47 SCM70_EHP3_ SCMSERV Mandatory All Scope Items SCM OPTIMIZER 10.0 ERP enhancement package 7 for ERP 6.0 Central Applications ERP60_EHP7_ CENTRAL_APP LICATION The Demand and Supply Network Planning rapid-deployment solution has been developed and tested on an enhancement package 7 for ERP 6.0 SP Level 03 installation. It contains automated content which requires enhancement package 7 for ERP 6.0 SP Level 03. All ERP Integration Scope Items According to the master guide of enhancement package 3 for Supply Chain SE Public Page 6 of 12

7 Management 7.0, enhancement package 6 for ERP 6.0 or higher is supported. NetWeav er Business Client NetWeaver Business Client 4.0 for Desktop Not applicable Optional Only required if optional Planner s Home Page is implemented or if you want to access Supply Chain Info Center using NetWeaver Business Client instead of your web browser. HANA Live for SCM HANA Live 1.0 for SCM HANA CONTENT HBA SCM 100 SP005 Supply Chain Info Center Supply Chain Info Center 1.0 APO_ANALY TICS 100 SP005 HANA HANA Appliance Software SPS07 HANA Server HANA Client HANA Studio SE Public Page 7 of 12

8 3.2 Notes The following Notes need to be considered: Note No. Content Comments Relevance Exception when accessing navigation attribute properties Locking issues occur in SCM system when PIR are transferred from ECC to SCM Planner Homepage Demand Planning view raises UNCAUGHT_EXCEPTION, LEADSEL does not exists dump. Data replication from SCM to HANA Live SP05 Data replication from SCM to HANA Live SP04 Delta replication does not work with compound info object characteristic Assignment to command interfaces with generic type Existing selection cannot be assigned to favourite Details of favorite selection items cannot be read SCM SCM Only required if Planner s Home Page is implemented Only required if optional Supply Chain Info Center is implemented. Only required if optional Supply Chain Info Center is implemented. Only required if optional Supply Chain Info Center is implemented. ERP and SCM Only required if Planner s Home Page is implemented Only required if Planner s Home Page is implemented SE Public Page 8 of 12

9 3.3 Solution Manager and Solution Manager Content Add-On For the implementation of the solution package, Solution Manager is recommended. Product Product Version Comments Solution Manager Solution Manager 7.0 Enhancement Package 1 SP18 or higher Or Solution Manager 7.1 SP01 or higher Or Solution Manager 7.1 on HANA (ST 712) SP00 or higher If using Solution Manager 7.0 with SP below 24, see Note For rapid-deployment solutions, implementation content is available in Solution Manager templates. The 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 Software Download Center on Service Marketplace at service.sap.com/swdc. For more information about downloading and installing ST-RDS 100 content add-ons, see Note and Note respectively. In the ST-RDS 100 content add-on, access the template in the following way: If you have Solution Manager 7.1 SP04 or lower, select the template ID and template name in the table below. If you have 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_DPSNP_SCM703V3 - Demand and Supply Network Planning RDS_V3 Demand and Supply Network Planning RDS_V3 SE Public Page 9 of 12

10 3.4 Best Practices Solution Builder and Activation Content Add-On For tool-supported, automated activation of the solution package, Best Practices solution builder is recommended. Product Product Version Comments Best Practices solution builder BP-SOLBLD 70Vx Always use the latest available version as outlined in Note 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). The following content is required: Always use the latest available version as outlined in Note (Release Strategy for Best Practices Package ABAP Add-ons) ( Product Product Version Components as tested Comments Relevance Best Practices Configuration Content (for SCM) Best Practices Configuration Content (for ERP) Best Practices Configuration Content (for NetWeaver) 703 BP-SCM Add-ons containing configuration content (only necessary to be implemented in the system which is used for the initial content activation (i.e. Sandbox or Development System). 607 BP-ERP Add-ons containing configuration content (only necessary to be implemented in the system which is used for the initial content activation (i.e. Sandbox or Development System). 731 BP-CANW Add-ons containing configuration content (only necessary to be implemented in the system which is used for the initial content activation (i.e. Sandbox or Development System). SCM system ERP system SCM system and ERP system SE Public Page 10 of 12

11 3.5 Active Business Functions Functionality in this solution package requires certain business functions to be active in the landscape. These business functions need to be activated: Product Business Function Configuration or Data required SCM SCM_APO_DP_SNP_CTM SCM-APO, Chart Usability (DP/SNP), Merging Orders (CTM) SCM SCM_APO_HOME_PAGE SCM-APO, Planner's Home Page (Reversible) Relevance Setting up Chart Engine (Optional) SCM-APO, Planner's Home Page 3.6 Software Landscape Diagram APO with HANA Side-by-Side APO on HANA data base SCM Server APO SNC Analytics SCM Server APO SNC Analytics SCM Basis LC replication SCM Basis LC replication VDM VDM Classical DB Live Cache HanaDB HanaDB Live Cache SLT Replication SCM powered by HANA - Deployment options SE Public Page 11 of 12

12 APO with HANA Side-by-Side Master data is transferred from SCM to HANA database using Landscape Transformation (SLT) replication Transactional data is transferred to HANA database using livecache (LC) replication Full and delta replication of APO data for snapshot and near to real time analytics Platform for Supply Chain Info Center and other future HANA based SCM developments APO on HANA database Master data is directly available in HANA database - SLT replication is not required Transactional data is transferred to HANA database using livecache replication Full and delta replication of APO data for snapshot and near to real time analytics Platform for Supply Chain Info Center and other future HANA based SCM developments 3.7 Connectivity The following connectivity is required: SCP: Settings for RFC Connectivity in ERP SCQ: Enhanced Connectivity in ERP SCR: Settings for RFC Connectivity in SCM SCS: Enhanced Connectivity in SCM DP0: SCM BW Connectivity with ERP SE Public Page 12 of 12