rds ewm ewm90v4 quick guide en xx

7/21/2019 Rds Ewm Ewm90v4 Quick Guide en Xx

http://slidepdf.com/reader/full/rds-ewm-ewm90v4-quick-guide-en-xx 1/38

SAP EWM 9.0

October 2013

English

Quick Guide to Implementing

SAP Extended WarehouseManagement rapid-deploymentsolution V4.90 (XX)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany



SAP Best Practices Quick Guide to Implementing the SAP EWM rapid-deployment solution V4.90

© SAP AG of 38

Copyright© 2013 SAP AG or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without theexpress 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 componentsof other software vendors.

National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informationalpurposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errorsor omissions with respect to the materials. The only warranties for SAP Group products and services arethose that are set forth in the express warranty statements accompanying such products and services, ifany. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and other countries. Please seehttp://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark informationand notices.




© SAP AG of 38

Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style DescriptionExample text Words or characters that appear on the screen. These include field

names, screen titles, pushbuttons as well as menu names, paths andoptions.

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 keywords of a programming language, when surrounded by body text, forexample, 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 asnames 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 thesystem exactly as they appear in the documentation.

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




© SAP AG of 38

Contents

1

Solution Overview and Implementation Options ................................................... 6

1.1

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

1.2

Implementation Options ......................................................................................... 6

2

System Setup & Preparation - Administrator ......................................................... 7

2.1

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

2.2

Check SAP EWM 9.0 Deployment Option ............................................................ 8

2.3

Release and Support Package Level .................................................................... 8

2.4

Required Product Versions and Software Components ........................................ 8

2.5

SAP Frontend Components................................................................................... 9

2.6 SAP Solution Manager and SAP Solution Manager Content Add-on ................... 9

2.6.1 Preparation of Logical Components Used in SAP Solution ManagerImplementation Project ......................................................................................... 10

2.7 SAP Best Practices Add-on and SAP Best Practices Solution Builder Add-on .. 10

2.8

General Client Settings ........................................................................................ 12

2.9 SAP Enterprise Extensions Sets and Enterprise Business Functions ................ 13

2.9.1 Activating Business Functions in SAP ERP.......................................................... 14

2.9.2 Activating Business Functions in SAP EWM ........................................................ 14

2.10 SAP Notes and Messages................................................................................... 14

2.10.1 SAP Notes in SAP EWM ....................................................................................... 14

2.11 Unicode Settings ................................................................................................. 15

2.12 Creating User for Activation of SAP Best Practices Content .............................. 15

2.13 Setting the Maximum Work Process Run Time................................................... 17

2.14

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

2.15

Setting Default Timeout for HTTP and HTTPS Services .................................... 18

2.16

Creating Transport Requests for Activation ........................................................ 19

2.17

Create RFC Destination for Remote Deployment of SAP ERP Configuration andSample Master Data ............................................................................................ 20

2.17.1 Create Trusted RFC in SAP ERP ......................................................................... 20

2.17.2 Create RFC Destination in SAP EWM .................................................................. 20

3 Preparation Activities - Activation Consultant ...................................................... 22

3.1 Initial Check of System Readiness ...................................................................... 22

3.2 SAP Software Change Registration (SSCR): Developer Key ............................. 22

3.3 User Settings for Activation ................................................................................. 22

3.3.1 Check/Set Decimal Notation and Date Format ..................................................... 23

3.3.2 Deactivate Info Dialog Box on Dynpro Size Check .............................................. 23

3.4 Activation Language ............................................................................................ 24

3.5 Check Note 1869426 ........................................................................................... 24

4 Implementation – Activation Consultant .............................................................. 24

4.1 Prerequisite: SAP Best Practices US Baseline ................................................... 24

4.2 Manual Implementation ....................................................................................... 25

4.3 Activation of Business Content / Scenarios with Solution Builder ....................... 25

4.3.1 Allow GUI Scripting ............................................................................................... 26

4.3.2 Getting the Business Content for Activation ......................................................... 26

4.3.2.1

Creating Folders for the Solution Scope and Installation Data Files .................... 26

4.3.2.2

Getting the Solution Scope Files .......................................................................... 27

4.3.2.3

Getting the Installation Data Files ......................................................................... 27




© SAP AG of 38

4.3.3 Activation of Scenarios ......................................................................................... 27

4.3.3.1 Import the Solution File ......................................................................................... 28

4.3.4 Assigning RFC Destinations to Target Systems ................................................... 28

4.3.5

Set Documentation Path for Solution Builder ....................................................... 29

4.3.6

Scope Your Solution ............................................................................................. 29

4.3.6.1

Upload the Installation Data .................................................................................. 30

4.3.6.2

Select Languages ................................................................................................. 30

4.3.6.3

Personalize the Solution ....................................................................................... 31

4.3.6.4

Starting Activation ................................................................................................. 31

4.3.7

Manual Interaction and Error Handling During Activation ..................................... 34

5

Error Handling: Installation Errors during Activation ........................................... 34

5.1

Error Occurs During Activation of Automated Task ............................................ 35

6 Evaluate Business Content / Processes ............................................................. 36

7 Troubleshooting ................................................................................................... 36

8 Security Aspects .................................................................................................. 37

8.1

General Security Guidelines ................................................................................ 37

8.2 Roles Overview ................................................................................................... 37

8.3 User Administration and Authentication .............................................................. 37

8.4 RFC Destinations ................................................................................................ 38

9 Related Documentation ....................................................................................... 38




© SAP AG of 38

Quick Guide to Implementing SAP ExtendedWarehouse Management rapid-deploymentsolution V4.90

PurposeThis Quick Guide helps consultants and customer project members implementing the SAPExtended Warehouse Management rapid-deployment solution.

The guide focuses on the technical implementation aspects and usage of the SAP SolutionManager and the SAP Best Practices Solution Builder. The document mentions all requiredsteps for a successful implementation of the rapid-deployment solution (RDS) and directs youto more detailed documentation if necessary.

The guides has following major sections:

The Implementat ion Opt ions section describes which options you have to implement the

solution.The System Setup & Preparat ion - Administ rator section lists all system prerequisites thathave to be fulfilled by customers before the implementation of the rapid-deployment solutioncan start.

The next section explains preparation activities for the activation consultant (PreparationAct iv i t ies - Act ivat ion Consul tant ).

Section Implementat ion – Act ivat ion Consul tant describes how to implement the solution,dependent on which implementation option you have decided for. You will be guided step-by-stepthrough the actual technical implementation process.

Further sections provide details on security aspects and troubleshooting hints.

1 Solution Overview and ImplementationOptions

1.1 Solution Overview

The SAP Extended Warehouse Management rapid-deployment solution V4.90:

is based on SAP EWM 9.0

targets at customers needing mission critical warehousing processes with anadvanced degree of complexity

provides an accelerated deployment of the required configuration settings

provides warehousing customers with an opportunity to set their basic criticalwarehousing processes running in a fixed time horizon

For an overview of the SAP rapid-deployment solution, refer to the Solution Details Presentation in the step-by-step guide (phase Start: Prepare Project ).

1.2 Implementation Options

The SAP Extended Warehouse Management rapid-deployment solution V4.90 is designed

to be implemented on a SAP EWM client which is a copy of client 000 and contains

all SAP EWM standard customizing




© SAP AG of 38

to be integrated with a SAP ERP based on SAP Best Practices US baseline for SAPERP 6.06

For this use case, an RDS fixed price service is offered.

The SAP Extended Warehouse Management V4.90 provides some additional sample master

