Download pdf - SAP® Supply Network Collaboration (SAP SNC) 7.0 … · Upgrade Master Guide Document version: 1.0 – 2016-01-27 SAP® Supply Network Collaboration (SAP SNC) 7.0 Including SAP Enhancement

Upgrade Master GuideDocument version: 1.0 – 2016-01-27

SAP® Supply Network Collaboration (SAP SNC) 7.0 Including SAP Enhancement Package 4Using SAP NetWeaver® 7.5

CUSTOMER

© Copyright 2016 SAP SE or an SAP affiliate company. Alle Rechte vorbehalten. All rights reserved. Tous droits réservés. Все права защищены.

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP SE oder ein SAP-Konzernunternehmen nicht gestattet.

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. All other product and service names mentioned are the trademarks of their respective companies. Please see www.sap.com/corporate-en/

legal/copyright/index.epx#trademark for additional trademark information and notices.

Terms for Included Open Source Software

This SAP software contains also the third party open source software products listed below. Please note that for these third party products the following special terms and conditions shall apply.

2

CUSTOMER© Copyright 2016 SAP SE or an SAP affiliate company.All rights reserved. SAP® Supply Network Collaboration (SAP SNC) 7.0 Including SAP Enhancement Package 4

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark

Documentation on the SAP Service Marketplace

You can find this document at the following address: service.sap.com/instguides

SAP® Supply Network Collaboration (SAP SNC) 7.0 Including SAP Enhancement Package 4Documentation on the SAP Service Marketplace

CUSTOMER© Copyright 2016 SAP SE or an SAP affiliate company.

All rights reserved. 3

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Finstguides

Typographic Conventions

Table 1

Example Description

< > Angle brackets indicate that you replace these words or characters with appropriate entries to make entries in the system, for example, “Enter your <User Name>”.

Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the documentation

Example Textual cross-references to an internet address, for example, www.sap.com

/example Quicklinks added to the internet address of a homepage to enable quick access to specific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ● Words or characters quoted from the screen. These include field labels, screen titles, pushbutton labels, menu names, and menu options.

● Cross-references to other documentation or published works

Example ● Output on the screen following a user action, for example, messages

● Source code or syntax quoted directly from a program

● File and directory names and their paths, names of variables and parameters, and names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, database table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

4

CUSTOMER© Copyright 2016 SAP SE or an SAP affiliate company.All rights reserved.

SAP® Supply Network Collaboration (SAP SNC) 7.0 Including SAP Enhancement Package 4Typographic Conventions

http://help.sap.com/disclaimer?site=Example

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.sap.com

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2F~form%2Fhandler%3F_APP%3D01100107900000000342%26_EVENT%3DREDIR%26_NNUM%3D123456%26_NLANG%3Den%26_NVERS%3D0


Document History

CautionBefore you start the implementation, make sure you have the latest version of this document. You can find the

latest version on SAP Service Marketplace service.sap.com/instguides .

The following table provides an overview on the most important document changes:

Table 2

Version Date Description

1.0 2016-01-27 Version 1

SAP® Supply Network Collaboration (SAP SNC) 7.0 Including SAP Enhancement Package 4Document History




Content

1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1 About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.2 Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.3 Important SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2 SAP Supply Network Collaboration Upgrade Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.1 Upgrade at a Glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.2 Upgrade Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.3 Enhancement Package Key Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.4 Key Facts About Enhancement Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.5 Application Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

