Quick Guide to Implementing the SAP PLM Rapid-Deployment Solution (Based on EHP 6 for ERP 6.0 and Part of PLM 7.02) (EN)

(1)

EHP 6 for ERP 6.0

PLM 7.02

July 2012

English

Quick Guide to

Implementing the SAP

PLM Rapid-Deployment

Solution (Based on EHP 6

for ERP 6.0 and Part of

PLM 7.02) (EN)

SAP AG

Dietmar-Hopp-Allee 16 69190 Walldorf

(2)

Copyright

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company.

Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

(3)

Icons

Icon Meaning Caution Example Note Recommendation Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

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

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

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

EXAMPLE TEXT _{Keys on the keyboard, for example, function keys (such as}_F2_{) or the} ENTER key.

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

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

(4)

Quick Guide to Implementing the SAP PLM

Rapid-Deployment Solution

1 About this Quick Guide

This Quick Guide is intended to help consultants and customer project members to implement the SAP PLM rapid-deployment solution (based on EHP 6 of ERP 6.0 and PLM 7.02). The guide focuses on the technical implementation aspects and usage of the SAP Solution Manager and SAP Best Practices solution builder. The document describes all the steps required for successful implementation of this rapid-deployment solution and directs you to more detailed documentation that you might find useful.

The System Landscape Prerequisites section lists all the system prerequisites that have to be met by customers prior to implementation of this rapid-deployment solution. Note that installation of the required systems is not within the scope of the SAP PLM rapid-deployment solution. The Preparation Activities section explains the specific activities that need to be performed to ensure the successful implementation of this rapid-deployment solution. These activities are within the scope of the rapid deployment of SAP PLM Foundation.

2 Solution Overview

The SAP PLM rapid-deployment solution Is based on SAP PLM 7.02

Supports swift deployment of the required configuration settings

Includes pre-configuration content and knowledge transfer to key users.

3 Implementation Methodology

Overall project guidance is provided by a phased, delivery-oriented methodology that streamlines implementation projects for solution packages, guiding project teams through the following phases:

Discover Start Deploy Run

The methodology supports project teams with templates, tools, questionnaires, and checklists, including guides and accelerators to ensure the quick and pragmatic implementation of rapid-deployment solutions.

(7)

1. Manual implementation – All Customizing activities are described in configuration guides and can be manually processed in the system. (see step-by-step guide: Deploy

Train key users Content Library).

2. SAP Solution Manager-based implementation – All Customizing activities are described in configuration guides that are delivered with an SAP Solution Manager template. You use this template to complete the configuration steps manually in an implementation project within SAP Solution Manager.

3. Solution Builder-based implementation – You can select and activate Customizing activities that run automatically.

For access to the methodology, approach your SAP Consulting contact.

4 SAP System Landscape Prerequisites

(Administrator)

This section summarizes the system-related requirements that the customer must ensure are in place prior to the actual implementation project.

Note that setup of the system landscape is not within the scope of the rapid-deployment solution delivery.

The customer will need to provide the system landscape, that is, install the required software components, to enable the project team to implement and configure the rapid-deployment solution. During this phase, SAP provides advice on aspects of the system landscape and the components required.

4.1 Required SAP Software Components

4.1.1 SAP ERP 6.0

It is assumed that the customer has already completed installation of the SAP ERP system before the start of the implementation project.

The following table summarizes the software requirements:

Product Version

Component Remarks Logical Component

SAP PLM rapid-deployment solution

SAP ERP 6.0 SAP ECC Server

Support package stack 3 or above

SAP_ERP_EHP_PLM

(required for SAP Solution Manager implementation) EHP6 FOR SAP ERP 6.0 ERP ABAP Server Support package stack 3 or above SAP_ERP_EHP_PLM

(required for SAP Solution Manager implementation)

(8)

4.1.2 SAP Solution Manager

The SAP Solution Manager system is required for the installation and management of maintenance certificates, enhancement packages, and upgrades.

In the context of SAP rapid-deployment solutions, implementation content is delivered in SAP Solution Manager templates.

It is assumed that the customer system landscape features a SAP Solution Manager production system (release 7.0, SP31 or above), particularly if the customer is already using other SAP products (for example, SAP ERP).

For more information about SAP Solution Manager, see the SAP Library

documentation for SAP Solution Manager at http://help.sap.com SAP Solution

Manager, or http://service.sap.com/solutionmanager. Product and Product

Version

Component Remark

SAP Solution Manager SAP Solution Manager 7.0 EHP1 (SP18 or higher)

If you use a SP level lower than 24, see SAP Note 1579267.

OR 7.1 SP01

ST Required

SAP Solution Manager Content 100 (SP01 or higher)

ST-RDS Required implementation content

It is assumed that the customer already has the SAP ERP system installed and configured.

4.2 4.3 SAP Software Component Installation Check

Before implementation of the pre-configured content can start, the SAP project team performs a check of the software installation based on the requirements provided in this guide. Depending on the result, the SAP project team advises the customer on any missing steps that need to be performed.

4.3.1 SAP ERP 6.0

Procedure

(9)

1. Look up the current product version using the following navigation path: SAP Menu System Status Component Version

2. Choose the Component Information pushbutton.

3. In the dialog box, check that the following component version is installed: Software

Component

Release Short Description of Software Component EA-APPL 606 SAP Enterprise Extension PLM, SCM, Finance

4.3.2 SAP Solution Manager

Make sure SAP Solution Manager is installed and always use the latest available SP level.

4.4 Installation

If the systems do not meet the required prerequisites, this chapter explains how to perform the necessary installations.

4.4.1 SAP ERP 6.0

Navigate to the First Steps document:

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 First Steps document

The Installation Guide is available at the following navigation path:

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 pack 6.0 for SAP ERP 6.0

For more information about installation of enhancement package 6 for SAP ERP 6.0, see SAP Note 1566412.

4.4.2 SAP Solution Manager

The Installation Guide is available at the following navigation path:

http://service.sap.com/instguides SAP Components SAP Solution Manager Release 7.0

