SAP Extend ed Wareho us e Managem ent (SA P EWM)
Re leas e 510
 .    S    P    L _
   S    C    M _
Copyright
© Copyright 2007 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.
 Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
 
Icons in Body Text
Caution
Example
Note
Recommendation
Syntax
 Additional icons are used in SAP Library documentation to help you identify different types of
information at a glance. For more information, seeHelp on Help → General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.
Typographic Conventions
Type Style Description
Example text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.
Cross-references to other documentation.
Example text Emphasized words or phrases in body text, graphic titles, and table titles.
EXAMPLE TEXT Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.
Exampl e t ext Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.
Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.
<Example text> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.
 
SAP Extended Warehouse Management (SAP EWM)...........................................................19 
Warehouse Structure...........................................................................................................21 
Using the Refresh Rate ................................................................................................76 
Make Browser Settings for the Easy Graphics Framework..........................................79 
Delivery Processing .............................................................................................................80 
Inbound Delivery...........................................................................................................88 
Menu Paths and Customizing Paths for Delivery Processing ....................................108 
Warehouse Request.......................................................................................................109 
Creating a Warehouse Request for an Inbound Delivery.......................................113 
Generation of a Warehouse Request for an Outbound Delivery Order..................116 
Using Inactive and Active Document Versions .......................................................119 
Warehouse Request for Internal Stock Transfer ........................................................122 
Internal Stock Transfers..........................................................................................123 
Performing Scrapping .............................................................................................130 
HU Integration in Delivery Processing........................................................................136 
User Interfaces in Delivery Processing.......................................................................138 
Printer Determination in Delivery Processing.............................................................141 
Delivery Split for Inbound Deliveries...........................................................................154 
Delivery Split for Outbound Deliveries........................................................................156 
Process Management and Control .............................................................................160 
Processing of Non-Picking-Relevant Delivery Items..................................................162 
Processing of Non-Putaway-Relevant Delivery Items................................................164 
Processing of Packaging Items ..................................................................................165 
Fulfilling Immediate Deliveries with Direct Outbound Delivery Orders.......................172 
Scrapping Using a Direct Outbound Delivery Order...................................................175 
 Availability Check........................................................................................................176 
Generate Inbound Delivery from Expected Goods Receipt .......................................187 
Generate Inbound Delivery Item from Expected Goods Receipt ...............................189 
Goods Receipt Posting from Production........................................................................191 
Connection of Delivery Processing to Additional Functions...........................................198 
Connection of Delivery Processing to Yard Management..........................................199 
Connection of Delivery Processing to Transportation Management ..........................201 
Route Determination in the Delivery...........................................................................202 
Executing Automatic Route Determination .............................................................207 
Route Determination on the User Interface ............................................................211 
Connection of Delivery Processing to Serial Numbers...............................................213 
Connection to SAP Global Trade Services (SAP GTS) .............................................214 
Connection of Delivery Processing to Transit Procedure .......................................215 
Transit Procedure for Inbound Deliveries............................................................216 
Transit Procedure for Outbound Deliveries.........................................................218 
Connection of Deliv. Proc. to the Customs Warehousing Procedure .....................221 
Connection of Delivery Processing to Checks in SAP GTS ...................................222 
Connection of Deliv. Processing to Determining Country of Origin............................224 
Connection of Delivery Processing to Post Processing Framework ..........................226 
Configuration of PPF Action Scheduling.................................................................227 
 
SAP Extended Warehouse Management (SAP EWM) 510 7
 Automatic Generation of a VAS Order for the Warehouse Request Item ..............231 
Updating the Warehouse Request Using the VAS Order .......................................232 
Updating the VAS Order Using the Warehouse Request .......................................233 
Kit in the Warehouse Request for the Outbound Delivery Order ...............................234 
Outbound Delivery Split for Kits..............................................................................236 
Delivery Quantity Correlation for Kits......................................................................238 
Integration of Delivery Processing with Pickup...........................................................246 
Communication from EWM to the ERP System.............................................................248 
Processing of Inbound Deliveries...............................................................................251 
Functional Enhancement Through Business Add-Ins (BAdIs) ...................................260 
Data Enhancement for Warehouse Requests............................................................261 
Updating the Inbound Delivery in the GR Process .................................................271 
Layout-Oriented Storage Control................................................................................275 
Update of Results in Product Master..........................................................................280 
Update Attribute Storage Bin Improvable ...............................................................281 
Consideration of Storage Types.................................................................................282 
Simulation of Slotting..................................................................................................286 
Counting .........................................................................................................................295 
Deconsolidation..............................................................................................................298 
Putaway..........................................................................................................................300 
Putaway Using Radio Frequency ...............................................................................306 
Manual Assembly of Warehouse Orders....................................................................309 
Stock Removal Path Determination............................................................................321 
Partial Picking .........................................................................................................325 
Pick Denial ..............................................................................................................327 
Cancellation of Picking............................................................................................329 
Updating the Outbound Delivery Order in the GI Process......................................339 
Layout-Oriented Storage Control................................................................................340 
Replenishment Control...................................................................................................346 
Kit to Order .....................................................................................................................349 
Kitting at a Work Center with a VAS Order.................................................................353 
VAS Order for the Kit Header Item of the Warehouse Request .............................356 
Kitting at a Work Center Without a VAS Order...........................................................358 
Kitting During Picking Without a VAS Order...............................................................360 
Packing at the Work Center ...........................................................................................362 
Scrapping .......................................................................................................................366 
Putaway and Stock Removal Strategies............................................................................374 
Strategy: Near Fixed Picking Bin................................................................................382 
Example: Optional HU Check When Creating a WT ..............................................386 
Strategy: Bulk Storage................................................................................................387 
Cross-Line Stock Putaway..........................................................................................390 
Examples of Capacity Check in Accordance with Capacity Key Figure .................394 
Stock Removal Strategies..............................................................................................396 
Strategy: Stringent FIFO Across All Storage Types ...................................................398 
Strategy: LIFO (Last In, First Out) ..............................................................................399 
Strategy: Partial Quantities First.................................................................................400 
Strategy: Shelf Life Expiration Date............................................................................403 
Determination of Priority for Inbound Deliveries.............................................................414 
 Ad Hoc Movement..........................................................................................................415 
Limit Values for Warehouse Order Creation Rules........................................................425 
Printing Warehouse Orders and Warehouse Tasks.......................................................426 
Manual Assembly of Warehouse Orders .......................................................................429 
Interface Between EWM and Non-SAP Systems...........................................................431 
Scenarios for Connecting Non-SAP Systems ............................................................432 
Connecting a Semi-Automated Warehouse............................................................433 
Connecting a Fully Automated Warehouse as a Black Box ...................................442 
Data Flow: EWM Transmits Data ...............................................................................445 
Managing TCP/IP Settings......................................................................................448 
Data Formatting..........................................................................................................454 
Description of the IDocs..............................................................................................459 
IDoc for Confirming Warehouse Tasks...................................................................466 
IDoc for Releasing Waves.......................................................................................472 
IDoc for Stock Movement with HUs ........................................................................475 
IDoc Error Processing.................................................................................................477 
Modification Options ...................................................................................................483 
Handling Unit (HU).............................................................................................................490 
SSCC Number Assignment According to EAN128 ....................................................505 
Packing at the Work Center ...........................................................................................506 
 Automatic Packing in the Inbound Delivery....................................................................510 
