SCM631

Additional Topics in Warehouse Management
SAP ERP Procurement and Logistics Execution

Date Training Center Instructors Education Website

Participant Handbook
Course Version: 73 Course Duration: 2 Days Material Number: 50086979

An SAP course - use it to learn, reference it for work

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.

Trademarks
• • • • • • Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation. IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and OS/400® are registered trademarks of IBM Corporation. ORACLE® is a registered trademark of ORACLE Corporation. INFORMIX®-OnLine for SAP and INFORMIX® Dynamic ServerTM are registered trademarks of Informix Software Incorporated. UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group. Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML 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, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered trademarks of their respective companies.

• • • •

Disclaimer
THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE, INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTS CONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY KIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOST PROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDED SOFTWARE COMPONENTS.

g200821242125

About This Handbook
This handbook is intended to complement the instructor-led presentation of this course, and serve as a source of reference. It is not suitable for self-study.

Typographic Conventions
American English is the standard used in this handbook. The following typographic conventions are also used. Type Style Example text Description Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths, and options. Also used for cross-references to other documentation both internal (in this documentation) and external (in other locations, such as SAPNet). Example text EXAMPLE TEXT Emphasized words or phrases in body text, titles of graphics, and tables 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. Screen output. This includes file and directory names and their paths, messages, names of variables and parameters, and passages of the source text of a program. Exact user entry. These are words and 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.

Example text

Example text

<Example text>

2008

© 2008 SAP AG. All rights reserved.

iii

About This Handbook

SCM631

Icons in Body Text
The following icons are used in this handbook. Icon Meaning For more information, tips, or background Note or further explanation of previous point Exception or caution Procedures

Indicates that the item is displayed in the instructor's presentation.

iv

© 2008 SAP AG. All rights reserved.

2008

Contents
Course Overview ......................................................... vii
Course Goals ...........................................................vii Course Objectives .....................................................vii

Unit 1: Storage Unit Management...................................... 1
Storage Unit Management.............................................2 Storage Unit Management in Bulk Storage........................ 18 Handling Unit Management.......................................... 31

Unit 2: Hazardous Material Management ........................... 39
Hazardous Material Handling ....................................... 40

Unit 3: Additional Functions in TO Processing ................... 53
Determining the Planned Data and Entering the Actual Data... 54 Transfer Order Split................................................... 59

Unit 4: Mobile Data Entry .............................................. 63
Mobile Data Entry - Technical Implementation .................... 64 Mobile Data Entry - Customizing.................................... 68

Unit 5: Connection of Warehouse Control Units ................. 89
The Technical Connection to a Warehouse Control Unit ........ 90 Using a Warehouse Control Unit - Scenarios ..................... 94

Unit 6: Decentralized Warehouse Management and Technical Themes ..................................................................... 99
Decentralized Warehouse Management..........................100 Technical Topics......................................................108

Index ....................................................................... 115

2008

© 2008 SAP AG. All rights reserved.

v

Contents

SCM631

vi

© 2008 SAP AG. All rights reserved.

2008

Course Overview
This course explains the various settings in Warehouse Management that can be used to optimize warehouse processes. This primarily involves Storage Unit Management and mobile data entry within the warehouse. In addition, this course discusses the settings for hazardous material management and using the decentralized Warehouse Management system.

Target Audience
This course is intended for the following audiences: • Project team members

Course Prerequisites
Required Knowledge
• SCM630 Warehouse Management

Course Goals
This course will prepare you to: • Gain an understanding of the additional topics in the SAP Warehouse Management system and the Customizing options that are available for special company requirements. put your knowledge into practice by completing specially selected exercises in an online system.

Course Objectives
After completing this course, you will be able to: • • Perform functions such as Customizing of Storage Unit Management, radio frequency, and hazardous material management. Describe the Customizing options and settings in the Warehouse Management system for Handling Unit Management, decentralized Warehouse Management, and performance data.

2008

© 2008 SAP AG. All rights reserved.

vii

Course Overview

SCM631

viii

© 2008 SAP AG. All rights reserved.

2008

Unit 1
Storage Unit Management
Unit Overview
This unit provides an overview of the required Customizing settings and the effects of using Storage Unit Management in certain storage types The use of Storage Unit Management is necessary for storage locations that are warehouse managed and which have handling unit requirements. This unit therefore also discusses the effects of Handling Unit Management on the warehouse.

Unit Objectives
After completing this unit, you will be able to: • • • • • • • • Define storage units and explain how to include them in the warehouse structure Create a storage type that uses Storage Unit Management with putaway strategy ‘P’ Process goods movements in the warehouse with storage units Define a bulk storage type in the warehouse number Process putaways of storage units from bulk storage to stock putaways and stock removals. Explain the concept of a handling unit Describe the relationship between handling units and storage units Describe the goods receipt process and goods issue process with handling units

Unit Contents
Lesson: Storage Unit Management .............................................2 Exercise 1: Implementing Storage Unit Management in a New Storage Type .............................................................................7 Lesson: Storage Unit Management in Bulk Storage ........................ 18 Exercise 2: Storage Unit Management in Bulk Storage ................ 21 Lesson: Handling Unit Management .......................................... 31

2008

© 2008 SAP AG. All rights reserved.

1

Unit 1: Storage Unit Management

SCM631

Lesson: Storage Unit Management
Lesson Overview
This lesson describes the Customizing settings that are required to use Storage Unit Management and the effect of these settings at process level.

Lesson Objectives
After completing this lesson, you will be able to: • • • Define storage units and explain how to include them in the warehouse structure Create a storage type that uses Storage Unit Management with putaway strategy ‘P’ Process goods movements in the warehouse with storage units

Business Example
You are using mobile devices in the warehouse and you want to be able to identify pallets according to one of the unique numbers for this warehouse.

Definition of the Storage Unit

Figure 1: Storage Bin with Storage Unit Management

The storage unit is an object that is used only within Warehouse Management. It is a logical composition of one or more material quantities (including pallets or containers) that can be managed as a unit in the warehouse. The identifies the pallets and containers only in terms of the storage unit type. Inventory

2

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Storage Unit Management

management of the pallets or containers can only take place using Handling Unit Management. Storage units can be homogeneous (non-mixed) or mixed. All storage units are assigned a unique number which is maintained in the system as the storage unit number so you can see at any given time where each storage unit is located within the warehouse complex. The type of number assignment and the assignment of the number range intervals for each warehouse number is set in Customizing: Logistics Execution → Warehouse Management → Storage Units → Master Data → Define Number Ranges.

The Classification of the Storage Unit in the Warehouse Structures

Figure 2: Warehouse Structures

If Storage Unit Management is to be used in a warehouse number, you must decide whether the stocks in each storage type should be managed using Storage Unit Management. Depending on your system settings, you can put away several mixed storage units into one storage bin. A warehouse number can contain storage types both with and without Storage Unit Management. However, you cannot activate Storage Unit Management for interim storage areas because the storage unit numbers are assigned only in a transfer order.

2008

© 2008 SAP AG. All rights reserved.

3

Unit 1: Storage Unit Management

SCM631

Figure 3: The Development of the Storage Unit During a Putaway

The storage unit is created in the system as soon as goods are put away in a storage type with active Storage Unit Management. The putaway is executed using the standard procedure for transfer order creation. If an homogeneous storage unit is put away, this putaway is covered by a single transfer order item. If a mixed storage unit is put away, a transfer order item is created for each individual material item in the storage unit. The system will distribute each transfer order item into a separate storage unit so you must create mixed storage units either manually or by using a user exit.

Identification Points and Pick Points

Figure 4: Intermediate Storage Types

4

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Storage Unit Management

In a warehouse complex, the system can use other storage types for Storage Unit Management in addition to the "physical" storage types. These identification point and pick point storage types can be used for goods receipt processes and goods issue processes. Identification point and pick point storage types are only an intermediate stop for materials and are usually assigned other storage types. The identification point storage type might be used for the following reasons: 1. To verifiy the system's information and the actual contents: Since storage units are identified by the storage unit number when they are put away, the contents of each storage unit can be accounted for. This makes it possible to make a rough comparison between the physical contents and the system information for each storage unit. 2. Contour control: An automatic contour control can be carried out at the identification point to determine whether the storage unit is properly loaded. 3. To change the means of transport: The means of transport is changed frequently at the identification point. For example, materials may be moved from a forklift to a conveyor system. 4. To determine the destination storage bin: The destination storage bin in the final storage type is determined at the identification point. The destination storage bin is not assigned until the material arrives at the identification point so that the location of the bin is determined based on the most current information about available space in the storage type. The pick point storage type must always be assigned to a storage type (for example, high rack) if the requirement to remove all stock is active and a return transfer to the source storage bin is not intended. This ensures that the storage unit number of the remaining quantity is retained when a partial withdrawal of the pallet quantity takes place. When the stock removal transfer order is confirmed, the stock of the original storage unit is usually posted to the pick point storage type. You can then decide whether aggregation and a subsequent putaway should occur, whether the pallets should be put away again into the source storage type, or whether they should be put away into a storage type for partial quantities. The transport of partial pallets from the pick point storage type must always be triggered manually or by a user exit.

2008

© 2008 SAP AG. All rights reserved.

5

Unit 1: Storage Unit Management

SCM631

Figure 5: Putaway with Preplanning

Storage units can be generated beforehand for a goods receipt from production. Before the physical goods receipt occurs, the first transfer order is created from the goods receipt area in the identification point with the generation of the storage units. The preplanned storage units can therefore be labelled in advance. If production has finished manufacturing a pallet, the transfer order item for the storage unit can be put away into a high rack, for example. Transaction LT09 in the SAP system allows you to confirm open transfer order items and to generate new transfer orders for this purpose. If too many storage units are preplanned, you can use the report RLVSPLRE to reorganize the unused storage units.

6

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Storage Unit Management

Exercise 1: Implementing Storage Unit Management in a New Storage Type
Exercise Objectives
After completing this exercise, you will be able to: • Create a storage-unit-managed storage type • Post a goods receipt • Create and confirm a transfer order with a storage unit number • Display a storage unit

Business Example
In an area of your warehouse, you manage spools of cable for maintenance purposes. You need to know how many meters of cable are on a spool. The amount of cable on a spool can vary by about 50 meters. You want to manage these spools using Storage Unit Management so you can see how many meters of cable you have for each storage unit. The spools are stored on industrial pallets in a storage type that is divided into aisles.

Task 1:
Check that Storage Unit Management is allowed in warehouse number 1## (“##” stands for your group number) and create a new storage type for storing the spools with Storage Unit Management. 1. 2. Display the control parameters for warehouse number 1## in Customizing and check that Storage Unit Management is active. Create new storage type 008 for spool storage by copying storage type 007. Activate Storage Unit Management and give the new storage type a description of your choice. Create a storage section for the new storage type 008. Use the key 001 and a description of your choice. Set the system so that storage unit type IP (industrial pallet) can be used in storage type 008. In warehouse number 1##, industrial pallets are allowed only in storage bins with bin type P1, P2 and B2. Putaway strategy P (Pallet types) is assigned to the new storage type 008. You must therefore define storage bin sections for using this strategy in your storage type. You need to put away up to four industrial pallets from storage unit type IP for each of the storage bins with bin type P1. The corresponding subdivisions of each storage bin should be defined with the numbers 1 to 4. Continued on next page

3. 4. 5.

2008

© 2008 SAP AG. All rights reserved.

7

Unit 1: Storage Unit Management

SCM631

6.

Define the storage type indicator 008 for the materials that will be put away into your new storage type in the future. Create an entry in the storage type search sequence for this indicator and your new storage type. Create the material C-1030-## with the material type Trading Goods and the industry sector Mechanical Engineering (views Basic Data 1, Basic Data 2, Purchasing, Warehouse Management 1, Warehouse Management 2 and Accounting 1). Use the material C-1030 as a copy template and add the storage type indicator 008 for putaway and stock removal to the view Warehouse Management 1. Create the views for plant 1000 and the warehouse number 1##. A standard spool should have 500 meters of cable. An industry pallet serves as the load carrier. Create the three storage bins P-001, P-002 and P-003 in storage type 008. The storage bins belong to bin type P1.

7.

8.

Task 2:
Test your configuration settings with a putaway. 1. 2. Post a goods receipt without a purchase order in plant 1000 and storage location 01## with 2078 meters of the material C-1030-##. Create a transfer order for the putaway of the material. You have received four spools with the cable lengths 498, 530, 510 and 540. Each spool needs to put away onto an industry pallet. Confirm the transfer order in the background and display the storage bin in which the four pallets were put away. Check the storage bin sections. Hint: Use the Warehouse Management stock overview to display the storage bin.

3.

8

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Storage Unit Management

Solution 1: Implementing Storage Unit Management in a New Storage Type
Task 1:
Check that Storage Unit Management is allowed in warehouse number 1## (“##” stands for your group number) and create a new storage type for storing the spools with Storage Unit Management. 1. Display the control parameters for warehouse number 1## in Customizing and check that Storage Unit Management is active. a) Go to the application menu and choose Tools → Customizing → IMG → Execute Project. Choose SAP Reference IMG to call the Implementation Guide. Choose the Customizing path Logistics Execution → Warehouse Management → Master Data → Define Control Parameters for Warehouse Number. Select your warehouse number and choose Details : In the Control Data/Management area, the SU Management Active indicator is set.

b)

c) 2.

