EHP3 for SAP SCM
7.0
March 2015
English
SAP Demand and Supply
Network Planning
rapid-deployment solution:
Software and Delivery
Requirements
SAP SE
Document Revisions Date
0 26.03.2014
1 09.03.2015
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 http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark 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.
Icons
Icon Meaning Caution Example Note Recommendation Syntax External ProcessBusiness 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
Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT
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.
Example
text 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 Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. <Example
Table of Contents
Contents
1 Purpose of the Document ... 5
2 General Project Prerequisites ... 5
3 Technical Requirements ... 6
3.1 Software Product Versions... 6
3.2 SAP Notes ... 8
3.3 SAP Solution Manager and SAP Solution Manager Content Add-On ... 9
3.4 SAP Best Practices Solution Builder and Activation Content Add-On ... 10
3.5 Active Business Functions ... 11
3.6 Software Landscape Diagram ... 11
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 Responsibility
Kick off and workshop dates, location and attendees agreed Customer Customer team allocated with correct skills and training in place Customer Project sponsors and stakeholder identified Customer
Hardware fully commissioned Customer
Software licenses in place Customer
Infrastructure team can respond to requests quickly enough e.g. CSS notes, BW content, patches, user requests, authorization changes and transports
Customer
User interfaces agreed e.g. SAPGUI, Netweaver Business Client or Portal
Customer
Remote access is in place for SAP consultants and SAP Active Global Support
Customer
Decision made whether pre-assembled delivery will be used Customer Decision made whether SAP Best Practices Solution Builder will be
used to activate content.
Customer
Decision made whether Solution Manager will be used. Solution Manager set up with any relevant templates.
Customer
Tool for project repository and collaboration agreed Customer
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 SAP Solution Manager Logical Component Comments Relevance SAP Supply Chain Managem ent SAP enhancement package 3 for SAP Supply Chain Management 7.0 SAP SCM 7.13 SPS03 SAP LC/LCAPPS 10.0 SP 010 or above BI CONT ADDON 7.47 SAP SCM OPTIMIZER 10.0 SCM70_EHP3_ SCMSERV
Mandatory All Scope Items
SAP ERP SAP
enhancement package 7 for SAP ERP 6.0 Central Applications ERP60_EHP7_ CENTRAL_APP LICATION
Management 7.0, SAP enhancement package 6 for SAP ERP 6.0 or higher is supported. SAP NetWeav er Business Client SAP NetWeaver Business Client 4.0 for Desktop Not applicable
3.2 SAP Notes
The following SAP Notes need to be considered:
SAP Note No.
Content Comments Relevance
1928225
Exception when accessing navigation attribute properties
SAP SCM
1962561
Locking issues occur in SCM system when PIR are transferred from ECC to SCM
SAP SCM
1964028
Planner Homepage Demand Planning view raises
UNCAUGHT_EXCEPTION, LEADSEL does not exists dump.
Only required if SAP Planner’s Home Page is implemented
1945658
Data replication from SAP SCM to SAP HANA Live SP05
Only required if optional SAP Supply Chain Info Center is implemented.
1904500
Data replication from SAP SCM to SAP HANA Live SP04
Only required if optional SAP Supply Chain Info Center is implemented.
1964007
Delta replication does not work with compound info object characteristic
Only required if optional SAP Supply Chain Info Center is implemented.
1859871 Assignment to command
interfaces with generic type SAP ERP and SCM
1983649 Existing selection cannot be assigned to favourite
Only required if SAP Planner’s Home Page is implemented 1985463 Details of favorite selection
items cannot be read
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 SP01 or higher
Or
SAP Solution Manager 7.1 on HANA (ST 712)
SP00 or higher
If using SAP Solution Manager 7.0 with SP below 24, see SAP Note
1579267.
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
1726649 and SAP Note 1686668 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
RDS_DPSNP_SCM703V3 - SAP Demand and Supply Network Planning RDS_V3
Solution Package Name(s)
3.4 SAP Best Practices Solution Builder and Activation
Content Add-On
For tool-supported, automated activation of the solution package, SAP Best Practices solution builder is recommended.
Product Product Version Comments
SAP Best Practices solution builder
BP-SOLBLD 70Vx
Always use the latest available version as outlined in SAP Note 1301301.
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 SAP Note 1301301 (Release Strategy for SAP
Best Practices Package ABAP Add-ons)
(https://service.sap.com/sap/support/notes/1301301
Product Product Version Components
as tested Comments Relevance SAP Best Practices Configuration Content (for SAP SCM) 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). SCM system SAP Best Practices Configuration Content (for SAP ERP)
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). ERP system SAP Best Practices Configuration Content (for SAP NetWeaver)
731 BP-CANW Add-ons containing
3.5 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
Relevance
SCM SCM_APO_DP_SNP_CTM SCM-APO, Chart Usability (DP/SNP), Merging Orders (CTM)
Setting up Chart Engine (Optional)
SCM SCM_APO_HOME_PAGE SCM-APO, Planner's Home
Page (Reversible)
SCM-APO, Planner's Home Page
3.6 Software Landscape Diagram
SAP APO
with SAP HANA Side-by-Side
SAP APO
on SAP HANA data base
Live Cache SCM Server SCM Basis … SNC APO HanaDB Analytics VDM Live Cache SCM Server Classical DB SCM Basis … SNC APO HanaDB Analytics VDM SLT Replication LC replication LC replication
SAP APO with SAP HANA Side-by-Side
Master data is transferred from SAP SCM to SAP HANA database using SAP Landscape Transformation (SLT) replication
Transactional data is transferred to SAP HANA database using SAP liveCache (LC) replication
Full and delta replication of SAP APO data for snapshot and near to real time analytics
Platform for SAP Supply Chain Info Center and other future SAP HANA based SAP SCM developments
SAP APO on SAP HANA database
Master data is directly available in SAP HANA database - SLT replication is not required
Transactional data is transferred to SAP HANA database using SAP liveCache replication
Full and delta replication of SAP APO data for snapshot and near to real time analytics
Platform for Supply Chain Info Center and other future SAP HANA based SAP SCM developments
3.7 Connectivity
The following connectivity is required:
