SAP PLM Master guide for 7.2

Master Guide SAP Product Lifecycle Management (SAP PLM) 7.02 Using SAP® ERP 6.0 (Including Enhancement Package 6) Target Audience ■ Consultants ■ Administrators ■ Others

Public Document version 1.05 – 12/16/2011

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 34 F +49/18 05/34 34 20 www.sap.com

© Copyright 2011 SAP AG. All rights reserved. Java is a registered trademark of Sun Microsystems, Inc No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG.

JavaScript is a registered trademark of Sun Microsystems, Inc., used

The information contained herein may be changed without prior

under license for technology invented and implemented by Netscape.

notice. SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, Some software products marketed by SAP AG and its distributors

ByDesign, SAP Business ByDesign, and other SAP products and

contain proprietary software components of other software vendors.

services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered

several other countries all over the world. All other product and

trademarks of Microsoft Corporation.

service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational

IBM, DB2, DB2 Universal Database, System i, System i5, System p,

purposes only. National product specifications may vary.

System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390,

These materials are subject to change without notice. These materials

OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM,

are provided by SAP AG and its affiliated companies ("SAP Group")

Power Architecture, POWER6+, POWER6, POWER5+, POWER5,

for informational purposes only, without representation or warranty of

POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System

any kind, and SAP Group shall not be liable for errors or omissions

Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks,

with respect to the materials. The only warranties for SAP Group

OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner,

products and services are those that are set forth in the express

WebSphere, Netfinity, Tivoli and Informix are trademarks or

warranty statements accompanying such products and services, if any.

registered trademarks of IBM Corporation.

Nothing herein should be construed as constituting an additional warranty.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Disclaimer Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either

Some components of this product are based on Java™. Any code

trademarks or registered trademarks of Adobe Systems Incorporated in

change in these components may cause unpredictable and severe

the United States and/or other countries.

malfunctions and is therefore expressively prohibited, as is any decompilation of these components.

Oracle is a registered trademark of Oracle Corporation. Any Java™ Source Code delivered with this product is only to be used UNIX, X/Open, OSF/1, and Motif are registered trademarks of the

by SAP’s Support Services and may not be modified or altered in any

Open Group.

way.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of

Documentation in the SAP Service Marketplace

Citrix Systems, Inc.

You can find this documentation at the following Internet address:

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

service.sap.com/instguides

.

Typographic Conventions Type Style Example Text

Represents Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options. Cross-references to other documentation

Example text

Emphasized words or phrases in body text, titles of graphics and tables

EXAMPLE TEXT

Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text

Icons

Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code as well as names of installation, upgrade and database tools.

Example text

Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.



Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

EXAMPLE TEXT

Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Icon

Meaning Caution Example Note Recommendation Syntax

Master Guide SAP Product Lifecycle Management

History of Changes The Master Guide is regularly updated in SAP Service Marketplace at http://service.sap.com/instguides. Make sure you have the latest version of the Master Guide by checking SAP Service Marketplace immediately before starting the installation. The following table provides an overview of the most important changes that were made in the latest versions. Master Guide Version

Important Changes

1.00 (November 21, 2008)

First version

1.01 (November 28, 2008)

Small addition regarding the role of EA_APPL and SAP APPL in the system landscape

1.02 (February 12, 2010)

From enhancement package 5, Business Context Viewer is no longer delivered with the PLM Web User Interface. Instead it is an independent component that can be integrated into the PLM Web User Interface and other applications once the associated business functions have been activated. Updated information about running PLM Web User Interface without SAP NetWeaver Portal or SAP NetWeaver Business Client Information about the following has also been added:

1.03 (March 28, 2011)



Enhancement packages



Enterprise services (SOA)



Value scenarios and implementable steps



Tools: Scenario component list, business process repository (BPR) viewer

Adding necessary Business Functions for EhP5 Adding license information for functions (chapter 2) Changing section about Business Processes (Chapter 3) Changing section about Implementation Steps in SAP Solution Manager (Chapter 7.1.2).

1.04 (November 8, 2011) 1.05 (December 16, 2011)

4

Informations about Engineering Desktop (EDESK) removed

June 2012

Master Guide SAP Product Lifecycle Management

Contents History of Changes ................................................................................ 4

1 Getting Started ..............................................................................6 1.1 About this Document ....................................................................... 6 1.2 Related Information ......................................................................... 7 1.2.1 Planning Information .......................................................................... 7 1.2.2 Further Useful Links ........................................................................... 7 1.2.3 Related Master Guides ........................................................................ 7

1.3 Important SAP Notes ....................................................................... 8

2 SAP Product Lifecycle Management: Overview .......................10 2.1 Enhancement Package Key Concept ........................................... 13 2.2 Key Facts about Enhancement Packages ................................... 14 2.3 Enhancement Package Implementation ...................................... 15 2.4 Integration of SAP BusinessObjects............................................ 17 2.5 Software Component Matrix ......................................................... 18 2.6 System Landscape......................................................................... 18 2.7 Overall Implementation Sequence ............................................... 21

3 Business Processes of PLM Web User Interface and BCV ......26 4 Solution-Wide Topics..................................................................27 4.1 Service-Orientated Architecture (SOA) ........................................ 27 4.2 Installation of the Service-Orientated Architecture (SOA) ......... 30 4.3 Related Documentation ................................................................. 31

5 References...................................................................................32 7 Appendix......................................................................................33 7.1 Tools and Resources for Planning Your System Landscape .... 33 7.2 Business Process Repository (BPR) Viewer ............................... 34 7.2.1 Using the BPR Viewer ....................................................................... 35 7.2.2 Scenario and Process Component List ........................................... 35

June 2012 5

1 Getting Started 1.1 About this Document

1 Getting Started 1.1 About this Document Purpose This Master Guide is the central starting point for the technical implementation of business processes for SAP Product Lifecycle Management 7.02 using SAP enhancement package 6 for SAP ERP 6.0. The following key areas are addressed in this document: 

Product Lifecycle Management Web User Interface (PLM-WUI)



PLM Web User Interface for Process Industries (Recipe Development in PLM Web UI (PLM-WUI-RCP))



Specification Management in PLM Web UI