Create new storage type 008 for spool storage by copying storage type 007. Activate Storage Unit Management and give the new storage type a description of your choice. a) b) c) Choose Logistics Execution → Warehouse Management → Master Data → Define Storage Type. Select storage type 007 in warehouse number 1## and choose Copy . As... In the Storage Type field, overwrite the key of the template (007) with the key of your new storage type (008) and change the description to a description of your choice. Set the SU mgmt active indicator, choose Enter to confirm your entries and then save to create the new storage type.

d)

Continued on next page

2008

© 2008 SAP AG. All rights reserved.

9

Unit 1: Storage Unit Management

SCM631

3.

Create a storage section for the new storage type 008. Use the key 001 and a description of your choice. a) b) c) Choose Logistics Execution → Warehouse Management → Master Data → Define Storage Sections. Choose New Entries. Enter the following data in the table and save to create the new storage section. Field Name or Data Type WhN Type Section Storage area name Values 1## 008 001 Total section (for example)

4.

Set the system so that storage unit type IP (industrial pallet) can be used in storage type 008. a) b) c) Choose Logistics Execution → Warehouse Management → Strategies → Activate Storage Bin Type Search. In the Assignments area, choose Storage Type. Choose New Entries and enter the following data into the table: Field Name or Data Type WNo Type 1st Stor. Unit Type Save your entries. Values 1## 008 IP

5.

In warehouse number 1##, industrial pallets are allowed only in storage bins with bin type P1, P2 and B2. Putaway strategy P (Pallet types) is assigned to the new storage type 008. You must therefore define storage bin sections for using this strategy in your storage type. You need to put away up to four

Continued on next page

10

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Storage Unit Management

industrial pallets from storage unit type IP for each of the storage bins with bin type P1. The corresponding subdivisions of each storage bin should be defined with the numbers 1 to 4. a) b) c) Choose Logistics Execution → Warehouse Management → Strategies → Putaway Strategies → Define Strategy for Pallets. Choose Define then New Entries. Enter the following data into the table: Field Name or Data Type WNo Type Section 1st bin item 2nd bin item 3rd bin item 4th bin item Save your entries and leave the table. d) e) Choose Assign then New Entries. Enter the following data into the table: Field Name or Data Type WNo Storage type Storage bin type SUT (Storage unit type) Bin section Save your entries. Values 1## 008 P1 IP A Values 1## 008 A 1 2 3 4

Continued on next page

2008

© 2008 SAP AG. All rights reserved.

11

Unit 1: Storage Unit Management

SCM631

6.

Define the storage type indicator 008 for the materials that will be put away into your new storage type in the future. Create an entry in the storage type search sequence for this indicator and your new storage type. a) b) c) d) e) Choose Logistics Execution → Warehouse Management → Strategies → Activate Storage Type Search. Choose Define then New Entries. Enter the warehouse number 1##, the storage type indicator 008, a description of your choice and then leave the table. Choose Determine Search Sequence then New Entries. Enter the following data into the table: Field Name or Data Type WNo Operation Type Indicator 1st storage type f) Values 1## EI 008 008

Repeat this step for a second entry with the operation indicator A (Stock Removal) and save your entries.

7.

Create the material C-1030-## with the material type Trading Goods and the industry sector Mechanical Engineering (views Basic Data 1, Basic Data 2, Purchasing, Warehouse Management 1, Warehouse Management 2 and Accounting 1). Use the material C-1030 as a copy template and add the storage type indicator 008 for putaway and stock removal to the

Continued on next page

12

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Storage Unit Management

view Warehouse Management 1. Create the views for plant 1000 and the warehouse number 1##. A standard spool should have 500 meters of cable. An industry pallet serves as the load carrier. a) b) Choose Logistics → Logistics Execution → Master Data → Material → Material → Create → Immediately. Enter the material number C-1030-##, choose the industry sector Mechanical Engineering, the material type Trading Goods and the material number C-1030 as the copy template. Choose Enter to confirm your entries. Select the views Basic Data 1, Basic Data 2, Purchasing, Warehouse Management 1, Warehouse Management 2, Accounting 1 and choose Enter. Enter plant 1000, warehouse number 1## and choose Enter again. The reference material is likewise created in plant 1000. Choose Enter to confirm the creation of the individual views. In the detailed display of the Warehouse Management 1 view, add the key 008 to the Stock removal and Stock placement fields. In the Warehouse Management 2 view, enter the loading equipment (LE) quantity 500, the unit (Un) M and the storage unit type (SUT) IP. Once you have confirmed the last data screen, save to create the material.

c)

d) e)

f) g) 8.

Create the three storage bins P-001, P-002 and P-003 in storage type 008. The storage bins belong to bin type P1. a) b) c) d) Choose Logistics → Logistics Execution → Master Data → Warehouse → Storage Bin → Create → Manually Enter warehouse number 1##, storage type 008, storage bin P-001 and choose Enter. Enter the storage section 001 and the storage bin type P1. Save to create the storage bin and repeat the process for the storage bins P-002 and P-003. Exit the transaction by choosing Cancel .

Continued on next page

2008

© 2008 SAP AG. All rights reserved.

13

Unit 1: Storage Unit Management

SCM631

Task 2:
Test your configuration settings with a putaway. 1. Post a goods receipt without a purchase order in plant 1000 and storage location 01## with 2078 meters of the material C-1030-##. a) Choose Logistics → Logistics Execution → Inbound Process → Goods Receipt for Purchase Order, Order, Other Transactions → Enter Goods Receipt for Purchase Order. Select Other for the document reference field (Purchase order is the default setting). The system changes the movement type from 101 to 501 (GI receipt w/o PO). Enter the material number C-1030-## on the Material tab page in the detailed data area. Enter the quantity 2078 on the Quantity tab page. Enter the plant 1000 and the storage location 01## on the Where tab page. Choose Enter to confirm your entries and save to create the document.

b)

c)

d)

Continued on next page

14

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Storage Unit Management

2.

Create a transfer order for the putaway of the material. You have received four spools with the cable lengths 498, 530, 510 and 540. Each spool needs to put away onto an industry pallet. a) Choose Logistics → Logistics Execution → Inbound Process → Goods Receipt for Purchase Order, Order, Other Transactions → Putaway → Create Transfer Order → For Material. Enter the warehouse number 1##, material C-1030-## and choose Enter. Choose TO in Foreground to create the transfer order in the foreground. Delete all system entries from the Palletization area and enter the following data in the Items area to form the four pallets: Field Name or Data Type Dest. target quantity SUT Dest. target quantity SUT Dest. target quantity SUT Dest. target quantity SUT Create the transfer order by saving. Values 498 IP 530 IP 510 IP 540 IP

b) c) d)

Continued on next page

2008

© 2008 SAP AG. All rights reserved.

15

Unit 1: Storage Unit Management

SCM631

3.

Confirm the transfer order in the background and display the storage bin in which the four pallets were put away. Check the storage bin sections. Hint: Use the Warehouse Management stock overview to display the storage bin. a) Choose Logistics → Logistics Execution → Inbound Process → Goods Receipt for Purchase Order, Order, Other Transactions → Putaway → Confirm Transfer Order → Single Document → In One Step. In the Control area, select Background for the foreground/background field and choose Enter to confirm the transfer order. Choose Logistics → Logistics Execution → Internal Whse Processes → Bins and Stock → Display → Total Stock per Material (Warehouse Management). Enter the warehouse number 1##, the material number C-1030-## and choose Enter. Select the line displaying the plant, the storage location and stock and choose Bin Stock. The figures of the four storage units that that were just put away are displayed. Click the coordinates of the storage bin P-001 to display the storage bin master record. Choose the Bin sectioning tab page. There are four quants and four storage units in the bin and one quant in each storage unit in each bin section.

b) c)

d) e)

f) g)

16

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Storage Unit Management

Lesson Summary
You should now be able to: • Define storage units and explain how to include them in the warehouse structure • Create a storage type that uses Storage Unit Management with putaway strategy ‘P’ • Process goods movements in the warehouse with storage units

2008

© 2008 SAP AG. All rights reserved.

17

Unit 1: Storage Unit Management

SCM631

Lesson: Storage Unit Management in Bulk Storage
Lesson Overview
In Storage Unit Management, storage types with putaway strategy B (Bulk Storage) are treated differently. You will become familiar with the particular system behavior and the required system settings so that you make an informed choice about using strategy B.

Lesson Objectives
After completing this lesson, you will be able to: • • Define a bulk storage type in the warehouse number Process putaways of storage units from bulk storage to stock putaways and stock removals.

Business Example
In an area of your warehouse, you manage mixed materials on pallets. These pallets can be stacked in different ways, depending on whether you are stacking industrial pallets or europallets. You want to know how many of each material are stored on a given pallet. You want to manage each pallet of material as a storage unit.

Bulk Storage with Storage Unit Management

Figure 6: Bulk Storage with Storage Unit Management

18

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Storage Unit Management in Bulk Storage

A storage type with putaway strategy B (Bulk Storage) can also use Storage Unit Management. Each addition that you make to existing stock in a storage bin generates a new quant with separate information. The quant information is retained as long as the storage unit is retained. Due to this and the fact that there is no specific storage unit for stock removal processes (only storage bins are proposed), you can assign putaway strategy B to other types of storage as well as typical bulk storage types. Storage Unit Management means that the first in first out (FIFO) principle is kept and the storage bin with the next oldest quant is always proposed. The employee can decide which storage units to remove during stock removal. This also means that it is relatively easy for you to make intentional overdeliveries to prevent small remaining quantities in the bins.

Figure 7: Putaway to Bulk Storage

In bulk storage with Storage Unit Management, putaways and stock removals are continuous and pallets can be “forgotten”. To prevent this, you can use the normal block logic for bulk storage types. • • • A storage bin can be blocked after the first stock removal. This block is removed automatically when the storage bin is empty. Storage bins can be blocked for putaway once a certain period has passed after the first putaway. Such blocks must be removed manually. If you set the block with a time limit, you can specify a blocking reason that is saved in the storage bin master record. The system removes the block when the last stock removal takes place, provided the blocking reason in the storage bin master record is the same as the blocking reason in Customizing.

2008

© 2008 SAP AG. All rights reserved.

19

Unit 1: Storage Unit Management

SCM631

Figure 8: Storage-Unit-Managed Bulk Storage with Partial Pallets and Mixed Storage

In principal, Storage Unit Management allows mixed storage in storage units or in bins with non-mixed storage units. When you activate Storage Unit Management in bulk storage types, you must therefore make a decision regarding the level of the total quant count information. During the stock removal processes, the system does not propose specific storage units for stock removal because it does not know the exact locations of the storage units in the bins. This means that during stock removal transfer orders, the system proposes only storage bins for stock removal. When it does so, it generates just one transfer order item for each quant key. It then checks the total quant count in the storage bin to see whether there is enough stock for the entire transfer order item. If the quantity is not enough, it suggests another storage bin for the stock removal. All stock removal transfer orders in bulk storage types with Storage Unit Management are subject to confirmation. This is because the storage unit is specified only when it has actually been removed (that is, during confirmation). Due to this fact, you should only use bulk storage with Storage Unit Management when mobile devices are used to confirm the transfer orders. If, for example, you do not use a mobile device, a stock removal of eight storage units with a storage unit number with 20 digits would mean an entry of 160 digits.

20

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Storage Unit Management in Bulk Storage

Exercise 2: Storage Unit Management in Bulk Storage
Exercise Objectives
After completing this exercise, you will be able to: • Customize the bulk storage type • Perform a stock removal from bulk storage

Business Example
In an area of your warehouse, you manage mixed materials on pallets. These pallets can be stacked in different ways, depending on whether you are stacking industrial pallets or europallets. You need to see how many of each material are stored on a given pallet. You want to manage each pallet of material as a storage unit

Task 1:
Customize the bulk storage type in your warehouse number. 1. 2. Check the settings of warehouse type 004 in warehouse number 1##. Is partial quantity management allowed? _________ Activate Storage Unit Management for storage type 004. Also, check that the putaway strategy of the storage type is B (Bulk Storage) and that the stock removal strategy is F (FIFO). Allow mixed storage without any limitations. In the storage control of the bulk storage, set the indicator for totals information. The totals information in storage type 004 should be non-batch specific. Define the block structure of storage type 004: When you stack industrial pallets, you can stack them three across and three high (that is, you can put away a total of 12 pallets in each line). When you stack europallets, you can stack them five across and four high (that is, you can put away 20 pallets). The storage bin type is P1. You must allow the storage of storage unit types IP and E1 in storage type 004.

3.

4.

5.

Continued on next page

2008

© 2008 SAP AG. All rights reserved.

21

Unit 1: Storage Unit Management

SCM631

Task 2:
Define a new storage type indicator for the materials that will be put away into storage type 004 in the future. Also, make a corresponding entry in the storage type search sequence. 1. Define the new storage type indicator 004 for mixed bulk storage pallets. Set up the search sequence for this indicator so that materials which have been appropriately flagged in storage type 004 are put away or removed from stock again. Change the master record of the material T-BW04-## by assigning it the storage type indicator 004 (defined in the last step) for putaway and stock removal. Create the storage bins B-001, B-002 and B-003 in storage type 004. The storage bin type is P1.

2.

3.