Packing During Warehouse Task Confirmation. ............................................................511 
Deconsolidation Using Radio Frequency .......................................................................512 
Usage of Stock Identification..........................................................................................521 
Stock Identification When Splitting Stock in the GR Process ........................................524 
Stock Identification When Splitting Stock in the GI Process..........................................526 
Value-Added Services (VAS).............................................................................................527 
VAS Order ......................................................................................................................528 
Goods Issue Process with VAS Order ...........................................................................533 
Create and Edit VAS Orders ..........................................................................................536 
 
Processing a VAS Order ................................................................................................538 
 Auxiliary Product Consumption Posting .........................................................................542 
Detailed Process Description......................................................................................555 
Example Scenario for PD/PFGR with Storage Control ..............................................564 
 Additional Functions in Cross-Docking ..........................................................................568 
Business Add-Ins in Cross-Docking ...........................................................................569 
Serial Number ....................................................................................................................571 
Making Settings for Serial Numbers (ERP System and EWM) ..................................579 
Serial Numbers for Document Items ..........................................................................581 
Serial Numbers at Warehouse Number Level............................................................583 
Serial Numbers in Inventory Management .................................................................585 
Entering and Editing Serial Numbers.............................................................................587 
Integration of the Serial Number in the Delivery .....................................................592 
Warehouse Task Creation with Reference to a Warehouse Request........................595 
Using Serial Numbers in a Warehouse Task..............................................................597 
Specifying Serial Numbers for Warehouse Task Creation .........................................599 
Confirming Warehouse Tasks with Predetermined Serial Numbers ..........................601 
Using Serial Numbers in the Work Center..................................................................602 
Using Serial Numbers in the Warehouse Management Monitor ................................604 
Using Serial Numbers in an RF Environment.............................................................605 
Shipping and Receiving .....................................................................................................607 
Loading and Unloading ..................................................................................................608 
Vehicle............................................................................................................................612 
 Assignment of Deliveries to Vehicles and TUs ..............................................................617 
Printer and Form Determination in Shipping and Receiving ..........................................618 
Yard Management..........................................................................................................619 
Yard ............................................................................................................................621 
Checkpoint..................................................................................................................622 
Printer and Form Determination in Transportation Management...............................636 
 Authorizations in Transportation Management...........................................................637 
General Transportation Cost Profile ...........................................................................649 
Static Route Determination.........................................................................................653 
Scheduling ..................................................................................................................656 
Labor Management (LM) ...................................................................................................685 
Processor....................................................................................................................689 
Formula and Condition Editor.....................................................................................691 
Indirect Labor Tasks Using Radio Frequency ............................................................701 
Function Key Settings for Indirect Labor Tasks in the RF Environment .................702 
Engineered Labor Standards .........................................................................................704 
Planned and Executed Workload...................................................................................713 
Labor Management (LM) in the Warehouse Management Monitor............................720 
Preprocessing ................................................................................................................722 
BAdIs for Preprocessing.............................................................................................727 
 Analytical Functions ...........................................................................................................739 
Warehouse Order Selection .......................................................................................757 
Warehouse Order Prioritization...............................................................................761 
Deconsolidation Using Radio Frequency ...................................................................799 
Putaway Using Radio Frequency ...............................................................................800 
Confirmation Correction Using Radio Frequency.......................................................803 
Yard Movement Using Radio Frequency....................................................................811 
Querying Using Radio Frequency ..............................................................................812 
Resource Management Using Radio Frequency........................................................814 
Enhancement Screen Wizard.........................................................................................816 
Split Screen Wizard........................................................................................................818 
 
Repeating or Resending an Acknowledged Telegram...................................................834 
MFS in the Warehouse Management Monitor ...............................................................835 
 Analyze Logs ..............................................................................................................837 
Status Management .......................................................................................................839 
Exception Handling ........................................................................................................841 
Master Data....................................................................................................................855 
Quality Inspection Engine...............................................................................................888 
Dynamic Modification..............................................................................................907 
Dynamic Modification at Inspection Decision ..................................................915 
Sample-Drawing Procedure....................................................................................917 
Sample-Drawing Unit...........................................................................................919 
Sample-Drawing Instruction.............................................................................920 
Document Assignment................................................................................................921 
Inspection Document..................................................................................................922 
Introduction .............................................................................................................943 
 Authorizations .........................................................................................................950 
Other Security-Relevant Information.......................................................................958 
EH&S Services...................................................................................................................967 
Dangerous Goods Management ....................................................................................973 
Transfer Stock Data....................................................................................................979 
 Authorizations.................................................................................................................985 
EWM: Warehouse Manager...........................................................................................988 
EWM: Warehouse Expert...............................................................................................993 
EWM: Warehouse Specialist for Goods Issue .............................................................1004 
EWM: Warehouse Specialist for Yard Management....................................................1007 
EWM: Warehouse Worker............................................................................................1009 
Data Archiving..................................................................................................................1019 
 Archiving in Delivery Processing (SCM-ECT-DLP)..................................................1024 
 Archiving Internal Warehouse Requests (SCM-ECT-DLP) ..................................1028 
 Archiving Warehouse Requests from External Systems (SCM-ECT-DLP)..........1030 
 Archiving in Quality Management.............................................................................1032 
 Archiving - Inspection Documents (CA-QIE).........................................................1033 
 Archiving Vehicle Activities (SCM-EWM-SR)........................................................1045 
 Archiving TU Activities (SCM-EWM-SR)...............................................................1048 
 Archiving Door Activities (SCM-EWM-SR)............................................................1052 
 Archiving in Transportation Management.................................................................1055 
 Archiving Shipments (SCM-EWM-TM) .................................................................1056 
 Archiving Freight Documents (SCM-EWM-TM)....................................................1058 
 Archiving in Wave Management (SCM-EWM-WAV)................................................1062 
 Archiving Telegram Flows (SCM-EWM-WOP) .....................................................1066 
 Archiving Relevant Resource Data (SCM-EWM-WOP-RM).................................1068 
 Archiving Performance Documents (SCM-EWM-LM-EP).....................................1075 
 Archiving Executed Workload (SCM-EWM-LM-WL).............................................1077 
 
