plant connectivity 15 - sap help portal · there is no separate upgrade master guide for plant...

Master GuideDocument version: 4.0 – 2016-11-04

Plant Connectivity 15.1

CUSTOMER

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

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

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.

2

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

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

Plant Connectivity 15.1Documentation 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

<Example> 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>”.

Example Example 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

www.sap.com Textual cross-references to an internet address

/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.

Plant Connectivity 15.1Typographic Conventions

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

4.0 2016-11-04 PCo 15.1 (SP03)

Plant Connectivity 15.1Document History




Content

1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 About this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2 Planning Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.3 Further Useful Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.4 Important SAP Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 Plant Connectivity Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.1 Software Component Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.2 System Landscape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.3 Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

3 Business Scenarios for Plant Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4 List of Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

A Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20A.1 The Main SAP Documentation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

6


Plant Connectivity 15.1Content

1 Getting Started

1.1 About this Document

You use the Master Guide to get an overview of Plant Connectivity (PCo), its software units, and its scenario, as seen from a technical perspective. The Master Guide is a planning tool that helps you design your PCo system landscape. It contains references to the further necessary documentation, mainly the following:

● Installation guides for individual software applications

● Upgrade information

● Important SAP Notes

● Configuration documentation

● Links to SAP Library and Service Marketplace documentation

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

NoteThere is no separate Upgrade Master Guide for Plant Connectivity. You can find all relevant upgrade information in this Master Guide.

The Master Guide consists of the following main sections:

● Getting Started

This section contains information about using this document and related information crucial to the installation.

● Plant Connectivity Overview

This section contains the following information:

○ A short introduction to PCo

○ The software component matrix that provides the information about which components are used in the business scenarios and whether the corresponding component is mandatory or optional

○ System landscape information

○ Upgrade information

● PCo Business Scenarios

This section contains an overview of the business scenarios and their implementation sequence.

● List of Documents

This section contains the list of documents related to PCo and its business scenario.

● The Main SAP Documentation Types

This section contains information about the documentation types for your SAP solution.

NoteYou can find the most current information about the technical implementation of PCo and the latest installation

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

Plant Connectivity 15.1Getting Started




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

1.2 Planning Information

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

Table 3

Content Location on SAP Service Marketplace

Latest versions of installation and upgrade guides service.sap.com/instguides under SAP Business Suite

Applications SAP Manufacturing Plant Connectivity

SAP Business Maps – information about solutions and business scenarios

service.sap.com/businessmaps under: Cross-Industry

Maps Manufacturing Manufacturing Visibility Shop

Floor Integration Plant Floor Connectors .

Product Availability Matrix (released platforms and technology-related topics, such as maintenance strategies and language support)

service.sap.com/pam

Network security service.sap.com/securityguide

Performance and sizing service.sap.com/sizing under Solution Lifecycle

Management Sizing Guidelines Solutions and

Platforms

1.3 Further Useful Links

The following table lists additional links on SAP Service Marketplace:

Table 4

Content Location on SAP Service Marketplace

Information about creating error messages service.sap.com/message

SAP Notes search service.sap.com/notes

SAP Software Distribution Center (software download and ordering of software, installation, support packs and patches)

service.sap.com/swdc

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

service.sap.com/rkt

8




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

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

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%2Fmessage

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

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

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

1.4 Important SAP Notes

The following table lists all SAP Notes that are relevant to Plant Connectivity.

Table 5

SAP Note Number Title Description

2166275 Release Installation Note for PCo 15.1 Service Pack 00

Up-to-date information about PCo 15.1 (SP00) installation







1973693 Migration of OPC UA source systems after upgrade to PCo 15.0 or a higher release.

After the upgrade to PCo 15.0 or a higher release the migration tool UAMigrationUtility is available. You can use the tool to migrate the OPC UA source systems so that the namespace URL is used for storing the node IDs of tags.









2 Plant Connectivity Overview

PCo provides connectivity services for the manufacturing industry, in particular unsolicited data notification services: In this way it enables the manufacturing integration between real-time manufacturing systems and SAP applications. PCo is a highly extensible infrastructure on which to build manufacturing applications.