Task 3:
Test your configuration by placing a material into bulk storage and then removing it again. 1. 2. 3. Post a goods receipt without a purchase order in plant 1000 and storage location 01## with 50 pieces of the material T-BW04-##. Create a transfer order for the putaway of the material. Confirm the transfer order in the background and use the stock overview to display the details of the storage unit. Note the storage unit number: _________________ Post a goods issue for cost center 1000 from plant 1000 and storage location 01## for three pieces of the material T-BW04-##. Create a transfer order for the material document in the background. Confirm the transfer order and assign it the storage unit generated in step two.

4. 5. 6.

22

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Storage Unit Management in Bulk Storage

Solution 2: Storage Unit Management in Bulk Storage
Task 1:
Customize the bulk storage type in your warehouse number. 1. Check the settings of warehouse type 004 in warehouse number 1##. Is partial quantity management allowed? _________ a) In the Implementation Guide, choose Logistics Execution → Warehouse Management → Strategies → Putaway Strategies → Define Strategy for Bulk Storage. Choose Define and select the table entry for the storage type 004 in warehouse number 1##. The Partial quantity management indicator is set.

b)

2.

Activate Storage Unit Management for storage type 004. Also, check that the putaway strategy of the storage type is B (Bulk Storage) and that the stock removal strategy is F (FIFO). Allow mixed storage without any limitations. a) b) c) Choose Logistics Execution → Warehouse Management → Strategies → Putaway Strategies → Define Strategy for Bulk Storage. Choose Activate, select the table entry for the storage type 004 in warehouse number 1## and choose Details . Set the SU mgmt active indicator and enter X in the Mixed storage field (Mixed storage without limitations). Remove the entry 001 from the Return storage type field. Save your changes.

3.

In the storage control of the bulk storage, set the indicator for totals information. The totals information in storage type 004 should be non-batch specific. a) b) c) Choose Logistics Execution → Warehouse Management → Strategies → Putaway Strategies → Define Strategy for Bulk Storage. Choose Define and select the table entry for the storage type 004 in warehouse number 1##. Enter 1 in the Total field and save your change.

Continued on next page

2008

© 2008 SAP AG. All rights reserved.

23

Unit 1: Storage Unit Management

SCM631

4.

Define the block structure of storage type 004: When you stack industrial pallets, you can stack them three across and three high (that is, you can put away a total of 12 pallets in each line). When you stack europallets, you can stack them five across and four high (that is, you can put away 20 pallets). The storage bin type is P1. a) b) c) Choose Logistics Execution → Warehouse Management → Strategies → Putaway Strategies → Define Strategy for Bulk Storage. Choose Block Struct. then New Entries. Enter the following data into the table: Field Name or Data Type WhN Storage type Storage bin type SUT Stacks Stack Height d) Repeat this process for europallets: Field Name or Data Type WhN Storage type Storage bin type SUT Stacks Stack Height Save your changes. Values 1## 004 P1 E1 5 4 Values 1## 004 P1 IP 4 3

Continued on next page

24

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Storage Unit Management in Bulk Storage

5.

You must allow the storage of storage unit types IP and E1 in storage type 004. a) b) c) Choose Logistics Execution → Warehouse Management → Strategies → Activate Storage Bin Type Search. Choose Storage Type then New Entries. Enter the following data into the table: Field Name or Data Type WhN Storage type 1st Stor. Unit Type 2nd Stor. Unit Type Save your changes. Values 1## 004 E1 IP

Continued on next page

2008

© 2008 SAP AG. All rights reserved.

25

Unit 1: Storage Unit Management

SCM631

Task 2:
Define a new storage type indicator for the materials that will be put away into storage type 004 in the future. Also, make a corresponding entry in the storage type search sequence. 1. Define the new storage type indicator 004 for mixed bulk storage pallets. Set up the search sequence for this indicator so that materials which have been appropriately flagged in storage type 004 are put away or removed from stock again. a) b) c) d) e) Choose Logistics Execution → Warehouse Management → Strategies → Activate Storage Type Search. Choose Define then New Entries. Enter the warehouse number 1##, the storage type indicator 004, a description of your choice and then leave the table. Choose Determine search sequence then New Entries. Add two table entries according to the following example: Field Name or Data Type WhN Operation Type Indicator 1st storage type WhN Operation Type Indicator 1st storage type Save your changes. Values 1## E 004 004 1## A 004 004

Continued on next page

26

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Storage Unit Management in Bulk Storage

2.

Change the master record of the material T-BW04-## by assigning it the storage type indicator 004 (defined in the last step) for putaway and stock removal. a) b) c) d) e) Choose Logistics → Logistics Execution → Master Data → Material → Material → Change → Immediately. Enter material number T-BW04-## and choose Enter. Select the Warehouse Management 1 view and choose Enter. Enter your warehouse number 1## and choose Enter. Enter the storage type indicator 004 in the Stock removal and Stock placement fields and save your changes.

3.

Create the storage bins B-001, B-002 and B-003 in storage type 004. The storage bin type is P1. a) b) c) d) Choose Logistics → Logistics Execution → Master Data → Warehouse → Storage Bin → Create → Manually Enter warehouse number 1##, storage type 004, storage bin B-001 and choose Enter. Enter the storage section 001, storage bin type P1 and save to create the storage bin. Repeat this process for the storage bins B-002 and B-003. Choose to leave the transaction. Cancel

Task 3:
Test your configuration by placing a material into bulk storage and then removing it again. 1. Post a goods receipt without a purchase order in plant 1000 and storage location 01## with 50 pieces of the material T-BW04-##. a) Choose Logistics → Logistics Execution → Inbound Process → Goods Receipt for Purchase Order, Order, Other Transactions → Enter Goods Receipt for Purchase Order. Select Other for the document reference field. On the Material tab page, enter the material number T-BW04-##. On the Quantity tab page, enter 50 and on the Where tab page, enter plant 1000 and storage location 01##. Save to create the document.

b) c)

d)

Continued on next page

2008

© 2008 SAP AG. All rights reserved.

27

Unit 1: Storage Unit Management

SCM631

2.

Create a transfer order for the putaway of the material. a) Choose Logistics → Logistics Execution → Inbound Process → Goods Receipt for Purchase Order, Order, Other Transactions → Putaway → Create Transfer Order → For Material Document. The system usually proposes the material document that was last posted. Confirm the system proposal with Enter. Choose Edit → Put Away → Background. The system generates a storage unit. Create the transfer order by saving.

b) c) 3.

Confirm the transfer order in the background and use the stock overview to display the details of the storage unit. Note the storage unit number: _________________ a) Choose Logistics → Logistics Execution → Inbound Process → Goods Receipt for Purchase Order, Order, Other Transactions → Putaway → Confirm Transfer Order → Single Document → In One Step. In the Control area, select Background for the foreground/background field and choose Enter to confirm the transfer order. Choose Logistics → Logistics Execution → Internal Whse Processes → Bins and Stock → Display → Total Stock per Material (Warehouse Management). Enter warehouse number 1## and material T-BW04-## and choose Enter. Select the line that displays the plant stock/storage location stock of storage type 004 and choose Bin Stock. Click the storage unit number to display its “master record”.

b) c)

d) e) f) 4.

Post a goods issue for cost center 1000 from plant 1000 and storage location 01## for three pieces of the material T-BW04-##. a) b) c) Choose Logistics → Logistics Execution → Outbound Process → Goods Issue for Other Transactions → Enter Goods Issue. Enter movement type 201, plant 1000, storage location 01## and choose Enter. Enter cost center 1000, material T-BW04-##, quantity 3 and save to create the document.

Continued on next page

28

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Storage Unit Management in Bulk Storage

5.

Create a transfer order for the material document in the background. a) Choose Logistics → Logistics Execution → Outbound Process → Goods Issue for Other Transactions → Picking → Create Transfer Order → For Material Document. In the control area, choose Background then choose Enter to create the transfer order. Choose Logistics → Logistics Execution → Outbound Process → Goods Issue for Other Transactions → Picking → Confirm Transfer Order → Single Document → In One Step. Choose Enter and attempt to save the document without the assignment of the storage unit. The system displays a screen for entering the storage unit number. Enter the number of the storage unit that was put away in step two and choose Conf. Item in Bckgrnd to confirm the transfer order.

b) 6.

Confirm the transfer order and assign it the storage unit generated in step two. a)

b)

c)

2008

© 2008 SAP AG. All rights reserved.

29

Unit 1: Storage Unit Management

SCM631

Lesson Summary
You should now be able to: • Define a bulk storage type in the warehouse number • Process putaways of storage units from bulk storage to stock putaways and stock removals.

30

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Handling Unit Management

Lesson: Handling Unit Management
Lesson Overview
If a warehouse-managed storage location also has a handling unit requirement, there are some points to note in Warehouse Management. This unit does not describe handling unit management in detail; instead, it focuses on the effects that handling unit management has on the warehouse.

Lesson Objectives
After completing this lesson, you will be able to: • • • Explain the concept of a handling unit Describe the relationship between handling units and storage units Describe the goods receipt process and goods issue process with handling units

Business Example
Stocks in a certain warehouse-managed storage location must always be packed and need to be identified by a unique number. You therefore use handling unit management.

Handling Unit Management
A handling unit is a unit consisting of material to packed and packaging material that is identified by a unique number. It can be used in the entire logistics process and, if required, can also be used outside your SAP system. This option of using handling units across processes constitutes the main difference between handling units and their “predecessors”, shipping units. A shipping unit is a unit that is generated by packing in the delivery. This means it can only be used in the delivery process. Note: As of SAP R/3 4.6C, the term handling unit replaces the term shipping unit. As a result, all units that are created by packing are called “handling units” in the system. Handling unit management was developed to simplify the technical system processing of logistics processes. Various material movements are performed in packages. Usually, it is sufficient to enter the identification number of the handling unit. You can use this identification number at any time to call up detailed information about the contents and packaging. Each handling unit also has a “history”, in other words a cross-process, chronological documentation of all its movements. The handling unit identification number can be unique either within a client, or across systems. If the number only needs to be unique at

2008

© 2008 SAP AG. All rights reserved.

31

Unit 1: Storage Unit Management

SCM631

client level, number assignment is made according to number ranges. For unique identifcation of the handling unit both inside and outside the SAP system, a Serial Shipping Container Code (SSCC) is used. The system also uses number ranges here, but with the addition of other elements. Note: The SSCC complies with coding conventions of European Article Number EAN 128. This is an eighteen-digit number used to identify logistics units. The goal is to identify a package uniquely using its SSCC for at least one year, worldwide.

Handling Units in Warehouse Management

Figure 9: Handling Units and Warehouse Management

If you use handling unit management in Warehouse Management, you must activate storage unit management for all storage types in which you want to store handling units. During the putaway, the system creates a storage unit for each handling unit of the transfer order's reference document. This storage unit has the same identification number as its “handling unit sister”. When there are nested handling units, the storage unit corresponds to the outer-most handling unit. When partial quantities are picked from such multi-level handling units, the system displays a screen asking you for the lower-level handling unit for the pick or complete stock pick. The numbering of the storage units is controlled by the number assignment parameters that are set for the handling units during handling unit management and not by the number range(s) of Storage Unit Management. You must therefore activate the storage unit number length conversion in Storage Unit Management

32

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Handling Unit Management

Customizing. You must use the same number of signs that is used in the identification numbers for the handling units. The setting applies to all clients (menu path in the Implementation Guide: Logistics Execution → Warehouse Management → Storage Units → Master Data → Define Number Ranges → Conversion exit for storage unit number).

Logistics Processes with Handling Units

Figure 10: Goods Receipt with Handling Units

In addition to goods receipts from production, goods receipts for purchase orders constitute a large part of the goods receipt volume. The shipping notification which the vendor uses to notify the goods recipient may also contain packing information. If the SAP system of the goods recipient receives a shipping notification in IDoc format, it can use this data to generate an inbound delivery automatically. If the inbound IDoc does not contain any packing information and the goods receipt is posted to an HU-managed storage location, the items of the inbound delivery must be packed. Processing cannot continue until handling units are generated in the inbound delivery. When handling units are generated, an inspection lot can be created in quality management and the stock category for the goods receipt posting is set to “stock in quality inspection”. You can use Customizing to decide whether the putaway or goods receipt posting occurs first. If an inbound delivery contains more than one handling unit, the system generates a separate transfer order for each storage unit that is to be put away.

2008

© 2008 SAP AG. All rights reserved.

33

Unit 1: Storage Unit Management

SCM631

Figure 11: Goods Issue with Handling Units

If the picking location of the delivery item requires handling units, the system does not allow packing in the outbound delivery. If Warehouse Management is inactive, complete handling units can be assigned to the delivery items in the packing dialog of the outbound delivery or the packing station (transaction HUPAST). If the picking location is warehouse managed, a direct assignment cannot be made. The handling units (or their corresponding storage units) are assigned to the outbound delivery by the transfer order instead.

Figure 12: Pick-Handling Unit

34

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Handling Unit Management

Partial stock removals from existing handling units are only possible if at least one pick-handling unit (a picking container) was created in advance and assigned to the transfer order. This step can be made automatic in handling unit management Customizing. When the transfer order is confirmed, the system assigns the complete stock removals and pick-handling units to the outbound delivery.

2008

© 2008 SAP AG. All rights reserved.

35

Unit 1: Storage Unit Management

SCM631

Lesson Summary
You should now be able to: • Explain the concept of a handling unit • Describe the relationship between handling units and storage units • Describe the goods receipt process and goods issue process with handling units

36

© 2008 SAP AG. All rights reserved.

2008

SCM631

Unit Summary