data and required preconfiguration on top of SAP ERP BP US baseline, in order to run allsupported scenarios integrated between SAP ERP and SAP EWM. The solution does NOTcontain documentation to be used for implementing the preconfigured scenarios against acustomer specific SAP ERP. Basically your SAP ERP system needs to comply with all settingsdescribed in configuration guide EW1 Basic Settings and Master Data in SAP ERP . In case you

are using different settings and your own master data, all related settings in SAP ERP and SAPEWM need to be adjusted to your SAP ERP settings and master data. Get in touch with your SAPconsultant to discuss this use case and related additional efforts.

Solution implementation can be done

Manually, just using the configuration guides, following the order of guides described inthe prerequisite matrix

See chapter ‘Manual Implementation ’ Almost fully automated via Solution Builder (some steps remain manual)

See chapter ‘ Activation of Business Content / Scenarios with Solution Builder ’.

In both cases, SAP recommends documenting the project in Solution Manager

See chapter ‘SAP Solution Manager and SAP Solution Manager Content Add-on’

Consider following notes before you decide for an implementation option.

Automated deployment is recommended only if you are implementing the rapid-deploymentsolution in a sandbox environment, where your SAP ERP and SAP EWM system were justinstalled, and SAP Best Practice US baseline was just implemented on SAP ERP, and bothsystems remained untouched since then. The SAP EWM rapid-deployment solution contains

pre-configuration on SAP ERP and SAP EWM, which can be deployed automatically. Bothparts (SAP ERP and SAP EWM part), have to be deployed from Solution Builder in SAP EWMsystem. Nevertheless, for automated deployment of the ERP part, you still need SolutionBuilder installed on SAP ERP. You need Solution Builder on SAP ERP also for installation ofSAP Best Practices US baseline.

We recommend manual implementation if you want to implement the rapid-deploymentsolution against an already existing SAP ERP system, which does not have SAP Best PracticeUS baseline, or the SAP Best Practice US baseline shall be significantly adjusted to yourneeds after implementation. Consider the hints given in sections above and get in touch withyour SAP consultant to discuss additional steps and effort. Automated deployment would bepossible also in this context, but just under certain pre-conditions and risk evaluation upfront.Get in touch with your SAP consultant to evaluate this option.

2 System Setup & Preparation - Administ ratorThis chapter 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 rapid-deploymentsolution delivery scope.

The customer needs to provide the system landscape, that is, install the required softwarecomponents, to enable the project team to implement and configure the scope of the RDS.During this phase, SAP provides advice on aspects of the system landscape and the

components required.




© SAP AG of 38

In addition to the following information, the SAP rapid-deployment solution’s specificimplementation methodology provides an installation related checklist covering additionalrequirements.

2.1 SAP Software Component Installation CheckBefore the content implementation activities can be executed, the SAP project team performsa check of the software installation based on the requirements provided in the following stepsof this guide. Based on the results, the project team advises the customer on any missingsteps to be performed.

The SAP EWM rapid-deployment solution requires that the SAP EWM system is integratedwith the SAP ERP system. It is assumed that the customer already has the SAP ERP systeminstalled and configured.

2.2 Check SAP EWM 9.0 Deployment OptionThe rapid deployment solution is available for several SAP EWM deployment options.

Check the latest version of the software requirements document for the rapid-deployment solutionand decide which option applies in your case. The document also contains the information aboutthe required support packages. The software requirements document can be found in the step-by-step guide Phase Discover: Communicate the Scope.

2.3 Release and Support Package LevelThe deliverables of SAP Best Practices packages were developed and tested in a systemlandscape with specific release and support package (SPS) level. If the SPS level in your systemis different, there may be errors during the activation. You may be able to perform the activationactivities 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 Best Practicesrequirements, only limited support can be provided.

If you need a higher SPS level in your system, for example, because of additionalfunctionality, first import and activate the SAP Best Practices package on the SPSlevels as mentioned below, then update your system to the target SPS level.

2.4 Required Product Versions and SoftwareComponents

Refer to the Software Requirements document which you find in the step-by-step guide (phaseStart: Confirm Installation).

Receiving the Software at the Correct SP Level

For delivery of the software, an installation number and a corresponding license agreement arerequired. An S-USER is required to order software in the Software Catalog or download from theSAP Software Download Center (SWDC) on SAP Service Marketplace (SMP). You can onlyorder unrestricted SAP software. Contact the SAP contract department to ask for a physicalshipment or create a customer message on component XX-SER-GEN-CONTR.

For downloading SPSs, use the Maintenance Optimizer in your SAP Solution Manager system.

You can also select relevant SPSs manually one-by-one via the SWDC on SAP ServiceMarketplace:




© SAP AG of 38

https://service.sap.com/swdc Support Packages and Patches A-Z Index

Only the current Service Release (SR) is delivered to SAP customers/partners via theSWDC on SMP and standard delivery (for example, the Software Catalogue). If youencounter the situation that the required SPS for correct SAP BP packages activation

is based on a SPS level LOWER than the current Service Release, the request forthe necessary SPS is handled by a customer message. For details, see SAP Note925690 Standard Ordering Procedures for SAP Software.

2.5 SAP Frontend ComponentsOnly SAPGUI based transactions are used in the package.

Ensure that you have installed the latest SAP GUI frontend components.

The following download path below leads you to an overview on how to install SAP frontendcomponents and how to apply patches. On the navigation level SAP Frontend Components, youcan select the SAP frontend components depending on your requirements.

To download the SAP frontend components, go to the Software Distribution Center (SWDC) onthe SAP Service Marketplace:

https://service.sap.com/swdc , Software Downloads SAP Software Download Center

Support Packages and Patches Browse our Download Catalog SAP FrontendComponents

Using the latest SAGUI version is important for correct execution of eCatts duringautomated deployment of the package. If you use an old SAPGUI version, eCattsmay fail and you have to maintain sample master data or configuration manually.

2.6 SAP Solution Manager and SAP Solution ManagerContent Add-on

For the implementation of the solution package, a SAP Solution Manager system isrecommended. SAP Solution Manager in general is needed for installation and managing ofmaintenance certificates, Enhancement Packages and upgrades. In the context of SAP Rapid-Deployment solutions, implementation content is delivered via SAP Solution Manager templates.

It is assumed that a productive SAP Solution Manager system is available in the customer’ssystem landscape: if the customer is already using other SAP products (for example, SAP ERP)SAP Solution Manager should already be present in the system landscape.

Import the following content Add-on corresponding to the SAP Solution Manager product versionin place:

SoftwareComponent

Product Version SP Level Description

ST SAP Solution Manager7.0 EnhancementPackage 1

OrSAP Solution Manager

SP18 or higher

In case the SP is below24, see SAP Note1579267.

https://service.sap.com/swdc


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










© SAP AG of 38

7.1

Or

SAP Solution Manager7.1 on HANA (ST 712)

SP01 or higher

SP00 or higher

ST-RDS 100 Always latest SP level This add-on containsSAP Solution Managercontent. See also SAPNotes 1686668, 1726649.

For more information about SAP Solution Manager (including system administrationand implementation aspects described in chapters below), see the SAP Librarydocumentation for SAP Solution Manager at http://help.sap.com → ApplicationLifecycle Management → SAP Solution Manager , or athttp://service.sap.com/solutionmanager .

The latest available ST-RDS 100 content support package has to be downloaded from the SAPSoftware Download Center on SAP Service Marketplace (http://service.sap.com/swdc

Installation and Upgrades Browse our Download Catalog SAP Rapid Deployment solutions

SAP Solution Manager Implementation Content ST-RDS 100 ).