This Master Guide is specifically designed for customers of SAP Product Lifecycle Management (SAP PLM). It is an addition to the Master Guide for SAP enhancement package 6 for SAP ERP 6.0, which you can find on SAP Service Marketplace at http://service.sap.com/instguides. For details see section 1.2.3 This Master Guide provides an overview of processes in SAP PLM and related software units from a technical perspective. You can use this guide as a planning tool to help you design your system landscape. It also refers you to the following detailed documentation:  Installation guides for single software units  SAP Notes  Configuration documentation  SAP Library documentation For a general overview of the available SAP documentation, see The Main SAP Documentation Types later in this guide. The Master Guide consists of the following main sections:  SAP Product Lifecycle Management: Overview This section provides you with an overview of the software components in PLM, covering cross, discrete, and process industries. It also gives an overview of possible system landscapes, and where to find more information about installation procedures.  Business Processes of PLM Web User Interface This section provides you with a short overview of business processes for PLM Web User Interface and how the business process for Business Context Viewer (BCV) can be integrated in the PLM Web User Interface. You can find the most current information about the technical implementation of PLM Web User Interface, BCV, and of SAP ERP as well as the latest installation and configuration guides on SAP Service Marketplace at http://service.sap.com/instguides. We strongly recommend that you use the documents available here. The guides are regularly updated.

Constraints This Master Guide primarily discusses the overall technical implementation of PLM Web User Interface, rather than its subordinate components. This means that additional software dependencies might exist without being mentioned explicitly in this document. You can find more information on component-specific software dependencies in the corresponding installation guides.

6

June 2012

1 Getting Started 1.2 Related Information

1.2 Related Information 1.2.1 Planning Information For more information about planning topics not covered in this guide, see the following content on SAP Service Marketplace: Content

Location on SAP Service Marketplace

Latest versions of installation and upgrade guides

http://service.sap.com/instguides

SAP Business Maps - information about applications and business scenarios

http://service.sap.com/businessmap s

Network Security

http://service.sap.com/securitygui de

1.2.2 Further Useful Links The following table lists further useful links on SAP Service Marketplace: Content

Location on SAP Service Marketplace

Information about creating error messages

http://service.sap.com/message

SAP Notes search

http://service.sap.com/notes

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

http://service.sap.com/swdc

1.2.3 Related Master Guides The following table lists related master guides: Title

Location

Master Guide – SAP enhancement package 6 for SAP ERP 6.0

http://service.sap.com/instguides  SAP Business Suite Applications  SAP ERP  SAP ERP 6.0  SAP enhancement packages for SAP ERP 6.0  SAP enhancement package 6 for SAP ERP 6.0

Master Guide - SAP enhancement package 5 for SAP ERP 6.0

http://service.sap.com/instguides  SAP Business Suite Applications  SAP ERP  SAP ERP 6.0  SAP enhancement packages for SAP ERP 6.0  SAP enhancement package 5 for SAP ERP 6.0

Master Guide - SAP enhancement package 4 for SAP ERP 6.0

http://service.sap.com/instguides  SAP Business Suite Applications  SAP ERP  SAP ERP 6.0  SAP enhancement packages for SAP ERP 6.0  SAP enhancement package 4 for SAP ERP 6.0

Master Guide - SAP Product Lifecycle Management (PLM) 7.0

http://service.sap.com/instguides  SAP PLM  using SAP enhancement package 4 for SAP ERP 6.0  Master Guide for SAP PLM 7.0

June 2012 7

1 Getting Started

Master Guide for SAP for Automotive

http://service.sap.com/instguides  Industry Solutions  Industry Solution Guides  SAP for Automotive

1.3 Important SAP Notes You must read the following SAP Notes before you start the installation. These SAP Notes contain the most recent information on the installation, as well as corrections to the installation documentation. Make sure that you have the up-to-date version of each SAP Note, which you can find on SAP Service Marketplace at http://service.sap.com/notes. SAP Note Number

Title

Comment

1258912

PLM Core 7.00 Release Notes and Information

Provides information about installing PLM Core 7.00 and importing related support packages

945986

Report PPE_PREL_FILL_APPLOBJ_TYPE deletes relationships

Only relevant for customers upgrading iPPE from DI 4.6C2

914554

EA-IPPE: Release or upgrade strategy

Provides information for planning the installation and upgrade of add-on EA-IPPE

1003900

TREX 7.1: Central note

Central note for SAP NetWeaver TREX 7.0

1164979

SAP NetWeaver 7.0 Embedded Search: Central Note

Info on Embedded Search for 7.0 release

1249465

TREX 7.1: Installing TREX for Embedded Search

Info on Embedded Search for 7.1 release

1249482

Functional corrections for Enterprise Search 7.01 SP03

Details on program errors

1319472

Installation Note for Viewer in SAP ERP 6.0 EHP5

824757

Dependencies between SAP ERP component lists

1178747

ACF-WDABAP: Java version for ACFExecute, ACFUpDown

Information about the relevant Java versions for document upload and download

1380566

Enabling WC/CC via PFCG role

Information about accessing the work center/control center without the portal installation of portal is no longer required

8

June 2012

1 Getting Started 1.3 Important SAP Notes

1413474

Settings with DMZ systems for the PLM Web UI

Describes the required data for the separate DMZ system

1429942

ICF Service Activation for PLM Web UI

Information about activating the Internet Communication Framework (ICF) service manually after installation

900000

NetWeaver Business Client FAQ

Information about the different NWBC versions

1296463

Main Browser Note for NW 7.0

Lists the main sources for browser support

976714

Activating ACF tracing in the client

Provides information about client traces for troubleshooting for network (JNet), gantt (JGantt) or office integration with StarOffice

1150277

Prerequisites for using ACF

Prodives details on how to display the SAP Active Component Framework (ACF) base control correctly in Internet Explorer

766191

Active Component Framework Installation

Information on how to install the front-end elements of ACF

960996

Web Dynpro Applets: Requirements for NW 7.0 and higher

Explains that limitations for Mac Operating System support.

1406768

ACF - Java Runtime settings

1419452

Content servers in the PLM DMZ Scenario

1319289

PLM 7.01 Release Notes and Information

1511580

Migration Recipe Management to Recipe Development

Explains how to install a patch if the ACF applet is not executed or does not respond correctly.

Information and references to other notes about installing PLM 7.01 and importing PLM 7.01 Support Packages. You use Recipe Management and want to migrate the data of the existing recipe and independent formulas to Recipe Development.

