Y38_BPP_EN_DE

SAP EWM 7.01 November 2011 English

Outbound Process Using Wave, Pick HU, Packing, Staging, and Loading (Y38) Business Process Documentation

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany

SAP Best Practices

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

Copyright © Copyright 2011 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the exchoose permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the exchoose warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG Page 2 of 24

SAP Best Practices

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

Icons Icon

Meaning Caution Example Note Recommendation Syntax External Process Business Process Alternative/Decision Choice

Typographic Conventions Type Style

Description

Example text

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

Example text

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

EXAMPLE TEXT

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

Example text

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

EXAMPLE TEXT

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

Example text

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



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

F2)

or the

© SAP AG Page 3 of 24

SAP Best Practices

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

Content 1 2

Purpose........................................................................................................................................ 5 Prerequisites................................................................................................................................. 5 2.1 Master Data and Organizational Data...................................................................................5 2.2 Preliminary Steps.................................................................................................................. 7 3 Process Overview Table............................................................................................................. 12 4 Process Steps............................................................................................................................ 14 4.1 Displaying Outbound Delivery Orders.................................................................................14 4.2 Checking the ODO-Item Assignment to the Wave (Optional)..............................................14 4.3 Creating Transportation Units (TU) and Assign a Route and Door......................................15 4.4 Releasing the Picking Wave to Create Warehouse Orders.................................................16 4.5 Processing of Picking Warehouse Orders Using Radio Frequency (RF).............................17 4.6 Repacking the Content of Pick HU into Ship HU.................................................................18 4.7 Completion of the Process Step for the Ship HU.................................................................19 4.8 Processing of the Staging of the Shipping HU.....................................................................20 4.9 Truck Arrives at the Check In and Drives to the Door..........................................................21 4.10 Loading of the Goods from the Staging Area onto the Truck...........................................21 4.11 Loading Completed.......................................................................................................... 22 4.12 Posting Goods Issues, Printing Delivery Notes and Laoding List in SAP.........................23 4.13 Truck Leaves the Door and the Premises........................................................................23

© SAP AG Page 4 of 24

SAP Best Practices

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

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

Purpose

This document describes the complex outbound process, which supports the goods issue and picking operations in your warehouse. It describes the sequence of tasks you need to execute in the system and the corresponding warehouse activities. This process can be used for selling higher quantities (sales unit CAR) for all product stored in the sample warehouse

2

Prerequisites

Master Data and Organizational Data The organizational structure and master data of your company was created in your SAP ERP system during implementation. The organizational structure reflects the structure of your company. The master data represents materials, customers, and vendors, for example, depending on the operational focus of your company. The business process is enabled with this organization-specific master data, examples are provided in the next section. Additional Default Values You can test the scenario with other SAP Best Practices default values that have the same characteristics. Check your SAP ECC system to find out which other material master data exists. Using Your Own Master Data You can also use customized values for any material or organizational data for which you have created master data. For more information on how to create master data, see the Master Data Procedures documentation.

If you integrate plant 1000, storage location YAFS/YROD to the SAP EWM warehouse according to the ERP-EWM Integration (Y31), the following organization structure is relevant for this process: © SAP AG Page 5 of 24

SAP Best Practices

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

Consider that the organization structure in the following tables is not valid any more. Instead customer defined organization units are used. ERP: Organizational Structure Org. data

Value

Company Code

1000

Plant

1000

Storage Location

YAFS

Warehouse Number

EWM

Sales organization

1000

Shipping Point

1000

Distribution Channel

20

Division

10

Master Data Details

Comments

Available for SaleStorage location Dom. Sale Org. Whole Sales

EWM-Organizational Data Master / Org. Data

Value

Supply Chain Unit

for example PL1000

EWM warehouse Number

YEWM

Custodian

for example491000

Entitled to Dispose

for example491000

Goods Receipt Office

SP1000

Master / Org. Data Details

Comments

The customers and product used in this process are created during the activation of the Y33 building block as manual steps. The following customers are used in the preconfigured sample processes: Vendor/customer

Description

EWMCUST001

Customer CUST001

EWMCUST002

Customer CUST002

EWMCUST003

Customer CUST003

EWMCUST004

Customer CUST004

© SAP AG Page 6 of 24

SAP Best Practices

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

The following table provides an overview about the products and their usage: Product