2.6.1 Preparation of Logical Components Used inSAP Solution Manager Implementation Project

This solution package is designed for a specific system landscape that is represented by itslogical components. By preparing and mapping the logical components to the actual physicalsystems in the landscape it enables you to configure the systems directly using SAP SolutionManager.

The logical component in SAP Solution Manager is an identifier provided by SAP for thecombination of product and product version. When selecting the SAP Solution Manager template,the logical component provided by SAP will automatically be mapped with the logical componentin the customer system landscape with the same combination of product and product version toset up access from SAP Solution Manager to the correct customer system.

Make the following entries (IT administrators, using transaction SMSY):

Delivered LogicalComponent

Product Product Version Product Instance LogicalComponent(CustomerNamespace)

EXT_WAREHOUSE_MGMT90_EWMonERP

SAP ExtendedWarehouseManagement

SAP EWM 9.0 EWM on SAP ERPOr

EWM on SAP SCM

Or

EWM Standalone

<Choose aname>

2.7 SAP Best Practices Add-on and SAP Best PracticesSolution Builder Add-on

http://service.sap.com/sap/support/notes/1686668





http://help.sap.com/



http://service.sap.com/solutionmanager


http://service.sap.com/swdc

http://service.sap.com/swdc








© SAP AG of 38

If you decide for automated deployment, Solution Builder has to be installed in yourSAP ERP and SAP EWM system.

The following SAP Best Practices add-ons must be imported into the system:

SoftwareComponent

Release Version Description

BP-CANW 731 Vx

Use the latest version asoutlined in SAP Note1301301 ReleaseStrategy for SAP BestPractices Package ABAP Add-ons

For more information, seethe document ImportingSAP Best Practices Add-Ons (ADDONINS.PDF) on the configuration DVD.

This add-on containsthe SAP BestPractices technicalframework (forexample, BC-Sets,eCATTS)

BP-SOLBLD 70 Vx SAP Best Practicessolution builder

This add-on contains

the SAP BestPractices solutionbuilder program

You can find additional and detailed information in the document Importing SAP Best Practices Add-Ons (ADDONINS.PDF) on the Configuration DVD (latest available DVD via SAP Note1240936).

To download the SAP Best Practices add-ons, go to the SAP Software Download Center (SWDC)on SAP Service Marketplace:

https://service.sap.com/swdc → Installations and Upgrades

→ Browse our download catalog→ SAP Rapid Deployment Solutions→ SAP Extended Warehouse Management rapid-deployment solution

Regular Updates Technical Environment

The technical add-ons provided by SAP Best Practices form the technical environmentrequired for the automated implementation of your SAP Best Practices version withsolution builder. This technical framework is continuously updated providing enhanced,fixed, or additional technical objects required for the technical implementation process.

SAP Best Practices therefore offers updated versions of the add-ons on a regular basis.Each updated add-on replaces the previous version in your system. For more informationabout the currently available versions of the add-on BP-ERP and the add-on BP-SOLBLD, see SAP Note 1301301 (see also section SAP Notes and Messages of thisdocument.)

Since the solution scope file and the most current installation data files alwayscorrespond to the current technical add-ons, you always have to ensure the system is atthe current versions before you start the technical implementation of the SAP BestPractices version.

The update of the technical framework has no impact on scope or business content ofyour SAP Best Practices version as it is described in the respective documentation.

























© SAP AG of 38

If corrections are available for Solution Builder, they have to be implemented inSAP ERP and SAP EWM.

Result

The Solution Builder and the BP-CANW content Add-on has been installed in your SAP ERPand SAP EWM system.

2.8 General Client Settings

Use

Certain client settings are required for activation of the rapid-deployment solution content.

The settings need to be done in your SAP ERP and SAP EWM system.

Client Roles:

The system must not comprise any clients with the role productive client . If the systemcontains a productive client, BC sets cannot be activated as required. As a consequence, theautomatic activation of SAP Best Practices content using SAP Best Practices solution builderis not possible, because BC sets cannot be activated in a productive system.

To check and maintain the settings of clients in your system, use transaction SCC4.

Changes and Transport for Client-specific Objects:

To activate a SAP Best Practices packages, an automatic recording of changes is required. Toensure that all the changes are automatically recorded in a change request, in the Changes andTransport for Client-specific Objects group box, choose Automatic recording of Changes.

Cross-client Object Changes:

During the activation of an SAP Best Practices package cross-client objects are created.

Cross-client functions include all cross-client customizing objects (for example, factorycalendar, definition of price list conditions, printer controls) and all objects of the SAPRepository (for example, reports, module pools, screens, dictionary and so on).

To enable changes to cross-client objects, in the Cross-Client Object Changes group box,choose Changes to Repository and Cross-client Customizing allowed .

In case you have not allowed changes to Repository and cross-client Customizing, youwill be asked during the activation of the package if these settings should be doneautomatically by solution builder. If you reject the required changes the activation cannotbe executed automatically.

Procedure

1. Access the activity choosing one of the following navigation options:

SAP ECC Menu Tools → Administration → Administration → Client Administration → Client Maintenance

Transaction Code SCC4

2. Choose Display → Change.

3. Confirm the warning message Caution: The table is cross-client .

4. Select your client and choose Details.




© SAP AG of 38

5. In the Change View “Clients”: Details screen, activate the following settings:

Automatic recording of changes.

Changes to Repository and cross-client Customizing allowed

eCATT and CATT allowed .

Setting eCatt and eCatt allowed is only required if you decide for automatedimplementation via Solution Builder.

6. Save.

7. Go back to the SAP Easy Access Menu.

2.9 SAP Enterprise Extensions Sets and EnterpriseBusiness Functions

Use

BEFORE implementing the rapid-deployment solution, the following Business Functions need tobe activated in in SAP ERP and SAP EWM.

Activating Enterprise Extensions, Business Functions, and Business Function Setsmeans permanent changes to your system which cannot be undone. For moreinformation about the impacts on your system, see the documentation of the relatedExtension Set or Business Function.

.

Ensure that you have activated all Business Functions as outlined below before youcreate the client in which the rapid-deployment solution shall be activated.

Procedure

1. Run the following activity in both systems, using the business functions mentioned in the twochapters below:

IMG Menu SAP Customizing Implementation Guide ActivateBusiness Functions

Transaction Code SFW5

2. On the Switch Framework: change Business Function Status screen, select each of thefollowing entries (by marking the column Planned Status) and then choose the ActivateChanges button:

EnterpriseExtensions

PlannedStatus

Remarks

<enterprise extension> ON See list of business functions in chapters below

Enterprise BusinessFunctions

PlannedStatus

Remarks

<enterprise businessfunction>

ON See list of business functions in chapters below

3. The system displays an informational dialog box. Choose Continue.

4. Choose Back .




© SAP AG of 38

2.9.1 Activating Business Functions in SAP ERPMore information on business functions listed below can be found on SAP Help Portal athttp://help.sap.com under Business Functions (SAP Enhancement Package 6 for SAP ERP 6.0)

Business Functions in SAP ERP Enterprise Business Functions.

2.9.2 Activating Business Functions in SAP EWM

Technical Name Description

Enterprise Business Functions

SCM_EWM_FND EWM, Essential Foundation Functions

SCM_EWM_MEAN EWM, Additional GTINs (EANs/UPCs) for Product