Unit Summary
You should now be able to: • Define storage units and explain how to include them in the warehouse structure • Create a storage type that uses Storage Unit Management with putaway strategy ‘P’ • Process goods movements in the warehouse with storage units • Define a bulk storage type in the warehouse number • Process putaways of storage units from bulk storage to stock putaways and stock removals. • Explain the concept of a handling unit • Describe the relationship between handling units and storage units • Describe the goods receipt process and goods issue process with handling units

2008

© 2008 SAP AG. All rights reserved.

37

Unit Summary

SCM631

38

© 2008 SAP AG. All rights reserved.

2008

Unit 2
Hazardous Material Management
Unit Overview
This unit describes how to use the hazardous material master to declare materials as hazardous materials and how to put these away into certain areas of the warehouse.

Unit Objectives
After completing this unit, you will be able to: • • • Create a hazardous material master record Define a material as a hazardous material Customize storage procedures for handling hazardous materials

Unit Contents
Lesson: Hazardous Material Handling ........................................ 40 Exercise 3: Hazardous Material Handling................................ 45

2008

© 2008 SAP AG. All rights reserved.

39

Unit 2: Hazardous Material Management

SCM631

Lesson: Hazardous Material Handling
Lesson Overview
This lesson describes the Customizing settings that are required to maintain the hazardous material master record and to activate the hazardous materials check at storage type level and storage section level.

Lesson Objectives
After completing this lesson, you will be able to: • • • Create a hazardous material master record Define a material as a hazardous material Customize storage procedures for handling hazardous materials

Business Example
Certain materials need to be declared as hazardous materials and therefore need to be put away into a specific storage type.

Hazardous Materials

Figure 13: Hazardous Materials Handling

40

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Hazardous Material Handling

The aim of hazardous material handling is to store hazardous materials separately according to storage class and water pollution class. The storage class categorizes the hazardous materials according to their storage conditions. Examples include: • • • • Storage class 1: Explosive materials Storage class 3.B: Combustible liquids Storage class 6.1 Poisonous materials Storage class 7 Radioactive materials

The water pollution class classifies hazardous materials according to their level of water pollution: • • • Water pollution class 1: Low hazard to water Water pollution class 2: Hazard to water Water pollution class 3: Severe hazard to water

Hazardous Materials Master Data

Figure 14: Hazardous Material Handling: Master Data

Materials are assigned to a hazardous material within a geographical region. The hazardous material master record stores data such as the storage class and the water pollution class. The geographical region is derived from the assignment of a regional code to a warehouse number and to the hazardous material master record. If a material is to be put away to different plants or warehouse numbers with different regional codes, you must maintain several hazardous material master records with the same key but with different regional codes. Each combination of key and regional code is assigned separate data so that you can maintain different information for each regional code. In the warehouse number, you can decide for

2008

© 2008 SAP AG. All rights reserved.

41

Unit 2: Hazardous Material Management

SCM631

each storage type whether hazardous material handling is active. The handling of hazardous materials is activated at storage type level or section level. You can activate hazardous material handling for each storage type, except the interim storage area. Do not assign a water pollution class or storage class to storage types that will not be assigned hazardous materials. However, there must be an entry for each storage type in the assignment table of permitted storage classes, otherwise you will be unable to put away any materials. Storage types that are intended for hazardous materials can be assigned several permitted storage classes. An entry must be made for each storage class in the table of permitted storage classes. In order to print the inventory list for the fire department, all storage bins in the warehouse number must be assigned a fire-containment section.

Hazardous Materials in Warehouse Management
The storage class and water pollution class of a hazardous material are taken into account during the storage type search. This means that a separate entry needs to be maintained in the storage type search table for each storage class/water pollution class combination. The additional information for the storage type search also needs to be taken into account.

Figure 15: Storage Type Control and Storage Section Control

If hazardous material handling is active at the storage section level, the storage class and the water pollution class are taken into account during the storage section search. This means that a sophisticated check of the following criteria can be achieved: • • • Storage section indicator Storage class Water pollution class

42

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Hazardous Material Handling

There are three reports in the Warehouse Management system that provide an overview of the quantity of stored hazardous materials: • The fire department inventory list (report RLS10060) displays information about the storage class, water pollution class and the amount of water pollutants among the hazardous materials in your warehouse. You can choose to run the report for a range of fire-containment sections and storage types within the warehouse or for the entire warehouse. The correct storage check (report RLS10070) creates a list for each storage type that lists the number of bins that were checked, the number of quants that were correctly stored and the number of quants that were stored incorrectly due to the hazardous material storage parameters that were set up for your warehouse. The hazardous substance list (report RLS10080) lists materials by hazardous material record number, concentration, hazardous material warning, aggregate state and quantity. This report only selects materials from storage types that are defined as storage types for hazardous materials in the WM system.

2008

© 2008 SAP AG. All rights reserved.

43

Unit 2: Hazardous Material Management

SCM631

44

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Hazardous Material Handling

Exercise 3: Hazardous Material Handling
Exercise Objectives
After completing this exercise, you will be able to: • Configure the storage of hazardous materials • Create a hazardous material master record and assign it to a material master record

Business Example
The engineering department has requested a new lubricant for use in the pump assembly. This new lubricant is considered a hazardous material and must be stored accordingly. You need to configure your warehouse for storing hazardous materials. You then need to create the hazardous material master records and assign them to the appropriate material master records.

Task 1:
Configure warehouse number 1## for storing hazardous materials. 1. Hazardous material storage type 006 already exists; however, no storage bins have yet been created. Create storage bins 001 to 004 in storage section 001. Assign the fire-containment section B to the storage bins. Each storage bin can hold a maximum weight of 1000 kilograms. In Warehouse Management Customizing, activate the hazardous materials check in warehouse number 1## at storage type level. Normally, the hazardous material check is active for all storage types (except for the interim storage area) so that hazardous materials are not stored incorrectly. For the purposes of this exercise, we will activate the hazardous materials check for just storage type 006. The lubricant is considered a water pollutant. Once you have activated the hazardous material check, check the regional code of your warehouse number. Configure storage type 006 so that you may store hazardous materials from storage class 3A. If hazardous materials are received that are assigned storage class 3A and water pollution class 2, they should be stored in storage type 006. Change the storage type search sequence accordingly.

2.

3. 4. 5.

Continued on next page

2008

© 2008 SAP AG. All rights reserved.

45

Unit 2: Hazardous Material Management

SCM631

Task 2:
Create a hazardous material master record and link it to a material master record. 1. Create the hazardous material master record T-GEF01-## with a description of your choice. Use the regional code of warehouse number 1## (see task 1, step 3). The hazardous material belongs to warehouse class 3A and is water polluting. The material is fluid. Create the new material master record T-BW22-## for plant 1000, warehouse number 1## and storage location 01## as a copy of the material T-BW20-##. The new material is a trading good of the “Mechanical Engineering” industry. Create the following views: Basic Data 1, Purchasing, General Plant Data/Storage 1, Warehouse Management 1, Warehouse Management 2 and Accounting 1. Assign the hazardous material master record T-GEF01-## to the Material Management 1 view.

2.

Task 3:
Test your configuration by using the example of a putaway. 1. 2. Post a goods receipt without reference for 500 pieces of the material T-BW22-## in plant 1000, storage location 01##. Create and confirm a transfer order for the putaway. You will receive an error during processing because the system will not be able to find a bin for the last quant of materials. Confirm the warning message and create the transfer order. Leave the fifth pallet in the goods receipt area.

46

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Hazardous Material Handling

Solution 3: Hazardous Material Handling
Task 1:
Configure warehouse number 1## for storing hazardous materials. 1. Hazardous material storage type 006 already exists; however, no storage bins have yet been created. Create storage bins 001 to 004 in storage section 001. Assign the fire-containment section B to the storage bins. Each storage bin can hold a maximum weight of 1000 kilograms. a) b) c) d) 2. Choose Logistics → Logistics Execution → Master Data → Warehouse → Storage Bin → Create → Manually. Enter warehouse number 1##, storage type 006, storage bin 001 and choose Enter. Enter the storage section 001, fire-containment section B, maximum weight 1000 and save to create the storage bin. Repeat this process for the storage bins 002, 003 and 004. Choose to leave the transaction. Cancel

In Warehouse Management Customizing, activate the hazardous materials check in warehouse number 1## at storage type level. Normally, the hazardous material check is active for all storage types (except for the interim storage area) so that hazardous materials are not stored incorrectly. For the purposes of this exercise, we will activate the hazardous materials check for just storage type 006. The lubricant is considered a water pollutant. a) b) c) d) Choose Tools → Customizing → IMG → Execute Project then SAP Reference IMG. Choose Logistics Execution → Warehouse Management → Hazardous Materials → Strategies → Activate Hazardous Material Management. Choose Activate. Select storage type 006 in warehouse number 1## and enter 1 in the Hazardous Mat. Mgmt field (Hazardous material check only at storage type level). Set the value in the WPC Water Pollution Class column to 2 (Water pollutant). Save your changes.

3.

Once you have activated the hazardous material check, check the regional code of your warehouse number. a) b) Choose Logistics Execution → Warehouse Management → Hazardous Materials → Strategies → Activate Hazardous Material Management. Choose Warehouse number and select the table entry for warehouse number 1##. The warehouse is assigned regional code D. Continued on next page

2008

© 2008 SAP AG. All rights reserved.

47

Unit 2: Hazardous Material Management

SCM631

4.

Configure storage type 006 so that you may store hazardous materials from storage class 3A. a) b) c) Choose Logistics Execution → Warehouse Management → Hazardous Materials → Strategies → Activate Hazardous Material Management. Choose Storage Type then New Entries. Enter warehouse number 1##, storage type 006, storage class 3A and save your changes.

5.

If hazardous materials are received that are assigned storage class 3A and water pollution class 2, they should be stored in storage type 006. Change the storage type search sequence accordingly. a) b) c) Choose Logistics Execution → Warehouse Management → Hazardous Materials → Strategies → Activate Hazardous Material Management. Choose Determine search sequence then New Entries. Enter the following data: Field Name or Data Type WNo Operation Storage Class (Stor.Class) WPC Water Pollution Class 1st Storage Type d) Values 1## E 3A 2 006

Repeat this step for stock removal management and replace the operation indicator E with A. Save your changes.

Continued on next page

48

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Hazardous Material Handling

Task 2:
Create a hazardous material master record and link it to a material master record. 1. Create the hazardous material master record T-GEF01-## with a description of your choice. Use the regional code of warehouse number 1## (see task 1, step 3). The hazardous material belongs to warehouse class 3A and is water polluting. The material is fluid. a) b) c) Choose Logistics → Logistics Execution → Master Data → Material → Hazardous Material → Create. Enter T-GEF01-## in the Hazardous material number field and D in the Regional codes field. Choose Enter. Enter a hazardous material text of your choice (for example, Lubricant group 01, enter the storage class 3A, the water pollution class 2 and the state of matter 2 (Fluid). Save to create the hazardous material master record.

d) 2.

Create the new material master record T-BW22-## for plant 1000, warehouse number 1## and storage location 01## as a copy of the material T-BW20-##. The new material is a trading good of the “Mechanical Engineering” industry. Create the following views: Basic Data 1, Purchasing, General Plant Data/Storage 1, Warehouse Management 1, Warehouse Management 2 and Accounting 1. Assign the hazardous material master record T-GEF01-## to the Material Management 1 view. a) b) Choose Logistics → Logistics Execution → Master Data → Material → Material → Create → Immediately. Enter the material number T-BW22-##, choose the industry sector Mechanical Engineering, the material type Trading Goods and the material number T-BW20-## as the copy template. Choose Enter to confirm your entries. Select the views Basic Data 1, Purchasing, General Plant Data/Storage 1, Warehouse Management 1, Warehouse Management 2, Accounting 1 and choose Enter. Enter plant 1000, storage location 01##, warehouse number 1## and choose Enter. The reference material is created for the same organizational units. Choose Enter to confirm the creation of the individual views. In the Warehouse Management 1 view, enter T-GEF01-## in the Hazardous material number field. Once you have confirmed the last data screen, save to create the material. Continued on next page

c)

d)

e)

f)

2008

© 2008 SAP AG. All rights reserved.

49

Unit 2: Hazardous Material Management

SCM631

Task 3:
Test your configuration by using the example of a putaway. 1. Post a goods receipt without reference for 500 pieces of the material T-BW22-## in plant 1000, storage location 01##. a) Choose Logistics → Logistics Execution → Inbound Process → Goods Receipt for Purchase Order, Order, Other Transactions → Enter Goods Receipt for Purchase Order. Select Other for the document reference field (Purchase order is the default setting). The system changes the movement type from 101 to 501 (GI receipt w/o PO). Enter the material number T-BW22-## on the Material tab page in the detailed data area. Enter the quantity 500 on the Quantity tab page. Enter the plant 1000 and the storage location 01## on the Where tab page. Choose Enter to confirm your entries and save to create the document.

b)

c)

d) 2.

Create and confirm a transfer order for the putaway. You will receive an error during processing because the system will not be able to find a bin for the last quant of materials. Confirm the warning message and create the transfer order. Leave the fifth pallet in the goods receipt area. a) Choose Logistics → Logistics Execution → Inbound Process → Goods Receipt for Purchase Order, Order, Other Transactions → Putaway → Create Transfer Order → For Material Document. Choose Enter and then Edit → Put Away→ Foreground: The system should propose the storage bin 001 in storage type 006 for storing the first quant. Confirm this and the next three system proposals with Enter. The fifth quant cannot be stored in storage type 006 because it contains only four storage bins. Choose Cancel .

