masterguide sapextendedwarehousemanagement9 - help.sap.com

Master GuideSAP Extended Warehouse Management 9.0Using SAP SCM 7.0 including SAP enhancement package 2, SAP ERP 6.0including SAP enhancement package 6, or SAP NetWeaver 7.3 includingSAP enhancement package 1

Target Audience

n Technical Consultantsn System Administrators

PUBLICDocument version: 1.2 ‒ 03/15/2013

SAP AGDietmar-Hopp-Allee 16

69190 WalldorfGermany

T +49/18 05/34 34 34F +49/18 05/34 34 20

www.sap.com

© Copyright 2013 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 permissionof 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 othersoftware vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries,xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner,WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks orregistered trademarks of IBM Corporation.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe SystemsIncorporated 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 registeredtrademarks 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 implementedby Netscape.MaxDB is a trademark of MySQL AB, Sweden.SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as wellas their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries allover the world. All other product and service names mentioned are the trademarks of their respective companies. Datacontained 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 notbe liable for errors or 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, if any. Nothing hereinshould be construed as constituting an additional warranty.

This document was created using stylesheet 2007-12-10 (V7.2) / XSL-FO: V5.1 Gamma and XSLT processor SAXON 6.5.2from Michael Kay (http://saxon.sf.net/), XSLT version 1.

DisclaimerSome components of this product are based on Java™. Any code change in these components may cause unpredictable andsevere malfunctions and is therefore expressively prohibited, as is any decompilation of these components.Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified oraltered in any way.

2/92 PUBLIC 03/15/2013

Documentation in the SAP Service MarketplaceYou can find this document at the following address: http://service.sap.com/instguides

03/15/2013 PUBLIC 3/92

http://service.sap.com/instguides



Typographic Conventions

Example Description

< > Angle brackets indicate that you replace these words or characters with appropriateentries to make entries in the system, for example, “Enter your <User Name>”.

Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in thedocumentation

Example Textual cross-references to an internet address, for example, http://www.sap.com

/example Quicklinks added to the internet address of a homepage to enable quick access tospecific content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example n Words or characters quoted from the screen. These include field labels, screen titles,pushbutton labels, menu names, and menu options.

n Cross-references to other documentation or published works

Example n Output on the screen following a user action, for example, messagesn Source code or syntax quoted directly from a programn File and directory names and their paths, names of variables and parameters, and

names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names,transaction codes, database table names, and key concepts of a programming languagewhen they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

4/92 PUBLIC 03/15/2013

http://www.sap.com

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


Document History

Caution

Before you start the implementation, make sure you have the latest version of this document. Youcan find the latest version on SAP Service Marketplace at http://service.sap.com/instguides.

The following table provides an overview on the most important document changes:

Version Date Description

1.0 7/31/2012 First version

1.1 8/28/2012 Correction to process naming

1.2 11/21/2012 Miscellaneous updates

03/15/2013 PUBLIC 5/92




Table of Contents

Chapter 1 Getting Started . . . . . . . . . . . . . . . . . . . . . . 91.1 About this Document . . . . . . . . . . . . . . . . . . . . . 91.2 Related Information . . . . . . . . . . . . . . . . . . . . . 111.3 Important SAP Notes . . . . . . . . . . . . . . . . . . . . . 12

Chapter 2 SAP EWMOverview . . . . . . . . . . . . . . . . . . . . . 152.1 Introduction to SAP EWM . . . . . . . . . . . . . . . . . . . 152.2 Software Component Overview . . . . . . . . . . . . . . . . . 182.2.1 Application Components . . . . . . . . . . . . . . . . . . . 182.2.2 Technology Components . . . . . . . . . . . . . . . . . . . 242.3 Software Component Matrix . . . . . . . . . . . . . . . . . . 262.4 System Landscape . . . . . . . . . . . . . . . . . . . . . . 292.5 Overall Installation Sequence . . . . . . . . . . . . . . . . . . 31

Chapter 3 Business Scenario: Warehouse Management with PreconfiguredProcesses . . . . . . . . . . . . . . . . . . . . . . . . . 33

3.1 Inbound Process Without Packing Information (Manual Goods Receipt) . . 353.2 Inbound Process Without Packing Information (Manual Warehouse Task) . 363.3 Inbound Process with Repacking for Putaway . . . . . . . . . . . . 383.4 Customer Returns with Quality Inspection . . . . . . . . . . . . . 393.5 Outbound Process Using Pick-HUs as Shipping HUs . . . . . . . . . . 403.6 Outbound Process Using Wave, Pick-HU, Packing, Staging, and Loading . . 423.7 Automatic Replenishment . . . . . . . . . . . . . . . . . . . 433.8 Unplanned Scrapping Due to Damaged Stock . . . . . . . . . . . . 443.9 Periodic Physical Inventory . . . . . . . . . . . . . . . . . . . 453.10 Cycle Counting . . . . . . . . . . . . . . . . . . . . . . . 46

Chapter 4 Business Scenario: Integration of Outbound Warehousing andTransportation . . . . . . . . . . . . . . . . . . . . . . 49

4.1 Managing Order-Based Outbound Processes (EWM-ERP-TM) . . . . . . 504.2 Handling Cancellation in Order-Based Outbound Processes (EWM-ERP-TM) 514.3 Managing Delivery-Based Outbound Processes (EWM-ERP-TM) . . . . . 534.4 Planning Transportation (EWM) and Billing (TM) in Outbound Processes . . 54

Chapter 5 Business Scenario: Dock Appointment Scheduling . . . . . . . . 57

6/92 PUBLIC 03/15/2013

5.1 Processing Dock Appointment Scheduling . . . . . . . . . . . . . 57

Chapter 6 Business Processes of SAP EWM . . . . . . . . . . . . . . . . 596.1 Inbound Process With Stock-Specific UoM (Manual Goods Receipt) . . . . 596.2 Inbound Process With Stock-Specific UoM (Manual Warehouse Task) . . . 606.3 Outbound Process With Stock-Specific UoM . . . . . . . . . . . . 626.4 Outbound Process with Cartonization Planning . . . . . . . . . . . 636.5 Inbound Processing and Receipt Confirmation with Warehouse Management in

SCM . . . . . . . . . . . . . . . . . . . . . . . . . . . 646.6 Outbound Processing with Warehouse Management in SCM . . . . . . 666.7 Warehousing and Storage in SCM . . . . . . . . . . . . . . . . 676.8 Physical Inventory on Storage Bin Level in SCM . . . . . . . . . . . 686.9 Merchandise Distribution . . . . . . . . . . . . . . . . . . . 696.10 Opportunistic Cross-Docking . . . . . . . . . . . . . . . . . . 706.11 Unpacked Inbound Delivery from Vendor (with Manual GR and Automatic

WT) . . . . . . . . . . . . . . . . . . . . . . . . . . . 716.12 Unpacked Inbound Delivery from Vendor (with Manual WT and Automatic

GR) . . . . . . . . . . . . . . . . . . . . . . . . . . . 726.13 Integration with Transportation (LE-TRA Component in ERP) . . . . . 74

Chapter 7 Solution-Wide Topics . . . . . . . . . . . . . . . . . . . . 777.1 Service-Oriented Architecture (SOA) . . . . . . . . . . . . . . . 777.1.1 Service Enablement . . . . . . . . . . . . . . . . . . . . . 777.1.2 Installation of the Service-Oriented Architecture (SOA) . . . . . . . . 807.1.3 Related Documentation . . . . . . . . . . . . . . . . . . . . 82

Chapter A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . 83A.1 List of Documents . . . . . . . . . . . . . . . . . . . . . . 83A.2 Media List . . . . . . . . . . . . . . . . . . . . . . . . . 85A.3 List of SAP Notes . . . . . . . . . . . . . . . . . . . . . . . 86A.4 Tools and Resources for Planning Your System Landscape . . . . . . . 87A.4.1 Business Process Repository (BPR) Viewer . . . . . . . . . . . . . 89A.4.2 Using the BPR Viewer . . . . . . . . . . . . . . . . . . . . . 89A.4.3 Scenario and Process Component List (SCL & PCL) . . . . . . . . . . 90A.4.4 Using the SCL/PCL . . . . . . . . . . . . . . . . . . . . . . 90

03/15/2013 PUBLIC 7/92

8/92 PUBLIC 03/15/2013

1 Getting Started

1 Getting Started

1.1 About this Document

This Master Guide provides a central starting point for the technical implementation of SAP ExtendedWarehouse Management (SAP EWM) 9.0. It contains all the information for the implementation ofSAP EWM business processes. To facilitate the installation, this document is organized by businessprocesses. You can choose from among several generic business processes and find all the informationthat is relevant for the technical implementation of a specific business process in that section.

Note

This Master Guide provides only one way to implement each business process using SAP EWM 9.0.For other ways to implement the business processes, see the Scenario Component List Viewer on SAPService Marketplace at http://service.sap.com/scl.For the technical upgrade of your SAP application/solution, see the Upgrade Master Guide on SAPService Marketplace at http://service.sap.com/instguides.

ContentBelow is a summary of the sections of this guide that you can refer to during the implementation ofthe business processes.

n Getting Started contains valuable information about using this document and related information(documentation and SAP Notes) crucial to the installation.

n SAP EWM Overview

l The Software Component Matrix provides the information about which business processes use whichcomponent and whether the corresponding component is mandatory or optional.

l System Landscape provides an overview of possible system landscapes and also provides installationinformation.

n Business Scenario: Warehouse Management with Pre-configured Processes contains the following information:l A short overview of the business scenario and the business processes in itl A software component matrix for the business scenario and each business process in it that

shows which components the business scenario uses and whether the component is mandatoryor optional

l References to further information about the business scenario and each business process in itn Business Scenario: Integration of Outbound Warehousing and Transportation contains the following information:l A short overview of the business scenario and the business processes in it

03/15/2013 PUBLIC 9/92

http://service.sap.com/scl


1 Getting Started1.1 About this Document

l A software component matrix for the business scenario and each business process in it thatshows which components the business scenario uses and whether the component is mandatoryor optional

l References to further information about the business scenario and each business process in itn Business Scenario: Dock Appointment Scheduling contains the following information:l A short overview of the business scenario and the business processes in itl A software component matrix for the business scenario and each business process in it that

shows which components the business scenario uses and whether the component is mandatoryor optional

l References to further information about the business scenario and each business process in itn Business Processes of SAP EWM contains the following information for each business process not

contained in the business scenarios mentioned above:l A short overview of the business processl A software component matrix for each business process that shows which components the

business process uses and whether the component is mandatory or optionall References to further information about each business process

n Solution-Wide Topics provides information about service-oriented architecture (SOA).n Depending on the specific business process, different installation guides, upgrade guides, and

master guides are required during the business process implementation. In the Appendix, you canfind an overview of all required documentation referenced in this Master Guide.

Note

You can find the most current information about the technical implementation of SAP EWMand the latest installation, upgrade, and configuration guides on SAP Service Marketplace athttp://service.sap.com/instguides. We strongly recommend that you use the documentsavailable here. The guides are regularly updated.

Information in the Master GuideUse the Master Guide to get a technical overview of SAP EWM and its business processes. The MasterGuide is a planning tool that helps you to design your system landscape and refers you to moredetailed documentation such as the following:

n Installation guides for single software unitsn Upgrade guides for single software unitsn SAP Notes

n Configuration documentationn SAP Library documentation

ConstraintsThe business processes that we present here serve as examples of how SAP software can be used.They are only intended as models and do not necessarily operate as we describe them in yourcustomer-specific system landscape. Check your requirements and systems to determine whether

10/92 PUBLIC 03/15/2013


1 Getting Started1.2 Related Information

these processes can be used at your site and be sure to test all processes thoroughly to ensure that theywork as desired in your environment.This Master Guide primarily discusses the overall technical implementation of SAP EWM thanits subordinate components. This means that additional software dependencies might existwithout being mentioned explicitly in this document. You can find more information aboutcomponent-specific software dependencies in the corresponding installation and upgrade guides.

1.2 Related Information

Related Documentation

The following table contains links to crucial information for implementing SAP EWM.

Content Location

Information about technical and release planningissues on SAP components

http://service.sap.com/pam

Information about the latest version of installationand upgrade guides for SAP components


Information about released platforms http://service.sap.com/platforms

Information about sizing and calculation of hardwarerequirements (such as CPU, disk, and memoryresource) with the Quick Sizer tool

http://service.sap.com/sizing

Information about network security ‒ SAP SecurityGuide

http://service.sap.com/securityguide

Information about network integration http://service.sap.com/network

Information about high availability http://service.sap.com/ha

Information about performance http://service.sap.com/performance

Information about the installation of SAP NetWeaver http://service.sap.com/instguidesNW

Documentation on SAP Help Portal http://help.sap.com

SAP Business Maps ‒ information aboutapplications/solutions and business scenarios

http://service.sap.com/businessmaps

Further Useful Links

The following table lists further useful links on SAP Service Marketplace:

Content Location on SAP Service Marketplace

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

SAP Notes search http://service.sap.com/notes

03/15/2013 PUBLIC 11/92





http://service.sap.com/platforms

http://service.sap.com/platforms





http://service.sap.com/network

http://service.sap.com/network

http://service.sap.com/ha

http://service.sap.com/ha

http://service.sap.com/performance

http://service.sap.com/performance

http://service.sap.com/instguidesNW

http://service.sap.com/instguidesNW

http://help.sap.com



http://service.sap.com/message

http://service.sap.com/message

http://service.sap.com/notes


1 Getting Started1.3 Important SAP Notes

Content Location on SAP Service Marketplace

SAP Software Distribution Center (software downloadand ordering of software)

http://service.sap.com/swdc

SAPOnline Knowledge Products (OKPs) ‒ role-specificLearning Maps

http://service.sap.com/rkt

1.3 Important SAP Notes

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

Relevant SAP Notes for SAP EWM

SAP Note Number Title Description

1705802 Implementation recommenda-tions for SAP EWM 9.0

For implementing SAP EWM 9.0

1691105 Installing or upgrading SCMEWM900

You want to perform an add-oninstallation or upgrade to SAPEWM 9.0.

1678780 BI_CONT / BI_CONT_XT 7x7:Information about installation andupgrade

Information about BusinessIntelligence Content 7x7 inrelation to add-on installation anddelta upgrade, and basis upgrade to7X.This note is only relevant if you useBI content for SAP EWM.

1606493 SAP EWM Deployment Options ‒Best Practices

Several deployment options existfor SAP EWM:. it can be deployedas Add-On to SAP NetWeaver, toSAP ERP or to SAP SCM.

1529649 Factory Calendar expires 2010 Factory calendars are deliveredfrom SAP with a validity until 2010in the standard. Before expirationno error message is displayed. Thiscould lead to follow-up errors atthe turn of the year, in differentapplications, using the calendar.

12/92 PUBLIC 03/15/2013













1 Getting Started1.3 Important SAP Notes


1515223 SAPNetWeaver Process Integration:Release Recommendation

Information about which PI releaseto use.This note is only relevant if you useEnterprise Services for SAP EWM.

1423066 Optimization of the performancein EWM

You are using SAP EWM and younotice that system performance isinadequate for your requirementswith regard to the dialog responsetimes or the consumption ofsystem resources.

1271261 EWM Upgrade: Pre- andPost-Upgrade Steps for DocumentFlow

Relevant only for the SAP EWMupgrade guide for 9.0. Informationrelevant for the Document Flow inSAP EWM.

1224284 Enterprise Services Bundles ‒Required Technical Usages andBusiness Functions

Lists business-related grouping ofEnterprise Services.This note is only relevant if you useEnterprise Services for SAP EWM.

1048230 De-activate the livecache for EWM Using SAP EWM in a SCM systemthe liveCache is not relevant andmay not be activated if you do notuse it for other SCM applications.This note is only relevant if youinstall SAP EWM as an Add-On toSAP SCM.

900000 Netweaver Business Client - FAQ This note is only relevant if you useNWBC for SAP EWM transactions.

03/15/2013 PUBLIC 13/92







This page is left blank for documentsthat are printed on both sides.

2 SAP EWM Overview

2 SAP EWM Overview

2.1 Introduction to SAP EWM

SAP Extended Warehouse Management (SAP EWM) is an advanced warehouse management solutionthat is fully integrated with SAP ERP. SAP EWM helps you gain more control over your warehousingprocesses and provides you with the tools needed to improve your warehouse efficiency, transformyour operations, and increase your competitiveness.With SAP EWM, you can optimize these processes:

n Inbound processes ‒ Establish support for yard management, putaway and stock removalstrategies, expected goods receipt, cross-docking, pick from goods receipt and push deployment,transportation cross-docking, value-added services, and quality management.

n Outbound processes ‒ Perform wave processing and replenishment processing.n Storage bin management and optimization ‒ Manage handling units, use slotting functions,

and take physical inventory.n Distribution center processes ‒ Enable planning and monitoring, radio frequency support, serial

number support, resource management, labor management, and automation and support formaterial flow systems.

The benefits offered include:

n Controlled warehouse processes ‒ Manage movements in the warehouse (from point-of-goodsreceipt to goods issue) and in the yard (from the time a trailer checks in until a product is packedand shipped).

n Improved warehouse efficiency ‒ Mitigate problems and major issues.n Real-time visibility and control of warehouse operations ‒ Transform operations into an adaptive

fulfillment supply chain in which customers, suppliers, and partners share knowledge andresources.

n Increased competitiveness and bottom-line improvement ‒ Respond faster to changes in supplyand demand.

SAP EWM allows for flexible and adaptive planning and coordination, in addition to executionof inbound and outbound processing, thereby consolidating the process flow across the entiresupply network. SAP EWM addresses the unique requirements of fulfillment operations across allwarehousing environments, such as:

n Very fast and very slow-moving items competing for the same warehouse spacen Customer demand for order accuracy and perfect order timing

03/15/2013 PUBLIC 15/92

2 SAP EWM Overview2.1 Introduction to SAP EWM

n Vast product differences - size, weight, model year, serial number, country of origin, batch andvaluation

n Complex cross-docking and order fulfillment processesn Integration of third-party logistics services for packaging (inbound processing) and packing

(outbound processing) of productsn Detailed packaging and shipping logistics with support for master bill of lading and a variety

of packaging optionsn Control of work processes inside and outside the warehouse such as bundling, waves, spreading,

resource management, work order, kitting, labeling, outside dock and yard managementn Third-party logistics and outsourcing support for consolidators and carriers using portal

capabilities

SAP EWM offers support for advanced storage and fulfillment that was only previously available innon-integrated, niche solutions; the advanced capabilities provided aim to dramatically improveservice levels while reducing working capital and labor expense.In addition to SAP EWM, the generic Business Scenario: Dock Appointment Scheduling [page 57] offers thefollowing capabilities:

n Planning for the WarehousePlanning of vehicle arrivals at the warehouse, and loading and unloading of the vehicles, isimportant for managing the efficient running of the warehouse, and for balancing the workloadacross the working day. You can use SAP Dock Appointment Scheduling to schedule loadingappointments for loading and unloading vehicles and to get an overview of the workload of aloading point for each day.

n Planning for the CarrierFor a carrier, planning is important to reduce the amount of time when the vehicles are notavailable for use, for example, if they are waiting to be unloaded. Carriers with access to the systemcan plan loading appointments for their own vehicles directly in the system, and update details oftheir loading appointments.

n ExecutionExecution of appointments is possible at the warehouse. This means to get the overview of theloading or unloding processes of the vehicles by maintaining different status and point of times ofan appointment, for example the Arrival at Checkpoint.

This Master Guide provides a central starting point for the technical implementation of the genericBusiness Scenario: Warehouse Management with Preconfigured Processes [page 33], which consists of the followingbusiness processes:

n Inbound Process Without Packing Information (Manual Goods Receipt) [page 35]n Inbound Process Without Packing Information (Manual Warehouse Task) [page 36]n Inbound Process with Repacking for Putaway [page 38]n Customer Returns with Quality Inspection [page 39]n Automatic Replenishment [page 43]

16/92 PUBLIC 03/15/2013

2 SAP EWM Overview2.1 Introduction to SAP EWM

n Outbound Process Using Pick-HUs as Shipping HUs [page 40]n Outbound Process Using Wave, Pick-HU, Packing, Staging, and Loading [page 42]n Unplanned Scrapping Due to Damaged Stock [page 44]n Periodic Physical Inventory [page 45]n Cycle Counting [page 46]

This Master Guide also provides a central starting point for the technical implementation of thegeneric Business Scenario: Integration of Outbound Warehousing and Transportation [external document], whichconsists of the following business processes:

n Managing Order-Based Outbound Processes (EWM-ERP-TM) [page 50]n Handling Cancellation in Order-Based Outbound Processes (EWM-ERP-TM) [page 51]n Managing Delivery-Based Outbound Processes (EWM-ERP-TM) [page 53]n Planning Transportation (EWM) and Billing (TM) in Outbound Processes [page 54]

The following industry scenarios are part of separate Industry Master Guides:

n Warehouse and DC ManagementFor more information, see theMaster Guide of SAP for Retail on the SAP Service Marketplace athttp://service.sap.com/instguides under Industry Solutions Industry Solution Guides SAPfor Retail .

n Service Parts WarehousingFor more information, see theMaster Guide of SAP Service and Asset Management on the SAP ServiceMarketplace at http://service.sap.com/instguides under Industry Solutions Industry SolutionGuides SAP Service & Asset Management .

This Master Guide also provides a central starting point for the technical implementation of thefollowing generic business processes:

n Inbound Process With Stock-Specific UoM (Manual Goods Receipt) [page 59]n Inbound Process With Stock-Specific UoM (Manual Warehouse Task) [page 60]n SUoM in Outbound Processes [external document]n Integration with Transportation [page 74] (LE-TRA component in ERP )n Outbound Process with Cartonization Planning [page 63]n Inbound Processing and Receipt Confirmation with Warehouse Management in SCM [page 64]n Outbound Processing with Warehouse Management in SCM [page 66]n Warehousing & Storage in SCM [page 67]n Physical Inventory on Storage Bin Level in SCM [page 68]n Merchandise Distribution [page 69]n Opportunistic Cross-Docking [page 70]n Unpacked Inbound Delivery from Vendor (with Manual GR and Automatic WT) [page 71]n Unpacked Inbound Delivery from Vendor (with Manual WT and Automatic GR) [page 72]

03/15/2013 PUBLIC 17/92







2 SAP EWM Overview2.2 Software Component Overview

2.2 Software Component Overview

This section provides information about:

n Application components of SAP EWMn Additional application components (not part of EWM) used in EWM processesn Additional technology components (not part of EWM) used in EWM processes

2.2.1 Application Components

The following content component versions are part of SAP Extended Warehouse Management:

n EWM Standalone

n EWM on SAP SCM

n EWM on SAP ERP

Note

SAP Dock Appointment Scheduling (DAS) is included in all content component versions of SAPEWM and must not be installed separately.

Application Components of EWM

EWM Standalone

The EWM Standalone component hosts the functionality of SAP Extended Warehouse Managementbased on SAP enhancement package 1 for SAP NetWeaver 7.3 (Application Server ABAP) and containsthe following software component versions:

Name Release Description

EA-IPPE 400 SAP Integrated Product and ProcessEngineering 400

SCMEWM 900 Extended Warehouse Management9.00

MDG_FND 731 MDG Foundation 731

QIE 200 QIE 200 (Quality Inspection Engine)

SAP_AP 700 SAP Application Platform 7.00

SCM_BASIS 702 SAP SCM BASIS 7.02

WEBCUIF 731 SAP Web UIF 731

SAP_BS_FND 731 SAP Business Suite Foundation 703

SCMBPLUS 702 SCM Basis PLUS 7.02

18/92 PUBLIC 03/15/2013


You can install the EWM Standalone component on the same system as Transportation Management(see the section on System Landscape [page 29]).

EWM on SAP SCM

The EWM on SAP SCM component hosts the functionality of SAP Extended Warehouse Managementbased on SAP enhancement package 2 for SAP SCM 7.0 (SCM Server) and contains the followingsoftware component versions:



No additional software component version is required as the SCM installation already containssoftware component versions used by SAP EWM.

EWM on SAP ERP

The EWM on SAP ERP component hosts the functionality of SAP Extended Warehouse Managementbased on SAP enhancement package 6 for SAP ERP 6.0 (SAP ECC Server) and contains the followingsoftware component versions:



QIE 200 QIE 200 (Quality Inspection Engine)

SCM_BASIS 702 SAP SCM BASIS 7.02

Content Components

The following content component versions are also part of SAP EWM:

n XI Content: XI CONTENT EWM 9.00, XI CONTENT QIE 200, XI CONTENT SCM BASIS 7.02,XI CONTENT SCM BASIS IC 7.02

n For additional content (for example, BI Content), see on SAP Service Marketplace athttp://service.sap.com/swdc under Support Packages and Patches Browse our Download CatalogSAP Content or under Installation and Upgrades Browse our Download Catalog SAP Content .

Note

As of SAP NetWeaver 7.0 BI Content Add-On 7 SP02, business intelligence (BI) content is availablefor SAP EWM 9.0. This enables you to use the BI reporting and analytic tools to evaluate, analyze,and interpret your business data. Analyzing logistics information on a strategic level is a criticalrequirement for easily summarizing and reporting the vast amounts of data such as quantities,volumes and weights handled by warehouses.

03/15/2013 PUBLIC 19/92



Additional Application Components

This section provides information about additional software components (not part of EWM) thatcan be used for specific scenarios or processes:

n SAP ERP

n SAP Transportation Managementn Plant Connectivityn SAP Supply Chain Management Server (SCM Server)n SAP Solutions for Auto-ID and Item Serialization (including SAP Event Management)n SAP CRM

n SAP Global Trade Services

SAP ERP

SAP ERP consists of different product instances and software components, each representing aparticular functional piece of the software. For more information, see the Master Guide for SAP ERPon SAP Service Marketplace at http://service.sap.com/instguides under SAP Business SuiteApplications SAP ERP SAP ERP 6.0 Planning .The following table gives an overview of the SAP ERP business functions required for EWM functionsand processes.

EWM Release New Functions andProcesses

CorrespondingSAP ERPRelease

SAP ERP BusinessFunctions Required forthe New EWMFunctionsand Processes

Goods receiptenhancements (basedon expected good receipt,fromproduction,withoutreference, tolerancechecks)

Kit to stock

Kit to order without CRM

Catch weight with EWMonly(Catch weight usingIS-CW in addition needsSAP enhancementpackage 5 of SAP ERP6.0)

Enhanced serial numberhandling

Enhanced batchmanagement

SAP EWM 2007 (5.1) SAP enhancementpackage 3 for SAP ERP6.0

LE, Extended WarehouseManagement Integration(LOG_LE_INTEGRATION)This business functionis recommended for allEWM business processescommunicating withERP.

20/92 PUBLIC 03/15/2013





EWM Release New Functions andProcesses

CorrespondingSAP ERPRelease

SAP ERP BusinessFunctions Required forthe New EWMFunctionsand Processes

Manual outbounddelivery

Goods issue for accountreference

Production supply EWM Integrationinto Manufacturing(LOG_PP_EWM_MAN)

SAP EWM 7.0

Merchandisecross-docking

SAP enhancementpackage 4 for SAP ERP6.0

Retail, MerchandiseDistribution-SAPEWM Integration(ISR_RET_CD/FT_EWM)

EWM, Returns in theDistribution Network


Service Parts Management:Innovations in ERP(SPE_CI_1)

SAP enhancementpackage 1 for SAP EWM7.0

EWM, Integration withTransportation (LE-TRAcomponent of EWM)

SAP ERP 6.0 No business function isrequired. SAP ERP 6.0 issufficient.

EWM, Additional GTINs(EANs/UPCs) for Product

SCM, CIF Transferof Additional GTINs(EANs/UPCs) for Material(LOG_SCM_MEAN_INT)

SAP enhancementpackage 2 for SAP EWM7.0

Advanced returnsmanagement


Advanced Returns Management2 (OPS_ADVRETURNS_2)

Integration of OutboundWarehousing andTransportation

SAP enhancementpackage 6 supportpackage 4 for SAP ERP6.0

ERP-TMS: Order andInvoice Integration(LOG_TM_ORD_INT_II)

Inbound Process WithStock-Specific UoM(Manual Goods Receipt)


No business functionis required but SAPNote 1612190 must beimplemented.

Inbound Process WithStock-Specific UoM(Manual WarehouseTask)


No business functionis required but OSSnote 1612190 must beimplemented.

SAP EWM 9.0

Outbound Process WithStock-Specific UoM


No business functionis required but OSSnote 1612190 must beimplemented.

03/15/2013 PUBLIC 21/92



For information about the enhancement packages for SAP ERP that are relevant forthe business process that you want to implement, see SAP Service Marketplace athttp://service.sap.com/instguides under SAP Business Suite Applications SAP ERP SAP ERP6.0 SAP enhancement packages for SAP ERP 6.0 .

SAP Transportation Management

Transportation costs have become an important factor in our economy. This is caused by increasingfuel costs and the highly increased demand to move goods within a more and more globalizedbusiness environment. Furthermore, the transportation market is highly competitive, which tends tolead to low margins in this sector. To operate private fleets efficiently, regardless of whether you are amanufacturer, retailer, or logistics service provider, you need to be able to plan your transportationneeds in an efficient way. SAP Transportation Management allows you to:

n Determine the most efficient transportation plan, while fulfilling the given constraints (such asservice level agreements, costs, and resource availability)

n Identify cost-saving opportunities (such as consolidation possibilities and the choice of the bestmeans of transport)

n Maximize the utilization of existing resources (such as using your own fleet)n React to execution events and solve possible conflicts with the initial plan

For more information, see the Master Guide for SAP TM on SAP Service Marketplace athttp://service.sap.com/instguides under SAP Business Suite Applications SAP TM Using SAPTM 9.0 .You can use Transportation Management in EWM processes involving Transportation Planningor Freight Order Settlement functions in TM.

Plant Connectivity

PCo provides connectivity services for the manufacturing industry, in particular unsoliciteddata notification services: In this way it enables the manufacturing integration between real-timemanufacturing systems and SAP applications. PCo is a highly extensible infrastructure on whichto build manufacturing applications. Through SAP MII, PCo can query real-time, historical, andstatistical data for agents that support such queries. PCo can write current and historical datafor specific agents. For more information, see the Master Guide for Plant Connectivity on SAPService Marketplace at http://service.sap.com/instguides under SAP Business Suite Applications SAPManufacturing Plant Connectivity Plant Connectivity 2.2 .You can use Plant Connectivity in EWM processes involving Material Flow System (MFS) forconnecting up a programmable logic controller (PLC) without the need for an additional warehousecontrol unit or in EWM processes using a scale connection.

SAP Supply Chain Management Server (SCM Server)

SAP Supply Chain Management Server (SAP SCM Server) is part of the SAP Supply ChainManagement application. It is an advanced planning and scheduling tool that enables real-time

22/92 PUBLIC 03/15/2013






decision support and collaborative network optimization across the extended supply chain. SAP SCMServer helps companies synchronize supply chain activities with their partners and excel at customerservice and order fulfillment. For more information, see the Master Guide for SAP SCM on SAPService Marketplace at http://service.sap.com/instguides under SAP Business Suite Applications SAPSCM SAP SCM Server Using SAP enhancement package 2 for SAP SCM Server 7.0 .You can use the SCM Server in EWM processes using functions such as availability check or slotting.

SAP Solutions for Auto-ID and Item Serialization

SAP solutions for auto-ID and item serialization enable the use of radio frequency identification(RFID) and other means of automatic identification such as bar codes to provide accurate, real-timeinformation about items as they move through your supply chain and to automate your businessprocesses. For more information, see theMaster Guide for SAP Solutions for Auto-ID and Item Serializationon SAP Service Marketplace at http://service.sap.com/instguides under SAP Business SuiteApplications SAP SCM SAP Auto-ID Infrastructure SAP Auto-ID Infrastructure 7.1 .SAP Solutions for RFID consist of the following offerings:

n SAP Auto-ID InfrastructureSAP Auto-ID Infrastructure is a flexible and customizable infrastructure that integrates RFIDtechnology with existing SAP logistics systems. It provides standard content that enables you toautomate and RFID-enable basic logistics processes, but also provides extensible capabilities thatallow you to easily adapt the standard content to implement your own customer-specific processes.

n SAP Auto-ID EnterpriseYou can install multiple local instances of the component SAP Auto-ID Infrastructure andimplement an SAP object event repository to collect data centrally from across your enterpriseand from your business partners. You can use the repository to query, manage, and monitoryour processes centrally.

n SAP Object Event RepositoryYou can use SAP object event repository (the repository) to capture, store, and query data aboutuniquely identified objects centrally in a disparate system landscape. You can automaticallycapture information about object-level events that occur across your supply chain, from bothwithin your enterprise and from your business partners. You can access the data in the repositoryand your business partner can use XML messages to query it. By enabling disparate applicationsto exchange information about uniquely identified objects, the repository provides visibility andtraceability of the objects throughout their respective lifecycles. Furthermore, you can use therepository to monitor business documents related to the objects.

n SAP Event ManagementSAP EventManagement allows you to track and query events across your supply chain and therebyprovides or improves visibility within your logistics processes, both in planning and in execution.The flexibility of the application allows you to map, control, and check all required businessprocesses. SAP Event Management is an optional component in SAP Auto-ID Infrastructure

03/15/2013 PUBLIC 23/92





processes. If you install SAP object event repository, it is also possible to use the standalonefunctionality of SAP Event Management.

SAP CRM

SAP Customer Relationship Management (SAP CRM) is a complete multichannel suite supportingall customer-facing lines of business across marketing, sales, and service, as well as customerinteraction channels such as the interaction center, the Internet, and mobile clients. Formore information, see the Master Guide (Including Upgrade Information) for SAP CustomerRelationship Management 7.0 Including SAP Enhancement Package 2 on SAP Service Marketplaceat http://service.sap.com/instguides under SAP Business Suite Applications SAP CRM SAPEnhancement Package 2 for SAP CRM 7.0 Plan .You can use CRM in EWM processes using functions such as invoice before goods issue.

SAP Global Trade Services

You can use SAP BusinessObjects Global Trade Services as enterprise-wide, centralized applicationthat enables your company to comply with worldwide trade regulations, communicate electronicallywith customs authorities and manage information that is relevant to foreign trade. It providesreporting features, especially for audits, that enable you to handle changing import and exportrequirements and controls. The solution is designed to be integrated with multiple SAP andnon-SAP systems in a heterogeneous environment. It can be implemented without changing yourexisting logistics processes. For more information, see the Master Guide for SAP GTS on SAP ServiceMarketplace at http://service.sap.com/instguides under SAP Components SAP Global TradeServices Using SAP GTS 10.0 .You can use GTS in EWM processes involving Customs Management functions such as licensemanagement for import and export controls or Compliance Management functions such as customscommunication services for imports, exports and special customs procedures.

2.2.2 Technology Components

This section provides information additional technology components (not part of EWM) neededfor specific processes.

SAP NetWeaver 7.0 or higher, Usage Type PI (Process Integration)

Based on a native Web infrastructure that leverages open standards, SAP NetWeaver ProcessIntegration (SAP NetWeaver PI) makes it possible to manage the broad diversity of highlyheterogeneous components from a multitude of vendors and to run in various technologyenvironments. The integration capabilities capture shared business semantics and act as a mediatorbetween the services and their technical implementations. It includes technical functions, such asWeb service discovery, queuing, mapping, and routing. It also establishes an infrastructure for businessprocess management and high-performance execution within and across organizational boundaries.

24/92 PUBLIC 03/15/2013




Exchange-based process integration removes the problems of direct connections by extracting sharedcollaboration knowledge. These shared business semantics ease the integration of both external andinternal components. Instead of directly coding point-to-point interfaces for each new component,the exchange infrastructure allows instant plug-in of new components once per component. Thisprovides the flexibility needed in today’s fast-changing business world, and it reduces integration costscompared to the direct connection approach.

Additional Information Regarding Enterprise Services

Enterprise services are shipped with SAP EWM.There are two technical scenarios for enterprise services:

n Using asynchronous enterprise services (EWM services)To run asynchronous enterprise services, installation of an SAP NetWeaver Process Integration (PI)is required. Note that SAP EWM services run with an SAP ERP system for message exchange.

n Using synchronous enterprise services (EWM services):There are two ways to run synchronous enterprise services: Access the back-end system viaWSDL/SOAP runtime directly or access the back-end system via SAP NetWeaver PI runtime(synchronous mediated). The latter requires an SAP NetWeaver PI integration server.

For more information about the required releases and support packages, see the respective sectionsabout the SAP EWM business processes.

Setting Up the Documentation Infrastructure for Enterprise Services

Enterprise services documentation runs with SAP Solution Composer, which is part of SAP SolutionManager.For more information about how to set up the documentation infrastructure for enterprise services,see About This Document in the Master Guide for Enterprise Services for SAP Business Suite on SAPService Marketplace at http://service.sap.com/instguides under SAP Business Suite ApplicationsSAP ERP SAP ERP 6.0 SAP enhancement packages for SAP ERP 6.0 SAP enhancement package 6 for SAPERP 6.0 .

Additional Information Regarding SAP Visual Business

SAP Visual Business is a user interface for visualizing data from various sources in interactivegeographical or three-dimensional applications. In SAP EWM 9.0, SAP Visual Business is used tovisualize route data on geographical maps. This provides a seamless integration of maps into theuser interface of SAP EWM 9.0. You must install a front-end client before you can use SAP VisualBusiness. For more information about SAP Visual Business, see the corresponding Installation andConfiguration Guide on SAP Service Marketplace at http://service.sap.com/instguides.

Additional Information Regarding Printing

EWM supports printing using Smartform forms and PDF-based forms. If you want to printdocuments such as delivery notes or bills of lading as PDF-based forms, you require Adobe Document

03/15/2013 PUBLIC 25/92



2 SAP EWM Overview2.3 Software Component Matrix

Services (ADS). For more information, see Configuration of Adobe Document Services for PrintApplications in SAP Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com/nw.

2.3 Software Component Matrix

This section provides an overview of which business scenario of SAP EWM uses which software unit.For information about the latest component version and patch level requirements, see SAP SupportPackage on SAP Service Marketplace at http://service.sap.com/sp-stacks.

Note

This Guide describes just one way to implement each business process. This is the implementationvalid for SAP EWM 9.0.For other ways to implement business processes, see the Scenario & Process Component List on SAPService Marketplace at http://service.sap.com/scl. The Scenario & Process Component Listhelps you to find realization alternatives for SAP solutions, business scenarios and processes. It showsyou which application components are needed to realize a business scenario or process.

Software ComponentsBusinessProcesses

SAP EWM 9.0 SAP ERP 6.0 SAP enhancementpackage <No.> forSAP ERP 6.0

Other SoftwareUnits

Inbound ProcessWithout PackingInformation(Manual GoodsReceipt)

X X EHP3

Inbound ProcessWithout PackingInformation(Manual WarehouseTask)

X X EHP3

Inbound Processwith Repacking forPutaway

X X EHP3

Customer Returnswith QualityInspection

X X EHP3

AutomaticReplenishment

X X EHP3

26/92 PUBLIC 03/15/2013

http://help.sap.com/nw

http://service.sap.com/sp-stacks







Other SoftwareUnits

Outbound ProcessUsing Pick-HUs asShipping HUs

X X EHP3

Outbound ProcessUsing Wave,Pick-HU, Packing,Staging, andLoading

X X EHP3

UnplannedScrapping Due toDamaged Stock

X X EHP3

Periodic PhysicalInventory

X X EHP3

Cycle Counting X X EHP3

Outbound Processwith CartonizationPlanning

X X EHP3

Inbound Processing& ReceiptConfirmationwith WarehouseManagement inSCM

X X -

OutboundProcessing withWarehouseManagement inSCM

X X -

Warehousing &Storage in SCM

X X -

Physical Inventoryon Storage Bin Levelin SCM

X X -

MerchandiseDistribution

X X EHP4

Opportunistic CrossDocking

X X -

03/15/2013 PUBLIC 27/92




Other SoftwareUnits

Unpacked InboundDelivery fromVendor (withManual GR andAutomatic GR)

X X -

Unpacked InboundDelivery fromVendor (withManual WT andAutomatic GR)

X X -

Integration withTransportation(LE-TRA)

X X -

ManagingOrder-BasedOutbound Processes(EWM-ERP-TM)

X X EHP6 (SP4) SAP TM 9.0

HandlingCancellationin Order-BasedOutbound Processes(EWM-ERP-TM)


ManagingDelivery-BasedOutbound Processes(EWM-ERP-TM)


PlanningTransportation(EWM) and Billing(TM) in OutboundProcesses


Inbound Processwith SUoM(ManualGR)

X X EHP6

Inbound Processwith SUoM(ManualWT)

X X EHP6

Outbound Processwith SUoM

X X EHP6

28/92 PUBLIC 03/15/2013

2 SAP EWM Overview2.4 System Landscape



Other SoftwareUnits

Dock AppointmentScheduling

X - -

Processing DockAppointmentScheduling

X -

Legend

n X: Mandatoryn -: Not part of the business process

2.4 System Landscape

SAP EWM 9.0 can be installed as follows:

n As standalone application (add-on) based on NetWeavern As add-on for SAP ERP

n As add-on for SAP Supply Chain Management

The following figure provides three examples for a minimal system landscape for SAP EWM. You canuse the same landscape for SAP Dock Appointment Scheduling, as it is included in the SAP EWMinstallation.

03/15/2013 PUBLIC 29/92

2 SAP EWM Overview2.4 System Landscape

Figure 1: Examples for Minimal System Landscape for SAP EWM

Caution

We strongly recommend that you use a minimal system landscape for test and demo purposes only.For performance, scalability, high availability, and security reasons, do not use a minimal systemlandscape as your production landscape.

The following figure provides an overview of a possible system landscape for SAP EWM, installedtogether with SAP Transportation Management and SAP Event Management as application basedon NetWeaver.For more information about the additional components installed on separate servers, see the sectionon Software Units for EWM in the Master Guide for SAP EWM 9.0.

30/92 PUBLIC 03/15/2013

2 SAP EWM Overview2.5 Overall Installation Sequence

Figure 2: Example System Landscape for SAP EWM

2.5 Overall Installation Sequence

The following table describes the overall installation sequence for SAP EWM. This table contains allavailable software units. However, to implement a specific scenario, you only need a subset of availablesoftware units. Some are only required for special processes. For information about which software isrequired to implement a specific scenario, see Software Component Matrix.For the latest component version and patch level requirements, see SAP Service Marketplace athttp://service.sap.com/sp-stacks.For documentation listed in the following table, see References.

SAP Netweaver for EWM Standalone

Installation of SAP NetWeaver 7.3 including SAPenhancement package 1

For more information, seehttp://service.sap.com/installNW73.

ERP Server for EWM as an Add-On to SAP ERP

Installation of SAP ERP 6.0 including SAPenhancement package 6

For more information, seehttp://service.sap.com/instguides un-der SAP Business Suite Applications SAP ERP SAPERP 6.0 SAP enhancement packages for SAP ERP 6.0SAP enhancement package 6for SAP ERP 6.0 .

03/15/2013 PUBLIC 31/92

http://service.sap.com/sp-stacks

http://service.sap.com/installNW73



2 SAP EWM Overview2.5 Overall Installation Sequence

SCM Server for EWM as an Add-On to SAP SCM

Installation of SAP SCM Server 7.0 including SAPenhancement package 2

For more information, seehttp://service.sap.com/instguides un-der SAP Business Suite Applications SAP SCM SAPSCM Server Using SAP enhancement package 2 for SAPSCM 7.0 .

PI Server

Step Action Remarks and Subsequent Steps

1 Installation of SAP NetWeaver 7.0 orhigher Usage Type PI

For more information, seehttp://service.sap.com/installNW70

or http://service.sap.com/installNW73.

2 Installation of Process IntegrationContext (XI Content) for SAP EWM 9.0

You can download the XI content for SAPEWM ES from SAP Service Marketplaceat http://service.sap.com/swdc underSupport Packages and Patches Support Packages and

Patches—Search for Support Packages and PatchesEWM 9.0 .

BI Server

Step Action Remarks and Subsequent Steps

1 Installation of SAP NetWeaver7.0 including SAP enhancementpackage 3 or higherUsage type BI

For more information, seehttp://service.sap.com/installNW70

orhttp://service.sap.com/installNW73

2 BI Content 7x7 or higher You can download the BIcontent for SAP EWM fromSAP Service Marketplace athttp://service.sap.com/swdc.

Business Functions

In SAP EWM 9.0, the following business function is available:

Name Description

SCM_EWM_FND EWM, Essential Foundation Functions

This business function SCM_EWM_FND is mandatory for all EWM business processes described in thisguide.

32/92 PUBLIC 03/15/2013













3 Business Scenario: Warehouse Management with Preconfigured Processes

3 Business Scenario: WarehouseManagement with PreconfiguredProcesses

This business scenario contains basic business processes used in a warehouse managed with SAPExtended Warehouse Management (EWM).As warehousing processes strongly depend on the warehouse structure and on the products stored inthe warehouse, all processes are integrated in a standard warehouse with a predefined structure anduse commonmaster data such as business partners, products, packaging specifications, and resources.The processes interact with each other and build a consistent product flow. For example, in aninbound process, you receive goods from vendors and store them on pallets in the warehouse. In anoutbound process, you pick cartons or eaches of the same goods from a picking area to pack and shipthem to customers. If the stock in the picking area falls below a predefined threshold, EWM triggersan automatic replenishment process to move cartons from the pallets to the picking area.The business process descriptions include not only the system and user activities, but also the physicalactivities in the warehouse. For this reason, some process steps are not carried out in the system.The business processes contain typical EWM functions. For example, some processes are paper-based,while others make use of radio frequency devices. Some use handling units to manage packed goods,while others use alternative units of measure for the same purpose. The processes also includemonitoring, printing, scanning, and integration to SAP ERP.You can use this business scenario to accelerate your EWM implementation. It is the recommendedway for getting started with EWM.This business scenario contains the following business processes. All processes run in parallel inthe warehouse:

n Inbound Process Without Packing Information (Manual GR)

n Inbound Process Without Packing Information (Manual WT)

n Inbound Process with Repacking for Putaway

n Customer Returns with Quality Inspection

n Outbound Process Using Pick-HUs as Shipping HUs

n Outbound Process Using Wave, Pick-HU, Packing, Staging, and Loading

n Automatic Replenishment

n Unplanned Scrapping Due to Damaged Stock

n Periodic Physical Inventory

n Cycle Counting

03/15/2013 PUBLIC 33/92

3 Business Scenario: Warehouse Management with Preconfigured Processes

Technical System Landscape

The following software components are either mandatory or optional, as indicated below, for thetechnical implementation of this scenario.The following table provides just one way to implement the business process. For other combinations,see http://service.sap.com/scl.

Software Units

Component Mandatory Optional

SAP ERP 6.0 X −

SAP enhancement package 3 forSAP ERP 6.0

X −

SAP EWM 9.0 X −

Further Information

The following documents provide more information about this business scenario:

Content Location

Scenario Description

Configuration Documentation

The scenario description is part of SAPSolution Manager implementationcontent ST-ICO 150_700 SP34. For moreinformation about SAP Solution Manager, seehttp://service.sap.com/solutionmanager.

Basic Settings for Warehouse Management with Preconfigured Processes

To implement SAP Extended Warehouse Management (EWM) 9.0 with the business scenarioWarehouseManagement with Preconfigured Processes, you need to consider basic configuration settings. Therefore, inSAP Solution Manager, you need to add the basic settings manually in the following way:

1. In transaction SOLAR02, select the structure node Configuration.2. On the Structure tab page, select the Change Configuration Structure button.3. On the Structure tab page, select the value help for the Configuration Element field.4. In the displayed structure, choose the basic settings under Solutions/Applications SAP EWM

Basic Settings for SAP EWM 9.0 .

The following basic settings are relevant for the business scenario:

n Integration of SAP ERP with SAP EWM

n Configuration of Warehouse Structure and Master Data for SAP EWM

34/92 PUBLIC 03/15/2013




http://service.sap.com/solutionmanager


3 Business Scenario: Warehouse Management with Preconfigured Processes3.1 Inbound Process Without Packing Information (Manual Goods Receipt)

3.1 Inbound Process Without Packing Information (ManualGoods Receipt)

Overview

You use this business process to receive goods on pallets from external vendors. Each pallet containsonly a single product. You do not receive packing information from the vendors, but some vendorssend advanced shipping notifications (ASN) to SAP ERP. You check the goods in the goods receiptarea, and post the goods receipt (GR) in SAP Extended Warehouse Management (EWM). Upon GRposting, warehouse orders (WOs) are created. Depending on the product attributes, you move thegoods to different areas in the warehouse using the information contained in the printed WOs. Youmove uncategorized products to a clarification zone before you put them away.When a truck arrives, a checkpoint clerk directs the truck to a door. The truck driver brings thedelivery note to the GR office. If the vendor has sent an ASN to SAP ERP, a GR office clerk finds thecorresponding inbound delivery in EWM. If there is no inbound delivery in the system, the GR officeclerk creates it in EWM. A warehouse worker unloads the truck. A warehouse clerk checks the goodsagainst the delivery note, writes differences on the delivery note, and takes the revised delivery noteto the GR office. The GR office clerk posts the GR. Upon GR posting, the system automaticallycreates and prints WOs for the inbound delivery to move the goods into the warehouse. The truckleaves. The warehouse worker moves the goods from the GR area into the warehouse. The goodsare then moved to the following storage types:

n A storage type for small parts, which is subdivided for slow-moving and fast-moving itemsn A storage type for large parts, where fixed storage bins are used

In the storage type for small parts, the next empty storage bin is determined as the destination storagebin. Products that have not yet been categorized as small or large parts, or that have no fixed binassignment, are moved into a separate storage type for clarification. When the goods are in thedestination storage bins, the warehouse clerk confirms the putaway WOs.

This process is used in the following scenarios:

Scenario Solution/Scenario Group

Warehouse Management with Preconfigured Processes -


The following software components are either mandatory or optional, as indicated below, for thetechnical implementation of this process.The following table provides just one way to implement the business process. For other combinations,see http://service.sap.com/scl.

03/15/2013 PUBLIC 35/92




3 Business Scenario: Warehouse Management with Preconfigured Processes3.2 Inbound Process Without Packing Information (Manual Warehouse Task)

Software Units


SAP ERP 6.0 X −


X −

SAP EWM 9.0 X −

For more information about the installation of these components, see System Landscapes [page 29].

Further Information

The following documents provide more information about this business process:

Content Location

Process Description


Test Case

The process description is part of SAPSolution Manager implementationcontent ST-ICO 150_700 SP34. For moreinformation about SAP Solution Manager, seehttp://service.sap.com/solutionmanager.

3.2 Inbound Process Without Packing Information (ManualWarehouse Task)

Overview

You use this business process to receive goods on pallets from external vendors. Each pallet containsonly a single product. You do not receive packing information from the vendors, but some vendorssend advanced shipping notifications (ASN) to SAP ERP. You check the goods in the goods receipt(GR) area, and create warehouse orders (WOs) in SAP Extended Warehouse Management (EWM).Depending on the product attributes, you move the goods to different areas in the warehouse usingthe information contained in the printed WOs. You move uncategorized products to a clarificationzone before you put them away. When you confirm the WOs, the system automatically posts the GR.When the truck arrives, a checkpoint clerk directs the truck to a door. The truck driver brings thedelivery note to the GR office. If the vendor has sent an ASN to SAP ERP, a GR office clerk finds thecorresponding inbound delivery in EWM. If there is no inbound delivery in the system, the GR officeclerk creates it in EWM. A warehouse worker unloads the truck. A warehouse clerk checks the goodsagainst the delivery note, writes differences on the delivery note, and takes the revised deliverynote to the GR office. The GR office clerk creates WOs for the inbound delivery to move the goodsinto the warehouse. The system automatically prints the WOs. The truck leaves. The warehouseworker moves the goods from the GR area into the warehouse. The goods are then moved to thefollowing storage types:

36/92 PUBLIC 03/15/2013



3 Business Scenario: Warehouse Management with Preconfigured Processes3.2 Inbound Process Without Packing Information (Manual Warehouse Task)

n A storage type for small parts, which is subdivided for slow-moving and fast-moving itemsn A storage type for large parts, where fixed storage bins are used

In the storage type for small parts, the next empty storage bin is determined as the destination storagebin. Products that have not yet been categorized as small or large parts, or that have no fixed binassignment, are moved into a separate storage type for clarification. When the goods are in thedestination storage bins, the warehouse clerk confirms the putaway WOs. Upon the confirmation ofthe putaway WOs, the system automatically posts the GR.



Warehouse Management with Preconfigured Processes .-



Software Units


SAP ERP 6.0 X −


X −

SAP EWM 9.0 X −


Further Information


Content Location

Process Description


Test Case


03/15/2013 PUBLIC 37/92






3 Business Scenario: Warehouse Management with Preconfigured Processes3.3 Inbound Process with Repacking for Putaway

3.3 Inbound Process with Repacking for Putaway

Overview

You use this business process to receive packed goods from vendors and repack them at a packingstation before moving them to a pallet rack in the warehouse. The vendors send advanced shippingnotifications (ASNs) to SAP ERP. A truck contains one or more inbound deliveries. The goods arepacked by the vendors but must be repacked for putaway purposes so that each pallet contains only asingle product.When a truck arrives, a checkpoint clerk creates a transportation unit (TU) in SAP ExtendedWarehouse Management (EWM) and directs the truck to a door. The truck driver brings the deliverynotes to the goods receipt (GR) office. A GR office clerk finds the corresponding inbound deliveriesin the system and assigns them to the TU. If the number of handling units (HUs) is printed on thedelivery notes, the GR office clerk creates HUswith unknown content for the deliveries, and prints thelabels for the HUs. A warehouse worker unloads the truck. A warehouse clerk checks the quantitieson the pallets and attaches the labels to the pallets at the staging area. If the number of HUs is notprinted on the delivery notes, the warehouse clerk counts the number of unloaded pallets and writesthem on the delivery notes. He or she then takes the revised delivery notes to the GR office. The GRoffice clerk corrects the GR quantities; if necessary he or she creates HUs with unknown content, andposts the GR. He or she checks out the truck and the truck leaves the door and the premises. Uponthe GR posting, the system automatically creates HU warehouse tasks (WTs) to move all pallets ofthe deliveries to a storage bin in the inbound section of the packing station. At the packing station, apacker repacks the goods onto pallets for storage. Once an HU is closed in the system, the systemautomatically creates the HUWTs for the putaway of the pallet into the final storage bin. A warehouseworker (for example, a forklift driver) executes the putaway using a radio frequency (RF) device.






Software Units


SAP ERP 6.0 X −

38/92 PUBLIC 03/15/2013




3 Business Scenario: Warehouse Management with Preconfigured Processes3.4 Customer Returns with Quality Inspection



X −

SAP EWM 9.0 X −


Further Information


Content Location

Process Description


Test Case


3.4 Customer Returns with Quality Inspection

Overview

You use this business process to handle customer returns. In this process, only small quantities(for example, single pieces) are returned. When you receive the rejected goods, you perform a100% inspection. The quality inspection is triggered and carried out in SAP Extended WarehouseManagement (SAP EWM). Depending on the inspection result, you decide if the goods are put awayor scrapped.By phone, a customer informs a sales clerk about a coming return and requests an identifier for it.The sales clerk creates a returns delivery and communicates the number to the customer. Thecustomer labels the goods with the delivery number and returns them. A truck arrives with therejected goods. When the goods are unloaded, a goods receipt (GR) office clerk posts the GR. Aquality inspection (QI) document is created automatically. A warehouse worker brings the rejectedgoods to the QI work center. A QI specialist checks the goods. He or she packs undamaged goods intocartons and puts damaged goods into a wire basket. He or she also enters the decision codes in thesystem. According to the decision codes, the system creates warehouse orders (WOs) for moving thegoods to the putaway bins or to the scrapping zone. The putaway WOs are printed automatically.The QI specialist attaches the printouts to the corresponding cartons. The warehouse worker bringsthe cartons with the undamaged goods to the final bins and passes the printouts to the internaloffice. A warehouse clerk confirms the WOs in the system. The WOs for moving the damaged goodsto the scrapping zone are confirmed automatically. The warehouse worker brings the wire basketwith the damaged goods to the scrapping zone as soon as the wire basket is full. A backgroundjob runs regularly to empty the scrapping zone.

03/15/2013 PUBLIC 39/92



3 Business Scenario: Warehouse Management with Preconfigured Processes3.5 Outbound Process Using Pick-HUs as Shipping HUs






Software Units


SAP ERP 6.0 X −


X −

SAP EWM 9.0 X −


Further Information


Content Location

Process Description


Test Case


3.5 Outbound Process Using Pick-HUs as Shipping HUs

Overview

You use this business process to send high-priority ordered goods to external customers. Only smallquantities (for example, single pieces) are ordered by the customers. On a daily basis a trucks arrives atthe warehouse to transport the high-priority deliveries. Warehouse orders (WOs) are created duringoutbound delivery order creation and are used to optimize the picking process. Picking consists of asingle paper-based step using pick-handling units (HUs) that you ship to the customers. Using onetransportation route, you deliver goods to several customers.

40/92 PUBLIC 03/15/2013






3 Business Scenario: Warehouse Management with Preconfigured Processes3.5 Outbound Process Using Pick-HUs as Shipping HUs

Upon outbound delivery order creation, the system automatically assigns the outbound deliveryorders to routes. The system then creates warehouse tasks (WTs) and warehouse orders (WOs)automatically, and the warehouse activities begin. The WOs are printed as a work list for a paper-basedpicking. A warehouse worker takes the printout of a WO and prepares a pick-HU to be used forthe picking of the products listed on the WO printout. He or she then takes two labels with thesame external HU identifiers, and sticks one to the physical HU and the other to the printout of theWO. The warehouse worker carries out the picking for one or several pick-HUs, and brings thegoods to the staging area. The warehouse worker then hands over the printouts of the WOs to thewarehouse clerk responsible for the confirmation of the picking. With the confirmation of the WOs,the pick-HUs are created in the system. In the staging area a warehouse worker weighs and labelsthe HUs with the shipping label, and creates an outbound delivery for each HU. This triggers theprintout of a delivery note, which is put into the HU before the HU is physically closed. When thetruck arrives, it is checked in and directed to a door by a checkpoint clerk. Once the truck arrives atthe door, the warehouse worker commences the physical loading of the HUs. After he or she hasfinished the physical loading of all HUs for the route, a shipping office clerk posts the goods issue(GI), prints a second delivery note for each outbound delivery, and hands the delivery notes over tothe truck driver. The truck leaves the premises.






Software Units


SAP ERP 6.0 X −


X −

SAP EWM 9.0 X −


Further Information


03/15/2013 PUBLIC 41/92




3 Business Scenario: Warehouse Management with Preconfigured Processes3.6 Outbound Process Using Wave, Pick-HU, Packing, Staging, and Loading

Content Location

Process Description


Test Case


3.6 Outbound Process Using Wave, Pick-HU, Packing,Staging, and Loading

Overview

You use this business process to send ordered goods to external customers. In this process, you cansend bigger quantities (for example, cartons or pallets) to the customers. You pick the goods by wavesinto pick-handling units (pick-HUs) and consolidate them into shipping HUs at a packing station.You then stage the shipping HUs and load them into a truck before posting the goods issue. You usea separate route for each customer.When the outbound delivery orders are created, the system automatically assigns the outbounddelivery orders to routes depending on scheduled dates. After the route assignment, the outbounddelivery orders are assigned to picking waves automatically. A shipping office clerk orderstransportation capacity from the shipper for each route. After the confirmation by the shipper, theshipping office clerk creates transportation units (TUs) and assigns them to the route and a door usedfor this route. With the automatic release of the waves, the warehouse activities begin. Warehouseworkers pick the goods from different areas in the warehouse using radio frequency (RF) devices andbring them to a packing station where they are consolidated and packed into shipping HUs such aseuropallets. The packer attaches shipping labels to the shipping HUs. The shipping HUs are thenmoved to the staging area. When the truck arrives, it is checked in and directed to the door. Thegoods are loaded from the staging area into the truck. When the loading is complete, the shippingoffice clerk posts the goods issue (GI), prints the delivery notes and loading lists, and hands themover to the truck driver. The shipping office clerk checks out the truck and the truck leaves thedoor and the premises.





The following software components are either mandatory or optional, as indicated below, for thetechnical implementation of this process.

42/92 PUBLIC 03/15/2013



3 Business Scenario: Warehouse Management with Preconfigured Processes3.7 Automatic Replenishment

The following table provides just one way to implement the business process. For other combinations,see http://service.sap.com/scl.

Software Units


SAP ERP 6.0 X −


X −

SAP EWM 9.0 X −


Further Information

Content Location

Process Description


Test Case


3.7 Automatic Replenishment

Overview

You use this business process to fill up a picking area in accordance with the demand for productsthat you pick in this area. In this automatic replenishment process, you use warehouse orders (WOs)to carry out replenishment. The system creates replenishment WOs in the background when youconfirm a pick-WO and the stock in the source bin falls below a predefined threshold. The systemcalculates the replenishment quantity in accordance with the maximum and minimum quantitymaintained for the product in the product master.






03/15/2013 PUBLIC 43/92






3 Business Scenario: Warehouse Management with Preconfigured Processes3.8 Unplanned Scrapping Due to Damaged Stock

The following table provides just one way to implement the business process. For other combinations,see http://service.sap.com/scl.

Software Units


SAP ERP 6.0 X −


X −

SAP EWM 9.0 X −


Further Information

Content Location

Process Description


Test Case


3.8 Unplanned Scrapping Due to Damaged Stock

Overview

You use this business process to scrap damaged stock detected in the warehouse. You change thestock type of the damaged stock so that it is not available for sale anymore. In this process, you use awarehouse order (WO) to move the stock to a scrapping container in the scrapping zone. The WO iscarried out using a mobile device or paper. A background job runs regularly to empty the scrappingzone. A truck arrives to pick up the scrapping container.

Note

You can also use this business process to scrap stock due to expired best-before date/shelf lifeexpiration date (BBD/SLED).




44/92 PUBLIC 03/15/2013






3 Business Scenario: Warehouse Management with Preconfigured Processes3.9 Periodic Physical Inventory



Software Units


SAP ERP 6.0 X −


X −

SAP EWM 9.0 X −


Further Information

Content Location

Process Description


Test Case


3.9 Periodic Physical Inventory

Overview

You use this business process to control your warehouse stock and to meet legal requirements. Inthis process, you create physical inventory (PI) documents for a chosen number of storage bins orproducts on a regular basis to spread the PI workload over the year. You carry out the counting usinga radio frequency (RF) device or paper. By posting the PI documents, you adjust the book inventoryin SAP Extended Warehouse Management (SAP EWM). By posting the differences to SAP ERP, youbalance the stock accounts.You can monitor the progress of your PI by using the warehouse management monitor.

03/15/2013 PUBLIC 45/92






3 Business Scenario: Warehouse Management with Preconfigured Processes3.10 Cycle Counting






Software Units


SAP ERP 6.0 X −


X −

SAP EWM 9.0 X −


Further Information


Content Location

Process Description


Test Case


3.10 Cycle Counting

Overview

You use this business process as a product-specific physical inventory (PI) process that you perform atregular intervals to ensure inventory accuracy in your warehouse and to meet legal requirements.These intervals depend on the Cycle Counting Indicator field that you maintain for all products thatyou want to include in cycle counting. The Cycle Counting Indicator field reflects the classification ofyour products according to their impact on operations and finance. You can automatically classifyyour products and maintain the Cycle Counting Indicator field for the products, for example, withthe help of an ABC analysis in SAP Supply Chain Management (SAP SCM).

46/92 PUBLIC 03/15/2013






3 Business Scenario: Warehouse Management with Preconfigured Processes3.10 Cycle Counting

In this process, you create PI documents for all cycle-counting-relevant products that are due to becounted. You carry out the counting using a radio frequency (RF) device or paper. By posting the PIdocuments, you adjust the book inventory in SAP Extended Warehouse Management (EWM). Byposting the differences to SAP ERP, you balance the stock accounts.You can monitor the progress of your PI by using the warehouse management monitor.






Software Units


SAP ERP 6.0 X −


X −

SAP EWM 9.0 X −


Further Information


Content Location

Process Description


Test Case


03/15/2013 PUBLIC 47/92






4 Business Scenario: Integration of Outbound Warehousing and Transportation

4 Business Scenario: Integrationof Outbound Warehousing andTransportation

This business scenario contains outbound processes in which goods ordered by external customers arepicked from an own warehouse and transported by an external carrier to the customer. It integrateswarehousing with SAP Extended Warehouse Management (EWM) and transportation with SAPTransportation Management (TM). For the communication between TM and EWM, ERP shipmentsare used. SAP TM enables the customer to run a transportation planning based on sales orderrequirements or outbound deliveries in order to optimize transportation costs and efforts in a flexibleand optimized way. As transportation planning results influence the warehouse internal processessuch as, for example the staging (like for example when and where to stage what), the integrationof the SAP TM transportation planning result into SAP EWM warehouse management processes istherefore a high benefit as it enables a smooth outbound processing with an optimized warehouseinternal process according to the transportation planning result. This business scenario containsalternative outbound processes. All processes can run in parallel in the warehouse:

n Managing Order-Based Outbound Processes (EWM-ERP-TM)

n Handling Cancellation in Order-Based Outbound Processes (EWM-ERP-TM)

n Managing Delivery-Based Outbound Processes (EWM-ERP-TM)

n Planning Transportation (EWM) and Billing (TM) in Outbound Processes


The following software components are either mandatory or optional, as indicated below, for thetechnical implementation of this scenario. The following table provides just one way to implementthe business process. For other combinations, see http://service.sap.com/scl.


SAP ERP 6.0 X -

SAP enhancement package 6 forSAP ERP 6.0 (SP4)

X -

SAP EWM 9.0 X -

SAP TM 9.0 X -


03/15/2013 PUBLIC 49/92

4 Business Scenario: Integration of Outbound Warehousing and Transportation4.1 Managing Order-Based Outbound Processes (EWM-ERP-TM)

Further Information

The following documents provide more information about this business scenario:

Content Location

Scenario Description


The scenario description is part of SAP SolutionManager implementation content ST-ICO 150_700SP34. For more information about SAP SolutionManager, see http://service.sap.com/solutionmanager.

4.1 Managing Order-Based Outbound Processes(EWM-ERP-TM)

You use this integrated warehousing and transportation process to send ordered goods to externalcustomers from a warehouse managed with SAP Extended Warehouse Management (EWM). Thegoods are transported by an external carrier.In this process you plan the transportation in SAP Transportation Management (TM) on the basis ofsales orders created in SAP ERP. SAP TM proposes and creates deliveries based on dates and quantitiesaccording to transportation planning results, taking into account transportation constraints such asresource availability and transportation durations. The SAP TM system sends delivery proposals toSAP ERP, which creates the deliveries and forwards them to SAP TM and to SAP EWM for furtherprocessing. As a result of the transportation planning in TM, a freight order is created in TM, whichresults in the creation of a shipment in ERP and of a transportation unit (TU) in EWM.In the warehouse you pick the goods by waves directly into shipping HUs (pallets). You then stagethe shipping HUs and load them into a truck before posting the goods issue. As a result of the goodsissue, the deliveries are updated in ERP for a later billing and the freight order in TM is updated for alater freight cost settlement.



Integration of Outbound Warehousing andTransportation

-

Note

You can fully integrate this business process with the business scenarioWarehouse Management withPreconfigured Processes.



50/92 PUBLIC 03/15/2013

4 Business Scenario: Integration of Outbound Warehousing and Transportation4.2 Handling Cancellation in Order-Based Outbound Processes (EWM-ERP-TM)

The following table provides just one way to implement the business process. For other combinations,see SAP Service Marketplace at http://service.sap.com/scl.

Software Units


SAP ERP 6.0 X -


X -

SAP EWM 9.0 X -

SAP TM 9.0 X -


Further Information


Content Location

Process Description


Test Case


4.2 Handling Cancellation in Order-Based OutboundProcesses (EWM-ERP-TM)

This process is a variant ofManaging Order-Based Outbound Processes (EWM-ERP-TM). During or at the endof the picking and staging step in the warehouse, the carrier calls the shipping office clerk to cancelthe appointment. The shipping office clerk un-assigns the outbound delivery orders from the TUappointments and deletes the TU appointment. In the warehouse the picking and staging can becompleted but the shipping HUs stay in the staging area (or are moved to a nearby area) and areready for loading. The EWM system forwards the TU cancellation to ERP, where the correspondingshipment is deleted and a message is sent to TM for cancellation of the freight order. After the freightorder cancellation, the DTRs are open for a new transportation planning and execution as describedin processManaging Order-Based Outbound Processes (EWM-ERP-TM).

03/15/2013 PUBLIC 51/92



4 Business Scenario: Integration of Outbound Warehousing and Transportation4.2 Handling Cancellation in Order-Based Outbound Processes (EWM-ERP-TM)




-

Note



The following software components are either mandatory or optional, as indicated below, for thetechnical implementation of this process.The following table provides just one way to implement the business process. For other combinations,see SAP Service Marketplace at http://service.sap.com/scl.

Software Units


SAP ERP 6.0 X -


X -

SAP EWM 9.0 X -

SAP TM 9.0 X -


Further Information


Content Location

Process Description


Test Case


52/92 PUBLIC 03/15/2013



4 Business Scenario: Integration of Outbound Warehousing and Transportation4.3 Managing Delivery-Based Outbound Processes (EWM-ERP-TM)

4.3 Managing Delivery-Based Outbound Processes(EWM-ERP-TM)

You use this integrated warehousing and transportation process to send ordered goods to externalcustomers from a warehouse managed with SAP Extended Warehouse Management (EWM). Thegoods are transported by an external carrier.In this process the inventory planning has priority over the transportation planning: you plan thetransportation in SAP Transportation Management (TM) on the basis of outbound deliveries createdand scheduled in SAP ERP. As a result of the transportation planning in TM, a freight order is createdin TM, which results in the creation of a shipment in ERP and of a transportation unit (TU) in EWM.In the warehouse you pick the goods by waves directly into shipping HUs (pallets). You then stagethe shipping HUs and load them into a truck before posting the goods issue. As a result of the goodsissue, the deliveries are updated in ERP for a later billing and the freight order in TM is updated for alater freight cost settlement.




-

Note




Software Units


SAP ERP 6.0 X -


X -

SAP EWM 9.0 X -

SAP TM 9.0 X -

03/15/2013 PUBLIC 53/92


4 Business Scenario: Integration of Outbound Warehousing and Transportation4.4 Planning Transportation (EWM) and Billing (TM) in Outbound Processes


Further Information


Content Location

Process Description


Test Case


4.4 Planning Transportation (EWM) and Billing (TM) inOutbound Processes

You use this integrated warehousing and transportation process to send ordered goods to externalcustomers from a warehouse managed with SAP Extended Warehouse Management (EWM). Thegoods are transported by an external carrier.In this process you execute the outbound deliveries created in SAP ERP as soon as possible in thewarehouse and plan the transportation in SAP EWM accordingly. As a result of the transportationplanning in EWM, you create a transportation unit (TU) in EWM and assign the outbound deliveriesto it.In the warehouse you pick the goods by waves directly into shipping HUs (pallets). You then stage theshipping HUs and load them into a truck before posting the goods issue. As a result of the goods issue,the deliveries are updated in ERP for a later billing, a shipment is created in ERP and a freight order inTM. The freight order is the basis for the freight cost settlement in TM




-

Note




54/92 PUBLIC 03/15/2013


4 Business Scenario: Integration of Outbound Warehousing and Transportation4.4 Planning Transportation (EWM) and Billing (TM) in Outbound Processes

The following table provides just one way to implement the business process. For other combinations,see SAP Service Marketplace at http://service.sap.com/scl.

Software Units


SAP ERP 6.0 X -


X -

SAP EWM 9.0 X -

SAP TM 9.0 X -


Further Information


Content Location

Process Description


Test Case


03/15/2013 PUBLIC 55/92



5 Business Scenario: Dock Appointment Scheduling

5 Business Scenario: Dock AppointmentScheduling

With SAP Dock Appointment Scheduling, you can plan and proceed with appointments for trucks orother transportation units to arrive at the warehouse for loading or unloading. It also allows carrierschosen by the warehouse to plan their own appointments directly in the warehouse’s system. In thisway it provides work leveling and helps to prevent bottlenecks at the warehouse where trucks arrivebut there are no available doors or staff and they must wait. It also helps the carriers to plan theirtransport more efficiently as they can reduce the amount of time trucks have to wait at warehouseswith this application.You must install the desktop version of NetWeaver Business Client (NWBC) 3.5 or higher to beable to use SAP Dock Appointment Scheduling.You must install Microsoft® Silverlight® 4 or higher to be able to use the Web Dynpro applicationswith graphical views in SAP Dock Appointment Scheduling.For more information, see Administrator’s Guide for SAP Dock Appointment Scheduling on SAPMarketplace at SAP Service Marketplace at http://service.sap.com/instguides under SAPBusiness Suite Applications SAP SCM SAP EWM Using SAP EWM 9.0 .This business scenario contains the following business process: Processing Dock Appointment Scheduling.

5.1 Processing Dock Appointment Scheduling

You use this process to plan the receipt of goods from external vendors. You want to optimize thecapacity utilization of your inbound docks. Therefore the carriers who deliver the products reservea time slot in a web application at least one day before the truck arrives at the warehouse. Thisreservation creates a loading appointment in SAP Dock Appointment Scheduling. When the truckarrives at the warehouse, you check if an appointment exists for the truck. Then you track theassignment of the truck to a dock of the loading point. After unloading, the truck leaves the dock andthe warehouse. Finally you can analyze the punctuality of your carriers.

Note

You must install the desktop version of NetWeaver Business Client (NWBC) 3.5 or higher to beable to use SAP Dock Appointment Scheduling.You must install Microsoft® Silverlight® 4 or higher to be able to use the Web Dynpro applicationswith graphical views in SAP Dock Appointment Scheduling.

03/15/2013 PUBLIC 57/92


5 Business Scenario: Dock Appointment Scheduling5.1 Processing Dock Appointment Scheduling



Dock Appointment Scheduling -

Note




Software Units


SAP EWM 9.0 X -

For more information about the installation of this component, see System Landscapes [page 29].

Further Information


Content Location

Process Description


Test Case


58/92 PUBLIC 03/15/2013



6 Business Processes of SAP EWM

6 Business Processes of SAP EWM

This section contains short process descriptions and information about the technical landscapeof the business processes that are not contained in the business scenarioWarehouse Management withPreconfigured Processes.The business processes below from Inbound Process With Stock-Specific UoM (Manual Goods Receipt) to OutboundProcess with Cartonization Planning can be fully integrated with the business scenarioWarehouse Managementwith Preconfigured Processes. The other processes cannot.

Recommendation

A detailed process description and configuration documentation is part of SAP Solution Managerimplementation content ST-ICO 150_700 SP31. For more information about SAP SolutionManager, see http://service.sap.com/solutionmanager.

6.1 Inbound Process With Stock-Specific UoM (Manual GoodsReceipt)

You use this business process to receive goods on pallets from external vendors. Each pallet containsonly a single product. The goods on the pallets have a UoM that represents a smaller package size,such as cartons containing six eaches. You are interested in this information because you will handleproduct in your warehouse in this UoM. Some vendors send advanced shipping notifications (ASN)to SAP ERP. You check the goods in the goods receipt area, and post the goods receipt (GR) in SAPExtended Warehouse Management (EWM). Upon GR posting, warehouse orders (WOs) are created.Depending on the product attributes, you move the goods to different areas in the warehouse usingthe information contained in the printed WOs. You move uncategorized products to a clarificationzone before you put them away.



- -

03/15/2013 PUBLIC 59/92




6 Business Processes of SAP EWM6.2 Inbound Process With Stock-Specific UoM (Manual Warehouse Task)

Note

You can fully integrate this business process with the business scenario Warehouse Managementwith Preconfigured Processes.



Software Units


SAP ERP 6.0 X -


X -

SAP EWM 9.0 X -

SAP TM 9.0 X -


Further Information


Content Location

Process Description


Test Case


6.2 Inbound Process With Stock-Specific UoM (ManualWarehouse Task)

You use this business process to receive goods on pallets from external vendors. Each pallet containsonly a single product. The goods on the pallets have a UoM that represents a smaller package size, e.g.cartons containing six eaches. You are interested in this information because you will handle productin your warehouse in this UoM. Some vendors send advanced shipping notifications (ASN) to SAPERP. You check the goods in the goods receipt (GR) area, and create warehouse orders (WOs) in SAPExtended Warehouse Management (EWM). Depending on the product attributes, you move the

60/92 PUBLIC 03/15/2013



6 Business Processes of SAP EWM6.2 Inbound Process With Stock-Specific UoM (Manual Warehouse Task)

goods to different areas in the warehouse using the information contained in the printed WOs. Youmove uncategorized products to a clarification zone before you put them away. When you confirmthe WOs, the system automatically posts the GR.



- -

Note




Software Units


SAP ERP 6.0 X -


X -

SAP EWM 9.0 X -

SAP TM 9.0 X -


Further Information


Content Location

Process Description


Test Case


03/15/2013 PUBLIC 61/92



6 Business Processes of SAP EWM6.3 Outbound Process With Stock-Specific UoM

6.3 Outbound Process With Stock-Specific UoM

You use this business process to send ordered goods to external customers. In this process, you cansend bigger quantities (for example, cartons or pallets) to the customers. Each carton/pallet in yourstorage bins contain only a single product. The goods on the pallets have a UoM that represents asmaller package size used within the warehouse, e.g. cartons containing six eaches. Warehouse orders(WOs) are created during outbound delivery order creation and are used to optimize the pickingprocess. Picking consists of a single paper-based step using pick-handling units (HUs) that you ship tothe customers. After loading them into a truck you post the goods issue.



- -

Note




Software Units


SAP ERP 6.0 X -


X -

SAP EWM 9.0 X -

SAP TM 9.0 X -


Further Information


62/92 PUBLIC 03/15/2013


6 Business Processes of SAP EWM6.4 Outbound Process with Cartonization Planning

Content Location

Process Description


Test Case


6.4 Outbound Process with Cartonization Planning

Overview

You use this business process to send ordered goods to external customers. In this process you sendsmaller quantities of many different products to many diffferent customers which are deliveredwithin the same route. The necessary packaging materials are optimized by usage of cartonizationplanning to minimize whitespace for the shippers’ truck as there are many possible differentpackaging materials to choose from. This information enables you to gain information about volume,weight and number of shipping HUs at a very early point in time during the outbound process whichcan be used for ordering a carrier regarding the upcoming shippments/loading.You pick the goods by waves into pick-HUs and consolidate them into shipping HUs at a packingstation according to the planned shipping handling units (PSHU). You then stage the shipping HUsand load them into a truck before posting the goods issue. You use the same route to deliver eachcustomer.



- -

Note




03/15/2013 PUBLIC 63/92





6 Business Processes of SAP EWM6.5 Inbound Processing and Receipt Confirmation with Warehouse Management in SCM

Software Units


SAP ERP 6.0 X −


X −

SAP EWM 9.0 X −


Further Information


Content Location

Process Description


Test Case


6.5 Inbound Processing and Receipt Confirmation withWarehouse Management in SCM

Overview

You use this business process for your inbound processing and receipt confirmation with SAP EWM.For this process variant - the logistics process of receiving goods in the warehouse, you must ensure ahigh degree of variability and flexibility. In the actual implementation, different optional steps can beinstalled to ensure an efficient and streamlined inbound process.Whenever a company requires a product to be procured from an external source of supply, theproduct is delivered according to the official procurement document (a PO) agreed between twobusiness partners. The arrival of the goods is announced by a message from the supplier (ASN). Theyare delivered in a certain quantity at a defined date and time at a defined company location. For thedelivered goods, the system selects an inbound delivery and processes it for putaway. Once the goodsare taken into stock, a goods receipt must be posted.Inbound processing and goods receipts are key steps in any procurement or replenishment process.Using inbound processing in SAP EWM supports specific requirements for receiving goods inwarehouses for discrete industries, for example for Service Parts Management.The inbound process is divided into several process steps which ensure that the physical receivingprocess is reflected in system activities and documents. The basic concept is to differentiate betweenplanned activities and notifications (for example ASN, inbound delivery notification) and finalized

64/92 PUBLIC 03/15/2013



6 Business Processes of SAP EWM6.5 Inbound Processing and Receipt Confirmation with Warehouse Management in SCM

documents after processing (inbound delivery). If Handling Unit (HU) Management for packing isused, you must use it in inbound delivery to pack against.The inbound process can optionally be supported in a Radio Frequency Identification (RFID)environment with fixed devices. For this purpose, SAP Auto-ID 7.1 must be part of your systemlandscape.



Service Order Managment with Service PartProcurement

SAP CRM/Enterprise Service

Warehouse & DC Management SAP for Retail

Service Parts Warehousing SAP Service and Asset Management

Service Delivery Cross-Application Implementation Packages/Delivery

Recall Management SAP CRM/Enterprise Services

Storage and Fulfillment Cross-Application Implementation Packages/Logistics


The following software components are either mandatory or optional, as shown in the table below,for the technical implementation of this process.The following table provides just one way to implement this business process. For other combinations,see http://service.sap.com/scl.

Software Units


SAP ERP 6.0 X −

SAP EWM 9.0 X −


Further Information


Content Location

Process Description



03/15/2013 PUBLIC 65/92






6 Business Processes of SAP EWM6.6 Outbound Processing with Warehouse Management in SCM

6.6 Outbound Processing with Warehouse Management inSCM

Overview

You can use this business process for the outbound processing with SAP EWM. Outbound processingcomprises the preparation of goods to be delivered from a warehouse to a receiving location.Outbound processing starts with the creation of an outbound delivery that typically has been createdbased on reference documents such as sales orders or stock transport orders. The outbound deliveryserves as the basis for the subsequent process steps.The outbound process can optionally be supported in a Radio Frequency Identification (RFID)environment with fixed devices. For this purpose, SAP Auto-ID 7.1 must be part of your systemlandscape.Outbound processing in typically comprises the following activities:

n Notification of goods (to be supplied from a warehouse to a customer for which the outbounddelivery serves as the reference document)

n Pickingn Packingn Loadingn Goods issue and goods issue postingn Finalizing the delivery process





Service Delivery Cross-Application Implementation Packages/Delivery




Software Units


SAP ERP 6.0 X −

SAP EWM 9.0 X −

66/92 PUBLIC 03/15/2013




6 Business Processes of SAP EWM6.7 Warehousing and Storage in SCM

For more information about the installation of these components, see System Landscapes [page 29]

Further Information


Content Location

Process Description



6.7 Warehousing and Storage in SCM

Overview

You use this business process to efficiently manage goods and processes in a complex warehouseenvironment. Goods movements and all logistic processes within the warehouse are planned andexecuted efficiently. This scenario begins with the creation and confirmation of a warehouse order(WO) and includes the optional processes of confirming warehouse orders via the desktop (ratherthan using radio frequency) as well as the optional processes of slotting, warehouse rearrangement,resource management, labor management, and monitoring.The inbound process can optionally be supported in a Radio Frequency Identification (RFID)environment with fixed devices. For this purpose, SAP Auto-ID 7.1 must be part of your systemlandscape.






The following software components are either mandatory or optional, as indicated below, for thetechnical implementation of this process.The following tables provide just one way to implement the business process. For other combinations,see http://service.sap.com/scl.

03/15/2013 PUBLIC 67/92






6 Business Processes of SAP EWM6.8 Physical Inventory on Storage Bin Level in SCM

Software Units


SAP ERP 6.0 X −

SAP EWM 9.0 X −


Further Information


Content Location

Process Description



6.8 Physical Inventory on Storage Bin Level in SCM

Overview

You use this business process to set up physical inventory on the storage bin level with SAP SupplyChain Management (SAP SCM). With the functions in EWM, a customer can perform physicalinventory for a product or handling unit at a single storage bin, at multiple storage bins, or at agrouping of several storage bins.






The following software components are either mandatory or optional, as indicated below, for thetechnical implementation of this process.The following tables provide just one way to implement the business process. For other combinations,see http://service.sap.com/scl.

68/92 PUBLIC 03/15/2013






6 Business Processes of SAP EWM6.9 Merchandise Distribution

Software Units


SAP ERP 6.0 X −

SAP EWM 9.0 X −


Further Information


Content Location

Process Description



6.9 Merchandise Distribution

Overview

Merchandise distribution is a variant of cross-docking, which is particularly important in the retailindustry.When cross-docking, products that have arrived at the warehouse are brought from goods receiptdirectly to goods issue without being put away. Merchandise distribution means that retailers, forexample, plan, control, and manage their flow of products or merchandise from the vendors viadistribution centers to the stores or customers. Vendors already pre-package all items based on therelevant customer. This means that in the warehouse, when handling units arrive, they alreadycontain information about the customer from whom they are packed. These handling units can bemixed handling units; that means, they can contain multiple items of an outbound delivery.






03/15/2013 PUBLIC 69/92






6 Business Processes of SAP EWM6.10 Opportunistic Cross-Docking

Software Units


SAP ERP 6.0 X −


X −

SAP EWM 9.0 X −

For more information about the installation of these components, see System Landscapes [page 29]

Further Information


Content Location

Process Description



6.10 Opportunistic Cross-Docking

Overview

Opportunistic cross-docking is a variant of cross-docking.When cross-docking, products that have arrived at the warehouse are brought from goods receiptdirectly to goods issue without being put away. Opportunistic cross-docking allows incomingdeliveries to be redirected to cover outbound requirements. The cross docking decision is made inSAP EWM.







70/92 PUBLIC 03/15/2013






6 Business Processes of SAP EWM6.11 Unpacked Inbound Delivery from Vendor (with Manual GR and Automatic WT)

Software Units


SAP ERP 6.0 X −

SAP EWM 9.0 X −


Further Information


Content Location

Process Description



6.11 Unpacked Inbound Delivery from Vendor (with ManualGR and Automatic WT)

Overview

In this simple inbound warehouse process, you receive goods from external vendors. A truck arrivesand the truck driver brings the delivery note to the goods receipt (GR) office. If the vendor hassent an advanced shipping notification (ASN) to SAP ERP, the GR clerk finds the correspondinginbound delivery in SAP Extended Warehouse Management (EWM). If no inbound delivery yet existsin the system, the GR clerk creates an inbound delivery with or without reference to the purchasingdocument in EWM. The truck driver drives the truck to the door assigned by the GR clerk. Thewarehouse clerk unloads the truck. The warehouse clerk checks the goods against the delivery noteand takes it with annotations to the GR office. The GR clerk posts the goods receipt in EWM, whichcreates and prints warehouse orders (WOs) with reference to the inbound delivery to move thegoods into the warehouse. The truck leaves. The warehouse clerk moves the goods from the GRarea into the warehouse. For example, they are moved to two different storage types: a storage typefor small parts and a storage type for large parts. The storage type for small parts is divided into twostorage sections: one for slow-moving items and one for fast-moving items. In the storage type forsmall parts, the next empty storage bin is determined as the destination storage bin. In the storagetype for large parts, fixed storage bins are used. Products that have not yet been categorized as smallor large parts or that have no fixed bin assignment are first moved into a separate storage type forclarification. When the goods are in the destination storage bins, the warehouse clerk confirms theputaway WO using a desktop transaction in EWM.

03/15/2013 PUBLIC 71/92



6 Business Processes of SAP EWM6.12 Unpacked Inbound Delivery from Vendor (with Manual WT and Automatic GR)



- -



Software Units


SAP ERP 6.0 X −

SAP EWM 9.0 X −


Further Information


Content Location

Process Description



6.12 Unpacked Inbound Delivery from Vendor (with ManualWT and Automatic GR)

Overview

In this simple inbound warehouse process, you receive goods from external vendors. A truck arrivesand the truck driver brings the delivery note to the goods receipt (GR) office. If the vendor hassent an advanced shipping notification (ASN) to SAP ERP, the GR clerk finds the correspondinginbound delivery in SAP Extended Warehouse Management (EWM). If no inbound delivery yet existsin the system, the GR clerk creates an inbound delivery with or without reference to the purchasingdocument in EWM. The truck driver drives the truck to the door assigned by the GR clerk. Thewarehouse clerk unloads the truck. The warehouse clerk checks the goods against the delivery noteand takes it with annotations to the GR office. The GR clerk creates warehouse tasks (WTs) in EWM,

72/92 PUBLIC 03/15/2013






6 Business Processes of SAP EWM6.12 Unpacked Inbound Delivery from Vendor (with Manual WT and Automatic GR)

which creates and prints warehouse orders (WOs) with reference to the inbound delivery to move thegoods into the warehouse. The truck leaves. The warehouse clerk moves the goods from the GRarea into the warehouse. For example, they are moved to two different storage types: a storage typefor small parts and a storage type for large parts. The storage type for small parts is divided into twostorage sections: one for slow-moving items and one for fast-moving items. In the storage type forsmall parts, the next empty storage bin is determined as the destination storage bin. In the storagetype for large parts, fixed storage bins are used. Products that have not yet been categorized as smallor large parts or that have no fixed bin assignment are first moved into a separate storage type forclarification. When the goods are in the destination storage bins, the warehouse clerk confirms theputaway WOs using a desktop transaction in EWM. Upon confirmation of the putaway WOs, thesystem automatically posts the goods receipt.



- -



Software Units


SAP ERP 6.0 X −

SAP EWM 9.0 X −


Further Information


Content Location

Process Description



03/15/2013 PUBLIC 73/92






6 Business Processes of SAP EWM6.13 Integration with Transportation (LE-TRA Component in ERP)

6.13 Integration with Transportation (LE-TRA Component inERP)

Overview

Integration with Transportation (LE-TRA Component in ERP) allows you to run the followingprocesses:

n Inbound Processing: Transportation Planning in ERPThis process allows you to use transportation planning of SAP ERP in the inbound process ofExtended Warehouse Management (EWM). The process uses the shipment documents as a basisfor carrying out transportation planning. The system converts handling units (HUs) in ERPshipments into transportation unit (TU) activities (and optionally vehicle activities). You cancontrol and monitor the entire transportation process from the planning stage to the goodsreceipt at your own plant.

n Outbound Processing: Transportation Planning in SAP ERPThis process allows you to use transportation planning of SAP ERP in the outbound process ofExtended Warehouse Management (EWM). The process uses the shipment documents as a basisfor carrying out transportation planning. The system converts handling units (HUs) in ERPshipments into transportation unit (TU) activities (and optionally vehicle activities). You cancontrol and monitor the entire transportation process from the planning stage to the goods issue.Transportation planning involves all the activities that must be performed before the shipmentleaves the shipping point.

n Outbound Processing: Transportation Planning in SAP EWM-ERPThis process allows you to use transportation planning of SAP ERP in the outbound processof Extended Warehouse Management (EWM). The system creates shipment documents inSAP ERP on the basis of transportation planning and execution in EWM. The system convertstransportation unit (TU) activities (and optionally vehicle activities) in ERP shipments. You cancontrol and monitor the entire transportation process from the planning stage to the goods issue.Transportation planning involves all the activities that must be performed before the shipmentleaves the shipping point.



- -



74/92 PUBLIC 03/15/2013




6 Business Processes of SAP EWM6.13 Integration with Transportation (LE-TRA Component in ERP)

Software Units


SAP ERP 6.0 X −

SAP EWM 9.0 X −

Further Information

The following documents provide more information about these business processes:

Content Location

Process Description



03/15/2013 PUBLIC 75/92



7 Solution-Wide Topics

7 Solution-Wide Topics

For information about shared services that are provided by SAP NetWeaver 7.0 and are requiredto run a system landscape, such as Solution Manager, System Landscape Directory, or SoftwareLifecycle Manager, see the current Master Guide for SAP NetWeaver 7.0 on SAP Service Marketplace athttp://service.sap.com/instguides under SAP NetWeaver SAP NetWeaver 7.0 Installation .

7.1 Service-Oriented Architecture (SOA)

SAP´s delivery on SOA (service-oriented architecture) differs from the pure architectural conceptof SOA in the delivery of ready-to use enterprise services. Enterprise services are SAP-defined Webservices which provide end-to-end business processes or individual business process steps that canbe used to compose business scenarios while ensuring business integrity and ease of reuse. SAPdesigns and implements enterprise service interfaces to ensure semantic harmonization and businessrelevance. This section deals with the service-enablement of SAP Business Suite 7.

7.1.1 Service Enablement

The service enablement of SAP Business Suite consists of one or more of the following SAPcomponents:

n SAP Business Suite 7Enterprise services are an integral part of the software components of the SAP Business Suiteapplications. Enterprise services are the technical interfaces to the functionality available in thebusiness application.

n SAP NetWeaver PI 7.0 or higherSAP NetWeaver Process Integration (SAP NetWeaver PI) is an open integration and applicationplatform that provides tools enabling you to set up a service-oriented architecture for businessapplications. You can use the platform for providing, discovering, and consuming services,integrating applications using the integration server, and managing business processes. Processintegration is required in a runtime environment to consume enterprise services in a mediatedscenario.We recommend that you use the highest version of SAP NetWeaver Process Integration (PI). Formore information, see SAP Note 1515223 and SAP Note 1388258.

03/15/2013 PUBLIC 77/92






7 Solution-Wide Topics7.1 Service-Oriented Architecture (SOA)

Note

Starting with SAP NetWeaver Process Integration (PI) 7.3, SAP provides a new installation optionAdvanced Adapter Engine Extended (AEX). Since AEX is based on AS Java alone, it is easierto install and maintain as well as it needs less memory and data storage. Therefore, AEX is acost-saving option compared to a full installation of SAP NetWeaver PI. For more informationabout the AEX, see the SAP Library at: http://help.sap.com/nw73 SAP NetWeaver 7.3 LibraryEnglish SAP NetWeaver Process Integration Concepts Installation and Connectivity Options AdvancedAdapter Engine Extended and SAP Note 1573180.

Note

Asynchronous services that are enabled forWeb Services Reliable Messaging (WS-RM) can be calledin a point-to-point communication scenario. Otherwise asynchronous services can only beconsumed in a mediated scenario.

n Enterprise Services RepositoryThe Enterprise Services Repository (ES Repository) is the central repository that contains thedefinition of all enterprise services and models. The ES Repository is shipped with SAP NetWeaverPI and with SAP NetWeaver Composition Environment (CE) starting with SAP NetWeaver PI 7.1and with SAP NetWeaver CE 7.1. The Enterprise Services Repository is a design time environmentthat enables you to create and enhance enterprise service definitions and to view enterpriseservice models.

Note

In a SAP NetWeaver 7.0x landscape you will require the Integration Repository to create andenhance enterprise service definitions in a design time environment.

n Services RegistryThe Services Registry is shipped with SAP NetWeaver PI and SAP NetWeaver CE starting with SAPNetWeaver PI 7.1 and SAP NetWeaver CE 7.1. The Service Registry is required for the publicationof enterprise service end-points (Web services) that have been configured and activated in theSAP Business Suite.

n SAP NetWeaver CE 7.1 or higherThe SAP NetWeaver Composition Environment (SAP NetWeaver CE) provides a robustenvironment for the design and implementation of composite applications.The design time environment of SAP NetWeaver CE can be used for the model-driven design anddevelopment of composite applications based on enterprise services. SAP NetWeaver CE offersthe tools and the environment necessary for running composite applications fast and efficientlyin a runtime environment.

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

78/92 PUBLIC 03/15/2013

http://help.sap.com/nw73





Figure 3: Overview: SAP’s Applications for SOA Enablement

The following table describes the SAP applications required or recommended for different runtimeand design time use cases:

SAP Applications

SAP BusinessSuite

SAPNetWeaverPI 7.0x(IntegrationRepository)

SAPNetWeaverPI 7.1 orhigher (ESRepository)

SAPNetWeaverCE 7.1 orhigher (ESRepository)

SAP SolutionManager7.0 EHP1or higher(SolutionComposer)

SAPNetWeaver7.1 or higherServicesRegistry

Runtime Usage:

EnterpriseServiceProvisioning

Required Optional

Process inte-gration andmediatedcommuni-cation

One option required

Design Time Usage:

03/15/2013 PUBLIC 79/92


Create andenhanceenterpriseservicedefinitions

Required One option required Recom-mended

Viewenterpriseservicemodels

One Option Required Recom-mended

Design anddevelopcompositeapplications

Required Recom-mended

Recom-mended

Enterpriseservice onlinedocumenta-tion

Required

Publicationsof enterpriseserviceend-points

Optional Required

7.1.2 Installation of the Service-Oriented Architecture (SOA)

The installation of service interfaces, and therefore the service enablement of SAP Business Suite,consists of one or more of the following phases:

n Identification of software components and required business functionsYou use the technical data section of the enterprise service documentation to identify thefollowing data for each enterprise service:l the software component version with which the service was shippedl the business function(s) required to be activated

n Identification of technical usages (relevant for SAP ERP only)SAP Note 1566412 provides a mapping of business functions and software component versions totechnical usages. You use this documentation to identify the required technical usages for your listof software component versions and business functions.

n Installation of the software component ECC-SE (relevant for SAP ERP only)The software component ECC-SE contains service implementations for ECC (the ERP CentralComponent). This component must be explicitly installed if you intend to use enterprise servicesfor ECC functionality. In this case you must also select the technical usage “ESA ECC-SE” duringthe enhancement package installation.

n Selection and installation together with the other parts of the enhancement package

80/92 PUBLIC 03/15/2013



In the enhancement package installation process you must select all the technical usages you haveidentified for service enablement together with the technical usages you identified for enhancedfeatures in SAP Business Suite. The selected technical usages will install the correspondingsoftware components that contain the enterprise services interfaces and implementations.

n Enterprise service definitions for SAP NetWeaver PI 7.0x or ES Repository (SAP NetWeaver7.1 or higher) (optional)To install the content required for the enterprise service definitions you must select the technicalusage “XI Content” in the enhancement package installation process. This usage type downloadsthe content files for SAP NetWeaver 7.0 or higher. Unpack the ZIP file and copy the tpz filescorresponding to your SAP NetWeaver version into the import directory of your IntegrationRepository (for SAP NetWeaver PI 7.0x) or Enterprise Services Repository (for SAP NetWeaverES Repository 7.1 or higher). Use the import function to import the content files into thecorresponding repository (Integration Repository or Enterprise Services Repository). (ChooseTools Import Design Objects )

n Enterprise service models for ES Repository (SAP NetWeaver 7.1 or higher) (optional)To install the content required for the enterprise service models you must select the technicalusage “ESR Content” in the enhancement package installation process. This usage type downloadsthe content files for SAP NetWeaver ES Repository 7.1 or higher. Unpack the ZIP file and copythe tpz files into the import directory of your Enterprise Services Repository. Use the importfunction to import the content files into the Enterprise Services Repository. (Choose ToolsImport design objects )

Note

The enterprise service models are not available for the Integration Repository (SAP NetWeaver PI7.0x)

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

n Services Registry (optional)The services registry is shipped starting with SAP NetWeaver PI 7.1 and CE 7.1. You must install theservices registry and then publish the enterprise services from the Business Suite application tothe registry using the transaction SOAMANAGER in the backend.For further information regarding the installation of SAP NetWeaver PI, CE and ES Repository,refer to the corresponding SAP NetWeaver Installation and Master Guides.

03/15/2013 PUBLIC 81/92



7.1.3 Related Documentation

For more information about the service-oriented architecture (SOA), see the following informationsources:

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

n The SAP Enterprise Service Workplace at http://ESWorkplace.sap.comn The Enterprise Services Wiki in the SAP Network at https://wiki.sdn.sap.com/wiki/x/LQ0

(registration required)n SAP Note 1224284: Enterprise Services, Installing and Accessing the SOA Documentationn SAP Note 1359215: Technical prerequisites for using enterprise services (relevant for ERP only)n SAP note 838402: Problems with non-Unicode system landscapes

82/92 PUBLIC 03/15/2013

https://www.sdn.sap.com/irj/sdn/soa

http://ESWorkplace.sap.com

https://wiki.sdn.sap.com/wiki/x/LQ0




A Appendix

A Appendix

A.1 List of Documents

The following table lists all documents mentioned in this Master Guide.

Title Purpose Location on SAP ServiceMarketplace

Installation Guides

SAP ERP 6.0 including SAPenhancement package 6

Installing the ERP Server http://service.sap.com/instguides SAPBusiness Suite Applications SAP ERPSAP ERP 6.0 SAP enhancement packagesfor SAP ERP 6.0 SAP enhancementpackage 6 for SAP ERP 6.0

SAP Supply ChainManagement 7.0 includingSAP enhancement package 2

Installing the SCM Server http://service.sap.com/instguides

SAP Business Suite Applications SAPSCM SAP SCM Server Using SAPenhancement package 2 for SAP SCM 7.0Server

SAP NetWeaver 7.3 includingSAP enhancement package 1

Installing SAP Netweaver for EWM asstandalone

http://service.sap.com//installNW73

Installing the XI ServerSAP NetWeaver 7.0 or higher

Installing the BI Server


orhttp://service.sap.com/installNW73

SAP Solution Manager Installing Solution Manager http://service.sap.com/instguides

SAP Components SAP SolutionManager

SAP Visual Business SAP Service Marketplace athttp://service.sap.com/instguide

Master Guides

SAP SCM 7.0 including SAP enhancement package 2 http://service.sap.com/instguides

under SAP Business Suite ApplicationsSAP SCM SAP SCM Server UsingSAP enhancement package 2 for SAP SCM7.0 Server

03/15/2013 PUBLIC 83/92













http://service.sap.com/instguide



A AppendixA.1 List of Documents


SAP ERP 6.0 including SAP enhancement package 6 http://service.sap.com/instguides

under SAP Business Suite ApplicationsSAP ERP SAP ERP 6.0 SAPenhancement packages for SAP ERP 6.0SAP enhancement package 6 for SAP ERP6.0

SAP Auto-ID infrastructure 7.1 http://service.sap.com/instguides

under SAP Business Suite ApplicationsSAP SCM SAPAuto-ID InfrastructureSAP Auto-ID Infrastructure 7.1

SAP for Retail http://service.sap.com/instguides

under Industry Solutions IndustrySolution Guides SAP for Retail SAPRetail

SAP Service & Asset Management http://service.sap.com/erp-inst

under Industry Solutions IndustrySolution Guides SAP Service & AssetManagement

Master Guide for Plant Connectivity SAP Service Marketplace athttp://service.sap.com/instguides

under SAP Business Suite ApplicationsSAP Manufacturing Plant ConnectivityPlant Connectivity 2.2

Administrator’s Guide for Dock Appointment Scheduling SAP Service Marketplace athttp://service.sap.com/instguides

under SAP Business Suite ApplicationsSAP SCM SAP EWM Using SAPEWM 9.0

SAP Transportation Management 9.0 Master Guide SAP Service Marketplace athttp://service.sap.com/instguides

under SAP Business Suite ApplicationsSAP TM Using SAP TM 9.0

Master Guide (Including Upgrade Information) for SAP CustomerRelationship Management 7.0 Including SAP Enhancement Package 2

SAP Service Marketplace athttp://service.sap.com/instguides

under SAP Business Suite ApplicationsSAP CRM SAP Enhancement Package 2for SAP CRM 7.0 Plan

Master Guide for SAP Global Trade Services SAP Service Marketplace athttp://service.sap.com/instguides

under SAP Components SAP GlobalTrade Services Using SAP GTS 10.0

84/92 PUBLIC 03/15/2013







http://service.sap.com/erp-inst

http://service.sap.com/erp-inst






A AppendixA.2 Media List


Master Guide for Enterprise Services for SAP Business Suite SAP Service Marketplace athttp://service.sap.com/instguides

under SAP Business Suite ApplicationsSAP ERP SAP ERP 6.0 SAPenhancement packages for SAP ERP 6.0SAP enhancement package 6 for SAP ERP6.0

Upgrade Master Guide

SAP Extended Warehouse Management 9.0 Upgrade Master Guide SAP Service Marketplace athttp://service.sap.com/instguides

under SAP Business Suite ApplicationsSAP SCM SAP EWM Using SAPEWM 9.0

SAP Business Objects

General information SAP Help Portal athttp://help.sap.com under SAPERP or SAP CRM Processes and Toolsfor Enterprise Applications (CA-EPT)Embedded Analytics

Installation information SAP Service Marketplace athttp://service.sap.com/bosap-instguides

and SAP Help Portal athttp://help.sap.comunder SAPBusinessObjects All Products

Configuration information SAP Solution Manager underSolutions/Applications Basic

Configuration Embedded Analytics

Service-Oriented Architecture (SOA)

SDN Community in the SAP Network https://www.sdn.sap.com/irj/sdn/soa

(registration required)

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

Enterprise Services Wiki in the SAP Network https://wiki.san.sap.com/wiki/x/LQ0

(registration required)

A.2 Media List

Material Number DVD / CD Label

50114052 DVD SAP EWM 9.0 Online Documentation

03/15/2013 PUBLIC 85/92



http://help.sap.com

http://service.sap.com/bosap-instguides

http://help.sap.com

https://www.sdn.sap.com/irj/sdn/soa

http://ESWorkplace.sap.com

https://wiki.san.sap.com/wiki/x/LQ0

A AppendixA.3 List of SAP Notes

A.3 List of SAP Notes

The following table lists all SAP Notes mentioned in this Guide.


1705802 Implementation recommenda-tions for SAP EWM

For implementing SAP EWM 9.0

1691105 Installing or upgrading SCMEWM900

Add-on installation or upgrade to SAP EWM9.0

1678780 Installation / upgrade BI_CONT /BI_CONT_XT 7x7

Information about Business IntelligenceContent 7x7 in relation to add-oninstallation and delta upgrade, and basisupgrade to 7X.This note is only relevant if you use BIcontent for EWM.

1606493 SAP EWMDeployment Options ‒Best Practices

Several deployment options exist for SAPEWM:. it can be deployed as Add-On to SAPNetweaver, to SAP ERP or to SAP SCM.

1529649 Factory Calendar expires 2010 Factory calendars are delivered from SAPwith a validity until 2010 in the standard.Before expiration no error message isdisplayed. This could lead to follow-uperrors at the turn of the year, in differentapplications, using the calendar.

1515223 SAP NetWeaver ProcessIntegration: ReleaseRecommendation

Information about which PI release to use.This note is only relevant if you useEnterprise Services for EWM.

1423066 Optimization of the performancein EWM

You are using Extended WarehouseManagement (EWM) and you notice thatsystem performance is inadequate for yourrequirements with regard to the dialogresponse times or the consumption ofsystem resources.

1224284 Enterprise Services Bundles ‒Required Technical Usages andBusiness Functions

Lists business-related grouping of EnterpriseServices.This note is only relevant if you useEnterprise Services for EWM.

1048230 De-activate the livecache for EWM Using EWM in a SCM system the liveCacheis not relevant and may not be activated ifyou do not use it for other SCM applications.This note is only relevant if you use SCM asAdd-On to SCM.

900000 Netweaver Business Client - FAQ This note is only relevant if you use NWBCfor EWM transactions

86/92 PUBLIC 03/15/2013











A AppendixA.4 Tools and Resources for Planning Your System Landscape


838402 Problems within non-Unicodesystem landscapes

Information about problems withoutUnicode

1612190 Interface enhancement for stockkeeping units

Enhancement of BAPIBAPI_OUTB_DELIVERY_CONFIRM_DEC with anew interface parameter NEW_ITEM_DATA_SKUfor delivery items in stock keeping units.

1388258 Version Interoperability withinthe SAP Business Suite

Information about version interoperabilitystarting with SAP Business Suite 7 and SAPNetWeaver 7.0.

1573180 AEX Enablement for SAP BusinessSuite

Information about how to facilitate usageof SAP NetWeaver Process Integration7.3 (including Enhancement Package 1)installation option Advanced AdapterEngine Extended (AEX) in context with SAPBusiness Suite 7 or SAP Business Suite 7 i2010.

A.4 Tools and Resources for Planning Your System Landscape

To plan your system landscape, you can use a few tools and resources that are available to you asSAP customer.

Tools

On SAP Service Marketplace, we provide some tools that allow you to look up more detailedinformation about business scenarios, business processes and implementable steps. These toolsinclude the following:

Tools for Looking Up Information about Business Processes, Scenarios, and Implementable Steps

Tool Purpose

Business process repository (BPR) viewer To look up descriptions of business scenarios, businessprocesses, and implementable steps

Scenario and process component list To look up the required components and releases for abusiness scenario, business process, or implementablesteps

In addition, there are tools in SAP Solution Manager that support you before, during, or after theinstallation of your SAP product or SAP enhancement package.These tools include:

03/15/2013 PUBLIC 87/92






Tools for Supporting Installations and Upgrades

Tool Purpose

Solution Manager System Landscape (transactionSMSY)

To model and set up your system landscape

SAP Solution Manager Maintenance Optimizer(transaction DSWP

To install support packages and SAP enhancementpackages

Business process repository To access configuration documentation, links toCustomizing activities and master data transactions,specifically tailored for individual business processes,business scenarios, or implementable steps

Business process change analyzer (available with SAPenhancement package 1 for SAP Solution Manager7.0)

To analyze the effects of transports and supportpackages as well as activation logs for businessfunctions

Note

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

n SAP Solution Manager 7.0 EHP1, SPS23 or higher

n SAP Solution Manager 7.1, SPS01 or higher

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

SAP Solution Manager: Implementation Content

To get implementation content that supports you during the configuration of your businessprocesses and business scenarios, you need the SAP Solution Manager add-on Implementation ContentST-ICO 150_700 (SP35).

Landscape Verification for SAP Solutions Manager

To verify and correct your system landscape SAP highly recommends that you use LandscapeVerification 1.0 for SAP Solution Manager 7.0, which is an add-on to your SAP Solution Manager 7.0system. This add-on allows you to identify and correct issues in your SAP SolutionManager landscape(transaction SMSY) before they cause problems, for example during a system update. Examples forerrors are a missing connection to the System Landscape Directory or the wrong assignment ofproducts to technical systems. For each type of error, a generic description for the solution is provided.For more information about the landscape verication add-on, see SDN athttp://www.sdn.sap.com/irj/sdn Application Lifecycle Management Tech-

nical Enablement Update and Upgrade Related Areas on Upgrade and UpdateManagement Landscape Verication(http://www.sdn.sap.com/irj/sdn/alm?rid=/webcontent/uuid/70fc3790-7ec9-2d10-57ad-95b2d0d1185d).

88/92 PUBLIC 03/15/2013




http://www.sdn.sap.com/irj/sdn



http://www.sdn.sap.com/irj/sdn/alm?rid=/webcontent/uuid/70fc3790-7ec9-2d10-57ad-95b2d0d1185d


SAP Business Suite: Landscape Implementation — Technical Planning Guide

To get an overview of the necessary steps for planning a system landscape, use the Landscape Implementation— Technical Planning Guide on SAP Service Marketplace at http://service.sap.com/instguides underSAP Business Suite Applications . The guide also provides you with more information about the

following:

n Examples of reference system landscapesn Planning tools such as the business process repositoryn Deployment optionsn Typical implementation process

A.4.1 Business Process Repository (BPR) Viewer

The business process repository viewer (BPR viewer) is a tool on SAP Service Marketplace that allowsyou to preview the existing business scenarios, business processes that are shipped as part of SAPSolution Manager content. You can make use of the information in SAP Solution Manager duringyour implementation project by taking the pre-delivered implementation content as the startingpoint for your project scope. The implementation content is delivered with the following assignedinformation:

n Description of the business scenario, process, or implementable stepn Configuration content (Customizing activities or configuration documentation)

A.4.2 Using the BPR Viewer

Calling Up the BPR ViewerYou can call up the BPR viewer directly using the Internet addresshttps://implementationcontent.sap.com/bpr. Alternatively, you can also call up the Internetaddress http://service.sap.com/bpr first, to see more background information about the BPRviewer and additional material on SAP Service Marketplace.

Working with the BPR ViewerTo call up information about business scenarios, business processes, or implementable steps, navigatethe following paths in the BPR viewer:

BPR Object Location

Business scenario Under Solutions/Applications

Business process Under Organizational Areas

Implementable step Under Solutions/Applications

03/15/2013 PUBLIC 89/92


https://implementationcontent.sap.com/bpr

http://service.sap.com/bpr


For each business scenario, business process, or implementable step, you can select between differentversions that depend on varying components and releases. To display the descriptions of a businessscenario, business process, or implementable step, choose the Documentation tab page. To displayconfiguration documentation, choose the Configuration tab page.

Note

The BPR Viewer displays all descriptions, but only a selection of the configuration documentation.To view all configuration documentation, install and use SAP Solution Manager at your customersite.

A.4.3 Scenario and Process Component List (SCL & PCL)

The scenario and process component list (SCL/PCL) is a tool on the SAP Service Marketplace thatallows you to find realization alternatives for SAP solutions, business scenarios, and processes for yourSAP enhancement package installation. You find the tool at http://service.sap.com/scl.The SCL/PCL helps you to bridge the gap between the business view and the technical view in SAP’sproducts. It shows you which application components are needed to realize a business scenario or aprocess and which business scenarios are possible with a given set of application components.

A.4.4 Using the SCL/PCL

1. Go to SAP Service Marketplace at http://service.sap.com/scl.2. To start the SCL/PCL, choose Start Application.

The following selection options are provided:n SAP Scenarios and Realization Alternatives

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

n SAP Components and Possible ScenariosThis option allows you to browse SAP’s products and components and to find out, whichbusiness scenarios and processes you can realize using the components.

For more information on how to use the tool, refer to the Help section.3. Select SAP Scenarios and Realization Alternatives.

Select one or several scenarios, processes, and variants you want to realize. You can make yourselection by using an alphabetical index or a full-text search. It is also possible to see all scenariosfor a certain solution. You will then get a list of the alternative ways to realize these scenarios. Youcan also search for the identified business functions of a SAP enhancement package.In the following steps we chose the scenario Billing Analysis in ERP as an example.

90/92 PUBLIC 03/15/2013




4. Add the scenario Billing Analysis in ERP to the Selected Scenarios/Processes/Variants list and choose ShowRealization Alternatives. The SCL/PCL then lists the different possibilities. With options likeValidity youcan switch between possible and impossible realization alternatives. The Optional Comp. dropdownlist helps you to find the minimum required SAP product versions.

03/15/2013 PUBLIC 91/92

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermanyT +49/18 05/34 34 34F +49/18 05/34 34 20www.sap.com

© Copyright 2013 SAP AG. All rights reserved.Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigungdurch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.