2.10 SAP Notes and MessagesIf issues become apparent after shipment of this rapid-deployment solution, (and hence of thisdocument), an SAP Note exists to document how to solve the issues.

Before you start the activation of the rapid-deployment solution, check thelatest version of the SAP Note 1869426 to obtain updates and corrections forproblems that have not become apparent until after shipment.

All SAP Notes have to be applied to the system via the SAP Note Assistant. All SAPNotes mentioned below need to have the implementation status Completelyimplemented . Some SAP Notes require manual action before you set the status to

completely implemented.

To avoid activation errors as a result of generating loads, you have to perform a

mass generation using transaction SGEN as described in the SAP Note 481548.

2.10.1 SAP Notes in SAP EWMThe following SAP Notes must be implemented in your SAP EWM system:

SAP Note # Description Component Remark

1870006 Duplicate PWP nodes in inbounddelivery

SCM-EWM-WOP-BF-WTC

Technical Name Description

Enterprise Business Functions required for SAP EWM integration in SAP ERP

LOG_LE_INTEGRATION LE, Extended Warehouse Management Integration

Enterprise Business Functions required for SAP ERP US baseline in SAP ERP

Activate all business functions mentioned in the quick guide of the best practice solution for SAPERP US baseline. Complete Best Practice US baseline solution, including Quick Guide, can bedownloaded from here

http://service.sap.com/bp-implcontent

Baseline Packages U.S.

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=481548&_NLANG=en&_NVERS=0










© SAP AG of 38

1880256 Duplicate PWP nodes in inbounddelivery v2

SCM-EWM-WOP-BF-WTC

1849731 Problems with the search in EWM CA-CL-CL

1889983 No doc flow for WT cancellation(TOR) for inbound delivery

SCM-EWM-WOP-BF-CC

2.11 Unicode Settings

Use

If your systems are set up as Unicode system, before each user logs on to the system for the firsttime, the user’s local GUI must be set to use the Unicode code page.

The setting needs to be done for your SAP ERP and SAP EWM system.

Procedure

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

2.12 Creating User for Activation of SAP Best PracticesContent

Use

In this activity, you create a user to run the activation of the related SAP Best Practices scope.

An activation user has to be created in your SAP ERP and SAP EWM system.

SAP EWM does not supply separate customizing or setup roles (according to the securityguideline). Instead, you should use the functions provided in Role Maintenance (transactionPFCG). Here you can define a role corresponding to your individual IMG project with all theauthorizations you need to access the corresponding IMG activities required for the SAP BestPractices scope.

For more information about building a role for a Customizing project, see the documentation forthe transaction PFCG.

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 theuser according to your internal authorization guidelines. Without the profileSAP_ALL, issues during the activation may occur and need to be solved. You can




© SAP AG of 38

use the transaction SU53 to get information on the missing authorizations andextend the authorization data as necessary.

Directly after activation of the SAP Best Practices content, remove theauthorizations you have given to the system user that has performed the

activation steps. This is for security reasons to avoid that the system user misusesthe authorizations granted before.

Procedure

1. To carry out the 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 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.


Field name User action and values Note

Password <initial password>

User type Dialog

7. Choose the Defaults tab.


Field Name Value Comments

Decimal Notation X 1,234,567.89 Formatting for decimal notation usuallyused in the U.S.

US decimal notation format is amandatory prerequisite forimplementing this solution.

Date Format 2 MM/DD/YYYY Month, Day and 4 digit Year usuallyused in the U.S.

Time Format (12/24h) 0 24 Hour Format(Example 12:05:10)

12 hour format using AM and PMusually used in the U.S.




© SAP AG of 38

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 thatthis corresponds to your internal security guidelines.

11. Save your entries.

Result

Users to activate SAP Best Practices content have been created in SAP ERP and SAP EWM.

2.13 Setting the Maximum Work Process Run Time

Use

Dynamic switchable profile parameters (indicated by a flag in the check box of the parameter)

have to be checked before activation. Therefore, check and adapt the following profileparameters.

For the activation of the SAP Best Practices content, the parameter value for maximum work process run time must be increased because there are some processes that must be performedin dialog and that last for more than 10 minutes.

Procedure

1. Run the following activity:

Transaction Code RZ11

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

Field Name Description User Action and Values NoteParam. 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 Newvalue

Note

rdisp/max_wprun_time Max work process runtime 3600 Check and adapt thevalue if the value is<3600


Result

You have changed the parameter. This change only becomes effective when you log-off and log-on to the system again.

Switch back to the default value after activating the solution package.

The change is lost when you restart the server (as all profile parameters). If youhad to restart the server, repeat these settings.




© SAP AG of 38

2.14 SAP Scripting

Use

eCATTs are used to automate the activation of the rapid-deployment solution configurationsettings. Before activation, 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 setto true.

Procedure



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

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:

Field Name Description User Action and Values Note

New Value New Value for userscripting

TRUE Enable SAPScripting

6. Choose Save.

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

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

2.15 Setting Default Timeout for HTTP and HTTPSServices

Use

We recommend that you set the following system parameters for both services TIMEOUT andPROCTIMEOUT to 300 seconds or 600 seconds. The default is 60 seconds.

Procedure



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

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

4. On the Maintain Profile screen, make the following entries

Parameter Name Description New Value Note

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

300 or 600 Set to 300 or 600(seconds) for




© SAP AG of 38

Parameter Name Description New Value Note

TIMEOUT andPROCTIMEOUT

icm/server_port_0 = httpPORT=8000

PROCTIMEOUT=300 TIMEOUT=600 Example

icm/server_port_2 = https

PORT=44300

PROCTIMEOUT=300 TIMEOUT=600

Example

5. Choose Back.

6. Choose Save.

2.16 Creating Transport Requests for Activation

UseThe activation users created in the preceding section require a workbench and a customizingrequest for implementing the solution.

The transport requests can be created by those users during activation. However, if the user isnot allowed to create own requests, the system administrator must create these requests inadvance and they can be used during implementation.

Transport requests have to be created in your SAP ERP and SAP EWM system.

Procedure

1. To carry out the activity, choose one of the following navigation options:

SAP Menu Tools

Customizing

IMG

Transport Organizer (Extended View)

Transaction Code SE10

2. On the Transport Organizer screen, choose the Create button.

3. In the Create Request dialog window, choose one of the following options:

For a Customizing Request Customizing request

For a TWorkbench Request Workbench request

4. Choose Enter .

5. In the Create Request dialog window, enter a Short Description.


Result

You have created a workbench and a customizing request to activate the solution content.

Repeat the steps above for all systems and clients you use.

If necessary, assign the requests to the relevant activation users. i.e. create taksfor them in the transport requests.

Pass the transport request numbers to the user.




© SAP AG of 38

2.17 Create RFC Destination for Remote Deployment ofSAP ERP Configuration and Sample Master Data

Use

The steps described in following chapters

Are only required if you activate your solution using SAP Best Practices solutionbuilder

Are NOT required if SAP EWM is installed as add-on with SAP ERP.

The ERP part of the rapid-deployment solution can be deployed from SAP EWM (‘remotedeployment’).For remote deplyoment, according to SAP security standard, trusted RFC destinations arerequired.

In this activity, you set up

- the trusted RFC between SAP ERP and SAP EWM

- the RFC destination in SAP EWM

2.17.1 Create Trusted RFC in SAP ERP

Use

A trusted RFC relationship needs to be configured on system level.

Procedure

The SAP guideline for handling trusted RFC relationships between systems is described on theSAP Help Portal. In addition consider SAP note 128447.

