SCM631
Additional Topics in Warehouse Management
SAP SA P AG AG 20 2003 2003 SAP AG©
System SAP R/3 Enterprise
2003/Q3
Material number: 5006 2792
Copyright
Copyright 2003 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. All rights reserved.
SAP AG 2003
Trademarks:
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation. IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries. ORACLE® is a registered trademark of ORACLE Corporation. UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group. Citrix®, 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. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.
Copyright
Copyright 2003 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. All rights reserved.
SAP AG 2003
Trademarks:
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation. IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries. ORACLE® is a registered trademark of ORACLE Corporation. UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group. Citrix®, 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. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.
Course Prerequisites
Required: SCM630 Warehouse Management
SAP AG 2003
Target Group
Audience:
Project team members
Duration: 2 days
SAP AG 2003
Note:
The training materials are not teach-yourself programs. They complement the course instructor's explanations. Your material includes space for writing down this additional information.
Introduction
Course Goals
Course Objectives
Course Content
Course Overview Diagram
SAP AG 1999
© SAP AG
SCM631
1-1
Course Goals
This course will enable you to:
Gain an understanding of and hands-on experience of additional topics within the SAP Warehouse Management System and the customizing options that are available to support company requirements.
SAP AG 2002
© SAP AG
SCM631
1-2
Objectives
On completion of this course, you should be able to:
Perform WM functions such as customizing Storage Unit Management, Radio Frequency, and Hazardous Material Management.
Discuss customizing options and settings within the Warehouse Management system for Handling Unit Management, decentralized Warehouse Management, and Performance Data.
SAP AG 2003
© SAP AG
SCM631
1-3
Course Contents
Preface Unit 1
Course Overview
Unit 2
Storage Unit Management
Unit 3
Additional Functions in TO Processing
Unit 4
Unit 5
Decentralized Warehouse Management
Unit 6
Technical Topics
Unit 7
Summary
Radio Frequency / LSR
SAP AG 2003
© SAP AG
SCM631
1-4
Overview Diagram
Course Overview
Storage Unit Management Hazardous Materials Management Additional Functions in TO Processing Radio Frequency / Frequency / LSR Decentralized Warehouse Management Technical Topics Summary
SAP AG 2003
© SAP AG
SCM631
1-5
© SAP AG
SCM631
1-6
Storage Unit Management
Storage Unit Management
Managing Bulk Materials
Handling Unit Management
SAP AG 2002
© SAP AG
SCM631
2-1
Storage Unit Management: Overview Diagram
Course Overview Storage Unit Management Hazardous Materials Management Additional Functions in TO Processing Radio Frequency / Frequency / LSR Decentralized Warehouse Management Technical Topics Summary
SAP AG 2003
© SAP AG
SCM631
2-2
Storage Unit Management: Objectives
At the conclusion of this topic, you will be able to:
Define storage units and explain how to include them in the warehouse structure
Create a storage type that uses SUM with placement strategy ‘P’
Process material movements in the warehouse using storage units
SAP AG 2002
© SAP AG
SCM631
2-3
Storage Unit Management: Business Scenario
In your warehouse, you move pallets that carry different materials. To reduce the complexity of these movements and in order to identify pallets in the Warehouse Management System, you assign a number to the storage unit with storage unit management.
SAP AG 2002
© SAP AG
SCM631
2-4
Storage Bin with Storage Unit Management
4769 IIII
4712 IIII
01-04-09 01-04-09
SAP AG 2002
A storage unit is a logical grouping of one or more amounts of material, such as pallet or container, which can be managed in a warehouse as a unit that belongs together.
This picture indicates a typical storage bin with storage unit management:
There are 3 quants in the bin.
There are 2 storage units in the bin.
Storage units can be homogeneous (containing one material) or mixed (containing two or more items).
All storage units are assigned an identifying number, which is maintained in the system as the storage unit number. You can see at any given time where each storage unit is located within the warehouse complex.
© SAP AG
SCM631
2-5
WM System without Storage Unit Management
Storage bin
Quant
Quant
Quant
SAP AG 2002
Warehouse Management (WM) without Storage Unit Management (SUM)
In the WM system without Storage Unit Management, material quantities (referred to in the WM system as quants) are managed at the level of the storage bin.
© SAP AG
SCM631
2-6
Management at the Storage Unit Level
Storage bin
Storage unit
Quant
Storage unit
Quant
Quant
SAP AG 2002
If you have implemented Storage Unit Management, the quantities (quants) are managed at the level of the storage unit. In a single storage bin, you can store one or more storage units, which, in turn, can contain one or more quants.
© SAP AG
SCM631
2-7
WM-System Hierarchy with SU Management
Warehouse (complex) number
Storage type
Storage bin
Storage bin
Quant
Quant
Storage type
Storage unit
Quant
Storage unit
Quant
SAP AG 2002
When SU management is not active in a storage type, stock is managed as separate quants at the storage bin level. With SU management, stock is managed at the pallet or storage unit level. One or more storage units can be located within a single storage bin, and each storage unit can consist of one or more quants.
In customizing, Storage Unit Management must first be allowed at the warehouse level. Then, you can choose for each storage type whether to allow SUM.
If you define a storage type for Storage Unit Management, this means that all the bins in this storage type are managed for storage units.
You may define SU management for physical storage types only. Interim storage types cannot be managed for storage units.
© SAP AG
SCM631
2-8
SU Management in a Warehouse Complex
GR area ID point
Goods receipt
High rack storage (with SU Mgmt
Partial pallets (with SU Management)
Bulk storage (with SU Mgmt)
GI area
Pick point
Goods issue
SAP AG 2002
In an SU-managed storage type you can execute stock placements via an ID point and stock removals via a pick point.
In Warehouse Management, the ID point is a physical location in the warehouse where incoming goods are identified for further processing.
The pick point is the actual, physical location in the warehouse where items are picked for a partial stock removal from a storage unit. As an example, partial storage units might be returned to the same storage type but a different bin after picking. Such partial units might also be transferred to another storage type that is specifically designated for partial storage units.
© SAP AG
SCM631
2-9
Introducing SU Mgmt in a Warehouse Complex
GR area
Shelf storage SU 2825 Mat. Mat. 11 100 100 pcs pcs
Mat. Mat. 11 50 50 pcs pcs
Transfer order Mat. 1
Mat. Mat. 22 20 20 pcs pcs
SU 2826 Transfer order
Mat. Mat. 33 10 10 pcs pcs
Mat. 1 Mat. 2 Mat. 3
SAP AG 2002
Storage units are created in the system whenever materials are placed into storage in an SU-managed storage type. The stock placement is executed using the standard procedure for transfer order creation.
If a homogeneous storage unit is placed into storage, this stock placement is covered by a single transfer order item.
If a mixed storage unit is placed into storage, a single transfer order item is created for each individual material item in the storage unit.
© SAP AG
SCM631
2-10
ID Point
Goods Receipt area
Shelf storage
11
22
SAP AG 2002
An ID point is a physical location in the warehouse where materials are identified for further processing.
Purposes: 1. Verification of System Information to Actual Contents: Since storage units are identified by the storage unit number when placed into storage, the contents of each storage unit can be displayed. This makes it possible to do a rough comparison of the physical contents with the system information for a storage unit. 2. Contour Control: An automatic contour control can be carried out at the ID point to determine whether the storage unit is properly loaded. 3. Changing the Mode of Transport: Frequently, the mode of transport is changed at the ID point. Materials may be moved from a forklift to a conveyor system, for example. 4. To Determine the Final Destination: The destination bin in the final storage type is determined at the ID point. The destination bin is not assigned until the material arrives at the ID point. This ensures that the location of the bin is determined based on the most current information about available space in the storage type.
© SAP AG
SCM631
2-11
Removing Storage Units via the Pick Point
Shelf storage Goods issue area Pick point point Pick
Rest
SAP AG 2002
Pick point: If stock is removed from a storage type where complete stock removal is defined, the storage unit with its entire quantity is first removed and transferred to a pick point within the warehouse. At this pick point, the required quantity is removed as required.
The pick point might be a specific point along a conveyor where storage units have been transferred for order picking. The pick point might also be a marked floor area where entire pallets can be brought for picking materials.
© SAP AG
SCM631
2-12
Stock Placement with Pre-planning
Warehouse number 003 Goods Goods receipt receipt Production Production
High High rack rack storage storage (SU Mgmt) (SU Mgmt) 1
ID point
2
2 Bulk Bulk storage storage (SU (SU Mgmt) Mgmt)
1
Pre-Planned TO
2
TO in physical warehouse
SAP AG 2002
Stock placement with pre-planning:
If transfer orders are pre-planned, the storage units are first transferred from the goods receipt (GR) area to an ID point.
As soon as the storage units physically arrive at the ID point, the transfer order items are confirmed, and a second transfer order is created to transfer the storage units to their final storage bin.
To pre-plan, create the transfer order from the goods receipt area to the ID point in advance of the arrival of goods. The second transfer order moves material from the ID point to the final destination.
The program RLVSPLRE can be run manually or in batch to delete the unused storage units after a specified number of days.
© SAP AG
SCM631
2-13
Storage Unit Management: Topic Summary
You are now able to:
Define Storage Units and explain how to use them in the WM System
Create a storage type that uses SUM with placement strategy ‘P’
Process material movements in the warehouse using storage units
SAP AG 2002
© SAP AG
SCM631
2-14
Managing Bulk Materials: Objectives
At the conclusion of this topic, you will be able to:
Define a bulk storage area in the warehouse
Process storage units into and out of bulk storage
SAP AG 1999
© SAP AG
SCM631
2-15
Managing Bulk Materials: Business Scenario
In one area of your warehouse, you manage mixed materials on pallets. These pallets can be stacked differently, depending on whether you are stacking large or small pallets. You have a business need to view how many of each material are stored on a given pallet. You want to manage each pallet of material as a storage unit.
SAP AG 2002
© SAP AG
SCM631
2-16
Bulk Storage with SU Management
Bulk storage SU 721 SU 864
SU 368 SU 369 SU 321
SU 921
Bin:
B3-01
B3-02
B3-03
SUT:
I1
E1
E1
Mat.:
A
A
B
B3-04
SU 462
SAP AG 2002
You may want to set up bulk storage with SU management, but you can also use bulk storage without SU management activated.
You define the storage bins using blocks and rows. A row is managed as a storage bin.
Bulk storage is often used to manage different types of storage units with different dimensions. For example, you might have standard pallets and industrial pallets. You can define the number of stacks and the stack height that can be accommodated for each pallet type. You can manage different storage unit types in bulk storage.
The bulk storage indicator on the material master can be used to specify how a material is to be stored in bulk storage.
© SAP AG
SCM631
2-17
SUM Bulk Storage with Partials and Mixed Storage
SU 721 SU 864
SU 368 SU 369 SU 321
SU 921
SU 992
SAP AG 2002
With SU management, it is possible to manage partial pallets and mixed storage in bulk storage areas.
One of the primary characteristics of tracking bulk storage under SU management is that the system does not keep a record of the exact location of a particular storage unit in a bin. Because of this, the system does not know which storage units are located in the front of a bin, making them accessible for picking. Since the system does not have a record of the actual structure of the storage units in a block, it cannot recommend specific storage units for order picking. During Transfer Order confirmation, the SU number must be specified.
© SAP AG
SCM631
2-18
Stock Placement in Bulk Storage
SU 721 SU 864
SU 368 SU 369 SU 321
SU 921
SU 992
SAP AG 2002
A storage bin can be blocked for further placement after the first stock removal. This block will automatically be removed when the bin is empty.
You can have storage bins blocked for putaway by making a manual entry after a certain time (set in Customizing) has passed since the first stock placement. This block must be manually removed.
You can set a blocking reason that is stored at the bin when you set the block with a time limit. As soon as the last stock removal takes place, this block is removed, as long as the blocking reason in the storage bin matches the blocking reason in Customizing.
© SAP AG
SCM631
2-19
Managing Bulk Materials: Topic Summary
You are now able to:
Define a bulk storage area in the warehouse
Process storage units into and out of bulk storage
SAP AG 1999
© SAP AG
SCM631
2-20
Handling Unit Management
At the conclusion of this unit, you will be able to:
Explain the concept of a Handling Unit
Describe how Handling Units and Storage Units fit together
Describe the inbound and the outbound process with Handling Units
SAP AG 2002
© SAP AG
SCM631
2-21
Definition: Handling Unit
A Handling Unit is a physical collection of goods consisting of
Packaging materials (e.g. pallet, carton, shrinkwrap, container) and
Packed goods
A Handling Unit has an unique identification number through which the related information can be read
123456
SAP AG 2002
Handling units (HUs) widen the pallet handling in warehouse and shipping logistics to all logistics components.
Normally, a handling unit could be a pallet or a wire box, but the concept of handling unit is more generic and includes any type of grouped materials and their packaging material.
In Warehouse Management, you can use handling units to process warehouse movements such as putaway, picking, or stock transfers. Handling units can be created in the warehouse, labeled, and also picked for existing deliveries.
© SAP AG
SCM631
2-22
Handling Units in the Supply Chain
Handling Units
Describe what is packed how
Have an identification number (licence plate eg. EAN128 or UCC128)
Have a history
Simplify the operation in the Supply Chain
Are known by all logistic applications
Enabling
Goods movements without typing material numbers
Customer specific packing
Inventory control per Handling Unit
SAP AG 2002
Handling units simplify the processes in logistics. Any goods movement can be done for the handling unit.
A handling unit is created only once. The content and the history information are kept in the handling unit and from there are available to the different logistics components.
© SAP AG
SCM631
2-23
Identification (EAN 128)
SSCC-18 = Serialized Shipping Container Code (18 Digits)
Worldwide unique within one year T 1
Origin (ILN) 2 . . . . . . . . . 8
T = Handling Unit Type
Consecutive Nr 9 . . . . . . . . . . 17
18
C = Check Digit
EAN 128 Definition Application Identification Barcode Profile
C
EAN 128 Decode Functions
(02) |||
| ||| | ||| (15) | || || ||| (37) | || ||| ||
EAN 13 (00) |
||| || ||| | ||| | |||| (10) | ||| | || ||| |||| SSCC
(37) |
Batch
|| ||| || (311) || | ||| (321) |||| | ||
SAP AG 2002
Since a handling unit is a physical unit of packaging materials (load carrier/packaging material) and the goods contained therein, each handling unit must be clearly identifiable. This unique identification takes place through an identification number.
For consistency, it is appropriate to assign a unique number to each handling unit. Within a client, the uniqueness of the number can be ensured through a number range object. Only with the assignment of a serialized shipping container (SSCC-18) can you guarantee that the identification number is unique throughout all the systems.
© SAP AG
SCM631
2-24
Handling Units and Warehouse Management
Handling Units
Storage Units
and
Have the same Identification Number (SSCC)
Can be nested
Know all quant information
Know serial numbers
Know packaging materials
Aggregate all materials from nested Handling Units
Are generated automatically by the Handling Unit
SAP AG 2002
Handling units are known in Warehouse Management. A handling unit in the warehouse becomes a storage unit. The storage unit recognizes the sum of the materials and their related quantities. Handling units are part of the packing hierarchies (resulting from nesting) and their serial numbers relate to them. If the stock is changed, it follows that both the storage unit and the handling unit are changed as well.
© SAP AG
SCM631
2-25
Creation of an Handling Unit
Manually
Taking the packaging material
Naming the pallet according to SSCC18
Packing the materials
Printing a label
Automatically
A quantity of material to be packed with packing instructions leads to a number of Handling Units with the same content
=
+
SAP AG 2002
Packing is an independent function within logistics. You can create handling units and assign material items at any point in the packing dialog by entering a packaging material. You can pack the handling units you created into other handling units, and so on, forming as many packing levels as you like (multilevel packing). Automatic packing allows you to use packing proposals to create handling units automatically in the background. The proposal includes both packaging material and the content for each handling unit.
© SAP AG
SCM631
2-26
Business Processes Inbound Inbound business processes covered with Handling Unit Management
Goods Receipt Process
Handling Units in the inbound delivery/ASN
Quality Management with Handling Units
Putaway in the warehouse
Production Replenishment
Order dependent (Pick Parts)
Order independent
Special processes in Production
Material Reconciliation
SAP AG 2002
Goods receipt and putaway are two basic warehouse processes, which take place when goods are delivered from a vendor or from production. The putaway process includes putting away goods in storage bins in the warehouse. You can use the putaway strategies in Warehouse Management to find a suitable bin easily.
When a vendor notifies the goods recipient of the delivery of goods by using a shipping notification, this can also contain packaging information. The shipping notification generates an inbound delivery that includes the packing data from the shipping notification. Also, an inspection lot in Quality Management can be created for the handling units, and the stock is then posted into quality inspection stock upon goods receipt.
For production supply, you can carry out material staging of production order components with handling units in conjunction with Warehouse Management.
You can also use material reconciliation with handling units. Material reconciliation is used to analyze and verify ingredients at the end of the production process in process manufacturing. It allows comparison of the material quantity that actually flowed in with the planned quantity or the quantity of the material produced.
© SAP AG
SCM631
2-27
Goods Receipt with Handling Units Inbound Delivery/ ASN containing Handling Unit numbers HU-Nr. 69179
Inbound Shipment 123456 123456
HU-Nr. 69180 HU-Nr. 69181
Transferorder Putaway
Goods Receiptposting
HU-Nr. 69179 HU-Nr. 69180 HU-Nr. 69181
Putaway confirmation
SAP AG 2002
You can generate putaway transfer orders for inbound deliveries or for handling units. If there is more than one Handling Unit in an inbound delivery, the putaway TO is split up in single transfer orders for every single handling units. You can create transfer orders before or after GR postings in Inventory Management. If you carry out the putaway before the GR posting, the storage unit is at the destination bin of the transfer order. A negative quant with the storage unit number is generated in the source storage bin of the transfer order. During goods receipt posting for the inbound delivery, negative quants in the GR area are deleted and the system notes in the storage unit that partial picks are now possible.
© SAP AG
SCM631
2-28
Business Processes Outbound Outbound business processes covered by Handling Unit Management:
Finished Goods processes in production
Packing in production
Goods Receipt from production
Picking and packing
Pick Handling Units
Handling Units in the Delivery
Handling Units and RF
Delivery Split with Handling Units
Handling Units in the shipment
Plant to plant movements
SAP AG 2002
Packing finished goods in production means you can group material produced from a production order in handling units. You pack the material and post goods receipt with reference to the handling unit or to the order. This means that material can be divided between several handling units.
Since all inventory is principally managed with handling units, it is necessary, even for pick TOs, that the stock is repacked into handling units.
Using the mobile data processing function, you can perform quick and error-free data transfer, because the data entered through scanning the bar codes is posted synchronously in SAP R/3.
Handling units are useful in transportation as well, because a container could be packed into a truck.
© SAP AG
SCM631
2-29
Goods Issue with Handling Units
Outbound Delivery Picking Transfer Order
ASN
HU-Nr. 69179 HU-Nr. 69180 HU-Nr. 69181
HU-Nr. 69179 HU-Nr. 69180 HU-Nr. 69181
Goods Issue
Outbound Shipment
SAP AG 2002
During picking, if a complete stock pick is made, it is possible to leave the stock in the storage unit and post only the stock to another bin. In Customizing, you can define by storage type or movement type whether the system should transfer the entire handling unit in the confirmation transaction as a default. When confirming a transfer order for a delivery, the pick-handling units are reported to the delivery. This allows the picking and packing to take place with handling units in one step.
© SAP AG
SCM631
2-30
Pick Handling Units
Partial picking quantities or lower-level Handling Units are transferred to a picking container. This picking container represents a Handling Unit itself, the pick Handling Unit. Process steps for picking are:
Taking an empty pick Handling Unit
Getting the stock with the options of:
Full Handling Units
Item Transfer Handling Unit to Handling Unit
Nested Handling Unit to Pick Handling Unit
Unpack Stock from Nested Handling Unit to Pick Handling Unit
Splitting the TO Item, if Pick Handling Unit overflows
SAP AG 2002
Picking
for deliveries with handling units basically involves a pick-and-pack scenario. This means that after the transfer order is confirmed, the pick-Handling Unit is always assigned to the delivery. The result is that the delivery is always packed completely after finished confirmation.
© SAP AG
SCM631
2-31
Functions of RF and Handling Units
The functions of radio frequency processing with HUs are:
Pick and Pack
Pack and Unpack
Load and Unload
Handling Unit Detail
Handling Unit Labels LM18 LM19 LM22 LM24 LM25 LM35 LM45 LM46 LM66 LM76
Handling Unit Inquiry Handling Unit - Pack Handling Unit - Unpack Packing HU by Delivery Unpack HU by Delivery Load Control - Detail by HU Pick and Pack Pick and Pack by Delivery Goods Issue by HU Goods Receipt by HU
SAP AG 2002
Pick and pack allows you to pack goods during the picking process. If you select a handling unit for an outbound delivery, you can specify the packaging material that you want to use and pack the goods directly. The handling-unit identification is assigned to the transfer order for picking.
Pack and unpack , with its the radio frequency function, supports creation of handling units during goods receipt and in the warehouse.
You can use loading and unloading functions to control the loading and unloading of handling units from or onto different means of transport.
You can use the corresponding inquiry function to call up detailed information about handling units.
The radio frequency function also supports printing of handling unit labels.
© SAP AG
SCM631
2-32
Handling Unit Management
You are now able to:
Explain the concept of a Handling Unit
Describe how Handling Units and Storage Units fit together
Describe the inbound and the outbound process with Handling Units
SAP AG 2002
© SAP AG
SCM631
2-33
© SAP AG
SCM631
2-34
Storage Unit Management - Exercises Unit: Storage Unit Management Topic: Storage Unit Management In this exercise, you will: •
Create a storage type for SU-managed materials
•
Customize your SU-managed area to use bin sectioning
•
Post a goods receipt
•
Create and confirm a transfer order with an SU number
•
Display a storage unit
In one area of your warehouse, you manage spools of cable for maintenance purposes. It is a business requirement 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 for each storage unit how many meters of cable you have. These spools are stored on industrial size pallets (IP) in a section of the warehouse that is laid out in aisles.
1-1
Verify that Storage Unit Management is allowed in your warehouse then create a new storage type in your warehouse using SUM for spool storage. 1-1-1 Go to the control parameters for your warehouse and verify that SU Management is active . 1-1-2 Create a new storage type 008 for spool storage by coping storage type 007. Activate SU mgmt, deactivate Storage Section Search, and change the description to Spool Storage. 1-1-3 Because you created the new storage type 008, you also need to create a storage section 001. Create the storage section 001- Total Section. 1-1-4 Also because you created the new storage type 008, you must allow the storage unit type IP to be stored there. Go to customizing the strategies , under storage bin type search and allow this pallet size in your new storage type. 1-1-5 Also within Strategies, define bin sectioning for storage type 008. Bin sectioning is available in the placement strategy for pallets. In section A of storage type 008, you have 4 bin sections, (1-4). You must also allow industrial pallets to be stored in the bin section for storage type 008.
© SAP AG
SCM631
2-35
1-1-6 For the test, you want to direct your spool receipts to storage type 008. Change the storage tyope search sequence so that the cables are sent to storage type 008. Define a new storage type indicator 008, then create the search sequence to direct materials with this indicator into storage type 008. 1-1-7 Create material C-1030-##, Material Type Trading Good , and Industry Sector Mechanical Engineering. Copy material C-1030 and attach the new storage type placement / removal indicator . Create the Basic Data 1, Purchasing, Warehouse 1 & 2, and Accounting 1 views for plant 1000 and your warehouse 1##. On the Warehouse Management 1 & 2 views, enter the stock placement and removal indicator 008. A standard spool should carry 500 meters of cable, but the exact amount of meters on each spool could vary. Enter the palletization data as 500m per IP. 1-1-8 You will need to create some bins in your storage type that will represent the pallets. Create manually bins P-001, P-002, and P-003 for storage type 008, storage section 001 in your warehouse. The storage bin type = P1. 2-1
Test your configuration settings. 2-1-1 Execute a goods receipt without PO for the material C-1030-## quantity 2078 M. 2-1-2 Create a TO for the material you just received. You have received 4 spools with the following lengths: 498, 530, 510, 540. Enter the corresponding palletization data and save. Transfer order number ___________________ Confirm the transfer order. Display the bin. How many quants are in the bin? ___________ How many bin sections are occupied? _______ Storage unit numbers:
(1)____________________ (2)____________________ (3)____________________ (4)____________________
© SAP AG
SCM631
2-36
Management - Exercises
Unit: Storage Unit Management Topic: Bulk Storage In this exercise, you will: •
Customize the bulk storage area
•
Modify a material master record
•
Post a goods receipt without reference
•
Create and confirm a transfer order to bulk storage
•
Create a goods issue from bulk storage
In one area of your warehouse, you manage mixed materials on pallets. These pallets can be stacked in different ways, depending on whether you are stacking large or small pallets. You have a business 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
3-1
Customize the bulk area. 3-1-1 Verify the storage type control for your bulk materials. Find the record for your warehouse and storage type 004. Is management of partial quantities allowed? _________ 3-1-2 You must modify storage type 004 in your warehouse to use storage unit management. Verify that the placement strategy for storage type 004 is Bulk and the removal strategy is FIFO. Activate SU Management. Allow mixed storage without limitation. Remove the entry 001 from the Return Storage Type field. Change the data where necessary. 3-1-3 Now you must return to the storage type control in the first step above to set the totals info. Set the totals column to 1 – Totals info not batch specific. 3-1-4 Define the block structure. If you are stacking industrial pallets, you can stack them 4 deep and 3 high for a total of 12 pallets in the area. If you are stacking Euro pallets, you can stack them 5 deep and 4 high, for a total of 20 pallets in the area. Use P1 for the storage bin type.
© SAP AG
SCM631
2-37
3-1-5 You must allow the storage unit types IP and E1 to be stored in storage type 004. Go to the Customizing for strategies, and, under storage bin type search allow these pallet sizes in your bulk storage area. 3-2
For this test, verify that your receipts for these materials will be directed to storage type 004. You want to create a new storage type indicator then modify the storage type search sequence . 3-2-1 Define a new storage type indicator 004 for bulk-mixed pallets . Enter the search sequence for this indicator so that materials are put away in storage type 004. Create this search sequence for removing materials from this storage type as well. 3-2-2 Then modify the material master to attach the new stock placement / removal indicator to the following materials: T-BW04-## T-BW05-## T-BW06-##
3-2-3 You will need to create some bins in your storage type. Create bins B-001, B002 and B-003 for storage type 004, storage section 001. The storage bin type = P1. 4-1
Now test your configuration settings with a goods receipt. 4-1-1 Post a goods receipt without PO for the following materials and quantities: T-BW04-##
8
T-BW05-##
7
T-BW06-##
5
4-1-2 Create a TO with reference to the material document created by the goods receipt. Create the TO in foreground. Create a single SU using storage unit type E1. Transfer order Number ___________________ 4-1-3 Confirm the transfer order. Note the storage unit number. Storage unit number: ____________________ 4-1-4 Display the storage unit. Drill down to see the storage bin data.
© SAP AG
SCM631
2-38
4-2
Now test your configuration settings with a goods issue. 4-2-1 Do a goods issue for material T-BW06-##, quantity 3 to cost center 1000. 4-2-2 Create a TO for the material document that was created by the goods issue. 4-2-3 Confirm the TO. Be sure to confirm the TO for the correct quantity!! 4-2-4 Display the storage unit number to see the updated quantity.
© SAP AG
SCM631
2-39
© SAP AG
SCM631
2-40
Solutions Unit: Storage Unit Management
1-1 Accelerated SAP Customizing Edit Project SAP Reference 1-1-1 Tools IMG Logistics Execution Warehouse Management Master Data Define control parameters for warehouse number. Position on your warehouse and double click, or select your warehouse and choose Details.
1-1-2 SAP Reference IMG Logistics Execution Warehouse Management Master Data Define storage type . Position on your warehouse and storage type 007 . Select 007, select copy as. Make the appropriate changes and save. 1-1-3 SAP Reference IMG Logistics Execution Warehouse Management Master Data Define Storage Section. Select New Entries. Field Name or Data Type
Values
Warehouse
1##
Type
008
Storage section
001
Storage Area Name
Total Section
Logistics Execution 1-1-4 SAP Reference IMG Strategies Activate storage bin type search Type – Storage Type. Select New Entries.
© SAP AG
Field Name or Data Type
Values
Warehouse
1##
Type
008
1. Storage Unit Type
IP
SCM631
Warehouse Management Assignments – Storage Unit
2-41
1-1-5 SAP Reference IMG Logistics Execution Warehouse Management Strategies Putaway strategies Define strategy for pallets Bin section – Define. In this table, define how many bin sections are available in which section of the storage type, and you define whether the bin suffix will be alpha (BIN/A) or numeric (BIN/1).
Select New Entries. Field Name or Data Type
Values
Warehouse
1##
Type
008
Section
A
1
1
2
2
3
3
4
4
Still within defining the pallet strategy, select Bin and storage unit types - Assign. Select New Entries.
© SAP AG
Field Name or Data Type
Values
Warehouse
1##
Storage Type
008
Storage Bin Type
P1
Storage Unit Type
IP
Bin Section
A
SCM631
2-42
1-1-6 SAP Reference IMG Logistics Execution Warehouse Management Strategies Activate storage type search Storage type indicator Define. Select New Entries. Field Name or Data Type
Values
Warehouse
1##
Storage Type Indicator
008
Description
Spool Storage
Go back and select Determine search sequence. Select New Entries. You will need 2 entries, one for Placement (Process ‘E’) and one for Removal (Process ‘A’).
© SAP AG
Field Name or Data Type
Values
Warehouse
1##
Operation
E
Type Indicator
008
1. Storage Type
008
Warehouse
1##
Operation
A
Type Indicator
008
1. Storage Type
008
SCM631
2-43
1-1-7 Go to the material master and create the material C-1030-## by copying C1030. Create the Basic Data 1, Purchasing, Warehouse 1 & 2 and Accounting 1 views for plant 1000, warehouse 1##. Logistics Logistics Execution Master data Material Material Create Immediately. Field Name or Data Type
Values
Material
C-1030-##
Industry Sector
Mechanical Engineering
Material Type
Trading Good
Copy from Material
C-1030
Select views
Basic Data, Purchasing, Warehouse 1&2, Accounting 1
Create Views Selected
Select
Organization Levels: Plant
1000
Warehouse
1##
Copy From: Plant
1000
WM1 View: Stock removal storage type indicator
008
Stock placement
008
WM2 View: LE quantity
500
Unit of Measure
M
SUT
IP
1-1-8 Logistics → Logistics Execution → Master Data → Storage bin → Create → Manually.
© SAP AG
Field Name or Data Type
Values
Warehouse
1##
Storage Type
008
Storage Bin
P-001, P-002, P-003
Storage Section
001
Storage Bin Type
P1
SCM631
2-44
2-1
Test your configuration settings. Goods Receipt for 2-1-1 Logistics Logistics Execution Inbound Process Other activities Goods receipt for other activities . Enter movement type 501, plant 1000, storage location 01##.
2-1-2 Logistics Logistics Execution Inbound Process Goods Receipt for Purchase Order, Order, Other Transactions Putaway Create Transfer Order By Material. Enter your warehouse 1## and Material C-1030-## and select enter. Select the TR and process in foreground. Enter the palletization data for each spool with SUT IP as directed in the exercise. Save. Confirm the Transfer Order. Select Logistics Logistics Execution Inbound Process Putaway Confirm Transfer Order Single Document One Step . Choose Input List. Page over to see the SU number. Save to confirm . Display the bin. Select Logistics Execution Storage bin Display ### Single bin.
Master Data
Warehouse
How many quants are in the bin? 4 How many bin sections are occupied? 4 (display bin sectioning) Select the Stock tab to see the quants, then select the Storage Unit Details icon to see the Storage Units. Select the Bin Sectioning tab to see the bin sections .
© SAP AG
SCM631
2-45
© SAP AG
SCM631
2-46
Solutions Unit: Bulk Storage
3-1
. Logistics Execution Warehouse Management 3-1-1 SAP Reference IMG Strategies Putaway Strategies Define strategy for bulk storage. Select Storage Type ctrl – Define. Choose New Entries. Position on your warehouse and storage type 004. Yes, partial quantity management is allowed for this storage type. Logistics Execution Warehouse Management 3-1-2 SAP Reference IMG Strategies Putaway Strategies Putaway Strategy - Activate. Position on your warehouse and storage type 004. Double click or select and choose details. Set the SU mgmt flag to Active . Set Mixed Storage to X. Blank out the entry 001 for the Return Storage Type. Logistics Execution Warehouse Management 3-1-3 SAP Reference IMG Strategies Putaway Strategies Define strategy for bulk storage Storage Type Ctrl - Define.
© SAP AG
SCM631
2-47
3-1-4 SAP Reference IMG Logistics Execution Warehouse Management Strategies Putaway Strategies Define strategy for bulk storage Definitions – Block Structures. Choose New Entries. Field Name or Data Type
Values
Warehouse
1##
Storage Type
004
Storage Bin Type
P1
SUT
IP
Stacks
4
Stack Height
3
Warehouse
1##
Storage Type
004
Storage Bin Type
P1
SUT
E1
Bulk Storage Indicator
BL
Stacks
5
Stack Height
4
Logistics Execution 3-1-5 SAP Reference IMG Strategies Activate storage bin type search Type – Storage Type. Choose New Entries.
© SAP AG
Field Name or Data Type
Values
Warehouse
1##
Storage Type
004
1. Storage Unit Type
E1
2. Storage Unit Type
IP
SCM631
Warehouse Management Assignments – Storage Unit
2-48
3-2 Logistics Execution Warehouse Management 3-2-1 SAP Reference IMG Strategies Activate storage type search Storage type indicator Define. Choose New Entries. Field Name or Data Type
Values
Warehouse
1##
Storage Type Indicator
004
Description
Bulk-Mixed Pallets
SAP Reference IMG Logistics Execution Warehouse Management Strategies Activate Storage Type Search Determine search sequence. Choose New Entries. You will need 2 entries, one for placement (Process ‘E’) and one for removal (Process ‘A’). Field Name or Data Type
Values
Warehouse
1##
Operation
E
Type Indicator
004
1. Storage Type
004
Warehouse
1##
Operation
A
Type Indicator
004
1. Storage Type
004
Logistics Execution Master Data Material Material 3-2-2 Logistics Change Immediately Enter the material and choose the Warehouse 1 view for Plant 1000, Warehouse 1##. Change both the stock placement and stock removal indicators to 004.
3-2-3 Logistics Logistics Execution Master Data Storage bin Create Manually.
© SAP AG
Field Name or Data Type
Values
Warehouse
1##
Storage Type
004
Storage Bin
B-001; B-002; B-003
Storage Section
001
Storage Bin Type
P1 SCM631
2-49
4-1 4-1-1 Logistics Logistics Execution Goods Receipt Process Goods Receipt for other Activities. Enter movement type 501 , plant 1000, storage location 01##. Logistics Execution Inbound Process Goods Receipt for 4-1-2 Logistics Purchase Order, Order, Other Transactions Putaway Create Transfer Order By Material Document. Enter the material document and Create SU (single). Enter storage unit type E1. Create and Save.
4-1-3 Logistics Logistics Execution Inbound Process Goods Receipt for Purchase Order, Order, Other Transactions Putaway Confirm Transfer Order Single Document In One Step. Select Input List. Page over to see the SU number. Save to confirm. Logistics Execution Internal Warehouse Processes Bins 4-1-4 Logistics and Stock Display Single Displays Storage Unit. Enter the storage unit number and Enter.
4-2 Logistics Execution Outbound Process Goods Issue for 4-2-1 Logistics Other Transactions Enter Goods Issue. Enter movement type 201 , plant 1000, storage location 01## and enter . Enter cost center 1000 , material TBW06-##, quantity 3 and Save. Logistics Execution Outbound Process Goods Issue for 4-2-2 Logistics Other Transactions Picking Create Transfer Order By Material Document. Enter the material document and Generate + next Material. Save.
4-2-3 Logistics Logistics Execution Outbound Process Goods Issue for Other Transactions Picking Confirm Transfer Order Single Document In One Step. Select Input List. Select Confirm Internally. Enter the Storage Unit Number. Enter the picked quantity (3) and Confirm Item in Background. Save. 4-2-4 Logistics and Stock
© SAP AG
Logistics Execution Internal Warehouse Processes Display Single Displays Storage Unit.
SCM631
Bins
2-50
Hazardous Materials Management
SAP AG 2002
© SAP AG
SCM631
3-1
Hazardous Materials Management: Overview Diagram
Course Overview Storage Unit Management Hazardous Materials Management Additional Functions in TO Processing Radio Frequency / Frequency / LSR Decentralized Warehouse Management Technical Topics Summary
SAP AG 2003
© SAP AG
SCM631
3-2
Hazardous Materials: Objectives
At the conclusion of this topic, you will be able to:
Create a hazardous material master record
Define a material as a hazardous material
Customize storage procedures for storing hazardous materials
SAP AG 2002
© SAP AG
SCM631
3-3
Hazardous Materials Mgmt.: Business Scenario
Your Engineering department has selected a new lubricant to use in the pump assembly. This lubricant is considered a hazardous material and must be stored accordingly. You need to configure your warehouse for the storage of hazardous materials, create the hazardous material master records, and assign them to the appropriate material master record.
SAP AG 2002
© SAP AG
SCM631
3-4
Handling Hazardous Materials
SAP AG 2002
The aim of hazardous material handling is to store hazardous materials separately according to storage class and water pollution class.
Storage Class - Categorization of hazardous materials according to their storage requirements:
Stora60
ge class 1
explosive materials
Storage class 3.B
flammable liquids
Storage class 6.1
poisonous materials
Storage class 7
radioactive materials
Water Pollution Class - Categorization of hazardous materials according to their capacity for polluting water:
Water pollution class 1
minimal water pollution danger
Water pollution class 2
water pollutant
Water pollution class 3
extreme water pollution danger
© SAP AG
SCM631
3-5
Hazardous Material Handling: Master Data
Warehouse number: Region
Hazardous material
Storage type Storage classes permitted WPC allowed Hazardous material handling active? Storage class Water pollution class
Storage section
Storage type
Fire section
A
Storage type
B
C
SAP AG 2002
Materials are assigned to a hazardous material within a geographical region. The hazardous material record stores data such as the storage class and the water pollution class.
The warehouse number is assigned to a region.
You can decide for each storage type individually whether hazardous material handling is active. The handling of hazardous materials is activated at storage type or section level.
Storage classes and water pollution classes are allowed for each storage type. Hazardous materials with similar characteristics are grouped within a storage class.
Each storage bin is assigned to a fire-containment section. An inventory list for the fire department can be created for each fire-containment section.
© SAP AG
SCM631
3-6
Storage Type Control
Goods receipt area s s 1 r. c l a o t S X M a t.
M at . Y S t or . c l ass 2
St. type 001 Storage class 1
St. type 002 Storage class 2
Material/Hazardous mat. Storage class Water pollution class Storage type indicator SAP AG 2002
A hazardous material's storage and water pollution classes are taken into account during the storage type search. In this way, variable control can be attained and stock placement is achieved according to:
storage type indicator
storage class
water pollution class
© SAP AG
SCM631
3-7
Storage Section Control
Goods receipt area
Storage type type 001
Storage class
Section 1/ storage class: 1
Section 2
Material/Hazardous mat. Storage class Water pollution class Storage type indicator
SAP AG 2002
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. In this way, variable control can be attained according to:
storage section indicator
storage class
water pollution class
© SAP AG
SCM631
3-8
Hazardous Material: Reports
Fire Department Inventory List Correct Storage of Hazardous Materials Hazardous Substance List
Sec. A
Sec. B
SAP AG 2002
Fire Department Inventory List
Correct Storage of Hazardous Materials
This report displays an inventory list for the fire department that includes information about the storage class, water pollution class, and amount of water pollutants for the hazardous materials in your warehouse. You can choose to run the report for a range of the fire-containment sections and storage types within the warehouse, or for an entire warehouse.
This report checks whether hazardous materials are correctly stored. For each storage type, this report lists the number of bins that were checked, the number of quants that were correctly stored, and the number of quants that were stored improperly based on the hazardous materials storage parameters that were set up for your warehouse.
Hazardous Substance List
This report lists goods by hazardous material record number, concentration, hazardous material warnings, aggregate state, and quantities. For this report, materials are only selected from storage types that are defined as storage types for hazardous materials in the WM system.
© SAP AG
SCM631
3-9
Hazardous Materials Management: Topic Summary
You are now able to:
Create a hazardous material master record
Define a material as a hazardous material
Customize storage procedures for storing hazardous materials
SAP AG 2002
© SAP AG
SCM631
3-10
Hazardous Materials - Exercises Unit: Hazardous Materials Management Topic: Hazardous Materials At the conclusion of this exercise, you will be able to: •
Make the appropriate configuration settings in your warehouse to store hazardous materials
•
Create a hazardous material master record
•
Create a new material master
•
Assign the hazardous material master record to the n ew material master record
•
Receive and put away the new material
•
Review the available hazardous material reports
Engineering 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 storage of hazardous materials, create the hazardous material master records and assign them to the appropriate material master records. 1-1
Create the warehouse structure for storage of hazardous materials. 1-1-1 Hazardous materials storage type 006 has been previously defined; however, no bins have been created. Create four (4) bins 001 through 004 in the appropriate storage type and storage section. Assign fire containment section B to the stoarge bins with a maximum weight of 1000kg. You can create these bins manually or automatically using the template. 1-1-2 Go into the IMG and activate the hazardous materials check. This check is activated by storage type. Normally, you would activate the hazardous material check in every storage type except your interim storage types so that hazardous materials do not get incorrectly stored in inappropriate areas. For the purposes of this exercise, we will activate the hazardous materials check only in storage type 006. For your warehouse 1## and storage type 006, activate the hazardous material check for the storage type level only. The lubricant is considered a water pollutant. 1-1-3 After you have activated the check, verify the region code for your warehouse (set to the country code of your choice).
© SAP AG
SCM631
3-11
1-1-4 Now customize your hazardous material storage type so the storage class 3A is allowed to be stored there. 1-1-5 When hazardous materials are received that are assigned to storage class 3A and water pollution class 2, they should be brought to storage type 006. Change the table for the search sequence so that these materials go to the storage type for hazardous materials. You want to modify the search sequence for both putaway and stock removal. 1-2
Create the required master data. You need to create a hazardous material master record and link it to a material master record. 1-2-1 Create the hazardous material master record for T-HAZ01-##. Use the region code you previously assigned to your warehouse. This record is for the Lubrication Group ## , with a Storage Class of 3A. The materials are fluid and they are considered water pollutants . In case of fire, do not extinguish with water. Add any other warnings as appropriate. 1-2-2 Create a new material master record for the lubricant T-BW22-## . Create this material in plant 1000, warehouse 1##, storage location 01##, with reference to the existing lubricant T-BW20-## (referencing the same organization levels). This new material is a Trading Good in the Mechanical Engineering Industry Sector . Create the Basic Data 1, Purchasing, General Plant Data/Storage 1, Warehouse Management 1&2 and Accounting views.
1-3
Test your configuration settings. 1-3-1 Execute a goods receipt without reference (movement type 501) for 500 pieces of material T-BW22-## into storage location 01##. 1-3-2 Create and confirm a transfer order for the material document. You will receie 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 5th pallet in the goods receipt area.
1-4
Evaluate the various reports that are available. 1-4-1 Run the Fire Department Inventory List report and determine the total amount of stored weight for storage class 3A. 1-4-2 Run the Correct Storage of Hazardous Materials report for all storage types and determine if any hazardous materials are NOT properly stored in your warehouse.
© SAP AG
SCM631
3-12
Hazardous Materials - Solutions Unit: Hazardous Materials Management Topic: Hazardous Materials
1-1 1-1-1 Manual creation: Logistics bin Create Manually
Logistics Execution
Master Data
Field Name or Data Type
Values
Warehouse
1##
Storage Type
006
Storage bin
001 (002, 003, 004)
Storage Section
001
Fire Containment Section
B
Maximum Weight
1000
Storage
Manual creation: Logistics Logistics Execution Master Data Storage bin Create Automatically Select New Entries. Note: Remember to line up the entries appropriately.
© SAP AG
Field Name or Data Type
Values
Warehouse
1##
Storage Type
006
Current number
001
Template
NNNCCCCCCC
Structure
AAA
Start value
001
End value
004
Increment
1
Storage Section
001
Maximum Weight
1000
Fire Containment Section
B
SCM631
3-13
Select Enter. Select Environment Create Bins. Choose Create Online. Select Yes to create the bins online. 4 bins are created.
© SAP AG
SCM631
3-14
AcceleratedSAP Customizing Edit Project SAP Reference 1-1-2 Tools IMG Logistics Execution Warehouse Management Hazardous Materials Strategies Activate Hazardous Materials Management. Activate. Position on your warehouse and Select HazMaterial Check storage type and enter Hazardous Materials Check 1 (Check at Storage Type Level). Enter 2 in the WPC column. Logistics Execution Warehouse Management 1-1-3 SAP Reference IMG Hazardous Materials Strategies Activate Hazardous Materials Management. Under Assignments Region Codes, Select Warehouse Number. Update the region code for your warehouse, if necessary. Logistics Execution Warehouse Management 1-1-4 SAP Reference IMG Hazardous Materials Strategies Activate Hazardous Materials Management. Under Assignments Storage Classes Allowed, Select Storage Type. Choose New Entries. Field Name or Data Type
Values
Warehouse
1##
Storage Type
006
Storage class
3A
Priority Blocked Confirm Placement
© SAP AG
SCM631
3-15
Reference IMG Logistics Execution Execution Warehouse Warehouse Management Management 1-1-5 SAP Reference Hazardous Hazardous Materials Materials Strategies Strategies Activate Hazardou Hazardouss Materials Management. Management. Storage Type Type Search Search Determine Determine Search Sequence. Sequence. Select Select New Entries. Entries.
© SAP AG
Field Name or Data Type
Values
Warehouse
1##
Operation
E
Storage class
3A
WPC
2
1. Storage Type
006
Warehouse
1##
Operation
A
Storage class
3A
WPC
2
1. Storage Type
006
SCM631
3-16
1-2 1-2-1 Logistics Material
Master Data Data
Material Material
Field Name or Data Type
Values
Haz. Mat. Num
T-HAZ01-##
Region Code
Your warehouse region code
Haz. Mat. Text
Lubrication Group ##
Storage class
3A
Water pollution class
2
HazWarning
01
Aggregate state
2
Hazardous Warning
You select
1-2-2 Logistics Create
© SAP AG
Logistics Execution Create
Logistics Execution Immediately. Immediately.
Master Data Data
Material Material
Field Name or Data Type
Values
Material
T-BW22-##
Industry Sector
Mechanical Engineering
Material Type
Trading Good
Copy from Material
T-BW20-##
Select views
Basic Data 1, Purchasing, General Plant Data / Storage 1, Warehouse Management 1 & 2, Accounting 1
Organization Levels: Plant
1000
Storage Location
01##
Warehouse
1##
Copy From: Plant
1000
Storage Location
01##
Warehouse
1##
SCM631
Hazardous Hazardous
Material
3-17
1-3 Logistics Execution Inbound Process Goods Receipts Receipts for 1-3-1 Logistics Purchase Orders, Order, Order, or other other Transactions Transactions Goods Receipts Receipts for Other Activities Field Name or Data Type
Values
Movement Type
501
Plant
1000
Storage Location
01##
Material
T-BW22-##
Quantity
500
1-3-2 Logistics Logistics Execution Inbound Process Goods Receipt Receipt for Purchase Order, Order, Order, Other Transactio Transactions ns Putaway Create Transfer Transfer Order By Material Document. You will get an error during TO creation th because you cannot putaway the 5 item of 100 pieces. Create and Confirm the TO for the other 4 items, leaving 100 in the Goods Receipt area. 1-4 Logistics Execution Information Information System Warehouse Warehouse 1-4-1 Logistics Stock Hazardous Hazardous Materials Materials Fire Department Department Inventory Inventory List List Logistics Execution Information Information System 1-4-2 Logistics Stock Hazardous Hazardous Materials Materials Check Goods Goods Storage Storage
© SAP AG
SCM631
Warehouse Warehouse
3-18
Additional Functions in TO Processing
Performance Data
Transfer Order Splitting
SAP AG 2003
© SAP AG
SCM631
4-1
Additional Functions in TO Processing: Overview Diagram
Course Overview Storage Unit Management Hazardous Materials Management Additional Functions in TO Processing Radio Frequency / LSR Decentralized Warehouse Management Technical Topics Summary
SAP AG 2003
© SAP AG
SCM631
4-2
Additional Functions in TO Processing: Business Scenario
You have to check the planned data and actual data, and the TO-split function in WM
SAP AG 2003
© SAP AG
SCM631
4-3
Performance Data: Topic Objective
At the conclusion of this topic, you will be able to:
Describe the Performance Data contained in the Transfer Order
SAP AG 1999
© SAP AG
SCM631
4-4
Scenario: Goods Receipt
Storage ItemType 1 005 GR Area
Storage Type 015
Item2
SAP AG 2002
In this business scenario, a goods receipt with two items is to be processed in the warehouse. The materials are to be put away in two different areas of the warehouse. What is the time estimate for this process versus the actual time taken? Performance data used in the Warehouse Management system is contained in the transfer order header and include both planned and actual data. Planned data is calculated, pre-existing target data that pertain to the processing of a WM transfer order. The planned TO processing time is the target time, or the time that is expected (planned) for a worker to process an entire transfer order (with one or several items). Actual data is the actual information about the processing of a transfer order. This data includes worker (personnel number), duration (actual time required to process the transfer order), start date and time, end date and time, and TO processing comment code.
© SAP AG
SCM631
4-5
Calculation of Target Data
Header Calculations Transfer Order TIME(WM) = Sum[PLAN(Item)] + PLAN(Setup) + PLAN(Travel) TIME(TOTAL) = TIME(WM) + TIME(EXTERNAL) 1 2
Item Level Calculation
Plan(Item) = PLAN(Constant) + PLAN (Variable)
SAP AG 2002
The planned processing time in the Transfer Order (TO) header is the processing time for the entire TO as calculated by WM. The planned TO processing time references the time unit (for example, minutes or seconds) that is calculated for the warehouse number. It is calculated as the sum of the planned processing times for the TO items, the setup times and the travel times.
The total planned processing time includes the planned processing time in WM plus the planned processing time that was transmitted from an external system to WM:
TIME(WM) = Sum[PLAN(ITEM)] + PLAN(SETUP) + PLAN(TRAVEL)
TIME(TOTAL) = TIME(WM) + TIME(EXTERNAL)
The planned processing time for the TO item is calculated from a constant processing time. For example, the planned setup time for the stock removal process for a TO item is added to the quantity dependent or variable processing time (for example, the processing time required to pick 10 cartons from a storage bin). The formula is:
PLAN(Item) = PLAN(Constant) + PLAN(Variable)
© SAP AG
SCM631
4-6
Actual Data
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 several transfer orders by central personnel (rapid creation)
Correction dialog for users with special authorization
Customize data entry
SAP AG 2002
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 TO header.
The indicator: Actual time required in TO controls whether the entry of actual time for a transfer order is necessary and in which format it is to appear. This indicator also controls which dialog box appears. Depending on the indicator you choose, the system selects the fields that are to be displayed for data entry.
With transaction LT1A, you can correct the data in the transfer order afterwards.
© SAP AG
SCM631
4-7
Use of Actual Data
Control of Transfer Order execution
Assign a processor prior to the TO execution
Recording work accomplished as statistical information
Worker and processing time for performance control
Selecting workers prior to processing transfer orders
Creating processing data for incentive wages
Worker, planned and processing times
SAP AG 2002
The transaction Single Entry of Actual Data allows you to assign a processor, using that person's personnel number.
This transaction uses report RLLT6300, which requires a variant that is created in Customizing.
You can transfer performance data to Human Resources (HR) via batch, and calculate incentive wages there. The batch program, RLT1HR00 (Interface WM pick orders → HR performance wage), calls an HR function module, which generates BAPIs to be processed in HR.
© SAP AG
SCM631
4-8
Transfer Order Splits: Objective
At the conclusion of this topic, you will be able to:
Describe Transfer Order split capability
SAP AG 1999
© SAP AG
SCM631
4-9
Splitting Transfer Orders for Large Deliveries
Goal:
Balanced workload based on volume and time TO #1
Transfer order as pick list
Automatic split criteria : Company Company
DEL
Invoice Invoice
Picking area
Planned time of Transfer Order
Weight
Volume
User Exit
M
Delivery
TO #2
TO #3
Transfer Orders
SAP AG 2003
Using the key for the movement type, the source and destination storage type, you can assign a performance data profile to a transfer order. Since the storage types in the transfer order are not at the header but at the item level, an implicit split is executed for the transfer order with a performance data profile. This means that the performance data profile applies to all items. For organizational reasons an explicit split might be desired, for example, a split according to picking areas or a parameter limit with respect to volume, weight or target time. Appropriate sorting of the TO items is a prerequisite for a suitable split.
© SAP AG
SCM631
4-10
Transfer Order Splitting
DELIVERY Not fulfilled
Transfer Order
Split Criteria?
Fulfilled
Transfer Order
Transfer Order
Transfer Order
SAP AG 2002
To achieve a balanced distribution of the workload of the warehouse, transfer orders can be split. Together with the splitting process, dynamic sorting of the TO items takes place. For this sorting process, you can use the sequence field in the storage bin. This field allows you to enter the exact sequence in which the storage bins are to be processed.
Transfer orders are split by a profile for the warehouse number. You can split the transfer orders by storage type and picking area:
Target time (header information), volume, and weight as value limits.
User exits are available for sorting and for splitting.
© SAP AG
SCM631
4-11
Additional Functions in TO Processing: Summary
You are now able to
Describe the performance data contained in the transfer order
Explain the possibilities for a transfer order split
SAP AG 2003
© SAP AG
SCM631
4-12
Radio Frequency/LSR
Implementing Radio Frequency
Scenarios for LSR
SAP AG 2002
© SAP AG
SCM631
5-1
Radio Frequency / LSR: Overview Diagram
Course Overview Storage Unit Management Hazardous Materials Management Additional Functions in TO Processing Radio Frequency / / LSR Decentralized Warehouse Management Technical Topics Summary
SAP AG 2003
© SAP AG
SCM631
5-2
Radio Frequency/LSR: Unit Objectives
At the conclusion of this unit, you will be able to:
Customize the Mobile Data Entry Screen
Activate the RF Monitor
Describe scenarios for linking WM to an automated Warehouse Control Unit
SAP AG 2002
© SAP AG
SCM631
5-3
Radio Frequency/LSR: Business Scenario
In your company, you have to evaluate the possibilities of linking mobile devices and physical warehouse control units to the SAP Warehouse Management System.
You configure the online Radio Frequency solution of WMS.
SAP AG 2002
© SAP AG
SCM631
5-4
General Goals
Increase automation in logistics
Increase mobility
Support local warehousing activities
Connect automatic storage retrieval systems
Connect automatic fork lift systems
Connect picking systems (carousels...)
SAP AG 2002
SAP WMS has an online solution for Radio Frequency processing in the warehouse.
SAP WMS can exchange data in each direction with an external warehouse control unit or hand held device.
SAP to External System:
External System to SAP:
Transfer Orders
Transfer Orders
Multiple Processing
Move Storage Unit
Request for Cancellation
Confirm Transfer Order
Inventory Records
Block Storage Bins
Cancel Transfer Order
Inventory Count Results
© SAP AG
SCM631
5-5
Radio Frequency in SAP Warehouse Management
Ready-to-use solution
RF terminals communicate data directly to the SAP R/3 System
Graphical and character RF terminals correspond to SAP R/3 screen display (SAP GUI)
Execution of individual functions by using pushbuttons on a touch screen, or function keys on a character-based device
Scanning information by using a bar code for transferring transferring information and verifying data
Hardware-independent Hardware-independent RF functionality functionality
2002 SAP AG 2002
The display of information on the RF device with a graphical screen corresponds to the SAP R/3 screen; the installation of an SAPGui is required. The various functions are executed via buttons on a touch screen. With a character device, SAP provides a non-graphical user interface.
The RF solution is designed for hardware-independent operation.
© SAP AG
SCM631
5-6
Benefits of Radio Frequency
Fast, reliable, and precise processing of individual goods movements
Simple and easy-to-view control for warehouse staff
Paper-free communication using mobile data processing techniques
Reasonable cost
Leads to a high standard of quality
2002 SAP AG 2002
The RF solution is new in SAP R/3 Release 4.6. However, the IDoc solution is still supported. The two different solutions have different aims. The following list provides the features.
MOB/LSR: Can also work offline Individual programming interface Requires third party software provider For complex automatic storage/retrieval systems Very secure asynchronous data transfer
Direct Radio Frequency: Online solution Standard solution with growing functionality Easy to write new ABAP transactions Cheaper Plug-and-play solution
© SAP AG
SCM631
5-7
System Landscape for RF Terminals
Different connection types of RF terminals
Graphical terminals using SAPGUI
Character terminals using TELNET TELNET and SAPConsole
Character terminals using proprietary protocol (supported by hardware hardware vendors) vendors) and SAPConsole SAPConsole
All screens and process flow logic can be developed with SPA Development Workbench.
Each screen can be replaced by a customer-specific screen without any need of change in processing logic (screen exit)
Easy implementation of new device types
Recovery in the case of a re-established connection after abnormal termination
2002 SAP AG 2002
© SAP AG
SCM631
5-8
Connection: From WMS to the RF Terminal
SAP Console (Windows NT)
SAP WMS
RF Terminal I/O
Data Connection
Translation
Interface Engine
r e l l o r t n o C F R
RF Terminal RF Terminal
SAP AG 2003
Zeichenorientierte Terminals werden mit dem WMS über SAPConsole verbunden. SAPConsole übersetzt die graphischen GUI-Informationen für nichtgrafische Bildschirme. Die SAPConsole kann auch durch Produkte von Hardwareherstellern ersetzt werden.
SAPConsole l uft auf einem NT-Frontend und verbindet die WMS-Daten mit dem RF-Controller, der Hardware. (Hinweis: Die Installation ist auch unter Windows 98 m glich, OSS-Hinweis 454430)
SAPConsole wird mit Release 4.6 ausgeliefert.
© SAP AG
SCM631
5-9
Radio Frequency Activities Selection of an RF Activity with pushbutton/function key
Next RF Activity selection on the following screen
SAP R/3 SAP R/3
F8 - LOff
F2-Clr
F3 - Back F4 - Next F8 - LOff
F2-Clr
F3 - Back F4 - Next
1. Putaway Activities 1. Select by SU
2. Picking Activities
2. Clustered
3. Inventory
3. Select by TO
4. Inquiry
4. System - Guided
5. Load Control 6. Queue
SAP AG 2002
Putaway process The warehouse employee scans the storage unit or the transfer order; with this information, the system tells him where to put the goods. When the goods are placed in the bin, the bin can be verified. This concludes the putaway process. Picking process The warehouse employee looks at a radio frequency terminal. This terminal displays the next transfer order, which indicates where to pick the next materials. At the bin the material or the EAN number can be verified by scanning it. Then the goods are taken to the goods issue area. Load control Packing and unpacking can be controlled by RF devices. There are different selection criteria such as loading for a shipment or for an outbound delivery, on the basis of identifiable shipping units. Inventory The physical inventory can be processed for storage bins or storage units. The user can choose a specific bin to be counted, or may be assigned to an inventory document at its creation time. After this, the user can work in a system-guided way. Stock information Information about material stock can be displayed. This supports selection by storage bins, goods receipt date, and shelf-life expiration date. Queue At TO creation time, transfer orders are assigned to different queues, thereby building workloads in those queues. To react in a flexible way to changes in workload or the available resources, you can change the assignment of the user to a queue.
© SAP AG
SCM631
5-10
Radio Frequency Screen Design Screen for all activities
Screen for putaway for putaway activities
SAP R/3 F8
SAP R/3 F2
F3
F4 F8
F2
F3
F4
1. Putaway Activities 1. Putaway Activities
2. Picking Activities 3. Inventory 4. Inquiry 5. Load Control
2. Inquiry
SAP R/3
F8
F2
F3
F4
3. Queue
6. Queue 1. Putaway Activities 2. Picking Activities 3. Inventory 4. Inquiry 5. Load Control 6. Queue
Picking Activities
Load Control Inventory SAP AG 2002
You can tailor the screens for the different activities, users, and queues to your needs. You customize this by the definition of the menu management in the Customizing of mobile data entry (in the IMG choose Logistics Execution → Mobile Data Entry → Define Menu Management ).
You can assign a specific transaction or menu to a dynamic menu, that is described by a text. Menus, in turn, are assigned to further menus or transactions.
For example, you define a main menu MAIN00 that contains five menus and one transaction. The menus are Putaway Activities, Picking Activities, Inventory, Inquiry, and Load Control; the transaction is called Queue and leads to transaction LM77. When you select Putaway Activities, you are taken to the next menu, which contains more menus or transactions.
You can customize the menus and transactions that occur for each user.
© SAP AG
SCM631
5-11
Putaway via Radio Frequency I SAP R/3
F8 - LOff
F2-Clr
F3 - Back F4 - Next
SAP R/3
1. Select by SU F2-Clr
2. Clustered
F3 - Back F4 - Next
3. Select by TO 4. System Guided
SU Barcode
10000001181
SAP AG 2002
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. There are different possibilities to define the activity, for example, the transfer order that is to be processed next.
The worker in the warehouse can scan the bar code of the transfer order and get the relevant information. Alternatively, the system can assign a transfer order to a worker by queue assignment.
If you have chosen system-guided management, the sorting of the transfer orders can be customized. The different possibilities to sort the sequence are: (blank): Sorting by TO number 1: Sorting by creation date 2: Sorting by priority of the transfer order 3: Sorting by a user-exit
© SAP AG
SCM631
5-12
Putaway via Radio Frequency II
SAP R/3 F8 - LOff
F2-Clr
F3 - Back F4 - Next
Destination Information Dest. Bin Dest. SU
008
01- 05 - 18
10000001181
Material Information
T-BW01-00
50 PC
SAP AG 2002
The user has to verify certain information for the confirmation of the transfer order. This could be the destination bin or the actual quantity. The identification of the scanned bin is compared to the information of the transfer order.
This verification can be defined individually for source and destination screens. The fields you can verify are:
Storage bins The scanned data for bin verification are checked against the value of the verification field in the storage bin master record. This field can be loaded with the bin name itself, or with something different. You can fill this field with a special transaction.
Storage unit number
Material ID This can be the SAP material number, the old material number from the material master record, or the EAN number.
Quantities
© SAP AG
SCM631
5-13
Radio Frequency: Queue Management
Goods receipt
TO #45
Fixed bin storage
Queue Goods receipt:
TO #46
TO #45 TO #46
High-rack storage TO #47
Queue Goods issue:
Goods issue
TO #47
SAP AG 2002
To organize the distribution of activities in the warehouse, you need to define queues that group similar activities. A queue that combines the activities for goods receipts can be defined and all related activities are assigned to this queue. Transfer orders for putaways are processed within this queue. Therefore, transfer orders and users are assigned to a queue.
Queues are necessary to coordinate the different RF activities in the warehouse. The view for each user at an RF terminal is limited to transfer orders of that user's current queue.
Queues can be defined for different activities, doors, and areas in the warehouse number. This enables high flexibility for the definition of different queues that coordinate the processing of transfer orders.
© SAP AG
SCM631
5-14
Radio Frequency Monitor
Queue Goods Receipt
Queue Goods Issue
TO #45
TO #46 TO #46 TO #45 TOTO #46#48
TO #46
User Joe Strummer
User Mick Jones TO #47 TO #51
T O# 48
T O# 4 6
SAP AG 2002
For the coordination of activities and users assigned to different queues, the central tool is the RF Monitor. It takes over the assignment of transfer orders created in the warehouse to queues. This assignment is based on the transfer type, and the source and destination data in the transfer order. You can also manage the workload and capacity of queues.
You can display the number of assigned transfer orders and users, as well as the ratio of users to the workload in any particular queue. Individual transfer orders can be sorted by creation date and time, with additional detailed information.
You can manually move transfer orders and users from one queue to another by dragging and dropping. This enables a quick and flexible response to unplanned situations.
It is possible to forward transfer orders from one queue to another. If there is no user available to process the transfer order, you can automatically forward the transfer order without manual movement.
The transfer priority of transfer orders can be changed and, as a result, the processing sequence can also be changed by that changed priority.
© SAP AG
SCM631
5-15
Interfaces: WM-LSR and MM-MOB
Interface scenarios for linking external software to SAP WMS
SAP AG 1999
© SAP AG
SCM631
5-16
Mobile Data Entry (MM-MOB) Functions
Stock placement (production, ordering)
Connection to scales
Stock removal (cost center, ...)
IM
Packaging of delivery items
SD Picking systems deliveries, picking quantities
Posting changes
Stock transfer
SAP AG 2003
Wenn Sie das WM nicht benutzen, k nnen Sie Lieferdaten direkt aus dem SD übertragen und die Rückmeldung von Kommissioniermengen senden. Sie k nnen Wareneing nge und -ausg nge, Umlagerungen und Umbuchungen über eine direkte Verbindung zur Bestandsführung bearbeiten.
© SAP AG
SCM631
5-17
Link to Warehouse Control Units (WM-LSR)
IM
SD WM
WCU
Administrative level
- Automatic Automatic storage storage retrieval retrieval system - Automati Automatic c fork lift lift system - Picking Picking system, system, carousel... carousel...
Physical control level
2002 SAP AG 2002
The warehouse control system might be an automatic storage or retrieval system, automatic forklift system, or picking system.
© SAP AG
SCM631
5-18
WM-LSR Function Functionality ality
WM Transfer order Transfer order Release reference number
Move storage units
Inventory bin location list
Cancellation of unconfirmed TO
Confirmation of transfer orders Transfer requirements
(Un)blocking
Cancellation request for transfer orders
bins
Inventory count data
WCU
2002 SAP AG 2002
Transactions can be processed between the WM system and the warehouse control unit (WCU) using IDocs.
© SAP AG
SCM631
5-19
Warehouse Control Control Unit with Mobile Data Entry
Packaging of delivery items
Connection to scales
IM
SD
Stock placement Stock removal
Stock transfer Posting change
Stock transfer in warehouse
Replenishment control
WM Inventory counting
WCU
Block bins in warehouse
2002 SAP AG 2002
When you are using the SAP WM system, you can manage warehouse activities with an external system via IDocs.
© SAP AG
SCM631
5-20
Scenario 1: Manual Warehouse
GR area
HRS
GI area
Bulk storage
WMS
Management of material stocks and storage bins Creation of stock placement/removal transfer orders Stock placement/stock removal strategies Inventory Execution of physical movements via fork lift TO in paper form or on the RF screen as information medium
SAP AG 2002
In the case of a manual warehouse, WM assumes full control over the management of the warehouse. In this case, a paper-based system can be used. Such a system can easily be supported by simple, wired barcode scanners for confirming the movements. This is an easy, efficient way to minimize data entry errors. This type of warehouse setup occurs frequently.
© SAP AG
SCM631
5-21
Scenario 2: Semi-Automated Warehouse
GR area
Shelf storage
GI area
WMS
WCU
Management of material stocks and storage bins Creation of stock placement/removal transfer orders Stock placement/removal strategies Control of automated storage/retrieval systems AS/RS Control of material flow Optimization of resources depending on extension level
SAP AG 2002
In a semi-automated warehouse, WM has full control over the management of the warehouse, and an external system has the responsibility of executing the movements.
A typical semi-automated system is an automated fork lift system, with fork lift mounted devices or a conveyor.
© SAP AG
SCM631
5-22
Scenario 3: Fully Automated Warehouse
HRS
GR area
GI area
K
I K
WMS
WCU
Management of material stocks and storage bins Creation of stock placement/removal transfer orders Stock placement/removal strategies Control of conveyor equipment Control of material flow Optimization of resources
SAP AG 2002
The external system assumes responsibility for warehouse control and, if necessary, a specific part of warehouse management.
In a fully automated warehouse, both the warehouse as a whole and the specifications of the automatic warehouse systems must be taken into consideration. Analysis of these factors allows you to determine how the functions can be distributed effectively between WM and an external system. There is no standard solution for distributing the functions. This analysis must be carried out separately for each individual customer, in accordance with the project in question.
© SAP AG
SCM631
5-23
Scenario 4: 'Black Box'
HRS
GR area
"Blackbox"
GI area
P
I P
WMS
WCU
Management of stock totals Creation of stock placement/removal transfer orders Management of material stock figures and storage bins ...
SAP AG 2002
In this example, WM manages the high rack storage area as a black box, and dummy storage bins are defined. SAP R/3 keeps inventory at a summary level.
The external system is to perform all warehouse functions and assume responsibility for warehouse management and warehouse control for a specific warehouse.
The quantity and reference data that is transferred during TO creation from WM to the WCU is primarily relevant for the external system.
© SAP AG
SCM631
5-24
Technical Overview MM-MOB/WM-LSR Transmit
Receive
Document creation
SAP
SAP
Document creation
ALE
ALE Receive IDoc and save in database
Communication IDoc
tRFC
tRFC
Receive IDoc and save in database
Processing
Preparation in IDocformat, buffering
SUB
Data creation
SUB
SAP AG 2002
On the external system side, a program in C or Visual Basic must be created. The program must be able to access functions in the RFC library.
SAP supports partners to certify the creation of interface programs.
The interface to external systems is a separate price list component that contains interfaces to other modules.
© SAP AG
SCM631
5-25
Example: Business Process for Stock Placement
Container arrival
Goods receipt with handheld device
Identification of pallet and putaway in high rack type
Palletization, via conveyer into warehouse
SAP AG 2002
This graphic shows a business process that we will analyze. The following graphics show some alternatives for executing this business process.
© SAP AG
SCM631
5-26
Solution 1: WMS Controls High Rack Storage
Physical
GR area
Goods Receipt + TO
Conveyer
(ID-point)
High Rack Storage
TO confirmed
2
WMS
GM
TO
Confirm
3 Sub
1
Identify
Putaway
SAP AG 2002
1. The container arrives. Scan the purchase order (PO) to post the goods movement. 2. SAP R/3 posts transfer order (TO) automatically. The destination bin is found by the placement strategy. The TO is sent to the subsystem. 3. The pallet is identified at the ID point, and the TO is confirmed and put away.
© SAP AG
SCM631
5-27
Solution 2: Subsystem Controls High Rack
Physical
GR area
Conveyer
ID-point
High Rack Storage
WMS managed
2
Goods Receipt + 1st TO
TO confirmed
GM
Confirm
2nd TO
WMS
Sub
TO
3
1
Identify
Move SU
4 Putaway
SAP AG 2002
1. The container arrives. Scan the PO to post Goods Movement. 2. SAP R/3 postings are done automatically, TO is sent to subsystem. 3. Pallet identified at ID point, TO confirmed and put away. 4. After putaway, send IDoc Move Storage Unit for second TO.
© SAP AG
SCM631
5-28
Solution 3: Subsystem as a 'Black Box'
Physical
GR area
Conveyer
ID-point
High Rack Storage
WMS-managed
2 WMS
Goods Receipt + TO
GM
TO confirmed
Confirm
TO
Sub
1
3 Identify
Putaway
SAP AG 2002
1. The container arrives. Scan the PO to post Goods Movement. 2. SAP R/3 postings are done automatically, and TO is sent to subsystem. 3. Pallet identified at ID point. TO confirmed and put away. The SAP R/3 System sees only stock in logical bins at the ID point.
© SAP AG
SCM631
5-29
Partner Concept
Customer SAP - Standard communication interface - Shorter installation time - Manageable interface projects - Release independent
- Knowledge transfer - Shorter installation - Wider range of functionality
Partner - Sales support through SAP - Product business at the interface - Certification partner for SAP
SAP AG 2002
Certification offers advantages for all partners: customers, manufacturers of interface software, and SAP.
SAP supports several different types of partners. The partnership program continues to expand, to bring valuable third-party solutions to meet customer requirements for a comprehensive solution.
For further reference, visit our Web site at www.sap.com. Select Partners, then Complementary Software.
© SAP AG
SCM631
5-30
Radio Frequency / LSR: Unit Summary
You are now able to:
Customize the Mobile Data Entry Screen
Activate the RF Monitor
Describe scenarios for linking WM to an automated Warehouse Control Unit
SAP AG 1999
© SAP AG
SCM631
5-31
© SAP AG
SCM631
5-32
Radio Frequency - Exercises Unit: Radio Frequency
At the conclusion of this exercise, you will be able to: •
Configure the radio frequency processing in the SAP Warehouse Management System.
•
Set up the verification control for RF transactions.
•
Define the menu management within RF transactions.
•
Define and configure queues and the RF Monitor.
In your warehouse, you use handheld terminals for paperfree communication. All transfer orders in the warehouse in the fixed bin area are processed via 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 co mpletely from the mobile devices. You receive material from a purchse order and process the the stock placement and the goods receipt posting from the RF transaction. You create the inbound delivery yourself..
1-1
For RF processing, you want to verify the storage bin where the worker places or removes the materials. Change the verification field of the storage bins in storage type 005 in your warehouse 1##. 1-1-1 The storage bins are named 400-## through 410-##. You do not want to verify the complete storage bin name but create a unique verification code for every bin. Create the verification field from the second and third characters of the bin name, for example bin 400-## has verification field 00. 1-1-2 Use the bin status report to display the changes. Display the verification fields using the ABAP List Viewer technique. 1-1-3 Assign material T-BW20-## to storage bin 402-## and material T-BW21-## to storage bin 405-##. Assign the putaway and stock removal type indicator FIX to the two materials because the storage type search sequence goes to storage type 005 first when this indicator is set.
© SAP AG
SCM631
5-33
1-2
For RF processing in the warehouse, you need to define the parameters regarding which data appears on the RF screens. When processing a TO 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. 1-2-1 Set a separate confirmation for material pick and transfer for your warehouse number 1##. 1-2-2 Set putaway and pick confirmation for the storage types 005 – Fixed Bin, 902 – GR Area External Receipts and 916 - Shipping Area Deliveries. 1-2-3 You find the confirmation control in Customizing of Warehouse Management.
2-1
Define the data you want to verify when processing a transfer order with RF. 2-1-1 Define two profiles, one for stock placement and one for stock removals in your warehouse 1##. For putaways, define profile IN1## with verification of destination bin and destination quantity. For removals, you want to use a profile OUT1## with verification of source bin and destination quantity. 2-1-2 Assign the verification profiles to the inbound and outbound movements. The respective movements are from the GR zone (storage type 902) to fixed bins (storage type 005) and from there to the shipping area for deliveries (storage type 916). The movement types are goods receipt purchase order (101) and GI for delivery (601).
2-2
Menu management defines the sequence of the screens on the RF terminal and the position and name of the pushbuttons. Copy the entries for the dynamic menu management from warehouse 001 to your warehouse 1##. 2-2-1 Name the default follow-up menus of the entry screen MAIN? 2-2-2 What are the follow-up transactions from the menu named PTWY01?
2-2-2 Since you do not use the storage unit or handling unit number for verification, you want to delete the transactions for selection by SU from the putaway menu PTWY01. Delete the transactions Select by SU and Clustered from the menu PTWY01 and move the remaining transactions to first, second and third position in this menu.
© SAP AG
SCM631
5-34
2-3
For the assignment of workload to workers in the warehouse, you want to use queues to organize the processes. Define different queues in your warehouse 1## for inbound and for outbound processing. You want to have different processors for inbound and outbound movements. 2-3-1 Define the queue GR001 – GR to fixed bin in your warehouse 1##. Also, define an outbound queue GI001 – GI fixed bin . 2-3-2 With a movement concerning storage type 005, the TO has to be processed in the appropriate queue. Assign the areas and the activities.
Set the values for source storage section, destination storage section and door to ***.
2-3-3 Assign your user LO531-## to the inbound queue. Set the user to Active. Specify the default values for logging on, since there is the presentation screen 8X40 and the default menu MAIN .
© SAP AG
SCM631
5-35
3-1
Test the configuration you just have set up. 3-1-1 Open another session with the RF monitor and run it for your warehouse 1##. Which queue are you assigned to? Keep the RF monitor in the separate session. 3-1-2 Create a purchase order with the following data. Set the confirmation control key on the line item detail to Inbound delivery. Order type: Standard purchase order Vendor: 1000 Organizational data: Purchasing organization: IDES Germany 1000 Purchasing group: 001 Company code: 1000 Item data: Material: T-BW20-## Quantity: 100 PC Delivery date: today Plant: 1000 Storage Location: 01## Material: T-BW21-## Quantity: 200 PC Delivery date: today Plant: 1000 Storage location: 01## Line item data: Confirmation control: Inbound delivery
3-1-3 Create an inbound delivery manually for this PO.
© SAP AG
SCM631
5-36
3-2
You now want to process the goods receipt for inbound delivery with the RF transaction. At first, you have to create the TO for placement and process the putaway. Finally, you post goods receipt for the inbound delivery. 3-2-1 Enter the mobile data entry screen. Navigate to the goods receipt screen for inbound deliveries. Enter your inbound delivery number you just created and create a transfer order for the putaway.
The navigation through the screen works with F1 to save, F4 to continue and F3 to go back. To create a TO, press F8 - G.TO.
Do not leave the screen after you created the transfer order. 3-2-2 Switch to the RF monitor. Which queue is the TO assigned to? How many pallets have to be moved? Display the TO and check the source and destination data. 3-2-3 Return to the session with the RF screen. Process the putaway to the destination bins. Finally, post goods receipt for the inbound delivery.
Press F6 – TO ex to process the TO and use F1 – Post
3-2-4 Switch to the RF monitor. Is the TO still there? Also, check the inbound delivery and display the goods movement status.
© SAP AG
SCM631
5-37
Optional Exercise:
4-1*
You want to add a new menu to the goods issue menu OUT00. This menu only consists of two transactions for picking. Finally, test it with an outbound delivery. 4-1-1 Define a new menu PKG## and add it to the dynamic menu OUT00 in your warehouse. The new menu consists of the two transactions LM06 Picking by delivery and LM12 – Inquiry for Material . Change the description and the short text to an appropriate description you like. 4-1-2 Create an outbound delivery without reference for 5 pieces of material TBW21-##. Shipping point is 1000, sales area 1000/10/00. The ship-to party is 1400, goods issue date 1 week from today. Create the TO. 4-1-3 Switch to the RF screen and process the transfer order. Are you able to process the TO? Why? 4-1-4 Change the queue you are assigned to to the queue that allows you to process the TO.
You can either change this assignment in the RF monitor or change it on the RF screen starting from the entry screen in the Internal Warehouse Processes.
4-1-5 Process the TO and finally post goods issue.
© SAP AG
SCM631
5-38
Radio Frequency - Solutions Unit: Radio Frequency
1-1
Master Data Logistics Change
Logistics Execution Master Data Verification Field Selection
Warehouse
Storage Bin
1-1-1 Partially fill the verification field for all bins. You want to adopt the second and third coordinates as the first and second ve rification fields. Field Name or Data Type
Values
Warehouse
1##
Storage Type
005
Adopt bin coordinate partially
Select
Second Field
1
Third Field
2
Press Execute and then Update. Logistics Execution Internal Warehouse Processes 1-1-2 Logistics and stocks Display Bin Status Report
Bins
Change the current display variant and add the verification field to the variant. 1-1-3 Create the material master WM views for T-BW20-## and T-BW21-## for warehouse 1## and storage type 005. Assign the type indicator and enter the storage bins as the fixed bins for these materials. 1-2
Confirmation control Tools Accelerated SAP Customizing SAP Reference IMG Logistics Execution Warehouse Management Activities Confirmation Define Differences Control
1-2-1 Press Warehouse Number and set Separate Confirmation for your warehouse 1##. 1-2-2 Press Storage Type and set Confirmation Placement and Confirmation Removal for storage types 005, 902, and 916. © SAP AG
SCM631
5-39
2-1
Verification Tools Accelerated SAP Customizing SAP Reference IMG Execution Mobile Data Entry Define Profiles
Logistics
2-1-1 Make a new entry and enter the following data. Field Name or Data Type
Values
Warehouse
1##
Profile
IN1##
Destination Bin
Select
Destination Quantity
Select
Profile
OUT1##
Source Bin
Select
Destination Quantity
Select
Save your entries. Accelerated SAP Customizing 2-1-2 Tools Logistics Execution Mobile Data Entry Goods Movements
SAP Reference IMG Assign Verification Profiles to
Make a new entry and enter the following data. Field Name or Data Type
Values
Warehouse
1##
Source Type
902
Destination Type
005
Movement Type
101
Source Type
005
Destination Type
916
Movement Type
601
Save your entries.
© SAP AG
SCM631
5-40
2-2
Menu Management Tools Accelerated SAP Customizing SAP Reference IMG Execution Mobile Data Entry Define Menu Management
Logistics
2-2-1 By default, the entries are: MAIN 1
Goods Receipt Process
MAIN 2
Outbound Process
MAIN 3
Stock transfer
MAIN 4
Internal Warehouse Processes
MAIN 5
Inquiries
2-2-2 By default, the entries are: PTWY01
1
Putaway by Storage Unit
PTWY01
2
Clustered Putaway
PTWY01
3
Putaway by Transfer Order
PTWY01
4
Putaway by Delivery
PTWY01
5
System-Guided Putaway
2-2-3 Delete the entry PTWY01 1 and PTWY01 2 for your warehouse 1##. Change the entry for Putaway by TO, Putaway by delivery and System-guided Putaway to sequence 1, 2, and 3. 2-3
Definition of Queues Tools Accelerated SAP Customizing SAP Reference IMG Execution Mobile Data Entry RF Queue Management
Logistics
2-3-1 Define two new queues. Field Name or Data Type
Values
Warehouse
1##
Queue
GR001
Queue Name
GR to fixed bin
Queue
GI001
Queue Name
GI fixed bin
Save your entries.
© SAP AG
SCM631
5-41
2-3-2 Assign Areas and activities to queues. Field Name or Data Type
Values
Warehouse
1##
Screen
Preparation for Placement
Transportation Type
E
Source Storage Type
902
Source Storage Area
***
Destination Storage Type
005
Destination Storage Area
***
Door
***
Queue
GR001
Warehouse
1##
Screen
Preparation for Removal
Transportation Type
A
Source Storage Type
005
Source Storage Area
***
Destination Storage Type
916
Destination Storage Area
***
Door
***
Queue
GI001
Save your entries.
2-3-3 Assign Processor to Queues.
© SAP AG
Field Name or Data Type
Values
Warehouse
1##
User
LO531-##
Queue
GR001
Status
Select
Screen format
8X40
Main Menu
MAIN00
SCM631
5-42
3-1
Test of Configuration Logistics Execution Execution 3-1-1 Logistics Monitor Mobile Mobile Data Entry Entry
Internal Warehouse Warehouse Processes Processes
You are currently assigned to queue GR001. GR001. Materials Management Purchasing Purchasing 3-1-2 Logistics Create Vendor/ Supplying Plant Known
Purchase Order
Field Name or Data Type
Values
Vendor
1000
Purchasing Organization
1000
Purchasing Group
001
Company Code
1000
Material
T-BW20-##
Quantity
100
Material
T-BW21-##
Quantity
200
Delivery Date
One week from today
Plant
1000
Storage Location
01##
Confirmation control
Inbound delivery
Save. Logistics Execution Execution Inbound Process Process Goods Receipt Receipt for 3-1-3 Logistik Inbound Delivery Delivery Inbound Delivery Delivery Create Single Documents Documents Enter your purchase order number and choose Enter. choose Enter. Save your inbound delivery.
3-2
RF Processing of the Goods receipt Logistics Execution Execution Internal Whse Whse Processes Processes Mobile Data 3-2-1 Logistics Entry Press F1 Press F1 – Save to Save to logon to the RF Screens. Press Inbound Press Inbound Process Goods Goods Receipt GR GR by delivery. Enter the inbound delivery number and press F4 press F4 Next . . Press F8 Press F8 - G TO and TO and confirm the information message to generate a transfer order.
© SAP AG
SCM631
5-43
3-2-2 Switch to the RF monitor monitor and double click on the TO that you just just created. There are 3 pallets to be moved and the TO is assigned to the inbound queue GR001. GR001. 3-2-3 Press F6 to execute the TO. You have to confirm the removal of the pallet from from the source bin with F1 and press F4 to get to the destination bin. When you confirm the transfer to the destination bin, you have to verify the bin with the verification field and the quantity that you transferred. Finally, post goods receipt for the inbound delivery by pressing F1. 3-2-4 The TO is is finally processed and does not occur in the RF monitor anymore. 4-1*
Optional Exercise for Goods Issue Accelerated SAP Customizing 4-1-1 Tools Logistics Execution Execution Mobile Data Entry
SAP Reference IMG Define Menu Menu Management Management
Press New Press New Entry and Entry and add two new entries named PKG## for your warehouse 1##. The menu/transaction type is 2 for transactions, the two transactions are LM06 - Picking by delivery and delivery and LM12 LM12 - Inquiry for Material . Make another new entry for the menu OUT00 with sequence number 4 and assign the new menu PKG##. Name the menu Picking for group ##. Save your new entries. 4-1-2 Logistics Logistics Execution Execution Outbound Process Goods Issue Issue for Outbound delivery Outbound delivery Create Single Document Without reference to a Sales Order. Enter shipping point 1000, delivery type LO and sales area 1000/10/00. Choose Enter and and enter goods recipient 1400 and material T-BW21-## with a quantity of 5 pieces. Select Subsequent functions Create Transfer Order to to create a TO. Logistics Execution Execution Warehouse Warehouse Internal Processes Mobile 4-1-3 Logistics Data Entry Press F1 to logon and navigate to your new menu. You are not able to process the TO because you are currently assigned to the inbound queue.
4-1-4 Switch to the session with your RF monitor and change the assignment by drag and drop. Alternatively, you can change your assignment to a particular queue in the RF transaction with Internal with Internal Warehouse Processes Queue Queue Change. Change. Logistics Execution Execution Outbound Process Goods Issue Issue for 4-1-5 Logistics Outbound Delivery Post Goods Issue Outbound delivery single document
Enter your outbound delivery number and press post goods issue.
© SAP AG
SCM631
5-44
Decentralized Decentraliz ed Warehouse Management
SAP AG 1999
© SAP AG
SCM631
6-1
Decentralized WM: Overview Diagram
Course Overview Storage Unit Management Hazardous Materials Management Additional Functions in TO Processing Radio Frequency / LSR Decentralized Warehouse Management
Technical Topics Summary
SAP AG 2003
© SAP AG
SCM631
6-2
Decentralized WM: Unit Objectives
Upon conclusion of this unit, you will be able to:
Describe the purpose of a decentralized warehouse management system.
Describe the procedure of stock placements and stock removals with inbound and outbound deliveries.
SAP AG 1999
© SAP AG
SCM631
6-3
Decentralized WM: Business Scenario
In your company, you want to separate the warehouse processes from the central processes, to make the warehouse processes run independently from the core system. Your warehouse processes include processes for inbound and outbound deliveries.
You want to evaluate the Decentralized Warehouse Management System within SAP LES.
SAP AG 2002
© SAP AG
SCM631
6-4
Distributed Functionality
Accounting • Controlling • Sales • Purchasing • Inventory Management • Production Planning • ATP • Credit Limit Check • Foreign Trade •
• • • •
BAPI
• • • • •
Inbound Delivery Goods Receipt Putaways Stock Movements Picking Goods Issue Outbound Delivery Warehouse Structure Planning/Monitoring
SAP AG 2002
An enterprise resource planning (ERP) system processes all partial processes that are a preparation or a subsequent processing of activities in the warehouse. These include the creation of sales or purchasing documents for different checks and subsequent invoice handling.
The Warehouse Management system (WMS) includes functions that handle warehouse processes. These functions include planning aspects, goods receipt, storing and goods issue, and monitoring warehouse activities.
Communication between ERP and WMS takes place through Business Application Programming Interfaces (BAPIs).
© SAP AG
SCM631
6-5
Overview of Processes
Sales Order Outbound Delivery
Purchase Order BAPI Replication
In-/Outbound Delivery
BAPI Replication
Inbound Delivery
Transfer Order
ERP
ERP Confirmation TO
BAPI
Goods Issue Confirmation
Invoice
BAPI
Posting of goods movement
WMS
Goods Receipt Confirmation
Invoice
SAP AG 2002
For incoming as well as outgoing processes, the inbound or outbound delivery serves as a basis for activities in the warehouse. The delivery is created for a sales order or a purchase order. During creation of a delivery, the system establishes whether it is relevant for distribution (see note below). If it is, a BAPI is called when the delivery is saved. This BAPI starts the creation of an intermediate document (IDoc) and sends the delivery to the WMS. There, replication of the delivery is done. This replication serves as a basis f or subsequent processes in the warehouse, such as creation and confirmation of transfer orders, printing shipping documents, and posting goods movements.
Posting the goods issue (or goods receipt) clears the interim storage bin and calls a BAPI. This BAPI confirms to the ERP system the data that was created or changed in the WMS (such as, quantities, weight, packaging, and batches).
When the confirmation is received in the ERP system, the goods movement is executed in Inventory Management.
Note:
The delivery is only relevant for distribution when all delivery items match in plant and storage location, and the combination of plant and storage location is allocated to a warehouse number. The warehouse number carries the information about a decentralized warehouse management system. To use this function, you have to use the delivery split by warehouse number. A delivery can be distributed only if all items are determined for this warehouse.
© SAP AG
SCM631
6-6
Connection to Several ERP Systems
Decentralized WMS
ERP 1
ERP 2
ERP n
SAP AG 2003
The following prerequisites must be fulfilled if you connect several ERP systems to a decentralized WMS:
Unique numbers for master data in decentralized WMS. The various customer master records, vendor master records, and material master records from the various ERP systems must have unique numbers so that a master records can always be read clearly in the decentralized WMS.
Unique numbers for organizational units in decentralized WMS. The various plants and storage locations must have unique numbers in the decentralized WMS.
Unique delivery numbers in the decentralized WMS. In the decentralized WMS, the deliveries from the various ERP systems must be unique. Make sure that on replication of the deliveries, they are unique in the decentralized system. (If the same delivery numbers come from several ERP systems, you can use customer exit V50S0001 and function module EXIT_SAPLV50S_001 to reassign the numbers. In this way, you can ensure that the delivery numbers in the decentralized system are unique.)
© SAP AG
SCM631
6-7
Subsequent Changes to the Delivery
ERP system Delivery Delivery
BAPI
1.
Unblock, Change, block
Change delivery?
Request Synch. RFC
2.
BAPI Changeable
Process
Delivery
4.
3.
Change delivery
Delivery Delivery
Decentralized WMS
SAP AG 2003
In inbound and outbound deliveries, you can change certain data after the deliveries have been distributed from the central ERP system to the decentralized Warehouse Management system (WMS). You can make this kind of change either in the central system or in the decentralized system.
© SAP AG
SCM631
6-8
Inventory Postings
Posting
Record IM Posting
1 2
Create delivery Distribute to WMS Physical stock movement Confirm to ERP Execute IM Posting SAP AG 2002
In contrast with the integrated scenario, inventory postings in the ERP system are not posted immediately. With the creation of the IM posting, an inbound or outbound delivery is created and communicated to the WMS (in the same way as a delivery for a sales order or for a purchase order). With the confirmation of the delivery from the WMS, the posting in Inventory Management is executed automatically.
To make this scenario possible, adjustments are required in Customizing for the warehouse number and for the reference movement type needed for the creation of the delivery.
Stock movements are possible where material is moved out of or into WMS. Posting changes (for example, material X to material Y) are not yet possible.
Stock movements are possible only in two steps; one-step movements are not possible in this scenario.
© SAP AG
SCM631
6-9
Delivery as an Interface
Distribution Status
Not relevant A
Relevant
B
Distributed
C
Confirmed
SAP AG 2002
In the decentralized scenario, the delivery is the main means of communication between the systems.
To reconstruct the status of the inbound or outbound delivery in the ERP system, a distribution status is used. This status indicates whether there is a decentralized scenario. If this is the case, the status indicates whether the delivery is relevant for distribution, distributed, or already confirmed by the WMS.
If the delivery has the status relevant , it can be changed (as long as a combination of plant/storage location is found in the header that is linked to a decentralized warehouse). When the delivery is saved, the distribution to the decentralized system takes place.
An ERP delivery with the status distributed can be changed to a limited degree only. The delivery can be changed in the WMS only.
With the goods movements postings in the WMS delivery, there is an automatic confirmation to the ERP system where the goods movements are executed in Inventory Management. To record this step, the distribution status is set to confirmed and the goods movement status is set to Completely processed . After this, invoicing can be processed.
© SAP AG
SCM631
6-10
Item Reference of the WMS Delivery
Sales Order
Purchase Oder
M1 M2
Purchase Order
Item Reference Data (for Purchase Order)
M1 M2
1 Pc 10 Pc
ERP
10 Pc 30 Pc
Sales Order
Delivery
Delivery
M1 M2
M1 M2
10 Pc 30 Pc
WMS
10 Pc 30 Pc
Item Reference Data (for Sales Order)
Outbound Delivery
Inbound Delivery
SAP AG 2002
Deliveries in the ERP system are usually created with reference to a purchase order or sales order. This reference gets lost when the delivery is sent to the WMS because the previous documents are not distributed. A delivery item reference provides information about the previous documents using selected data from the purchase order or the sales order that is relevant for the WMS.
The document flow to the previous document is not visible in the WMS.
© SAP AG
SCM631
6-11
Distribution Model
Material
Classification
Vendor
Material
Classification
Lieferung
M1 M2
Customer
Vendor
Lieferung
10 ST 30 ST
M1 M2
Delivery
Customer
10 ST 30 ST
Delivery
A B
Inventory Posting
Lieferung
M1 M2
Inventory Posting
Batch
10 ST 30 ST
Confirmation
Lieferung
Batch M1 M2
10 ST 30 ST
Confirmation
ERP
WMS
SAP AG 2002
The communication between the two systems takes place asynchronously. In certain scenarios (for example, the generation of the distribution model and possible stock comparisons), direct communication is set up. To enable this communication, a distribution model must be generated that contains all objects for the information flow.
In the IMG, there is a tool that enables you to maintain a distribution scenario. All objects are available that are sent or received by the systems. The distribution model is generated for an already existing warehouse number, and sets up the basis to communicate different information with the decentralized WMS. The objects that are to be distributed are made up from master data and application data.
The distribution differs in each installation. Therefore, you should create your own message types (for example, material master, vendor master and customer master records). Customer master record and material master records have to be distributed, whereas vendor master records and classification depend on the necessity in their decentralized system. In principle, only the required master data should be distributed, so that the WMS can work efficiently. Data that has only local significance is maintained in the WMS (for example, Warehouse Management Views in the material master).
Distribution of master data and application data from the ERP to the WMS: material master, customer master, vendor master, classification, inbound delivery, outbound delivery
Distribution of master data and application data from the WMS to the ERP: batches master, confirmation inbound delivery, confirmation outbound delivery, inventory postings
© SAP AG
SCM631
6-12
Distribution Model: Procedure
Define Define Message Message Types Types
Generate Generate Distribution DistributionModel Model
Generate Generate Addresses Addresses (optional) (optional)
Generate Generate Partner Partner Profile Profile
ERP Distribute Distribute Model Model to to WMS WMS
WMS Generate Generate Partner PartnerProfile Profile
SAP AG 2002
Before generation of the distribution model, the reduced message types for material master, customer master, and vendor master must be created.
Also, logical systems must be defined for both the ERP system and the WMS.
After this, you can start the generation per warehouse number. You have the option of using filters to distribute only certain views of the material or customer master. This can be useful if the material master is maintained for different organizational units, but data in the WMS is only needed for one organizational unit.
If you need the address file, the distribution of the addresses is intended as an independent object. Therefore, you have a separate generation function on the final screen of the generation of the WMS distribution. After the generation, it is possible to generate the necessary partner profiles for all messages and methods in the created model view.
Afterwards, the model view can be introduced to the WMS. The distribution model itself is sent to the WMS. With this step, the communication channels are known in the WMS.
Finally, generate the partner profiles in the WMS.
Note:
Depending on whether both systems are provided by SAP, the distribution model is to be generated only (in SAP R/3) or to be generated in the ERP system and then distributed (when both systems are provided by SAP).
© SAP AG
SCM631
6-13
Decentralized WM: Unit Summary
You are now able to:
Describe the purpose of a decentralized warehouse management system.
Describe the procedure of stock placements and stock removals with inbound and outbound deliveries.
SAP AG 1999
© SAP AG
SCM631
6-14
Technical Topics
Archiving
User Exits
Function Modules
SAP AG 1999
© SAP AG
SCM631
7-1
Technical Topics: Overview Diagram
Course Overview Storage Unit Management Hazardous Materials Management Additional Functions in TO Processing Radio Frequency / LSR Decentralized Warehouse Management Technical Topics
Summary
SAP AG 2003
© SAP AG
SCM631
7-2
Technical Topics: Objectives
At the conclusion of this unit, you will be able to:
Outline the archiving process and locate the programs required for archiving data
Discuss user exits and function modules, and locate the supplied programs that help you make customer-specific enhancements in your system
SAP AG 2002
© SAP AG
SCM631
7-3
Technical Topics: Business Scenario
You are responsible for communicating the special needs of the warehouse, including programs for archiving and customer-specific enhancements.
SAP AG 2002
© SAP AG
SCM631
7-4
Archiving Programs
Posting Change Notices
Transfer Orders
Archive Read Archives Delete Archives
Archive Read Archives Delete Archives
Transfer Requirements
Archive Read Archives Delete Archives
Inventory History Records
Inventory Records
Archive Read Archives Delete Archives
Archive Read Archives Delete Archives
SAP AG 2003
Tranfer requirements:
Transfer orders:
Posting change notices:
Inventory records
Inventory History Records
© SAP AG
RLREOB00
Archives TRs
RLREOB10
Deletes archived TRs
RLRB0001
Report for reading archived TRs
RLREOT00
Archives TOs
RLREOT10
Deletes archived TOs
RLRT0001
Report for reading archived TOs
RLREOU00
Archives PCNs
RLREOU10
Deletes archived PCNs
RLRU0001
Report for reading archived PCNs
RLREOI00
Archives inventory records
RLREOI10
Deletes inventory records
RLRI0001
Report for reading archived inventory records
RLREOH00
Archives inventory history records
RLREOH10
Deletes inventory history records
RLRH0001
Report for reading archived inventory history records SCM631
7-5
Function Modules
Function Module Create transfer requirement Change transfer requirement Create transfer order Confirm transfer order Cancel transfer order Create multiple processing list Start multiple processing run Release multiple processing list
SAP AG 1999
You can use function modules to replace a series of existing batch-input processes that are used in the WM system.
You can use these modules to combine different transactions on one screen or to expand the current functions of your system to meet the particular requirements in your organization.
For further information on function modules, refer to the WinHelp documentation for Warehouse Management.
For a detailed description of these processes, refer to the online documentation for the individual function modules.
© SAP AG
SCM631
7-6
User Exits
User Exit Update own data by creating transfer orders Update own data by confirming transfer orders Own stock placement strategy Own stock removal strategy Under and overdeliveries Palletization Conversion of storage unit numbers Interface to external systems
SAP AG 2002
Using customer-specified logic, user exits permit you to become involved in the storage bin search process. Afterwards, you can update customer data when creating and confirming transfer orders.
When you create customer-specific projects using this function, you can display additional SAP R/3 system information about each individual user exit.
You will find a complete list of the user exists available in the WM system in the WinHelp documentation. For a detailed description of these processes, refer to the online documentation of the individual user exits in transaction SMOD/CMOD.
© SAP AG
SCM631
7-7
Technical Topics: Summary
You are now able to:
Outline the archiving process and locate the programs required for archiving data
Discuss user exits and function modules, and locate the supplied programs that help you make customer-specific enhancements in your system
SAP AG 2002
© SAP AG
SCM631
7-8
Summary
Course Overview Storage Unit Management Hazardous Materials Management Additional Additional Functions Functions in in TO Processing Radio Frequency / LSR Decentralized Warehouse Management Technical Topics Summary
SAP AG 2003
© SAP AG
SCM631
8-1
Objectives
You are now able to:
Perform WM functions such as customizing Storage Unit Management, Radio Frequency, and Hazardous Material Management.
Discuss customizing options and settings within the Warehouse Management system for Handling Unit Management, decentralized Warehouse Management, and Performance Data.
SAP AG 2003
© SAP AG
SCM631
8-2
Follow-Up Courses
SCM610 Delivery Processes
SCM611 Transportation
SCM650 Cross-Functional Customizing in SD
SAP AG 2003
© SAP AG
SCM631
8-3