4.4.3 Receiving the Software at the Correct SP Level

For delivery of the software, you require an installation number and corresponding license agreement. You need an S user to order software from the SAP Software Catalog or to download software from the SAP Software Download Center on SAP Service Marketplace.

You can only order unrestricted SAP software. Contact the SAP contract department to ask for a physical shipment or create a customer message on component XX-SER-GEN-CONTR.

(10)

You use the maintenance optimizer in SAP Solution Manager to download and install the required software components and SP levels

If you need to download software components manually from the SAP Software Download Center on SAP Service Marketplace at https://service.sap.com/swdc, use the following navigation path:

SAP Software Download Center Installations and Upgrades Browse our Download Catalog SAP Application Components SAP ERP SAP ERP ENHANCE

PACKAGE EHP6 FOR SAP ERP 6.0

Only the current release is delivered to SAP customers / partners through SAP SWDC on SAP Service Marketplace and standard delivery (for example, Software Catalog). If the required SPS for correct SAP BP packages activation is based on an SPS level lower than the current release, you can request the necessary SPS by creating a customer message. For more information, see SAP Note 925690.

4.5 Required SAP Notes and Messages

It may be that issues become apparent after shipment of the SAP PLM rapid-deployment solution (and this document). An SAP Note exists to cover such eventualities.

Before you start the building block installation process, check the latest version of the SAP Note below to obtain updates and corrections for any problems identified after shipment.

SAP Note Description

1677023 SAP PLM rapid-deployment solution 1678803 SAP PLM RDS V2 606 - collective note

Troubleshooting

If errors occur during the installation process, proceed as follows:

1. Check for troubleshooting notes in the step description of the Building Block Configuration Guide.

2. Check for relevant SAP Notes listed in the Building Block Configuration Guide.

3. Log on to SAP Service Marketplace and search for problem-related SAP Notes. If the problem persists, proceed as follows:

o If the problem relates to the SAP PLM rapid-deployment solution, create a customer message on component SV-RDS-PLM.

o If the problem is a general one, indicate the relevant application component.

4.6 Other Related Documentation (Optional)

The Master Guide SAP PLM 7.02 provides crucial information about the installation of SAP PLM 7.02. Read this guide thoroughly.

(11)

http://service.sap.com/instguides SAP Business Suite Applications SAP PLM using SAP enhancement package 6 for SAP ERP 6.0 Master Guide SAP PLM 7.02

The Security Guide SAP ERP provides an overview of the security-relevant information that applies to SAP ERP.

http://service.sap.com/securityguide SAP Business Suite Applications SAP ERP 6.0, EHP6 SAP ERP 6.0 Security Guides

The Configuration Guide SAP PLM 7.02 provides additional information about Customizing activities.

http://service.sap.com/plm SAP Enhancement Packages for SAP PLM 7.02 Media Library Enhancement Packages for SAP PLM SAP PLM 7.02 SAP EHP6 for SAP PLM -

Configuration for SAP PLM Web UI

5 System Preparation for SAP

Rapid-Deployment Solution Implementation

(Administrator/ Consultant)

Before starting the automated content implementation for this solution, the consultant must perform the following steps in this chapter.

5.1 Activate Services

Use

SAP NetWeaver Business Client uses HTTP services that are defined in the Internet

Communication Framework (ICF). By default, HTTP services are delivered as inactive for security reasons.

Procedure

1. Access the following transaction: Transaction Code SICF

2. On the Maintain Services screen, enter Service in the Hierarchy Type field to filter the ICF hierarchy.

3. Choose the Execute pushbutton.

4. Expand the hierarchy and activate the following services (including all sub nodes) by choosing the Activate Service option in the context menu of each service:

Field Name Entry Value

Virtual Hosts / Services Default_host SAP BC NWBC

Result

(12)

5.2 SAP NetWeaver Business Client

The SAP NetWeaver Business Client (NWBC) is a new SAP UI that presents end users with a seamless integration of classic SAP GUI-based transactions and newer Web Dynpro-based applications. The desktop variant offers a high-fidelity UI to improve user experience. Thus, the NWBC provides a typical, modern desktop-based user experience.

SAP NetWeaver Business Client is generally available for all ERP customers with SAP NetWeaver 7.02 SP02.

Further Information

The SAP NetWeaver Business Client (NWBC) is a rich UI client that offers a single point of entry to SAP applications, especially harmonizing access to existing SAP GUI transactions and newly developed applications based on SAP Web Dynpro. NWBC itself is a high-fidelity shell designed to harmonize the user experience over different UI technologies.

NWBC comes in two flavors:

NWBC for HTML is a browser-based shell (for use with ABAP systems) for casual use scenarios. Within this environment, all SAP GUI transactions are rendered using the SAP GUI for HTML rendering engine.

NWBC for Desktop is a Microsoft .NET-based application that targets the power user. In this scenario, the SAP GUI itself is used as the rendering engine if installed. NWBC effectively replaces SAP GUI as the main entry point to SAP applications.

Documentation

Documentation comes with the SAP NetWeaver Business Client for Desktop (navigation path:

Help Show Documentation). Alternatively, see the documentation link mentioned in SAP Note

900000.

Procedure

Download the software in the SAP Service Marketplace at: service.sap.com/installations A-Z Index NETWEAVER BUSINESS CLIENT NWBC NW BUSINESS CLIENT 3.0

After downloading the software, install the SAP NetWeaver Business Client on a local PC. For further requirements and restrictions, see SAP Note 1029940. For configuration instructions, see SAP Note1368177

.

When using NWBC for Desktop, specific information is required in the front end configuration. To determine the URL for the NWBC for Desktop configuration, proceed as follows:

1. Log on to your SAP system using SAP GUI.

2. Start transaction NWBC. The NWBC for HTML opens in the default browser. 3. Copy the path from the address, for example,

https://<domain>:<portnumber>/nwbc. Ignore any additional path information in the URL after “…/nwbc”.

4. Start NWBC for Desktop and create a new connection. 5. Define the following parameters:

(13)