The maintenance of trusted RFC relationships has to comply with the overallcompany security standard. Therefore it is recommended that this step is executedby the system administrator.

Create a trusted relationship according to this guidance by considering the following specifics:

Trusted system: System used for central solution activation with Solution Builder (SAPEWM)

Trusting system: System called from Solution Builder for remote configuration (SAP ERP)

The Solution Builder activation user created in step Creating a User for Activation of SAPBest Practices Content requires the authorization S_RFCACL in the trusting system (SAPERP).

ResultYou have created the trusted RFC connection between SAP ERP and SAP EWM.

2.17.2 Create RFC Destination in SAP EWM

Procedure

In SAP EWM, create a RFC destination from the trusted system SAP EWM to the trusting systemSAP ERP by using the established trusted relationship.

1. Access the activity using one of the following navigation options:

Transaction CodeSM59

http://help.sap.com/saphelp_nw04/helpdata/en/8b/0010519daef443ab06d38d7ade26f4/content.htm










© SAP AG of 38

SAP EWM Menu Tools

Administration

Administration

Network

RFC Destinations

2. Choose Create (F8).

3. Enter the following data:

Field Entry

RFC Destination <system name>CLNT<client>_A (the postfix _A ismandatory), for example: ERPCLNT100_A

Connection Type 3 (Connection to ABAP System)

Description Include the solution name, for example:

ERP System for Solution Builder Activation

4. Choose Enter. Technical Settings

Load Balancing No

Target host <Target host SAP system>, for example, pwdf0421

System number <System number of SAP system>

Logon/Security

Trusted Relationship YES

Status of SecureProtocol

Inactive

Language EN

Client <SAP trusting system client>

User <blank>

Password <blank>

Current User <Selected>

Unicode

Communication Typewith target system

Set the Unicode flag if the Unicode Test has been executedsuccessfully. You can perform this test by choosing UnicodeTest in the menu area. The RFC destination has to be saved

first before the test can be performed. An informationmessage appears (Example of a message: “Target is aUnicode system (character size 2”)).

5. Save your RFC destination.

Result

You have successfully created the RFC connection.

You can now test your newly created RFC connection.

Connection test for a technical test (Host, IP Address) of the target system.

Logon test for checking logon to the target system, using the maintained user and password

of the RFC destination.




© SAP AG of 38

This RFC destination will be used in the Solution Builder system landscape maintenance duringactivation (see step Assigning RFC Destinations to Target Systems).

3 Preparation Activities - Act ivat ion Consu l tant

3.1 Initial Check of System ReadinessEnsure that the system administrator has also finished all activities as described in sectionSystem Setup & Preparation - Administrator .

It is especially important that you check if your system administrator has applied the correctproduct versions and SPS level as outlined in section Release and Support Package Level .

Continue with the following steps only if these prerequisites are met.

3.2 SAP Software Change Registration (SSCR):Developer Key

Use

During activation of the solution, workbench/development objects may be created.

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. TheSSCR developer key is needed, because the user ID used for SAP Best Practices activationcreates and changes objects from the customer name range during the SAP Best Practicesactivation process. If the SAP Best Practices activation user is not registered as a developer, theautomated SAP Best Practices 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 userdocumentation on how to proceed to get the SSCR developer key.

An SSCR developer key is a 20 character combination of digits that is queried whena user tries to create or change an object from the customer name range FOR THEFIRST TIME. The prompting message for the developer key appears once for eachuser; if registration is successful, this user is no longer prompted to enter a developerkey. The SSCR developer key is generated from the installation number of theaffected installation and the user name.

3.3 User Settings for ActivationThe following settings need to be made for the activation user in your SAP ERP andSAP EWM system.

For activation, we recommend that only one User ID is used to activate the SAP BestPractices. It may be difficult to change ownership of the activation of the solution.

Make sure that you only have one single SAP GUI session running when youactivate SAP Best Practices. If you run several SAP GUI sessions, some automatedinstallation activities might run into errors.




http://service.sap.com/sscr








© SAP AG of 38

3.3.1 Check/Set Decimal Notation and Date Format

Use

Perform this activity to check proper set up of activation user.

US format for Decimal Notation and Date are mandatory prerequisite forimplementing this solution.

Procedure

1. Access the transaction using one of the following navigation options:

SAP Menu System→ User Profile

Own Data Transaction Code SU3

2. On screen Maintain User Profile:

3. Navigate to tab Defaults 4. On Defaults tab check/change the following data:

Field Name Value Comments

Decimal Notation X 1,234,567.89 Formatting for decimal notation usuallyused in the U.S.

Date Format 2 MM/DD/YYYY Month, Day and 4 digit Year usuallyused in the U.S.

Time Format (12/24h) 0 24 Hour Format(Example 12:05:10)

US format not required here!

5. Choose Save .

If you have changed the settings, log off and log on is necessary sincethe change in the user settings only becomes effective when you log onto the system again.

Result

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

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

3.3.2 Deactivate Info Dialog Box on Dynpro Size Check

Use

The dialog box sizing conflicts may appear, which may pop up during activation, has to bedeactivated.




© SAP AG of 38

Procedure

1. Log on with the user in the system.

2. Choose the first button from the right side of the Standard Tool Bar Customize Local Layout.

3. Select the menu item Options.

4. Select the menu item SAP Internal – SAP Internal.

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

6. Choose the OK button at the bottom.

3.4 Activation LanguageMake sure that your logon language is always English (and NOT your local language) for allactivation activities.

Activation language EN is mandatory.

3.5 Check Note 1869426Before you start the activation, check note 1869426.

Attachments of the note may contain updated documentation

‘Known issues’ section can contain hints on known issues, which were not correctedyet in official documentation

4 Implementation – Activation Consultant

PrerequisitesBefore you can start activating the business processes, all activities in sections

System Setup & Preparation - Administrator

Preparation Activities - Activation Consultant

must be completed.

4.1 Prerequisite: SAP Best Practices US BaselineBefore you start implementing the SAP Extended Warehouse Management rapid-deplyomentsolution, SAP ERP Best Practice for US needs to be implemented on your SAP ERP system.

For implementation of SAP ERP Best Practice for US baseline refer to the Quick Guide of thesolution.

Consider following hints when you deploy the US baseline for the EWM rapid-deploymentsolution:

Scoping SAP BP US Baseline

For the SAP EWM rapid-deployment solution, only certain BP US baselinescenarios need to be activated.

You can either activate complete SAP ERP BP US baseline, or only the scenarioswhich are relevant for SAP EWM integration. Only activating those relevant

http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=%201869426&_NLANG=en&_NVERS=0







© SAP AG of 38

scenarios will reduce the effort for SAP BP US baseline activation. The followingscenarios are relevant for SAP EWM integration; you can de-scope all other

scenarios during the scoping step described in the Quick Guide for SAP BP USbaseline activation

o 109 Sales Order Processing: Sale from Stock

o 130 Procurement without QM

Personalization of SAP BP US Baseline

If you are using personalization during implementation of SAP ERP BestPractice for US, you have to make sure the personalized values are used forthe implementation of the SAP Extended Warehouse Management rapid-deployment solution.

If you do not use these personalized values during implementation of the SAPEWM rapid-deployment solution, it will note be usable.

To generate a list containing default and personalized values refer to SAP note1421667.

Use this list to replace the default values of SAP EWM rapid-deploymentsolution in the deployment options described below.

4.2 Manual ImplementationThe pre-configuration of the solution can be implemented manually by following the configuration