SAP Extended Warehouse Management (SAP EWM)
Purpose
Extended Warehouse Management (EWM) offers you flexible, automated support for processing various goods movements and for managing stocks in your warehouse complex. The system supports planned and efficient processing of all logistics processes in your warehouse.
Introductory Notes
If you manage your warehouse stocks using the application componentInventory Management (MM-IM), you manage the quantities and values of stocks in several storage locations.
In contrast, EWM gives you the option of mapping your entire warehouse complex in detail in the system, down to storage bin level. Not only does this give you an overview of the total quantity of a product in the warehouse, but you can also always see exactly where a specific product is, at any time, in your warehouse complex. With EWM, you can optimize the use of various storage bins and stock movements, and can store together stocks from several plants in randomly-managed warehouse. Using EWM, you can control and optimize various processes in the warehouse.
Integration
EWM is completely integrated into Inventory Management and Delivery Processing. Business processes, which you trigger in other application components, lead to physical goods movements in your warehouse. You organize, control, and monitor these goods movements using EWM.
Features
Storage Bin Management and Optimization
You map the entirety of your storage facilities in EWM. You can set up different storage facilities such as automatic warehouses, high-rack storage areas, bulk storage areas, or fixed bin warehouses, in various storage types [Seite 25], according to your requirements.
You manage the stocks at storage bin level. You can define these storage bins according to your own requirements. Every storage bin in your warehouse is mapped in the system. This enables you to constantly track all stock movements in detail. You can see exactly where a specific product is located in your warehouse. You can also use EWM to optimize storage bin management, since EWM takes on a large part of optimizing the products, so that each product is assigned to the correct storage bin, depending on its size and frequency of access.
Inventory Management and EWM are fully integrated. Using the physical inventory procedures and the entry of stock differences, the system ensures that the book inventory balance in Inventory Management always matches the warehouse stock in EWM.
Goods Movements
You process all goods movements that affect your warehouse using EWM, such as goods receipts, goods issues, stock transfers, and automatic replenishment. These movements can include goods receipts, goods issues, stock transfers, automatic replenishment, management of dangerous goods, layout-oriented and process-oriented storage control, effective work preparation using automatic wave pick creation, resource optimization using rule-based bundling of warehouse tasks, or processing of inventory differences in your warehouse.
 
Work Center
You can use the work center [Seite 35] to map a physical unit in the warehouse, which you use to carry out warehouse activities such as packing, deconsolidation, weighing, quality inspections, and counting. You can personalize each work center, so that each user sees exactly those fields, data, and tab pages that are necessary for their work.
Physical Inventory
You use physical inventory [Seite 667] to regularly perform a physical stock take in your warehouse. You compare the actual, existing, physical, stock with the data managed in EWM. By entering physical inventory differences, you update the accounting data for the stock, according to the results of the physical stock take. If you have performed physical inventory at least once in a fiscal year for each storage bin/each product, the physical inventory is classed as complete.
If you use EWM, the physical inventory is performed atWarehouse Management level. You can perform a physical inventory based on products and/or based on storage bins. There is a difference monitor available, with configurable tolerance groups, which you can use to define maximum values for posting differences for each user. In addition, the system supports automatic posting according to time intervals, different priorities for each individual inventory procedure, a zero stock check, and a low stock check. The radio frequency functions are integrated into the physical inventory and support you when you perform the different physical inventory procedures, such as cycle counting, physical inventory during putaway, and physical inventory using zero stock check. Handling units are fully integrated into the physical inventory process.
Planning and Monitoring
EWN gives you an overview of all goods movements and warehouse stocks. The system supports you in planning, monitoring, and optimizing work processes. For example, it gives you a preview of the workloads for the coming days, or enables you to take preventive action in critical warehouse processes, so that you can perform stock movements on time. The extensive monitoring functions give you a current view of all activities in the warehouse. You can control the actual work in the warehouse using the individual monitors.
Radio Frequency Connection
To structure the work in the warehouse efficiently and cost-effectively, you control the warehouse workers’ work steps clearly and simply via mobile radio-frequency terminals.
The radio frequency connection [Seite 781] (RF connection) to mobile data entry achieves fast and accurate data transfer. The RF devices receive data directly from the SAP system and transfer data back to the system. You can enter and verify information using bar codes. This means that you ensure a high standard of quality in your warehouse.
Warehouse Control
 
SAP Extended Warehouse Management (SAP EWM) 510 21
Warehouse Structure Before you implement Extended Warehouse Management (EWM), you must define the structure, meaning the physical structure, of your warehouse or warehouse complex and map this in the system.
When you implement EWM, you define the individual warehouses (high-rack storage area, bulk storage area, picking storage area, and so on) as storage types within a warehouse complex, and join them together under one warehouse number.
If other warehouses (storage types) exist that you do not manage using EWM, then you should define other storage locations.
In EWM, you define storage bins for each storage type. EWM uses these to manage stock information about all products in the warehouse, at storage bin level.
Mapping the Physical Warehouse in EWM
Warehouse Number 
Storage Section
Storage Type
Storage Bin
The warehouse structure in warehouse management is divided hierarchically and consists of the following elements:
  Warehouse number
In EWM, you can manage an entire physical warehouse complex using a single warehouse number.
  Storage type
You can define the individual warehouse facilities or warehouses that make up the warehouse complex, using their technical, spatial, and organizational characteristics as storage types.
  Storage section
 
  Storage bin
Each storage type and storage section consists of a selection of storage compartments that are called storage bins in EWM. The coordinates of the storage bin tell you the exact position in the warehouse, where you can store products.
  Quant
The quant is used for inventory management of a product in a storage bin.
   Activity area
The activity area is a logical grouping of storage bins. It can refer to a storage bin, or can concatenate bins from several storage types.
You can either assign storage bins manually to the activity areas, or if there is a 1:1 relationship between storage type and activity area, you can have the system generate the assignment.
To map the structure of your physical warehouse in the system, you define the warehouse structures in EWM in Customizing. We recommend that you use the following sequence when configuring the warehouse structure in the system.
In the Implementation Guide (IMG) for EWM, choose Extended Warehouse Management → 
Master Data →  ... ...
5.  Activity Areas→ Define Activity Area 
6.  Activity Areas→ Assign Storage Bins to Activity Areas 
...
 