1. Name: <for example, RDS System>

2. URL: https://<domain>:<portnumber>/nwbc. 3. Type: ABAP

4. Client: <Client number> 6. Choose the Connect (Restart) pushbutton.

In case of problems refer to SAP Note 1400383, SAP BAiO: NWBC & EhP4 for SAP

ERP 6.0 (ABAP) - Configuration.

5.3 Installation of Java Runtime Environment

To run the WebDynpro application of the PLM Web user interface and to upload and download files using the Active Component Framework (ACF), you need to have Java Runtime

Environment 1.6 or above installed on your local machine.

Procedure

To download the software, follow this link: http://www.java.com/en/download/

The following Java Runtime environment releases are currently supported: JRE 1.6.0.13 – 1.6.0.23. See related SAP Notes 1305974 and 1577193.

5.4 SAP Product Visualization

Product visualization is an integral component of modern business software solutions. The SAP viewer for 2-dimensional (2D) images and 3-dimensional (3D) scenes provides basic visualization as a permanently available and fully integrated solution component. That is, basic viewing

functionality is always available to enable the visualization of parts and assemblies when working on tasks within a business process.

Procedure

Download the software in the SAP Service Marketplace at:

service.sap.com/installations Support Packages and Patches Search for Support Packages and Patches. Enter Product Visualization as the search term and start your search. As a

minimum, download Product Visualization 7.1 that includes redlining and DMU capabilities. Once you have downloaded the software, install the viewer on your local PC.

5.5 Define Storage Category

Before activation can commence, the SAP standard storage category DMS_C1_ST has to be defined and customized in the SAP system. The reason for this is that the test data of Building Block A19 stores the document files in this storage category. This prerequisite should be completed by the customer.

(14)

5.6 Installation of the SAP Best Practices Add-On

These steps are only required if SAP Best Practices solution builder is to be used to implement the content.

The following SAP Best Practices content add-on has to be installed in order to use the automated installation of the SAP PLM rapid-deployment solution:

Software Component

Release Version

BP-ERP 606Vx 606Vx Always use the latest available version as outlined in

SAP Note 1301301 (Release Strategy for SAP Best Practices Package ABAP Add-ons)

Use

SAP Best Practices scenarios can be configured automatically using, if possible, Business Configuration Sets (BC Sets) to maintain Customizing settings and Extended Computer Aided Test Tool procedures (eCATT) to create master data.

BC Sets and eCATTs were delivered as transport files with SAP Best Practices add-on BP-ERP 606Vx. Import this file into your ERP system if you want to make use of the automated

configuration.

Procedure

1. Download add-on BP-ERP 606Vx from the SAP Software Download Center:

http://service.sap.com/swdc Installations and Upgrades Browse our Download Catalog SAP Rapid Deployment Solutions SAP PLM rapid-deployment solution

2. Import the SAR file into your SAP ERP system using transaction SAINT.

Result

BC Sets and eCATTs are now available in your ERP system and can be activated in combination with the SAP Best Practices solution builder for automated configuration of BP ERP scenarios.

5.7 Installation of the SAP Best Practices Solution

Builder

These steps only have to be performed if SAP Best Practices solution builder is being used to implement the content.

The SAP Best Practices solution builder has to be installed in order to use the automated activation of the SAP PLM rapid-deployment solution:

Software Component

Release Version

BP-SOLBLD 70Vx Always use the latest available version as outlined in SAP Note 1301301 (Release Strategy for SAP Best Practices Package ABAP Add-ons)

(15)

Use

Use the SAP Best Practices solution builder to easily install the complete SAP Best Practices package or selected scenarios in the minimum amount of time.

The SAP Best Practices solution builder is a tool that guides you step by step through the installation process directly in the system.

Procedure

1. Download add-on BP-SOLBLD 70Vx from the SAP Software Download Center:

http://service.sap.com/swdc Installations and Upgrades Entry by Application Group SAP Rapid Deployment Solutions SAP PLM rapid-deployment solution

2. Import the SAR file into your SAP ERP system using transaction SAINT.

Result

The SAP Best Practices solution builder is now installed in your SAP ERP system. For more information about using the tool, see the Installation of Business Content section of this guide.

5.8 General Client Settings

5.8.1 Creating User for Activation of SAP Rapid-Deployment

Solution Content

Use

If you want to create a user to run the content activation of the related SAP rapid-deployment solution scope, you need to consider the following:

The SAP PLM rapid-deployment solution does not supply separate roles for Customizing or setup activities.

If necessary, you can define a separate role corresponding to your individual Customizing project according to the functions provided in the Role Maintenance (transaction PFCG). In this

transaction you can find all the authorizations you need to access the corresponding Customizing activities required for the scope of this rapid-deployment solution.

Alternatively, you can use authorization profile SAP_ALL. If this authorization does not comply with your authorization concept, you should restrict the rights of the user according to your internal authorization guidelines. If you do not use profile

SAP_ALL, issues may occur during activation that will need to be resolved. You can

use transaction SU53 to obtain information on the missing authorizations and extend the authorization data as needed.

Immediately after activation of the SAP PLM rapid-deployment solution content, remove the authorizations you have given the system user that performed the activation steps. This is for security reasons to prevent the system user from misusing previously granted authorizations.

A number of system users are created manually during content activation of the SAP PLM rapid-deployment solution, and authorization roles are assigned accordingly. These users should only access the SAP system from the SAP NetWeaver Business Client.

(16)

The following procedure describes the steps to set up a system user to activate the SAP PLM rapid-deployment solution-specific content.

Procedure

1. To perform this activity, choose one of the following navigation options:

SAP Menu Tools Administration User Maintenance Users

Transaction Code SU01

2. On the User Maintenance: Initial Screen, in the Userfield,enter<User-ID>and choose the

Create pushbutton.

3. Choose the Address tab page. 4. Make the following entries:

Field Name User Action and Values Note

Last name <Last name of the user>

First name <First name of the user> 5. Choose the Logon Data tab page.

6. Make the following entries:

Password <initial password>