guides according to the sequence of the Prerequisites Matrix. The Prerequisites Matrix gives anoverview of the configuration building blocks and related configuration guides, required for eachbusiness process and the correct sequence for implementing the building blocks.

The Prerequisites Matrix can be found in the step-by-step guide Deploy Activate Solution

Manual Activation and Configuration Content Library Prerequisites Matrix .

We recommend using SAP Solution Manager to control the manual implementationas well as to document your implementation of the solution package.

4.3 Activation of Business Content / Scenarios withSolution Builder

The following section describes the activities that have to be done to install all required add-oncomponents, and for activation of the rapid-deployment solution by the consultant, using SolutionBuilder.

If you decide to implement the solution via Solution Builder, it needs to be installed on SAPERP and SAP EWM.

The implementation of SAP Extended Warehouse Management rapid-deplyoment solutionautomated content (SAP EWM and SAP ERP part) is started from Solution Builder in SAP

EWM. Nevertheless for technical reasons you also need Solution Builder installed on SAPERP.







© SAP AG of 38

4.3.1 Allow GUI Scripting

Use

Perform this activity so that eCATT GUI scripts can be executed with your GUI.

Procedure

1. Choose the first button from the right side of the Standard Tool Bar Customize Local Layout.

2. Select the menu item Options.

3. Expand the folder Accessibility & Scripting.

4. Select the item Scripting.

5. Select the Enable scripting checkbox.

6. Deselect the checkboxes

a. Notify when a script attaches to a SAP GUI and

b. Notify when a script opens a connection.

7. Choose the OK button at the bottom.

4.3.2 Getting the Business Content for Activation

Use

The preconfiguration (‘Business Content’) is provided in form of

Solution Scope file

The technical structure for each solution (scenarios, building blocks, and technical

objects) of the SAP Best Practices is managed by a solution scope file.

Installation Files

The installation settings (configuration settings and master data) of the SAP BestPractices are managed by the installation data files.

Before activating the content, you need to download these files from SAP Service Marketplace.

Perform the steps Gett ing the Solut ion Scop e Fi le and Gett ing the Instal lat ion

Data Files on the same day. If you download them at different times, you mayencounter errors due to mismatching versions.

4.3.2.1 Creating Folders for the Solution Scope andInstallation Data Files

Use

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

Procedure

Create a folder on a hard drive that can be accessed from within the SAP system where you wantto activate the rapid-deployment solution.




© SAP AG of 38

If you have implemented SAP ERP BP US baseline in your ERP system, DO NOT use the same folder for SAP EWM RDS implementation. Otherwise you may overwritepersonalized values!

Ensure that the persons who will activate the solution have the necessary user rights to accessthese folders.

4.3.2.2 Getting the Solution Scope Files

Use

The technical structure for each solution (scenarios, building blocks, and technical objects) ofthe SAP Best Practices is managed by a solution scope file.

Procedure

1. To download the solution scope files, first go to SAP Service Marketplace athttp://service.sap.com/bp-implcontent.

2. Choose the Solution files link.

3. In section SAP EWM 9.0 , choose the link for SAP EWM 9.0

4. Download solution file SOL_RDS_EWM_EWM90V4_BP_CANW731Vx.zip

(x stands for a sequential number, always use the latest version).

5. Unpack the ZIP file and copy the solution scope file (*XML) into the folder created in thesection above.

4.3.2.3 Getting the Installation Data Files

Use

The installation settings (configuration settings and master data) of the SAP Best Practices aremanaged by the installation data files.

Procedure

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

2. Choose the Installation data file sets link.

3. In section SAP EWM 9.0 , choose the link for SAP EWM 9.0

4. Download installation data file INST_FILES_EWM90_XX_BP_CANW731Vx.zip(x stands for a sequential number, always use the latest version).

5. Unpack the ZIP file and copy the Installation data files (*TXT) into the folder created insection above.

4.3.3 Activation of Scenarios

Use

This section describes the activation of the SAP Extended Warehouse Management rapid-deployment solution using the SAP Best Practices Solution Builder.

Procedure

All steps below need to be performed in your SAP EWM system

You will perform following steps in order to perform the activation. Main steps cover:



https://websmp104.sap-ag.de/~sapidb/011000358700000335202012E/EWM900/EWM900.htm



https://websmp210.sap-ag.de/~sapidb/011000358700000335192012E/ERP606/INST_FILES_EWM_XX_BP_ERP606V4.zip
















© SAP AG of 38

Import the Solution File

Assign RFC destination for remote deployment of SAP ERP content

Scope your solution

Upload Installation Data

Personalize values

Activate solution

During activation some manual steps are required (the solution file structure withinSolution Builder will guide you through those steps)

4.3.3.1 Import the Solution File1. To run the SAP Best Practices Solution Builder, from the Command field, enter /n/smb/bbi

and press Enter .

2. On the Solution Builder – Solution editor screen, from the menu, chooseSolution

Import

Solution (XML).3. On the Select the Solution Scope File (XML) dialog box, browse to the location of your XML

file (in the folder you created during step Creating Folders for the Solution Scope andInstallation Data Files), select it, and choose Open.

4. Confirm the upcoming information message.

4.3.4 Assigning RFC Destinations to Target Systems

Use

This step is NOT required if SAP EWM is installed as add-on with SAP ERP.

You have to assign the RFC destinations created in the step Create RFC Destination for RemoteDeployment of SAP ERP Configuration and Sample Master Data to the target systems in theSystem Landscape Maintenance.

Procedure

1. On the Solution Builder – Solution Editor screen, choose Goto → System LandscapeMaintenance.

2. In the System Landscape Maintenance dialog box, the Solution ID of the solution to beactivated, should be shown (RDS_EWM_EWM90V4).

3. Mark the row with target system ECC .

4. Choose Edit Entry .Enter the trusted RFC destination for the SAP ERP system created in section Create RFCDestination for Remote Deployment of SAP ERP Configuration and Sample Master Data.

You do not need to assign a RFC destination to target system SCM. SCM stands for the SAPEWM system; in this system the solution is activated.

5. Choose OK .

Result

You have maintained the system landscape information required to activate configuration contentremotely.




© SAP AG of 38

4.3.5 Set Documentation Path for Solution Builder

Use

By setting the path to SAP documentation in solution builder, the relevant configuration guidesautomatically appear during activation. This enables you to process manual installation steps.

Procedure

1. On the Solution Builder – Solution Editor screen, from the menu choose Goto UserSettings.

2. Choose the External Documents tab.

3. Make sure the documentation parameter is set accordingly:

Parameter Value

DOCUMENTATION http://help.sap.com/saap/sap_bp/BBLIBRARY/HTML/

4. In case the parameter is missing, choose the Display <> Change button.

5. Choose the Insert Row button.

6. Make the following entries as described in the table above.7. Choose Save.

8. Choose Back .

4.3.6 Scope Your Solution

Use

All processes of an uploaded solution represent the maximum scope that can be implemented.Depending on the individual requirements, a smaller solution scope may be sufficient. Thescoping tool provides an easy to use graphical user interface that provides additional detailsabout each process, and an easy select/deselect-function to add or remove processes in a

scope.

Prerequisites

You have imported the solution file (XML) successfully.

Procedure

1. On the Solution Builder – Solution Editor screen, choose Solution →Create →.CustomerSolution (Ctrl+F9).

The scope matrix for your solution is displayed.

2. Initially all processes are selected. Click on a process and choose Details to get more

information about a process.

3. Deselect the process to remove it from the scope.

4. After completion of scoping, choose Save Data to save your result.