Warehouse Number
Definition  
In Extended Warehouse Management (EWM), you combine an entire physical warehouse under one warehouse number . You can use the warehouse number to manage several storage facilities, which together form the complete warehouse complex.
Use 
The organizational and physical attributes of a warehouse complex are collected together under the warehouse number.
For example, the weight unit, volume unit, and time unit are defined at warehouse number level. You can also define determination procedures for palletization data andpackaging specifications [Seite 494] here. You should not change these settings at a later time.
We recommend using one warehouse number for each group of storage areas or buildings (warehousing complex) in the same geographical area. If your warehousing facilities are located in different cities or are physically separated by a longer distance, it is appropriate to assign a separate warehouse number to each warehouse complex.
For more information about defining a warehouse number, see the Implementation Guide
(IMG) for Extended Warehouse Management  under Master Data → Define Warehouse Number Control.
You must make a one-time assignment between the warehouse number and asupply chain unit [Seite 53] with the business character Warehouse as a continuous setting. For more
information, see the IMG for Extended Warehouse Management  under Master Data →  Assign Warehouse Numbers. Note, however, that you must make this assignment in the production system. For this reason, you should make this setting from the SAP menu under Extended Warehouse Management  → Settings →  Assignments: Warehouse Numbers/Business Partners.
The supply chain unit contains essential information, such as country, region, and time zone. The system uses the time zone for the warehouse number when displaying all date and time fields. You can create a supply chain unit in the SAP menu underExtended Warehouse Management  → Master Data → Maintain Supply Chain Unit. 
 As soon as you actively use a warehouse number, for example because you have already created a warehouse number product, you should no longer change the assignment of the supply chain unit to the warehouse number. Doing so can result in follow-on errors.
Example 
  Goods receipt area
  Goods issue area
  Bulk storage area
 
  Storage space outdoors for special substances
 
Storage Type
Definition
 A storage type is a storage space, storage facility, or storage zone, which you define for a warehouse number in Extended Warehouse Management (EWM). The storage type is a physical or logical subdivision of a warehouse complex, which is characterized by its warehouse technologies, space required, organizational form, or function. A storage type consists of one or more storage bins.
You can define the following commonly-usedphysical storage types in EWM:
  Bulk storage area
  General storage area
Use
The storage types form the warehouse complex and can be located in one or more buildings. You manage all storage types under a single warehouse number.
The standard system for EWM comes configured with several complete storage types that you can use straightaway. These include:
  High rack storage area
  General storage area
  Pallet storage area
These storage types have all been defined with different control indicators for putaway and picking.
You can use the standard storage types as the basis for your individual settings, or you can create your own storage types to meet the special requirements of your company.
Defining Control Indicators in the Storage Type
 At storage type level, you must specify the control indicators that control the material flow (putaway and picking) in each storage type. These include the control indicators for:
  Putaway
  Stock removal (picking)
 
SAP Extended Warehouse Management (SAP EWM) 510 26
You can only activate or deactivate the level of the available quantities and handling unit management requirement, if there are no stocks present within a storage type.
We recommend that you only change the capacity check for a storage type if no more stocks are present within the storage type.
Particular care should be taken if you subsequently change the putaway behavior for putaway.
In the storage type, there are indicators that you can override in the warehouse process category. This means that specific functions, such as the confirmation requirements for putaway and picking or the option for posting changes to the same storage bin, are valid for specific storage types, but are not valid for a specific posting.
For more information about changing the predefined storage types or creating new storage types, see the Implementation Guide (IMG) for EWM underExtended Warehouse Management → Master Data → Define Storage Type. 
Example
You can define several storage types for each warehouse number. The following figure shows five storage types that are assigned to a warehouse number:
Storage Type
 Activity Area
Definition
Logical section of the warehouse that groups storage bins based on defined warehouse activities.
Examples of activity areas include:
  Putaway [Seite 300] 
  Picking [Seite 322] 
  Inventory [Seite 667] 
Use
You use activity areas to provide logical subdivisions in your warehouse. In these activity areas, different warehouse workers execute certain warehouse activities, such as putaway or picking.
You create activity-dependent bin sortings within an activity area. Extended Warehouse Management (EWM) uses these bin sortings to optimize the execution of warehouse tasks.
Structure
 An activity area consists of one or more assigned storage bins.
You can define the assigned storage bins using the following attributes:
   Aisle
  Stack
  Level
   Any assigned deconsolidation groups
You can sort these storage bins into any sequence you want, and assign as many activities to them as you require.
For more information, see the Implementation Guide (IMG) forExtended Warehouse Management under  Master Data → Activity Areas → Assign Storage Bins to Activity Areas and Define Sort Sequence for Activity Area.
To be able to work with activity areas, you have to generate the bin sorting.
On the SAP Easy Access screen, choose Extended Warehouse Management  → 
Master Data → Storage Bin → Sort Storage Bins. 
You can generate activity areas from storage types in Customizing. For more
 
Integration
EWM generates warehouse orders [Seite 419] for each activity area.
 
Storage Section
Definition  
In Extended Warehouse Management (EWM), a storage section is an organizational subdivision of a storage type, which joins together storage bins with similar attributes for the purpose of putaway. The criteria for joining these bins together can be defined in any way, for example, heavy parts, bulky parts, fast-moving items, slow-moving items.
Use 
You can use the storage section as an organizational aid for putting away goods in the warehouse. When you use storage types and storage sections, you must define the organizational aims clearly. The physical location is the main organizational factor. It is not absolutely mandatory that you subdivide a storage type into two or more storage sections. However, you must create at least one storage section for each storage type.
You can only define control parameters and control values in thestorage type.
For information on how to define a storage section for a storage type, see the Implementation
Guide (IMG) for Extended Warehouse Management  under Master Data → Define Storage Sections. 
Example 
High rack storage areas frequently consist of many storage bins that vary in size. For example, in many such storage areas, the bins in the lower level are larger for especially large and heavy parts, while those in the upper levels are smaller.
The following figure shows a high-rack storage area divided into two storage sections. You use the front storage section for fast-moving items, and the back storage section for slow- moving items.
Bin type
High bins
Low bins
Low bins
Storage section
Storage Bin
Definition  
 A storage type consists of a selection of storage spaces, which are calledstorage bins  in Extended Warehouse Management  (EWM). The storage bin is the smallest spatial unit in a warehouse. Therefore, the storage bin represents the exact position in the warehouse where products are and/or can be stored.
Since the address of a storage bin is frequently derived from a coordinate system, a storage bin is often referred to as a coordinate. For example, the coordinate 01-02-03 could be a storage bin in aisle 1, stack 2, and level 3.
Use
To each storage bin, you assign the warehouse number in which the storage bin is located. You just also assign a storage type [Seite 25] and storage section [Seite 29] to each storage bin.
You can also define the following additional attributes for a storage bin:
  Maximum weight
  Total capacity
  Fire-containment section
  Storage bin type (for example, for large or small pallets)
In some putaway strategies, the storage bin type plays an important role during optimization of the automatic search for a storage bin, in connection with the pallet type. For example, you can define the putaway strategy in such a way that you put away large industrial pallets into special large bins, and smaller pallets into small bins.
For information about defining storage bins, see the Implementation Guide (IMG) for
Extended Warehouse Management  under Master Data → Storage Bins. 
Structure
 
Quant
Definition  
Stock of a specific product with the same characteristics in one storage bin [Seite 30], resource [Seite 752], and transportation unit [Seite 613]. The system manages different batches of a product as different quants. You can increase the quantity of a quant by adding to the existing stock. Quants can only be created and deleted using movements.
Use 
Quants are used to manage stocks at storage bin level, resources, and transportation units.
When you put a product away into an empty bin in Extended Warehouse Management (EWM), the system generates a quant in this storage bin. When you remove the quantity from storage, the system automatically deletes the quant.
In the quant record, the system manages the data for the products collected together in the quant. This data includes:
  Quant identification