User type Dialog 7. Choose the Defaults tab.

8. Enter the following:

Logon language EN

Decimal notation 1.234.567,89

Date format DD.MM.YYYY 9. Choose the Roles tab page.

10. Enter the user role you created that contains the necessary authorization profile.

Alternatively, you can assign profile SAP_ALL on the Profiles tab page. Make sure that this corresponds to your internal security guidelines.

11. Save your entries.

Result

The user that was created can be used to activate the content of the SAP PLM rapid-deployment solution.

5.8.2 Deselecting Activation Links in BC Sets

SAP recommends that you turn off the creation of activation links. This significantly increases activation speed and helps to avoid errors.

(17)

Procedure

1. Use one of the following navigation options:

SAP Menu Tools Customizing Business Configuration Sets Activation of BC Sets

Transaction Code SCPR20

2. On the Business Configuration Sets: Activation screen, choose Utilities System Settings.

3. Choose the Change pushbutton (Shift + F1).

4. In the Activation section, select the Do Not Create radio button. 5. Choose the Enter pushbutton to confirm the information message. 6. Save your entries.

5.8.3 Maximum Work Process Runtime

Use

Dynamic switchable profile parameters (indicated by a selected checkbox) have to be checked before activation. The following profile parameters therefore have to be checked and adapted.

Procedure

1. Access the following transaction: Transaction Code RZ11

2. On the Maintain Profile Parameters screen, make the following entries:

Field Name Description User Action and

Values

Note Param. Name Profile parameter name rdisp/max_wprun_time 3. Choose the Display pushbutton.

4. On the Display Profile Parameters Attributes screen, select the Change values pushbutton. 5. On the Change Parameter Value screen, make the following entries.

Parameter Name Description New

Value

Note

rdisp/max_wprun_time Max work process run time 3600 Check and adapt value if value is <3600

6. Choose Save.

When you save the change, the window closes and the value of the parameter is changed. Note that this change only becomes effective when you log off and then log on to the system again.

(18)

5.8.4 SAP Scripting

Use

eCATTs are used to automate the activation of configuration settings for the rapid deployment of SAP PLM. Prior to activation, you must allow eCATT processing in the system by setting the profile parameter sapgui/user_scripting. You need to set the value for Enable or disable user

scripting on the front-end to true.

Procedure

1. Access the following transaction: Transaction Code RZ11

2. On the Maintain Profile Parameters screen, enter the following:

Field name Description User Action and

Values

Note

Param. Name Profile parameter name sapgui/user_scripting 3. Choose the Display pushbutton.

4. On the Display Profile Parameters Attributes screen, choose the Change values pushbutton. 5. On the Change Parameter Value screen, enter the following:

Field Name Description User Action and Values

Note

New Value New Value for user scripting

TRUE Enable SAP scripting

When you save the change, the window closes and the current value of the

parameter changes to TRUE. Note that this change only becomes effective when you log off and then log on to the system again.

If the parameter is set in RZ11, you lose the change when you restart the server.

5.8.5 Set Default Timeout for HTTP and HTTPS Services

Use

SAP recommends that you set the TIMEOUT and PROCTIMEOUT value to 300 or 600 (seconds) for both services. The default is 60.

The values are also set using system parameters (see the Procedure section below): icm/server_port_<*> - Standard value for *: 0: http, 1 or 2: https

For example:

icm/server_port_0 = PROT=HTTP, PORT=8000, PROCTIMEOUT=300, TIMEOUT=600

(19)

TIMEOUT=600

Procedure

1. Access the transaction using the following navigation paths:

SAP Menu Tools CCMS Configuration System Profile

Transaction Code RZ10

2. On the Edit Profiles screen, enter your instance profile.

3. In the Edit Profile box, select the Extended maintenance radio button and choose the Change pushbutton.

4. On the Maintain Profile screen, enter the following:

Parameter Name Description New

Value

Note

icm/server_port_<*> Default value for *: 0: http, 1 or 2: https

300 or 600

Set to 300 or 600 (seconds) for TIMEOUT and PROCTIMEOUT, the default is 60 5. Choose the Back pushbutton

6. Choose the Save pushbutton.

These profile parameters only require adaptation if you are using SAP NetWeaver Business Client.

5.9 Prepare System User for Content Activation

5.9.1 SAP Software Change Registration (SSCR): Developer

Key

The user ID used for activation has to be registered as a developer on SAP Service Marketplace (SAP Software Change Registration (SSCR)). For more information, see SAP Note 86161. The SSCR developer key is needed because the user ID used for SAP PLM rapid-deployment solution activation creates and changes objects from the customer name range during the SAP rapid-deployment solution activation process. If the SAP rapid-deployment solution activation user is not registered as a developer, automated SAP rapid-deployment solution activation will incur errors.

Procedure

1. Access SAP Service Marketplace at http://service.sap.com/sscr.

2. For detailed user documentation about how to obtain the SSCR developer key, see the SAP

Software Change Registration (SSCR) homepage.

An SSCR developer key is a 20-character combination of digits that is queried when an SAP ERP user tries to create or change an object from the customer name range for the first time. The prompting message for the developer key appears once for each SAP ERP user. If registration is successful, this SAP ERP user is no longer

(20)

prompted to enter a developer key. The SSCR developer key is generated from the installation number of the affected installation and the SAP ERP user name.

5.9.2 Activation Language

Make sure that your logon language (not your local language) for all activation activities is always

English.

5.9.3 User Settings for Activation

For activation, SAP recommends that only one user ID be used to activate the SAP rapid-deployment solution. Changing ownership for the activation of the solution can be a complicated process.

Make sure that you only have a single SAP GUI session running when you activate SAP Best Practices. If you run several SAP GUI sessions, some automated

installation activities might run into errors.

5.9.4 Deactivate Info Dialog Box on Dynpro Size Check

Use

The sizing conflicts dialog box that may appear during activation has to be deactivated.

Procedure

1. Log on to the system with the user.

2. Choose the Customizing of Local Layout pushbutton (the first on the right side of the standard toolbar) or enter ALT + F12.