June 2012 9

2 SAP Product Lifecycle Management: Overview 1.3 Important SAP Notes

2 SAP Product Lifecycle Management: Overview SAP ERP 6.0 includes the following software functions for Product Lifecycle Management (PLM). They are grouped logically by the area they relate to – PLM Core, Discrete, and Process. Additional functions that do not belong in these areas are also described. Some functions require a specific license for activation.

Cross-Industry and PLM Core 

Access Control Management You can use access control management (ACM) to administer access authorizations granted by access control contexts (ACCs) and access control lists (ACLs). ACCs ensure that PLM business objects, for example material, material BOM, document, recipes can only be accessed by users with the appropriate context roles. ACLs further determine a user’s access authorization by restricting or expanding the activities that can be carried out for a specific business object. Usage of this functionality requires a specific license.



Document Management SAP Document Management allows you to manage documents and coordinate document processing. You can automate the entire lifecycle of a document from creation to storage and access them immediately both in your SAP systems and external systems. In addition you can do redlining on products for collaborative tasks.



SAP Easy Document Management SAP Easy Document Management allows you to use its extensive features without having detailed knowledge of document management. It is integrated with Microsoft Windows Explorer making it easy to navigate and offers the following features: o Create public and private folders o Set up hierarchical structures o Check documents in and out from Microsoft applications, such as Word and Excel, using the “save as” function o Access SAP Product Lifecycle Management from SAP Easy Document Management to create, edit, and delete The benefits of SAP Easy Document Management include the following: o Link document management with computer-aided development and production systems to prevent redundant data retention, inconsistencies, and reduce the effort needed for keeping data up-to-date. o Adhere to quality management standards - new and strict product liability laws also make it increasingly important to archive documents during the life cycle of a product. Making a quality product demands more than just the product itself, it also requires a corresponding manufacturing process and organizational environment. A company that supports certifiable quality management (such as the ISO 9000to 9006 series of standards) cannot fulfill the high quality requirements without a document management system. SAP Easy Document Management manages and coordinates these complex requirements. You can automate the complete life cycle of a document - from

10

June 2012

2 SAP Product Lifecycle Management: Overview 1.3 Important SAP Notes

creation to successful check in, from access to update and you can access every document from every work center in a network. 

Classification With classification, you can use characteristics to describe all types of objects and to group similar objects into classes. This makes it easy to search for and find your objects.



Bill of Materials (BOMs) BOMs are used to formally list all the components that make up a product or assembly. This list contains important basic data for numerous areas of a company, for example, material provisions for production, and plant maintenance.



Engineering Change Management You can use engineering change management to change various objects, for example bill of materials (BOMs), materials or documents, depending on the history or specific parameters.



Engineering Record An engineering record is an object that controls the planning and execution of changes. It contains a collection of objects that collectively belong to a workflow, which is controlled by the engineering change process. The functionality of engineering change management is used in this process. Usage of this functionality requires a specific license.



Viewer Product visualization is an integral component in modern business software solutions. The viewer provided by SAP, which is fully integrated with the PLM Web User Interface, renders 2D and 3D graphic files as a means to visualize product data and collaborate. Additional business processes like Redlining and Digital Mockup can also be used. Business benefits include seamless exchange, publishing, and collaboration of engineering documents across extended enterprise, leading to improved product design quality.

Discrete 

Product Structure Management Digital mockup viewing is possible in product structure management.



Variant Configuration This is used for manufacturing complex products. Often a manufacturer is required to offer variants of its products. New variants are created by modifying existing product designs as the order is processed. This allows the manufacturer to react quickly to customers' requirements. The variants of a product are covered in the system with one (configuration) model. There are several scenarios available to support the customers’ business needs, for example, Engineer to Order, Configure to Order, and Assemble to Order.

June 2012 11

2 SAP Product Lifecycle Management: Overview 1.3 Important SAP Notes

Process 

Recipe Development This allows you to create and manage the master data for process manufacturing. The recipe is used to describe the manufacturing of products or the execution of a process. Recipes comprise information about the products and components of a process, the process steps to be executed, and the resources required for the production.



Specification Management Specifications are used to capture all the technical information about materials or subcomponents of materials that are used in the development and manufacturing of a product. They are used within the formula of a recipe to describe all input materials used to generate a given output and to describe the output itself.



Product Labeling in SAP PLM Recipe Development Product Labeling manipulates data to be printed on final packaging. The process allows the user to define, maintain and finalize information for different parts of a final product label which is represented as a single Label Set object.



Compliance Check The compliance check functionality in Recipe Management is used to ensure that new or modified product formulations are in compliance with rules imposed by government regulations as well as other external and internal constraints. These can be legal constraints or constraints laid down by an enterprise or a customer, for example.

Additional Software Components Handover to Manufacturing 

Guided Structure Synchronization This allows you to handover engineering product structures to manufacturing BOMs and keeps them up-to-date. Usage of this functionality requires a specific license.

Project Management 

Project System Project system allows you to closely monitor all technical and commercial aspects of projects across departments in your company.

Foundation 

Business Context Viewer (BCV) BCV is optionally available to integrate with the PLM Web User Interface and other applications where required. To use BCV, you must activate the /PLMU/PI_BCV and /BCV/MAIN business functions. Usage of this functionality requires a specific license. BCV provides analytical functions in a side panel, which allows you to see additional information related to a PLM business object. For more information about the configuration of BCV, see the following:

12

June 2012

2 SAP Product Lifecycle Management: Overview 2.1 Enhancement Package Key Concept 

Customizing for Business Context Viewer under Cross-Application Components  Processes and Tools for Enterprise Applications.



SAP Help Portal at http://help.sap.com/erp . In SAP Library choose SAP ERP Central Component  SAP ERP Enhancement Packages  ERP Central Component Enhancement Package 5  Processes and Tools for Enterprise Applications (CA-EPT)  Business Context Viewer  Configuration Center  Configuration of Business Context Viewer (BCV).

2.1 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



New installation of an SAP system including an enhancement package



Upgrade of an SAP system including an enhancement package

The installation process of enhancement packages consists of two different steps: 

Technical installation of the selected parts of an enhancement package



Activation of new 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. 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.

You cannot reverse a business function once it is activated. After you have activated a business function, you can see the changes and new developments in the SAP system, for example: 

