124 BPP en in-Lean Warehouse

SAP ECC 6.0 EhP3

August 2008

English

Lean Warehouse Management (124)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Business Process Documentation

SAP Best Practices Lean Warehouse Management (124): BPD

Copyright

© Copyright 2008 SAP AG. All rights reserved.

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

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

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

IBM, DB2, DB2 Universal Database, 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 or registered trademarks of IBM Corporation.

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, xApps, xApp, 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 in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

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

© SAP AG of 12


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 F2) or the ENTER key.

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

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

© SAP AG of 12


Contents

1 Purpose........................................................................................................................................ 5

2 Prerequisites................................................................................................................................ 5

2.1 Master Data........................................................................................................................... 5

2.2 Business Conditions..............................................................................................................9

2.3 Roles................................................................................................................................... 10

3 Process Overview Table.............................................................................................................10

4 Business Processes................................................................................................................... 10

4.1 Printing the Picking Document (Lean WM)..........................................................................10

5 Appendix.................................................................................................................................... 12

5.1 Used Forms......................................................................................................................... 12

5.2 Frequently Asked Questions...............................................................................................12

© SAP AG of 12


Lean Warehouse Management

1 Purpose

DocumentThis document describes the business process of Lean Warehouse Management

ScenarioLean Warehouse Management is used to have a picking document in the shipping process.

A picking document is printed when a delivery is created for a storage location which is assigned to a warehouse. This is done automatically. There is no need for a user to deal with transport orders from the warehouse management.

2 Prerequisites

2.1 Master DataSAP Best Practices Standard Values

Essential master and organizational data was created in your ERP system in the implementation phase, such as the data that reflects the organizational structure of your company and master data that suits its operational focus, for example, master data for materials, vendors, and customers.

This master data usually consists of standardized SAP Best Practices default values, and enables you to go through the process steps of this scenario.