b)

c)

d) e)

and then Save Select the fifth item, choose Delete selected items . Choose Yes when the system asks you whether the generated items are sufficient.

50

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Hazardous Material Handling

Lesson Summary
You should now be able to: • Create a hazardous material master record • Define a material as a hazardous material • Customize storage procedures for handling hazardous materials

2008

© 2008 SAP AG. All rights reserved.

51

Unit Summary

SCM631

Unit Summary
You should now be able to: • Create a hazardous material master record • Define a material as a hazardous material • Customize storage procedures for handling hazardous materials

52

© 2008 SAP AG. All rights reserved.

2008

Unit 3
Additional Functions in TO Processing
Unit Overview
This unit provides an overview of the options during planned data entry and actual data entry and the transfer order split.

Unit Objectives
After completing this unit, you will be able to: • • • Define a profile for determining the planned times and entering the actual data during the creation of the transfer order Maintain all necessary data for determining the planned time Define a split profile for the transfer order split

Unit Contents
Lesson: Determining the Planned Data and Entering the Actual Data ... 54 Lesson: Transfer Order Split ................................................... 59

2008

© 2008 SAP AG. All rights reserved.

53

Unit 3: Additional Functions in TO Processing

SCM631

Lesson: Determining the Planned Data and Entering the Actual Data
Lesson Overview
This lesson explains the principles of determining the planned time during the creation of the transfer order and the entry of the actual data during the confirmation of the transfer order.

Lesson Objectives
After completing this lesson, you will be able to: • • Define a profile for determining the planned times and entering the actual data during the creation of the transfer order Maintain all necessary data for determining the planned time

Business Example
You will enter the actual time required to process a transfer order once it is complete. In the meantime and so that you can respond quickly to any problems that may occur, you use past figures and the planned time to calculate the approximate time required for transfer order processing. You will therefore be able to compare the planned time and the actual time. In the future, employees will also enter their personnel numbers during transfer order confirmation to allow for specific queries.

54

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Determining the Planned Data and Entering the Actual Data

Determining the Planned Time

Figure 16: Example: Goods Receipt

In a warehouse number, you can use assign a performance data profile to certain goods movements and the storage types that are involved to control the determination of the planned times and the entry of the actual data. If you intend to enter the actual data after the determination of the planned times (during the confirmation of the transfer order), you can compare the planned time and the actual time taken for a specific process. Planned data and actual data are both updated at transfer order header level. If you intend to calculate the planned time for a certain operation, the planned time for this item is also determined at item level. The actual data is only updated at header level because it is usually whole transfer orders rather than individual items that are cinformed. You can also enter the personnel number of the warehouse worker as well as the actual time required.

2008

© 2008 SAP AG. All rights reserved.

55

Unit 3: Additional Functions in TO Processing

SCM631

Figure 17: Calculation of the Planned Time

The planned processing time in the transfer order header is the processing time that the system calculates for the entire transfer order. The planned transfer order processing time references the time unit (for example, minutes or seconds) that is calculated for the warehouse number. This is the total of the planned processing times for the transfer order items and the setup and travel times of the storage types that are involved. TIME(WM) = SUM[PLANNED(ITEM)] + PLANNED(SETUP) + PLANNED(TRAVEL TIME) The setup time and travel time can be determined only once at header level. An implicit transfer order split may therefore occur if there are several transfer order items with different destination storage types or source storage types that contain different parameters. The planned processing time for the transfer order item is calculated from a constant processing time. Example: the planned setup time for the stock removal process for a transfer order item plus the quantity dependent or variable processing time (for example, the processing time required to pick 10 cartons from a storage bin). The formula is: PLANNED(ITEM) = PLANNED(CONSTANT) + PLANNED(VARIABLE) The values for calculating the planned time at item level are stored in the maintain warehouse workload table. The total planned processing time includes the planned processing time in WM plus the planned processing time that was transferred from an external system to WM: • TIME(TOTAL) = TIME(WM) + TIME(EXTERNAL)

56

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Determining the Planned Data and Entering the Actual Data

As well as determining the planned time, you can use the performance data profile to control whether it is necessary to specify the actual time and the personnel number during the confirmation of the transfer order.

Actual Data in the Transfer Order
• • • Processor, actual processing time Kept in the transfer order header Separate confirmation dialog – – – – Confirmation of individual transfer orders by processor Confirmation of transfer orders by central personnel (rapid creation) Correction dialog for users with special authorization Customized data entry

Actual data is the actual information about the processing of a transfer order. This data includes the personnel number of the worker and the actual time or the stop and start times. The data is stored in the transfer order header. An indicator in the transfer order controls whether it is necessary to enter the actual time for a transfer order and what format this must take during the entry of performed activities. This indicator also controls which dialog box is displayed. Depending on the settings you choose, the system displays the fields that are relevant for data entry. Afterwards, you can use transaction LT1A to correct the data in the transfer order. The actual data can be used in different ways. For example, you can use the assignment of an employee to a transfer order to check the execution of the transfer order. Because you can change the actual data at a later date, you can also enter the completed work as statistical information for transfer orders that do not require confirmation. It could also be used to determine incentive wages.

2008

© 2008 SAP AG. All rights reserved.

57

Unit 3: Additional Functions in TO Processing

SCM631

Lesson Summary
You should now be able to: • Define a profile for determining the planned times and entering the actual data during the creation of the transfer order • Maintain all necessary data for determining the planned time

58

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Transfer Order Split

Lesson: Transfer Order Split
Lesson Overview
This lesson describes the configuration of a split profile and its effects on the creation of the transfer order.

Lesson Objectives
After completing this lesson, you will be able to: • Define a split profile for the transfer order split

Business Example
By default, outbound deliveries are picked using a transfer order for each outbound delivery. This may mean that some transfer orders are created that contain too many items for an employee. To distribute the workload in the warehouse more evenly, you use a split profile to divide the transfer order into several smaller transfer orders.

Transfer Order Split

Figure 18: Split Criteria

Transfer orders can be split to achieve an even distribution of the workload in the warehouse. The system first creates an “internal” transfer order which references the request document (delivery/transfer requirement/posting change notice). According to the split profile that is assigned to this movement, the transfer order may be divided into several smaller transfer orders. The assignment of the split profile is determined by the key for the movement type, the source storage type and the destination storage type. Each split profile should also be assigned a sort profile so that the transfer order items are ordered correctly before the split. It is often appropriate to sort according to the Picking sort field in the storage bin master

2008

© 2008 SAP AG. All rights reserved.

59

Unit 3: Additional Functions in TO Processing

SCM631

record. This method orders the storage bins in a path sequence that is optimal. If you use picking areas, you can split the transfer order according to a picking area with optimal paths. Other standard split criteria include parameter limits according to weight, volume or planned time. If different criteria are required for the transfer order split, use SAP enhancement MWMTO012. You can use this enhancement to make any field of the transfer order a criterion for a transfer order split. The application also allows you to sort the contents of the transfer order (by assigning a sort profile to the split profile, you can order the items in the sequence you require without actually performing a split).

Figure 19: Transfer Order Split

In addition to the split profile, there are also criteria which which lead to an automatic split. These split criteria generate a transfer order split automatically, even if a split profile is not defined. Examples of these split criteria include different header parameters when the planned time is determined and a change of queue when mobile data entry is used with queue management. Each handling units generates a separate transfer order during inbound delivery processing.

60

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Transfer Order Split

Lesson Summary
You should now be able to: • Define a split profile for the transfer order split

2008

© 2008 SAP AG. All rights reserved.

61

Unit Summary

SCM631

Unit Summary
You should now be able to: • Define a profile for determining the planned times and entering the actual data during the creation of the transfer order • Maintain all necessary data for determining the planned time • Define a split profile for the transfer order split

62

© 2008 SAP AG. All rights reserved.

2008

Unit 4
Mobile Data Entry
Unit Overview
This unit provides an overview of the SAP radio frequency solution which makes it possible to work anywhere in the warehouse.

Unit Objectives
After completing this unit, you will be able to: • • • • Describe how the mobile devices are connected technically Set up menu management Set up the verification control Set up queue management

Unit Contents
Lesson: Mobile Data Entry - Technical Implementation .................... 64 Lesson: Mobile Data Entry - Customizing .................................... 68 Exercise 4: Mobile Data Entry in the Warehouse ....................... 73

2008

© 2008 SAP AG. All rights reserved.

63

Unit 4: Mobile Data Entry

SCM631

Lesson: Mobile Data Entry - Technical Implementation
Lesson Overview
This lesson describes the technical implementation of mobile data entry in the warehouse. The basics of this implementation are introduced.

Lesson Objectives
After completing this lesson, you will be able to: • Describe how the mobile devices are connected technically

Business Example
You want to use the radio frequency solution to introduce mobile data entry to your warehouse complex. You need to know the technical requirements for this and what methods of implementation there are.

The Radio Frequency Solution

Figure 20: Radio Frequency in Warehouse Management

SAP developed the radio frequency solution (RF) for Warehouse Management in SAP 4.6B. When RF is used in the warehouse, employees can perform warehouse activities quickly and while on-the-move. The solution is hardware-independent so you can continue to use any existing mobile data-entry devices (mobile devices) that you have. You can use graphical and character-based handheld devices in combination with each other. Depending on the presentation device, the various functions are executed by pushbutton, touch screen, function key or by scanning

64

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Mobile Data Entry - Technical Implementation

a barcode. In each case, the data is transferred and updated in the database immediately (it is no longer necessary to send IDocs). The RF solution replaces the need for the interface of a middleware provider.

System Landscape for RF Terminals
• Different connection types of RF terminals - Graphical terminals that use the SAP GUI - Character-based terminals that use Telnet and the SAPConsole - Character-based terminals that use proprietary protocol (supported by hardware vendors) and the SAPConsole Screens and flow logic are developed entirely in the development environment of SAP You can replace each screen with your own specific screen without having to change the processing logic (dynpro exit) New device types are implemented easily Recovery is possible if the connection is lost and you set up the connection again

• • • •

Several things must be taken into account for the implementation of the RF solution. Depending on whether you are using a graphical or character-based mobile device, it requires certain specifications or a Windows NT server/Windows 2000 server. Graphical handheld devices must be configured for the installation of the SAP GUI. SAP provides the SAPConsole for character-based handheld devices which must be installed on a Windows NT or Windows 2000 server in conjunction with a Telnet server. There are also hardware providers who have solutions that can replace the SAPConsole/Telnet combination. If you use an SAP system for recovery purposes, the two-step confirmation function must be active. Alternatively, you can use the controller (if you are using one) to keep RF users connected to the SAP system. This means that if the connection is temporarily lost (by a loss of transmission, for example), the controller keeps the RF user logged on to the SAP system. The RF solution supports two screen formats (8x40 and 16x20) for the default RF transactions which means that two physical screens exist for each logical screen. If the devices use a different format, there is a dynpro exit for each logical screen which can be used to adjust the dynpros individually and without having to change the flow logic. New RF transactions and screens are developed in the ABAP development environment. There must be an application user in the SAP system for each RF user.

2008

© 2008 SAP AG. All rights reserved.

65

Unit 4: Mobile Data Entry

SCM631

Figure 21: The Connection of the Mobilde Device to the SAP System

The infrastructure for character-based handheld devices could be implemented as shown above. In this scenario, the SAPConsole, Telnet server and RF controller are installed on a Windows NT server which is integrated into the network. The SAPConsole is responsible for creating the data connection to the SAP system, converting the graphical information into character-based information, and the connection to the RF controller. The SAPConsole is delivered with the SAP GUI. If just graphical handheld devices are used, you do not require the NT server with the SAPConsole. In this situation, the system transmits the data to the handheld device directly.

66

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Mobile Data Entry - Technical Implementation

Lesson Summary
You should now be able to: • Describe how the mobile devices are connected technically

2008

© 2008 SAP AG. All rights reserved.

67

Unit 4: Mobile Data Entry

SCM631

Lesson: Mobile Data Entry - Customizing
Lesson Overview
This lesson describes the Customizing settings that are required to use the RF solution in the warehouse.

Lesson Objectives
After completing this lesson, you will be able to: • • • Set up menu management Set up the verification control Set up queue management

Business Example
The RF users are to be assigned individual menus in the warehouse complex. You use queue management to assign transfer orders and employees to certain areas in the warehouse. You also use data verification to reduce the number of errors.

Mobile Data Entry in the Warehouse

Figure 22: RF Screen

SAP delivers a default menu with all standard RF transactions in warehouse number 001 of the delivery clients. You can use this default menu to create custom menus for individual users. The RF users are created with the same

68

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Mobile Data Entry - Customizing

key as the users in the SAP system and are assigned an initial menu. You can determine whether users are able to change the initial menu when they log on to the handheld device. Users may have several options, depending on the menu they have been assigned. This selection screen corresponds to the dynamic menu. You use Customizing to determine whether the selection of an activity takes a user to another dynamic menu with further options or whether the selection executes a transaction. SAP has defined the following activities as RF transactions: Putaway, picking, warehouse internal process (such as inventory), queries (such as for stock). You can determine all standard RF transactions using transaction SE80 (ABAP Development Workbench) and package LMOB.

Figure 23: Example: Putaway by Storage Unit