Menu entries

June 2012 13

2 SAP Product Lifecycle Management: Overview 2.2 Key Facts about Enhancement Packages 

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. Test 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. You must install 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. If the SAP system is on a lower Support Package stack level, all relevant Support Package stacks are automatically included into the download queue, as well as the latest available Support Packages for the enhancement package.

Tools The enhancement package installation requires the following tools: 

SAP Solution Manager Maintenance Optimizer



Installation or upgrade tools (depending on your scenario)

The SAP Solution Manager Maintenance Optimizer (accessible from the Change Management work center) 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 as well as for the upgrade of an SAP system to a higher release including an enhancement package, you use the standard installation and upgrade tools (SAPinst, SAPup and SAPJup). To install an enhancement package on an existing SAP system, you use the SAP Enhancement Package Installer (SAPehpi). It allows enhancement packages to be installed with reduced downtime. SAPehpi uses the shadow system installation strategy, a well-known feature in the upgrade technology.

2.2 Key Facts about Enhancement Packages The following list summarizes important facts about the enhancement package concept and recommended approaches: 

14

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

June 2012

2 SAP Product Lifecycle Management: Overview 2.3 Enhancement Package Implementation 

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.



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 business functions and extension sets is irreversible. 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.3 Enhancement Package Implementation In the following, you will find an overview of the steps involved in the three different enhancement package implementation scenarios.

Enhancement Package Installation in an Existing SAP System Process 1. 2. 3. 4. 5. 6. 7. 8. 9. 10.

You find out, which of the new functions are interesting for your business. You analyze the landscape dependencies. You identify the relevant installable parts of the enhancement package. You make sure that you have set up your SAP Solution Manager system for the download of packages, and that you have configured the Maintenance Optimizer. You download the installation queue. You perform the installation. You analyze the impact of the business function activation with the dependency analyzer and the impact analyzer (transaction SWF5). You activate the business functions. You perform additional Customizing, if necessary. You test the new functions.

Tools  

SAP Solution Manager Maintenance Optimizer (mandatory) SAP Enhancement Package Installer (SAPehpi)

June 2012 15

2 SAP Product Lifecycle Management: Overview 2.3 Enhancement Package Implementation 

Switch framework with Dependency Analyzer and Impact Analyzer in SAP Solution Manager (transaction SWF5)

New Installation of an SAP System with Enhancement Packages Process 1. You install the SAP system. The installation of SAP ERP 6.0 including enhancement package 5 comprises the technical usage “Central Applications”. You can either use this system as it is or install further technical usages. 2. If you want to install further technical usages: 1. You identify the relevant installable parts of the enhancement package. 2. You make sure that you have set up your SAP Solution Manager system for the download of packages, and that you have configured the Maintenance Optimizer. 3. You download the installation queue. 4. You perform the installation. 5. You activate the business function using the switch framework (transaction SWF5). 3. You perform the Customizing for the SAP system. 4. You test the SAP system.

Tools   

Standard installation tool (SAPinst) SAPehpi or SAINT to install additional technical usages Switch framework with Dependency Analyzer and Impact Analyzer in SAP Solution Manager (transaction SWF5)

Upgrade to an SAP System Including an Enhancement Package Installation Customers who are upgrading from a lower release to an SAP system for which enhancement packages are available can include parts of enhancement packages into the upgrade process. SAP has enhanced the following tools:  

SAP Solution Manager Maintenance Optimizer Standard upgrade tool

In phase EHP_Inclusion of the upgrade, a dialog screen appears and asks if you want to include parts of an enhancement package into the upgrade process. Caution The use of SAP Solution Manager Maintenance Optimizer is mandatory if you want to include enhancement packages in your release upgrade.

16

June 2012

2 SAP Product Lifecycle Management: Overview

Process 1. You plan the upgrade to the new release. Decide which parts of the enhancement package you want to include into the upgrade procedure before you start with the upgrade. 2. You identify the relevant installable parts of the enhancement package. 3. You make sure that you have set up your SAP Solution Manager system for the download of packages, and that you have configured the Maintenance Optimizer. 4. You download the required parts of enhancement packages and Support Packages as well as the enhancement package stack configuration file. 5. You perform the upgrade including parts of the enhancement package. In phase EHP_Inclusion of the upgrade, a dialog screen appears and asks if you want to include parts of an enhancement package into the upgrade process. 6. You activate the business functions using the switch framework (transaction SWF5). 7. You perform the delta Customizing for the SAP system. 8. You use the test SAP system.

Tools  

Standard upgrade tools (SAPup and SAPJup) SAP Solution Manager Maintenance Optimizer

2.4 Integration of SAP BusinessObjects The integration of SAP BusinessObjects Crystal Reports and SAP BusinessObjects Xcelsius in SAP Business Suite provides you with analysis functions that are integrated in the user interface and processes: Embedded Analytics. Predefined reports and dashboards provide a detailed, graphical, or interactive display of (transaction) data from SAP Business Suite or from SAP NetWeaver BW.

Embedded Analytics contain the following integrations: 

Crystal Reports as an alternative for displaying simple lists in SAP GUI ALV Grid, Web Dynpro ABAP ALV, and POWER list (not in SAP CRM)



Crystal Reports for the formatted display of data from queries (You must install SAP BusinessObjects Enterprise Server.)



Xcelsius for the graphical or interactive display of data from queries in dashboards

Users can call these functions in SAP NetWeaver Business Client, SAP NetWeaver Portal, or SAP CRM. For more information about the different topics, see the information sources in the following table. Topic

Information Source

General Information

SAP Service Marketplace at http://service.sap.com/instguides SAP Business Suite Applications

Installation Information

under

SAP Service Marketplace at

June 2012 17

2 SAP Product Lifecycle Management: Overview 2.5 Software Component Matrix

http://service.sap.com/bosap-instguides and SAP Library under SAP BusinessObjects All Products Configuration Information

SAP Solution Manager under Solutions/Applications Basic Configuration

Installation Instructions

SAP Notes 1353044 and 1345320

2.5 Software Component Matrix This Master Guide provides just an overview of the system landscape for PLM Web User Interface. For more information about the required software components for PLM processes, see the scenario and process component lists on SAP Service Marketplace at http://service.sap.com/scl. For more information on the configuration of SAP PLM Web UI see Solution Manager for SAP PLM Web UI.