Through SAP MII, PCo can query real-time, historical, and statistical data for agents that support such queries. PCo can write current and historical data for specific agents.

PCo can act as OPC UA client as well as OPC UA server to integrate into Industry 4.0 communication networks. With its ability to model operational sequences, PCo is able to orchestrate independent machine units on plant level. Especially when acting as server, PCo provides a modification- free extensibility. Customers and partners can enhance the functionality in a vertical direction by adding their own server methods to PCo without modification of the standard.

2.1 Software Component Matrix

This Master Guide provides just one way to implement each business scenario. They are described in greater detail below.

Table 6

Business Scenario Software units

Key: X = mandatory, (X) = optional

SAP SLD SAP MII PCo

Remote Monitoring (via Remote Client)

(X) - X

Retrieval of Tag Information from Shop Floor System

- X >= PCo 2.1

Event Notification to SAP MII - X X

Event Notification to SAP ME using Web Services

- (X) X

Event Notification using Web Services and ENP

- (X) >= PCo 2.3

Event Notification Writing to a SAP HANA Database

- - >= PCo 15.0

OPC UA Server Functionality - - >= PCo 15.1 (SP03)

Orchestration of Machine Units

- (X) >= PCo 15.1 (SP03)

10


Plant Connectivity 15.1Plant Connectivity Overview

2.2 System Landscape

In a typical scenario, you would have multiple PCo installations in your setup, which communicate with different data sources and destination systems and which could also communicate with each other. For example, in each plant you can set up an MII/ ME system which connects to multiple PCo instances, each on a separate Windows machine. Each MII/ ME system can be connected to a central ERP system for further processing of the data obtained, as shown in the following graphic.

Figure 1: Sample System Landscape

When you use a PCo Web service destination system, you can directly transfer data from the shop floor to a third-party system, such as an SAP ME system. In this case the destination system is a SAP ME system or another supplier of Web services.

2.3 Upgrade

You can upgrade from any Plant Connectivity (PCo) release to Release 15.1 with support package 03. All upgrade information for the installation can be found in the Plant Connectivity Installation Guide. There is no separate upgrade guide for Plant Connectivity.

Plant Connectivity 15.1Plant Connectivity Overview



3 Business Scenarios for Plant Connectivity

Among other things, Plant Connectivity supports the following business scenarios:

● Remote monitoring of multiple PCo instances via Remote Client

● Retrieval of tag information from shop floor system

● Event notification to SAP MII for further transaction processing

● Event notification using Web services

● Event notification using Web services and enhanced notification processing

● Event notification writing to a SAP HANA database

● Orchestration of independent machine units on shop floor level

Remote Monitoring

This scenario allows an administrator to monitor a large number of PCo installations remotely. The administrator can manually add PCo installations or use an SLD (system landscape directory) to select PCo installations. Once set up, the following steps can be carried out for each PCo installation:

● Monitoring of the overall status for the PCo installation

● Monitoring of the status of each agent instance in a PCo installation

● Starting/stopping an agent instance

● Retrieval of logs

● Retrieval of configuration files

The following table describes the overall installation sequence for PCo, with all available software units. For information about the software units to be installed, see the section above called Software Component Matrix.

Table 7

Step Action Remarks/Subsequent Steps

1 Install a NetWeaver system. See the installation guide for NetWeaver on SAP Service Marketplace at

service.sap.com/instguides SAP

NetWeaver .

Optional for the use of a System Landscape Directory (SLD)

2 Install the SLD package on the NetWeaver system. For more information, see

www.sdn.sap.com/irj/sdn/nw-sld .

Optional for the use of a System Landscape Directory (SLD)

3 Install PCo 15.1 (SP03) under

service.sap.com/instguides . Go to

SAP Business Suite Applications

SAP Manufacturing SAP Plant

Connectivity SAP Plant Connectivity

15.1 .

-

12


Plant Connectivity 15.1Business Scenarios for Plant Connectivity

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

http://help.sap.com/disclaimer?site=http%3A%2F%2Fwww.sdn.sap.com%2Firj%2Fsdn%2Fnw-sld


Retrieval of Tag Information from Shop Floor System