3. Select menu item Options. 4. Select the SAP Internal checkbox

5. De-select the Enable dialog box for dynpro size check checkbox. 6. Choose the OK pushbutton at the bottom.

5.9.5 Unicode Settings

Use

Before each user logs on to the system for the first time, the user’s local GUI must be set to use the Unicode code page.

Procedure

1. From the SAP Logon Pad, select your system ID. 2. Choose the Change Item button.

(21)

3. In the System Entry Properties dialog box, toggle to the Codepage tab page. 4. Select Unicode (UTF-8) from the Encoding dropdown list.

5. Choose the OK pushbutton.

5.9.6 Allow GUI Scripting

Use

You perform this activity to enable eCATTs GUI scripts to be executed with your GUI.

Procedure

1. Log on to the system with the user

2. Choose the Customizing of Local Layout pushbutton (the first on the right side of the standard toolbar) or enter ALT + F12.

3. Select the menu item Options.

4. Choose the Accessibility & Scripting folder. 5. Select the Enable scripting checkbox.

6. Deselect the checkboxes Notify When a Script Attaches to SAP GUI and Notify When a

Script opens a Connection.

7. Choose the OK pushbutton at the bottom.

5.9.7 Set Decimal Notation and Date Format

Use

Perform this activity to set up the activation user ID.

Procedure

1. Use one of the following navigation options:

Menu Bar System User Profile Own Data

Transaction Code SU3 2. Choose the Defaults tab page.

3. Make sure you set Decimal Notation according to your country’s default, for example, 1.234.567,89.

4. Make sure you set Date Format according to your country’s default, for example, DD/MM/YYYY.

5. Make sure that you assign your printer in the field output device (see also the Printer

Environment section above).

6. Save your entries. 7. Log off from the system. 8. Log on to the system.

You have to log off and then back on to allow the change in the user settings to take effect.

(22)

9. When the complete activation procedure is finished, you may change these values as desired.

Result

The decimal notation and date format have been set up according to your country format. The standard printer has been defined.

6 Implementation of Rapid-Deployment Solution

Business Content (Consultant)

When the customer has finished setting up the system landscape, the project team can start the implementation of the rapid-deployment solution. This chapter describes additional preparation activities that need to be carried out by the project team.

6.1 Installation of Language/Country-Specific Content

The SAP PLM rapid-deployment solution provides translation into different languages, but no country-specific settings.

The currently available version of the SAP PLM rapid-deployment solution comprises all languages; there are no separate SAP PLM rapid-deployment solution versions for different countries or languages.

Language-specific Customizing and test data is automatically installed in the SAP system when using the SAP Best Practices solution builder.

For manual configuration activities, translation is provided in the configuration guides; language-specific texts have to be maintained manually.

Typical configuration content is installed in the master language English and a second local language. There is, however, also the option of installing content in additional languages.

6.2 Rapid-Deployment Solution Content Installation

Variants

Before running the implementation as described in section Implementation of rapid-deployment

solution Business Content, choose one of the different installation variants offered by the SAP

PLM rapid-deployment solution.

The customer can choose from the following three variants for implementation of rapid-deployment solution content:

1. Manual implementation – All Customizing activities are described in configuration guides and can be manually processed in the system.

2. SAP Solution Manager-based implementation – All Customizing activities are described in configuration guides that are delivered with an SAP Solution Manager template. You use this template to complete the configuration steps manually in an implementation project within SAP Solution Manager.

3. Solution Builder-based implementation – You can select and activate Customizing activities (as many activities as technically possible) that run automatically.

(23)

6.2.1 Manual Implementation

If you have decided to manually implement the SAP PLM rapid-deployment solution, you have to follow the implementation activities of the configuration guides in the sequence shown below. You can find the configuration guides in the SAP PLM rapid-deployment solution content library (see step-by-step guide: Deploy Train key users Content Library).

Building Blocks for Basic Management of Product Data (Discrete Industries) A13 BB ID Building Block Name

A10 Embedded Search

A11 Content Server

A04 PLM Web UI Technical Settings

A12 PLM Web UI Advanced Technical Settings A19 Sample Data for Discrete Industries

Building Blocks for Basic Management of Product Data (Process Industries) A17 BB ID Building Block Name

A10 Embedded Search

A04 PLM Web UI Technical Settings

A12 PLM Web UI Advanced Technical Settings A24 Specification Management Settings

A21 Recipe Settings

A22 Compliance Check Settings

A23 WWI Settings

A20 Sample Data for Process Industries

6.2.2 Solution Manager Based Implementation

If you have decided to implement the SAP PLM rapid-deployment solution using Solution Manager, proceed as described in the following sections.

6.2.2.1 Maintain System Landscape in SAP Solution Manager

The SAP PLM rapid-deployment solution is designed for a specific system landscape that is represented by logical components in the Solution Manager template.

The SAP Solution Manager template contains the logical components that define the system landscape required for the rapid deployment of SAP PLM. You can use the logical components to map the physical systems in your system landscape. This allows you to configure the systems directly using SAP Solution Manager.

During the template selection, you can also check and maintain the system landscape. However, we recommend maintaining the system landscape before the template selection and completing this administrative IT task before the business content implementation.

(24)

For more information about the system landscape in SAP Solution Manager, see the SAP Solution Manager documentation in the SAP Help Portal at

http://help.sap.com/solutionmanager SAP Solution Manager 7.0 SAP Solution Manager 7.0 EhP1 SP26 Basic Settings Solution Manager System Landscape.

Procedure

1. To maintain the system landscape in SAP Solution Manager, choose System Landscape –

SAP Solution Manager (transaction SMSY).

2. Choose System Groups and Logical Components Logical Components.

3. In the context menu of Logical Components, choose Create New Logical Components. 4. In the dialog box, create the following settings:

Field Name Entry Value

Logical Component ERP60_EHP6_ECC_SERVER_PLM

Product SAP ERP ENHANCE PACKAGE

Product Version EHP6 FOR SAP ERP 6.0

Product Instance SAP ECC Server VPack Successor