2.6 System Landscape Minimum System Landscape: PLM Web User Interface PLM Web User Interface needs the following minimum system landscape:

Intranet TREX Server

PLM Core PLMWUI EA-APPL

SAP_APPL EA-IPPE SAP_BS_FND SAP_ABA

SAP NetWeaver Enterprise Portal

SAP NetWeaver 7.1

Internal user

SAP_BASIS

18

June 2012

2 SAP Product Lifecycle Management: Overview 2.6 System Landscape

We 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. The system landscape includes the following software component versions as a minimum. These software components are included in SAP ERP 6.0, including SAP enhancement package 6, with support package 01. This installation also includes SAP NetWeaver 7.02 enhancement package 02, with support package 01.  EA-IPPE 406 EA-IPPE 406 functions are available with the installation of SAP enhancement package 6 for SAP ERP 6.0 and with the activation of the /PLMU/IPPE_INT_3 business function.  PLM-WUI 702 PLM-WUI 702 functions are available with the installation of SAP enhancement package 6 for SAP ERP 6.0 and with the activation of the /PLMU/WEB_UI_3 business function.



To use the Business Context Viewer (BCV), you must activate the following business functions: PLMU/PI_BCV (PLM, Product Intelligence with Business Context Viewer, /BCV/MAIN (FND, Business Context Viewer Main Application). SAP APPL 606 and EA_APPL 606 Some of the PLM processes require SAP APPL 606 and EA_APPL 606. Other processes still run with SAP APPL 600 and EA_APPL 600. For more information about which software components are required for individual processes, see the scenario and process component list on SAP Service Marketplace at http://service.sap.com/scl.

 



SAP BS_FOUNDATION 731 SAP NetWeaver Enterprise Portal Installation of the portal is optional from enhancement package 4, support package 05. For more information see SAP Note 1380566 in section 1.3. SAP NetWeaver 7.1 TREX server You need to install a TREX server to run SAP NetWeaver Enterprise Search with BCV. For more information, see SAP Note 1249465. Note that, if you also use the ERecruiting business scenario in SAP ERP, running only one TREX is not possible. For more information, see SAP Note 824757.

System Landscape with Demilitarized Zone In the standard scenarios, you use PLM Web User Interface in your own intranet. Internal users only need an installed Web browser to access PLM Web User Interface functions. For processes running with PLM Web User Interface, the following system landscape is also possible. If you also want to grant access to external users because you cooperate with business partners, you need an additional installation of SAP ERP 6.0 with enhancement package 6 and with PLM activated in a demilitarized zone (DMZ). External users only need a Web browser.

June 2012 19

2 SAP Product Lifecycle Management: Overview 2.6 System Landscape

PLM System Setup Internet

DMZ

Intranet hidden

public http:

http: Web Dispatcher https:

https:

ERP & PLM-Core

SAP PLMWUI

Access Control Authorization

(Empty ERP)

External user

SAP PLMWUI Internal user

(only Web Browser required)

DB

SAP CS’

TREX

ODBC

SAP CS

Max DB

DMZ Scenario

1-System-Scenario

The system in the DMZ does not require any master and transaction data or any comprehensive configuration. It is solely used for accessing the PLM Web UI. Master and transaction data are stored in the PLM system in the intranet. Access to the PLM Web User Interface in the DMZ is controlled by an authorization framework for PLM Web User Interface. For more information about setting up the system landscape, see the configuration documentation for PLM processes and scenarios in SAP Solution Manager. For more information about the authorization concept, see the PLM chapters in the SAP ERP security guide on SAP Service Marketplace at http://service.sap.com/securityguide SAP Security Guides  SAP ERP 2005 Security Guides.

20

June 2012

2 SAP Product Lifecycle Management: Overview 2.7 Overall Implementation Sequence

System Landscape: PLM Web User Interface with Optional Components In the following, you can see an example system landscape for PLM Web User Interface with all possible optional components:

BI Server SAP NetWeaver 7.01 Business Intelligence (BI) Conversion Server (Customer or partner software) SAP Plug-In

PLM Web User Interface

Intranet

SAP ERP 6.0 EHP 6 SAP NetWeaver 7.02 KPro

Internal user

TREX Server cProjects Server SAP cProjects Suite 4.5

SAP NetWeaver 7.1

Uses Web browser, and optional installations: NW Business Client, viewers, SAP Easy Doc. Mgmt, CAD

For more information about installing these optional components, see the Overall Implementation Sequence chapter below.

2.7 Overall Implementation Sequence Purpose The following table describes the overall installation sequence for PLM Web User Interface. This table contains all available software units. However, to implement 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 implement a specific scenario, see the scenario and process component lists on SAP Service Marketplace at http://service.sap.com/scl. For the latest component version and patch level requirements, see SAP Service Marketplace at http://service.sap.com/sp-stacks. For documentation listed in the following table, see References.

Process June 2012 21

2 SAP Product Lifecycle Management: Overview 2.7 Overall Implementation Sequence Implementation Sequence: Minimum System Landscape Step

Action [Required Documentation]

Remarks/Subsequent Steps

1

Installation of SAP ERP 6.0 with enhancement package 6. [Installation guide for SAP ERP 6.0 Enhancement Package 5.]

Note that you also need to install the Java stack of SAP NetWeaver if you want to use printing functions. For more information, see the “Installations for Printing” section below.

2

Installation of SAP NetWeaver Enterprise Portal – this is optional from enhancement package 5, support package 04. [Installation Guide for SAP NetWeaver 7.0]

For more information, see SAP Note 1380566 and the “SAP NetWeaver Enterprise Portal and SAP NetWeaver Business Client” section below.

3

Installation of SAP NetWeaver TREX 7.1 [Installation Guide for SAP NetWeaver TREX 7.1]

See also SAP Note 1249465.

4

Installation of additional software on local clients, such as SAP Easy Document Management, viewers, applets [See the “Front-End Component Installation” section below]

SAP NetWeaver Portal and SAP NetWeaver Business Client You run PLM Web User Interface with SAP NetWeaver Portal or with SAP NetWeaver Business Client. We deliver Portal Content for the PLM Web User Interface as part of the Business Package for PLM Web User Interface. You can use the business package with SAP NetWeaver Portal or with SAP NetWeaver Business Client. For more information, see the following: 

Installing SAP NetWeaver: see the SAP NetWeaver Master Guide and the SAP NetWeaver Installation Guides on SAP Service Marketplace at http://service.sap.com/installnw70.



Installing SAP NetWeaver Business Client: see the SAP Library for SAP NetWeaver under SAP NetWeaver 7.0 including enhancement package 1  Functional View  SAP NetWeaver by Key Capability  People Integration By Key Capability  SAP NetWeaver Business Client (with PCD Connection).

NetWeaver Business Client for HTML From SAP ERP 6.0, enhancement package 5, you can also run PLM Web User Interface without SAP NetWeaver Portal or SAP NetWeaver Business Client. The portal is made optional by introducing the central backend system role storage (transaction PFCG) as local menu container for PLM. This frame forms the user interface, where you can see the header area, navigation bar, and working area without entering the SAP NetWeaver Enterprise Portal. The URL for NWBC for HTML can be generated by executing the transaction “NWBC” and selecting the corresponding user role, for example, “SAP_PLMWUI_DISCRETE_MENU”. For more information about NWBC, see SAP Notes on the SAP Service Marketplace at http://service.sap.com/notes. The related SAP Note is 900000.

22

June 2012

2 SAP Product Lifecycle Management: Overview 2.7 Overall Implementation Sequence

Installations for Printing To print your documents using SAP Interactive Forms by Adobe, you must install and deploy Adobe Document Services (J2EE server) with SAP NetWeaver. Adobe Document Services is part of SAP NetWeaver 7.0 (2004s) Support Package Stack 05 or higher (Stack Application Server Java). For more information about the installation and configuration of Adobe Document Services, see https://www.sdn.sap.com/irj/sdn/adobe and SAP Note 944221.

Front-End Component Installation SAP Easy Document Management You use SAP Easy Document Management to support the exchange of documents between cFolders and a backend system on SAP ECC Server. You install it as an optional front-end component within your own intranet. Before you install the current SAP Easy Document Management version on your system instances, you need to uninstall existing prior versions. For more information about the installation of SAP Easy Document Management, see the installation guide for SAP Easy Document Management on SAP Service Marketplace at http://service.sap.com/instguides under SAP Business Suite Applications  SAP ERP  SAP ERP 6.0  SAP enhancement packages for SAP ERP 6.0  SAP enhancement package 4 for SAP ERP 6.0  Installation Guide SAP Easy Document Management 7.0

Viewers for 2D and 3D Graphics To display 2D and 3D graphics in PLM Web User Interface, you can use a viewer, which must be installed locally on each user’s client. In particular, you can use the viewer that is shipped with SAP enhancement package 5 for SAP ERP 6.0. For more information about how to install this viewer for PLM Web User Interface, see SAP Note 1319472. If you work with viewers, it might also be necessary to install a conversion server, on which the system converts CAD files into a format that your viewer can display. For more information, see the Installation of Optional Components section.

Additional Installations on Local Clients For running PLM Web User Interface, all users must also have two additional applets installed on their local clients. For more information about how to prepare the installation and local security settings for these applets centrally, see SAP Note 1224097. Installation of SAP Active Component Framework (ACF) To display the SAP Active Component Framework (ACF) base control correctly in Internet Explorer and to use Adobe forms and Office Integration, you must make certain browser settings and install the front-end elements of ACF. For more information on how to do this, see the following SAP Notes: 

1150277 – Prerequisites for using ACF



766191 – Active Component Framework Installation

Required Java Applets The following notes provide information about the Java applets required and any limitations that exist. 

1178747 – ACF-WDABAP: Java version for ACFExecute, ACFUpDown Explains the Java version that is required for document upload and download



960996 - Web Dynpro Applets: Requirements for NW 7.0 and higher Explains that limitations for Mac Operating System support.



1406768 - ACF - Java Runtime settings

June 2012 23

2 SAP Product Lifecycle Management: Overview 2.7 Overall Implementation Sequence

Explains how to install a patch if the ACF applet is not executed or does not response correctly. Creating a Whitelist For more information, see the SAP Implementation Guide (IMG). In transaction SPRO, choose Display SAP Reference IMG. The path in the Implementation Guide for SAP NetWeaver is: Application Server Web Dynpro ABAP Set Up Whitelist for Active Controls and Activate Whitelist for Active Controls. For general information about platform support, see the Product Availability Matrix (PAM) on http://service.sap.com/pam

Installation of Optional Components Conversion Server If you work with viewers, it might also be necessary to install a conversion server. The conversion server is installed on a separate system, and you can run either your own or a partner software on it to convert files. For more information about conversion servers, see SAP Library for SAP ERP on SAP Help Portal at http://help.sap.com/erp. In SAP Library choose SAP ERP Central Component  SAP ERP Central Component  SAP ERP Enhancement Packages  ERP Central Component Enhancement Package 5  SAP ERP Cross-Application Functions  Cross-Application Components  Document Management  Conversion.

Knowledge Provider The knowledge provider is part of the SAP NetWeaver installation and it supports file exchange for document management, including file exchange with a content server. For more information about the knowledge provider, see SAP Service Marketplace at http://service.sap.com/contentserverand http://service.sap.com/kpro.



Respositories on Content Server The PLM Collaboration (DMZ scenario) is supported in by content server using a MaxDB (database). For more information, see SAP Note 1419452. For more information about the configuration of SAP PLM Web UI see Solution Manager (http://service.sap.com/solutionmanager) for SAP PLM Web UI.

24

June 2012

2 SAP Product Lifecycle Management: Overview 2.7 Overall Implementation Sequence



Respositories on System Database Repositories on the system database can be accessed through HTTP using the SAP Web Application Server. To do this you need a user for anonymous access, without any permissions in your system. You can create this user in transaction SICF. If you do not create this user, the system displays a logon screen at the relevant point. For more information about setting up repositories on SAP Web Application Server, see SAP Library for SAP NetWeaver under SAP NetWeaver 2004  SPS 23  SAP NetWeaver 2004 Library  Application Platform  Business Services  Knowledge Provider  Content Management Service (BC-SRV-KPR)  HTTP Access for Repositories on SAP Web Application Server. The relevant section is “Activities”. Repositories on the system database not supported in the DMZ scenario.

BI Server If you want to run BCV processes and you have a SAP NetWeaver Business Intelligence (BI) already installed for your SAP ERP, you can integrate BI queries into BCV.

cProjects Server You can also integrate cProjects with SAP ERP 6.0 (with enhancement package 5). For more information about installing cProjects, see the Portfolio and Project Management Master Guide on SAP Service Marketplace at http://service.sap.com/instguides SAP Business Suite Applications  SAP PLM  using SAP Portfolio and Project Management

June 2012 25

3 Business Processes of PLM Web User Interface and BCV 2.7 Overall Implementation Sequence

3 Business Processes of PLM Web User Interface and BCV The following Business Functions are relevant for the PLM Business Scenarios: For PLM Web UI Discrete Industries: 

PLM Web User Interface (/PLMU/WEB_UI_3)



Synchronization of Engineering BOM with Manufacturing BOM (/PLMU/GSS_E2M)



PLM, Product Structure and Assembly Management (/PLMU/IPPE_INT_3)

 PLM, Product Intelligence with Business Context Viewer (/PLMU/PI_BCV) For PLM Web UI Process Industries:  Recipe Development on PLM Web UI (/PLMU/RCP_2) For further information concerning the Business Functions see SAP Library for SAP ERP on SAP Help Portal. In SAP Library choose SAP ERP Central Component  SAP ERP Enhancement Packages  ERP Central Component Enhancement Package 6  Business Functions (SAP Enhancement Package 6 for SAP ERP 6.0)

Further Information The following documents provide more information about the business processes: Content

Location

Scenario Description

See the documentation in SAP Solution Manager under Solutions/Applications  SAP PLM  Configuration Structures  SAP PLM 7.01  Web UI.

Configuration Documentation

See the documentation in SAP Solution Manager.

Security Guide

For more information, see the sections about PLM in the SAP ERP security guide on SAP Service Marketplace at http://service.sap.com/securityguide.

26

June 2012

4 Solution-Wide Topics

4 Solution-Wide Topics SAP Solution Manager contains processes and scenarios for PLM Web User Interface and for BCV. For more information about SAP Solution Manager, see http://service.sap.com/solutionmanager.

4.1 Service-Orientated 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.

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), currently this is SAP NetWeaver PI 7.3. For more information, see SAP Note 1515223 and SAP Note 1388258. Starting 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, see the SAP Library at:http://help.sap.com/nw73  SAP NetWeaver 7.3 Library English  SAP NetWeaver Process Integration  Concepts  Installation and Connectivity Options  Advanced Adapter Engine Extended and SAP Note 1573180. Asynchronous 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. ES Repository is shipped with SAP NetWeaver PI 7.1 and with SAP NetWeaver CE 7.1. The

June 2012 27

4 Solution-Wide Topics

Enterprise Services Repository is a design time environment that enables you to create and enhance enterprise service definitions and to view enterprise service models. In a SAP NetWeaver 7.0x landscape you require the Integration Repository to create and enhance enterprise service definitions in a design time environment. 

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



SAP Solution Manager 7.0 EHP1 The Solution Composer, shipped with SAP Solution Manager 7.0 EHP 1 SP 23, is required to host the enterprise service online documentation.

Overview: SAP’s Applications for SOA Enablement

28

June 2012

4 Solution-Wide Topics

The following table describes the SAP applications required or recommended for different runtime and design time use cases: SAP Applications SAP Business Suite

SAP NetWeaver PI 7.0x (Integration Repository)

SAP NetWeaver PI 7.1 or higher (ES Repository)

SAP NetWeaver CE 7.1 or higher (ES Repository)

SAP Solution Manager 7.0 EHP1 or higher (Solution Composer)

SAP NetWeaver 7.1 or higher Services Registry

Runtime Usage: Enterprise Service Provisioning

Required

Process integration and mediated communication

Optional

One option required

Design Time Usage: Create and enhance enterprise service definitions

Required

View enterprise service models

Design and develop composite applications

One option required

Recommended

One option required

Required

Recommended

Recommended

Enterprise service online documentation

Required

Publications of enterprise service endpoints

Optional

Recommended

Required

June 2012 29

4 Solution-Wide Topics

4.2 Installation of the Service-Orientated 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:



o

the software component version with which the service was shipped

o

the business function(s) required to be activated

Identification of technical usages (relevant for SAP ERP only) SAP Note 1566412 provides a mapping of business runctions 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 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.



Enterprise service definitions for SAP NetWeaver PI 7.0x or ES Repository (SAP NetWeaver 7.1 or higher) (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 usage type downloads the content files for both SAP NetWeaver 7.0 or higher. Unpack the ZIP file and copy the tpz files corresponding to your SAP NetWeaver 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 )



Enterprise service models for ES Repository (SAP NetWeaver 7.1 or higher) (optional) To install the content required for the enterprise service models you must select the technical usage “ESR Content” in the enhancement package installation process. This usage type downloads the content files for SAP NetWeaver ES Repository 7.1 or higher. Unpack the ZIP file and copy the tpz files into the import directory of your Enterprise Services Repository. Use the import function to import the content files

30

June 2012

4 Solution-Wide Topics

into the Enterprise Services Repository. (Choose )

Tools

Import Design Objects

The enterprise service models are not available for the Integration Repository (SAP NetWeaver PI 7.0x) 

Enterprise service online documentation for Solution Composer (optional) To install the content required for the enterprise service online documentation you must download the content file for the corresponding Business Suite application product version from the Service Marketplace. Then you must import the content file into your Solution Composer. Refer to SAP Note 1224284 for further information.



Services Registry (optional) The services registry is shipped with SAP NetWeaver PI 7.1 and CE 7.1. You must install 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 installation of SAP NetWeaver PI, CE and ES Repository, refer to the corresponding SAP NetWeaver Installation and Master Guides.

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

SDN Community in the SAP Network at https://www.sdn.sap.com/irj/sdn/soa (registration required)



The SAP Enterprise Service Workplace at http://ESWorkplace.sap.com



The Enterprise Services Wiki in the SAP Network at https://wiki.sdn.sap.com/wiki/x/LQ0 (registration required)



SAP Note 1224284: Enterprise Services, Installing and Accessing the SOA Documentation



SAP Note 1359215: Technical prerequisites for using enterprise services



SAP Note 838402: Problems with non-Unicode system landscapes

June 2012 31

5 References

5 References List of Documents The following table lists all documents mentioned in this Master Guide: Title

Where to Find

SAP ERP 6.0 Enhancement Package 5 Installation Guide

SAP Service Marketplace at http://service.sap.com/instguides SAP Business Suite Applications  SAP ERP  SAP ERP 6.0  SAP enhancement packages for SAP ERP 6.0  SAP enhancement package 5 for SAP ERP 6.0

SAP NetWeaver 7.0 Installation Guides

SAP Service Marketplace at http://service.sap.com/installnw70

SAP NetWeaver TREX 7.1 Installation Guides

SAP Service Marketplace at http://service.sap.com/installnw70  3 Installation Standalone Engines  SAP NetWeaver Search and Classification TREX See also SAP Note 1003900.

Information about installing SAP NetWeaver Business Client

SAP Library for SAP NetWeaver under SAP NetWeaver  SAP NetWeaver 7.0 (including enhancement package 1)  Functional View  SAP NetWeaver by Key Capability  People Integration By Key Capability  SAP NetWeaver Business Client (with PCD Connection)

SAP Easy Document Management Installation Guide

SAP Service Marketplace at http://service.sap.com/instguidesunder SAP Business Suite Applications  SAP ERP  SAP ERP 6.0  SAP enhancement packages for SAP ERP 6.0  SAP enhancement package 4 for SAP ERP 6.0  Installation Guide SAP Easy Document Management 7.0

Information about installing Adobe Document Services

https://www.sdn.sap.com/irj/sdn/adobe and SAP Note 944221

Master Guide for SAP for Automotive

SAP Service Marketplace at http://service.sap.com/instguides  Industry Solutions  Industry Solution Guides  SAP for Automotive

SAP ERP Security Guide

SAP Service Marketplace at http://service.sap.com/securityguide

Master Guide: Portfolio and Project Management

SAP Service Marketplace at http://service.sap.com/instguides SAP Business Suite Applications  SAP PLM  using SAP Portfolio and Project Management

Installation Note for Viewer in SAP ERP 6.0 EHP4

SAP Note 1179524

32

June 2012

7 Appendix

7 Appendix 7.1 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.

Tools On SAP Service Marketplace, we provide some tools that allow you to look up more detailed information about business scenarios, business processes, and implementable steps. These tools include the following: Tools for Looking Up Information about Business Processes, Scenarios, and Implementable Steps Tool

Purpose

Business process repository (BPR) viewer

To look up descriptions of business scenarios, business processes, and implementable steps

Scenario and process component list

To look up the required components and releases for a business scenario, business process, or implementable step

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: Tools for Supporting Installations and Upgrades Tool

Purpose

Solution Manager System Landscape

To model and set up your system landscape

SAP Solution Manager Maintenance Optimizer

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

You require at least one of the following versions of SAP Solution Manager. -

SAP Solution Manager 7.0 EHP1, SPS23 or higher

-

SAP Solution Manager 7.1, SPS01 or higher

June 2012 33

7 Appendix

SAP Solution Manager 7.0 EHP1, SPS23 supports all update and maintenance processes (for example, transaction SMSY or Maintenance Optimizer) There is no need to upgrade to SAP Solution Manager 7.1. For more information, see SAP Service Marketplace at http://service.sap.com/solutionmanager.

SAP Solution Manager: Implementation Content To get implementation content that supports you during the configuration of your business processes, business scenarios, and implementable steps, you need the SAP Solution Manager add-on Implementation Content ST-ICO 155 L022 (SP25).

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 http://www.sdn.sap.com/irj/sdn  Application Lifecycle Management  Technical Enablement  Update and Upgrade  Related Areas on Upgrade and Update Management  Landscape Verification (http://www.sdn.sap.com/irj/sdn/alm?rid=/webcontent/uuid/70fc3790-7ec9-2d10-57ad95b2d0d1185d).

SAP Business Suite: Landscape Implementation – Technical Planning Guide To get an overview of the necessary steps for planning a system landscape, use the Landscape Implementation – Technical Planning Guide on SAP Service Marketplace at http://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 Deployment options Typical implementation process

7.2 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, and implementable steps 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: 

34

Description of the business scenario, process, or implementable step

June 2012

7 Appendix



Configuration content (Customizing activities or configuration documentation)

7.2.1 Using the BPR Viewer Procedure Calling up the BPR Viewer You can call up the BPR viewer directly using the Internet address https://implementationcontent.sap.com/bpr. Alternatively, you can also call up the Internet address http://service.sap.com/bpr first, to see more background information about the BPR viewer and additional material on SAP Service Marketplace.

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: 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. The 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.

7.2.2 Scenario and Process Component List The scenario and process component list (SCL/PCL) is a tool on the SAP Service Marketplace that allows you to find realization alternatives for SAP solutions, business scenarios, and processes for your SAP enhancement package installation. You find the tool at http://service.sap.com/scl. The SCL/PCL helps you to bridge the gap between the business view and the technical view in SAP's products. It shows you which application components are needed to realize a business scenario or a process and which business scenarios are possible with a given set of application components.

Using the SCL/PCL

Procedure 1. Go to SAP Service Marketplace at http://service.sap.com/scl. 2. To start the SCL/PCL, choose Start Application. The following selection options are provided: 

SAP Scenarios and Realization Alternatives With this option you can browse SAP’s solutions, business scenarios, and processes. You can find out which components are needed and the available alternatives.

June 2012 35

7 Appendix



SAP Components and Possible Scenarios This option allows you to browse SAP’s products and components and to find out, which business scenarios and processes you can realize using the components. For more information on how to use the tool, refer to the Help section. 3. Select SAP Scenarios and Realization Alternatives. Select one or several scenarios, processes, and variants you want to realize. You can make your selection by using an alphabetical index or a full-text search. It is also possible to see all scenarios for a certain solution. You will then get a list of the alternative ways to realize these scenarios. You can also search for the identified business functions of a SAP enhancement packages. In the following steps we chose the scenario Billing Analysis in ERP as an example. 4. Add the scenario Billing Analysis in ERP to the Selected Scenarios/Processes/Variants list and choose Show Realization Alternatives. The SCL/PCL then lists the different possibilities. With options like Validity you can switch between possible and impossible realization alternatives. The Optional Comp. dropdown list helps you to find the minimum required SAP product versions.

36

June 2012