Door
Definition
Location in the warehouse where the goods arrive at or leave the warehouse. The door is an organizational unit that you assign to the warehouse number.
Vehicles [Seite 612] and their transportation units (TUs) [Seite 613] drive up to the doors of a warehouse to load or unload goods there. The doors are in close proximity to the relevant staging areas [Seite 33].
Use
To control putaway and stock removal processes in your warehouse, you can define doors and staging areas within a warehouse number.
You can assign various functions to a door:
  Inbound
  Outbound
  Inbound and outbound
In delivery processing, the system uses determination rules to determine the following for each delivery item:
  Staging area groups
  Doors
The determination rules are influenced by the possible assignments that you have defined in Customizing between doors and staging areas as well as between doors and staging area/door determination groups. The system updates the delivery at item level with the values that it finds.
You define doors in Customizing for Extended Warehouse Management (EWM) under Master Data → Warehouse Door → Define Warehouse Door. You assign staging areas and staging
area/door determination groups to your doors underMaster Data → Warehouse Door. 
Structure
You assign each door to a storage bin that you can use to post goods receipts or goods issues. You assign this storage bin to a storage type with the storage type roleF.
You can also assign doors to supply chain units [Seite 53] to control authorization checks. You can also assign doors to yard bins (seeYard Management [Seite 619]).
See also:
 
Staging Area
Definition
Organizational unit that is assigned hierarchically to the warehouse number and that is used to organize the flow of goods in the warehouse.
Use
Staging areas are used for the interim storage of goods in the warehouse. They are located in close proximity to the doors [Seite 32] assigned to them. You can define staging areas for different purposes and even simultaneously for multiple purposes:
  Goods receipt
Interim storage of unloaded goods until they are put away
  Goods issue
Interim storage of picked goods until they are loaded
In Customizing, you define staging areas and assign the staging areas to the relevant doors. For more information, see the Implementation Guide (IMG) forExtended Warehouse Management (EWM) under  Master Data → Staging Areas → Define Staging Areas and  Master Data → Warehouse Door  →  Assign Staging Area to Warehouse Door .
Structure
You can group multiple staging areas into staging area groups. The staging area group corresponds to a storage type (storage type role “D”), while the staging area corresponds to a storage section. You can divide each staging area into one or more storage bins. You need multiple storage bins, for example, if you want to define a loading sequence.
See also:
 
 
Work Center
Definition
The work center is a physical unit in the warehouse, in which you can perform warehouse activities such as packing, distribution, or weighing.
Use
You can use the work center in the following processes:
  Packing
  Deconsolidation
  Counting
Extended Warehouse Management (EWM) contains the following transaction types for the work center:
  Packing - General
  Deconsolidation
This transaction type is for distributing mixed handling units (HUs) into HUs for non- mixed deconsolidation groups.
  Quality Inspection and Count
This transaction type is for entering count and inspection results, and for confirming inspection results.
  Packing in the Staging Area
This transaction type is for packing together HUs according to the criterionStop on Route.
You must assign each work center to a warehouse number, storage type, and storage bin. Note that you can only use storage types that have the storage type role ‘Work Center’ (E), ‘Pick Point’ (B), or ‘Identification and Pick Point’ (C). You can configure more than once work center for each storage type in the system.
You can assign an inbound and outbound section to each work section. For more information about setting up work centers, see the Implementation Guide (IMG) for EWM underExtended Warehouse Management → Master Data → Work Center .
Example
The following example shows you various options, for example, on how a work center for deconsolidation can be structured:
 
Outb. Section Work Center 
 
You can also join work centers together into work center groups. This means that you can send individual products or HUs to a work center group, which corresponds to a storage section. In the above example, this would be a warehouse task to storage section 0001.
 
Resource
Definition
 A resource is an entity representing a user or equipment, which can execute work in the warehouse.
Use
 A resource can log on to a radio frequency (RF) or non-RF environment.
Once the resource is logged on to the system, it can receive work for execution, and can be tracked and displayed in the warehouse management monitor [Seite 878].
For more information about logging on to an RF environment, seeLogon [Seite 790].
For more information about how resources receive work, see Assignment of Warehouse Order to Resource [Seite 755].
Structure
 A resource belongs to a resource type [Seite 753] and resource group [Seite 754].
You define a resource in the transaction for resource maintenance. To do so on
the SAP Easy Access screen, choose Extended Warehouse Management → 
 
Resource Type
Definition
 A resource type is a grouping of resources with similar technical or physical qualifications.
Use
The resource type determines the following for its correspondingresources [Seite 752]:
  Horizontal velocity
The velocity of a resource can influence the LSD of a warehouse order (WO).
For more information, see Latest Starting Date (LSD) [Seite 760].
   Applicability of position management
For more information, see Position Management [Seite 795].
  Qualifications and preferences (reflected by priority values) regardingbin access types [Extern] and HU type groups [Extern] 
The qualifications and priority values influence which WOs are selected for a resource requesting work.
For more information, see Warehouse Order Selection [Seite 757].
You define resource types, and assign to them qualifications, in Customizing for
Extended Warehouse Management  → Cross-Process Settings → Resource Management → Define Resource Types.
 
Resource Group
Definition
 A resource group is a grouping of resources forqueue [Seite 764] assignment purposes.
Use
The resource group determines the sequence of allowed queues for its corresponding resources [Seite 752], which can influence which WOs are selected for a resource. For more information, see Warehouse Order Selection [Seite 757].
You assign/unassign a resource group to/from a queue using the queue sequence for resource group transaction, accessed on theSAP Easy Access 
 
Warehouse Product
Definition
Warehouse-number-dependent view of the product master data. The warehouse product comprises all the properties of a product that relate to its storage in a certain warehouse within the framework of Extended Warehouse Management  (EWM), such as the putaway control indicator.
Use You need the warehouse product if you wish to use a product whose global data you have already maintained in the product master inEWM. You can create or change a warehouse product via the SAP menu underExtended Warehouse Management → Master Data → Maintain Warehouse Product. Entry of the warehouse number [Seite 23] and the ‘party entitled to dispose’ is mandatory, because the warehouse-number-dependent data pertaining to the warehouse product applies only to this warehouse number and this party.
Structure
The warehouse-number-dependent data on the warehouse product can be found on the following tab pages in the maintenance function for warehouse products:
  Warehouse data
Here you maintain data on the warehouse in which the product is stored.
  Slotting
  Storage type data