Name <Enter a name.> 5. Choose Continue.

In the left screen area, the Current System Assignments tab appears.

6. Assign your systems to the appropriate system roles. Place your cursor in the column and select the system/client combination. Specify systems for the following system roles:

Development System Evaluation System

6.2.2.2 Creating the SAP Solution Manager Project and

Template Selection

Use

You select the SAP Solution Manager template in SAP Solution Manager so that you can use the content in your implementation project.

Procedure

To select the SAP Solution Manager template, do the following:

1. In the SAP Solution Manager system, access transaction SOLAR_PROJECT_ADMIN. 2. On the Project Administration screen, select an existing implementation project.

To create a new project, proceed as follows: 1. Choose Create Project.

(25)

2. In the dialog box, make the following entries:

Project Type Solution

<Enter a name.> Implementation Project <Leave empty.> 3. Choose Continue.

4. Enter a title.

5. On the General Data tab, select the project language. 6. Save and confirm the message.

3. On the Scope tab, choose the Template Selection tab.

4. Select template IPD_XX_V02 - SAP rapid-deployment solutions – Integrated Product

Development. Expand the node to display the business scenarios it contains.

To learn about the content of a template, you can access the template description on the Template Selection tab by selecting the template name.

5. Select the Integrated Product Development scenario to copy the content into your implementation project.

6. Save your project.

If you save your project for the first time, you need to specify the enhancement context in which the project documents are to be saved in the Knowledge Warehouse.

7. Map the logical components assigned to the process steps of the selected business scenario (ERP60_EHP6_ECC_SERVER_PLM in this template) to your current system landscape. The system identifies missing logical components for product versions / instances required for the business processes.

The system may propose logical components redundantly for the mapping. To solve this issue, see SAP Note 1589864.

1. To add the logical components to your system landscape, choose Continue. The list of logical components is updated on the System Landscape tab. 2. Assign the systems in your system landscape to the logical components.

For more information about assigning logical components to a project, see SAP Help Portal at http://help.sap.com SAP Solution Manager 7.0 EHP1 SP26 SAP Solution Manager Implementing and Upgrading SAP Solutions Project Administration Create/Change Project System Landscape Tab Specify Project System Landscape

Assign Logical Components to the Project.

6.2.2.3 Adjust the Process Scope in SAP Solution Manager

You refine the solution scope to reflect your business needs and adjust the configuration settings in the systems accordingly.

In the SAP Solution Manager system, in the Business Blueprint (transaction SOLAR01), you can specify the business processes you wish to implement. You can check which processes are

(26)

mandatory or optional for the rapid deployment of SAP PLM by accessing the template description.

In the SAP Solution Manager template, all business processes are self-contained with related business content assigned on the various tabs. The nodes Master Data, Organizational Unit and

Interface Scenarios are not relevant, and we recommend deselecting these nodes to have a

better overview during the configuration later.

For more information about the business blueprint, see the SAP Solution Manager documentation on SAP Help Portal at http://help.sap.com SAP Solution Manager

SAP Solution Manager 7.0 EhP1 SP26 Implementing and Upgrading SAP

Solutions Business Blueprint.

When the business blueprint is finalized, the system configuration in the transaction SOLAR02 can start.

For more information about configuration in SAP Solution Manager, see the SAP Solution Manager documentation on SAP Help Portal at http://help.sap.com SAP Solution Manager SAP Solution Manager 7.0 EhP1 SP26 Implementing and Upgrading SAP Solutions Configuration (transaction SOLAR02) Configuration

tab page.

To navigate to the configuration guides for the relevant building blocks, proceed as follows: 1. Once your project has been created, access transaction SOLAR02. Alternatively, choose the

following navigation path from the menu bar: GoTo Project Configuration.

Your project opens on a new screen.

2. In the Configuration Structure on the left, choose the following navigation path: <Project Title>

Configuration Business Scenarios Ramp-up for Production Business Processes

3. Select Hand over Product Structure for Production and go to the Configuration tab page on the right.

On this tab page you can find and access directly the building block configuration guides for each business process.

6.2.3 Solution Builder-Based Implementation

If you have decided to implement the SAP PLM rapid-deployment solution using SAP Best Practices solution builder, proceed as described in the following sections.

6.2.3.1 Create Installation Folder for Content Activation

Use

For the scoping, personalization, and installation of the solution, you need to place the implementation content files (solution scope file and installation data files) in a specific folder.

Procedure

Create an installation data folder on a server that can be accessed from within the SAP system in which you want to install the SAP Best Practices package. Ensure that the persons who will be installing the SAP rapid-deployment solution have the necessary user rights to access this folder.

(27)

6.2.3.2 Accessing the Solution Scope Files

Use

The solution scope file contains the technical structure of the solution (scenarios, building blocks, and technical objects).

Procedure

1. To download the solution scope file, go to SAP Service Marketplace at http://service.sap.com/bp-implcontent.

2. Choose Solution files EHP6 for SAP ERP 6.0.

3. Download the following *.zip file: SOL_RDS_PLM_ERP606V2_BP_ERP606Vx.zip Note that [x] is a placeholder for the add-on version.

4. Unzip the file and copy the solution scope file for the installation of the solution into the installation data folder that you created before.

6.2.3.3 Accessing the Installation Files

Use

Installation data files are used to deploy installation settings (configuration settings and master data).

Procedure

1. To download the installation data files, go to SAP Service Marketplace at http://service.sap.com/bp-implcontent.

2. Choose the Installation data file sets EHP6 for SAP ERP 6.0.

3. Download the following *.zip file: INST_FILES_PLM_XX_BP_ERP606Vx.zip Note that [x] is a placeholder for the add-on version.

4. Unzip the file into the installation data folder you created before.

In this folder you find the installation data files (*.txt files) as well as language-specific subfolders named with a two letter language abbreviation (for example, DE).

5. Optional: Identify the second language, if available (for example, DE in addition to English), that you want to use to create for sample master data. Copy all files included in this second language folder (for example, DE) into the installation data folder and confirm to replace the existing files.