5. Enter a Solution ID and a Description for your individual scope.

6. Choose Back.

Result

The custom solution with the selected scope of processes is created.

To continue the following operations regarding your custom solution, ensure that yoursolution has been defined as Favorite solution (On the view Solution Builder – SolutionEditor, choose the Favorite button).




© SAP AG of 38

4.3.6.1 Upload the Installation Data

Use

The purpose of this step is to upload the installation data to SAP Best Practices solution builder.

Prerequisites

The installation data files have been downloaded to the local directory you created in stepCreating Folders for the Solution Scope and Installation Data Files.

The solution file has been uploaded into the system.

For the user who activates this solution, the following user settings must be set under Solution

Builder Solution Editor Goto User Settings, General tab:

Deselect the setting Check consistency with eCATT definitions during Installation dataupload.

Deselect the Enable activation with BC Set API checkbox.

Procedure

1. On the Solution Builder – Solution Editor screen, choose the Upload Installation Data button

(Ctrl + F5).

2. In the Upload and Download external file data dialog box, browse to the location of yourinstallation data files, select them, and choose Continue (Enter).

Select the folder/ZIP-file, and choose Continue (Enter).

4.3.6.2 Select Languages

Use

SAP EWM rapid-deplyoment solution is only provided in EN, further languages maybe provided in future releases.

The configuration content (Customizing) of the solution package is provided in several languages.

On solution level, you can define which languages will be activated for language-specificCustomizing.

In the default settings, all languages supported by the solution package are selected. Reduce thelist of languages only in the following cases:

Only a subset of languages is required for your solution.

Some languages that are active on solution level have not been installed in your system.

Procedure

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

2. Choose Change Solution.

3. In the Change Solution dialog box and screen area Released Languages, deselect those

languages that are not relevant for your project or that are not installed in the SAP EWMsystem. Language EN always has to be active.

Use transaction SMLT to identify the installed system languages.

4. Choose Enter.




© SAP AG of 38

4.3.6.3 Personalize the Solution

This step is mandatory for the SAP EWM rapid-deployment solution. It is essential forthe activation of the solution that all mandatory personalization steps are executedaccurately.

Wrong m aintenance of the personal izat ion and integrat ion data may lead to

issues dur ing the act ivat ion and the us age of the package . However, you canusually change the data after the activation, in the corresponding transactionsmentioned in the configuration guide.

1. On the Solution Builder – Solution editor screen, choose button Personalization (Ctrl+F8) On the Generic Personalization Composer screen, you can see all activities that can be

personalized.

2. Navigate to all activities and double-click the activity to maintain the required data. A document is attached for each step. These documents describe whether an activity ismandatory, which data has to be maintained and how to determine the required values inthe back end client. To open the document, choose button Display documentat ion .

NOTE, only deployment option 'EWM as Add-On with SAP ERP':

During personalization you cannot maintain the hostname for the RFC destination fromSAP EWM to SAP ERP (third personalization activity). The system does not accept thehostname because you have used same value already for personalization of RFCdestination from SAP ERP to SAP EWM. Solution: Leave the hostname field empty, andchange the value in transaction SM59 after activation of the solution via Solution Builder.

3. Make any personalized entries and set the status to document the progress of yourpersonalization activities.

When you are done with personalization, set the status of each activity to‘Completed’. Personalized data will not be used if you forget setting this status.

4. Save your entries after each personalization activity is done.

When you are done with personalization, double check all personalized valuesby double clicking on each personalization activity. Check whether thepersonalized values are displayed, if not, you need to create thepersonalization data again.

You can get the list of default values and their personalized values. To generate a listcontaining default and personalized values refer to SAP Note 1421667. This is anoptional step and is only possible if you have personalized the solution.

4.3.6.4 Starting Activation

Please consider: Activation of the solution will block your PC, i.e. you cannot do other

tasks on your PC in parallel, so you may want to do the activation on a separate PC.








© SAP AG of 38

1. Ensure that your solution is set as a favorite solution.

2. From the menu, choose Goto Implementation Assistant (Ctrl Shift + F3).

3. Select the top node of the solution, and choose the Activate button.

4. On the Activate solution dialog box, make the following entries:

Field name User action and values Comments

With demo Data

(this field is onbottom of thescreen, butshould bemaintained first)

Select

If you cannot mark thedemo data flag, emptyfield ‘Target Language’and the transport requestfields.

If selected, system executes activationsteps that create demo data. Ifdeselected, these steps are notexecuted.

The SAP EWM rapid-deploymentsolution does not use the demo dataflag. However, select the flag, do notdeselect.

Target Language EN Maintain EN as target language, as so

far only EN is supported. Furtherlanguages may be added in futurereleases.

SupplementalData

Leave this field empty. As you have uploadedinstallation data,message ‘InstallationData Upload Complete’should appear with greentraffic light left hand side.

Do NOT start activation if message‘Installation Data Upload incomplete’appears. Create OSS ticket oncomponent SV-RDS-SCM if thismessage appears.

Workbench <workbench requestnumber>

By default, this field and the WorkbenchRequest button are not active because

the Create Request checkbox isselected. The system creates theworkbench request automatically whenthe Create Request checkbox isselected. If you want to manually createor select an existing transport, deselectthe Create Request checkbox.

Customizing <customizing requestnumber>

By default this field and the CustomizingRequest button are not active becausethe Create Request checkbox isselected. The system creates thecustomizing request automatically when

the Create Request checkbox isselected . If you want to manually createor select an existing transport, deselectthe Create Request checkbox.

Skip this Screen Select If selected, the system does not displaythe Activate solution dialog box uponresumption of activation following anerror or manual activity. If deselected,the Activate solution dialog box willdisplay every time after resumption ofactivation.




© SAP AG of 38

Errors occur during activation – Where can I find more information to solve theissue?

In case of any issues during activation of the SAP EWM rapid-deploymentsolution, always check section below: ‘Use

The installation procedures of some building blocks contain manual installation steps and / or

require manual confirmation. This section describes how to handle manual steps in SAP BestPractices solution builder.

Procedure

If SAP Best Practices solution builder stops because of a manual activity, proceed as follows:

When you have set the user parameters in solution builder, the respective configuration guide isautomatically opened at the activation start of each building block. Keep this document open untilyou have finished all relevant activities for this building block. Confirm the information screen.

If the respective configuration guide does not open automatically, access the Content

Library via the Step-by-step guide Deploy Activate Solution Manual

Activation and Configuration Content Library .Navigate to the corresponding building block and open the configuration guide.

1. Use Ctrl+C to copy the task description to the clipboard. Use the Search function (Ctrl+F) tofind the corresponding step in the configuration guide.

2. In solution builder, choose the proposed navigation option, for example, Navigate to IMG, andexecute the configuration activity manually by following the instruction of the related sectionin the configuration guide.

3. Choose Back (from the IMG activity or the transaction).

4. Choose Proceed.

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

6. Enter a reason (optional) and choose Enter .

7. Proceed with the activation.

Result

You have successfully processed a manual activity.

Error Handling: Installation Errors during Activation’.

For errors during activation of Best Practice SAP ERP baseline, check therespective Quick Guide.

5. Choose Continue.

Manual Step Handling

There are some manual steps that you will need to handle during activation. TheSolution Builder displays a procedure dialog box with instructions for you to follow toprocess the step. Read next chapter for more detailed instructions for manual steps.

If you use PERSONALIZED values, do NOT use the DEFAULT values mentioned inthe manual step configuration descriptions and configuration guides, but use yourpersonalized values wherever applicable.