Here you maintain data on the type of facility in which the product is stored. For more information, see Storage Type [Seite 25].
Integration
Global, warehouse-number-independent data pertaining to the storage of the product can be found on the Storage tab page. This tab page is also displayed in product master maintenance.
The following warehouse-number-independent data on the storage of a product is adopted in EWM from the ERP system.
  Handling unit types
  Warehouse product group
  Warehouse storage condition
  Warehouse handling indicator
  Serial number profiles
  Quality inspection groups
 
 
Hazardous Substance
Definition
Substance that can pose a danger to humans, animals, or the environment when being handled or stored. The handling and storage of hazardous substances is governed by law.
For more information, see the SAP Help Portal underSAP ERP Central Component → 
Logistics → Environment, Health and Safety (EHS) → Hazardous Substance Management (EHS-HSM) → Hazardous Substance Master   → Hazardous Substance. 
 
Packaging Specification
Definition
 A packaging specification is master data. The packaging specification defines all the necessary packing levels for a product in order, for example, to put away or transport the product. For a product, a packaging specification mainly describes in which quantities you can pack the product into which packaging materials in which sequence.
Use
  In printed form, a packaging specification is a set of instructions for the employee in the warehouse. More specifically, the work steps that you enter in a packaging specification are intended as information for the employee. In this way you can, for example, give the employee exact instructions as to where to place the label on a box, or how a product should be stacked onto a pallet.
  The system can determine packaging specifications during various processes (see below). Processes that determine packaging specifications use only parts or specific attributes from the packaging specification.
Structure
Header
Pack. mat. Work stepElement 2
Level 2 Pack. mat. Work stepElement 1
Level n Pack. mat. Work stepElement 1
Product
Packaging
specification
OR
  Header
 
  Contents
 A packaging specification contains a product. However, some packaging specifications contain more than one product, or refer to other packaging specifications.
  Level
You can map various packing levels in a packaging specification. Each level contains a target quantity, which defines how many times you can pack the previous level into this level.
  Element group
For each level there is exactly one element group. However, you can reuse element groups in several packaging specifications.
  Elements
Elements consist of a packaging material and/or a work step.
  Step
 A text with an identification, which you can use in one or more packaging specifications.
  Packaging material
 A product that is defined with a packaging material type in the product master.
Example for a Packaging Specification and Its Structure:
Header: Name: PS1, Status: New
Contents: product A, 1 piece
Level 1: Target quantity one, element group EG1
Element group EG1:
  Element E1: packaging material ‘Small box’, work step ‘Place 1 piece upright in each box’
  Element E2: additional packaging material ‘Label’, work step ‘Place label on upper left’
Level 2: Target quantity 50, shift quantity 10, element group EG2
Element group EG2:
  Element E3: packaging material ‘Pallet’, work step ‘Place boxes layer by layer onto pallet’
Integration
 
iPPE Cond.
Whse-int.
processes
 
In both the Inventory Collaboration Hub (ICH) and in Extended Warehouse Management (EWM), you can use the same packaging specification for an inbound delivery or an ASN that you then use for the Automatic Packing [Seite 510] process.
Example
Palletization data in EWM
In your warehouse, you put away product A onto pallets for 50 pieces. Create a packaging specification with a level that contains the main packaging material Pallet and the contents Product A. For this level, enter the target quantity 50.
In the process ‘Putaway’ for the inbound delivery, the system splits the quantity in the inbound delivery across multiple warehouse tasks, due to this packaging specification. For example, if a quantity of 100 pieces is delivered, then the system creates two warehouse tasks for 50 pieces.
Functions of the Packaging Specification
The following functions are possible for packaging specifications:
  Create, copy, and activate (see also: Creation of Packaging Specifications [Seite497])
  Determine (see also: Packaging Specification Determination [Seite499])
  in mehrere Systeme verteilen.
Route
Definition
Sequence of legs that are connected by transshipment locations [Extern].
Use
The route represents a framework or corridor that comprises a multitude of trips, in other words, possible concrete itineraries. The system uses routes to determine trips inroute determination [Seite 638].
 
Structure
Leg
 A leg is assigned uniquely to a route, in other words, it cannot be part of multiple routes. You define legs as a sequence of stops. Each stop is asupply chain unit (SCU) [Seite 53], in other words, a location or zone [Seite 646]. The stops that connect two consecutive legs must be locations.
By specifying whether the stop-offs are optional or mandatory, you define which locations the carrier is to serve in which order.
You assign exactly one means of transport to each leg. In most cases, adjacent legs of a route have different means of transport. However, it might also be necessary to change legs due to various properties of the legs. Nonetheless, in most cases, the legs of a route represent its unimodal parts.
Stop
 
SAP Extended Warehouse Management (SAP EWM) 510 47
In static route determination, the system determines the mode of transport for foreign trade for outbound shipments (trips) in the following sequence:
1. Country of first location
2. Part of the location sequence of the trip that runs from the first location within this country
3. The first location in this part of the location sequence when going backward that is a stop along the leg and for which a mode of transport for foreign trade was defined, in other words, the location that lies closest to the border.
Carrier Assignment
You can assign as many different carriers as you want to your means of transport or any of its subordinate means of transport for the leg. You can specify whether dangerous goods can be transported for each such combination of leg, means of transport, and carrier.
In static route determination, the system defines the carrier for a trip as the carrier for the first leg who can transport dangerous goods, if required, and for which you have defined the lowest costs for transportation along this leg in the carrier profile.
Departure Calendar Assignment
You can define a departure calendar for the leg. If the departures for a specific request type do not correspond with the departure calendar for the leg, you can also define a specific departure calendar for this request type.
The system takes into account departure calendars whenscheduling [Seite 656] a trip for both the start location of the request and for each transshipment location served.
Validity and Restrict ions
You can restrict the validity of a route by specifying the following:
   A validity period that the system compares with the cutoff time of a single request.
  Permitted shipping conditions that the system compares with the shipping conditions of a single request.
Permitted request types that the system compares with the request type of a single request.
You can specify permitted request types at the header level of the route and for each stop within the leg (customer, for example). The request types at stop level must be part of the request types that you specify at header level. Request types at stop level have a higher priority than those at header level. Accordingly, the request types at header level are valid for those stops for which you have not defined separate request types.
  Permitted transportation groups that the system compares with the transportation groups of the products in a single request.
  Weight limits for single and collective requests that the system compares with the total weight of the products in the single request or in multiple combined requests
You can also specify weight limits for single and collective requests for each stop within a leg. These limits overwrite the relevant limits that you specify for the route at header level.
  Volume limits for single and collective requests that the system compares with the total volume of the products in the single request or in multiple combined requests
You can also specify volume limits for single and collective requests for each stop within a leg. These limits overwrite the relevant limits that you specify for the route at header level.
  Dimension limits (length, width, and height)
 
SAP Extended Warehouse Management (SAP EWM) 510 48
You can specify the maximum dimensions that a product is permitted to have to be valid for a certain route. The system compares these dimensions with those that you defined in the product master.
 