6.2.3.4 Import Solution Scope File

Prerequisite

You have copied the solution scope file (*.xml file) that is needed for the SAP PLM rapid-deployment solution into the installation data folder.

(28)

To install the SAP PLM rapid-deployment solution, upload the relevant solution scope file as follows:

1. Start the SAP Best Practices solution builder using the following navigation options: Transaction name Solution and Implementation

Transaction code /n/SMB/BBI

2. The Solution Editor screen displays all the solutions available in the system.

The solution list is empty the first time you enter the Solution Editor (if no other users have uploaded or created solutions in the system).

The application toolbar indicates the sequence of operation for end users.

SAP strongly recommends that you add the Solution Builder transaction (/SMB/BBI) to the favorites on your SAP User Menu.

3. On the Solution Builder – Solution Editor screen, choose Solution Import Solution (XML)

from the menu.

4. In the Select the Solution Scope File (XML) dialog box, enter the path to the installation directory, select the relevant solution scope file, and choose the Open pushbutton.

5. After the solution has uploaded (depending on the size of the solution, this may take a few seconds or up to one minute), a dialog box appears with information about the uploaded scenarios and building blocks. Choose the OK pushbutton to confirm.

6. Choose the Implementation Assistant pushbutton to check the result.

Result

The uploaded solution is visible in the solution list and is marked as your favorite solution.

If the path to the installation data directory is too long, you receive an error message. You may either rename directories in the path to shorten the file path, or copy the installation files to a directory that is closer to the root folder of the hard drive.

6.2.3.5 Maintain User Settings: Path to Installation Data

Use

The content of a solution is comprised of implementation content files (solution scope file and installation data files).

To simplify the procedure and avoid confusion with different sets of installation data, SAP strongly recommends that you assign the installation data directory’s path to the solution. This is done in the user settings (because path information is very often user dependent).

This is an important step for consultants that have imported multiple solutions in the SAP Best Practices solution builder.

(29)

1. On the Solution Builder – Solution Editor screen, choose Goto User Settings from the

menu.

2. On the Solution Specific tab page, select the directory where you stored your installation data files.

The solution ID of the Favorite solution is fixed. To maintain it for another solution, select another solution as a Favorite before maintaining the solution-specific part of the user settings.

3. Choose the OK pushbutton to confirm the settings.

Result

The path to the installation data directory being assigned to the solution is always set as the default entry for the particular solution.

6.2.3.6 Maintain Solution Settings: Select Languages

Use

The configuration content (Customizing) for the rapid deployment of SAP PLM is available in several languages. On solution level, you can define which languages you want to activate for language-specific Customizing.

By default, all languages supported by the solution are selected. You have to reduce the list of languages only in the following cases:

Only a subset of languages is required for your solution

Some languages, active on solution level, are not installed in your system

Procedure

1. On the Solution Builder – Solution Editor screen, select your favorite solution. 2. Choose the Change Solution pushbutton.

3. In the Change Solution dialog box and the Released Languages screen area, deselect any languages that are not relevant for your project or not installed in the ERP system (use transaction SMLT to identify the installed system languages).

Language EN always has to be active. 4. Choose the Enter pushbutton.

Result

Languages have been activated for language-specific Customizing.

6.2.3.7 Upload Installation Data

Use

This step is a prerequisite for solution implementation.

(30)

You have downloaded the installation files to the Installation Folder and uploaded the solution scope file to the solution builder.

This activation step uses the files in the installation folder. Ensure that you have uploaded the correct installation data files and that you are using the correct folder location.

Procedure

To upload the installation files, proceed as follows in the Solution Builder: 1. Go to the Solution Builder – Solution Editor screen.

2. From the menu, choose Solution Set as Favorite to set the uploaded solution as a favorite.

3. Choose the Upload Installation Data pushbutton (Ctrl+F5).

4. In the Upload Installation Data dialog box, enter the following values:

Field Name Value

Path <your directory of installation files>

All Files Select the radio button. 5. Choose Continue.

Result

The following system message should appear: Installation data have been uploaded successfully.

6.2.3.8 Implementation of Solution

6.2.3.8.1 Activating a Solution

Use

You perform the implementation of a solution in the Implementation Assistant.

The Implementation Assistant screen provides the scenario list of a solution on the left-hand side. Expanding the scenario displays the building blocks of the scenario in the correct sequence. Expanding a building block displays the implementation activities of each building block in the correct sequence.

On the right-hand side in the upper part of the screen, you see the building block repository for your solution. The lower part shows all messages and message details that are generated during checks and implementation.

The Implementation Assistant provides the following activation options: Activation in the Solution View (standard view)

All selected scenarios are installed according to the sequence listed in the

Solution/Scenario structure.

No parallel activation or individual selection of scenarios possible Recommended activation option for activation conflicts can be avoided Activation in the Scenario View

(31)

You can select individual scenarios for activation and freely define the installation sequence.

Activation in the Scenario View does not prevent parallel activation of solution content, because only the currently activated scenario is protected.

If you run automated steps in different scenarios accessing the same data, table errors and inconsistencies can occur.

Therefore, using this activation option is not recommended and is at your own risk – for example, you should make sure that only a single user is running the activation.

Procedure

To activate a solution, the following activation information must be provided: Target language

The language of text fields for system parameters that are not language dependent in a technical sense. After starting the installation, the target language cannot be changed. Folder containing installation data

It is recommended to use the already-determined folder retrieved from the user settings. A workbench and Customizing request

You can create these using the respective Create buttons at the bottom of the activation dialog box.

Other options

Skip this screen – During activation, if the system stops due to a manual task or error,

you must restart activation. This option prevents the activation dialog box from displaying again. The system uses the same settings from the first activation. To redisplay this activation option screen, you choose Display Activation Option in the context menu of the solution node.

If the Activation Options are skipped, you can make the Implementation Assistant stop the activation after the installation of each scenario and to display the activation options screen (Choose option Stop activation by the end of each Scenario)

1. Choose the Implementation Assistant button.

