ewm quick guide en de

Quick Guide for Implementing the SAP Extended Warehouse Management rapid-deployment solution

SAP EWM 7.0

March 2011

English


SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany


Copyright

© 2010 SAP AG. All rights reserved.

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

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, 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, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

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

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

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, Clear Enterprise, SAP BusinessObjects Explorer, 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 SAP France in the United States and in other countries.

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.

© SAP AG of 36


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

© SAP AG of 36


Content

1 About this Quick Guide.........................................................................................6

2 Solution Overview.................................................................................................6

3 Implementation Methodology................................................................................7

4 SAP System Requirements (Administrator)..........................................................8

4.1 SAP Software Component Installation Check.......................................................8

4.2 Required SAP Software Components...................................................................9

4.2.1 SAP EWM Software Components.........................................................................9

4.2.2 SAP R/3 4.6C (or higher ECC releases): R/3 Server...........................................10

4.2.3 SAP Solution Manager........................................................................................11

4.3 Receiving the Software at the Correct SP Level.................................................12

4.4 Required SAP Notes and Messages...................................................................12

4.5 Troubleshooting..................................................................................................13

4.6 Related Documentation.......................................................................................13

5 System preparation for SAP RDS Implementation (Administrator/ Consultant). .13

5.1 Installation of the SAP Best Practices Add-On....................................................14

5.2 Installation of the SAP Best Practices Solution Builder.......................................14

5.3 General Client Settings.......................................................................................15

5.3.1 Creating User for Activation of SAP RDS Content...............................................15

5.3.2 Deselecting Activation Links in BC Sets..............................................................17

5.3.3 Maximum Work Process Run Time.....................................................................17

5.3.4 SAP Scripting......................................................................................................18

5.4 Prepare system user for Content Activation........................................................19

5.4.1 SAP Software Change Registration (SSCR): Developer Key..............................19

5.4.2 Activation Language............................................................................................19

5.4.3 User Settings for Activation.................................................................................19

5.4.4 Deactivate Info Dialog Box on Dynpro Size Check..............................................20

5.4.5 Unicode Settings.................................................................................................20

5.4.6 Allow GUI Scripting..............................................................................................20

5.4.7 Set Decimal Notation and Date Format...............................................................21

6 Implementation of RDS Business Content (Consultant)......................................21

6.1 Installation of Language/Country-specific Content..............................................21

6.2 RDS Content Installation Variants.......................................................................22

6.2.1 Automated Implementation using SAP Best Practices solution builder...............22

6.2.1.1 Create Installation Folder for Content activation.................................................23

6.2.1.2 Import Solution Scope File..................................................................................23

6.2.1.3 Maintain User Settings: Path to Installation Data................................................24

© SAP AG of 36


6.2.1.4 Maintain User Settings: Path to Documentation..................................................25

6.2.1.5 Maintain Solution Settings: Select Languages....................................................25

6.2.1.6 Personalization of Solution..................................................................................26

6.2.1.7 Implementation of Solution..................................................................................28

6.2.1.8 Processing General Errors during Installation.....................................................30

6.2.2 Manual Implementation.......................................................................................31

6.2.3 Solution Manager Template based Implementation.............................................32

6.2.3.1 Checking the System Landscape in SAP Solution Manager...............................32

6.2.3.2 Creating the SAP Solution Manager Project.......................................................34

6.2.3.3 Selecting the SAP Solution Manager Template..................................................35

6.2.3.4 Adjust the process scope in SAP Solution Manager...........................................35

© SAP AG of 36


Quick Guide to Implementing the SAP Extended Warehouse Management rapid-deployment solution

1 About this Quick Guide

This Quick Guide helps consultants and customer project members to implement the SAP Extended Warehouse Management rapid-deployment solution. The guide focuses on the technical

Implementation aspects and usage of the SAP Solution Manager and the SAP Best Practices Solution Builder add-on. The document mentions all required steps for a successful

implementation of the SAP Extended Warehouse Management rapid-deployment solution and directs you to more detailed documentation if necessary.

The System Landscape Prerequisites section lists all system pre-requisites that have to be fulfilled by customers before the implementation of the rapid-deployment edition can start. Installation of the required systems is not part of the SAP Extended Warehouse Management rapid-deployment solution´s delivery scope.

The Preparation Activities section explains the tasks that need to be carried out specifically for the implementation of the SAP Extended Warehouse Management rapid-deployment solution.

In the Implementation section you will be guided step-by-step through the actual technical

Implementation process. What you actually implement and configure is subject to a previous scoping effort.

The SAP Extended Warehouse Management rapid-deployment solution addresses core functional needs of Warehousing. Operations. From a technical implementation perspective the content of this guide is valid for the SAP Extended Warehouse Management rapid-deployment solution.

2Solution Overview

SAP Extended Warehouse Management rapid-deployment solution:- is based on SAP EWM 7.0- provides an accelerated deployment of the required configuration settings- provides warehousing customers with an opportunity to set their basic critical

warehousing processes running in a fixed time horizon- provides preconfigured basic warehousing processes like Inbound, Outbound, Inventory

and Replenishment, Scrapping, Customer Returns- provides the sample warehouse structure and required master data to run preconfigured

processes- provides preconfiguration that is technically parameterized to adapt to unique needs of

customers for specific warehousing scenarios in a limited way

© SAP AG of 36


- targets on customers that are having the needs for mission critical warehousing processes with defined complexities

Baseline processes required in SAP ERP are expected to be running to start the SAP Extended Warehouse Management rapid-deployment solution implementation.The SAP Extended Warehouse Management rapid-deployment solution does not take care of setting up an SAP ERP system. It only integrates the existing ERP system with SAP EWM.

3Implementation Methodology

Overall project guidance is provided by a specific implementation roadmap, the Implementation Methodology for SAP Extended Warehouse Management rapid-deployment solution, which is 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 guidebooks and accelerators to ensure the quick and pragmatic implementation of

rapid-deployment solutions.

To get access to the methodology, contact SAP consulting.