The RF function leads the warehouse personnel through the warehouse activities step-by-step by displaying the information of transfer orders on the RF Terminal. Depending on the menu, there are various option for choosing the next activity to be processed (for example, transfer order). The warehouse worker can scan the barcode of the transfer order or storage unit and get the corresponding information, or the system can assign a transfer order to the worker by queue assignment. In the system-guided mode, the transfer order is assigned according to the priority of the transfer order and then the transfer order number. If you want assignment to occur according to other criteria, you can use a user exit. During the processing of a transfer order, the source information is displayed to the warehouse worker first. However, if the warehouse worker is standing next to a storage unit, he or she can override this display by scanning the storage unit number. Once the source information for one or more item(s) has been confirmed, the destination information for the chosen items is displayed.

2008

© 2008 SAP AG. All rights reserved.

69

Unit 4: Mobile Data Entry

SCM631

Data Entry Verification
Depending on the system settings, the user has to verify certain information for the confirmation of the transfer order. This could be the source bin, destination bin or the actual quantity. The identification of the scanned bin is compared to the information in the transfer order.

Figure 24: Example: Verification of the storage unit number

You can use the verification profile in Customizing to determine which information has to be confirmed during transfer order processing for the various movements in the warehouse. This verification for the source and destination bins can be defined separately. The fields you can verify are: • Storage bins The scanned data for bin verification is checked against the value of the verification field in the storage bin master record. This field can be set up with the bin name itself or a different name. You can fill this field with a special transaction. • • Storage unit number Material number This can be the material number, the old material number from the material master record, or the EAN number. • Quantity You must use dynpro exits if you wish to confirm other fields in addition to these fields. This is the only way to add and verify other input-ready fields in an existing dynpro.

70

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Mobile Data Entry - Customizing

Queue management
To organize the distribution of activities in the warehouse, you need to define queues that group similar activities. For example, you can define a queue for goods receipt. All affected activities are assigned to this queue. Transfer orders for putaways are processed in this queue. Therefore, transfer orders and employees are assigned to a queue. You can define the queues so that employees can only process transfer orders from the queue that they are assigned to or so that they can access transfer orders in other queues.

Figure 25: RF Queues

Queues can be defined for different activities, doors, and areas in the warehouse number. Queue management is also independent of mobile data entry and can be used for those work areas that contain system accesses. This guarantees a system-guided transfer order assignment.

2008

© 2008 SAP AG. All rights reserved.

71

Unit 4: Mobile Data Entry

SCM631

Figure 26: RF monitor

The RF monitor is the central tool for coordinating the activities and users that are assigned to the different queues. The RF monitor displays the assignment of the transfer orders that were created in the warehouse to the queues. This assignment is based upon the transfer type and the source and destination data in the transfer order. You can use the drag and drop function to move transfer orders and users from one queue to another manually. This allows you to respond quickly and flexibly to unplanned situations. You can also use the queue forwarding function to forward transfer orders from one queue to another. For example, the drag and drop function is used to assign queue 1 to queue 2. This means that when working in system-guided mode, employees who are assigned to queue 1 can also be assigned transfer orders from queue 2. The transfer order that an employee is assigned in system-guided mode depends primarily on the priority of the transfer order. The transfer order number plays a role in determining the next transfer order only when the priority of the transfer orders are the same. If you want a specific transfer order to be assigned next, you must use the drag and drop function in the RF monitor to move it to the front of the queue. By moving the transfer order in the queue, you change its priority to the highest priority (0). No transfer orders can be placed before a transfer order with priority 0. If you are using planned time determination during the creation of your transfer orders, you can display the user/workload relationship in the queue of the RF monitor.

72

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Mobile Data Entry - Customizing

Exercise 4: Mobile Data Entry in the Warehouse
Exercise Objectives
After completing this exercise, you will be able to: • Configure the RF solution for Warehouse Management • Set up the verification control for RF transactions. • Define menu management within the RF transactions. • Define and configure the queues and the RF Monitor.

Business Example
In your warehouse, you use handheld terminals for paper-free communication. All transfer orders in the warehouse are processed using RF. You want to separate the inbound movements and the outbound movements into different work areas. Therefore, you define different queues. Goods receipts from inbound deliveries are processed entirely with the mobile devices. You receive material for a purchase order and you process the the putaway and goods receipt posting from the RF transaction. You create the inbound delivery yourself.

Task 1:
Change the master data that is required for the example scenario. 1. For RF processing, you want to verify the storage bin where the warehouse worker stores or removes materials. Change the verification field of the storage bins in storage type 005 in warehouse number 1##. The storage bins have the coordinates 400-## through 410-##. You do not want to verify all of the storage bin names; instead, you want to create a unique verification code for each bin. Create the verification field from the second and third characters of the storage bin coordinates: Storage bin 401-## has, for example, the verification field 01. Check the result using the example of storage bin 401-##. Assign the storage bin 402-## to the material T-BW20-##. Add the storage location view for storage location 005 to the material master. In addition, assign the stock removal indicator and the stock placement indicator FIX to the materials T-BW20-## and T-BW21-##.

2. 3.

Continued on next page

2008

© 2008 SAP AG. All rights reserved.

73

Unit 4: Mobile Data Entry

SCM631

Task 2:
Set up Customizing for mobile data entry in your warehouse number. 1. For RF processing in the warehouse, you must use parameters to determine which data appears on the RF screens. When processing a transfer order with RF, you want the source bin of a movement to be available as soon as possible. Set the confirmation control in your warehouse accordingly. In the future, stock removals from goods receipt area 902 and shipments to goods issue area 916 should be confirmed separately. Determine which data you want to verify when processing a transfer order with RF. In warehouse number 1##, define two profiles - one for putaways (INB##) and one for stock removals (OUTB##). You can copy the entries from template warehouse number 001 to do this. Assign suitable goods receipts for the purchase order (movement type 101) and goods issues for the outbound delivery (movement type 601) to your new verification profile. Goods receipts are received in the goods receipt area (storage type 902) and they are put away into fixed bin storage (storage type 005). Outbound deliveries leave the warehouse from the fixed bin storage via the shipping zone for deliveries (storage type 916). Menu management defines the sequence of the screens displayed by the RF terminal as well as the positions and names of the pushbuttons. Copy the dynamic menu management entries from warehouse number 001 for your warehouse number 1##. You want to use queues to organize the processes of assigning workloads to warehouse workers. Define the queues WE001 (Goods Receipt) and WA001 (Goods Issue) for warehouse number 1##. Putaways in storage type 005 are processed by the queue WE001 and stock removals from storage type 005 are processed by the queue WA001. Create the corresponding table entries. Hint: Pick areas do not play a role in this example scenario. Therefore, fill the corresponding fields with ***. 7. Assign your user SCM631-## to the goods receipt queue and activate the queue. The screen format should be 8X40 and the standard menu should be MAIN.

2.

3.

4.

5.

6.

Continued on next page

74

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Mobile Data Entry - Customizing

Task 3:
Test your configuration using the example of a goods receipt for purchase order. 1. Open another session with the RF monitor for warehouse number 1##. Which queue are you assigned to? Leave the session of the RF monitor open and carry out the following steps in a second session. Create a purchase order with the following data. In the next step you will create an inbound delivery for this purchase order. You must therefore set a suitable confirmation control key (Inbound Delivery for the two purchase order items. Purchase order type: Vendor: Organizational data: Purchasing organization: Purchasing group: Company code: Item details: Material: Quantity: Gross price: Plant: Storage Location: Material: Quantity: Gross price: Plant: Storage Location: Item details: Confirmation control: 3. Inbound delivery T-BW20-## 100 (pieces) 2 (Euro) 1000 01## T-BW21-## 200 (pieces) 2 (Euro) 1000 01## IDES Deutschland 1000 001 1000 Standard purchase order 1000

2.

Create an inbound delivery with reference to your purchase order. Write down the document number: ________________ Continued on next page

2008

© 2008 SAP AG. All rights reserved.

75

Unit 4: Mobile Data Entry

SCM631

4.

Log on to the system as an RF user and create the transfer order for the inbound delivery that you created in step 3. Confirm this transfer order from the RF simulation. Hint: To navigate, use the function keys F1 to save, F4 to scroll forwards and F3 to scroll backwards. Choose F8 to create a transfer order.

5.

Switch to the RF Monitor session. To which queue has the transfer order that you have just created been assigned? How many pallets have to be moved? Display the transfer order and check the source and destination data. Return to the RF session, confirm the transfer order and post the goods receipt for your inbound delivery. Check the RF monitor once again.

6. 7.

76

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Mobile Data Entry - Customizing

Solution 4: Mobile Data Entry in the Warehouse
Task 1:
Change the master data that is required for the example scenario. 1. For RF processing, you want to verify the storage bin where the warehouse worker stores or removes materials. Change the verification field of the storage bins in storage type 005 in warehouse number 1##. The storage bins have the coordinates 400-## through 410-##. You do not want to verify all of the storage bin names; instead, you want to create a unique verification code for each bin. Create the verification field from the second and third characters of the storage bin coordinates: Storage bin 401-## has, for example, the verification field 01. a) b) Choose Logistics → Logistics Execution → Master Data → Warehouse → Storage Bin → Change → Verification Field Selection. Enter your warehouse number 1## and storage type 005. Select Adopt bin coordinate partially, enter 1 in the second field and 2 in the third field. Choose Execute . Choose Update. The system displays a message telling you that 11 storage bins were changed. Choose Logistics → Logistics Execution → Master Data → Warehouse → Storage Bin → Change → Single Bin. Enter warehouse number 1##, storage type 005, storage bin 401-## and choose Enter. The coordinate element 01 is displayed in the Verif.fld field.

c) 2.

Check the result using the example of storage bin 401-##. a) b)

Continued on next page

2008

© 2008 SAP AG. All rights reserved.

77

Unit 4: Mobile Data Entry

SCM631

3.

Assign the storage bin 402-## to the material T-BW20-##. Add the storage location view for storage location 005 to the material master. In addition, assign the stock removal indicator and the stock placement indicator FIX to the materials T-BW20-## and T-BW21-##. a) b) Choose Logistics → Logistics Execution → Master Data → Material → Material → Create → Immediately. Enter the material number T-BW20-##, select 'mechanical engineering' as the industry sector and 'trading goods' as the material type. Choose Enter. Select the Warehouse Management 1 and Warehouse Management 2 views and choose Enter. Enter the warehouse number 1##, storage type 005 and choose Enter. Enter FIX in the stock removal field and FIX in the stock placement field. Choose Enter to confirm your entries. Enter the storage bin 402-## and save your changes. Choose Logistics → Logistics Execution → Master Data → Material → Material → Change → Immediately. Enter material number T-BW21-## and choose Enter. Repeat steps c) to e) for material T-BW21-##. (You only have to fill the stock placement field. The storage bin 400-## has already been assigned).

c) d) e) f) g) h) i)

Task 2:
Set up Customizing for mobile data entry in your warehouse number. 1. For RF processing in the warehouse, you must use parameters to determine which data appears on the RF screens. When processing a transfer order with RF, you want the source bin of a movement to be available as soon as

Continued on next page

78

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Mobile Data Entry - Customizing

possible. Set the confirmation control in your warehouse accordingly. In the future, stock removals from goods receipt area 902 and shipments to goods issue area 916 should be confirmed separately. a) b) c) d) e) In Customizing, choose Logistics Execution → Warehouse Management → Activities→ Confirmation. Choose Warehouse number, select warehouse number 1## and set the Sep. Conf. indicator.. Save your changes and exit the table. Choose Storage Type and select the table entry for warehouse number 1## and storage type 902. Set the RC indicator (Confirmation of removal required). Select the entry for warehouse number 1##, storage type 916 and set the EQ indicator (Confirmation of Putaway Required). Save your changes.

2.

Determine which data you want to verify when processing a transfer order with RF. In warehouse number 1##, define two profiles - one for putaways (INB##) and one for stock removals (OUTB##). You can copy the entries from template warehouse number 001 to do this. a) b) c) d) Choose Logistics Execution → Mobile Data Entry → Verification Control → Define Profiles. Choose New Entries, enter warehouse number 1## und the profile name INB## . Se the Dest. bin ad Qty dest. bin indicators. Create an entry in the same way for the stock removal profile OUTB##. Set the Source bin and Qty dest. bin indicators and save your entries.

3.

Assign suitable goods receipts for the purchase order (movement type 101) and goods issues for the outbound delivery (movement type 601) to your new verification profile. Goods receipts are received in the goods receipt

Continued on next page

2008

© 2008 SAP AG. All rights reserved.

79

Unit 4: Mobile Data Entry

SCM631

area (storage type 902) and they are put away into fixed bin storage (storage type 005). Outbound deliveries leave the warehouse from the fixed bin storage via the shipping zone for deliveries (storage type 916). a) b) Choose Logistics Execution → Mobile Data Entry → Verification Control → Assign Verification Profiles to Goods Movements. Choose New Entries and enter the following data: Field Name or Data Type Warehouse number Source storage type Destination storage type Movement type Profile c) Values 1## 902 005 101 INB##

Using this template, create a second entry for the source storage type 005, destination storage type 916, movement type 601 and profile OUTB##. Save your changes.

4.