2. On the Implementation Assistant - Solution Editor, choose Activate.

3. Alternatively, you can select a specific scenario in the Implementation Assistant - Scenario

view for activation.

4. Specify the activation options as described above. 5. Confirm the Activation dialog box.

Result

The activation starts. Depending on the number of manual activities and possible errors during implementation, the activation may stop occasionally, waiting for manual input or troubleshooting.

Refer to the information provided with your solution for any specific information that must be considered for prerequisites or during implementation. This will also provide you with information of the expected implementation time and specific

(32)

If several people are involved in the implementation, make sure to take activation ownership (choose the Change Activation Owner button). Otherwise, the solution is locked.

6.2.3.8.2 Manual Interaction During Installation of Building

Blocks

Use

The installation procedures of the following scenarios / building blocks contain manual installation steps and / or require manual confirmation.

Procedure

If the Solution Builder stops because of a manual activity, proceed as follows:

1. Confirm the message: There is no instructional document attached to this manual task. 2. On the Navigation option screen, memorize the header of this screen. This header

information is identical to the configuration activity that has to be executed manually. 3. Open the configuration guide for this building block, which is provided in the content library

(see step-by-step guide: Deploy Train key users Content Library). Navigate to the

building block and open the configuration guide.

4. Choose the proposed navigation option, for example, Navigate to the Customizing. 5. Execute the configuration activity manually by following the instructions in the relevant

section of the configuration guide.

6. Choose the Back pushbutton (from the Customizing activity or transaction). 7. Choose the Proceed pushbutton.

8. In the Implementation Assistant – Scenario Edit View, choose the Confirm Manual Step pushbutton.

9. Enter a reason (optional) and choose the Enter pushbutton. 10. Proceed with the activation.

6.2.3.9 Processing General Errors during Installation

Use

When activation of an automated task runs into errors, activation stops at the point the error occurs. No further implementation can be done until the error is resolved.

Procedure

1. On the Implementation Assistant – Solution View screen, select a task that has a red light in the Current status column.

2. Expand the task and choose the log assigned to this task.

(33)

3. On the Error List pane, choose Display Detailed Log. This displays detailed log information about an eCATT or BC Set activation.

4. In this log information, check entries with a red light to identify the reason for the error. If the error can be resolved based on the log information, you can run the eCATT or BC Set again.

If activation fails because of locked objects, make sure that no objects are locked by any users. Then try to activate the activity again.

See the document SAP Best Practices Tools (J00_BPTools_EN.pdf) for details about the manual activation of eCATTs and BC sets. This document is part of the documentation package located in the following folder: SAP_BP BBLibrary General.

5. If the log information is not sufficient to resolve the problem, you can proceed as follows: o Execute the task manually as described in the corresponding section of the

configuration guide, or

o Open a customer message for this problem specifying component SV-RDS-PLM.

Do not delete Solution Builder scenarios once they have been activated. If you delete scenarios, the activation history and the respective logs are lost and it is not possible to find possible error reasons with tenable efforts.

In such cases, no SAP support can be provided.

6. When you have solved the problem (either executed the task manually or a solution has been provided via customer message), choose the Change pushbutton that is displayed in the Old

Status column to the right of the task.

Do not proceed with installation if the problem has not been solved. If you continue without solving the problem, severe errors might result in the subsequent installation steps that cause incalculable efforts to fix.

In such cases, no SAP support can be provided.

7. In the Confirmation dialog box, choose the OK pushbutton to manually change the status to

successful.

8. In the Information dialog box, you can enter a reason for changing the status. 9. Choose the Continue pushbutton.

The information is saved in a log. To view details for a changed task, choose the red light in the Original Status column for that task. A dialog box displays the user who performed the change, the date of the change, and the reason for the change. Choose the Continue pushbutton to close the dialog box.

Quick Guide to Implementing the SAP PLM Rapid-Deployment Solution (Based on EHP 6 for ERP 6.0 and Part of PLM 7.02) (EN)

EHP 6 for ERP 6.0

PLM 7.02

July 2012

English

Quick Guide to

Implementing the SAP

PLM Rapid-Deployment

Solution (Based on EHP 6

for ERP 6.0 and Part of

PLM 7.02) (EN)

Copyright

Icons

Typographic Conventions

Contents

Quick Guide to Implementing the SAP PLM

Rapid-Deployment Solution

1 About this Quick Guide

2 Solution Overview

3 Implementation Methodology

4 SAP System Landscape Prerequisites

(Administrator)

4.1 Required SAP Software Components

4.1.1 SAP ERP 6.0

4.1.2 SAP Solution Manager

4.2

4.3 SAP Software Component Installation Check

4.3.1 SAP ERP 6.0

Procedure

4.3.2 SAP Solution Manager

4.4 Installation

4.4.1 SAP ERP 6.0

4.4.2 SAP Solution Manager

4.4.3 Receiving the Software at the Correct SP Level

4.5 Required SAP Notes and Messages

4.6 Other Related Documentation (Optional)

5 System Preparation for SAP

Rapid-Deployment Solution Implementation

(Administrator/ Consultant)

5.1 Activate Services

Use

Procedure

Result

5.2 SAP NetWeaver Business Client

Further Information

Procedure

.

5.3 Installation of Java Runtime Environment

Procedure

5.4 SAP Product Visualization

Procedure

5.5 Define Storage Category

5.6 Installation of the SAP Best Practices Add-On

Use

Procedure

Result

5.7 Installation of the SAP Best Practices Solution

Builder

Use

Procedure

Result

5.8 General Client Settings

5.8.1 Creating User for Activation of SAP Rapid-Deployment

Solution Content

Use

Procedure

Result

5.8.2 Deselecting Activation Links in BC Sets

Procedure

5.8.3 Maximum Work Process Runtime

Use

Procedure

5.8.4 SAP Scripting

Use

Procedure

5.8.5 Set Default Timeout for HTTP and HTTPS Services

Use

Procedure

5.9 Prepare System User for Content Activation

5.9.1 SAP Software Change Registration (SSCR): Developer