SAP Extended Warehouse Management rapid-deployment solution Content Implementation Options

The SAP Extended Warehouse Management rapid-deployment solution can be implemented by integrating an existing and functional SAP ERP system with the SAP EWM system.

SAP Extended Warehouse Management rapid-deployment solution Content Implementation Variants

For the implementation of the SAP Extended Warehouse Management rapid-deployment solution the following implementation variants are offered:

Automated Implementation using SAP Best Practices solution builder

© SAP AG of 36


The highly automated version of the SAP EWM rapid-deployment solution will be available at the end of March 2011.

For details, refer to SAP EWM rapid-deployment solution-specific SAP Note 1554351.

Manual Implementation following configuration guides

SAP Solution Manager Template based Implementation

The SAP Solution Manager Template for the SAP Extended Warehouse Management rapid-deployment solution will be available early in Q2 in 2011.

4 SAP System Requirements (Administrator)

This section summarizes the prerequisites that are assumed to be delivered by the customer, that is in a phase preceding the actual implementation project.

Note that the setup of the system landscape is not part of the SAP Extended Warehouse Management rapid-deployment solution delivery scope.

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

In addition to the following information, the SAP rapid-deployment solution’s specificimplementation methodology provides an installation related checklist covering additional aspects. Prior to installing and activating the SAP Extended Warehouse Management rapid-deployment solution, the target SAP Application Server (AS) must be installed with the Support Package Stack (SPS) specified in this section, and the SAP Note as specified in detail in the SAP Notes and Messages section in this guide.

4.1 SAP Software Component Installation Check

Before the SAP Extended Warehouse Management rapid-deployment solution content implementation activities can be executed. The SAP project team performs a check of the software installation based on the requirements provided in the following steps in this guide. Based on the result, the project team advises the customer on any missing steps to be performed.

© SAP AG of 36


4.2 Required SAP Software Components

The deliverables of the SAP Extended Warehouse Management rapid-deployment solution were developed and tested in a system landscape with specific SPS levels. If the SPS level in your system is different, there may be errors during the activation. You may be able to perform the activation activities manually using the configuration guides, but errors may still occur.

Make sure that your system meets the minimum SPS level requirements. In caseyour system has an exceptional SPS level compared to the SAP Extended Warehouse Management rapid-deployment solution, issues might occur. If you need a higher SPS level in your system, for example because of additional functionality, FIRST import and activate the SAP Extended Warehouse Management rapid-deployment solution SPS levels as mentioned below, THEN upgrade your system to the current SPS level.

The support package levels relevant for the SAP Extended Warehouse Management rapid-deployment solution are listed together with the required components in the next sections.

4.2.1 SAP EWM Software Components

Before the SAP Extended Warehouse Management rapid-deployment solution can be implemented, two SAP EWM 7.0 systems (development or sandbox or quality system and production system) must be installed and updated to service pack level 09 To customize the SAP EWM back end, you need the SAP GUI for Microsoft Windows. End users access SAP SCM via their local Web browsers. SAP SCM 7.0 supports InternetExplorer 6.0, 7.0, and 8.0, and Firefox (conditionally). Additionally, SAP’s Product Availability Matrix bundles technical information on SAPComponents for quick reference. You can find it via http://service.sap.com/support→Release & Upgrade Info → Product Availability Matrix → SAP EWM 7.0.

Usually required software components and SP levels are downloaded using the MaintenanceOptimizer of SAP Solution Manager. If you need to download manually from SAP's Software Distribution Center in Service Marketplace, follow below given path:

Installationhttps://service.sap.com/swdc SAP Software Distribution Center → Download → Installations and Upgrades → browse our download catalogue → SAP Application Components → SAP EXTENDED WAREHOUSE MGMT → SAP EWM 7.0

© SAP AG of 36


Support Packages

https://service.sap.com/swdc SAP Software Distribution Center → Download → Support Packages and Patches → browse our download catalogue → SAP Application Components → SAP EXTENDED WAREHOUSE MGMT

Detailed information regarding the installation of enhancement package 4 for SAPERP 6.0 can be found in SAP Note1143022 - Installation of Enhancement Package4 on SAP ERP 6.0. As outlined in SAP Note 1064635, SPS levels for SAP ERP are synchronized throughout all enhancement package versions. Software components and add-ons not used within an enhancement pack should have the SP level assigned to the concurrent SPS of SAP ECC 6.00. Attached to note1386389 - SAP BAiO/BP: Stack Information/Explanation for UsedProducts is SAP BAiO /BP: Stack Information/Explanation for Used Products, anoverview of all software components and their support package levels combined inthe various support package stacks is given.

4.2.2 SAP ERP & SAP EWM PrerequisitesSAP Extended Warehouse Management rapid-deployment solution provides integration with the customer’s existing SAP ERP system, and it is assumed that the customer has an SAP ERP system up and running in the system landscape. Integration touch points exist for business partner master records, product master records, ERP Sales Orders, Purchase Orders ( with Logistics Execution ).

Note : As a prerequisite, always start EWM RDS implementation with a client copy from 000´ client provided as part of standard EWM 7.0 product. The pre-configuration of this rapid-deployment solution have only been validated withSAP ERP 6.0 Enhancement Packages 04. Therefore, the use of one of these ERP releases are recommended.

Business Process Minimum SAP ERP Release

SAP EWM Rapid Deployment Solutions SAP ECC 6.0 EHP 4.0 (sales & purchasing processes running with Logistics Execution)

Component Mandatory Remark

SAP Extended Warehouse Management rapid-deployment solution

SAP EWM 7.0 X Updated to SP 09

Special Instruction: Additional notes to be implemented if not in SP09 level in your EWM system:

© SAP AG of 36


Note Description Area Comments

1438837 CIF activation returns error message BRAIN009

CIF Check if implemented (relevant if BW client

active)

1498542 CIF returns error message BRAIN009

CIF Check if implemented (relevant if BW client

active)

1510817 Missing Enhancement Options for Action Profiles

All processes a lot of manual steps /Coding

1516253 Short dump REF_TYPE_CONFLICT during printing in monitor