Menu management defines the sequence of the screens displayed by the RF terminal as well as the positions and names of the pushbuttons. Copy the dynamic menu management entries from warehouse number 001 for your warehouse number 1##. a) b) c) Choose Logistics Execution → Mobile Data Entry → Define Menu Management. Select all of the entries for warehouse number 001 and choose Copy As . In each of the copied entries, overwrite the warehouse number 001 with warehouse number 1##. Save your changes.

5.

You want to use queues to organize the processes of assigning workloads to warehouse workers. Define the queues WE001 (Goods Receipt) and WA001 (Goods Issue) for warehouse number 1##. a) b) c) Choose Logistics Execution → Mobile Data Entry → RF Queue Management. Choose Define Queues then New Entries. Enter warehouse number 1##, queue WE001 and the description Goods Receipt. On the next line, enter the warehouse number again, the queue WA001 and the description Goods Issue. Save your changes. Continued on next page

80

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Mobile Data Entry - Customizing

6.

Putaways in storage type 005 are processed by the queue WE001 and stock removals from storage type 005 are processed by the queue WA001. Create the corresponding table entries. Hint: Pick areas do not play a role in this example scenario. Therefore, fill the corresponding fields with ***. a) b) c) d) Choose Logistics Execution → Mobile Data Entry → RF Queue Management. Choose the entry Assign Activities and Areas to Queues and then New Entries. Enter warehouse number 1## and choose the entry Preparation screen for placement into stock for the Screen field. Enter the following data: Field Name or Data Type Transportation Type Source storage type Source picking area Destination storage type Destination picking area Door Queue Values E 902 *** 005 *** *** GR001

Choose Enter to confirm the warning message telling you that the source storage type and area are not relevant and save your changes. e) Repeat the last step for picking control by entering the warehouse number 1## and choosing the entry Preparation screen for stock removal for the screen field. Enter the following data: Field Name or Data Type Transportation Type Source storage type Source picking area Destination storage type Values A 005 *** 916

Continued on next page

2008

© 2008 SAP AG. All rights reserved.

81

Unit 4: Mobile Data Entry

SCM631

Destination picking area Door Queue

*** *** GI001

Choose Enter to confirm the warning message telling you that the source storage type and area are not relevant and save your changes. 7. Assign your user SCM631-## to the goods receipt queue and activate the queue. The screen format should be 8X40 and the standard menu should be MAIN. a) b) c) Choose Logistics Execution → Mobile Data Entry → RF Queue Management. Choose the entry Assign Processor to Queues and then New Entries. Enter warehouse number 1##, user SCM631-## and the queue GR001. Set the Status indicator, select the screen format 8X40 and the main menu MAIN. Save your changes.

Task 3:
Test your configuration using the example of a goods receipt for purchase order. 1. Open another session with the RF monitor for warehouse number 1##. Which queue are you assigned to? Leave the session of the RF monitor open and carry out the following steps in a second session. a) b) 2. Choose Logistics → Logistics Execution → Internal Whse Processes → Mobile Data Entry → Monitor Mobile Data Entry. You are currently assigned to queue GR001.

Create a purchase order with the following data. In the next step you will create an inbound delivery for this purchase order. You must therefore set a suitable confirmation control key (Inbound Delivery for the two purchase order items. Purchase order type: Vendor: Organizational data: Purchasing organization: Purchasing group: IDES Deutschland 1000 001 Continued on next page Standard purchase order 1000

82

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Mobile Data Entry - Customizing

Company code: Item details: Material: Quantity: Gross price: Plant: Storage Location: Material: Quantity: Gross price: Plant: Storage Location: Item details: Confirmation control: a) b) c) d)

1000 T-BW20-## 100 (pieces) 2 (Euro) 1000 01## T-BW21-## 200 (pieces) 2 (Euro) 1000 01## Inbound delivery

Choose Logistics → Materials Management → Purchasing → Purchase Order → Create → Vendor/Supplying Plant Known. Enter 1000 in the Vendor field and choose Enter. The Org. Data tab page is displayed. On this tab page, enter the purchasing organization 1000, purchasing group 001 and company code 1000. Open the item overview and enter the material T-BW20-##, purchase order quantity 100, gross price 2 (Euro), plant 1000, and storage location 01##. Make a second entry in the item overview for the material T-BW21-##, purchase order quantity 200, gross price 2 (Euro), plant 1000, and storage location 01##. Go to the item level for the two purchase order items and enter the confirmation control key Inbound Delivery on the Confirmations tab page. Save to create the purchase order.

e)

f)

Continued on next page

2008

© 2008 SAP AG. All rights reserved.

83

Unit 4: Mobile Data Entry

SCM631

3.

Create an inbound delivery with reference to your purchase order. Write down the document number: ________________ a) Choose Logistics → Logistics Execution → Inbound Process → Goods Receipt for Inbound Delivery → Inbound Delivery → Create → Single Documents. The system usually proposes the purchase order and the vendor that was last processed. Confirm the system proposal with Enter. On the Stock placement tab page, check that your warehouse number 1## is proposed for the putaway of the two delivery items then save to create the inbound delivery.

b) c)

4.

Log on to the system as an RF user and create the transfer order for the inbound delivery that you created in step 3. Confirm this transfer order from the RF simulation. Hint: To navigate, use the function keys F1 to save, F4 to scroll forwards and F3 to scroll backwards. Choose F8 to create a transfer order. a) b) c) d) e) Choose Logistics → Logistics Execution → Internal Whse Processes → Mobile Data Entry → Mobile Data Entry. Choose F1 to log on as an RF user. Choose Inbound Process then Goods Receipt. On the next screen, choose GR by Delivery, enter the document number of the inbound delivery from step 3 in the Delivery field then choose F4. Choose F8 to create the transfer order for the inbound delivery. Choose F4 to confirm the prompt that follows. The system then displays a message with the number of the transfer order. Choose OK to return to the inbound delivery screen.

f) 5.

Switch to the RF Monitor session. To which queue has the transfer order that you have just created been assigned? How many pallets have to be moved? Display the transfer order and check the source and destination data. a) b) The transfer order is assigned to the queue GR001. To display your transfer order, double-click its number which is displayed in the list of transfer orders on the right side of the screen. There are three pallets to be put away into the fixed bin storage type.

Continued on next page

84

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Mobile Data Entry - Customizing

6.

Return to the RF session, confirm the transfer order and post the goods receipt for your inbound delivery. a) In the RF screen of step 4, choose the function key F6. The system displays the source data of the first transfer order item and the material quantity that is to be put away. Choose F1 then F4. The destination data is displayed. You must enter the partial coordinate of the verification field in the storage bin master record. In the field on the right next to the bin coordinates, enter 02 and choose F1. Proceed in the same way with the next two transfer order items. Enter 00 to verify the second storage bin. Once you have confirmed the last of the three items, the system returns to the overview screen of the inbound delivery. Choose F1 to post the goods receipt. Choose F4 to confirm the prompt that follows. Choose OK to confirm the message telling you that the goods receipt for the inbound delivery was posted and choose F3 to go back to the initial screen of the main menu. Choose F8 to log off. Return to the RF monitor session and choose Refresh The confirmed transfer order is no longer displayed.

b)

c) d) e)

f)

g) 7. a) b)

Check the RF monitor once again.

2008

© 2008 SAP AG. All rights reserved.

85

Unit 4: Mobile Data Entry

SCM631

Lesson Summary
You should now be able to: • Set up menu management • Set up the verification control • Set up queue management

86

© 2008 SAP AG. All rights reserved.

2008

SCM631

Unit Summary

Unit Summary
You should now be able to: • Describe how the mobile devices are connected technically • Set up menu management • Set up the verification control • Set up queue management

2008

© 2008 SAP AG. All rights reserved.

87

Unit Summary

SCM631

88

© 2008 SAP AG. All rights reserved.

2008

Unit 5
Connection of Warehouse Control Units
Unit Overview
This unit describes scenarios when you might connect the warehouse control unit to Warehouse Management in the SAP system.

Unit Objectives
After completing this unit, you will be able to: • • Describe how the warehouse control unit is connected technically to Warehouse Management in the SAP system Describe various scenarios that require the use of a warehouse control unit

Unit Contents
Lesson: The Technical Connection to a Warehouse Control Unit ......... 90 Lesson: Using a Warehouse Control Unit - Scenarios ...................... 94

2008

© 2008 SAP AG. All rights reserved.

89

Unit 5: Connection of Warehouse Control Units

SCM631

Lesson: The Technical Connection to a Warehouse Control Unit
Lesson Overview
This lesson provides an overview of the technical connection to the warehouse control unit (WCU) and the data that is exchanged between Warehouse Management in the SAP system and the WCU.

Lesson Objectives
After completing this lesson, you will be able to: • Describe how the warehouse control unit is connected technically to Warehouse Management in the SAP system

Business Example
You will set up a fully-automated high rack storage area in the warehouse complex. It must be integrated in the warehouse number because other parts of the warehouse are managed by the SAP system. You therefore require an overview of the technical connections.

Connections to External Systems

Figure 27: Connection to Warehouse Control Units (WM-WCU)

When the warehouse complex is complicated and largely automated, a warehouse control unit is often required to check the stock at a physical level. The SAP Warehouse Management system is designed for use at management level (it knows which stock is in which storage bin). However, it is not designed to know when

90

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: The Technical Connection to a Warehouse Control Unit

the transfer orders are being processed physically. In automated systems, this task is the responsibility of the warehouse control unit. A warehouse control unit is often used for fully-automated high rack storage systems, picking systems and forklift control systems. As of SAP R/3 Enterprise, there is a fully integrated solution which takse over the tasks of the warehouse control unit: Task and Resource Management (TRM). TRM is responsible for checking the execution of the warehouse activities. It aims to assign the the most efficient tasks to the correct resources. In addition to checking the physical movements, TRM also maps activities in the warehouse that were not previously possible such as packing with a specific task and price marking. TRM uses geocoordinates that are based on a coordinate system. It therefore recognizes the geographical location of each work center and resource in the warehouse. With additional programming effort, TRM can successfully manage fully-automated systems (automatic storage retrieval, high rack storage areas) and can therefore replace the warehouse control unit.

Figure 28: WM-WCU Functions

When warehouse control units are used, standard systems exchange various pieces of information. The figure below demonstrates these different processes. From a technical point of view, the ALE interface is required to exchange the information. If you intend to exchange additional information with the subsystem, the ALE interface must be adjusted.

2008

© 2008 SAP AG. All rights reserved.

91

Unit 5: Connection of Warehouse Control Units

SCM631

Figure 29: Technical Overview of MM-MOB / WM-WCU

The ALE interface functions as follows: The SAP system sends intermediate documents (IDocs) to the subsystem and expects to find the information in the receiving area in IDoc format. A program in C or Visual Basic must be created in the external system. The program must be able to access the functions of the RFC library. It is responsible for receiving the IDocs, saving the IDocs and preparing the data that is to be transferred to the SAP system.

92

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: The Technical Connection to a Warehouse Control Unit

Lesson Summary
You should now be able to: • Describe how the warehouse control unit is connected technically to Warehouse Management in the SAP system

2008

© 2008 SAP AG. All rights reserved.

93

Unit 5: Connection of Warehouse Control Units

SCM631

Lesson: Using a Warehouse Control Unit - Scenarios
Lesson Overview
This lesson describes various scenarios that require the use of a warehouse control unit in the warehouse complex.

Lesson Objectives
After completing this lesson, you will be able to: • Describe various scenarios that require the use of a warehouse control unit

Business Example
You will introduce some automated subsystems into your warehouse complex. These must be integrated in the warehouse number because other parts of the warehouse are managed by the SAP system.

Connections to External Systems: Scenarios

Figure 30: Scenario 1: Manual Warehouse

In a manual warehouse, the SAP system controls all warehouse management activities. A paper-based system and simple, wired barcode scanners are used to confirm the movements. This is a simple and efficient way to minimize data entry errors. The SAP Warehouse Management System was originally designed for this scenario and does not usually require many individual adjustments if it is used in this way.

94

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Using a Warehouse Control Unit - Scenarios

Figure 31: Scenario 2: Semi-Automated Warehouse

In a semi-automated warehouse, the SAP system controls the warehouse management activities. An external system is responsible for executing the movements. A typical semi-automated system is a fork lift system with fixed devices or a conveyor belt. The TRM function can be used for this scenario instead of the warehouse control unit.

Figure 32: Scenario 3: Fully Automated Warehouse

2008

© 2008 SAP AG. All rights reserved.

95

Unit 5: Connection of Warehouse Control Units

SCM631

In this scenario, the external system is responsible for warehouse control and, if necessary, a specific part of warehouse management. In a fully automated warehouse, you must consider both the warehouse as a whole and the specifications of the automated warehouse systems to determine the best way of distributing the warehouse functions between the SAP system and the external system. There is no standard solution for distributing the functions. This analysis must be carried out separately for each individual customer and in accordance with the project in question. This scenario only usually comes into play when other areas of the warehouse complex are managed solely by the SAP system. The storage bins (and therefore the exact bin inventory in the high-shelf storage area) are managed by both systems in this scenario.

Figure 33: Scenario 4: “Black Box”

In this example, the SAP system manages the high rack storage area as a “black box” and there are just dummy storage bins. The external system is responsible for all warehouse functions, including warehouse management and storage control. The quantity and reference data that is transferred during transfer order creation from the SAP system to the warehouse control unit is relevant for the external system. In this scenario, the storage bins and bin inventories are managed solely by an external system. In the SAP system there is just one storage bin (addition to existing stock and mixed stock are allowed without any restrictions) or a fixed bin for each material that is put away.