Description

EWMPROD-S01

Small part, fast-moving 01

EWMPROD-S02

Small part, fast-moving 02

EWMPROD-S03

Small part, fast-moving 03

EWMPROD-S04

Small part, fast-moving 04

EWMPROD-S05

Small part, slow-moving 05

EWMPROD-S06

Small part, slow-moving 06

EWMPROD-M01

Medium part 01

EWMPROD-M02

Medium part 02

EWMPROD-M03

Medium part 03

EWMPROD-L01

Large part 01

EWMPROD-L02

Large part 02

EWMPROD-L03

Large part 03

The Outbound Process using Wave, Pick HU, Packing Staging and Loading process is designed to ship bigger quantities (cartons or pallet) of a certain product to the customer. The used sales unit is CAR, which is assigned in the master date to the product listed above for the distribution channel 20-Wholesales.

Preliminary Steps Creating Sales Orders Use In this step, you create the Sales Order (SO), which is the basis for creating an outbound delivery.

Procedure 1. Access the transaction using one of the following navigation options: SAP ECC Menu

Logistics  Sales and Distribution  Sales  Order  Create

Transaction Code

VA01

2. On the Create Sales Order screen, make the following entries, and then choose Execute: Field

User Action and Values

Order Type

OR

Sales Organization

1000

Comment

© SAP AG Page 7 of 24

SAP Best Practices

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

Field

User Action and Values

Distribution Channel

20

Division

10

Comment

3. On the Create Standard Order: Overview screen, make the following entries: Field

User Action and Values

Comment

Sold-to Party



For example EWMCUST001

PO Number



Any external number can be given,

Material



for example EWMPROD-M02

Order Quantity



Sales unit CAR is determined according to the settings in the Material Master

4. Choose Enter. 5. On the Create Standard Order: Overview screen, on the Sales tab page, make the following entries: Field

User Action and Values

Payment Term

0001

6. Choose Enter. 7. Select the line item 10. 8. Choose Goto  Item  Shipping. 9. On the Shipping tab page, make the following entries: Field

User Action and Values

Plant

1000

Storage location

YAFS

User Action and Values

10. On the Create standard order: Item Data screen, go to the Conditions tab page. 11. On the Create Standard Order: Item Data screen, on the Conditions tab page, make the following entries: Field

User Action and Values

Condition Type

PR00

Amount



User Action and Values

Any price can be entered

12. Choose Enter. 13. Choose Goto  Header. 14. On the Create Standard Order: Header Data screen, on the Billing Document tab page, make the following entries: Field

User Action and Values

Inco terms

FOB Walldorf

User Action and Values

15. Choose Enter. © SAP AG Page 8 of 24

SAP Best Practices

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

16. Choose Save.

Create Outbound Delivery in ERP Use In this step, you create the outbound delivery, which is distributed to the inbound delivery.

Procedure 1. Access the transaction using one of the following navigation options: SAP ECC Menu

Logistics  Sales and Distribution  Shipping and Transportation  Outbound Delivery  Create  Single Document  With Reference to Sales Order

Transaction Code

VL01N

2. On the Create Outbound Delivery with Order reference screen, make the following entries: Field

User Action and Values

Shipping point

1000

Selection date



Order



Delivery Type

LF: Delivery

Comment

Enter the sales order number create in previous step

3. Choose Enter. 4. Choose Save. 5. Note down the Outbound Delivery Number.

Result The outbound delivery is created in SAP ERP and distributed to the SAP EWM system.

Creating Default Values for Process Transportation Units Use In this step, you set up user settings that are necessary for Process Transportation Units.

Procedure 1. Access the transaction using the following navigation options:

© SAP AG Page 9 of 24

SAP Best Practices

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

SAP Easy Access Menu

Extended Warehouse Management  Shipping and Receiving  Process Transportation Unit

Transaction Code

/N/SCWM/TU

2. On the Process TU- Warehouse YEWM screen, choose Default Values. If you access the transaction /SCWM/TU for the first time, the system message for maintaining the default values is processed automatically. 3. Make the following entries: Field Name

Description

User Action and Values

Warehouse No.

Warehouse Number

YEWM

Assigmnt Start Date

Assignment Start Date



Assigmnt Start Time

Assignment Start Time



Assignment End Date

Assignment End Date