© SAP AG of 38

Running an eCATT in Foreground Mode

Activation activities may require running an eCATT in foreground mode. Thefollowing description provides an instruction on how to run the eCATT in theforeground mode.

Procedure

1. On the Start eCATT Test configuration screen, select Display Start Options.

2. Choose the Execute button.

3. On the following screen, choose the UI Control tab.

4. In the TCD box, in Start Mode for Command TCD, use the dropdown to select A Process in Foreground, Synchronous Local .

4.3.7 Manual Interaction and Error Handling During Activation

Use

The installation procedures of some building blocks contain manual installation steps and / orrequire manual confirmation. This section describes how to handle manual steps in SAP BestPractices solution builder.

Procedure

If SAP Best Practices solution builder stops because of a manual activity, proceed as follows:

When you have set the user parameters in solution builder, the respective configuration guide isautomatically opened at the activation start of each building block. Keep this document open untilyou have finished all relevant activities for this building block. Confirm the information screen.

If the respective configuration guide does not open automatically, access the Content

Library via the Step-by-step guide Deploy Activate Solution Manual

Activation and Configuration Content Library .

Navigate to the corresponding building block and open the configuration guide.

8. Use Ctrl+C to copy the task description to the clipboard. Use the Search function (Ctrl+F) tofind the corresponding step in the configuration guide.

9. In solution builder, choose the proposed navigation option, for example, Navigate to IMG, andexecute the configuration activity manually by following the instruction of the related sectionin the configuration guide.

10. Choose Back (from the IMG activity or the transaction).

11. Choose Proceed.

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

13. Enter a reason (optional) and choose Enter .

14. Proceed with the activation.

Result

You have successfully processed a manual activity.

5 Error Handling: Installation Errors duringActivation




© SAP AG of 38

The following information helps you to solve problems that might occur during the installationprocess.

Before you start with detailed error analyzing and working through the error

processing as described below, proceed as follows:

Activate your solution or the respective scenario in the Solution Builderimplementation assistant again. It might be the case that error does not reappear. Inthis case, no correctional activities are needed and the installation is proceeding.

5.1 Error Occurs During Activation of Automated Task

Use

When an activation of an automated task runs into errors, the activation stops at the point of theerror. 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 inthe 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 aneCATT or BC set activation is displayed.

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

a. In case the error can be solved based on the log information, you can run theeCATT or BC set again.

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

5. In case 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 theconfiguration guide for executing the task,

or

b. Open a customer message for this problem specifying the component <specificcomponent>.

Do NOT delete Solution Builder scenarios after they have been activated. If youdelete scenarios, the activation history and the respective logs are lost and it is notpossible 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 beenprovided via customer message), choose the Change button that is displayed in the OldStatus column to the right of the task.




© SAP AG of 38

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

In such cases NO SAP SUPPORT CAN BE PROVIDED.

7. Choose the Change button that is displayed in the Old Status column to the right of the task.

8. On the Confirmation dialog box, choose OK to manually change the status to successful.

9. On the Information dialog box, enter a reason for changing the status.

10. Choose Continue.

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

11. Choose Activate to continue with the installation.

6 Evaluate Business Content / ProcessesThis section describes the activities that have to be done by the business consultant who is takingcare that the business processes work as desired.

Details for individual scenarios are available in the content library which is part of the step-by-stepguide of the rapid-deployment solution.

The business process documentation (BPD) provides a detailed process step description

of the business scenario. The configuration guide describes the system configuration of the respective scenario.

Together with the configuration guides of the underlying building blocks, you can trackwhich system settings have been configured.

You can use the documents as described above to review the business scenarios you are

interested in. Use the business process documentation (BPD) to evaluate the scenario in the

system.

7 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 thecomponent SV-RDS-SCM.

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




© SAP AG of 38

8 Security AspectsThis section provides an overview of the security-relevant information that applies to thedeliverables of this solution package.

8.1 General Security GuidelinesThis section provides an overview of security guides delivered by the solution.

These guides cover generic security aspects for the underlying software products.

To access the latest version of the security guide, log on to SAP Service Marketplacehttp://service.sap.com/support → Release & Upgrade Info → Installation & Upgrade Guides →SAP Business Suite Applications → SAP EWM → Using SAP EWM 9.0 → Security Guide

8.2 Roles OverviewFor the rapid-deployment solution no special roles are required for navigation. You can use the

standard SAP menu for navigation.

For generation of authorization profiles, use the information provided in the process step list in thebusiness process documentation. Generate an authorization profile which covers all transactionsmentioned in the process step list.

All authorization profiles will have to be adapted according to the necessary requirements and theauthorization concept that has to be realized, respectively. Further information on this topic canbe found on the SAP Help Portal at http://help.sap.com: In the search entry field enter the termUser and Role Administration of AS ABAP as search term and confirm your entry. Finally, in thesearch results select the link to User and Role Administration of AS ABAP.

8.3 User Administration and AuthenticationThis section provides an overview of the users required for this solution package.

Purpose User-ID UserType

Created in InitialPassword

AuthorizationProfile

Comment

ActivationUser

User ID isdefined by yourSystem-Admin.

Dialog(Type A)

SAP ERPand SAPEWM’

Passwordis definedby yourSystem

Admin.

Authorization isdefined by yourSystem Admin.

EvaluationUser

User ID isdefined by yourSystem-Admin.

Dialog(Type A)

SAP ERPand SAPEWM

Passwordis definedby yourSystem

Admin.

Authorization isdefined by yourSystem Admin,according to

authorizationsrequired for thetransactions asdescribed in thebusinessprocessdocumentation.

You can check the users using transaction SU01.

http://service.sap.com/support




http://help.sap.com/saphelp_nw04s/helpdata/en/99/acdc3ed98f7650e10000000a114084/content.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/99/acdc3ed98f7650e10000000a114084/content.htm






For security reasons we recommend changing the password of users which areautomatically created during the implementation of the package, e.g. RFC User‘RFCDIAUSER’ in SAP ERP and SAP EWM.

Additional Information: Information about network security ‒ SAP Security Guideshttp://service.sap.com/securityguide

8.4 RFC DestinationsThis section gives an overview of the RFC destinations required that have been created and usedfor this package.

RFC Destination Description ConnectionType

Createdin

Logon Data Comment

<SAP ERP systemname>CLNT<SAPERP client>

SAP ERPsystem

3 SAPEWM

User:

Created duringimplementation

<SAP EWM systemname>CLNT<SAPEWM client>

Or in case SAPEWM is installed asadd-on with SAPERP:

<SAP EWM systemname>EWM<SAPEWM client>

SAP EWMsystem

3 SAP ERP User:

Created duringimplementation

You can check the destinations using transaction SM59.

For security reasons we recommend changing the password of users which arecreated during the implementation of the package, e.g. RFC User ‘RFCDIAUSER’ inSAP ERP and SAP EWM. Make sure passwords are also adjusted in thecorresponding RFC destinations.

9 Related DocumentationThe Master Guide for SAP EWM 9.0 provides crucial information on the installation of SAP EWM9.0.

The Application Operations Guide for SAP EWM 9.0 provides a starting point for managing yourSAP EWM solutions and keeping them up and running optimally.

To access the latest version of these guides, log on to the SAP Service Marketplace athttp://service.sap.com/support → Release & Upgrade Info → Installation & Upgrade Guides →SAP Business Suite Applications → SAP EWM → Using SAP EWM 9.0 .

http://service.sap.com/securityguide