96

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Using a Warehouse Control Unit - Scenarios

Lesson Summary
You should now be able to: • Describe various scenarios that require the use of a warehouse control unit

2008

© 2008 SAP AG. All rights reserved.

97

Unit Summary

SCM631

Unit Summary
You should now be able to: • Describe how the warehouse control unit is connected technically to Warehouse Management in the SAP system • Describe various scenarios that require the use of a warehouse control unit

98

© 2008 SAP AG. All rights reserved.

2008

Unit 6
Decentralized Warehouse Management and Technical Themes
Unit Overview
This unit describes how to set up the decentralized Warehouse Management system. It also lists the archiving reports and user exits that are available in Warehouse Management.

Unit Objectives
After completing this unit, you will be able to: • • • Describe goods movements in a decentralized Warehouse Management system Determine the programs that are required to archive Warehouse Management data Determine the user exits that can be used to aid custom enhancements

Unit Contents
Lesson: Decentralized Warehouse Management ..........................100 Lesson: Technical Topics ......................................................108

2008

© 2008 SAP AG. All rights reserved.

99

Unit 6: Decentralized Warehouse Management and Technical Themes

SCM631

Lesson: Decentralized Warehouse Management
Lesson Overview
Decentralized Warehouse Management is available as of SAP R/3 4.5 and allows Warehouse Management to be separate from the ERP system. This lesson explains the basic processes (putaway, removal and stock transfer processes). It also demonstrates the required Customizing settings.

Lesson Objectives
After completing this lesson, you will be able to: • Describe goods movements in a decentralized Warehouse Management system

Business Example
Your warehouse processes should be independent of the central processes in the ERP system. You therefore examine the use of the decentralized Warehouse Management system.

The Basics of Decentralized Warehouse Management

Figure 34: Distributed Functions

The ERP System contains all subprocesses for preparing and postprocessing the warehouse activities. These include the creation of sales and purchasing documents with various checks and subsequent billing. Decentralized Warehouse

100

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Decentralized Warehouse Management

Management contains the functions for the warehouse processes - these include the planning aspects, goods receipt, storing, goods issue and monitoring of warehouse activities. The separation of Warehouse Management in a second (logical or physical) system is made possible by an ALE scenario in the SAP system. This preconfigured scenario works with Business Application Programming Interfaces (BAPIs) that are called asynchronously.

Figure 35: Overview of the Processes

The inbound or outbound delivery is the basis for the activities in the warehouse for both inbound and outbound processes. The delivery is created for a sales order or purchase order. When you create a delivery, the system checks to see whether it is relevant for distribution (that is, intended for further processing in a decentralized warehouse number). If it is, a BAPI is called when the delivery is saved. This BAPI triggers the creation of an IDoc and sends the delivery to the decentralized Warehouse Management system. The delivery is then replicated in the decentralized Warehouse Management system. This replication serves as the basis for the following processes in the warehouse such as the creation and confirmation of the transfer order and the printing of shipping documents. When the goods issue (or goods receipt) is posted, the interim storage bin is cleared and a BAPI is called. This BAPI confirms the data to the ERP system that was created or changed in the decentralized Warehouse Management system (for example, quantities, weights, packaging and batches). After successful inbound processing of the confirmation in the ERP system, the goods movement is posted automatically in inventory management.

2008

© 2008 SAP AG. All rights reserved.

101

Unit 6: Decentralized Warehouse Management and Technical Themes

SCM631

As of SAP ERP 6.0, partial goods receipts can also be posted in the decentralized system. This means that stored partial quantities are created in the inventory management environment of the ERP system on time.

System Landscape

Figure 36: Connection to Several ERP Systems

As of SAP R/3 Enterprise, several ERP systems can be connected to a decentralized Warehouse Management system. The following prerequisites must be met in order to connect more than one ERP system to a decentralized Warehouse Management system: • The master data in the decentralized Warehouse Management system must contain unique numbers: The customer master, supplier master, vendor master, and material master records from the various ERP systems must have unique numbers so that they can be read uniquely in the decentralized Warehouse Management system. The organizational units in the decentralized Warehouse Management system must contain unique numbers: The various plant and storage location numbers must be unique in the decentralized Warehouse Management system. The delivery numbers in the decentralized Warehouse Management system must be unique: In the decentralized Warehouse Management system, the deliveries from the various ERP systems must be unique. (If there are duplicate delivery numbers from different ERP systems, you can use customer exit V50S0001 and function module EXIT_SAPLV50S_001 to reassign the numbers. You can therefore ensure that the delivery numbers in the decentralized Warehouse Management system are unique).

102

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Decentralized Warehouse Management

Document Changes

Figure 37: Subsequent Changes to the Delivery

As of SAP R/3 Enterprise, you can change the way that deliveries are distributed from the ERP system to the decentralized Warehouse Management system. To do this, change management must be set up in the decentralized Warehouse Management system. In change management, certain information can be changed at header and item level. At header level, for example, you can changed the specifications for weight, volume, delivery date, door and external identification number. At item level you can likewise change the weight, volume and delivery quantity. You can also delete items and change partners or partner addresses.

2008

© 2008 SAP AG. All rights reserved.

103

Unit 6: Decentralized Warehouse Management and Technical Themes

SCM631

Goods Movement Postings

Figure 38: Inventory Postings

In contrast to the integrated scenario, inventory postings that were entered in the ERP System are not posted immediately. Instead, the system generates an inbound delivery or outbound delivery that is forwarded to the decentralized Warehouse Management system when a transfer posting is entered. A posting is made in the inventory management area of the ERP system when the decentralized Warehouse Management system confirms the delivery. To make this scenario possible, you must adjust warehouse number Customizing and the settings of the reference movement type that is needed to create the delivery. Posting changes between two plants or storage locations can only be processed using a two-step procedure.

Basic Settings
The delivery is the central means of communication for all inventory management postings that are involved with the decentralized Warehouse Management system. It is assigned a special task that is documented by a new status. The distribution status in the delivery tells you (from the perspective of the ERP system) whether the delivery is relevant for the decentralized Warehouse Management system, whether it has already been distributed or whether the goods movement has already been posted. If you do not use change management, you can change deliveries in the ERP system only if they have not yet been forwarded to the decentralized Warehouse Management system. If the deliveries refer to preceding documents (sales orders, purchase orders), the numbers of these documents are transferred to the decentralized Warehouse Management system using the item reference data. Nevertheless, the preceding documents exist only in the ERP system.

104

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Decentralized Warehouse Management

Figure 39: Distribution Model

The communication between the two systems is asynchronous. Direct communication takes place only for scenarios such as the generation of the distribution model and stock comparison. The decentralized Warehouse Management Customizing activities are used to create a suitable distribution model view. This contains all objects that are sent between the systems. The distribution model is generated for a warehouse number that already exists in the system and it forms the basis for the information exchange with the decentralized Warehouse Management system. The objects to be distributed are made up from master data and application data.

2008

© 2008 SAP AG. All rights reserved.

105

Unit 6: Decentralized Warehouse Management and Technical Themes

SCM631

Figure 40: Distribution Model View: Creating and Distributing

It is necessary to distribute master data and movement data from the ERP system to the decentralized Warehouse Management system before the decentralized Warehouse Management system can be used. This includes the material master, customer master and vendor master records and possibly also batch and classification information. Logical systems must be defined for both the ERP system and the decentralized Warehouse Management system. You can then generate the model view for each warehouse number. You can set filters when doing this so that only certain views of the material master or customer master are distributed. You may wish to do this if, for example, the material master is maintained for different organizational units but the data is required for just one organizational unit in the decentralized Warehouse Management system. After this has been done, the model view can be introduced to the decentralized Warehouse Management system. The distribution model view itself is sent to the decentralized Warehouse Management system. Afterwards, the partner profiles then need to be generated in the decentralized Warehouse Management system. Hint: If just one system is an SAP system (either the ERP system or decentralized Warehouse Management system), the distribution model should not be generated or distributed. If both systems are SAP systems, you should generate the distribution model view in the ERP system and then distribute it.

106

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Decentralized Warehouse Management

Lesson Summary
You should now be able to: • Describe goods movements in a decentralized Warehouse Management system

2008

© 2008 SAP AG. All rights reserved.

107

Unit 6: Decentralized Warehouse Management and Technical Themes

SCM631

Lesson: Technical Topics
Lesson Overview
This lesson describes the current reports for archiving and the existing user exits in Warehouse Management.

Lesson Objectives
After completing this lesson, you will be able to: • • Determine the programs that are required to archive Warehouse Management data Determine the user exits that can be used to aid custom enhancements

Business Example
Many documents are created in your warehouse and they need to be archived regularly.

Archiving in Warehouse Management
The following programs are responsible for archiving the individual documents in Warehouse Management: Transfer Requirements: RLREOB10: Deletes archived transfer requirements RLRB0001: Report for reading archived transfer requirements Posting change notices: RLREOU00: Archives posting change notices RLREOU10: Deletes archived posting change notices RLRU0001: Report for reading archived posting change notices Transfer orders: RLREOT00: Archives transfer orders RLREOT10: Deletes archived transfer orders RLRT0001: Report for reading archived transfer orders System inventory records: RLREOI00: Archives system inventory records RLREOI10: Deletes system inventory records RLRI0001: Report for reading archived system inventory records

108

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Technical Topics

Inventory count records (history): RLREOH00: Archives inventory count records (history) RLREOH10: Deletes inventory count records (history) RLRH0001: Report for reading archived inventory count records (history) You can schedule all reports as jobs in archive administration (transaction SARA) and you can read documents again that have already been archived.

Function Modules and User Exits in Warehouse Management

Figure 41: Function Modules

You can use function modules to replace a series of existing batch-input processes that is used in the Warehouse Management system. You can use these modules to combine different transactions on one screen or to enhance the range of functions in your system to meet your particular organizational requirements. You can find more information about function modules in the Warehouse Management documentation.

2008

© 2008 SAP AG. All rights reserved.

109

Unit 6: Decentralized Warehouse Management and Technical Themes

SCM631

Figure 42: User Exits

SAP enhancements (user exits) allow you to use your own logic to modify the search for storage bins. They also allow you to update your own data when you generate transfer order confirmations. If you use this function to create your own projects, you can display additional information about each enhancement. The documentation contains a complete list of the user exits available in Warehouse Management. For a detailed description of these processes, see the documentation for the individual user exits in transaction SMOD or CMOD.

110

© 2008 SAP AG. All rights reserved.

2008

SCM631

Lesson: Technical Topics

Lesson Summary
You should now be able to: • Determine the programs that are required to archive Warehouse Management data • Determine the user exits that can be used to aid custom enhancements

2008

© 2008 SAP AG. All rights reserved.

111

Unit Summary

SCM631

Unit Summary
You should now be able to: • Describe goods movements in a decentralized Warehouse Management system • Determine the programs that are required to archive Warehouse Management data • Determine the user exits that can be used to aid custom enhancements

112

© 2008 SAP AG. All rights reserved.

2008

SCM631

Course Summary

Course Summary
You should now be able to: • • Perform functions such as Customizing of Storage Unit Management, radio frequency, and hazardous material management. Describe the Customizing options and settings in the Warehouse Management system for Handling Unit Management, decentralized Warehouse Management, and performance data.

2008

© 2008 SAP AG. All rights reserved.

113

Course Summary

SCM631

114

© 2008 SAP AG. All rights reserved.

2008

Index
A
Actual data, 55 ALE interface, 91–92 Archiving, 108 Automatic system, 90 Identification point storage type, 5 Implicit transfer order split, 56 Inspection lot, 33 Inventory list for fire department, 41

B
Black box, 96

C
Change management, 103 Contour control, 5 Correct storage check, 43

M
Mobile data-entry device (mobile device), 64

N
Number assignment (SU management), 2

D
Distribution model, 105–106 Distribution status, 104 Dynamic menu, 68

P
Pick point storage type, 5 Picking system, 90 Planned time, 55

E
Entry of performed activities, 57

Q
Queue, 71 Queue management, 71

F
Fire department inventory list, 43 Fire-containment section, 41 Forklift control system, 90, 95 Function modules, 109

R
Recovery, 65 Replication of the delivery, 101 RF controller, 66 RF menu, 68 RF monitor, 72 RF solution, 64 Dynpro exit, 65

H
Handling unit, 31 Handling unit management, 31 Hazardous material handling, 41 Hazardous material master record, 41 Hazardous substance list, 43

S
SAP enhancements, 110 SAPConsole, 65–66 Shipping unit, 31 Sort profile, 59 Split criteria, 59–60 Split profile, 59–60

I
Identification number, 31

2008

© 2008 SAP AG. All rights reserved.

115

Index

SCM631

SSCC number, 32 Storage class, 41 Storage unit, 2 Storage Unit Management Bulk storage, 19 SU management, 3 Storage unit number, 2

Total quant count information, 20

U
User exit, 110

V
Verification field, 70 Verification profile, 70

T
Task and Resource Management (TRM), 90 Telnet server, 65

W
Warehouse control unit, 90 Water pollution class, 41

116

© 2008 SAP AG. All rights reserved.

2008

Feedback
SAP AG has made every effort in the preparation of this course to ensure the accuracy and completeness of the materials. If you have any corrections or suggestions for improvement, please record them in the appropriate place in the course evaluation.

2008

© 2008 SAP AG. All rights reserved.

117

Sign up to vote on this title
UsefulNot useful