If you implement this scenario, you can get access from SAP MII to data from any shop floor system for which a PCo agent exists. This includes:

● Reading tag data

● Writing tag data

● Reading time series (historical data)

For the software units to be used, see the above section called Software Component Matrix.

The implementation sequence is as follows:

Table 8

Step Action Remarks/Subsequent Steps

1 Install SAP MII (any release).

See the installation guide for MII on the SAP Service Marketplace at:

service.sap.com/instguides under


SAP Manufacturing SAP Manufacturing Integration and

Intelligence .

If you use MII 12.2 or later, you can choose between two query types:

● UDC – in PCo: Servers tab, choose Server Type SAP MII Query Server (before 12.2); (supported for compatibility reasons only)

● PCo – in PCo: Servers tab, choose Server Type SAP MII Query Server (recommended)

2 Install PCo 15.1 (SP03).

The PCo Installation Guide can be found under service.sap.com/

instguides under SAP Business

Suite Applications SAP

Manufacturing SAP Plant


15.1

-

Event Notification to SAP MII

If you implement this scenario, you can establish notification processes that will send notification messages to SAP MII, based on events or predefined trigger conditions for SAP MII.

The events or trigger conditions depend on shop floor data (for example, when the temperature value of a sensor reaches a critical limit). The notification message can contain any shop floor data that is retrievable by PCo.


Table 9

Step Action Remarks / Subsequent Steps

1 Install SAP MII (any release).

See the MII installation guide on SAP Service Marketplace at:


SAP Business Suite Application

Manufacturing SAP Manufacturing

Integration and Intelligence .

-









2 Install PCo 15.1 (SP03)






15.1

-

Event Notification Using Web Services

If you implement this scenario, you can use PCo to transfer data directly from production to a third-party system, for example, to an SAP ME system. You can implement the notification process for this and subscribe to specific tags of the data source. When specific events occur, PCo sends notification messages to the destination system by means of a Web service call. If you want to connect SAP ME, for example, you must create a destination system of the type Web Service Destination in PCo. SAP ME provides its own Web services such as the Web service ProductionProcessingInClient.


Table 10


1 Install the Web service provider and configure the Web services. If SAP ME is the Web service provider, see the ME installation guide on SAP Service Marketplace at:


Business Suite Application SAP


Execution .

-







15.1

-

Event Notification Using Web Services and Enhanced Notification Processing

As of PCo 2.3, an interface is available for implementing enhanced notification processing (ENP). Enhanced notification processing (ENP) enables you to flexibly control and document the data flow in production in connection with various destination systems, for example, with Web services. In this way, you can connect a third-party system, such as SAP ME, to PCo and transfer data from machine level to the desired SAP ME activity using Web service calls. This makes it possible, for example, starting from PCo, to call a Web service provided by SAP

14








ME, evaluate the result of the call, and then, depending on the results of the Web service call, call an additional Web service or write data back to a source system.

SAP delivers the standard enhancement Destination System Calls with Response Processing for enhanced notification processing with which you can execute one or multiple destination system calls and with which you can write back the results of the calls to the data source of the agent instance or other agent instances. This covers the most common requirements in communication between data sources of production and business systems.

If you want to implement requirements that go beyond the function scope of the SAP standard enhancement, you can implement a customer-owned enhancement. PCo provides an interface for this purpose that you can implement. The notification enhancement is mapped in the form of a destination system so that the enhancement is called as part of a notification process.

Enhanced notification processing enables you to do the following:

● You can call one or more destination systems one after the other in any order. This might be, for example, a regular Web service or a RESTful Web service.

● You can call mass-enabled destination systems (Web services) for multiple object instances, for example, for multiple SFCs when connected to SAP ME.

● You can assign the output expressions of a notification to the parameters of a Web service statically or dynamically.

● You can perform a program-controlled evaluation of the results of a destination system call and react to the results accordingly.

● After a notification message is received, the destination system can send information to a specific agent and update, for example, a tag value in the source system.

● You can send data from the notification enhancement to a data stream or a data window in an SAP ESP project.

● You can send data to a destination system of the type ODBC destination.