Cross-Docking Route
Definition
One or more inbound routes or one or more outbound routes that are connected by exactly one cross-docking location (warehouse or distribution center relevant to cross-docking).
Use
You use cross-docking routes (CD routes) to link routes to route networks. The system takes into account CD routes when you use route determination [Seite 638] as part of cross-docking [Seite 544]. Here you can define per route pair (inbound route and outbound route) whether goods at the cross-docking location (CD location) are to remain on the same vehicle or whether they are be loaded onto a different vehicle.
Structure
To define a CD route, you must make the following settings:
  You specify a CD location for the route at header level.
  You specify one or more inbound routes on theCD Routes tab page. Here the destination location of all these routes must be identical with the CD location.
  You specify one or more outbound routes on theCD Routes tab page. Here the start location of all these routes must be identical with the CD location.
By specifying a different CD route as the inbound or outbound route, you can create a route network with multiple CD locations. Here an outbound CD route from CD location 1 must have at least one inbound route with the start locationCD location 1. An inbound CD route to CD location 2 must have at least one outbound route with the destination location CD location 2.
  On the CD Attributes tab page, you define the required attributes, for example, whether transshipment is not required (goods remain on the same vehicle), for the route pairs that consist of inbound and outbound routes.
You define CD routes in the master data forExtended Warehouse Management (EWM) under Master Data → Shipping and Receiving → Route Determination → Maintain Route.
Example
 
Cross-
Docking
Location 1
R o u t e  1 ( I n b o u n d  ) 
  R o  u t e
  2
  3
Cross-Docking Route 1
 R o u  t e  6
 
 
Vehicle
Definition  A specialization of a particular means of transport. A vehicle can comprise one or more transportation units [Seite 613].
Use
You define vehicles in the master data for transportation. You use vehicles to group deliveries and to communicate with invoicing and Transportation Management (TM) [Seite 629].
If you assign transportation units to a vehicle in a fixed way, you cannot assign these transportation units to another vehicle. In this case, data that you define for the vehicle is also valid for the assigned transportation units.
The dimensions of the vehicle come from the means of transport that you assign to the vehicle, and are used as the planned size.
Integration
  When the loading process has been completed, a status change triggers the sending of a message to TM that enables bills of lading to be created automatically (see Integration of TM with the Loading Process [Seite635]).
  Before goods issue posting, you can create the current invoice via an invoice request to SAP CRM Billing (see Invoice Creation Before Goods Issue [Seite368]).
Example
 
Transportation Unit
Definition
The smallest loadable unit of a vehicle [Seite 612] that is used to transport goods. The transportation unit (TU) can be a fixed part of the vehicle.
The following figure shows different transportation units:
  Vehicle 1: Semitrailer truck with one transportation unit
  Vehicle 2: Truck with cargo area and trailer, in other words, two transportation units
 
Vehicle 1
 
You map transportation units as handling units (HUs) and assign packaging materials to them. By linking these packaging materials to means of transport, you define construction rules for your vehicles. In this way, you define, for example, how many transportation units a vehicle is supposed to have and the order in which they are to be arranged. You also specify whether a transportation unit is to be optional or obligatory:
  Obligatory transportation units are a fixed part of a vehicle (fixed assignment). You cannot assign them to another vehicle, for example, truck cargo area.
  You can assign optional transportation units to other vehicles, for example, trailer for a truck.
Use
You define transportation units in the master data for transportation. You use them for inventory management in the yard.
Example
  Compartment in a tank truck
  Container
Supply Chain Unit (SCU)
Definition
Physical or organizational unit that is used with one or more business characters within a logistical process. An organizational unit may be a goods receiving office or a shipping office, for example.
The business characters are predefined by SAP.
Use
With the SCU, you can replicate certain business characters of locations, such asdoor  or warehouse, which you need in the processes of Extended Warehouse Management  (EWM). You can use an SCU with different business characters. An SCU can simultaneously be used as a planning location and a shipping office, for example.
You can create hierarchies of SCUs to represent the organization of a supply chain.
You can create, change, and delete SCUs via the SAP menu, underExtended Warehouse Management → Master Data → Maintain Supply Chain Unit. 
Structure
The SCU contains general data and address data of the corresponding location. In contrast to the latter, however, it does not contain any further global or application-specific data. The SCU also has one or more business characters.
You will find this SCU data on the following tab pages:
  General 
General header data of the SCU/location, such as the global location number (GLN) and geographical data.
The technical name of an SCU must be unique in the system. That is to say, it must not conflict with the technical name of a location.
   Address Data 
  Business Character  
Integration
When a location is created in SAP SCM either manually or by transfer via the core interface (CIF), the system automatically creates an SCU with identical general and address data and the business character planning location.
Conversely, if you create an SCU with the business characterplanning location, the system automatically creates a location with identical general and address data.
This relationship is of significance when a location is deleted. When you delete a location, the system only deletes the business characterplanning location of the corresponding SCU. If the SCU has further business characters, it remains in the system with the same name. To delete the SCU from the system, you must first delete all other existing business characters.
 
 
Warehouse Task
Definition
Document that uses Extended Warehouse Management  (EWM) to execute goods movements. Logical or physical goods movements or even stock changes can be the basis for a warehouse task. These include:
  Picks
  Putaways
Use
You create the warehouse task either with reference to a warehouse request or without a reference document, for example for internal goods movements.
The following figure shows the different warehouse tasks for products and handling units (HUs):
Product Warehouse Tasks [Seite 406] 
Handling Unit Warehouse Tasks [Seite 407] 
 
HU WT Handling Unit Warehouse Task
 
You or the system use product warehouse tasks, for example, fordeconsolidation [Seite 298]  and handling unit warehouse tasks, for example, forunloading [Seite 608].
You can identify the type of the warehouse task from the warehouse process type in the warehouse task. For more information about the simultaneous use of product warehouse tasks and handling unit warehouse tasks, seePick Point [Seite 410].
EWM also submits hazardous substance texts [Seite 969] in the warehouse task.
 
Warehouse Order
Definition
Document that represents an executable work package that a warehouse employee should perform at a specific time. The warehouse order consists of warehouse tasks or physical inventory items.
Use
When you move products, in other words you or Extended Warehouse Management (EWM) create warehouse tasks, then EWM groups these warehouse tasks together into warehouse orders, and makes them available for processing.
When you perform a physical inventory, in other words you create physical inventory items, EWM also groups these physical inventory items together into warehouse orders.
You can adjust the scope and type of a warehouse order using the warehouse order creation rules that you have defined in Customizing.
For more information about warehouse order creation rules, see the
Implementation Guide (IMG) for EWM under Cross-Process Settings → 
Warehouse Order → Define Creation Rule for Warehouse Orders. 
Integration
The warehouse groups together warehouse tasks or physical inventory items.
Example
 
Handling Unit (HU)
Definition
 A handling unit is a physical unit consisting of packaging materials (load carriers/packing material) and the goods contained on/in it. A handling unit is always a combination of products and packaging materials [Seite 492]. All the information contained in the product items, for example, about batches, is retained in the handling units and is always available.