Physical Inventory Coding correction

1550675 Physical Inventory Progress Monitor: wrong completeness


1559241 Physical Inventory: Check Already-Inventoried Objects


1523935 Dump during activation /SCWM/DLV_OUTBOUND_SIMPLE

BC-Set

All processes (not Required

Coding correction

1517482 Beleg- und Positionsarten vereinfachte Lieferungsprozesse

All Processes BC set activation- check attachment

1510636 Fehler "Parameter nicht konsistent" beim "Entladen

Complex Inbound/Outbound

Coding correction

1526300 Fehler F5 669 bei Warenausgang aus dem EWM

Complex Outbound

Coding correction

1564519 PDI: GR correction does not work for return delivery

Customer Returns Coding correction

1556355 Fehlermeldung bei Anlegen erweiterbarer BAdI-Implementierung

(not translated yet)

All Processes Coding correction

1562858 Automatische Bestellanlage beim Hinzufügen einer Position (not

translated yet)

Simple Inbound Coding correction

1550529 Determining customer and ship-to address in /SCWM/HU_SHPLABEL

Inbound/Outbound Coding correction/SMARTFORMS

(check attachment in the note)

1508900 Incorrect unit of weight for capacity check

Warehouse Order Processing

Correction

4.2.3 SAP Solution Manager

For implementing SAP Extended Warehouse Management rapid-deployment solution, SAP Solution Manager system is recommended. SAP Solution Manager in general is needed for installation and managing of maintenance certificates, Enhancement Packages and upgrades. In the context of SAP Rapid-Deployment solutions, implementation content is delivered via SAP Solution Manager templates.

© SAP AG of 36


The template content for SAP Solution Manager is tailored for the deployment of the SAP Extended Warehouse Management rapid-deployment solution. It is assumed that a productive SAP Solution Manager system (7.0 or higher) is available in theCustomer’s system landscape: if the customer is already using other SAP products (e.g. SAPERP) then the customer should already have SAP Solution Manager in the system landscape. For more information about SAP Solution Manager, see the SAP LibraryDocumentation for SAP Solution Manager at http://help.sap.com →SAP SolutionManager, or at http://service.sap.com/solutionmanager.

Component Mandatory Remark

SAP Solution Manager

SAP Solution Manager 7.0 (or higher) ABAP

Recommended If you do not wish to use SAP Solution Manager to leverage the SAP Extended Warehouse Management rapid-deployment solution, see the section RDS Content Installation Variants in this document

The implementation of the SAP Extended Warehouse Management rapid-deployment solution is based on a two-system landscape that is a combined development and quality system and a production system. If other systems are required (such as a dedicated quality assurance system), these must be planned and implemented separately, since they are not part of the SAP Extended Warehouse Management rapid-deployment solution delivery scope. It is assumed that the customer already has the SAP ERP system installed and configured; as part of implementing the SAP Extended Warehouse Management rapid-deployment solution, the SAP EWM system will be integrated with the SAP ERP system.

4.3 Receiving the Software at the Correct SP Level

For delivery of the software, an installation number and a corresponding license agreement are required. An S-USER is required to order software in the Software Catalog or download from SAP's Software Distribution Center within SAP's Service Marketplace (SAP's SWDC in SMP).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. For downloading SPSs, use the Maintenance Optimizer within your SAP Solution Manager. You can also select relevant SPs manually one-by-one via SAP's SWDC in the SMP: https://service.sap.com/swdc SAP Software Distribution Center → Download → Support Packages and Patches → browse our download catalogue → SAP Application Components → SAP ERP → SAP ERP.

Only the current Service Release (SR) is delivered to SAP customers / partners via SAP's SWDC in SMP and standard delivery (for example, Software Catalogue). If you encounter the situation that the required SPS for correct SAP BP packages activation is based on SPS level LOWER than the current SR, the request for the necessary SPS is handled via a customer message. For details, see the SAP Note 925690 - Standard Ordering Procedures for SAP Software(https://service.sap.com/sap/support/notes/925690).

© SAP AG of 36

https://service.sap.com/sap/support/notes/925690

https://service.sap.com/swdc

http://service.sap.com/solutionmanager


4.4 Required SAP Notes and Messages It may be that issues become apparent after the shipment of SAP Extended Warehouse Management rapid-deployment solution (and hence also of 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 problems that do not become apparent until after shipment.

SAP Note # Description

1554351 SAP Extended Warehouse Management rapid-deployment solution(https://service.sap.com/sap/support/notes/1554351)

All notes have to be applied to the system using the SAP Note Assistant (transaction SNOTE).

All notes mentioned below need to have the implementation status completely implemented. Note that some SAP Notes require manual action before you set them to the status completely implemented.

4.5 TroubleshootingIf errors occur during the installation process, proceed as follows:

1. Check for troubleshooting notes in the step description of the Configuration Guide.2. Check for SAP Notes on the relevant topic in the section SAP Notes in the Building Block

Configuration Guide.3. Log on to the Service Marketplace and search for problem-related SAP Notes. If the

problem persists, proceed as follows:- Only if the problem relates to the SAP Extended Warehouse Management rapid-

deployment solution pre-configuration, open a customer message with the component SV-RDS-SCM.

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

4.6 Related Documentation

The Master Guide SAP SCM 7.0 provides crucial information on the installation of SAPSCM 7.0. Read this guide thoroughly. The Security Guide SAP SCM 7.0 provides an overview of the security-relevant information that applies to SAP SCM.The Application Operations Guide SAP SCM 7.0 provides a starting point for managing your SAP solutions and keeping them up and running optimally. To access the latest version of these guides, log on to the SAP Service Marketplace(http://service.sap.com).

© SAP AG of 36



5 System preparation for SAP RDS Implementation (Administrator/ Consultant)

Before the Consultant can start with the automated SAP Extended Warehouse Management rapid-deployment solution content implementation the steps in the following chapter needs to be performed.

5.1 Installation of the SAP Best Practices Add-On

The following SAP Best Practices content add-on has to be installed to use the automated installation of the SAP Extended Warehouse Management rapid-deployment solution

Software Component

Release Version

BP-SCM-700V1 March 2011 Always use the latest available version as outlined in SAP Note1301301 (Release Strategy for SAP Best Practices Package ABAP Add-ons) (https://service.sap.com/sap/support/notes/1301301)

UseIf possible, Business Configuration Sets (BC Sets) for maintaining customizing settings and Extended Computer Aided Test Tool procedures (eCATT) for master data creation are used for SAP Best Practices. This use automates the configuration of the SAP Best Practices scenarios. BC Sets and eCATTs were delivered as so-called add-on transport files with the SAP Best Practices ADD-ON BP-SCM-700V1. Import this file into your EWM / SCM system, if you want to make use of the automated configuration.

Procedure1. Download the Add-On BP-SCM-700V1 from the Software Distribution center:

http://service.sap.com/swdc → Installations and Upgrades → Browse our Download Catalogue → SAP Rapid Deployment Solutions → SAP Extended Warehouse Management rapid-deployment solution

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

ResultBC Sets and eCATTs are now available in your SAP EWM system and can be used in combination with the SAP Best Practices Solution Builder for automated configuration of your scenarios.

5.2 Installation of the SAP Best Practices Solution Builder

The following SAP Best Practices add-ons have to be installed in order to use the automated

© SAP AG of 36



Installation of the SAP Extended Warehouse Management rapid-deployment solution

Software Component

Release Version

BP-SOLBLD 70V4 Always use the latest available version as outlined in SAP Note1301301 (Release Strategy for SAP Best Practices Package ABAP Add-ons) (https://service.sap.com/sap/support/notes/1301301)

Use Use the SAP Best Practices Solution Builder to easily install the complete SAP Best PracticesPackage or selected scenarios at minimum time. The SAP Best Practices Solution Builder is a tool that guides you step-by-step through theInstallation process directly in the system.

Procedure

1. Download the Add-On BP-SOLBLD 70V4 from the Software Distribution center:

http://service.sap.com/swdc -→ Installations and Upgrades -→ Browse our Download Catalogue -→SAP Rapid Deployment Solutions -→ SAP Extended Warehouse Management rapid-deployment solution

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

Result The Solution Builder has been installed in your SAP EWM system. The use of the Solution Builder is described in the section Installation of Business Content of this guide..

5.3 General Client Settings

5.3.1 Creating User for Activation of SAP RDS Content

Use

If you want to create a certain user to run the activation of the related SAP rapid-deployment solution scope, please consider the following: SAP Extended Warehouse Management rapid-deployment solution does not supply separate roles for customizing or setup tasks.If necessary, you can define a separate role corresponding to your individual IMG project according to the functions provided in Role Maintenance (transaction PFCG), containing all the authorizations you need to access the corresponding IMG activities required for the SAP rapid-deployment solution scope.

© SAP AG of 36


Alternatively you can use the authorization profile SAP_ALL. If this authorization does not apply to your authorization concept, you should restrict the rights of the user According to your internal authorization guidelines. Without the profile SAP_ALL, issues during the activation may occur and need to be solved. You can use the transaction SU53 to get information on the missing authorizations and extend the authorization data as necessary. Directly after activation of the SAP RDS SAP Extended Warehouse Management rapid-deployment solution content, remove the authorizations you have given to the System user that has performed the activation steps. This is for security reasons to avoid that the system user misuses the authorizations granted before. The procedure below describes how to setup a system user necessary to activate the SAP Extended Warehouse Management rapid-deployment solution specific content.

Procedure1. To carry out the activity, choosee of the following navigation options:

SAP Menu Tools Administration User Maintenance Users

Transaction Code SU01

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

3. Choose the Address tab.

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.



Password <initial password>

User type Dialog

7. Choose the Defaults tab.



Logon language EN

Decimal notation 1.234.567,89

Date format DD.MM.YYYY

© SAP AG of 36


9. Choose the Roles tab.

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

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

After you have activated the business content for your RDS, ensure that the sample and installation users adhere to your security guidelines.

11. Save your entries.

Result A user to activate SAP Extended Warehouse Management rapid-deployment solution content has been

created.

5.3.2 Deselecting Activation Links in BC Sets

We recommend that you turn off the creation of activation links. By doing this, you can significantly increase activation speed and avoid errors.

Procedure1. Run the following activity:

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 Change (Shift + F1).

4. In the Activation section, select the radio button for Do Not Create parameter.

5. Choose Enter on the information message.

6. Save your settings.

5.3.3 Maximum Work Process Run Time

UseDynamic switchable profile parameters (indicated by a flag in the check box of the parameter) have to be checked before activation. Therefore the following profile parameters must be checked and adapted.


Transaction Code RZ11

© SAP AG of 36


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

4. On the Display Profile Parameters Attributes screen, select Change values.

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

This parameter value is only needed for activation of SAP Extended Warehouse Management rapid-deployment solution as there are some processes that need to be performed in dialog and last for more than 10 minutes.Switch back to the default value after activation of SAP Extended Warehouse Management rapid-deployment solution !

5.3.4 SAP Scripting

UseeCATTs are used to automate the activation of <SAP RDS Name> configuration settings. Prior to activation, you must allow eCATT processing in the system by setting the profile parameter sapgui/user_scripting. The value for Enable or disable user scripting on the front-end must be set true.

Procedure Run the following activity:

Transaction Code RZ11

On the Maintain Profile Parameters screen, make the following entries

Field name Description User action and values

Note

Param. Name Profile parameter name sapgui/user_scripting

Choose Display.

© SAP AG of 36


On the Display Profile Parameters Attributes screen, select Change values.

On the Change Parameter Value screen, make the following entries.

Field name Description User action and values Note

New Value New Value for user scripting

TRUE Enable SAP Scripting

Choose Save.

When you save the change, the window closes and the current value of the parameter changes to TRUE. This change only becomes effective when you log on to the system again.

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

5.4 Prepare system user for Content Activation

5.4.1 SAP Software Change Registration (SSCR): Developer Key

The user ID used for activation has to be registered as 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 Extended Warehouse Management 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, the automated SAP rapid-deployment solution activation incurs errors.

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

2. On the SAP Software Change Registration (SSCR) start page, you get the detailed user documentation on how to proceed to get the SSCR developer key.

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 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.4.2 Activation Language Make sure that your logon language is always English (and NOT your local language) for all activation activities.

© SAP AG of 36

http://service.sap.com/sscr


5.4.3 User Settings for Activation

For activation, we recommend that only one User ID be used to activate the SAP Rapid-Deployment Solution. It can be a tedious procedure to change ownership of the activation of the solution.

Make sure that you only have one 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.4.4 Deactivate Info Dialog Box on Dynpro Size Check The dialog box sizing conflicts may appear which may pop up during activation has to be deactivated.

Procedure1. Log on with the user in the system.

2. Choose the first button from the right side of the Standard Tool Bar Customizing of Local Layout or type ALT + F12.

3. Select the menu item Options.

4. Choose the Options tab.

5. De-select the Enable dialog box for dynpro size check checkbox.

6. Choose the OK button at the bottom.

5.4.5 Unicode Settings

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

Procedure1. From the SAP Logon pad, select your system ID.

2. Choose the Change Item button.

3. On the System Entry Properties dialog box, choose the Code Page tab.

4. On the Encoding dropdown, select Unicode (UTF-8).

5. Choose OK.

5.4.6 Allow GUI Scripting

UsePerform this activity so that eCATTs GUI scripts can by executed with your GUI.

Procedure1. Choose the first button from the right side of the Standard Tool Bar Customizing of Local

Layout or type ALT + F12.

© SAP AG of 36


2. Select the menu item Options.

3. Choose the Scripting tab.

4. Select the Enable scripting checkbox.

5. Deselect the checkboxes Notify When a Script Attaches to a Running GUI and Notify When a Script opens a Connection.

6. Choose the OK button at the bottom.

5.4.7 Set Decimal Notation and Date Format

UsePerform this activity to set up the activation user ID.


SAP Menu System User Profile Own Data

Transaction Code SU3

2. Choose the Defaults tab.

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

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

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

6. Save your settings.

7. Log off from the system.

8. Log on to the system.

A renewed log on is to necessary since the change in the user settings only becomes effective when you log on to the system again.

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

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

6 Implementation of RDS Business Content (Consultant)

When the customer has finished with the set-up of the system landscape, the project team can start with the implementation of the rapid-deployment edition. The following chapter describes additional preparation activities that need to be carried out by the project team.

© SAP AG of 36


6.1 Installation of Language/Country-specific Content

SAP Extended Warehouse Management rapid-deployment solution content is built only in English, but only very few country-specific settings.

Country-specific settings, such as pricing and taxes are automatically configured in the SCM system via the initial download from the ERP system.

The current available version of SAP Extended Warehouse Management rapid-deployment solution is only in English; there are no separate SAP Extended Warehouse Management rapid-deployment solution versions for different countries/languages.

6.2 RDS Content Installation Variants

6.2.1 Automated Implementation using SAP Best Practices solution builder

Pre configuration of this solution is packaged as following configuration Building Blocks (BB). All technical objects required for automatic implementation such as BC sets & eCatts are bundled under these building Blocks :

BB ID Building Block Name

Y31 ERP-EWM Integration

Y32 Sample Warehouse Structure

Y33 Central Master Data

Y34 Resource Management

Y35 Inbound Process with no Packing Information from Vendor

Y36 Inbound Process with Repacking for Put away

Y37 Outbound Process Using Pick HUs as Shipping HUs

Y38 Outbound Process Using Wave, Pick HU, Packing, Staging, and Loading

Y39 Periodic Physical Inventory

Y40 Cycle Counting

© SAP AG of 36



Y41 Automatic Replenishment

Y42 Scrapping due to Best-Before Date/Shelf-Life Expiration Date

Y43 Customer Returns with Quality Inspection

6.2.1.1 Create Installation Folder for Content activation

UseThe scoping, personalization, and installation phase of the Solution Builder require solution scope and installation data files in a specific folder.

Procedure1. Create an installation data folder on a server that can be accessed from within the SAP

system where you want to install the SAP rapid-deployment solution. Ensure that the persons who will install SAP rapid-deployment solution will have the necessary user rights to access this folder.

2. The solution scope file can be found as attachment EWM_Scope_File_EN_DE.zip of the RDS EWM release note 1554351 (for details on the current note number, see the above section Required SAP Notes and Messages).

3. Unpack the file EWM_Scope_File_EN_DE.zip and copy the solution scope file (*.xml file) that is needed for the SAP rapid-deployment solution installation into the installation data folder created in step 1.

4. The installation data files can be found as attachment EWMData_VariantFile_EN_DE.zip of the SAP RDS release note 1554351.

5. Unpack the file EWMData_VariantFile_EN_DE.zip into the installation data folder created in step 1. After doing so, you will find the installation data files (*.txt files)

6.2.1.2 Import Solution Scope File

The relevant solution scope file (*.xml file), that is needed for the SAP Extended Warehouse Management rapid-deployment solution, has been copied into the installation data directory (like described in chapter Create Installation Folder for the SAP Rapid Deployment Solution Implementation Installation Files and Scope File).

ProcedureTo install the SAP Extended Warehouse Management rapid-deployment solution, upload the relevant solution scope file as follows:

1. Start the SAP Best Practices Solution Builder

Procedure1. To start the Solution Builder, use one of the following navigation options:

Transaction name Solution and Implementation

Transaction code /n/SMB/BBI

© SAP AG of 36


2. The Solution Editor screen displays, listing all 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 button bar indicates the sequence of operation for end-users.

We strongly recommend adding the transaction for the Solution Builder (/SMB/BBI) to the favorites of your SAP user menu.

2. In the Solution Builder – Solution Editor screen, choose Solution → Import → Solution (XML) from the menu.

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

4. Choosee of the following Solution Scope files:

RDS_EWM.xml

5. After the solution is uploaded (depending on the size of the solution a few seconds up to one minute), an information box about the uploaded scenarios and building blocks is displayed. Choose OK to confirm.

ResultThe 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, the system will display an error message. If you receive this error message, either rename directories in the path to shorten the file path, or copy the installation files to a directory being closer to the root folder of the hard drive.

6.2.1.3 Maintain User Settings: Path to Installation Data

UseThe solution definition (as uploaded as XML file) and the installation data define the solution content, that will be implemented.

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

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

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

menu.

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

© SAP AG of 36


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. If you want to perform the activation using Installation Data stored on the local drive, please check the checkbox 'Allow Activation with External Data'. Or you can perform the activation using the Installation Data uploaded to the Solution Builder. (Please see the Upload Installation Data section below)

4. Choose OK to confirm the settings.

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

6.2.1.4 Maintain User Settings: Path to Documentation

UseThis activity sets the document path for information that may be useful during activation so that users can find details from the SAP Help Portal about the scenario being activated.


Transaction Code /n/SMB/BBI

2. From the menu, choose Goto User Settings.

3. Choose tab External Documents.

4. Choose button Display <→ Change.

5. Choose the Insert Row button.

6. Enter the following value:

Parameter Value

% EWM_DOCU % path to directory …\EWM\BBLibrary\Documentation of the documentation downloaded

7. Choose Save.

8. Choose Back.

6.2.1.5 Maintain Solution Settings: Select Languages

UseThe configuration content (customizing) of SAP Extended Warehouse Management rapid-deployment solution is provided in several languages. On solution level, you can define which languages will be activated for language-specific customizing.

In the default settings, all languages supported by SAP Extended Warehouse Management rapid-deployment 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

© SAP AG of 36


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

Procedure1. On the Solution Builder – Solution Editor screen select your favorite solution.

2. Choose button Change Solution.

3. In dialog box Change Solution and screen area Released Languages, deselect those languages, which are not relevant for your project or which are not installed in the EWM system (use transaction SMLT to identify the installed system languages). Language EN always has to be active. ( current version of RDS is only in English)

4. Choose Enter.

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

6.2.1.6 Personalization of Solution6.2.1.6.1 Personalize your Solution

Use

Personalization is mandatory for SAP EWM RDS.Don’t skip this section !!!

The EWM RDS does not use the generic personalization functionality provided in the Solution Builder because EWM has a special Organizational Units setup. To personalize your solution, it's necessary to change the values within the TDC variant files.

Note: TDC variant files are files that store Organizational Unit values and all other variant files will refer to these TDC variant files to get Organizational Unit values during activation. As a result, the Organizational Unit value can be personalized and the maintenance effort is minimized.

For the EWM RDS, please see the table below for all TDC variant files.

TDC variant file name Comments

SMB99_GENERAL_DATA_D00_J02.TXT General data including country code, language key, fiscal year etc.

SMB99_ACTIVITY_AREA_DW4_J01.TXT Activity Area

SMB99_BIN_ACC_TYPE_DW3_J01.TXT Bin Access Type

SMB99_INVENTORY_AREA_DW7_J01.TXT Inventory Area

SMB99_MATERIAL_MASTER_D42_J30.TXT Material Master Number

SMB99_PACK_MAT_TYPES_D34_J04.TXT Packaging Material Type

SMB99_STAGING_AREA_DW5_J01.TXT Staging Area

SMB99_STOR_BIN_TYPE_DW2_J01.TXT Storage Bin Type

SMB99_STORAGE_SECTION_DW1_J01.TXT Storage Section

SMB99_STORAGE_TYPE_D25_J02.TXT Storage Type

SMB99_WAREHOUSE_D24_J02.TXT Warehouse Number

SMB99_WAREHOUSE_DOOR_DW6_J01.TXT Warehouse Door

© SAP AG of 36


TDC variant file name Comments

SMB99_WORK_CENTER_D82_DA0.TXT Work Center

These TDC files can be found included in the installation data and if you have the requirement to personalize the Organizational Unit values, first change the values in the TDC files before uploading the installation data.

6.2.1.6.2 Upload Installation Data

Prerequisites

The installation files have been downloaded to the local directory you created in step Create

Installation Folder for the SAP Extended Warehouse Management rapid-deployment solution Installation Files and Scope File.

The Solution Scope file has been uploaded into the EWM system.

Use

This step is the prerequisite for the personalization of the default delivered settings for theImplementation of a solution. If you have the requirement to personalize the Organizational Unit values, first change the values in the TDC files before uploading the installation data.In addition, the upload allows you to review the installation data for the tasks in the Building Block Builder for better transparency, troubleshooting, or to maintain installation data and run the activation much faster than using external Installation Data. The step activating a solution is independent of the uploading the installation data step. The activation step uses the files in the installation data folder on the presentation server, to ensure that you have uploaded the correct installation data files and been pointed to the correct folder location.

ProcedureTo upload the installation files, proceed as follows in the Solution Builder:

1. Go to view Solution Builder – Solution Editor.

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

3. Choose button Upload Installation Data (Ctrl+F5).

4. In dialog box Upload Installation Data, maintain the following values, then choose Continue:

Field Name Value

Path <your directory of installation files>

Choose all files

© SAP AG of 36


Result

The Installation data upload step has been completed (with or without personalization )

6.2.1.7 Implementation of Solution6.2.1.7.1 Activating a Solution

UseThe implementation of a solution is performed in the Implementation Assistant.

The Implementation Assistant provides two activation options:

Activation in the Solution View (standard view)

o All selected scenarios will be installed according to the sequence listed in the Solution/Scenario structure.

o No parallel activation or individual selection of scenarios possible.

o Recommended Activation Option because activation conflicts will be avoided.

Activation in the Scenario View

o Scenarios can be individually selected for activation and the installation sequence can be freely defined.

Activation in the Scenario View will 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.

The Implementation Assistant screen provides the scenario list of a solution on the left-hand side. Expanding the Scenario shows the Building Blocks of the Scenario in the correct sequence.

Expanding a Building Block shows 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.

ProcedureTo 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 already-determined folder retrieved from the user settings). If you have uploaded the Installation Data into the

© SAP AG of 36


Solution Builder, you can perform the activation without specifying the folder path. You can also check the checkbox 'Use External Data' and specify the folder path to perform the activation with Installation Data stored on your local drive (in the user settings for the solution, you need to check the checkbox 'Allow Activation with External Data'. Please refer to the Maintain User Settings: Path to Installation Data in previous section).

A workbench and customizing request (these can be created using the respective create buttons at the bottom of the activation dialog box)

Other options

o 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 can right-choose the solution node, and choose Display Activation Option.

o 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 button.

2. In the Implementation Assistant - Solution view choose the button.

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.

ResultThe 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 troubleshooting procedures.

If several people are involved in the implementation, make sure to take activation

ownership (choose the button). Otherwise, the solution is locked.

6.2.1.7.2 Manual interaction during Installation of Building Blocks

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

ProcedureIf the Solution Builder stops because of a manual activity please proceed as follows:

© SAP AG of 36


1. Choose the ‘go to transaction’ button to access the transaction.2. Follow the instructions in the popup document window.3. Execute the required activity steps manually by following the instruction of the related

section in the popup document window.4. After executing the required steps, Choose Back to leave the transaction.5. Choose Proceed.6. In the Implementation Assistant, choose Confirm Manual Step.7. Enter a reason (optional) and choose Enter.8. Proceed with the activation.

6.2.1.8 Processing General Errors during Installation

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

Procedure1. 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 that is assigned to this task. Detailed information about the error is displayed in the Error List pane.

3. In the Error List pane choose Display Detailed Log. The detailed log information about an eCATT or BC Set activation is displayed.

4. In this log information, check entries with a red light to identify the reason for the error.

If the error can be solved based on the log information, you can run the eCATT or BC Set again.

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

See the document SAP Best Practices Tools for details about the manual activation of eCATTs and BC Sets. The document can be found in the documentation in the area Technical Information Tools & Concepts.

5. If the log information is not sufficient to solve the problem you can proceed as follows:

a. Execute the task manually: use the description of the related section in the Configuration Guide for executing the task,

or

b. Open a customer message for this problem specifying the component SV-RDS-CRM.

© SAP AG of 36


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 button 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. On the Confirmation dialog box, choose OK to manually change the status to successful.

8. On the Information dialog box, you can enter a reason for changing the status.

9. Choose Continue.

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 Continue to close the dialog box.

10. Choose Activate to continue with the installation.

6.2.2 Manual Implementation

If you have decided to implement SAP Extended Warehouse Management rapid-deployment solution, consultant implements the configuration guides in the sequence shown below. The configuration guides can be found in the SAP Extended Warehouse Management rapid-deployment solution content library.

Building Blocks for SAP Extended Warehouse Management rapid-deployment solution


Y31 ERP-EWM Integration

Y32 Sample Warehouse Structure

Y33 Central Master Data

Y34 Resource Management

© SAP AG of 36



Y35 Inbound Process with no Packing Information from Vendor

Y36 Inbound Process with Repacking for Put away

Y37 Outbound Process Using Pick HUs as Shipping HUs

Y38 Outbound Process Using Wave, Pick HU, Packing, Staging, and Loading

Y39 Periodic Physical Inventory

Y40 Cycle Counting

Y41 Automatic Replenishment

Y42 Scrapping due to Best-Before Date/Shelf-Life Expiration Date

Y43 Customer Returns with Quality Inspection

6.2.3 Solution Manager Template based Implementation 6.2.3.1 Checking the System Landscape in SAP Solution

ManagerSAP Extended Warehouse management rapid-deployment solution is designed for a specific system landscape that is represented by the logical components in the Solution Manager Template.

By mapping the logical components to the actual physical systems in the landscape, it enables you to configure the systems directly via the SAP Solution Manager tool.

You can also check and maintain the system landscape during the template selection. However, we recommend maintaining the system landscape before to the template selection, thereby completing this administrative IT task before starting the business-driven content implementation.

To maintain the system landscape in SAP Solution Manager tool, access the SAP Solution Manager Easy Access menu and choose System Landscape (SMSY).

1. Choose System Groups and Logical Components.

2. Open Logical Components → SAP SCM → SCM Application Server ABAP.

3. Right-choose SCM Application Server ABAP and choose Create New Logical

Components.

4. Enter the following values:

© SAP AG of 36


Logical Component Product in Template

Product Version Product Instance

Name

1 Z_SCM_EWM_70

_<System

ID>_<client>

SAP

SCM

SAP SCM 7.0 SCM

Application

Server ABAP

<Choose a

name>

2 Z_SCM_EWM_70

<System

ID>_<client>

SAP

SCM

SAP SCM 7.0 SCM

Application

Server ABAP

<Choose a

name>

For SAP Extended Warehouse Management rapid-deployment solution, peform the steps 5-7

5. Open Logical Components → SAP ERP ENHANCE PACKAGE → SAP ECC Server V Pack successor

6. Right-choose SAP ECC Server VPack successor and choose Create New Logical Components.

7. Enter the following values:

Logical Component Product in Template

Product Version Product Instance

Name

1 Z_ECC_SNC_604

_<System ID>_<client>

SAP ERP

Enhance

ment

EHP 4 for SAP ERP 6.0 SAP ECC

Server

VPack

Successor

<Choose a

name>

2 Z_ECC_SNC_604

<System ID>_000

SAP ERP

Enhance

ment

EHP 4 for SAP ERP 6.0 SAP ECC

Server

VPack

Successor

<Choose a

name>

8. In the table on the right-hand side assign your test system and client in the column Development System and in the column Evaluation System.

Technically, there are no restrictions regarding the use of SAP IT Service Desk Operation rapid-deployment edition with deviating SAP ERP release levels, as the SAP ERP part of the SAP IT Service Desk Operation rapid-deployment solution installation is performed manually without eCATTs or BC Sets.

However, the SAP IT Service Desk Operation rapid-deployment solution documentation is only provided for the recommended SAP ERP release levels.

For more information on the system landscape in SAP Solution Manager, see the SAP Solution Manager documentation in the SAP Help Portal at http://help.sap.com →

© SAP AG of 36

http://help.sap.com/

http://help.sap.com/saphelp_smehp1/helpdata/en/45/59dccac2091deae10000000a155369/frameset.htm


SAP Solution Manager → SAP Solution Manager 7.0 EhP1 SP23 → Basic Settings → Solution Manager System Landscape.

6.2.3.2 Creating the SAP Solution Manager ProjectCreate a project to organize you work in SAP Solution Manager.

To create a project, perform the following steps:

1. In the SAP Solution Manager Easy Access menu, choose Project Administration (transaction SOLAR_PROJECT_ADMIN)

2. Create a new project and enter the following values:

Project Typ Solution

<Enter a name> Implementation Project <leave empty>

3. Choose Ok.

4. On the next screen enter a title.

5. Choose a project language.

6. Save und confirm the message.

7. When a pop-up box appears map the logical components of the template to the existing logical components in the system (which you created in chapter 5.1).

8. Choose the tab System Landscape and assign your new logical components on the Systems tab.If you use an ERP release lower than ECC 6.0 EHP 4, assign your logical components which you created in chapter 5.1 as well.

For more information refer to the SAP Solution Manager documentation in the SAP Help Portal at http://help.sap.com → SAP Solution Manager → SAP Solution Manager 7.0 EhP1 SP23 → Implementing and Upgrading SAP Solutions → Project Administration.

SAP Extended Warehouse Management rapid-deployment solution comprises the integration with SAP ERP and the template contains both EWM and ERP related configuration information. On the ERP side the template’s content has only been validated with SAP ECC 6.0 EHP4. In case you are using an SAP ERP release lower than SAP ECC 6.0 EHP4 and want to leverage the template’s ERP content, you may follow the steps below as a workaround solution:

Choose the project which you created in the step above. Open Business Scenarios → RDS SCM Extended Warehouse Management →

Business Processes Mark the entry in the Configuration Structure. Check that the transaction is in display mode, otherwise change to display mode. Choose Edit → Replace Log. Comp. from the menu bar. In the pop-up enter the logical component for SAP ECC 6.0 EHP 4 in the field

logical component to be replaced. Enter your actual R/3 / ERP logical component in the field Replace with Logical Component.

Choose Save. Confirm the warning.

6.2.3.3 Selecting the SAP Solution Manager TemplateTemplates in SAP Solution Manager assist you in performing predefined implementation projects. The template specific to the SAP Extended Warehouse Management rapid-deployment solution contains the content for the ‘default’ implementation of the SAP Extended Warehouse Management rapid-deployment solution.

To select the template, carry out the following steps in transaction SOLAR_PROJECT_ADMIN:

1. Navigate to Scope tab

© SAP AG of 36

http://help.sap.com/saphelp_smehp1/helpdata/en/c7/b6dd3ae2b1f745e10000000a114084/frameset.htm



2. Select Template Selection view

3. Search for the template

RDS for SAP Extended Warehouse Management

o (technical ID:RDS_EWM)

4. To select the template, mark the checkbox next to the relevant template.

5. Save your project.

6. In the pop-up window, check if your system landscape fits to the required system landscape of the template. If the systems in your landscape are not maintained completely, in the Logical Component column, choose the F4 help for guidance in selecting the correct logical component. For more information, see chapter 5.1 Checking the System Landscape in SAP Solution Manager.

For more information on the system landscape in SAP Solution Manager, see the SAP Solution Manager documentation in the SAP Help Portal at http://help.sap.com → SAP Solution Manager → SAP Solution Manager 7.0 EhP1 SP23 Language English → Implementing and Upgrading SAP Solutions → Project Administration → Create/Change Project → Specify Scope.

7. On the System Landscape tab, make sure the required system landscape for the selected template is assigned to your project.

For more information about using templates in a project, see the SAP Solution Manager documentation in the SAP Help Portal at http://help.sap.com → SAP Solution Manager → SAP Solution Manager 7.0 EhP1 SP23 →Implementing and Upgrading SAP Solutions → Roadmap and Using Templates.

6.2.3.4 Adjust the process scope in SAP Solution Manager In the subsequent steps you will adjust the scope of the solution where possible to fit business goals, and adjust the configuration settings in the systems accordingly.

In SAP Solution Manager, adjust the scope of the business processes you would like to implement. In the SAP Easy Access menu, choose Business Blueprint (transaction SOLAR01). For more information on the SAP CRM rapid-deployment edition’s scope refer to the template description.

In the template all business processes (scenarios) are self-contained, i.e. have all related content assigned. Therefore you do not need to select ‘master data’ or ‘organizational unit’ nodes or ‘interface scenarios’ in the blueprint structure. We recommend to deselect these nodes to have a better overview during the configuration step later (transaction SOLAR02).

In transaction SOLAR01, you can also access the Template Description to check which processes are mandatory/optional for the rapid-deployment edition.

To access the template description, in the structure on the left, select the column Templates. Then the system displays the name of the Template selected for the project in the structure (if the template name is not shown scroll to the right until you can see the Templates column). By chooseing on the template name displayed you can access the template description.

For more information about Business Blueprints in SAP Solution Manager, see the SAP Solution Manager documentation in the SAP Help Portal at http://help.sap.com → SAP Solution Manager → SAP Solution Manager 7.0 EhP1 SP23 → Implementing and Upgrading SAP Solutions → Business Blueprint.

© SAP AG of 36


http://help.sap.com/saphelp_smehp1/helpdata/en/45/f6da633a292312e10000000a11466f/frameset.htm


http://help.sap.com/saphelp_smehp1/helpdata/en/57/92f63aad7e3014e10000000a11402f/frameset.htm


http://help.sap.com/saphelp_smehp1/helpdata/en/45/59dccac2091deae10000000a155369/frameset.htm