For more information about Destination System Calls with Response Processing, see help.sap.com/pco( Application Help SAP Plant Connectivity Processes and Integration Scenarios with SAP PCo Integration w. Third-Party Systems Using Enhanced Notification Processing Destination System Calls with Response Processing ).


Table 11


1 Install the Web service provider and configure the Web services. If SAP ME is the Web service provider, see the ME installation guide on SAP Service Marketplace at:


Business Suite Application SAP


Execution .

-



-




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








15.1

3 Implement a customer-specific logic.

An implementation guide for the customer-specific logic is available at



SAP Manufacturing SAP Plant


15.1.

-

Event Notification Writing to a SAP HANA Database

SAP HANA databases allow you to efficiently analyze high volume time-series data, for example, measurement data from technical equipment. PCo 15.0 or higher offer several options to write notification data to a SAP HANA database. You can, for example, write notification data to an ODBC destination connected to a HANA database table.


Table 12


1 Install the SAP HANA database. For more information, see help.sap.com/saphelp_hana/sap_hana_studio_installation_update_g

uide_en.pdf and help.sap.com/hana/SAP_HANA_Client_Installation_Update

_Guide_en.pdf .

-

2 Establish the connection between the HANA database and the local computer as described in the PCo application help. For more information about setting up the connection, see

help.sap.com/pco Application

Help SAP Plant Connectivity

Configuration Elements in SAP PCo

Destination System ODBC

Destination ODBC Destination

System: Configuration Tab Setting Up the Connection to the SAP HANA

Database

-

16





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




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






3 Install PCo 15.1.






15.1

-

4 Create an ODBC Destination System.

(see help.sap.com/pco

( Application Help SAP Plant

Connectivity Configuration Elements

in SAP PCo Destination System

ODBC Destination )

-

Orchestration of Independent Machine Units on Shop Floor Level

Choreographies of machines and machine units had to be programmed inside the PLC or in the master computer in a classical environment. A change of a tag value (for example done by PCo) triggered a program inside a PLC which in turn steered the machines or machine units. PCo allows those sequences to be modeled outside of the PLC by configuration. Running PCo as an OPC UA server and using OPC UA destination systems enables communication through method calls between the machine units, based on the OPC UA protocol.

Table 13








15.1

-










2 Configure PCo OPC UA server and OPC UA destination systems.

For more information, see

help.sap.com/pco under

Application Help SAP Plant

Connectivity Processes and

Integration Scenarios with SAP PCo

PCo as OPC UA Server and




OPC UA Destination System .

-

3 Use the multiple call destination system to model operational sequences. As a sequence step you can include any destination system that is available in PCo.

For more information, see

help.sap.com/pco under




Multiple Call Destination SystemConfiguring a Multiple Call Destination

System .

-

18





4 List of Documents

The following table lists all documents relevant to this Master Guide.

Table 14

Title Location on SAP Service Marketplace

PCo Installation Guide (for installation and upgrade) service.sap.com/instguides SAP Business Suite

Applications SAP Manufacturing SAP Plant Connectivity SAP


PCo Security Guide service.sap.com/instguides SAP Business Suite



PCo Application Operations Guide service.sap.com/instguides SAP Business Suite



Performance and Sizing Guide service.sap.com/sizing under Sizing Guidelines Solutions

and Platforms

PCo Application Help help.sap.com Product Lifecycle Mgmt SAP Plant

Connectivity

Plant Connectivity 15.1List of Documents






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

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

A Reference

A.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 languages, 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:


20


Plant Connectivity 15.1Reference



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

○ 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 scenarios, business processes, and implementable steps. It contains Customizing activities, transactions, and so on, as well as documentation.

● Target group:





○ In SAP Solution Manager

The Implementation Guide (IMG) is a tool for configuring (Customizing) a single SAP system. The Customizing 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 Customizing 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 application operations guides of SAP Business Suite. 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 application 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 scenarios and processes 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 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 in a particular release or changes to existing features since the previous release. Release notes about ABAP developments are the technical prerequisite for generating delta and upgrade Customizing in the Implementation Guide (IMG).

● 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)

22






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

www.sap.com

http://www.sap.com