SAP Supply Network Collaboration (SAP SNC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 SAP Supply Chain Management Server (SAP SCM Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 SAP ERP – ECC Server – S/4HANA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 SAP Portfolio and Project Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 SAP Event Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2.6 Technology Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 SAP NetWeaver Process Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2.7 Sets of Software Components and Software Units in SAP SNC Landscapes . . . . . . . . . . . . . . . . . . . 21 Software Component Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Software Units for the Business Processes of SAP SNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

2.8 Minimal System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.9 Overall Upgrade Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

3 SAP SNC on SAP HANA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.1 Introduction to Using SAP HANA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.2 Technical System Landscape Using SAP HANA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.3 Update/Upgrade and Migration Process: Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4 Business Processes of SAP SNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.1 Responsive Demand Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.2 Responsive Replenishment Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354.3 Purchase Order Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374.4 Supplier Managed Inventory (SMI) with Replenishment Order Processing . . . . . . . . . . . . . . . . . . . . 384.5 Delivery Control Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394.6 Dynamic Replenishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404.7 Invoice Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414.8 Self-Billing Invoice Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

5 Solution-Wide Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445.1 SAP Solution Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445.2 Extended Implementation Content in SAP Solution Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445.3 Service-Oriented Architecture (SOA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Service Enablement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

6


SAP® Supply Network Collaboration (SAP SNC) 7.0 Including SAP Enhancement Package 4Content

Installation of the Service-Oriented Architecture (SOA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48A.1 List of Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48A.2 Media List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49A.3 Tools and Resources for Planning Your System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Business Process Repository (BPR) Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Using the BPR Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

B Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52B.1 The Main SAP Documentation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

SAP® Supply Network Collaboration (SAP SNC) 7.0 Including SAP Enhancement Package 4Content



8

CUSTOMER© Copyright 2016 SAP SE or an SAP affiliate company.All rights reserved. SAP® Supply Network Collaboration (SAP SNC) 7.0 Including SAP Enhancement Package 4

1 Getting Started

SAP Supply Network Collaboration

Supply network collaboration can take place upstream between your company and your suppliers, and downstream between you and your customers.

Supplier collaboration refers to a collaborative business process in which one of the companies is a manufacturer or customer in a typical buy-sell relationship. Collaboration processes and capabilities in this relationship take place between the manufacturer and its suppliers.

With the increase in globalization and outsourcing, supplier collaboration has become even more complex. For example, a manufacturer working with several contract manufacturing suppliers may also be collaborating with a number of component suppliers as well. In turn, some of these component suppliers may not only be providing goods directly to the manufacturer, but to some of its contract manufacturing suppliers as well. This creates a complex web of collaborative connections that can make it difficult for all parties involved to share essential data regarding shipments, supplies on hand, quality, manufacturing capacity, and other factors that impact productivity.

Customer collaboration includes the business processes that result when the manufacturer is the seller and distributors, wholesalers or retailers are the customers.

1.1 About this Document

This SAP Supply Network Collaboration (SAP SNC) Upgrade Master Guide provides a central starting point for the technical implementation of an SAP SNC upgrade. It contains all the information for the upgrade of SAP SNC business processes.

SAP SNC consists of the following business processes:

● Responsive Demand Planning

● Responsive Replenishment Planning

● Purchase Order Processing

● Supplier Managed Inventory with Replenishment Order Processing

● Delivery Control Monitor

● Dynamic Replenishment

● Invoice Processing

● Self-Billing Invoice Processing

To facilitate the implementation and upgrade, all information within this document is ordered by business processes. You can choose from several generic business processes and find all the information that is relevant for the technical implementation of a specific business process in that particular section.

In addition to the business processes mentioned above, there are a number of industry business scenarios running on SAP SNC:

SAP® Supply Network Collaboration (SAP SNC) 7.0 Including SAP Enhancement Package 4Getting Started



Table 3

Business Scenario Industry

Supplier Managed Inventory Automotive

Release Processing Automotive

Web-Based Supplier Kanban Automotive

Web-Based Supplier Kanban with MRP Automotive

Responsive Replenishment Consumer Products

Supply Network Inventory High Tech

Contract Manufacturing Procurement High Tech

Work Order Collaboration High Tech

NoteThe central starting point for the technical implementation of your SAP solution is the Master Guide, which

you can find on SAP Service Marketplace at service.sap.com/instguides .

Use the Upgrade Master Guide to get an overview of the upgrade paths, the upgrade of the involved software units and scenarios from a technical perspective. The Upgrade Master Guide is a planning tool that helps you to decide what software units you have to upgrade taking into account the dependencies between the software units. It refers you to the required detailed documentation, mainly:

● Upgrade guides for single software units

● SAP Notes

● Configuration documentation

● SAP Library documentation

For a general overview of available SAP documentation, see The Main SAP Documentation Types.

For more information about these business scenarios, see the appropriate industry Master Guides on the SAP

Service Marketplace at service.sap.com/instguides Industry Solutions Industry Solution Master Guides .

For more information about the upgrade of these business scenarios, see the respective Upgrade Master Guides

at service.sap.com Industry Solutions Industry Solution Guides .

This Upgrade Master Guide provides information about which components and guides are required during the installation:

● Getting Started [page 9] contains valuable information about using this document and related information (documentation and SAP Notes) crucial to the installation and upgrade.

● Solution-Wide Topics [page 44] contains a short description of the software components that are part of SAP SNC.

● The Software Component Matrix [page 22] provides the information about which business processes use which component and whether the corresponding component is mandatory or optional.

● Minimal System Landscape [page 23] contains information about the minimum technical landscape that is needed by the business processes of SAP SNC.

● SAP SNC on SAP HANA [page 27] provides information about the upgrade to an SAP HANA database.

● Business Processes of SAP SNC [page 34] contains the following information for all SAP SNC business processes:

10





http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com

○ Business process overview

○ Information about the required technical system landscape

● Depending on the specific business process, different installation and master guides are required during the business process implementation.

NoteYou can find the most current information about the technical upgrade of SAP SNC and the latest upgrade,

installation, and configuration guides on SAP Service Marketplace at service.sap.com/instguides .

We strongly recommend that you use the documents available here. The guides are regularly updated.

Constraints

● The business scenarios that are presented here serve as examples of how you can use SAP software in your company. The business scenarios are only intended as models and do not necessarily run the way they are described here in your customer-specific system landscape. Ensure to check your requirements and systems to determine whether these scenarios can be used productively at your site. Furthermore, we recommend that you test these scenarios thoroughly in your test systems to ensure they are complete and free of errors before going live.

● This Upgrade Master Guide at hand primarily discusses the overall technical upgrade of name of solution, rather than its subordinate components. This means that additional software dependencies may exist without being mentioned explicitly in this document. You can find more information about component-specific software dependencies in the corresponding upgrade guides.

1.2 Related Information

Planning Information

For more information about planning topics not covered in this guide, see the following content on SAP Service Marketplace:

Table 4

Content Location on SAP Service Marketplace

Latest versions of installation and upgrade guides service.sap.com/instguides

SAP Upgrade Info Center – general information about upgrade topics and solution-specific upgrade information

support.sap.com/upgrade

Information about network security – SAP Security Guide service.sap.com/securityguide

Sizing and calculation of hardware requirements – such as CPU, disk and memory resource

service.sap.com/sizing

Released platforms and technology-related topics such as maintenance strategies and language support

service.sap.com/platforms

To access the Platform Availability Matrix directly, enter

support.sap.com/pam






http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fupgrade

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fsecurityguide

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fsizing

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fplatforms

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fpam


Network security service.sap.com/securityguide

High Availability scn.sap.com/docs/DOC-7848

Performance of SAP Software Solutions service.sap.com/performance

Information about Support Package Stacks, latest software versions and patch level requirements

support.sap.com/sp-stacks

Information about Unicode technology scn.sap.com/docs/DOC-8284

Further Useful Links

The following table lists further useful links on SAP Service Marketplace:

Table 5

Content Location in SAP Service Marketplace

Information about creating incidents support.sap.com/message

SAP Notes search support.sap.com/notes

SAP Software Distribution Center (software download and ordering of software)

support.sap.com/swdc

SAP Online Knowledge Products (OKPs) – role-specific Learning Maps

service.sap.com/rkt

Related Master Guides

This Upgrade Master Guide is based on Upgrade Master Guides for cross-industry solutions. You can find more information about the relevant solutions in the following documents:

Table 6

Title Location

Upgrade Master Guide for SAP Supply Chain Management 7.0 including enhancement package 4

service.sap.com/instguides

Upgrade Master Guide for SAP Event Management 9.2 service.sap.com/instguides

Upgrade Master Guide for SAP Portfolio and Project Management 6.1


Upgrade Master Guide for Automotive service.sap.com/instguides

Upgrade Master Guide for Consumer Products service.sap.com/instguides

Upgrade Master Guide for High Tech service.sap.com/instguides

Related Business Functions

The following table lists related business functions for SAP SNC 7.0 including enhancement package 4

12




http://help.sap.com/disclaimer?site=http%3A%2F%2Fscn.sap.com%2Fdocs%2FDOC-7848

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fperformance

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fsp-stacks

http://help.sap.com/disclaimer?site=http%3A%2F%2Fscn.sap.com%2Fdocs%2FDOC-8284

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fmessage

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fnotes

http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fswdc

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Frkt







Table 7

Content Location

Information about the business function for SAP SNC SAP Library for SAP Supply Network Collaboration on SAP

Help Portal at help.sap.com/snc704 . In SAP Library,

choose Business Functions (SAP Enhancement Package 4

for SAP SNC 7.0) Business Functions in SAP SNC Supply

Network Collaboration 1 .

SAP Library for SAP Supply Network Collaboration on SAP








for SAP SNC 7.0) Business Functions in SAP SNC SNC

Optimizations for SAP HANA .






1.3 Important SAP Notes

You must read the following SAP Notes before you start the upgrade. These SAP Notes contain the most recent information about the upgrade, as well as corrections to the upgrade documentation.

Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP Service Marketplace

at service.sap.com/notes .

Table 8

SAP Note Number Title Description

836200 SAP NetWeaver 7.0: Importing Process Integration

1180861 SAP SNC 7.0 ERP integration

2171392 EHP4 for SAP SCM 7.0 SP stacks - Release & Information Note

2265871 Implementation recommendations for SNC 7.04 (EHP 4)

1169790 SAP SNC 7.0x: Steps After Upgrade




http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fsnc704




http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fnotes







1388258 Version Interoperability within the SAP Business Suite

1064596 Making cFolders and EM IMG visible in SNC Installation

944221 Troubleshooting if problems occur in forms processing

2050605 Installation/upgrade SCEMSRV 920

2242851 Installation/Upgrade SCMSNC 704 on NW 7.0 EHP5

1821685 Installation/delta upgrade CPRXRPM 610_740 to NW 7.5

1224284 Enterprise Services, Installing and Accessing the SOA Docu

1224543 Release of ESR/PI Content for SAP NetWeaver PI 7.1

Process Integration (PI) Content (also called ESR Content) that is released in SAP Business Suite for SAP NetWeaver Process Integration 7.0 is now generally released for SAP NetWeaver Process Integration 7.1. This means that ESR Content that has been used or enhanced on the basis of SAP NetWeaver PI 7.0 can also be used on the basis of an SAP NetWeaver PI 7.1 implementation.

1515223 SAP NetWeaver Process Integration: Release Recommendation

This SAP note sets out our recommendation on which release of SAP NetWeaver PI you should use.

1943931 BI Content 7.06: Information about Installation and Delta

14













2 SAP Supply Network Collaboration Upgrade Overview

2.1 Upgrade at a Glance

Table 9: Component Mapping Table for an SAP Supply Network Collaboration (SAP SNC) upgrade from SAP SNC 5.1 to SAP SNC 7.0 including enhancement package 4

SAP SNC 5.1 SAP SNC 7.0 EHP4 Action / Further Information

SAP SCM Server 2007 SAP SCM Server 7.0 including enhancement package 4

Upgrade

SAP SNC 5.1 SAP SNC 7.0 including enhancement package 4

Upgrade

SAP NetWeaver 7.0 (2004s) SAP NetWeaver 7.5 Upgrade

SAP NetWeaver 7.0 (2004s) usage type Process Integration (PI)

SAP NetWeaver Process Integration (PI) 7.31

Upgrade

RecommendationWe recommend you read and

consider SAP Notes 1574235 ,

1865292 and 2230615 .

XI Content for SAP SNC 5.1 XI Content for SAP SNC 7.0 including enhancement package 4

Migration of content

SAP ERP 6.0 – ECC server SAP ERP 6.0 – ECC server Migration of content

If you require functions from SAP ERP 6.0 EHP8, you must upgrade to that SAP ERP release.

SAP NetWeaver 7.0 (2004s) usage type BI

SAP NetWeaver Business Warehouse 7.5

Migration of content

SAP BI Content 7.03 SP6 BI Content 7.57 Upgrade

SAP cProjects Suite 4.00 SAP Project and Portfolio Management 6.1

Upgrade

SAP Event Management 5.1 SAP Event Management 9.2 Upgrade

SAP® Supply Network Collaboration (SAP SNC) 7.0 Including SAP Enhancement Package 4SAP Supply Network Collaboration Upgrade Overview






2.2 Upgrade Paths

Upgrading from SAP Supply Network Collaboration

An upgrade to SAP Supply Network Collaboration (SAP SNC) 7.0 including enhancement package 4 is supported based on SAP SNC 5.1.

Upgrading from SAP Inventory Collaboration Hub

The two applications SAP Inventory Collaboration Hub (SAP ICH) and SCM Basis were previously an integral part of SAP Supply Chain Management (SAP SCM). As of Release 5.1, SAP SNC 5.1 and SCM Basis are de-coupled from SAP SCM, so it is now possible to use SAP SNC together with SCM Basis outside of an SCM Server installation. (Technically, SAP SNC and SCM Basis as of Release 5.1 are add-ons to SAP NetWeaver.) If you want to upgrade from SAP ICH 5.0 to SAP SNC 5.1 or a higher SAP SNC Release, we recommend that you use the upgrade path described for an SCM Server upgrade. For information about an upgrade of an SCM Server version of the application, see the Upgrade Master Guide for SAP Supply Chain Management 7.0 EHP4, under

service.sap.com/instguides .

After the upgrade you must consider the following SAP Notes:

● 1019288 (Steps after upgrade to Release 5.1)

● 1169790 (Steps after upgrade to Release 7.0)

2.3 Enhancement Package Key Concept

We have adapted our major release strategy to better fit your adoption cycle. To ensure that you benefit from new developments and innovations while minimizing the impact on your core operational systems, SAP uses enhancement packages to speed up the delivery of new functions.

With SAP enhancement packages, you can install and activate new functions depending on your business needs without having to perform a system upgrade.

You can selectively implement the new functions and activate the software upon business demand. As a result, you can isolate the impact of software updates and make new functions available faster due to shortened test cycles.

Implementation

There are three different scenarios to implement an enhancement package:

● Installation of an enhancement package on an existing SAP system (update)

● New installation of an SAP system including an enhancement package (installation)

● Upgrade of an SAP system including an enhancement package (upgrade)

To implement new business functions you carry out the following two steps:

● Technical installation of an enhancement package

● Activation of business functions using the switch framework technology

You have a choice on both levels – installation and activation. You do not need to install a full enhancement package. Instead, you can update the software components that are related to the functional enhancements you want to use.

16






NoteKeep in mind that you cannot mix the installation of different enhancement package versions in your ABAP-based SAP system. You can have just one enhancement package version in the SAP system.

From a business point of view, functional enhancements are grouped into business functions (BFs). The technical installation of the business functions does not change the system behavior. The new functions are available in the system, but are not active. After the installation, no user interface or process change takes place. You must explicitly activate new functions so that they become visible in the system. As a result, changes are predictable and there are no side effects as only the activated areas change.

With the switch framework technology (transaction SFW5), it is possible to control the activation of new SAP objects in ABAP-based SAP systems. The activation process triggers a background job that automatically performs all changes in the SAP system.

CautionYou cannot reverse most business function once they are activated. Due to technical restrictions, only a limited number of business functions are reversible.

After you have activated a business function, you can see the changes and new developments in the SAP system, for example:

● Menu entries

● New screens

● New fields on the application user interfaces

● IMG activities required for the implementation

● New table entries in Customizing tables and system tables

You can create a transport request with the current settings of the switch framework. You can check functional changes and the impact of an activated business function in advance in the business function documentation.

RecommendationTest the installation and activation on a sandbox system.

Maintenance

SAP enhancement packages have Support Packages of their own that are equivalent to the Support Package versions of the underlying SAP system. We highly recommend installing the enhancement package in combination with the latest available Support Package stack. This approach reduces installation, modification adjustment, and testing effort. Using this strategy, you can install SAP enhancement packages as a normal maintenance activity together with Support Package stacks.

An enhancement package requires a specific Support Package stack level in the source release SAP system.

NoteIf the SAP system is on a lower Support Package stack level, all relevant Support Package stacks for the EHP installation are automatically included into the download queue by the Maintenance Optimizer, as well as the latest available Support Packages for the enhancement package.

Tools

The enhancement package installation requires the following tools:




● SAP Solution Manager

NoteUse of SAP Solution Manager is mandatory.

SAP recommends that you use SAP Solution Manager 7.1, SPS 10 or higher.

For more information, see SAP Support Portal at support.sap.com/solutionmanager .

Make sure that you have correctly defined and maintained your system landscape in SAP Solution Manager (transaction SMSY). To verify and correct your system landscape SAP highly recommends that you use the Landscape Verification Tool (LVT) for SAP Solution Manager 7.0, which is an add-on to your SAP Solution Manager 7.0 system. This add-on allows you to identify and correct issues in your SAP Solution Manager landscape (transaction SMSY) before they cause problems, for example during a system update. Examples for errors are a missing connection to the System Landscape Directory or the wrong assignment of products to technical systems. For each type of error, a generic description for the solution is provided.

For more information about the landscape verification add-on, see SDN at www.sdn.sap.com/irj/sdn/alm?

rid=/webcontent/uuid/70fc3790-7ec9-2d10-57ad-95b2d0d1185d .

RecommendationBefore installing the enhancement package, we recommend that you install the landscape verification add-on to check your landscape setup and your data (transaction SMSY) and to correct data should it be necessary.

● Installation and Update Tools

Installation or upgrade tools (depending on your scenario).

The SAP Solution Manager Maintenance Optimizer (transaction SM_WORKCENTER) supports the download of a consistent queue that includes all necessary Support Packages and enhancement packages. In addition, SAP Solution Manager calculates a valid import queue for the selected SAP system and generates the enhancement package stack configuration file that you require for the installation.

For the new installation of an SAP system including enhancement package you use the standard installation tool Software Provisioning Manager (SWPM).

To install an enhancement package on an existing SAP system, as well as for the upgrade of an SAP system to a higher release including an enhancement package, you use the Software Update Manager (SUM).

For more information about SWPM and SUM, see the documentation at service.sap.com/sltoolset .

2.4 Key Facts About Enhancement Packages

The following list summarizes important facts about the enhancement package concept and recommended approaches:

● Install only selected parts of the enhancement package. The selection is driven by the functional need from a business point of view.

● You cannot mix the installation of different enhancement package versions in your ABAP-based SAP system. You can have just one enhancement package version in the SAP system. This means, if you have already updated technical usages to a previous EHP you need to apply the current EHP to those components as well.

18



http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fsolutionmanager

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.sdn.sap.com%2Firj%2Fsdn%2Falm%3Frid%3D%2Fwebcontent%2Fuuid%2F70fc3790-7ec9-2d10-57ad-95b2d0d1185d


http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fsltoolset

● SAP enhancement packages are cumulative, meaning that each new enhancement package includes new innovations of its own as well as all innovations delivered with prior packages.

● We recommend installing the latest available enhancement package version.

● Install enhancement packages and Support Packages in one single step (this includes the preconditioned Support Packages).

● SAP enhancement packages have Support Packages of their own that are equivalent to the Support Package versions of the underlying SAP system.

● SAP enhancement packages have the same maintenance period as the underlying core application.

● The installation of an enhancement package is irreversible.

● As long as you do not activate a business function, the installation of an enhancement package has no impact on existing business processes or user interfaces.

You can only activate business functions in ABAP-based systems, not in Java-based SAP systems.

● The activation of most business functions and extension sets is irreversible. Only a small number of business functions is reversible.

Test the installation process and activation of new functions in advance on a sandbox system. Ensure that you evaluate the runtime and the SAP system behavior, its dependencies and impacts. Make sure that your SAP system is free of errors before going live.

2.5 Application Components

2.5.1 SAP Supply Network Collaboration (SAP SNC)

SAP Supply Network Collaboration (SAP SNC) is an application that supports participants in a complex supply chain network to collaborate efficiently with each other. SAP SNC supports, among other things, the management of inventories by suppliers and customers, timely shipments of replenishments, and advanced shipping notification and invoice creation. It also supports forecasting processes and work order collaboration.

2.5.2 SAP Supply Chain Management Server (SAP SCM Server)

SAP Supply Chain Management Server (SAP SCM Server) is part of the SAP Supply Chain Management application suite. It is an advanced planning and scheduling tool that enables real-time decision support and collaborative network optimization across the extended supply chain. SAP SCM Server helps companies synchronize supply chain activities with their partners and excel to improve customer service and order fulfillment. For more information, see the SAP SCM Master Guide available in SAP Service Marketplace at

service.sap.com/instguides/ SAP Business Suite Applications SAP SCM .




http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Finstguides%2F

2.5.3 SAP ERP – ECC Server – S/4HANA

Product instance SAP ERP 6.0 - SAP ECC Server (SAP ERP Central Component) consists of product version SAP ECC 6.0. It is the central component of SAP ERP 6.0 and is the successor component of SAP ERP 5.0, and thus the successor of the previous SAP R/3 releases.

For more information, see the ERP Master Guide on SAP Service Marketplace at service.sap.com/instguides

SAP Business Suite Applications SAP ERP SAP ERP 6.0 Planning .

SAP SNC 7.0 EHP4 can be linked to ERP systems by SAP. This also includes SAP S/4HANA, on-premise edition.

For more information, see SAP Note 2238445 .

2.5.4 SAP Portfolio and Project Management

SAP Portfolio and Project Management 6.1 (technical component CPRXRPM) is the foundation for processes dealing with operational project management and collaboration in product development with Collaboration Folders (cFolders). For SAP Supply Network Collaboration, you can activate cFolders.

For more information about cFolders, see SAP Service Marketplace at service.sap.com/plm-inst SAP PLM Collaboration Folders 4.5 .

For more information about the deployment options, see the Master Guide for SAP Portfolio and Project

Management available in SAP Service Marketplace at service.sap.com/plm-inst Using SAP Portfolio and Project Management 6.1 .

2.5.5 SAP Event Management

SAP Event Management 9.2 offers you the possibility to process application objects in various application systems and thereby to track events for individual objects, processes, or parts of these throughout the entire supply chain. The Web Dynpro ABAP-based web interface offers information access and full supply chain visibility for SAP Event Management 7.0, for example, via the Internet. SAP Event Management can link, update, and evaluate the event messages with the application data from the supply chain network. It allows you to:

● Monitor, measure, and evaluate business processes

○ SAP Event Management automatically monitors events that occur and those that have not been reported (for example, goods issue, purchase order transfer, production end, or unreported proof of delivery).

○ SAP Event Management can automatically transfer data to a data warehouse system that uses key performance indicators to create performance data for the quality of execution and notification.

● Employ checking processes and notify persons responsible to control events

○ SAP Event Management checks the Supply Chain Event Management-relevant objects as soon as they are saved in the application system.

○ SAP Event Management can automatically inform the decision maker in critical situations that action is required (for example, automatic rescheduling of the subsequent process step when a delay has occurred)

● Exchange and query information between partners (for example, e-mail or Internet)

20





http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fplm-inst

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fplm-inst

RecommendationIf you want to use SAP Event Management together with SAP Auto-ID Infrastructure, you must use SAP enhancement package 1 for SAP Event Management 7.0 only together with SAP Auto-ID Infrastructure 7.1.

Together with SAP Supply Network Collaboration (SAP SNC), you can use SAP Event Management to monitor processes. This is based on events that are expected in a process by specific dates/times at the latest. Delays in the actual events lead to alerts. The following visibility processes are available:

● SNC Visibility Process for Inbound Message

● SNC Visibility Process for Purchase Order

● SNC Visibility Process for Replenishment Order

For more information about using SAP SNC with SAP Event Management, see SAP Library for SAP Supply

Network Collaboration on SAP Help Portal at help.sap.com/snc704 . In SAP Library, choose SAP Supply Network Collaboration (SAP SNC) Cross-Application Functions Visibility Processes for SAP SNC .

2.6 Technology Components

2.6.1 SAP NetWeaver Process Integration

Based on a native Web infrastructure that leverages open standards, SAP NetWeaver Process Integration (SAP PI) makes it possible to manage the broad diversity of highly heterogeneous components from a multitude of vendors and to run in various technology environments. The integration capabilities capture shared business semantics and act as a mediator between the services and their technical implementations. It includes technical functions, such as Web service discovery, queuing, mapping, and routing. It also establishes an infrastructure for business process management and high-performance execution within and across organizational boundaries.

Exchange-based process integration removes the problems of direct connections by extracting shared collaboration knowledge. These shared business semantics ease the integration of both external and internal components. Instead of directly coding point-to-point interfaces for each new component, the exchange infrastructure allows instant plug-in of new components once per component. This provides the flexibility needed in today’s fast-changing business world, and it reduces integration costs compared to the direct connection approach.

2.7 Sets of Software Components and Software Units in SAP SNC Landscapes

2.7.1 Software Component Matrix

You can upgrade or update your SAP SNC system to SAP enhancement package 4 for SAP Supply Network Collaboration 7.0 on SAP NetWeaver 7.5.





NoteYou can install SAP NetWeaver 7.5 on any database, not exclusively on SAP HANA.

Table 10: Set of Software Components of SAP SNC for SAP NetWeaver 7.5

SAP NetWeaver 7.5

SAP AP 7.50

MDG FOUNDATION 749

SAP SCM BASIS 7.14

SAP WEB UIF 748

SAP_BS_FOUNDATION 748

SCMB PLUS 7.14

SNC 7.14

SCEMSRV 9.2

2.7.2 Software Units for the Business Processes of SAP SNC

This section provides an overview of which business process of SAP Supply Network Collaboration (SAP SNC) uses which software unit.

For the latest component version and patch level requirements, see SAP Service Marketplace at DownloadsAdditional Download Info SAP Stack Information & Download . Alternatively, you can quick link /sp-stacks in SAP Service Marketplace

You can also implement the business processes with SAP enhancement package 2 for SAP Supply Network Collaboration 7.0.

Table 11: Software Units for SAP Enhancement Package 4 for SAP SNC 7.0

SAP SNC Business Processes

Software Unit

Business Process

SAP SCM Server 7.0 EHP 4

SAP SNC 7.0 EHP 4

SAP NetWeaver 7.5

SAP ERP 6.0

SAP ERP 6.0 EHP 6 or higher

SAP NetWeaver BW 7.5

SAP NetWeaver PI 7.31 or higher

Responsive Demand Planning

Required Required One option required Optional SAP NetWeaver PI 7.31 or higher recommended

Responsive Replenishment Planning

Required Required One option required Optional SAP NetWeaver PI 7.31 or higher recommended

22



SAP SNC Business Processes

Software Unit

Business Process

SAP SCM Server 7.0 EHP 4

SAP SNC 7.0 EHP 4

SAP NetWeaver 7.5

SAP ERP 6.0

SAP ERP 6.0 EHP 6 or higher

SAP NetWeaver BW 7.5

SAP NetWeaver PI 7.31 or higher

Purchase Order Processing

One option required Required Limited functionality

Required Optional SAP NetWeaver PI 7.31 or higher recommended

Purchase Order Processing with the Simplifed User Interface*



SMI with Replenishment Order Processing



Delivery Control Monitor

One option required Required One option required Optional SAP NetWeaver PI 7.31 or higher recommended

Dynamic Replenishment



Invoice Processing


Self-Billing Invoice Processing


*for this option you also need SAP NetWeaver Gateway and SAP Web Dispatcher

2.8 Minimal System Landscape

The following diagram provides an overview of the minimal system landscape for SAP Supply Network Collaboration (SAP SNC). Depending on which business processes you reuse from SAP or which business processes you design and implement yourself, you need a different system landscape.




Figure 1: Minimal System Landscape

This is the minimal system landscape for the business processes covered by this SAP SNC Upgrade Master Guide. For more information about the requirements – systems, software units, and their releases – for each process, see Software Units for the Business Processes of SAP SNC [page 22].

CautionWe strongly recommend that you use a minimal system landscape for test and demo purposes only. For performance, scalability, high availability, and security reasons, do not use a minimal system landscape as your production landscape.

2.9 Overall Upgrade Sequence

The following table describes the overall upgrade sequence for SAP Supply Network Collaboration (SAP SNC).

This table contains all available software units. However, to run a specific scenario, you only need a subset of available software units. Some are only required for special processes. For information about which software is required to run a specific scenario, see Software Component Matrix [page 22].

For the latest component version and patch level requirements, see SAP Service Marketplace at DownloadsAdditional Download Info SAP Stack Information & Download . Alternatively, you can quick link /sp-stacks in SAP Service Marketplace.

For documentation listed in the following table, see List of Documents [page 48].

24



Process

Table 12

Step Action

Required Documentation

Remarks / Subsequent Steps

1 Upgrade to SAP NetWeaver 7.5.

For more information, see service.sap.com/

upgradenw75 .

2 Upgrade to SAP NetWeaver Process Integration (PI) 7.5.


upgradenw75 .

3 Upgrade to SAP NetWeaver Business Warehouse 7.5.


upgradenw75 .

For more information, see SAP Note 1388258

4 Upgrade to SAP ERP 6.0 – SAP ECC Server.


instguides .

For some SAP SNC business processes you must install SAP enhancement package 4 or SAP enhancement package 5 for SAP ERP 6.0 or higher. For more information, see Software Component Matrix [page 22].

5 Upgrade to SAP SCM Server 7.0 EHP4.


instguides .

An upgrade to SAP SCM Server 7.0 EHP4 is only required if you plan on running business processes for which an SAP SCM Server installation is required or optional. For more information, see Software Component Matrix [page 22].

6 Upgrade to SAP SNC 7.0 EHP4 including SAP SCM BASIS 704. For more information, see

service.sap.com/instguides .

An upgrade to SAP SNC 7.0 EHP4 is only required if you plan on running or enhancing business processes for which SAP SNC 7.0 EHP4 is required or optional. For more information, see Software Component Matrix [page 22].

7 Upgrade to SAP Event Management 9.2. For more

information, see service.sap.com/instguides .

An upgrade to SAP Event Management 9.2 is only required if you plan on running or enhancing business processes for which SAP Event Management 9.2 is required or optional. For more information, see Software Component Matrix [page 22].




http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fupgradenw75













Step Action

Required Documentation

Remarks / Subsequent Steps

8 Upgrade to SAP Project and Portfolio Management 6.1. For more information, see service.sap.com/

instguides .

An upgrade to SAP Project and Portfolio Management 6.1 is only required if you plan on running or enhancing business processes for which SAP Project and Portfolio Management 6.1 is required or optional. For more information, see Software Component Matrix [page 22].

26





3 SAP SNC on SAP HANA

SAP is enabling the existing functions of SAP enhancement package 4 for SAP SNC 7.0 to utilize the in-memory technology and enable better performing business applications. Thereby, business applications can manage large data volumes faster.

NoteTo use SAP SNC on an SAP HANA database, you must install SAP NetWeaver 7.5 as well as a different set of software component versions. For more information, see the Software Component Matrix [external document].

3.1 Introduction to Using SAP HANA

SAP enhancement package 4 for SAP Supply Network Collaboration 7.0 can run on an SAP HANA database either as a stand-alone system or as part of an SAP Supply Chain Management system landscape.

NoteThis section only provides information about the stand-alone deployment option of SAP SNC on SAP HANA. For information about SAP SNC on SAP HANA as part of an SAP Supply Chain Management system landscape, see the Master Guide for SAP enhancement package 4 for Supply Chain Management 7.0 on SAP Service

Marketplace at service.sap.com/instguides Installation & Upgrade Guides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 3 for SAP SCM Server 7.0Master Guide .

SAP HANA comprises the required hardware as well as the SAP HANA appliance software (SAP HANA database and data replication tools, for example). Note that the SAP HANA appliance software can only be installed by certified hardware partners on validated hardware running a specific operating system.

For more information, see SAP Note 1514967 and the SAP HANA Technical Operations Manual on the SAP Help

Portal at help.sap.com/hana_appliance , under System Administration and Maintenance Information SAP HANA Technical Operations Manual (TOM) .

Related Information

For more information about implementation topics not covered in this section, see the following content on SAP Service Marketplace:

Table 13


Information about SAP HANA service.sap.com/hana

help.sap.com/hana_appliance

Additional information about SAP HANA www.saphana.com/

SAP® Supply Network Collaboration (SAP SNC) 7.0 Including SAP Enhancement Package 4SAP SNC on SAP HANA





http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fhana_appliance

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fhana


http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.saphana.com%2F

Related Guides

You can find more information about the relevant applications in the following documents:

Table 14

Guide Location

SAP HANA Technical Operations Manual help.sap.com/hana_appliance , under System

Administration and Maintenance Information SAP HANA

Technical Operations Manual (TOM)

Guides for SAP HANA appliance software help.sap.com/hana_appliance

Upgrade Master Guide for SAP EHP 2 for SAP SNC 7.0 help.sap.com/snc704

Installation Guides for SAP EHP 4 for SAP SCM 7.0 service.sap.com/instguides Installation & Upgrade

Guides SAP Business Suite Applications SAP SCM SAP

SCM Server Using SAP enhancement package 4 for SAP

SCM Server 7.0 Installation Guides Installation Guides for

SAP EHP 4 for SAP SCM 7.0

Planning Guide for the SAP Business Suite service.sap.com/instguides Installation & Upgrade



SCM Server 7.0 Planning Guide

Upgrade and Update Guides for SAP EHP 4 for SAP SCM 7.0 service.sap.com/instguides Installation & Upgrade



SCM Server 7.0 Upgrade Guides Upgrade and Update

Guides for SAP EHP4 for SAP SCM 7.0

Upgrade Master Guide for SAP EHP 4 for SAP SCM 7.0 service.sap.com/instguides Installation & Upgrade



SCM Server 7.0 Upgrade Master Guide

Software Update Manager service.sap.com/sltoolset SL Toolset Software

Logistics Toolset 1.0

Software Provisioning Manager service.sap.com/sltoolset SL Toolset Software

Logistics Toolset 1.0

NoteThe guide describes the tool-specific steps that are necessary to perform an installation (including information on system copy and dual stack split). Note that the Software Provisioning Manager has replaced SAPinst as the installation tool.

28












Important SAP Notes

You must read the following SAP Notes before you start the implementation. These SAP Notes contain the most recent information on the implementation, as well as corrections to the implementation documentation.

Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP Service Marketplace

at service.sap.com/notes .

Table 15


1514967 SAP HANA: Central Note Central SAP Note about the SAP HANA appliance software and the SAP HANA database

1514966 SAP HANA 1.0: Sizing SAP In-Memory Database

Sizing information about the SAP HANA database

1826100 Multiple applications SAP Business Suite powered by SAP HANA

Support and special considerations for multiple applications on a single SAP HANA system within SAP Business Suite powered by SAP HANA.

1681092 Multiple SAP HANA databases on one appliance

Support and special considerations for multiple SAP HANA databases on a single SAP HANA appliance.

855534 Dual Stack and SAP Business Suite 7 Implementation of Dual Stack with SAP Business Suite 7

1686144 Dual-Stack Split 2.0 SP2 for Systems Based on SAP NetWeaver

Dual-Stack Split 2.0 SP2 for Systems Based on SAP

1655335 Use Cases for Splitting Dual-Stack Systems

Contains use Cases for splitting dual-stack systems

1785057 Recommendations for migrating Suite systems to SAP HANA

Contains recommendations for migrating suite systems to SAP HANA.

1794297 Secondary indexes for the Business Suite on HANA

Contains recommendations for migrating suite systems to SAP HANA.

1787787 IMS for Suite on HANA This SAP Note contains information about transparent tables after migration to SAP HANA.

1051576 Conversion of Single Code Page Systems to Unicode

This SAP Note contains information about conversion to Unicode (including references to additional notes describing the conversion to Unicode from ambiguous blended code page systems).

1718576 Migration from SAP HANA to another database system

This SAP Note contains information about available migration scenarios from SAP HANA to other databases.




http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fnotes














NoteThis SAP Note is relevant for SAP NetWeaver Business Warehouse only.

1309506 SPAM/SAINT with parallel R3trans This SAP Note provides information about applying add-ons and support packages.

1778621 Sequence problem in EDID4 after declustering

928729 Combined Upgrade & Unicode Conversion (CU &UC)

1695112 Activities in BW after migrating to the SAP HANA

1793153 Usage of cProjects / cFolders and Workforce Mgmt

1791482 Unique indexes display as non-unique indexes

1754729 SHBD: Consistency checking for distributed HANA systems

1756099 RSHDB: Consistency check for tables (7.30 SP9)

1827752 Planning Object Structure Persistence Changes on SAP HANA

Describes the reasons and background to POS persistence changes.

1818080 Planning Object Structure migration report: DSO persistence

This SAP Note contains information about the report Migrate Planning Object Structures to DataStore Object Persistence (/SCMB/PSTRU_MIGRATION_TO_DSO).

1810952 SAP HANA LCAPPS 1.00 release information

3.2 Technical System Landscape Using SAP HANA

Note● SAP enhancement package 4 for SAP SNC 7.0 does not contain any Java components.

● SAP HANA runs natively on Unicode only. If your system is not yet running on Unicode, consider doing the conversion separately before migrating to SAP HANA. The Unicode conversion could technically be done

30














during the database migration (that is, during the heterogeneous system copy), but preparatory steps are

required as described in SAP Note 1051576 .

The following figure shows the stand-alone deployment option for SAP SNC:

Figure 2: SAP SNC on SAP HANA

NoteFor information about deployment options of SAP enhancement package 4 for Supply Network Collaboration 7.0 as part of SAP Supply Chain Management, see the Master Guide for SAP enhancement package 4 for SAP

Supply Chain Management 7.0 on SAP Service Marketplace at service.sap.com/instguides Installation & Upgrade Guides SAP Business Suite Applications SAP SCM SAP SCM Server Using SAP enhancement package 4 for SAP SCM Server 7.0 Master Guide .

3.3 Update/Upgrade and Migration Process: Overview

NoteThis section contains information for the update/upgrade and migration process for the stand-alone deployment option of SAP enhancement package 4 for SAP Supply Network Collaboration 7.0. For more information about the update/upgrade and migration process of SAP enhancement package 4 for SAP Supply Network Collaboration 7.0 as part of Supply Chain Management, see the Installation Guide for your SAP SCM

version on SAP Service Marketplace at service.sap.com/instguides Installation & Upgrade Guides SAP Business Suite Applications SAP Business Suite Applications SAP SCM SAP SCM Server .

This section provides an overview of the update and upgrade process steps required to enable SAP enhancement package 4 for SAP SNC 7.0 to run on SAP HANA.







NoteNote the difference between installation, upgrade, and update, as explained in the following table:

Table 16

Term Definition

Installation New installation of SAP SNC 7.0 including SAP enhancement package 4

Update Installation of SAP enhancement package 4 on an existing SAP SNC 7.0 system

Upgrade Upgrade of an SAP SNC system lower than 7.0 to SAP SNC 7.0 including enhancement package 4

The update/upgrade process consists of the steps listed below, some of which may be optional, depending on your start release.

NoteBefore performing the steps below, consider making a homogeneous system copy to preserve your current status, so that you have a reference or fallback system in place. You can do the system copy before any of the steps below, depending on your requirements and scheduling. For information, see the following documentation:

● System copy of systems based on SAP NetWeaver 7.3 (or higher)

See the documentation for the Software Provisioning Manager at service.sap.com/sltoolset , under SL Toolset Software Logistics Toolset 1.0 .

● System copy of systems based on SAP NetWeaver releases lower than 7.3

See the SAP NetWeaver installation guides at service.sap.com/instguides , under Installation & Upgrade Guides SAP NetWeaver .

1. Upgrade or update to SAP SNC 7.0 including SAP enhancement package 4

NoteBefore performing the upgrade or update, check the release information note for SAP SNC 7.0 EHP4,

2242851 .

For the available technical usages, see the section Technical System Landscape in the section Using SAP HANA of this guide or the corresponding chapter in the Master Guide for SAP SCM 7.0 EHP 4.

For more information about SAP SNC-specific steps, see the Installation and Upgrade Information on SAP

Help Portal at help.sap.com/snc704 .

2. Perform a dual-stack split

As only ABAP components are enabled for SAP HANA, and dual-stack systems are not supported beyond

Business Suite i2011 (see SAP Note 1655335 ), you cannot deploy a dual-stack system (with both ABAP and Java components running in the same system). If your SAP SCM system is currently implemented as a dual-stack system, you have to perform a split.

For information on how to do a dual-stack split, see the following:

○ SAP Note 1686144

○ Tool guides at service.sap.com/sltoolset , under SL Toolset Software Logistics Toolset 1.0

3. Perform the migration to the SAP HANA database

32










1. Install SAP HANA

For more information, see SAP Note 1514967 and the SAP HANA Technical Operations Manual on the

SAP Help Portal at help.sap.com/hana_appliance , under System Administration and Maintenance Information SAP HANA Technical Operations Manual (TOM) .

2. Perform a heterogeneous system copy

To migrate your source database to the SAP HANA database, you perform a heterogeneous system copy.

NoteData Base Migration for SAP HANA Database

An existing SAP system is migrated to the SAP HANA database automatically using the Database Migration Option (DMO) of the Software Update Manager (SUM), which updates and migrates the

database in one step. For more information, see SAP Notes 1875197 and 1813548 , and SAP

Service Marketplace at service.sap.com/sltoolset under SL Toolset Software Logistics Toolset 1.0 . You need to use at least SPS 09 of the Software Update Manager 1.0.

NoteWhen planning your database migration, consider the following points:

○ The database migration to SAP HANA requires some preparation steps related to the database tables in your system. For example, you need to check the usage of cluster tables and pool tables, because they are automatically resolved to transparent tables during the database migration.

○ SAP HANA runs natively on Unicode only. If your system is not yet running on Unicode, consider doing the conversion separately before migrating to SAP HANA. The Unicode conversion could technically be done during the database migration (that is, during the heterogeneous system

copy), but preparatory steps are required as described in SAP Note 1051576 .

○ For more information about migration preparation, see SAP Note 1785057 .

NoteFor information about migration scenarios for SAP NetWeaver Business Warehouse from SAP HANA

to other databases, see SAP Note 1718576 .












4 Business Processes of SAP SNC

This section contains short process descriptions and information about the technical landscape of the business processes.

RecommendationProcess descriptions and configuration documentation are part of SAP Solution Manager implementation content ST-ICO 160 SP01.

4.1 Responsive Demand Planning

Description

You can use this business process to promote close collaboration with your business partners in a short-term planning horizon. During this process, all data received from your customer are validated and the short-term baseline and promotion demands are planned accordingly. Thus, a company can respond very quickly to changes in the Distribution Supply Chain.

Responsive Demand Planning contains the following building blocks:

Controlled Data Import

In the Data Import Controller, all incoming messages that are transferred from the customer to the vendor are validated and adjusted automatically or manually when appropriate. Where needed, this validation step checks and adjusts master data and transaction data before the system executes subsequent supply chain planning.

Responsive Forecasting

In Responsive Forecasting, the Vendor Managed Inventory (VMI) Analyst develops an unconstrained forecast of future demand. To develop the unconstrained forecast, a number of statistical forecasting and extrapolation techniques are applied to the historical sales data transmitted by the customer. The majority of the process flow steps in Responsive Forecasting is automated; user intervention is only required when exceptional situations occur. Responsive Forecasting filters these situations and presents them in the Alert Monitor for subsequent (manual) processing by the VMI Analyst.

In addition, the statistical baseline forecast can be compared with the baseline forecast sent in by the customer. Deviations are visualized and a tolerance dependent alerting is provided. For these exceptional situations a rule based consensus forecast is calculated with the option for an additional user interaction.

The goal of Responsive Forecasting is twofold: to capture the demand situation as accurately as possible, and to monitor short-term fluctuations in market demand closely, so that quick action can be taken, if necessary, to prevent stockouts.

Responsive Promotion Planning

You can use this building block of the Responsive Demand Planning process to:

● Plan the promotional uplift as accurately as possible

34


SAP® Supply Network Collaboration (SAP SNC) 7.0 Including SAP Enhancement Package 4Business Processes of SAP SNC

● Monitor – and if necessary respond quickly to – changes in promotional demand during the replenishment period, with the goal of preventing stockouts. This use is particularly important because promotion items experience a significantly higher stockout rate than baseline items.

● Model cannibalization and post-promotion effects

Promotion planning fulfills a number of requirements, including the following:

● Correction of historical sales data by removing effects that are related to promotions alone. By correcting historical sales data, Responsive Promotion Planning enables the calculation of accurate historical data that can be used, in turn, as a foundation for forecasting.

● Inclusion, in the forecast, of changes in demand that are related to promotions and events alone. By including these changes, Responsive Promotion Planning enables sufficient supply to be secured

● Rapid response to unforeseen changes thus ensuring that promotion quantities are appropriately adjusted, optimal supply fulfilled, and stockouts prevented.

Technical System Landscape

The following software units are either mandatory or optional, as indicated below, for the technical implementation of this process.

Table 17: Software Units with Enhancement Package 4 for SAP SNC 7.0

Component Mandatory Optional

SAP NetWeaver 7.5 X

SAP enhancement package 4 for SAP SCM 7.0

X

SAP ERP 6.0 One option required

SAP ERP 6.0 including enhancement package 6 or higher

SAP NetWeaver Process Integration (PI) 7.31 or higher

X


X

XI Content for SAP SNC 7.04 X

For more information about the installation of these components, see Technical Landscapes for SAP Supply Network Collaboration.

4.2 Responsive Replenishment Planning

Description

You can use this business process to plan responsive replenishment. Based on the results of the Responsive Demand Planning Process, Responsive Replenishment Planning plans the optimal shipments to the locations of a customer. During this process the netting takes place, then transport loads are created, and finally the orders are created. Promotion and baseline demands can be planned independently from another.

Responsive Replenishment Planning contains the following building blocks:




● Replenishment Planning (RP)

● Transport Load Building (TLB)

● Order Publication (OP)

Replenishment Planning

You can use Replenishment Planning to calculate the quantities that are delivered to a customer location, for example, a distribution center, to satisfy customer demand and to maintain the desired service level. Starting with the demand forecast that is generated upon completion of Responsive Forecasting, Replenishment Planning determines the optimal short-term to medium-term plan that is required to fulfill the estimated demand. This plan covers the quantities that must be transported from the vendor’s distribution center (or production plant) to the customer’s distribution center (or store).

Transport Load Building

You can use Transport Load Building to consolidate replenishment orders resulting from Replenishment Planning, and to create feasible transport units on the basis of business rules. These rules represent the constraints of the relevant means of transport, thereby remaining within the corresponding minimum and maximum capacities.

Order Publication

You can also use this business process to ensure that the Transport Load Builder (TLB) shipments – generated during Transport Load Building – are prepared for publication and then transferred to the vendor back-end system for subsequent sales orders and outbound delivery processing. During this processing, in the supplier back-end system, an availability check can be executed, which results in a committed quantity for a committed delivery date. Order Publication also ensures that vendor-generated orders – representing the purchase order acknowledgments – are transferred to the customer back-end system for subsequent purchase orders and inbound delivery processing. In order to keep the planning and execution systems in a consistent and synchronized state, changes to sales orders in the back-end system are communicated to the planning component.



Table 18: Software Units with SAP Enhancement Package for SAP SCM 7.0


SAP NetWeaver 7.5 X

SAP enhancement package 4 for SAP SCM 7.0

X




X


X

36






4.3 Purchase Order Processing

Description

You can use this business process to send out purchase orders (POs) to the supplier using the Web-based application SAP Supply Network Collaboration (SAP SNC). Purchase orders are typically generated as part of the customer’s MRP run or are manually created by the customer. With SAP SNC, customers and suppliers can collaborate not only on purchase order items and component information (in the case of a subcontracting purchase order), but also the customer batch number for the product at item level or for a product at component level can now be transmitted in the SAP SNC purchase order. This includes characteristic values for a classified batch-managed product as well as the product configuration at item level and component level.

The suppliers can view the purchase orders by status, enter free text notes, and also print or download. The supplier can enter confirmations or order responses indicating which date and quantity that can be committed to. At time of shipment, the supplier can create ASN messages as well, which together with the confirmations update the customer’s ERP/MRP system. Suppliers and customers can create quality notifications at any point of production or delivery to document problems or deviations from the expected product and to define a structured data flow between supplier and customer to communicate these quality issues.

The main business value is derived from the fact that the customer can communicate requirements accurately and in real-time, replacing older methods, such as phone, fax, or e-mail. Suppliers can find their requirements through a Web browser only and are proactively alerted to exception situations, such as a new or changed purchase order, on-screen or per e-mail. Suppliers can respond to the requirements quickly and accurately via confirmations and ASNs.

Optionally, customers can use supplier performance management to analyze the performance of their suppliers based on business data from purchase orders and ASNs. To use supplier performance management, you must activate the business function Supply Network Collaboration 2 (SCM_SNC_GEN_2). For more information about supplier performance management and its settings, see SAP Library for SAP Supply Network Collaboration on

SAP Help Portal at help.sap.com/snc704 . In SAP Library, choose SAP Supply Network Collaboration (SAP SNC) Cross-Application Functions Supplier Performance Management .



Table 19: Software Units with SAP Enhancement Package 4 for SAP SNC 7.0


SAP NetWeaver 7.5 X

SAP enhancement package 4 for SAP SNC 7.0

X






SAP ERP 6.0 One option required; limited functionality with SAP ERP 6.0



X


Required for supplier performance management



4.4 Supplier Managed Inventory (SMI) with Replenishment Order Processing

Description

You can use this business process to shift net replenishment planning and execution from the customer to the supplier. The supplier uses gross demand (dependent requirements) and stock balance to calculate a replenishment plan based on minimum-maximum inventory level logic, and subsequently converts the plan into replenishment orders (ROs) and ASNs at time of shipment. The replenishment orders and ASNs are sent back to the customer’s ERP system as an indication of a supplier commitment to deliver goods. Replenishment orders are optional in the SMI process. The replenishment plan can be converted directly into ASNs if needed.

The main business value is derived from the fact that the customer no longer has to perform the MRP net planning and replenishment activities for the purchased components or raw materials and the supplier can better utilize his own capacity by conducting both the planning and execution pieces of the replenishment process.

The end-to-end business process includes SAP ERP (Materials Management, MM) and SAP Supply Network Collaboration (SAP SNC), where the replenishment orders are exchanged via messages (using SAP NetWeaver Process Integration as the EAI tool), as such the replenishment order exists in both SAP ERP and SAP SNC. SAP SNC is the collaborative view of the replenishment order. A replenishment order in SAP SNC is the same thing as a purchase order (PO) in SAP ERP; or rather a purchase order is what is created in the customer’s SAP ERP system after the supplier user (in SAP SNC) sends the replenishment order to the customer’s SAP ERP system.

Alternatively, the end-to-end business process can start in Supply Network Planning (SNP) of SAP Advanced Planning and Optimization (SAP APO) in addition to SAP ERP (MM) and SAP SNC. The Supplier Managed Inventory (SMI) application of SAP SNC receives gross demand (dependent requirements) and stock balance from SAP APO (SNP). You can send supplier planned receipts to the SAP APO system if, for example, you want to run constrained Capable-to-Match (CTM) planning. Replenishment orders and ASNs are transmitted from SAP SNC to SAP ERP (MM) by means of XML messages using SAP NetWeaver Process Integration (SAP NetWeaver PI) as the EAI tool.



38





SAP NetWeaver 7.5 X


X




X


X



4.5 Delivery Control Monitor

Description

You can use this business process to shift net replenishment planning and execution from the customer to the supplier.

In this process, suppliers use stock balance updates and preset signal levels (reorder points) to understand when replenishment needs to take place. Replenishment is based on min/max inventory limits, and the Delivery Control Monitor (DCM) functionality calculates the suggested replenishment quantities using the maximum level as the upper limit. DCM is a one-screen environment where the supplier user has access to stock on hand, signal levels, min/max limits and in-transits as well as the calculated replenishment quantities. In addition, alerts are triggered and shown by dedicated colors on screen representing a breach of the signal level or the minimum stock level as examples, and the alerts can also be e-mailed to one or many recipients. From the DCM in the Replenishment Web UI in SAP SNC, the user can select the products that need replenishing and with one click convert the data into the ASN screen of SAP SNC. The system automatically loads data such as delivery date and quantity. ASNs are sent back to the customer’s ERP system as an indication of a supplier’s commitment to deliver goods. The customer’s SAP ERP system has a scheduling agreement set up acting as a blanket order for the ASNs and the physical goods receipts.

The advantages of this business process are that the customer no longer has to perform the MRP net planning and replenishment activities for the purchased components or raw materials, and the supplier can better utilize their own capacity by being able to manage the replenishment process.








SAP NetWeaver 7.5 X


X




X


X



4.6 Dynamic Replenishment

Description

You can use this business process to collaborate with your suppliers during planning. You compare customer and supplier planning data in a one-screen environment, where deviations between customer’s plan and supplier’s plan are shown as absolute numbers and percentages. There are also color-coded thresholds that visualize the deviations on screen. The customer’s SAP ERP system is used for extracting data like planned orders and purchase requisitions, which is shown as “customer plan” values in SAP Supply Network Collaboration (SAP SNC). The same is true for already created purchase orders (POs), which are shown as “customer order” values. The supplier can send in or enter the corresponding responses via the Web, for the “supplier plan” and “supplier order” values. This is a planning collaboration business process, not an execution process that includes creation of ASNs or orders, for example.

Alternatively, instead of receiving the demand forecast data from SAP ERP (Materials Management, MM), the Order Forecast Monitor (OFM) of SAP SNC can receive the demand forecast data from Supply Network Planning (SNP) in SAP Advanced Planning and Optimization (SAP APO). You can send supplier planned receipts to the SAP APO system if, for example, you want to run constrained Capable-to-Match (CTM) planning. Transaction data is exchanged between SAP APO and SAP SNC by means of XML messages using SAP NetWeaver Process Integration as the EAI tool.

The main business value is derived from the fact that both supplier and customer can get a mid- to long-term awareness of deviations in supply and demand, and take appropriate action early to avoid delayed shipments or over production situations.

Dynamic replenishment is a business process running on SAP SNC.

40







SAP NetWeaver 7.5 X


X

SAP ERP 6.0 One option required; limited functionality with SAP ERP 6.0



X


X



4.7 Invoice Processing

Description

You can use this business process to collaborate with your suppliers during invoice processing. Invoice processing allows the supplier to charge you (the customer) for goods or services that you have purchased. In this process, it is the supplier who initiates the invoicing process.

With this process, you can see what the supplier is charging for, and can compare this with your own records. The process then enables the correct release of payments for the goods or services that you have purchased from the supplier.





SAP NetWeaver 7.5 X


X








X


X



4.8 Self-Billing Invoice Processing

Description

As a customer, you can use this business process to create an invoice yourself for goods or services that you have purchased from a supplier. With this process, the responsibility for creating an invoice does not lie with the supplier; however the supplier is able to view invoices when you publish them. The supplier can also view the status of a payment run for an invoice. That is, when you have initiated and completed it.

When you purchase goods or services from a supplier, you can issue an invoice yourself, thus shortening the time of document creation. You can then initiate payment for that invoice.





SAP NetWeaver 7.5 X


X




X


X


42







5 Solution-Wide Topics

This section provides additional information about the most important software components of SAP Supply Network Collaboration (SAP SNC).

NoteOnly a subset of these components is required for the installation of a specific business scenario. For a scenario-specific overview of components, see the section Business Processes of SAP SNC [page 34].

5.1 SAP Solution Manager

SAP provides SAP Solution Manager as a highly recommended platform to efficiently support the implementation of your solution. Using SAP Solution Manager significantly accelerates the implementation process and helps you achieve your business goals. At the same time, SAP delivers Support Services based on the business scenarios designed and documented in SAP Solution Manager. Implementation content for your solution may further accelerate the implementation process. For information about availability of content specifically tailored to your

solution, see SAP Service Marketplace at service.sap.com/solutionmanager .

CautionIn the installation or upgrade process, an SAP Solution Manager system is required to generate the SAP Solution Manager Key. Without the SAP Solution Manager Key, you cannot continue the installation process. The generation of the required key is implemented into SAP Solution Manager as of Release 3.2 SP8. For more

information, see SAP Note 811923 .

5.2 Extended Implementation Content in SAP Solution Manager

In the business process repository of SAP Solution Manager, you can find high-quality business processes under Solutions/Applications Extended Implementation Content for Lines of Business . These business processes

are highly demanded by consultants and customers and provide optimized configuration information for various lines of business (for example, Finance, Sales, Manufacturing, and Supply Chain).

Extended implementation content for lines of business is characterized by carefully drafted configuration information, including the following:

● Configuration information is assigned to all business processes. This process-specific configuration information always contains a clear reference to additional basic configuration settings that are available for the required components of a process. Therefore, when you include a business process in a self-defined scenario, you can easily identify all relevant configuration settings that are relevant for your project.

44


SAP® Supply Network Collaboration (SAP SNC) 7.0 Including SAP Enhancement Package 4Solution-Wide Topics

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fsolutionmanager


● Configuration information that is specific for an optional process step is directly assigned to that process step. Therefore, when you remove an optional process step from your project because you do not need it, the corresponding configuration activities are also automatically excluded from your implementation project.

For your implementation project, this means:

● With the extended implementation content, the implementation of a business process is easier than before.

● You can adjust SAP business processes to your own enterprise-specific requirements.

● You can be sure to get all required configuration information if you include an SAP business process in a self-defined business scenario.

5.3 Service-Oriented Architecture (SOA)

SAP’s delivery on SOA (service-oriented architecture) differs from the pure architectural concept of SOA in the delivery of ready-to use enterprise services. Enterprise services are SAP-defined Web services which provide end-to-end business processes or individual business process steps that can be used to compose business scenarios while ensuring business integrity and ease of reuse. SAP designs and implements enterprise service interfaces to ensure semantic harmonization and business relevance. This section deals with the service-enablement of SAP Business Suite 7.

5.3.1 Service Enablement

The service enablement of SAP Business Suite consists of one or more of the following SAP components:

● SAP Business Suite 7

Enterprise services are an integral part of the software components of the SAP Business Suite applications. Enterprise services are the technical interfaces to the functionality available in the business application.

● SAP NetWeaver PI 7.0 or higher

SAP NetWeaver Process Integration (SAP NetWeaver PI) is an open integration and application platform that provides tools enabling you to set up a service-oriented architecture for business applications. You can use the platform for providing, discovering, and consuming services, integrating applications using the integration server, and managing business processes. Process integration is required in a runtime environment to consume enterprise services in a mediated scenario.

We recommend that you use the highest version of SAP NetWeaver Process Integration (PI). For more

information, see SAP Note 1515223 and SAP Note 1388258 .

NoteStarting with SAP NetWeaver Process Integration (PI) 7.3, SAP provides a new installation option Advanced Adapter Engine Extended (AEX). Since AEX is based on AS Java alone, it is easier to install and maintain as well as it needs less memory and data storage. Therefore, AEX is a cost-saving option compared to a full installation of SAP NetWeaver PI. For more information about the AEX, enter the phrase Advanced Adapter Engine Extended in the documentation of SAP NetWeaver Process Integration at

help.sap.com/nw73 and see SAP Note 1573180 .






http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fnw73


NoteAsynchronous services that are enabled for Web Services Reliable Messaging (WS-RM) can be called in a point-to-point communication scenario. Otherwise asynchronous services can only be consumed in a mediated scenario.

● Enterprise Services Repository

The Enterprise Services Repository (ES Repository) is the central repository that contains the definition of all enterprise services and models. The ES Repository is shipped with SAP NetWeaver PI and with SAP NetWeaver Composition Environment (CE) starting with SAP NetWeaver PI 7.1 and with SAP NetWeaver CE 7.1. The Enterprise Services Repository is a design time environment that enables you to create and enhance enterprise service definitions.

NoteIn a SAP NetWeaver 7.0x landscape you use the Integration Repository to create and enhance enterprise service definitions.

● Services Registry

The Services Registry is shipped with SAP NetWeaver PI and SAP NetWeaver CE starting with SAP NetWeaver PI 7.1 and SAP NetWeaver CE 7.1. The Service Registry is only required for the publication of enterprise service end-points (Web services) that have been configured and activated in the SAP Business Suite.

● SAP NetWeaver CE 7.1 or higher

The SAP NetWeaver Composition Environment (SAP NetWeaver CE) provides a robust environment for the design and implementation of composite applications.

The design time environment of SAP NetWeaver CE can be used for the model-driven design and development of composite applications based on enterprise services. SAP NetWeaver CE offers the tools and the environment necessary for running composite applications fast and efficiently in a runtime environment.

5.3.2 Installation of the Service-Oriented Architecture (SOA)

The installation of service interfaces, and therefore the service enablement of SAP Business Suite, consists of one or more of the following phases:

● Identification of software components and required business functions

You use the technical data section of the enterprise service documentation to identify the following data for each enterprise service:

○ the software component version with which the service was shipped

○ the business function(s) required to be activated

● Identification of technical usages (relevant for SAP ERP only)

SAP Note 1818596 provides a mapping of business functions and software component versions to technical usages. You use this documentation to identify the required technical usages for your list of software component versions and business functions.

● Installation of the software component ECC-SE (relevant for SAP ERP only)

The software component ECC-SE contains service implementations for ECC (the ERP Central Component). This component must be explicitly installed if you intend to use enterprise services for ECC functionality. In

46




this case you must also select the technical usage “ESA ECC-SE” during the enhancement package installation.

● Selection and installation together with the other parts of the enhancement package

In the enhancement package installation process you must select all the technical usages you have identified for service enablement together with the technical usages you identified for enhanced features in SAP Business Suite. The selected technical usages will install the corresponding software components that contain the enterprise services interfaces and implementations.

● Import of ESR Content (aka XI Content) (optional)

To install the content required for the enterprise service definitions you must select the technical usage “XI Content” in the enhancement package installation process. This downloads the content files for SAP NetWeaver PI 7.0 or higher. Unpack the ZIP file and copy the tpz files corresponding to your SAP NetWeaver PI version into the import directory of your Integration Repository (for SAP NetWeaver PI 7.0x) or Enterprise Services Repository (for SAP NetWeaver ES Repository 7.1 or higher). Use the import function to import the content files into the corresponding repository (Integration Repository or Enterprise Services Repository). (Choose Tools Import Design Objects )

● Services Registry (optional)

The services registry is shipped starting with SAP NetWeaver PI 7.1 and CE 7.1. You must configure the services registry and then publish the enterprise services from the Business Suite application to the registry using the transaction SOAMANAGER in the backend.

For further information regarding the SAP NetWeaver PI, CE and ES Repository, refer to the corresponding SAP NetWeaver Installation and Master Guides.

5.3.3 Related Documentation

For more information about the service-oriented architecture (SOA), see the following information sources:

● SCN Community in the SAP Network at scn.sap.com/community/soa (registration required)

● SAP Note 1359215 : Technical prerequisites for using enterprise services (relevant for ERP only)

● SAP note 838402 : Problems with non-Unicode system landscapes




http://help.sap.com/disclaimer?site=https%3A%2F%2Fscn.sap.com%2Fcommunity%2Fsoa



A Appendix

A.1 List of Documents

The following table lists all documents mentioned in this Upgrade Master Guide.

Table 25

Title Purpose Where to Find

Installation Guides

Installation Guide of SAP SCM Server 7.0 EHP4

Installing SAP SCM Server service.sap.com/instguides SAP Business Suite

Applications SAP SCM SAP SCM Server Using SAP

enhancement package 4 for SAP SCM Server 7.0

How to Install SAP Enhancement Package 4 for SAP SCM 7.0: A Practical Guide

A practical guide to help install the SAP enhancement package 4 for SAP SCM

service.sap.com/instguides SAP Business Suite

Solutions SAP SCM SAP SCM Server Using SAP SCM

7.04 Install

Installation Guides of SAP ERP 6.0

Installing the ERP Server service.sap.com/instguides SAP Business Suite

Solutions SAP ERP SAP ERP 6.0 Installation

Installation/Upgrade Note – SAP SNC 7.0 EHP4

Installing the SAP SNC Add-On

SAP Note 2242851

Installation Guide – SAP NetWeaver 7.5

Installing the PI Server service.sap.com/installnw75

Installation Guide – SAP Solution Manager

Installing Solution Manager service.sap.com/instguides SAP Components SAP

Solution Manager

Installation Note – CPRXRPM 610

Installing CPRXRPM 610 SAP Note 1821685

Installation/Upgrade Note – SAP EM 9.2

Installing SAP EM SAP Note 2050605

Installation Guide: SAP Enhancement Package Installation Using SAP Enhancement Package Installer (SAPehpi) 7.03

Installing enhancement packages


Troubleshooting and Administration for Installations Using SAPehpi (ABAP)

Troubleshooting and administration tips for the installation of enhancement packages


Master Guides

48


SAP® Supply Network Collaboration (SAP SNC) 7.0 Including SAP Enhancement Package 4Appendix





http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Finstallnw75






Title Purpose Where to Find

SAP SNC 7.0 including enhancement package 4 service.sap.com/instguides SAP Business Suite

Solutions SAP SCM SAP SNC

SAP ERP 6.0 service.sap.com/instguides SAP Business Suite

Solutions SAP ERP SAP ERP 6.0 Planning

SAP ERP 6.0 including enhancement package 8 service.sap.com/instguides SAP Business Suite

Solutions SAP ERP SAP ERP 6.0 SAP enhancement

packages for SAP ERP 6.0 SAP enhancement package 8 for

SAP ERP 6.0

SAP NetWeaver 7.5 service.sap.com/installnw75

A.2 Media List

NoteThe material numbers of the corresponding DVDs and CDs may change as new updates become necessary. Therefore, make sure you always use the most up-to-date version of the indicated data carrier(s).

Table 26: Media List

Material Number DVD / CD Label

Master Guide Installation – SAP SNC 7.0 EHP 4

Upgrade Master Guide Installation – SAP SNC 7.0 EHP 4

DVD SAP SNC 7.0 English and German Online Documentation

DVD SAP SNC 7.0 EHP 4 English and German Online Documentation

DVD SAP NetWeaver 7.5 including BI Content 7.40 Add-On 7.57

To install SAP Supply Network Collaboration and its necessary system landscapes, you also need the software DVDs for SAP NetWeaver and SAP ERP. Use your existing software DVDs or order them on SAP Service

Marketplace at service.sap.com/swdc .

A.3 Tools and Resources for Planning Your System Landscape

To plan your system landscape, you can use a few tools and resources that are available to you as SAP customer.







http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Finstallnw75

http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Fswdc

Tools

On SAP Service Marketplace, we provide the Business Process Repository (BPR) Viewer to look up descriptions of business scenarios and business processes.

In addition, there are tools in SAP Solution Manager that support you before, during, or after the installation of your SAP product or SAP enhancement package.

These tools include:

Table 27: Tools for Supporting Installations and Upgrades

Tool Purpose

Solution Manager System Landscape (transaction SMSY) To model and set up your system landscape

SAP Solution Manager Maintenance Optimizer (transaction DSWP)

To install support packages and SAP enhancement packages

Business Process Repository To access configuration documentation, links to Customizing activities and master data transactions, specifically tailored for individual business processes, business scenarios, or implementable steps

Business Process Change Analyzer (available with SAP enhancement package 1 for SAP Solution Manager 7.0)

To analyze the effects of transports and support packages as well as activation logs for business functions

NoteSAP recommends that you use SAP Solution Manager 7.1, SPS 10 or higher.

For more information, see SAP Support Portal at support.sap.com/solutionmanager .

SAP Solution Manager: Implementation Content

To get implementation content that supports you during the configuration of your business processes and business scenarios, you need the SAP Solution Manager add-on Implementation Content ST-ICO 150_700 (SP38).

Landscape Verification for SAP Solutions Manager

To verify and correct your system landscape SAP highly recommends that you use Landscape Verification 1.0 for SAP Solution Manager 7.0, which is an add-on to your SAP Solution Manager 7.0 system. This add-on allows you to identify and correct issues in your SAP Solution Manager landscape (transaction SMSY) before they cause problems, for example during a system update. Examples for errors are a missing connection to the System Landscape Directory or the wrong assignment of products to technical systems. For each type of error, a generic description for the solution is provided.

For more information about the landscape verification add-on, see SDN at www.sdn.sap.com/irj/sdn/alm?

rid=/webcontent/uuid/70fc3790-7ec9-2d10-57ad-95b2d0d1185d .

Planning Guide – SAP Business Suite Landscape Implementation

To get an overview of the necessary steps for planning a system landscape, use the Planning Guide - SAP Business

Suite Landscape Implementation on SAP Service Marketplace at service.sap.com/instguides under SAP Business Suite Applications . The guide also provides you with more information about the following:

● Examples of reference system landscapes

● Planning tools such as the business process repository

50



http://help.sap.com/disclaimer?site=http%3A%2F%2Fsupport.sap.com%2Fsolutionmanager




● Deployment options

● Typical implementation process

A.3.1 Business Process Repository (BPR) Viewer

The business process repository viewer (BPR viewer) is a tool on SAP Service Marketplace that allows you to preview the existing business scenarios, business processes that are shipped as part of SAP Solution Manager content. You can make use of the information in SAP Solution Manager during your implementation project by taking the pre-delivered implementation content as the starting point for your project scope. The implementation content is delivered with the following assigned information:

● Description of the business scenario, process, or implementable step

● Configuration content (Customizing activities or configuration documentation)

A.3.2 Using the BPR Viewer

Procedure

Calling Up the BPR Viewer

You can call up the BPR viewer directly using the Internet address implementationcontent.sap.com/bpr .

Working with the BPR Viewer

To call up information about business scenarios, business processes, or implementable steps, navigate the following paths in the BPR viewer:

Table 28

BPR Object Location

Business scenario Under Solutions/Applications

Business process Under Organizational Areas

Implementable step Under Solutions/Applications

For each business scenario, business process, or implementable step, you can select between different versions that depend on varying components and releases. To display the descriptions of a business scenario, business process, or implementable step, choose the Documentation tab page. To display configuration documentation, choose the Configuration tab page.

NoteThe BPR Viewer displays all descriptions, but only a selection of the configuration documentation. To view all configuration documentation, install and use SAP Solution Manager at your customer site.




http://help.sap.com/disclaimer?site=https%3A%2F%2Fimplementationcontent.sap.com%2Fbpr

B Reference

B.1 The Main SAP Documentation Types

The following is an overview of the most important documentation types that you need in the various phases in the life cycle of SAP software.

Cross-Phase Documentation

SAPterm is SAP’s terminology database. It contains SAP-specific vocabulary in over 30 labout anguages, as well as many glossary entries in English and German.

● Target group:

○ Relevant for all target groups

● Current version:

○ On SAP Help Portal at help.sap.com/glossary

○ In the SAP system in transaction STERMSAP Library is a collection of documentation for SAP software covering functions and processes.

● Target group:

○ Consultants

○ System administrators

○ Project teams for implementations or upgrades


○ On SAP Help Portal at help.sap.com (also available as documentation DVD)

The security guide describes the settings for a medium security level and offers suggestions for raising security levels. A collective security guide is available for SAP NetWeaver. This document contains general guidelines and suggestions. SAP applications have a security guide of their own.

● Target group:


○ Technology consultants

○ Solution consultants


○ On SAP Service Marketplace at service.sap.com/securityguide

Implementation

The master guide is the starting point for implementing an SAP solution. It lists the required installable units for each business or IT scenario. It provides scenario-specific descriptions of preparation, execution, and follow-up of an implementation. It also provides references to other documents, such as installation guides, the technical infrastructure guide and SAP Notes.

● Target group:


52


SAP® Supply Network Collaboration (SAP SNC) 7.0 Including SAP Enhancement Package 4Reference

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com%2Fglossary

http://help.sap.com/disclaimer?site=http%3A%2F%2Fhelp.sap.com


○ Project teams for implementations


○ On SAP Service Marketplace at service.sap.com/instguides

The installation guide describes the technical implementation of an installable unit, taking into account the combinations of operating systems and databases. It does not describe any business-related configuration.

● Target group:





Configuration Documentation in SAP Solution Manager—SAP Solution Manager is a life-cycle platform. One of its main functions is the configuration of business and IT scenarios. It contains IMG activities, transactions, and so on, as well as documentation.

● Target group:





○ In SAP Solution Manager

The Implementation Guide (IMG) is a tool for configuring a single SAP system. The IMG activities and their documentation are structured from a functional perspective. (In order to configure a whole system landscape from a process-oriented perspective, SAP Solution Manager, which refers to the relevant IMG activities in the individual SAP systems, is used.)

● Target group:


○ Project teams for implementations or upgrades


○ In the SAP menu of the SAP system under Tools Customizing IMG

Production Operation

The technical operations manual is the starting point for operating a system that runs on SAP NetWeaver, and precedes the solution operations guide. The manual refers users to the tools and documentation that are needed to carry out various tasks, such as monitoring, backup/ restore, master data maintenance, transports, and tests.

● Target group:




The solution operations guide is used for operating an SAP application once all tasks in the technical operations manual have been completed. It refers users to the tools and documentation that are needed to carry out the various operations-related tasks.

● Target group:












Upgrade

The upgrade master guide is the starting point for upgrading the business and IT scenarios of an SAP solution. It provides scenario-specific descriptions of preparation, execution, and follow-up of an upgrade. It also refers to other documents, such as the upgrade guides and SAP Notes.

● Target group:


○ Project teams for upgrades



The upgrade guide describes the technical upgrade of an installable unit, taking into account the combinations of operating systems and databases. It does not describe any business-related configuration.

● Target group:





Release notes are documents that contain short descriptions of new features or changes in SAP NetWeaver or an SAP application since the previous release. Release notes about ABAP developments enable the SAP system to generate delta and upgrade IMGs.

● Target group:

○ Consultants



○ On SAP Service Marketplace at service.sap.com/releasenotes

○ In the SAP menu of the SAP system under Help Release Notes (only ABAP developments)

54






http://help.sap.com/disclaimer?site=http%3A%2F%2Fservice.sap.com%2Freleasenotes

www.sap.com

Material Number: 50107447

*50107447*

http://www.sap.com