Handling units can be nested, and you can create a new handling unit from several other handling units.
 A handling unit has a unique, scannable identification number that you can construct according to industry standards such as EAN 128 or SSCC.
© SAP AG Filename Date/ 1
Container = HU 100 Pallet = HU 110
Package
Structure
  Identification number
  Packaging material
  Packaging specification
 A handling unit consists of a handling unit header and handling unit items. It receives a unique number that is used for identification purposes.
Handling Unit Header  
The header data of a handling unit is divided up as follows:
  Weight/volume/dimension
SAP Extended Warehouse Management (SAP EWM) 510 58
For more information about the different detailed information, seePacking at the Work Center [Seite 506].
Status
The handling unit is connected to general status management. This enables you to document the various physical statuses (such as planned or realized) and other attributes (such as, weighed, loaded, blocked, or posted for GI) for a handling unit.
If you want to use your own status, you can store a user schema for the packaging material type.
Handling Unit Item 
 
Monitoring
Purpose
  Warehouse Management Monitor [Seite 878] 
  Easy Graphics Framework [Seite 68] 
 
Warehouse Management Monitor
Use
The warehouse management monitor is a central tool for keeping warehouse managers constantly up-to-date as to the current situation in the warehouse, and to enable them to initiate appropriate responses in light of this situation.
The warehouse management monitor also contains alert monitoring capabilities, which highlight to warehouse managers actual and potential problematic situations in the warehouse, and provide exception handling tools.
Prerequisites
2. Entering the warehouse number and name of the monitor.
3. Choosing Execute.
Node Hierarchy Tree
The node hierarchy tree [Extern] contains all of the predefined nodes representing different object classes.
The tree is used solely for navigation purposes. You can use the hierarchy tree to display in the upper view area object information for a specific node, based on selection criteria.
The warehouse management monitor contains nodes for object classes relating to the following:
 
SAP Extended Warehouse Management (SAP EWM) 510 61
  Processes such as stock and bin, and resource management [Seite 750] 
   Alerts such as overdue waves [Seite 769] or overdue deliveries without goods issue/goods receipt
Drilldown Capabilities
 After displaying in the upper view area object information for a node, you can drill down and display the object information for its lower-level nodes, via designated pushbuttons.
You can similarly drill down to the lower-level nodes from the lower view area.
List and Form Views
By default, object information is displayed as a list view [Extern]. The list view is displayed in an ALV grid, and offers all standard ALV functionalities, including sorting, filtering and printing.
You also have the option of toggling to form view [Extern] for a selected object. The form view provides a focused view of the object, and provides more detailed information than the list view. The form view is displayed in an HTML viewer.
Methods
 After object information is displayed in either view area, you can call methods to perform actions on selected objects. For more information about the available methods, seeMonitor Methods [Seite 882].
Customizing Options
You can use the standard SAP monitor or you can create your own monitor in Customizing.
For more information about creating your own monitor, see the Implementation
Guide (IMG) for EWM under Extended Warehouse Management  → Monitoring → Warehouse Management Monitor.
If you use the standard SAP monitor, you can tailor it to your needs by either creating variants for the standard nodes, or creating new variant nodes, based on the standard nodes.
  Creating variants for the standard nodes enables you to use predefined selection criteria while running a session of the monitor. The variant-node assignments are lost when you close the monitor session.
 
Monitor Basic Operations
Hide a selected node in the hierarchy tree
This operation is invoked by choosing the Hide Node option in the node’s context menu.
Show hidden nodes This operation is invoked by choosingShow Hidden Nodes.
 After choosing this option, previously hidden nodes are displayed in the
hierarchy tree, with the icon.
Unhide a selected node in the hierarchy tree
This operation is invoked by choosing theUnhide Node option in the node’s context menu.
 After choosing this option, the node
icon changes to (regular node) or
(variant node).
There are two options from the node’s context menu:
Create Variant Node for Current Level – creates a variant node directly underneath the original node
Create Variant Node for Category Level – creates a variant node under the original node, on the same level as the node’s category
When creating the variant node, you have one of the following execution options:
Execute – creates only the variant node based on the source node
Execute with Sub-Tree – creates the variant node, as well as all of the same lower-level nodes as are contained in the source node
 After creating the variant node, you can create a variant for selection criteria, as well as assign to it a layout variant.
Delete variant node This operation is invoked by choosing the Remove Node option in the node’s context menu.
Change variant node text This operation is invoked by choosing the Rename Node option in the node’s context menu.
Display in list view object information for a node
 
Expand all nodes in the hierarchy tree
This operation is invoked by choosing
in the top tool bar.
Collapse all nodes in the hierarchy tree
This operation is invoked by choosing
in the top tool bar.
Display object information of a lower-level node in the higher- level node’s list view
This operation is invoked by selecting a row in the  ALV, and choosing the pushbutton corresponding to the lower-level node.
Information on the lower-level objects appears in the bottom list view.
Toggle between list and form views
You call this operation by selecting one or more
rows in the ALV, and choosing from the list view tool bar.
You can toggle back from form view
to list view, by choosing again.
Show display transaction for object
 
Monitor Methods
Use
The warehouse management monitor methods enable you to manage and control warehouse objects and processes.
The methods are assigned to object classes, and carried out on specific objects within the object classes. They are implemented by utilizing function modules from content providers responsible for the object classes.
Prerequisites
You have defined object class methods, and their presentation, in Customizing forExtended Warehouse Management → Monitoring → Warehouse Management Monitor → Define Object Class Methods.
Methods are included in the standard delivery. The methods are displayed as standard with the accumulated methods menu buttons.
 Activ ities
Description
Change Bin
BIN Storage Bin Enables you to change data of the selected storage bin (transaction /SCWM/LS02)
Print HU
Reprint HU
Display HU
HU Handling Unit Enables you to display detailed information for an HU at a work center
PIDIFF Differences-{}- 
PIHREF References
 
PIHSTK Product
Maint. Resource
Enables you to maintain a selected resource [Seite 752] (transaction /SCWM/RSRC)
Logon Resource
Enables you to log on a selected resource to the desktop environment
Logoff Resource
Enables you to log off a selected resource from the desktop environment
Send Message
RSRC Resource
Enables you to create and send a message to one or more selected resources
 Assign Queue
Unassign Queue
RSRCG R
Resource Group
Enables you to assign/unassign a queue [Seite 764]  to/from the selected resource group [Seite 754]  (transaction /SCWM/QSEQ)
Simulate WO
Enables you to simulate WO creation for one or more selected WTs, based on a specified WO creation rule.
If none is specified, the system will attempt to determine one pursuant to the search sequence for WO creation rules per activity area.
Display WT Log
Split from WO
Enables you to unassign one or more WTs from a WO, and group them into a newly-created WO.