Additional Master Data (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.

Use the following master data in the process steps described in this document:

Master / org. data

Value Master / Org. data details Comments

Material H10 Trading with line item category YBNA (PD planning and drop

See sections Business Conditions and Preliminary Steps.

© SAP AG of 12


Master / org. data


shipment)

no Serial no.; no batch

Material H11 Trading Good for Reg. Trading with line item category NORM (PD planning)



Material H12 Trading Good for Reg. Trading with line item category NORM (reorder point planning)

no Serial no.; batch


Material H13 Trading with line item category YBNA (Reorder point planning and drop shipment)



Material H20 Trading Good for Reg. Trading with line item category NORM (reorder point planning) with serial numbers

Only use if you have activated the building blocks Batch Management (117) or Serial Number Management (126).

See the sections Business Conditions and Preliminary Steps.

Material H21 Trading Good for Reg. Trading with line item category NORM (reorder point planning), batch controlled (Exp. Date)



Material H22 Trading Good for Reg. Trading with line item category NORM (reorder point planning), batch controlled (FIFO strategy)


See sections Business Conditions and Preliminary Steps

Material R13 Raw material as subcontracting component with line item, NORM (PD planning), no batch, no serial number


Material R14 Raw material as subcontracting component with line item, NORM (PD


© SAP AG of 12


Master / org. data


planning), no batch, no serial number

Material R16 Raw material as BOM component to S22 with line item, NORM (PD planning), no batch, no serial number






Material R20 Raw material for external procurement with line item, NORM (PD planning), no batch, no serial number


Material R27 Raw material for external procurement with line item, NORM (PD planning), no batch, no serial number


Material R120 Raw material for external procurement for QM processing, with line item, NORM (PD planning), no batch, no serial number


Material R122 Raw material for external procurement, with line item, NORM (PD planning), Batch-Fifo, Procure Import, no serial number


Material R128 Raw material for external procurement for consignment processing with line item, NORM (PD planning), no batch, no serial number


Material R124 Raw material for external procurement with line item, NORM (reorder point planning), Fixed Bin info, no batch, no serial


© SAP AG of 12


Master / org. data


number

Material S21 Semi finished Good for Trading / Repetitive manufacturing with line item category NORM (PD planning), no batch, no serial number


Material S22 Semi finished Good for Reg. Trading / production with line item category NORM (PD planning), phantom assembly, no batch, no serial number


Material S23 Semi finished Good for Reg. Trading / production with line item category NORM (PD planning), for subcontracting process, no batch, no serial number


Material S24 Semi finished Good for Reg. Trading / production with line item category NORM (PD planning), subcontracting, no serial number, batch controlled (FIFO strategy)


Material S25 Semi finished Good for External procurement with line item category NORM (PD planning), subcontracting, no serial number, no batch


Material F29 Finished Good MTS for Process Industry (PD planning)

no Serial no.; with batch


Material F126 Finished Good MTS for Discrete Industry (PD planning)

with Serial no.; with / w/o batch


Sold-to party

100003 Domestic Customer You can test the scenario using another domestic customer.

Ship-to party

100003 Domestic Customer

© SAP AG of 12


Master / org. data


Payer 100003 Domestic Customer

Plant 1000 Plant1

Plant 1100 Plant2

Storage Location

1020 Plant 1000 Shop floor w/o lean WM

Storage Location

1030 Plant 1000 Shipping w/ lean WM

Storage Location

1040 Plant 1000 Shipping w/o lean WM

Storage Location

1050 Plant 1000 Stores w/ lean WM

Storage Location

1060 Plant 1000 Returns

Storage Location

1130 Plant 1100 Shipping w/ lean WM

Storage Location

1140 Plant 1100 Shipping w/o lean WM

Storage Location

1160 Plant 1100 Returns

Shipping Point

1000 Plant 1000 Shipping point 1000

Shipping Point

100R Plant 1000 Shipping point 100R

Shipping Point

1100 Plant 1100 Shipping point 1100

Shipping Point

110R Plant 1100 Shipping point 110R

Sales organization

1000

Distribution channel

10

Division 10

2.2 Business ConditionsThe business process described in this Business Process Procedure is part of a bigger chain of integrated business processes or scenarios. As a consequence, you must have completed the following processes and fulfilled the following business conditions before you can start going through this scenario:

© SAP AG of 12


Business condition Scenario

You have completed all relevant steps described in the Business Process Procedure Prereq. Process Steps (154).

Prereq. Process Steps (154)

2.3 Roles

UseThe following roles must have already been installed to test this scenario in the SAP NetWeaver Business Client (NWBC). The roles in this Business Process Procedure must be assigned to the user or users testing this scenario. You only need these roles if you are using the NWBC interface. You do not need these roles if you are using the standard SAP GUI.

PrerequisitesThe business roles have been assigned to the user who is testing this scenario.

Business role Technical name Process step

Warehouse Clerk SAP_BPR_WAREHOUSESPECIALIST-S

Printing the Picking Document

3 Process Overview TableProcess Step

External Process Reference

Business Condition Business Role

Trans-action code

Expected Results

Printing the Picking Document

– You have created a delivery for storage location, which is Lean-WM relevant

Warehouse Clerk

Automatically / manually by LT31

Picking document printed

4 Business Processes

4.1 Printing the Picking Document (Lean WM)

UseThe purpose of this activity is to print a picking document automatically when a delivery for a WM relevant storage location is created.

© SAP AG of 12


The procedure describes how to continue if the printout is missing.

Procedure

1. The printout should be printed automatically. If that is not the case, continue with the following steps.

2. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics Logistics Execution Outbound Process Goods issue for Outbound Delivery Outbound Delivery Change Single Document

Transaction code VL02N

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role Warehouse Clerk (SAP_BPR_WAREHOUSESPECIALIST-S)

Business role menu Warehouse Management Shipping Change Outbound Delivery

3. On the Change Outbound Delivery screen, enter the delivery number. Check that the storage location used in the delivery is one assigned to warehouse management.

4. Choose menu Environment Document flow or choose F7.

5. Note down the WMS transfer order number: ______________.

6. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics Logistics Execution Internal Whse Processes Stock Transfer Print Transfer Order Single Print Transfer Order

Transaction code LT31

Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role Warehouse Clerk (SAP_BPR_WAREHOUSESPECIALIST-S)

Business role menu Warehouse Management Shipping Print Transfer Order Manually

7. On the Print Transfer Order screen, make the following entries:

Field name Description User action and values Comment

Warehouse Number

Warehouse_1 (for example, 110)

TO Number The noted one from the step above

© SAP AG of 12


Print Code 01

Printer LP01 (or LOCL or other printer)

8. Choose menu Transfer Order Print or Ctrl+P.

9. Exit the transaction.

5 Appendix

5.1 Used Forms

UseThe table below provides details on the forms used in this business process:

Common Form Name

Form Type Used in Process step Output Type

Form Technical Object

Print TO single item SAPscriptPrinting the Picking Document

-none- LVSTAEINZEL

Print transfer order list

SAPscriptPrinting the Picking Document

-none-LVSTALISTE

Print TO single item SAPscriptPrinting the Picking Document

-none-LVSTOSOLO

WMS pick list for several TOs


-none-LVSKOMMIL1

WMS Pick list for several TOs


-none-LVSKOMMIL2

5.2 Frequently Asked Questions Questions Answers

Is it possible to use bar code output for the warehouse?

Yes.

Can we use warehouse management functionality for material management?

Yes, the functionality exists – further requirement analysis needs to be done to determine the project scope.

© SAP AG of 12

124 BPP en in-Lean Warehouse

Documents

Transcript of 124 BPP en in-Lean Warehouse