Vous êtes sur la page 1sur 1078

SAP Extended Warehouse Management (SAP EWM)

Release 510

ADDON.SPL_SCM_WM

SAP Online Help

20.07.2007

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

SAP Extended Warehouse Management (SAP EWM)

510

SAP Online Help

20.07.2007

Icons in Body Text


Icon Meaning 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, see Help 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 Example text Description 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 EXAMPLE TEXT Emphasized words or phrases in body text, graphic titles, and table titles. 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. 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. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. Keys on the keyboard, for example, F2 or ENTER.

Example text

Example text <Example text>

EXAMPLE TEXT

SAP Extended Warehouse Management (SAP EWM)

510

SAP Online Help

20.07.2007

SAP Extended Warehouse Management (SAP EWM) ........................................................... 19 Warehouse Structure ........................................................................................................... 21 Warehouse Number ......................................................................................................... 23 Storage Type .................................................................................................................... 25 Activity Area...................................................................................................................... 27 Storage Section................................................................................................................ 29 Storage Bin....................................................................................................................... 30 Quant................................................................................................................................ 31 Door.................................................................................................................................. 32 Staging Area..................................................................................................................... 33 Work Center ..................................................................................................................... 35 Resource .......................................................................................................................... 37 Resource Type ............................................................................................................. 38 Resource Group ........................................................................................................... 39 Warehouse Product.......................................................................................................... 40 Hazardous Substance ...................................................................................................... 42 Packaging Specification ................................................................................................... 43 Route ................................................................................................................................ 46 Cross-Docking Route.................................................................................................... 49 Vehicle.............................................................................................................................. 51 Transportation Unit ....................................................................................................... 52 Supply Chain Unit (SCU).................................................................................................. 53 Warehouse Task .............................................................................................................. 55 Warehouse Order............................................................................................................. 56 Handling Unit (HU) ........................................................................................................... 57 Monitoring ............................................................................................................................ 59 Warehouse Management Monitor.................................................................................... 60 Monitor Basic Operations ............................................................................................. 62 Monitor Methods ........................................................................................................... 64 Easy Graphics Framework ............................................................................................... 68 Definition of EGF Cockpit Layouts................................................................................ 71 Make Settings for the Easy Graphics Framework ........................................................ 73 Using the Refresh Rate ................................................................................................ 76 Interfaces, Methods and Function Modules in the EGF ............................................... 77 Make Browser Settings for the Easy Graphics Framework.......................................... 79 Delivery Processing ............................................................................................................. 80 Delivery Processing.......................................................................................................... 81 Documents in Delivery Processing............................................................................... 83 Inbound Delivery Notification ........................................................................................ 87 SAP Extended Warehouse Management (SAP EWM) 510 4

SAP Online Help

20.07.2007

Inbound Delivery........................................................................................................... 88 Outbound Delivery Request.......................................................................................... 90 Outbound Delivery Order.............................................................................................. 91 Outbound Delivery ........................................................................................................ 93 Status Management...................................................................................................... 94 Quantity offsetting......................................................................................................... 97 Field Control ................................................................................................................. 99 Validation .................................................................................................................... 101 Incompleteness Check............................................................................................ 102 Consistency Check ................................................................................................. 103 Tolerance Check ................................................................................................. 104 Post Processing Framework in Delivery Processing.................................................. 105 Change Documents in Delivery Processing ............................................................... 107 Menu Paths and Customizing Paths for Delivery Processing .................................... 108 Warehouse Request....................................................................................................... 109 Warehouse Req. for Inbound Delivery or Outbound Delivery Order.......................... 112 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 Executing an Ad Hoc Movement............................................................................. 125 Executing a Replenishment .................................................................................... 126 Executing a Warehouse Reorganization................................................................. 127 Warehouse Request for Posting Changes ................................................................. 128 Performing Scrapping ............................................................................................. 130 Warehouse Request for Returns ................................................................................ 132 Processing, Deleting, and Archiving Warehouse Requests ....................................... 135 HU Integration in Delivery Processing........................................................................ 136 User Interfaces in Delivery Processing....................................................................... 138 Basic Functions in Delivery Processing ......................................................................... 139 Determination of Priority for Inbound Deliveries ......................................................... 140 Printer Determination in Delivery Processing ............................................................. 141 Printing Delivery Notes............................................................................................ 143 Text Management....................................................................................................... 145 Delivery Quantity Adjustment ..................................................................................... 147 Quantity Differences for Stock Transfer Orders...................................................... 150 Delivery Split for Inbound Deliveries........................................................................... 154 Delivery Split for Outbound Deliveries........................................................................ 156 Validation .................................................................................................................... 159

SAP Extended Warehouse Management (SAP EWM)

510

SAP Online Help

20.07.2007

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 Direct Outbound Delivery Order ..................................................................................... 167 Processing of Direct Outbound Delivery Orders......................................................... 170 Fulfilling Immediate Deliveries with Direct Outbound Delivery Orders ....................... 172 Scrapping Using a Direct Outbound Delivery Order................................................... 175 Availability Check........................................................................................................ 176 Notification of Expected Goods Receipt......................................................................... 179 Expected Goods Receipt ............................................................................................ 180 Using Expected Goods Receipts................................................................................ 181 Generate and Delete Expected Goods Receipts........................................................ 184 Generate Inbound Delivery from Expected Goods Receipt ....................................... 187 Generate Inbound Delivery Item from Expected Goods Receipt ............................... 189 Goods Receipt Posting from Production ........................................................................ 191 Goods Receipt Posting Triggered by ERP ................................................................. 192 Goods Receipt Posting Triggered by EWM................................................................ 195 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 Making Settings for Route Determination ............................................................... 205 Executing Automatic Route Determination ............................................................. 207 Data Use in Route Determination ........................................................................... 209 Special Features for Outbound Delivery Objects.................................................... 210 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 Delivery Processing to Safekeeping................................................ 220 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 Creating Condition Records .................................................................................... 229 Connection to Value-Added Service Order (VAS Order) ........................................... 230

SAP Extended Warehouse Management (SAP EWM)

510

SAP Online Help

20.07.2007

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 Connection of Delivery Processing to Quality Management ...................................... 243 Connection of Delivery Processing to Batch Management ........................................ 245 Integration of Delivery Processing with Pickup........................................................... 246 Communication from EWM to the ERP System............................................................. 248 Processing of Inbound Deliveries ............................................................................... 251 Processing of Outbound Deliveries ............................................................................ 253 Delivery Processing Administration................................................................................ 256 Interfaces for Communication from EWM to the ERP System ................................... 257 Functional Enhancement Through Business Add-Ins (BAdIs) ................................... 260 Data Enhancement for Warehouse Requests ............................................................ 261 Goods Receipt ................................................................................................................... 263 Storage Control .............................................................................................................. 265 Process-Oriented Storage Control ............................................................................. 267 Direct and Combined Storage Control (Putaway)................................................... 268 Updating the Inbound Delivery in the GR Process ................................................. 271 Layout-Oriented Storage Control................................................................................ 275 Storage Group......................................................................................................... 276 Slotting............................................................................................................................ 277 SAP APO Interface for Transferring Requirement Data............................................. 279 Update of Results in Product Master.......................................................................... 280 Update Attribute Storage Bin Improvable ............................................................... 281 Consideration of Storage Types ................................................................................. 282 Use of Storage Bin Type Determination Rules........................................................... 283 Simulation of Slotting .................................................................................................. 286 Rearrangement........................................................................................................... 287 Example of Rearrangement .................................................................................... 289 Storage Bin Determination for Putaway ......................................................................... 291 Connection of Delivery Processing to Quality Management.......................................... 293 Counting ......................................................................................................................... 295 Deconsolidation.............................................................................................................. 298 Putaway.......................................................................................................................... 300 Creation of Warehouse Tasks for Putaway ................................................................ 302 Specification of the Putaway Path .............................................................................. 304 Putaway Using Radio Frequency ............................................................................... 306

SAP Extended Warehouse Management (SAP EWM)

510

SAP Online Help

20.07.2007

Manual Assembly of Warehouse Orders.................................................................... 309 Confirmation Correction ................................................................................................. 311 Processing of Non-Putaway-Relevant Delivery Items.................................................... 313 Goods Issue ....................................................................................................................... 314 Stock Removal ............................................................................................................... 317 Creation of Warehouse Tasks for Stock Removal ..................................................... 319 Stock Removal Path Determination............................................................................ 321 Picking ........................................................................................................................ 322 Pick and Pack During Picking ................................................................................. 323 Partial Picking ......................................................................................................... 325 Pick Denial .............................................................................................................. 327 Cancellation of Picking............................................................................................ 329 Processing of Non-Picking-Relevant Delivery Items .................................................. 332 Storage Control .............................................................................................................. 334 Process-Oriented Storage Control ............................................................................. 336 Direct and Combined Storage Control (Stock Removal) ........................................ 337 Updating the Outbound Delivery Order in the GI Process...................................... 339 Layout-Oriented Storage Control................................................................................ 340 Stock Determination ....................................................................................................... 341 Storage Bin Determination for Stock Removal............................................................... 343 Work Center Determination in Goods Issue................................................................... 345 Replenishment Control................................................................................................... 346 Handling Differences When Picking for Warehouse Request........................................ 348 Kit to Order ..................................................................................................................... 349 Kit................................................................................................................................ 352 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 Invoice Creation Before Goods Issue ............................................................................ 368 Print Profile Determination for Invoice Printout........................................................... 372 Putaway and Stock Removal Strategies............................................................................ 374 Putaway Strategies ........................................................................................................ 375 Manual Entry............................................................................................................... 376 Strategy: Fixed Storage Bin........................................................................................ 377 Strategy: General Storage .......................................................................................... 379 Strategy: Addition to Existing Stock............................................................................ 380 Strategy: Empty Storage Bin ...................................................................................... 381

SAP Extended Warehouse Management (SAP EWM)

510

SAP Online Help

20.07.2007

Strategy: Near Fixed Picking Bin ................................................................................ 382 Strategy: Pallet Storage (by HU Type) ....................................................................... 383 Example: Optional HU Check When Creating a WT .............................................. 386 Strategy: Bulk Storage................................................................................................ 387 Cross-Line Stock Putaway.......................................................................................... 390 Capacity Check........................................................................................................... 391 Examples of Capacity Check in Accordance with Capacity Key Figure ................. 394 Stock Removal Strategies .............................................................................................. 396 Strategy: FIFO (First In, First Out).............................................................................. 397 Strategy: Stringent FIFO Across All Storage Types ................................................... 398 Strategy: LIFO (Last In, First Out) .............................................................................. 399 Strategy: Partial Quantities First................................................................................. 400 Strategy: Stock Removal Suggestion According to Quantity ..................................... 402 Strategy: Shelf Life Expiration Date............................................................................ 403 Strategy: Fixed Storage Bin........................................................................................ 404 Warehouse Task ................................................................................................................ 405 Product Warehouse Task............................................................................................... 406 Handling Unit Warehouse Task...................................................................................... 407 Identification Point .......................................................................................................... 408 Pick Point........................................................................................................................ 410 Creation of Warehouse Tasks for Warehouse Request ................................................ 412 Determination of Priority for Inbound Deliveries............................................................. 414 Ad Hoc Movement.......................................................................................................... 415 Posting Change for Stocks............................................................................................. 417 Warehouse Order Creation................................................................................................ 419 Warehouse Order........................................................................................................... 423 Filters for Warehouse Order Creation Rules.................................................................. 424 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 ............................................................ 438 Connecting a Fully Automated Warehouse as a Black Box ................................... 442 Data Flow: EWM Transmits Data ............................................................................... 445 Managing TCP/IP Settings...................................................................................... 448 Managing Transaction Identifiers (TID)................................................................... 449 Data Flow: EWM Receives Data ................................................................................ 452 Data Formatting .......................................................................................................... 454

SAP Extended Warehouse Management (SAP EWM)

510

SAP Online Help

20.07.2007

Description of the IDocs.............................................................................................. 459 IDoc for Sending WTs to a Non-SAP System......................................................... 460 IDoc for Receiving WTs from a Non-SAP System .................................................. 465 IDoc for Confirming Warehouse Tasks ................................................................... 466 IDoc for Canceling Warehouse Tasks .................................................................... 470 IDoc for Releasing Waves....................................................................................... 472 IDoc for Blocking Storage Bins ............................................................................... 473 IDoc for Stock Movement with HUs ........................................................................ 475 IDoc Error Processing................................................................................................. 477 Processing Technical IDoc Errors........................................................................... 478 Processing Logical IDoc Errors in EWM ................................................................. 481 Modification Options ................................................................................................... 483 Modification Concepts: IDoc Inbound Processing .................................................. 484 Modification Concepts: IDoc Outbound Processing ............................................... 487 BAdI Methods for the Interface ............................................................................... 489 Handling Unit (HU)............................................................................................................. 490 Packaging Materials ....................................................................................................... 492 Packaging Specification ................................................................................................. 494 Creation of Packaging Specifications ......................................................................... 497 Packaging Specification Determination ...................................................................... 499 Distribution of Packaging Specifications..................................................................... 502 Unique Identification of Handling Units .......................................................................... 504 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 Packing using Radio Frequency..................................................................................... 513 Printing Handling Unit Documents ................................................................................. 514 Stock Identification............................................................................................................. 517 Stock Identification in the GR and GI Processes ........................................................... 518 Usage of Stock Identification.......................................................................................... 521 Stock Identification When Splitting Warehouse Tasks................................................... 523 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 Receipt Process with VAS Order........................................................................ 530 Goods Issue Process with VAS Order ........................................................................... 533 Create and Edit VAS Orders .......................................................................................... 536

SAP Extended Warehouse Management (SAP EWM)

510

10

SAP Online Help

20.07.2007

Processing a VAS Order ................................................................................................ 538 Auxiliary Product Consumption Posting ......................................................................... 542 Cross-Docking (CD)........................................................................................................... 544 Transportation Cross-Docking (TCD)............................................................................. 547 Example Scenario for TCD with Storage Control ....................................................... 553 Detailed Process Description...................................................................................... 555 Push Deployment (PD) and Pick from Goods Receipt (PFGR) ..................................... 559 Example Scenario for PD/PFGR with Storage Control .............................................. 564 Additional Functions in Cross-Docking .......................................................................... 568 Business Add-Ins in Cross-Docking ........................................................................... 569 Make Settings for Exception Handling in CD.............................................................. 570 Serial Number .................................................................................................................... 571 Serial Number Profile ..................................................................................................... 573 Provisional Serial Number.............................................................................................. 575 Using the Serial Number Requirement .......................................................................... 576 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 Using Serial Numbers in the Delivery......................................................................... 590 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 Complex Loading and Unloading ................................................................................... 610 Loading and Unloading Using Radio Frequency............................................................ 611 Vehicle............................................................................................................................ 612 Transportation Unit ..................................................................................................... 613 Creating Vehicles and Transportation Units ............................................................... 614 Staging Area and Door Determination ........................................................................... 615 Assignment of Deliveries to Vehicles and TUs .............................................................. 617 Printer and Form Determination in Shipping and Receiving .......................................... 618 Yard Management.......................................................................................................... 619

SAP Extended Warehouse Management (SAP EWM)

510

11

SAP Online Help

20.07.2007

Yard ............................................................................................................................ 621 Checkpoint .................................................................................................................. 622 Arrival at/Departure from Checkpoint...................................................................... 623 Shipping and Receiving Activity ................................................................................. 624 Yard Movement .......................................................................................................... 626 Yard Movement Using Radio Frequency ................................................................ 628 Transportation Management in EWM ............................................................................ 629 Shipment..................................................................................................................... 630 Freight Document ....................................................................................................... 632 Creation of Freight Documents................................................................................... 633 Integration of TM with the Loading Process ............................................................... 635 Printer and Form Determination in Transportation Management ............................... 636 Authorizations in Transportation Management........................................................... 637 Route Determination ...................................................................................................... 638 Route .......................................................................................................................... 641 Cross-Docking Route .............................................................................................. 644 Zone............................................................................................................................ 646 Carrier Profile for the Routing Guide .......................................................................... 647 General Transportation Cost Profile ........................................................................... 649 Hierarchical Relationships Between Means of Transport........................................... 651 Static Route Determination......................................................................................... 653 Route Determination as Part of Cross-Docking...................................................... 655 Scheduling .................................................................................................................. 656 Results of Scheduling ............................................................................................. 658 Calculation of Transportation Costs ........................................................................... 660 Simulation of Route Determination............................................................................. 662 Distribution of Master Data ......................................................................................... 666 Physical Inventory.............................................................................................................. 667 Periodic Physical Inventory Procedure .......................................................................... 669 Continuous Physical Inventory Procedures ................................................................... 670 Cycle Counting ............................................................................................................... 673 Processing of Physical Inventory Documents ................................................................ 674 Difference Analysis......................................................................................................... 677 Physical Inventory Progress........................................................................................... 680 Reports in Physical Inventory......................................................................................... 682 Physical Inventory Using Radio Frequency ................................................................... 684 Labor Management (LM) ................................................................................................... 685 Activating Labor Management (LM) ............................................................................... 686 Master Data in Labor Management (LM) ....................................................................... 688 Processor.................................................................................................................... 689

SAP Extended Warehouse Management (SAP EWM)

510

12

SAP Online Help

20.07.2007

Formula and Condition Editor ..................................................................................... 691 Formula Editor......................................................................................................... 694 Condition Editor....................................................................................................... 696 Indirect Labor.................................................................................................................. 698 Indirect Labor Tasks Using Radio Frequency ............................................................ 701 Function Key Settings for Indirect Labor Tasks in the RF Environment ................. 702 Engineered Labor Standards ......................................................................................... 704 Configuring Engineered Labor Standards (ELS)........................................................ 706 Uploading Engineered Labor Standards (ELS) .......................................................... 708 Example for Engineered Labor Standards ................................................................. 711 Planned and Executed Workload ................................................................................... 713 Planned Workload Document ..................................................................................... 715 Executed Workload Document ................................................................................... 716 Planned Workload ...................................................................................................... 717 Executed Workload..................................................................................................... 718 Interaction Between Performance Document and Executed Workload.................. 719 Labor Management (LM) in the Warehouse Management Monitor............................ 720 Preprocessing ................................................................................................................ 722 Preprocessing for Deliveries and Physical Inventory ................................................. 725 BAdIs for Preprocessing ............................................................................................. 727 Operational Planning...................................................................................................... 728 Simulation of Planning ................................................................................................ 731 Employee Performance.................................................................................................. 732 Performance Document.............................................................................................. 736 Performance Document Status................................................................................... 737 Performance Document and Connection to an HR System ....................................... 738 Analytical Functions ........................................................................................................... 739 Warehouse Cockpit ........................................................................................................ 741 Measurement Services................................................................................................... 744 Tailored Measurement Service (TMS)........................................................................ 747 Calculated Measurement Service (CMS) ................................................................... 748 Evaluation of Measurement Services ......................................................................... 749 Resource Management...................................................................................................... 750 Resource ........................................................................................................................ 752 Resource Type ........................................................................................................... 753 Resource Group ......................................................................................................... 754 Assignment of Warehouse Order to Resource .............................................................. 755 Warehouse Order Selection ....................................................................................... 757 Mode ....................................................................................................................... 759 Latest Starting Date (LSD) ...................................................................................... 760

SAP Extended Warehouse Management (SAP EWM)

510

13

SAP Online Help

20.07.2007

Warehouse Order Prioritization............................................................................... 761 Queue ......................................................................................................................... 764 Wave Management............................................................................................................ 766 Wave Template .............................................................................................................. 767 Wave .............................................................................................................................. 769 Processing of Waves .................................................................................................. 771 Automatic Wave Assignment...................................................................................... 773 Two-Step Picking........................................................................................................ 778 Radio Frequency Framework............................................................................................. 781 RF Navigation................................................................................................................. 783 RF Function Keys........................................................................................................... 786 Standard RF Functionalities ........................................................................................... 789 Logon .......................................................................................................................... 790 Logoff .......................................................................................................................... 793 Recovery..................................................................................................................... 794 Position Management ................................................................................................. 795 Work Processing Using Radio Frequency ..................................................................... 797 Loading and Unloading Using Radio Frequency........................................................ 798 Deconsolidation Using Radio Frequency ................................................................... 799 Putaway Using Radio Frequency ............................................................................... 800 Confirmation Correction Using Radio Frequency ....................................................... 803 Picking ........................................................................................................................ 804 RF Picking Flow ...................................................................................................... 805 Packing using Radio Frequency................................................................................. 807 Physical Inventory Using Radio Frequency................................................................ 808 Ad Hoc Movements Using Radio Frequency.............................................................. 809 Yard Movement Using Radio Frequency.................................................................... 811 Querying Using Radio Frequency .............................................................................. 812 Resource Management Using Radio Frequency........................................................ 814 Handling Unit Differences Using Radio Frequency .................................................... 815 Enhancement Screen Wizard......................................................................................... 816 Split Screen Wizard........................................................................................................ 818 Material Flow System (MFS).............................................................................................. 820 Structure of the MFS ...................................................................................................... 824 Programmable Logic Controller (PLC) ....................................................................... 825 Communication Channel ............................................................................................ 826 Communication Point.................................................................................................. 827 Conveyor Segment ..................................................................................................... 828 Resource..................................................................................................................... 829 Set Up the Material Flow System ................................................................................... 830

SAP Extended Warehouse Management (SAP EWM)

510

14

SAP Online Help

20.07.2007

Repeating or Resending an Acknowledged Telegram................................................... 834 MFS in the Warehouse Management Monitor ............................................................... 835 Analyze Logs .............................................................................................................. 837 MFS in the Easy Graphics Framework .......................................................................... 838 Status Management ....................................................................................................... 839 Exception Handling ........................................................................................................ 841 Business Contexts ...................................................................................................... 842 Internal Exceptions ..................................................................................................... 845 Internal Process Codes .............................................................................................. 847 MFS in the Alert Monitor................................................................................................. 850 Quality Management (QM)................................................................................................. 851 Customizing Settings for QM in EWM............................................................................ 853 Master Data .................................................................................................................... 855 QM-Specific Master Data............................................................................................ 856 Creation of Inspection Rule ........................................................................................ 857 Sample-Drawing Procedure........................................................................................ 860 Quality Level ............................................................................................................... 862 Dynamic Modification.................................................................................................. 863 Quality Inspection........................................................................................................... 866 Inspection Process ..................................................................................................... 867 Creation of Inspection Document ............................................................................... 869 Inspection Object Types ............................................................................................. 871 Findings ...................................................................................................................... 873 Inspection Decision..................................................................................................... 874 Logistical Follow-Up Actions....................................................................................... 876 Warehouse Management Monitor .............................................................................. 878 Monitor Basic Operations........................................................................................ 880 Monitor Methods ..................................................................................................... 882 Quality Inspection Using Radio Frequency (RF)............................................................ 886 Quality Inspection Engine............................................................................................... 888 Quality Inspections with the QIE................................................................................. 890 Determination of the Sample Size .............................................................................. 894 System Interaction ...................................................................................................... 897 Inspection Object Type ............................................................................................... 900 Inspection Rule ........................................................................................................... 901 Inspection Procedure .............................................................................................. 902 Sample Determination............................................................................................. 903 Sampling Procedure ............................................................................................ 904 Sampling Scheme ............................................................................................... 905 Sampling Plan ..................................................................................................... 906

SAP Extended Warehouse Management (SAP EWM)

510

15

SAP Online Help

20.07.2007

Dynamic Modification .............................................................................................. 907 Dynamic Modification Criteria.............................................................................. 910 Dynamic Modification Rule .................................................................................. 911 Quality Level........................................................................................................ 912 Dynamic Modification at Inspection Document Creation ................................. 913 Dynamic Modification at Inspection Decision .................................................. 915 Sample-Drawing Procedure .................................................................................... 917 Sample-Drawing Unit........................................................................................... 919 Sample-Drawing Instruction............................................................................. 920 Document Assignment................................................................................................ 921 Inspection Document .................................................................................................. 922 Inheritance of Inspection Specifications.................................................................. 923 Sample .................................................................................................................... 925 Item ......................................................................................................................... 926 Findings ...................................................................................................................... 927 Catalog........................................................................................................................ 929 Inspection Decision..................................................................................................... 930 Archiving - Inspection Documents (CA-QIE) .............................................................. 931 Inspections (CA-QIE) .............................................................................................. 933 Application Customizing (CA-QIE).......................................................................... 934 Preprocessing: Editing Variants (CA-QIE) .............................................................. 935 Writing: Editing Variants (CA-QIE).......................................................................... 936 Deleting: Editing Variants (CA-QIE)........................................................................ 937 Authorizations (CA-QIE).......................................................................................... 938 Log (CA-QIE) .......................................................................................................... 939 Displaying Archived Inspection Documents (CA-QIE)............................................ 941 Quality Inspection Engine (QIE) Security Guide......................................................... 942 Introduction ............................................................................................................. 943 Before You Start...................................................................................................... 945 Technical System Landscape ................................................................................. 946 User Administration and Authentication.................................................................. 947 User Management ............................................................................................... 948 Integration into Single Sign-On Environments .................................................... 949 Authorizations ......................................................................................................... 950 Network and Communication Security.................................................................... 952 Communication Channel Security ....................................................................... 953 Network Security ................................................................................................. 954 Communication Destinations............................................................................... 955 Data Storage Security ............................................................................................. 956 Security for Additional Applications......................................................................... 957

SAP Extended Warehouse Management (SAP EWM)

510

16

SAP Online Help

20.07.2007

Other Security-Relevant Information....................................................................... 958 Trace and Log Files ................................................................................................ 959 Appendix ................................................................................................................. 960 Customs Procedure ........................................................................................................... 961 Safekeeping.................................................................................................................... 962 Customs Warehousing Procedure ................................................................................. 964 Scrapping as Part of the Customs Warehousing Procedure...................................... 965 EH&S Services................................................................................................................... 967 Phrase Management ...................................................................................................... 968 Hazardous Substance Master ........................................................................................ 969 List of Hazardous Substances for Fire Department ....................................................... 971 Dangerous Goods Management .................................................................................... 973 General Functions.............................................................................................................. 976 Interfaces........................................................................................................................ 977 Transfer Storage Bin or Storage Bin Sorting .............................................................. 978 Transfer Stock Data.................................................................................................... 979 Integration of PPF and the Condition Technique ........................................................... 981 Authorizations................................................................................................................. 985 Roles for Extended Warehouse Management (EWM) ...................................................... 987 EWM: Warehouse Manager ........................................................................................... 988 EWM: Warehouse Expert............................................................................................... 993 EWM: Warehouse Specialist for Goods Receipt.......................................................... 1001 EWM: Warehouse Specialist for Goods Issue ............................................................. 1004 EWM: Warehouse Specialist for Yard Management.................................................... 1007 EWM: Warehouse Worker............................................................................................ 1009 EWM: Physical Inventory Planner ................................................................................ 1011 EWM: Physical Inventory Counter ............................................................................... 1013 EWM: Displaying Warehouse Information ................................................................... 1014 EWM: ERP Integration ................................................................................................. 1015 EWM Labor Planner ..................................................................................................... 1016 EWM: Warehouse Analyst ........................................................................................... 1017 EWM: Warehouse Specialist for Labor Management .................................................. 1018 Data Archiving.................................................................................................................. 1019 Introduction to Data Archiving (CA-ARC)..................................................................... 1020 Archiving in Extended Warehouse Management (SCM-EWM) ................................... 1022 Archiving in Delivery Processing (SCM-ECT-DLP) .................................................. 1024 Archiving Internal Warehouse Requests (Inb. Del.) (SCM-ECT-DLP) ................. 1026 Archiving Internal Warehouse Requests (SCM-ECT-DLP) .................................. 1028 Archiving Warehouse Requests from External Systems (SCM-ECT-DLP) .......... 1030 Archiving in Quality Management............................................................................. 1032

SAP Extended Warehouse Management (SAP EWM)

510

17

SAP Online Help

20.07.2007

Archiving - Inspection Documents (CA-QIE)......................................................... 1033 Inspections (CA-QIE)......................................................................................... 1035 Application Customizing (CA-QIE) .................................................................... 1036 Preprocessing: Editing Variants (CA-QIE) ........................................................ 1037 Writing: Editing Variants (CA-QIE) .................................................................... 1038 Deleting: Editing Variants (CA-QIE) .................................................................. 1039 Authorizations (CA-QIE) .................................................................................... 1040 Log (CA-QIE)..................................................................................................... 1041 Displaying Archived Inspection Documents (CA-QIE) ...................................... 1043 Archiving in Shipping and Receiving ........................................................................ 1044 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 for Value-Added Services ......................................................................... 1059 Archiving Value-Added Service Orders (SCM-EWM-VAS) .................................. 1060 Archiving in Wave Management (SCM-EWM-WAV)................................................ 1062 Archiving Waves (SCM-EWM-WAV) .................................................................... 1063 Archiving in Warehouse Order Processing (SCM-EWM-WOP) ............................... 1065 Archiving Telegram Flows (SCM-EWM-WOP) ..................................................... 1066 Archiving Relevant Resource Data (SCM-EWM-WOP-RM)................................. 1068 Archiving Warehouse Tasks (SCM-EWM-WOP) .................................................. 1070 Archiving Warehouse Orders (SCM-EWM-WOP) ................................................ 1072 Archiving in Labor Management (SCM-EWM-LM) ................................................... 1074 Archiving Performance Documents (SCM-EWM-LM-EP)..................................... 1075 Archiving Executed Workload (SCM-EWM-LM-WL)............................................. 1077 Archiving Indirect Labor Tasks (SCM-EWM-LM-ILT) ........................................... 1078

SAP Extended Warehouse Management (SAP EWM)

510

18

SAP Online Help

20.07.2007

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 component Inventory 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. EWM optimizes warehouse capacities and material flows using putaway and stock removal strategies that you can adjust to your needs, or by you using handling units [Seite 490].

SAP Extended Warehouse Management (SAP EWM)

510

19

SAP Online Help

20.07.2007

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 at Warehouse 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
EWM also contains an interface to external systems (warehouse control units). This enables you to integrate automated putaway and stock removal systems, or forklift control systems for all stock movements using this Application Link Enabling interface (ALE interface) in the warehouse management system.

SAP Extended Warehouse Management (SAP EWM)

510

20

SAP Online Help

20.07.2007

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 Type

Storage Type

Storage Type

Storage Sec.
Activity Area Storage Bin

Storage Section

Storage Bin

Quant

Quant

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 Each storage type is divided into storage sections. All storage bins with specific common attributes belong to one storage section, for example, storage bins for fastmoving items that are close to the goods issue zone.

SAP Extended Warehouse Management (SAP EWM)

510

21

SAP Online Help

20.07.2007

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
... ...

1. Define Warehouse Numbers 2. Define Storage Type 3. Define Storage Section 4. Storage Bins Define Storage Bin Types 5. Activity Areas Define Activity Area 6. Activity Areas Assign Storage Bins to Activity Areas
...

SAP Extended Warehouse Management (SAP EWM)

510

22

SAP Online Help

20.07.2007

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 and packaging 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 a supply 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 under Extended 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
The warehouse for company XYZ includes the following facilities: Goods receipt area Goods issue area Hall with high rack shelves Bulk storage area Activity areas of category Picking with Fixed Bins

SAP Extended Warehouse Management (SAP EWM)

510

23

SAP Online Help

20.07.2007

Storage space outdoors for special substances

Each of the storage facilities listed above is called a storage type [Seite 25] in EWM. EWM groups these facilities together under a warehouse number.

SAP Extended Warehouse Management (SAP EWM)

510

24

SAP Online Help

20.07.2007

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-used physical storage types in EWM: Bulk storage area General storage area High rack storage area Fixed bin storage area Rack 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 Bulk storage area Fixed bin 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)

Some control indicators for storage types are mutually exclusive, and certain combinations of indicators cannot be permitted for legal reasons or due to internal guidelines. In these cases, the system generates an error message. We recommend that you check and test all new combinations carefully, before you release them in the production system. SAP Extended Warehouse Management (SAP EWM) 510 25

SAP Online Help

20.07.2007

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 under Extended 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:

Warehouse Number 0001 Storage Type 9020 GR Area Goods Receipt High Rack Storage Area Storage Type 0040 Storage Type 0010

Block Storage Area Storage Type 9100 GI Area Fixed Bin Storage Area Goods Issue Storage Type 0050

SAP Extended Warehouse Management (SAP EWM)

510

26

SAP Online Help

20.07.2007

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 Bin subdivision Depth Information about the storage type 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) for Extended 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 information, see the IMG for EWM under Master Data Activity Area Generate Activity Area from Storage Type. In this case, the activity area has the same storage bins as the storage type.

SAP Extended Warehouse Management (SAP EWM)

510

27

SAP Online Help

20.07.2007

Integration
EWM generates warehouse orders [Seite 419] for each activity area. When EWM generates warehouse tasks, it considers the activity area and copies attributes from this activity area, such as the deconsolidation group.

SAP Extended Warehouse Management (SAP EWM)

510

28

SAP Online Help

20.07.2007

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 the storage 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 slowmoving items.
Storage bin 02-02-03

Bin type

High bins

Low bins Slow-moving items Low bins Fast-moving items

Storage section

SAP Extended Warehouse Management (SAP EWM)

510

29

SAP Online Help

20.07.2007

Storage Bin
Definition
A storage type consists of a selection of storage spaces, which are called storage 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
You can use any combination of letters and numbers for storage bin coordinates. However, you should ensure that you orient the parts of the structure to the indicators defined for the warehouse for aisle, stack, level, and so on.

SAP Extended Warehouse Management (SAP EWM)

510

30

SAP Online Help

20.07.2007

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 Number Batch number Stock category type Stock category Stock usage

SAP Extended Warehouse Management (SAP EWM)

510

31

SAP Online Help

20.07.2007

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 Staging areas Staging bays 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 under Master 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 role F. You can also assign doors to supply chain units [Seite 53] to control authorization checks. You can also assign doors to yard bins (see Yard Management [Seite 619]). See also: Staging Area and Door Determination [Seite 615]

SAP Extended Warehouse Management (SAP EWM)

510

32

SAP Online Help

20.07.2007

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) for Extended 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: Staging Area and Door Determination [Seite 615]

SAP Extended Warehouse Management (SAP EWM)

510

33

SAP Online Help

20.07.2007

SAP Extended Warehouse Management (SAP EWM)

510

34

SAP Online Help

20.07.2007

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 Quality Inspection

Extended Warehouse Management (EWM) contains the following transaction types for the work center: Packing - General This transaction type is for all general repacking transactions. Deconsolidation This transaction type is for distributing mixed handling units (HUs) into HUs for nonmixed 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 criterion Stop 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 under Extended 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: Work center 1 represents the deconsolidation work center, which has no inbound section and no outbound section. Work center 2 represents the deconsolidation work center, which has an outbound section but no inbound section. Work center 3 represents the deconsolidation work center, which has both an inbound section and an outbound section.

SAP Extended Warehouse Management (SAP EWM)

510

35

SAP Online Help

20.07.2007

Work Center WC1

Work Center WC2

Work Center WC3 WC3I Deconsolidation HU Putaway-HU WC3I-01 WC3I-02

WC1

WC2

WC3

Inb. Section Work Center

Work Center

0001

0001

0001

Outb. Section Work Center

WC2O-01WC2O-02WC2O-03

WC3O-01 WC3O-02WC3O-03

Storage Bin

Storage Type 8000

WC2O

WC3O

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. The system only determines the final storage bin, and thus the work center, when you confirm the warehouse task.

SAP Extended Warehouse Management (SAP EWM)

510

36

SAP Online Help

20.07.2007

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, see Logon [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 Master Data Resource Management /SCWM/RSRC Maintain Resource. Alternatively you can define a resource by using the warehouse management monitor (method [Seite 882] Maint. Resource).

SAP Extended Warehouse Management (SAP EWM)

510

37

SAP Online Help

20.07.2007

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 corresponding resources [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) regarding bin 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. You maintain the qualification priority values using the execution priority maintenance transaction, accessed on the SAP Easy Access screen (Extended Warehouse Management Master Data Resource Management /SCWM/EXECPR - Maintain Execution Priorities).

SAP Extended Warehouse Management (SAP EWM)

510

38

SAP Online Help

20.07.2007

Resource Group
Definition
A resource group is a grouping of resources for queue [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 the SAP Easy Access screen (Extended Warehouse Management Master Data Resource Management /SCWM/QSEQ - Maintain Queue Sequence for Resource Group), or from the warehouse management monitor [Seite 878] (Assign Queue/Unassign Queue methods [Seite 882]).

SAP Extended Warehouse Management (SAP EWM)

510

39

SAP Online Help

20.07.2007

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 in EWM. You can create or change a warehouse product via the SAP menu under Extended 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 For more information, see Slotting [Seite 277]. 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

For more information about the transfer and maintenance of this data, see the Implementation Guide (IMG) for EWM under Master Data Product Settings in the ERP System.

SAP Extended Warehouse Management (SAP EWM)

510

40

SAP Online Help

20.07.2007

SAP Extended Warehouse Management (SAP EWM)

510

41

SAP Online Help

20.07.2007

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 under SAP ERP Central Component Logistics Environment, Health and Safety (EHS) Hazardous Substance Management (EHS-HSM) Hazardous Substance Master Hazardous

Substance.

SAP Extended Warehouse Management (SAP EWM)

510

42

SAP Online Help

20.07.2007

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 Product

Contents

OR or

Packaging specification Level 1 EG 1 Element 1 Element 2 Level 2 EG 2 Element 1 Pack. mat. Pack. mat. Pack. mat. Work step Work step Work step

Level n

EG n

Element 1

Pack. mat.

Work step

Header Attributes such as the name of the packaging specification, user name of the creation user, status, and so on.

SAP Extended Warehouse Management (SAP EWM)

510

43

SAP Online Help

20.07.2007

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
The following figure shows which processes use the packaging specification, and using which components:

SAP Extended Warehouse Management (SAP EWM)

510

44

SAP Online Help

20.07.2007

Processes for the Packaging Specification

Inb. delivery/ASN

Putaway-WT Stock-removal-WT Slotting Palletization Whse-int. processes

Pick-HU proposal

ATP sourcing

MM deployment

Automatic packing

Warehouse order

Rounding rules

ICH

EWM

APO

Packaging Specification
iPPE Cond. technique

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 [Seite 497]) Determine (see also: Packaging Specification Determination [Seite 499]) in mehrere Systeme verteilen.

SAP Extended Warehouse Management (SAP EWM)

510

45

SAP Online Help

20.07.2007

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 in route determination [Seite 638]. The following figure shows a route with three legs that are connected by the transshipment locations P and M. It also shows a (red) trip for the case where all stop-offs in the middle leg are optional and a (blue) trip for the case where these stop-offs are mandatory.
Transshipment Location P
Le g

Destination Location Z

Start Location A

Transshipment Location M

Trip (Skipping Not Allowed) Trip (Skipping Allowed) Route

You can form cross-docking routes [Seite 644] from routes.

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 a supply 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 At stop level, you can assign a mode of transport for foreign trade to each location. The system then takes into account this mode of transport for outbound shipments in the case of exports. The value that represents this mode of transport is dependent on the country in which the location lies. The system does not check if the mode of transport semantically matches the means of transport used for the leg of this location. Since, in most cases, the system cannot define a unique country for zones, it does not permit you to define a mode of transport for such stops.

SAP Extended Warehouse Management (SAP EWM)

510

46

SAP Online Help

20.07.2007

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 when scheduling [Seite 656] a trip for both the start location of the request and for each transshipment location served. Validity and Restrictions 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

47

SAP Online Help

20.07.2007

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. You can also define various lead times for the different request types. These influence the start time of a trip in scheduling.

SAP Extended Warehouse Management (SAP EWM)

510

48

SAP Online Help

20.07.2007

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 the CD 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 the CD 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 location CD 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 for Extended Warehouse Management (EWM) under Master Data Shipping and Receiving Route Determination Maintain Route.

Example
The following figure shows a route network consisting of two CD routes:

SAP Extended Warehouse Management (SAP EWM)

510

49

SAP Online Help

20.07.2007

Cross-Docking Route 2 CrossDocking Location 2

e6 Rout

Rou (Inb te 1 oun d)

3 ute Ro

Rou te 5

ute Ro

CrossDocking Location 1

Rou (Ou te 4 tbo und )

Cross-Docking Route 1

See also: Route Determination as Part of Cross-Docking [Seite 655]

SAP Extended Warehouse Management (SAP EWM)

510

50

SAP Online Help

20.07.2007

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 [Seite 635]). Before goods issue posting, you can create the current invoice via an invoice request to SAP CRM Billing (see Invoice Creation Before Goods Issue [Seite 368]).

Example
The truck with the license plate number HSK-116 has a trailer. This means that it consists of two transportation units: The cargo area and the trailer.

SAP Extended Warehouse Management (SAP EWM)

510

51

SAP Online Help

20.07.2007

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 3: Train with four wagons, in other words, four transportation units
Transportation Unit 1

Vehicle 1

Vehicle 2

Transportation Unit 1

Transportation Unit 2

Vehicle 3 TU 1 TU 2 TU 3 TU 4

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
The following are additional examples of transportation units: Compartment in a tank truck Container

SAP Extended Warehouse Management (SAP EWM)

510

52

SAP Online Help

20.07.2007

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 as door 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, under Extended 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 Address data of the location/SCU Business Character One or more business characters of the SCU.

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 character planning 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 character planning 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. If you create an SCU with the business character Warehouse, the system does not create a corresponding location.

SAP Extended Warehouse Management (SAP EWM)

510

53

SAP Online Help

20.07.2007

SAP Extended Warehouse Management (SAP EWM)

510

54

SAP Online Help

20.07.2007

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 Internal goods movements Posting changes Goods receipt postings Goods issue postings

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]
PROD WT

HU WT

HU WT

PROD WT HU WT

Product Warehouse Task Handling Unit Warehouse Task

You or the system use product warehouse tasks, for example, for deconsolidation [Seite 298] and handling unit warehouse tasks, for example, for unloading [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, see Pick Point [Seite 410]. EWM also submits hazardous substance texts [Seite 969] in the warehouse task. When you confirm a warehouse task, you can also perform a physical inventory at the same time [Seite 670]. Here, EWM can work with the low-stock physical inventory.

SAP Extended Warehouse Management (SAP EWM)

510

55

SAP Online Help

20.07.2007

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
EWM creates warehouse tasks for an outbound delivery with four delivery items. EWM uses warehouse order creation to assign the resulting four warehouse tasks to a new warehouse order. A warehouse employee receives this warehouse order as a work package to pick the items listed in the delivery.

SAP Extended Warehouse Management (SAP EWM)

510

56

SAP Online Help

20.07.2007

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.
Pallet = HU 110 Pallet = HU 120 Container = HU 100

Package HU 111

Package HU 112

Package HU 121

Package HU 122

SAP AG

Filename

Date/ 1

Fig. 1: Example of a Handling Unit

Structure
The object Handling Unit contains the following attributes: Identification number Dimension Weight Volume Status Products and quantities 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 General data Storage-specific data

SAP Extended Warehouse Management (SAP EWM)

510

57

SAP Online Help

20.07.2007

For more information about the different detailed information, see Packing 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


The items of a handling unit can consist of products, auxiliary packaging materials, or other handling units, which are displayed in an overview. For more information about this overview, see Packing at the Work Center [Seite 506].

SAP Extended Warehouse Management (SAP EWM)

510

58

SAP Online Help

20.07.2007

Monitoring
Purpose
The following options are available to you in monitoring: Warehouse Management Monitor [Seite 878] Easy Graphics Framework [Seite 68]

SAP Extended Warehouse Management (SAP EWM)

510

59

SAP Online Help

20.07.2007

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
You have accessed the warehouse management monitor by:
...

1. Choosing Extended Warehouse Management Monitoring /SCWM/MON Warehouse Management Monitor on the SAP Easy Access screen. 2. Entering the warehouse number and name of the monitor. 3. Choosing Execute.

Features
Upper View Area

Node Hierarchy Tree

Lower View Area

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: Documents such as warehouse requests (WRs) [Extern], warehouse orders (WOs), warehouse tasks (WTs), and physical inventory documents 510 60

SAP Extended Warehouse Management (SAP EWM)

SAP Online Help

20.07.2007

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, see Monitor 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. Creating variant nodes enables you to create your own nodes, which are based on the standard nodes, but with specific selection criteria, or with a specific layout. Variant nodes are always available when the user utilizes the monitor.

SAP Extended Warehouse Management (SAP EWM)

510

61

SAP Online Help

20.07.2007

Monitor Basic Operations


Use
Functions Function Hide a selected node in the hierarchy tree Show hidden nodes What You Should Know This operation is invoked by choosing the Hide Node option in the nodes context menu. This operation is invoked by choosing Show Hidden Nodes. After choosing this option, previously hidden nodes are displayed in the icon. hierarchy tree, with the Unhide a selected node in the hierarchy tree This operation is invoked by choosing the Unhide Node option in the nodes context menu. After choosing this option, the node icon changes to (regular node) or (variant node). Create a variant node in the hierarchy tree There are two options from the nodes 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 nodes 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 nodes context menu. This operation is invoked by choosing the Rename Node option in the nodes context menu. This operation is invoked either by double-clicking the node, or choosing the Set Selection Criteria option in the nodes context menu.

Change variant node text

Display in list view object information for a node

SAP Extended Warehouse Management (SAP EWM)

510

62

SAP Online Help

20.07.2007

Expand all nodes in the hierarchy tree Collapse all nodes in the hierarchy tree Display object information of a lower-level node in the higherlevel nodes list view

This operation is invoked by choosing in the top tool bar. This operation is invoked by choosing in the top tool bar. 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 again. to list view, by choosing

Show display transaction for object

For some objects, such as warehouse task (WT), warehouse order (WO), wave, inbound delivery, outbound delivery, and storage bin, you can go directly to the relevant display transaction. You call this function by choosing the required object in the ALV, which in this case is indicated by a hotspot. For some objects, you can select multiple rows, and use the ALV tool bar to branch to the display transaction of multiple objects of the same type. The display transaction is shown in a new session. If you set parameter /SCWM/MONNAV to X in the user profile, the display is started in the same session.

SAP Extended Warehouse Management (SAP EWM)

510

63

SAP Online Help

20.07.2007

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 for Extended 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.

Activities
Standard Monitor Methods Method Name Display Bin BIN Change Bin Print HU WO Reprint HU WT WO Display HU Display PI Doc. Process PI Doc. HU PIDIFF PIDLOC PIDSTK PIHHU PIHIST PIHLOC PIHREF Handling Unit Warehouse Order Handling Unit Warehouse Task Warehouse Order Handling Unit Differences-{}Storage Bin Product Handling Unit Doc. History Storage Bin References Enables you to display detailed information for an HU at a work center Enables you to display or process a physical inventory document (transaction /SCWM/PI_PROCESS) Enables you to reprint HU, WT or WO details Storage Bin Enables you to change data of the selected storage bin (transaction /SCWM/LS02) Enables you to print HU or WO details Object Class Name Presentation Text Displays data for the selected storage bin (transaction /SCWM/LS03) Description

SAP Extended Warehouse Management (SAP EWM)

510

64

SAP Online Help

20.07.2007

PIHSTK PISLOC Maint. Resource Logon Resource Logoff Resource Send Message Assign Queue Unassign Queue Simulate WO RSRCG R

Product Storage Bin Enables you to maintain a selected resource [Seite 752] (transaction /SCWM/RSRC) Enables you to log on a selected resource to the desktop environment Enables you to log off a selected resource from the desktop environment Enables you to create and send a message to one or more selected resources Enables you to assign/unassign a queue [Seite 764] to/from the selected resource group [Seite 754] (transaction /SCWM/QSEQ)

RSRC

Resource

Resource Group

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

Displays the application log for a selected WT Enables you to unassign one or more WTs from a WO, and group them into a newly-created WO. Using this method, you can determine the warehouse 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. You can also specify a reason for the split, which is stored in the exception log for WOs.

WT

Warehouse Task

Assign WT Unassign WT

Enables you to assign one or more selected WTs to a specified WO Enables you to unassign one or more selected WTs from a specified WO

To execute the WTs, you will need to assign them to a WO. Cancel WT Confirm Foregr. Confirm Backgr. Create User Maintain User Enables you to cancel a WT Enables you to confirm in the foreground one or more selected WTs or WOs (transaction /SCWM/TO_CONF) Confirms in the background one or more selected WTs or WOs Enables you to create/maintain a user (transaction /SCWM/USER)

WT WO

Warehouse Task Warehouse Order

USER

User(s)

SAP Extended Warehouse Management (SAP EWM)

510

65

SAP Online Help

20.07.2007

Hold Wave

Sets the status of the selected waves [Seite 769] to On Hold. Waves of this status cannot be released until their status is changed back to Initial

Unhold Wave

Sets the status of the selected waves to Initial

You can perform this method only on waves of status On Hold. Delete Wave WAVE Merge Wave Wave Deletes the selected waves. All the wave items are unassigned from the waves Merges the selected waves into one wave. The merged wave inherits its attributes from the first wave Enables you to change the attributes of a selected wave Releases one or more selected waves

Change Wave Release Wave

You can release only those waves of status Initial. Subsyste m Split WAVITM Unassign Assign to Wave WAVITM WHRITO WHRI Wave Item Warehouse Request Item Warehouse Request (Inbound) Warehouse Request (Outbound) Warehouse Request (Inbound) Warehouse Request (Outbound) Warehouse Request Item (Inbound) Warehouse Request Item (Outbound) Warehouse Order Displays the application log for a selected WO Displays the inspection document(s) and inspection outcomes for a selected WR or WR item Wave Item Activates the WOs and WTs sent to a subsystem Splits the selected wave items from their waves, and creates a new wave for them Unassigns the selected wave items from the wave Enables you to assign one or more selected wave items or WR items to a specified wave

Display WR

Enables you to display details of a selected WR (transactions /SCWM/PRDI and /SCWM/PRDO)

WHRO

Displ. Insp.Doc

WHRI

WHRO

WHRITI

WHRITO

Display WO Log

WO

SAP Extended Warehouse Management (SAP EWM)

510

66

SAP Online Help

20.07.2007

Merge WOs

Enables you to merge selected open WOs, which unassigns the WTs from the WOs, and groups them into a newly-created WO. Using this method, you can determine the warehouse 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. You can also specify a reason for the merge, which is stored in the exception log for WOs.

Hold WO

Sets the status of one or more selected WOs to Waiting. The WO cannot be executed until its status is set to Open.

Open WO Add WO Assign Rsrce Unassign Rsrce Queue ndern Change LSD

Sets the status of one or more selected WOs to Open. Adds an empty WO to a super WO (loading/unloading scenario) Enables you to assign/unassign a resource to/from one or more selected WOs

Enables you to change the queue to which the selected WOs are assigned Enables you to change the latest starting date (LSD) [Seite 760] of the selected WOs

SAP Extended Warehouse Management (SAP EWM)

510

67

SAP Online Help

20.07.2007

Easy Graphics Framework


Purpose
The Easy Graphics Framework (EGF) is a generic tool that you can use for the simple configuration of cockpits for applications such as Extended Warehouse Management (EWM), which you can use in addition to text-based monitors and to display your data graphically. Multiple users can work with the EGF cockpit at the same time.

For more information about an example implementation, see Warehouse Cockpit [Seite 741]. For more information, see the Implementation Guide (IMG) for EWM under Monitoring Easy Graphics Framework.

Implementation Considerations
If you are implementing the standard EGF graphics, you must have SAP GUI 6.40 or later installed. For more information, see SAP Service Marketplace under service.sap.com/patches.

Integration
By default, the EGF uses SAP Internet Graphics Server (SAP IGS) as its graphics provider to generate graphics from data. You can however use any other graphics provider that generates graphics from data. These graphics must be transferred to the EGF in the form of Uniform Resource Locators (URLs) (see Make Settings for the Easy Graphics Framework [Seite 73]). The service provider defines which data the EGF displays for an EGF object. To ensure that the EGF can be displayed without errors, you must have installed Microsoft Internet Explorer version 5 or higher. For more information about security settings in Internet Explorer, see SAP Help Portal under help.sap.com mySAP ERP SAP ERP Central Component Logistics Production Planning and Control (PP) Production Planning for Process Industries (PP-PI) Process Management (PP-PI-PMA) Process Instruction Sheets (PI Sheets) Browser-Based PI Sheet Setting Up the Browser for PI Sheets and Cockpits.

Features
The following figure provides an overview of the simplified process flow in the EGF:

SAP Extended Warehouse Management (SAP EWM)

510

68

SAP Online Help

20.07.2007

Display

Call corresponding to Customizing

Easy Customizing Graphics Framework

Graphics Provider
SAP Internet Graphics Server Customer-Specific

URL for generated graphic

Drilldown

The EGF receives data from a service provider, for example about the utilization of resources. If you are using a chart type to display this data that is delivered in the standard SAP system, the EGF sends the data to SAP IGS. If you are using your own chart type to display this data, the EGF uses method GET_URL to send the data to your graphics provider (see Interfaces [Seite 77]). SAP IGS or your graphics provider generates a relevant graphic, and sends a URL to the EGF. The EGF uses this URL to display the graphic in your cockpit. The following functions are available in the EGF: By default, the EGF uses SAP IGS as a graphics provider. You can use a selection of chart types [Extern], which are provided by SAP IGS. The EGF also provides you with further chart types, such as traffic lights. You can also use your own graphics provider and your own chart types (see Make Settings for the Easy Graphics Framework [Seite 73]). The EGF displays all chart types that you have defined in Customizing for the EGF. The EGF also shows all chart types for which a graphics provider sends a URL that refers to this chart type. This can be SAPs own graphics, such as from SAP xApp Manufacturing Integration and Intelligence (xMII) or Business Server Page applications, or graphics from external providers (see Make Settings for the Easy Graphics Framework [Seite 73]). You can display graphics either in a cockpit, with or without Customizing, or in your own application (see Make Settings for the Easy Graphics Framework [Seite 73] und Interfaces [Seite 77]). The EGF displays the current data sent by a service provider, and refreshes this data in specified intervals. You can define the input data for a displayed EGF object, including the refresh rate (see Using the Refresh Rate [Seite 76]). If you have defined follow-up activities, you can navigate from the graphic in the EGF to another application (see Make Settings for the Easy Graphics Framework [Seite 73]). For example, you display the number of open warehouse tasks in a graphic, and have defined a follow-up activity to navigate to warehouse task confirmation. If you want to navigate from the EGF to a follow-up activity, you can do this in one of the following ways: In the context menu of the EGF object, select the corresponding option.

SAP Extended Warehouse Management (SAP EWM)

510

69

SAP Online Help

20.07.2007

In the graphic, select a data value, from which you can drill-down.

You can define EGF object data, such as resource or utilization data, which a user can display as a graphic. You can define these authorizations for each EGF object or for each function using an authorization group. Users can only see EGF objects in the navigation tree, or functions in the context menu, for which they have authorization (see Make Settings for the Easy Graphics Framework [Seite 73]).

You have the EGF objects Door Assignment and Unconfirmed Warehouse Tasks in a cockpit. You want user A to be able to see only the EGF object for unconfirmed warehouse tasks in the navigation tree of the cockpit, and define authorizations correspondingly. You want user B to see only unconfirmed warehouse task data for warehouse numbers 0001 and 0002, and define authorizations correspondingly. For more information, see the IMG for EWM under Monitoring Easy Graphics Framework Define Authorization Groups. You can define a cross-user or a user-specific EGF cockpit layout. For an EGF cockpit menu, for example, you can define a changed structure in the navigation tree with newly created structure nodes (see Definition of EGF Cockpit Layouts [Seite 71]). In Customizing for the EGF, you can define the following for displaying EGF objects (see Make Settings for the Easy Graphics Framework [Seite 73]): Cockpit Available EGF objects for each cockpit Available chart types for each EGF object Default chart type You can specify a default chart type for each EGF object. Input data for an EGF object Follow-up activities for each EGF object

SAP Extended Warehouse Management (SAP EWM)

510

70

SAP Online Help

20.07.2007

Definition of EGF Cockpit Layouts


Use
You can define different EGF cockpit layouts either user-specifically or cross-user.

Integration
For more information about EGF integration, see Easy Graphics Framework [Seite 68].

Prerequisites
For more information about EGF prerequisites, see Easy Graphics Framework [Seite 68].

Features
You can define the following for a cross-user or user-specific EGF cockpit layout: Default layout of an EGF cockpit

If you do not define a default layout, the EGF displays both the standard SAP EGF objects and your own EGF objects. You can reload a cockpit layout at any time, for example if you have deleted EGF objects from the navigation tree and want to display them again. Grouping of EGF objects in the navigation tree, to display your EGF objects in a clearer way Saving input data, such as the warehouse number Number of rows and columns of the display grid and the layout of the grid You can divide a cell of a grid into further rows and columns. You can also insert a grid within a grid, or define the size of the individual viewers. Size of the displayed graphic If you change the display size of a displayed EGF object, the EGF automatically adjusts the size of the displayed graphic as soon as the next refresh interval [Seite 76] has occurred. If you choose with the quick info Regenerate Graphics, the EGF adjusts the display size for EGF objects that are already displayed straight away.

Activities
If you want to define a cross-user or user-specific EGF cockpit layout, choose the EGF cockpit (transaction /SCWM/EGF) and define your EGF cockpit layout. Choose Save Layout. The system displays a modeless dialog box, in which you can define the following: Layout name Description Layout options: EGF cockpit menu only EGF cockpit menu and grid layout EGF cockpit menu, grid layout, and input data

SAP Extended Warehouse Management (SAP EWM)

510

71

SAP Online Help

20.07.2007

Depending on your authorizations, you can also set the Default Layout indicator for a userspecific EGF cockpit layout and Cross-User for a cross-user EGF cockpit layout in this modeless dialog box (see Make Settings for the Easy Graphics Framework [Seite 73]). If you want to change the settings for the grid and refresh rate at runtime, choose the secondary mouse button.

SAP Extended Warehouse Management (SAP EWM)

510

72

SAP Online Help

20.07.2007

Make Settings for the Easy Graphics Framework


To be able to use the Easy Graphics Framework (EGF), you must make the following Customizing settings.

Settings for EGF Objects


If you want to display a graphic in a cockpit, define your own chart types and assign these or existing chart types to EGF objects. To do this, in Customizing for EWM, execute the IMG activity Define Chart Types and Define Objects. For more information, see the Implementation Guide (IMG) for EWM under Monitoring Easy Graphics Framework Define Chart Types and Define Objects. If you navigate from a displayed EGF object to follow-up activities, and want to use the Post Processing Framework or a workflow, define follow-up activities. To do this, in Customizing for EWM, execute the IMG activity Define Functions. For more information, see the IMG for EWM under Monitoring Easy Graphics Framework Define Functions. If you want to define authorizations for each EGF object or function, define authorization groups and assign these to an EGF object or function. To do this, in Customizing for EWM, execute the IMG activity Define Authorization Groups and Define Objects. For more information, see the IMG for EWM under Monitoring Easy Graphics Framework Define Objects.

The EGF only performs the authorization check for EGF objects. If you define a navigation to follow-up activities and follow-up objects, you have to perform an authorization check yourself. You define the default chart type for an EGF object. To do this, in Customizing for EWM, you specify the default chart type for an EGF object in the Chart Type field of IMG activity Define Objects. For more information, see the IMG for EWM under Monitoring Easy Graphics Framework Define Objects. If you want to change the predefined refresh rate, define your own refresh rate. To do this, in Customizing for EWM, you specify your refresh rate in the Interval column of dialog structure Objects in the IMG activity Define Objects (see Using the Refresh Rate [Seite 76]). For more information, see the IMG for EWM under Monitoring Easy Graphics Framework Define Objects.

Settings for Displaying EGF Objects in the Navigation Tree of the EGF Cockpit
You specify the cockpit for displaying an EGF object by defining a new EGF implementation. To do this, in Customizing for EWM, execute the IMG activity Define Cockpits. For more information, see the IMG for EWM under Monitoring Easy Graphics Framework Define Cockpits. You define the number of EGF objects for each cockpit. To do this, in Customizing for EWM, specify the number in dialog structure Cockpits Objects in IMG activity Define Cockpits. For more information, see the IMG for EWM under Monitoring Easy Graphics Framework Define Cockpits. You define input data for an EGF cockpit. To do this, in Customizing for EWM, specify the number in dialog structure Cockpits Input Data in IMG activity Define Cockpits. For more information, see the IMG for EWM under Monitoring Easy Graphics Framework Define Cockpits.

SAP Extended Warehouse Management (SAP EWM)

510

73

SAP Online Help

20.07.2007

Settings for Graphics


You define the attributes of a graphic for each EGF object, such as per resource or warehouse task, or per user. For example, you can define that the background color in graphics is always blue, or that EGF is to always use blue, yellow, red and green to display pie charts. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Monitoring Process Chart Template. Make your changes, and save them. When saving, you can choose between User-Specific and Cross-User. You have defined the authorizations per EGF object or user if required. You can assign the following authorizations: User * USER1 USER2 You can define a chart type, and allow it as a default chart type for all users, EGF cockpits, and EGF objects. You can define a chart type, and allow it as a default chart type for user USER1, all EGF cockpits, and all EGF objects. You can define a third chart type, and allow it as a default chart type for user USER2, EGF cockpit COCKPIT2, and EGF object OBJECT2. EGF Cockpit * * COCKPIT2 EGF Object * * OBJECT2 Chart Type PIE CHART PIE CHART PIE CHART Default Chart Type DEFAULT DEFAULT1 DEFAULT2

To do this, in Customizing for EWM, you define the graphic attributes for each EGF object in dialog structure Cockpits of IMG activity Define Settings. For more information, see the IMG for EWM under Monitoring Easy Graphics Framework Define Cockpits.

Settings for Your Own Graphics


If you want to use something other than SAP Internet Graphics Server (SAP IGS) as your graphics provider, define your own graphic types and set the URL indicator. This calls the GET_URL method of your service provider, allowing you to return a Uniform Resource Locator (URL) to the EGF. To do this, in Customizing for EWM, execute the IMG activity Define Chart Types. For more information, see the IMG for EWM under Monitoring Easy Graphics Framework Define Chart Types.

The EGF uses an HTML Viewer to display a URL that links to a graphic. You can use the GET_URL method of interface /SCWM/IF_EGF_SP to implement your own graphics provider instead of the SAP Internet Graphics Server (SAP IGS). The EGF receives the data from which a graphic is to be generated from the service provider. The EGF then calls your graphics provider instead of the SAP IGS. In this situation, you are responsible for which data the EGF displays with the URL. Calling a URL outside of the SAP system and calling a graphics provider within an SAP system may not be safe, since data can enter the system without undergoing a virus check, for example. We recommend that you use SAP Web Repository to save and display graphics using a URL with the EGF, for example. You can activate a virus check with the SAP Web Repository to check documents and graphics before an upload. We recommend that you make the following settings in your Browser: Make Browser Settings for the Easy Graphics Framework [Seite 79] For more information, see:

SAP Extended Warehouse Management (SAP EWM)

510

74

SAP Online Help

20.07.2007 The IMG for EWM under SAP NetWeaver Application Server System Administration Virus Scan Interface. SAP Service Marketplace under

service.sap.com/securityguide SAP Supply Chain


Management SAP Supply Chain Management Security Guide SCM 5.1

SAP Help Portal at help.sap.com SAP R/3 Enterprise Release 4.70 SAP NetWeaver Components SAP Internet Transaction Server ITS Implementation Models WebRFC Programming ### Web Reporting. SAP Help Portal under help.sap.com SAP NetWeaver 2004s SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability ABAP Technology UI Technology Front-End Services (BC-FES) SAP HTML Viewer (BCCI)

You define the available EGF objects for each EGF cockpit. To do this, in Customizing for EWM, you executed the IMG activity Define Chart Types and Define Cockpit Settings. For more information, see the IMG for EWM under Monitoring Easy Graphics Framework Define Chart Types and Define Cockpits.

SAP Extended Warehouse Management (SAP EWM)

510

75

SAP Online Help

20.07.2007

Using the Refresh Rate


Use
The Easy Graphics Framework (EGF) uses a refresh rate [Extern] to refresh the data sent by a service provider for an EGF object.

Features
The default refresh rate is set to one minute. The refresh rate is located at EGF object level. The EGF checks to see whether a refresh is required for the first cell in the grid, for example. If this is the case, the EGF calls the service provider and waits for its response. If the service provider only responds after ten minutes, the EFG only checks after ten minutes whether a refresh is required for the second cell in the grid. If you are using the EGF for planning purposes or for forecasts, you can deactivate the refresh rate, enabling you to display trends, such as a trend for the coming year, or forecasts, such as daily resource requirements for a warehouse task.

Activities
You deactivate the refresh rate by setting the refresh rate value to zero either in Customizing for the EGF for the object, or in the context menu for the object at runtime. You can define the refresh rate for each EGF object.

You can change the refresh rate at runtime. You can refresh an EGF object that you are displaying as a graphic immediately by choosing the option Refresh Display in the context menu for the object. You can also refresh all displayed objects by choosing Refresh Data in the SAP GUI. See also: Make Settings for the Easy Graphics Framework [Seite 73]

SAP Extended Warehouse Management (SAP EWM)

510

76

SAP Online Help

20.07.2007

Interfaces, Methods and Function Modules in the EGF


Use
The Easy Graphics Framework (EGF) allows you to work with various interfaces, methods, and function modules.

Features
Interfaces and Methods
The following table gives you an overview of the methods in the EGF. Interface /SCWM/IF_EGF_SP Method GET_DATA Description Gets chart data from the application. Most charts require a group of row values and a group of data categories as data format. A simple chart, such as a traffic light, only sets the color of the traffic light. Gets a URL from the application. This URL forms the link to the graphic that the EGF is to display. If the application receives a function code for a follow-up activity, this interface method enters the function code for the chart. Generates graphic of a graphics provider in the EGF, such as for all EGF graphics of class /SCWM/CL_EGF_IGS_SERVICES in interface /SCWM/IF_EGF_CHART.

/SCWM/IF_EGF_SP

GET_URL

/SCWM/IF_EGF_SP

HANDLE_FUNCTION

SCWM/IF_EGF_CHART

CREATE_CHART

You can use these interfaces to do the following: Define a source for your chart data Define your own graphics provider Define your own chart types and send them to the EGF using a URL Define follow-up activities for an EGF object

For more information, see the interface documentation.

Function Modules
The following table gives you an overview of the function modules in the EGF. Function Module /SCWM/EGF_COCKPIT Description Starts an EGF cockpit implementation. You must enter the cockpit ID as an import parameter.

SAP Extended Warehouse Management (SAP EWM)

510

77

SAP Online Help

20.07.2007

/SCWM/EGF_CONTAINER

You transfer a container instance to the function module, such as to class CL_GUI_CUSTOM_CONTAINER, in which the required EGF object is displayed. The system generates a modeless dialog box in which the required EGF object is displayed. Starts an EGF cockpit dynamically. All the data required for generating the cockpit is transferred using the interfaces of the function module. No Customizing is required here. You transfer a container instance to the function module, such as to class CL_GUI_CUSTOM_CONTAINER, in which the required EGF object is displayed. The EGF object definition is done dynamically using the interface of the function module. No Customizing is required here. The system generates a modeless dialog box in which the required EGF object is displayed. The EGF object definition is done dynamically using the interface of the function module. No Customizing is required here.

/SCWM/EGF_POPUP /SCWM/EGF_COCKPIT_DYNAMIC

/SCWM/EGF_CONTAINER_DYNAMIC

/SCWM/EGF_POPUP_DYNAMIC

You can use these function modules to do the following: Start an EGF cockpit implementation Transfer a container instance to a function module Generate a modeless dialog box You can display a graphic as a subscreen or as a separate modeless dialog box in your application. To do this, choose the following in Customizing for EWM: Monitoring Easy Graphics Framework Define Chart Types and Define Cockpits. For more information, see the function module documentation.

SAP Extended Warehouse Management (SAP EWM)

510

78

SAP Online Help

20.07.2007

Make Browser Settings for the Easy Graphics Framework


Use
If you work with a Microsoft Internet Explorer in the Easy Graphics Framework (EGF), you must meet the following prerequisites and make the following security settings.

Prerequisites
To ensure that the EGF can be displayed without errors, you must have installed Microsoft Internet Explorer version 5 or higher. You must also make the security settings listed below in your Microsoft Internet Explorer.

Procedures
...

1. In the Internet Explorer menu, choose Tools Internet Options. 2. Choose the Security tab page. 3. Choose the Web content zone: Under Internet Options, you can choose from different options. We cannot recommend Internet. Trusted Sites is safer, but Local Intranet offers better performance (see also SAP Note 785308). 4. Choose Custom Level.... 5. In the Security Settings window, make the following settings: Function Download signed ActiveX controls Launching programs and files in an IFRAME Navigate sub-frames across different domains Setting Prompt Prompt Prompt

SAP Extended Warehouse Management (SAP EWM)

510

79

SAP Online Help

20.07.2007

Delivery Processing
Use
Extended Warehouse Management (EWM) has its own Delivery Processing area. The following section describes the available functions, as well as the integration with EWM. For an overview of the available user transactions, see User Interfaces in Delivery Processing [Seite 138]. For more information, see Delivery Processing [Seite 81].

SAP Extended Warehouse Management (SAP EWM)

510

80

SAP Online Help

20.07.2007

Delivery Processing
Purpose
Delivery processing plays a significant role in the logistics chain. It provides functions for executing goods receipt and goods issue activities. Corresponding to the goods receipt and goods issue processing, a difference is made in delivery processing between the inbound delivery process and the outbound delivery process.

Inbound delivery process


The following inbound delivery scenarios are supported by delivery processing: Deliveries to the customer, to the warehouse, to any ship-to party, or to any ship-to location. Returns to the supplier, to any ship-to party or to any ship-to location.

From the purchase order, the delivery process covers the notification, the delivery the subsequent putaway and the goods receipt posting of the ordered goods. Information about planning is saved in the inbound delivery, the status is monitored, and all the data collected during the inbound delivery is recorded. On creation of the delivery, activities such as the putaway or scheduling, are triggered and the data generated by the delivery process is recorded.

Outbound delivery process


The following outbound delivery scenarios are supported by delivery processing: Deliveries from the supplier, from any ship-from party or from any ship-from location. Returns from the customer, from any ship-from party or from any ship-from location.

The outbound delivery process covers all shipping activities such as picking, packing, transportation and goods issue. Information about shipping planning is saved in the inbound delivery, the status is monitored, and all the data collected during the inbound delivery is recorded. On creation of the delivery, shipping activities such as picking or shipment scheduling, are triggered and the data generated by the shipping processing is recorded.

Features
In delivery processing, documents [Seite 83] are provided which represent the delivery process in the system. Delivery processing also provides a series of services and functions to configure how the documents are to be processed and to define the business features of the documents in a way that best suits your business process. The following services and functions are provided by delivery processing: Status management [Seite 94] Quantity offsetting [Seite 97] Text management

For more information about text management in delivery processing, see the documentation for the relevant SAP application (for example, mySAP Supply Chain Management SAP Extended Warehouse Management). Field control [Seite 99] 510 81

SAP Extended Warehouse Management (SAP EWM)

SAP Online Help

20.07.2007

Validation [Seite 101] Connection to the Post Processing Framework (PPF) [Seite 105] Change documents [Seite 107] Archiving

For more information about archiving in delivery processing, see the documentation for the relevant SAP application (for example, mySAP Supply Chain Management Data Archiving).

SAP Extended Warehouse Management (SAP EWM)

510

82

SAP Online Help

20.07.2007

Documents in Delivery Processing


Use
A document contains all the data required to document and control a business process. Various documents are used in delivery processing to control the processes. The inbound delivery process is represented in the system by the following documents: Inbound Delivery Notification [Seite 87] Inbound Delivery [Seite 88]

The outbound delivery process is represented in the system by the following documents: Outbound Delivery Request [Seite 90] Outbound Delivery Order [Seite 91] Outbound Delivery [Seite 93]

Every document provides various actions that are used to control the individual delivery processing steps. The execution of the actions depends on the settings in the Post Processing Framework (PPF) [Seite 105].

Structure
A document comprises a document header and any number of document items. The following figure shows the structure of a delivery document.

Header

e.g. Shipping point, goods recipient

Item 1

e.g. Material, quantity

Item 2

Item 3

Document header
The document header contains the general data for the inbound or outbound delivery. This data is relevant for the complete document. It includes: Goods receiving point or shipping point Scheduling data (for example, shipping or delivery date) Weights and volumes for the complete inbound/outbound delivery Supplier, sold-to party and goods recipient numbers

SAP Extended Warehouse Management (SAP EWM)

510

83

SAP Online Help

20.07.2007

The document header is defined in the system by the document category and the document type. The document category classifies the different documents that can be processed by the system in delivery processing. It is defined by the system and cannot be changed. The document type classifies the documents with regard to the complete delivery process. The document type defines the business aspects of a document. The following figure shows a possible relationship between the document category and the document type in the inbound delivery process. In this case, only one document type (Z100) is used for the complete inbound delivery process.

Document cat. IDR Inbound delivery notification

Document cat. PDI Inbound delivery

Document type Z100

Inbound delivery process

Using the document type determination, you can derive several document types from a document category and therefore define certain delivery processes. The following figure shows a relationship between the document category and the document type whereby two different document types were derived from one document type.

Document cat. IDR Inbound delivery notification

Document cat. PDI Inbound delivery

Document type Z100

Document type Z200 Document type Z300

Inbound delivery process

The document type Z100 is defined for the document category inbound delivery notification. Document types Z200 and Z300 are defined for the document category inbound delivery. The document type determination defines that document types Z200 and Z300 are to be derived from document type Z100 in the inbound delivery process. In Customizing for Delivery Processing [Seite 108], you can define your own document types and document type determination.

Document items
In the document items, you find the data relevant to the individual items. This includes:

SAP Extended Warehouse Management (SAP EWM)

510

84

SAP Online Help

20.07.2007

Material number Delivery quantity Location specifications (goods receiving point, unloading point or shipping point) Putaway date or picking date Weights and volumes of the individual items Tolerances for underdelivery or overdelivery

The document items are defined in the system by the item category and by the item type. The item category classifies the different items that can be processed by the system for delivery processing. It is defined by the system and cannot be changed. The following item categories exist in delivery processing: Normal delivery item Return item Text item

The item type classifies the items for a document type with regard to the complete delivery process. The item type defines the business aspects of the document items. As for the document header, for the document items, you can also configure your business process via the item type and the item type determination in Customizing for Delivery Processing.

Service profiles
Service profiles define how a document is processed in the system as well as its business scope. Two types of service profile exist: System profile Customer profile (for example, status profile, text profile and incompleteness profile)

The system profile is not configurable and is linked to the document categories and item categories. The customer profiles are linked to the document types and to the item types. In Customizing for Delivery Processing, you can define more customer profiles and therefore adjust the documents to suit your business process. In delivery processing, you can configure the following functions using the customer profiles: Status management Quantity offsetting Text management Field control Incompleteness check Actions Partner processing Process codes Reference document types

SAP Extended Warehouse Management (SAP EWM)

510

85

SAP Online Help

20.07.2007

Date types

SAP delivers predefined status profiles for the standard processes in delivery processing.

General Settings
The general settings for the documents in delivery process are not controlled by the service profiles. You can define the following general settings in Customizing for Delivery Processing: Number range intervals Delivery priority Shipping conditions Incoterms

You can find more information in Customizing for Delivery Processing [Seite 108].

SAP Extended Warehouse Management (SAP EWM)

510

86

SAP Online Help

20.07.2007

Inbound Delivery Notification


Definition
The inbound delivery notification is a document [Seite 83] containing all the relevant logistics data in the inbound delivery process right from the origin of the inbound delivery process (shipping notification, delivery note or purchase order, for example). The shipping notification from the supplier is saved in the inbound delivery notification.

Use
You use the inbound delivery notification to save the logistics data transferred data from a reference document in order to create an inbound delivery [Seite 88]. Using the inbound delivery notification, you can also process or reject incoming changes to an existing inbound delivery.

Structure
The inbound delivery notification comprises the following: Document category with the same name Inbound Delivery Notification Document type Item category Item type Service Profiles

In Customizing for Delivery Processing [Seite 108], you can define your own document types, item types and service profiles and therefore you can adapt the document to suit your business process.

Integration
The execution of the actions depends on the settings in the Post Processing Framework (PPF) [Seite 105]. The following configuration exists in the standard system: The delivery process receives a message from a reference document with all the relevant logistics data. An inbound delivery notification is created automatically as a result of this message. All the information contained in the message is saved in the inbound delivery notification. An inbound delivery is created automatically from the inbound delivery notification. Changing an existing inbound delivery: If a change to an existing inbound delivery is rejected, an inactive inbound delivery notification (inactive version) is created in addition to the existing active inbound delivery notification. You can process the data in the inactive inbound delivery notification and you can create a new inbound delivery by activating the request manually.

SAP Extended Warehouse Management (SAP EWM)

510

87

SAP Online Help

20.07.2007

Inbound Delivery
Definition
The inbound delivery is a document [Seite 83] containing all the data required for triggering and monitoring the complete inbound delivery process. This process starts on receipt of the goods in the yard and ends on transferal of the goods at the final putaway, production or outbound delivery.

Use
The inbound delivery is used as a working object in the inbound delivery process. You use this document in delivery processing when executing the following actions: Registering the delivery in the yard Unloading the delivery Canceling the unloading of the delivery Placing the delivery into stock (putaway) Canceling the delivery putaway Adjusting the delivery quantity to the quantity posted in the goods receipt (in case of overdelivery or underdelivery. Adjusting the delivery quantity and the transferred quantity In this case, the delivery quantity is adjusted to the quantity posted in the goods receipt. The quantity in the inbound delivery notification is also adjusted and a new inbound delivery is created. Posting a goods movement Canceling a goods movement Creating items Deleting items

You can save, validate and delete an inbound delivery.

Structure
The inbound delivery request comprises the following: Document category with the same name Inbound Delivery Document type Item category Item type Service Profiles

In Customizing for Delivery Processing [Seite 108], you can define your own document types, item types and service profiles and therefore you can adapt the document to suit your business process.

SAP Extended Warehouse Management (SAP EWM)

510

88

SAP Online Help

20.07.2007

Integration
The inbound delivery is created after activating an inbound delivery notification [Seite 87]. The inbound delivery adopts all the relevant data from the inbound delivery notification. The execution of the actions depends on the settings in the Post Processing Framework (PPF) [Seite 105].

SAP Extended Warehouse Management (SAP EWM)

510

89

SAP Online Help

20.07.2007

Outbound Delivery Request


Definition
The outbound delivery request is a document [Seite 83] containing all the relevant logistics data in the outbound delivery process right from the origin of the outbound delivery process (sales order, for example).

Use
You use the outbound delivery request to save the transferred data from a reference document in order to create an outbound delivery order [Seite 91]. Using the outbound delivery request, you can also process or reject incoming changes to an existing outbound delivery order.

Structure
The outbound delivery request comprises the following: Document category with the same name Outbound Delivery Request Document type Item category Item type Service Profiles

In Customizing for Delivery Processing [Seite 108], you can define your own document types, item types and service profiles and therefore you can adapt the document to suit your business process.

Integration
The execution of the actions depends on the settings in the Post Processing Framework (PPF) [Seite 105]. The following configuration exists in the standard system: The delivery process receives a message from a reference document with all the relevant logistics data. An outbound delivery request is created automatically as a result of this message. The delivery process saves the information from the message in the outbound delivery request. The message itself is not saved. An outbound delivery order is created automatically from the outbound delivery request. Changing an existing outbound delivery order: If a change to an existing outbound delivery order is rejected, an inactive outbound delivery request (inactive version) is created in addition to the existing active outbound delivery request. You can process the data in the inactive outbound delivery request and you can create a new outbound delivery order by activating the request manually.

SAP Extended Warehouse Management (SAP EWM)

510

90

SAP Online Help

20.07.2007

Outbound Delivery Order


Definition
The outbound delivery order is a document [Seite 83] containing all the data required for triggering and monitoring the complete outbound delivery process. This process starts with the first planning activities for the outbound delivery and continues until the finished goods have been loaded and sent.

Use
You either use the outbound delivery order to preview the planning of pending warehouse activities or to execute the actions required to create the delivery. You can use the outbound delivery order to execute the following actions: Creating the delivery and therefore creating an outbound delivery [Seite 93] Picking the delivery Canceling the delivery picking Loading the delivery Canceling the delivery loading Setting the status Leave Yard Adjusting the delivery quantity to the picked quantity Posting a goods movement Canceling a goods movement Creating items Deleting items

You can save, validate, delete and archive an outbound delivery order.

Structure
The outbound delivery order comprises the following: Document category with the same name Outbound Delivery Order Document type Item category Item type Service profiles

In Customizing for Delivery Processing [Seite 108], you can define your own document types, item types and service profiles and therefore you can adapt the document to suit your business process.

Integration
The execution of the actions depends on the settings in the Post Processing Framework (PPF) [Seite 105]. The following configuration exists in the standard system:

SAP Extended Warehouse Management (SAP EWM)

510

91

SAP Online Help

20.07.2007

The outbound delivery order is created automatically after activating the outbound delivery request [Seite 90]. Here, all the relevant data is copied from the outbound delivery request. One or several outbound deliveries are created from the outbound delivery order.

The outbound delivery order has the status Locked (Preceding Document) when only used as a preview for planning warehouse activities. This status is determined via the corresponding outbound delivery request from the reference document. In this case, you cannot create a delivery.

SAP Extended Warehouse Management (SAP EWM)

510

92

SAP Online Help

20.07.2007

Outbound Delivery
Definition
The outbound delivery is a document [Seite 83] representing the goods to be delivered together to a goods recipient.

Use
The outbound delivery is used as the basis for printing the delivery note or for sending a shipping notification. You can execute the following actions using this document: Posting a goods movement Canceling a goods movement Setting the status Leave Yard

You can save, process, delete and archive an outbound delivery.

Structure
The outbound delivery comprises the following: Document category with the same name Outbound Delivery Document type Item category Item type Service profiles

In Customizing for Delivery Processing [Seite 108], you can define your own document types, item types and service profiles and therefore you can adapt the document to suit your business process.

Integration
You create an outbound delivery when you select the action Create Outbound Delivery in the outbound delivery order [Seite 91]. The execution of the actions depends on the settings in the Post Processing Framework (PPF) [Seite 105].

SAP Extended Warehouse Management (SAP EWM)

510

93

SAP Online Help

20.07.2007

Status Management
Use
Status Management controls business transactions (also called activities) by assigning one or several statuses to a delivery document. A status can allow or prohibit a business transaction or it may have no influence at all. The field control [Seite 99] for delivery processing also depends on status management.

Integration
The status management described here is used in delivery processing exclusively.

Features
A status in delivery processing consists of the following parameters: Status type Status value

The status type describes a partial view or a partial process in the processing of a delivery document (for example, goods receipt status, unloading status or putaway status). A basic quantity of status types for the document header and the document item is saved in the system profile for status management. The status types are linked to the document and item types of delivery processing via a status profile. You can change the settings for the status types using this status profile. The status value defines the delivery document status with regard to the status type (for example, Yes/No or Not Started/In Process/Completed). It changes along with the business transactions. A status value can disallow a business transaction. On the other hand, a business transaction can set a new status. The following conditions must be fulfilled before a business transaction can be carried out: At least one status value must allow the transaction. No status value may disallow the transaction.

SAP delivers predefined status types for the standard processes in delivery processing. Several of these status types are indicated by special attributes which are displayed in the following table. You cannot change these attributes in Customizing. Attribute Aggregated status Meaning The system calculates the status value of such a status type from the status values of all the partial objects in a lower document level. The system calculates the status value of such a status type from the status type with the same name from higher document levels. The system calculates the status value of such a status type from the current status values of a predefined quantity of status types from the same partial object (for Use An aggregated status at document header level provides compact information on the status of all the items, for example in a display or change transaction. A projected status at document item level provides the option of controlling activities and the field control at item level by a status at header level. This attribute has a purely technical meaning. An overall status provides compact information on a certain quantity of statuses for the same partial object (for example, header or item).

Projected status

Overall status

SAP Extended Warehouse Management (SAP EWM)

510

94

SAP Online Help example, header or item). Transient status The system only calculates this status type for the runtime. The status type is not saved permanently.

20.07.2007

This indicator is only set for derived status types (aggregated status, overall status, for example).

Status value if original status ambiguous Inactive

The derived status value is set for an aggregated status or an overall status if the status values of the influencing status types are not unique. You use this indicator to activate or deactivate several status types in each status profile. However, there are also status types which always have to be active. You cannot change this indicator for these status types.

You can increase the number of available status types by adding your own user statuses. As opposed to the status types predefined by SAP, the user statuses can only have two values (Yes/No). The user statuses are grouped via the user status profile in the general status management. The user status profile in the general status management is linked to the system profile for delivery processing via an object type. Here, a user status profile in the general status management can be assigned to several object types and, therefore, to several system profiles.

In the status management for delivery processing, you cannot assign several user status profiles to one object type. The object type and system profile have a one-to-one relationship. On the other hand, several status profiles for the configuration of document and item types can be derived from one system profile. The following graphic shows the relationships between the individual objects in status management.
User Status Profile of General Status Management

Ux Ux User Status Sx Sx Predefined Status Type

U1 U1

U2 U2 1:n

U3 U3

Object Type 1

Objekt Type 2

1:1
System Profile 1 System Profile 2

S1 S1 U1 U1

S2 S2 U2 U2

S3 S3 U3 U3 1:n

S1 S1 U1 U1

S2 S2 U2 U2

S3 S3 U3 U3

Status Profile 1 of Delivery Processing

Status Profile 2 of Delivery Processing

S1 S1 U1 U1 U2 U2

S3 S3

S1 S1

S2 S2 U2 U2 U3 U3

The user status profile of the general status management is not identical to the status profile for the document types and item types.

SAP Extended Warehouse Management (SAP EWM)

510

95

SAP Online Help

20.07.2007

Actions
In Customizing for Delivery Processing [Seite 108], you can execute the following activities: Activate or deactivate certain status types in the status profile Create status profiles Define a user status profile of the general status management for the user status Define user statuses

SAP Extended Warehouse Management (SAP EWM)

510

96

SAP Online Help

20.07.2007

Quantity offsetting
Use
Using the quantity offsetting function, you can offset quantities consistently independently of the application. In delivery processing, you use the quantity offsetting to calculate the open quantities for a document or to calculate the relevant quantities (requested quantity and reduced quantity) for checking a document execution, for example. This means that you can check whether you actually delivered the agreed quantity on a certain date.

Integration
The quantity offsetting is a cross-application service within Logistics.

Features
The quantity offsetting is executed at item level and at schedule line level of a document. At present, the schedule line level is not supported by the documents in delivery processing. Quantity offsetting consists of the following features: Quantity type Quantity calculation Quantity offsetting Quantity role Quantity offsetting profile

Quantity type
The quantity type is a classification of the different quantities for quantity offsetting. Examples of quantity types include: Requested quantity Reduced quantity Open quantity

Quantity calculation
The quantity calculation determines the mathimatical function (quantity calculation rule) for calculating the relevant data for quantity offsetting. You therefore define how the reduced quantity of a document is determined and which algorithm is to be used to calculate this quantity, for example. The relevant data for the quantity calculation algorithm comes from either the document flow or from a different source (from a service, for example). If you use the document flow for the quantity calculation algorithm, you have to define which links are relevant in Customizing for delivery processing.

The data in Handling Unit Management (HUM) is used for the packed quantity.

Quantity offsetting
The quantity offsetting determines the function (quantity offsetting rule) with which the different quantities are calculated.

SAP Extended Warehouse Management (SAP EWM)

510

97

SAP Online Help

20.07.2007

Depending on how it is used, you can access the quantity offsetting with or without quantity calculation.

Quantity role
The quantity role is used to group quantity calculation or quantity offsetting rules for certain applications or processes. In this way, you can define the quantity calculation or quantity offsetting rules according to the application or the process. A quantity role can exist of several quantity types.

Quantity offsetting profile


If you want to execute quantity offsetting automatically, a quantity offsetting profile exists in the quantity offsetting. This profile contains the quantity calculation and quantity offsetting rules to be used by the quantity offsetting to calculate the quantities automatically. The quantity offsetting profile is linked to the document type and item type of a document. SAP delivers predefined quantity offsetting profiles types for the standard processes in delivery processing. You can find more information in Customizing for Delivery Processing [Seite 108].

Activities
In Customizing for Delivery Processing, you can execute the following activities: Define quantity type Define quantity type Define quantity offsetting profile Define quantity calculation rules Define quantity offsetting rules

SAP Extended Warehouse Management (SAP EWM)

510

98

SAP Online Help

20.07.2007

Field Control
Use
A document [Seite 83] in Delivery Processing contains a multitude of fields. The system uses the field control settings to determine which fields are displayed over the course of the delivery process and which fields can be changed. The field control supports fields at header and item level of a document.

Integration
Field control depends on status management [Seite 94]. During the delivery process, the system controls which fields can be displayed and changed via the status of the document and item type. The field control is accessed by delivery processing during the following events: When creating a document or a document item When switching between display mode and change mode After changing the data in a document

Features
Logical field names
The individual fields of a document are represented in the system as components [Extern] of structures [Extern]. Every component in a structure is uniquely identified by the logical field name and can therefore be addressed directly.

Field attributes
In the field attributes of the field control, the system defines the status for which a field is displayed and can be changed for each logical field name. Field attributes in the field control Field attribute Status type Description Describes a partial view or a partial process in the processing of a delivery document (for example, goods receipt status, unloading status or putaway status). Defines the delivery document status with regard to the status type (for example, Yes/No or Not Started/In Process/Completed). If this indicator is set, the field is displayed as a non-changeable field depending on the assigned status (status type and status value). If this indicator is set, the field is not displayed depending on the assigned status (status type and status value).

Status value Display field Hide

Several statuses can be assigned to one field. One field may have different settings for different statuses. When accessing the field control, the table of field attributes is read sequentially by the system. Here, the system compares the status information in the table with the current status information of the document. Every time this information is consistent, the system assigns the corresponding attributes from the field attributes (display or hide field) to the field. If no consistencies are found, the field remains changeable and is not hidden.

SAP Extended Warehouse Management (SAP EWM)

510

99

SAP Online Help

20.07.2007

System profile of the field control


The system profile for the field control contains the allowed fields and their field attributes for a certain document or item type. Via the system profile, you can include new logical field names in the field control. The assignment to the document or item type is carried out via the field control profile. The field attributes saved in the system profile are valid for all assigned field control profiles. You cannot change these field attributes in the system profile nor in the assigned field control profiles.

The incompleteness profile also depends on the system profile of the field control. It uses the list of all allowed fields.

Field control profile


A field control profile contains all the allowed fields and their field attributes for a certain document or item type. Every field control profile is assigned to a system profile. When accessing the field control, the system determines the assigned field control profile via the document and item type. SAP delivers predefined logical field names, system profiles and field control profiles for the standard processes in delivery processing. You cannot change the field attributes of the system profiles delivered by SAP. However, you can add new field attributes.

Activities
In Customizing for Delivery Processing [Seite 108], you can execute the following activities for the field control: Define a new field control profile Maintain field attributes You cannot change any of the field attributes delivered by SAP. However, you can add new field attributes. Define logical field names for new fields Add new logical field names to the system profile of the field control

SAP Extended Warehouse Management (SAP EWM)

510

100

SAP Online Help

20.07.2007

Validation
Use
The validation checks whether a delivery document [Seite 83] is complete and consistent so that it can be further processed in the system.

Features
The validation comprises the following checks: Incompleteness Check [Seite 102] Consistency Check [Seite 103] with Tolerance Check [Seite 104]

SAP Extended Warehouse Management (SAP EWM)

510

101

SAP Online Help

20.07.2007

Incompleteness Check
Use
The incompleteness check determines whether all the relevant fields in a delivery document [Seite 83] are filled so that it can be further processed in the system.

Integration
The incompleteness check uses the logical field names assigned to the system profile of the field control [Seite 99].

Features
Mandatory fields
Every input and output field that must be filled to be able to further process a document is a mandatory field. A mandatory field is defined by a logical field name in the system. Every logical field name that represents a mandatory field is assigned an action. Every time this action is executed, the corresponding field is automatically checked for completeness.

Incompleteness profile
The settings for the incompleteness check are saved in an incompleteness profile. The incompleteness profile is assigned to the document and item types. When accessing the incompleteness check, the system determines the assigned completeness profile via the document and item types and therefore the corresponding settings for the mandatory fields. SAP delivers predefined logical field names and incompleteness profiles for the standard processes in delivery processing. You cannot change the field attributes delivered by SAP. However, you can add new field attributes.

Activities
The incompleteness check is executed automatically by the system. If the incompleteness check determines a mandatory field that has not been filled, the action is terminated and an appropriate message is issued. In Customizing for Delivery Processing [Seite 108], you can execute the following activities for the field control: Define a new incompleteness profile Maintain field attributes You cannot change any of the field attributes delivered by SAP. However, you can add new field attributes. Define logical field names for new mandatory fields Add new logical field names to the system profile of the field control

SAP Extended Warehouse Management (SAP EWM)

510

102

SAP Online Help

20.07.2007

Consistency Check
Use
The consistency check determines whether any data inconsistencies exists between the delivery document [Seite 83], Customizing and master data.

Features
The consistency check contains the following checks: Check whether the document type, document category, item type and item category correspond to the settings in Customizing for delivery processing. Check whether the document contains items. Check whether the product data corresponds to the product master (for example, product ID and allowed units of measure). Check whether the location data corresponds to the location master. Check whether the delivery date lies in the past. Check whether the specifications for the Incoterms, process codes, partner roles, reference documents and date types correspond to the settings in Customizing for delivery processing. Check whether partial deliveries are allowed. Delivery processing determines the number of allowed partial deliveries from the reference document. The consistency check uses these specifications to determine whether partial deliveries are allowed. If no partial deliveries are allowed, the system issues a message and you cannot split the delivery. Check whether the retention period is expired.

Activities
The consistency check is executed automatically by the system. You can also trigger the consistency check manually by choosing the delivery document in the maintenance transaction. If a document is inconsistent, the system issues an appropriate message.

Example
If you want to compare the delivery quantity of the inbound and outbound delivery with the tolerance defined in Customizing, you can perform a Tolerance Check [Seite 104].

SAP Extended Warehouse Management (SAP EWM)

510

103

SAP Online Help

20.07.2007

Tolerance Check
Use
The tolerance check determines whether the delivery quantity lies within the given tolerances for both inbound and outbound deliveries.

Integration
You define the tolerances for the delivery quantity in the reference document that is used to trigger the delivery process. You cannot change the tolerances in the delivery process.

Features
The tolerance check is split into the underdelivery tolerance and the overdelivery tolerance. Underdelivery tolerance The minimum allowed delivery quantity. It is specified as a percentage. Overdelivery tolerance The maximum allowed delivery quantity. It is specified as a percentage. As soon as the delivery quantity changes in a document, the delivery process checks to see whether the changed delivery quantity still lies within the defined tolerances. If the goods quantity lies below or above the tolerance values, the system issues a warning message. The tolerance check in delivery processing checks the delivery quantities in the following documents: Inbound Delivery Notification [Seite 87] Inbound Delivery [Seite 88] Outbound Delivery Request [Seite 90] Outbound Delivery Order [Seite 91]

Unlimited Overdelivery If this indicator is set, overdeliveries of any size are allowed. The system does not issue any message.

Activities
The tolerance check is executed automatically by the system.

SAP Extended Warehouse Management (SAP EWM)

510

104

SAP Online Help

20.07.2007

Post Processing Framework in Delivery Processing


Use
The Post Processing Framework (PPF) [Extern] is a SAP basis technology used in Delivery Processing for scheduling and processing actions with reference to a document [Seite 83].

Integration
The PPF provides basic functions that are delivered with pre-defined settings depending on the application. You can adjust the settings as you require. Note that to what extend it is recommended to make changes to the presettings depends on the application.

Features
The PPF provides the following functions: Technique for determining actions Technique for aggregating found actions Medium for processing actions User interface for Customizing action templates including determination and aggregation techniques as well as processing mediums User interface for Customizing conditions if you use determination via conditions

Action Profile
The actions are saved in an action profile. The action profile is linked to the document type. You assign the actions to a document type via the action profile.

Conditions
In the PPF there are schedule conditions and start conditions. Delivery processing only uses the schedule conditions. You use the schedule conditions to determine when an action is scheduled.

For more information, see Post Processing Framework (BC-SRV-GBT) [Extern].

Activities
In Customizing for Delivery Processing [Seite 108], you can execute the following activities: Define actions Define action profiles Define conditions

Example
Examples of actions include: Activate inbound delivery notification Post goods receipt Print delivery note

SAP Extended Warehouse Management (SAP EWM)

510

105

SAP Online Help

20.07.2007

SAP Extended Warehouse Management (SAP EWM)

510

106

SAP Online Help

20.07.2007

Change Documents in Delivery Processing


Use
You can use change documents to access information on changes made to a delivery document. However, you cannot resave old statuses documented in the change documents in the system.

Features
As soon as a delivery document is changed and saved by a user, a change document is created in delivery processing. The change document contains the following information: which changes were made to a delivery document which user made the changes when the changes were made

Activities
In the maintenance transaction of the corresponding delivery document, choose Display Change Document (see Menu Paths and Paths in Customizing for Delivery Processing [Seite 108]) You receive a list with all the change documents for the selected delivery document.

SAP Extended Warehouse Management (SAP EWM)

510

107

SAP Online Help

20.07.2007

Menu Paths and Customizing Paths for Delivery Processing


This section provides you with information on which SAP application contains the delivery processing component and its functions and where to find this information.

Menu Paths
For the inbound delivery, start from the SAP Easy Access screen and choose Extended Warehouse Management Delivery Processing Inbound Delivery. For the outbound delivery, start from the SAP Easy Access screen and choose Extended Warehouse Management Delivery Processing Outbound Delivery.

Customizing
Processing document and item types: For the inbound delivery start from the Implementation Guide (IMG) and choose Extended Warehouse Management Goods Receipt Process Inbound Delivery. For the outbound delivery start from the Implementation Guide (IMG) and choose Extended Warehouse Management Goods Issue Process Outbound Delivery. General Settings: To define the cross-process settings such as Services in the SAP Reference IMG, choose Extended Warehouse Management Cross-Process Settings Delivery Processing. Business Add-Ins (BAdIs): For the inbound delivery, in the Implementation Guide (IMG), choose Extended Warehouse Management Business Add-Ins (BAdIs) for the Extended Warehouse Management Goods Receipt Process Inbound Delivery. For the outbound delivery, in the Implementation Guide (IMG), choose Extended Warehouse Management Business Add-Ins (BAdIs) for the Extended Warehouse Management Goods Issue Process Outbound Delivery. For the cross-process settings such as services, in the Implementation Guide (IMG) choose Extended Warehouse Management Business Add-Ins (BAdIs) for the Extended Warehouse Management Cross-Process Settings Delivery Processing.

SAP Extended Warehouse Management (SAP EWM)

510

108

SAP Online Help

20.07.2007

Warehouse Request
Definition
A warehouse request is a document that enables the processing of warehouse activities for a specific product. The warehouse activities for a product include the following: Picking Putaway Posting change Stock transfer (within warehouse) Scrapping

Use
You use this document in Extended Warehouse Management (EWM) to: Process specific product quantities within a warehouse for your goods receipt process or goods issue process (for example, for putaway or picking). Create posting changes [Seite 128] Process internal goods movements [Seite 122] Process scrappings [Seite 130]

EWM uses warehouse requests to build waves [Seite 773]. EWM works with both inactive and active document versions [Seite 119]. It creates warehouse tasks [Extern] to fulfill the warehouse requests. You can create, process, delete, or archive warehouse requests [Seite 135].

Structure
A warehouse request consists of Document categories with different document types. You can define the document types in Customizing for delivery processing.

For more information about defining document types in EWM, see the Implementation Guide (IMG) for EWM: Goods Receipt Process Inbound Delivery Define Document Types for Inbound Delivery Process Using Wizard Manual Settings Define Document Types for Inbound Delivery Process

Goods Issue Process Outbound Delivery Define Document Types for Outbound Delivery Process Using Wizard Manual Settings Define Document Types for Outbound Delivery Process

SAP Extended Warehouse Management (SAP EWM)

510

109

SAP Online Help

20.07.2007 Internal Warehouse Processes Delivery Processing Posting Changes Define Document Types for the Posting Change Process Using Wizard Manual Settings Define Document Types for Posting Change Process

Internal Warehouse Processes Delivery Processing Stock Transfers Define Document Types for the Stock Transfer Process Using Wizard Manual Settings Define Document Types for the Stock Transfer Process

Item categories with different item types. You can define the item types in Customizing for delivery processing.

For more information about defining item types in EWM, see the Implementation Guide (IMG) for EWM: Goods Receipt Process Inbound Delivery Define Item Types for Inbound Delivery Process Using Wizard Manual Settings Define Item Types for Inbound Delivery Process

Goods Issue Process Outbound Delivery Define Item Types for Outbound Delivery Process Using Wizard Manual Settings Define Item Types for Outbound Delivery Process

Internal Warehouse Processes Delivery Processing Posting Changes Define Item Types for the Posting Change Process Using Wizard Manual Settings Define Item Types for the Posting Change Process

Internal Warehouse Processes Delivery Processing Stock Transfers Define Item Types for the Stock Transfer Process Using Wizard Manual Settings Define Item Types for the Stock Transfer Process

Services that EWM can use. These include: Text management [Seite 145] Quantity offsetting [Seite 97]

SAP Extended Warehouse Management (SAP EWM)

510

110

SAP Online Help

20.07.2007

Status management [Seite 94] Field control [Seite 99] Connection to the Post Processing Framework (PPF) [Seite 105]

Integration
Systems outside of EWM send messages for a warehouse request to EWM. For a goods receipt process, this is an ERP system. For a goods issue process, this is a sales order system.

For more information about Customizing of integration between an Enterprise Resource Planning (ERP) system and EWM, see the Implementation Guide (IMG) for EWM under Interfaces ERP Integration.

SAP Extended Warehouse Management (SAP EWM)

510

111

SAP Online Help

20.07.2007

Warehouse Req. for Inbound Delivery or Outbound Delivery Order


Definition
This warehouse request defines a work list for Extended Warehouse Management (EWM) that determines whether to put away or pick goods.

Use
The warehouse request for an inbound delivery or outbound delivery order serves in EWM as basis for the execution of putaway or picking activities. For example, EWM uses a warehouse request to create warehouse tasks for putaway or picking. As well, EWM executes the posting of goods movements for the goods receipt or goods issue based on the warehouse request. EWM uses the inbound delivery notification or outbound delivery request, in other words the messages from the ERP system, to create a warehouse request for an inbound delivery [Seite 88] or an outbound delivery order [Seite 91].

Structure
For a description of the structure of a warehouse request, see Warehouse Request [Seite 109]. The warehouse request for inbound and outbound deliveries includes additional fields and functions, compared to an inbound delivery or outbound delivery order.

Integration
EWM receives inbound delivery notifications [Seite 87] or outbound delivery requests [Seite 90] from other systems. Based on these messages, EWM can automatically create the corresponding warehouse requests for inbound or outbound deliveries. However, you can also create these warehouse requests manually. In the case of outbound deliveries, manual creation is limited to the warehouse requests for the scrapping process. See also: Creation of a Warehouse Request for an Inbound Delivery [Seite 113], Warehouse Request for Inbound Delivery or Outbound Delivery Order [Seite 116], and Scrapping [Seite 130]. The priority points are calculated in SAP Advanced Planning & Optimization. The inbound delivery only displays these priority points. See also: Determination of Priority for Inbound Deliveries [Seite 414]

SAP Extended Warehouse Management (SAP EWM)

510

112

SAP Online Help

20.07.2007

Creating a Warehouse Request for an Inbound Delivery


Use
Extended Warehouse Management (EWM) uses this function to create a warehouse request for your goods receipt process (inbound delivery notification).

Integration
When EWM creates a warehouse task for a warehouse request, it updates the document flow for the warehouse request for the delivery. When you generate a warehouse request for an inbound delivery, you can generate valueadded service orders (VAS orders) automatically for the warehouse request item [Seite 231].

Prerequisites
The warehouse process type in the warehouse request must be defined. For more information about defining and determining the warehouse process type, see the Implementation Guide (IMG) for EWM under Cross-Process Settings Warehouse Task Define Warehouse Process Type and Determine Warehouse Process Type.

Features
The common functions that run when creating or changing a warehouse request (either inbound or outbound) automatically, as well as for the inbound delivery and outbound delivery order, enable you to do the following: Automatic Packing EWM automatically creates handling units according to the packing instruction. It uses the condition technique to do this. Connection to SAP Business Information Warehouse When a delivery item has been completed in EWM, EWM sends the current data to SAP Business Information Warehouse. A prerequisite for this is that you must have activated the update of delivery items in SAP Business Information Warehouse. For more information, see the IMG for EWM under Interfaces SAP Business Information Warehouse General Settings Activate BW Update. The additional functions that run when creating or changing a warehouse request automatically for the inbound delivery, enables you to do the following: If no packaging specification [Extern] exists for the packing of products during goods receipt, EWM can automatically trigger a WebFlow or SAP Alert Framework to notify someone. For this to occur, you must have defined the WebFlow or SAP Alert Framework accordingly. For more information, see the IMG for SCM Basis under Packing Packaging Specification. For more information about the WebFlow Engine, see the SAP Library under SAP Web Application Server Business Management (BC-BMT) WebFlow Engine (BCBMT-WFM). For more information about Alert Management, see the SAP Library under SAP Web Application Server Basis-Services/Communications Interface (BC-SRV) Business Workplace and Services (BC-SRV-OFC) Alert Management (BC-SRV-GBT-ALM).

SAP Extended Warehouse Management (SAP EWM)

510

113

SAP Online Help

20.07.2007

Determination of a payment for each delivery item Review of the handling unit type for notified handling units During creation of an inbound delivery with a corresponding handling unit, delivery processing checks whether the handling unit is permissible for the warehouse in question. For more information, see the IMG for EWM under Goods Receipt Process Slotting Influencing Parameters HU Types Define HU Types per Warehouse Number.

Creation of batches Before you create batches, you must assign a batch class of the class type 023 to the product subject to a batch management requirement in SAP ERP. You have also assigned the object characteristics LOBM_HERKL (country of origin) and LOBM_VFDAT (shelf life expiration date, minimum shelf life) to the batch class. A batch of the product must also exist already in EWM. If the batch is known in ERP, the ERP system sends this information to EWM. EWM automatically provides this in the delivery. If a batch is unknown in EWM, you can specify this batch manually in the inbound delivery.

For more information, see Connection of Delivery Processing to Batch Management [Seite 245]. Goods receipt posting If EWM automatically creates a delivery based on a warehouse request from ERP, you can carry out partial goods receipt postings using the warehouse task confirmation. When you confirm a warehouse task, EWM automatically executes a corresponding partial goods receipt posting. It reports this to ERP. With the delivery UI, you can either post the goods receipt for individual handling units only, or you can post it completely.

Wave assignment For more information about Customizing, see the IMG for EWM under Goods Issue Process Wave Management.

Activities
At the same time as an inbound delivery is generated in ERP, ERP sends a message for an inbound delivery notification [Seite 87] or posting change request to EWM. EWM automatically generates a warehouse request using the Post Processing Framework (PPF). During automatic creation and saving of the warehouse request, EWM triggers the following: Mapping of delivery data from ERP onto the EWM delivery data Data enrichment using data from the functions described under Features Wave assignment, depending on your Customizing Determination of warehouse process type, which controls the processing of a warehouse task in EWM, such as whether EWM is to immediately confirm a warehouse task

SAP Extended Warehouse Management (SAP EWM)

510

114

SAP Online Help

20.07.2007

EWM creates the warehouse tasks at the same time as releasing the wave. In accordance with the warehouse tasks, EWM creates warehouse orders to assemble work packages for the individual warehouse workers. For more information, see Warehouse Order Creation [Seite 419] and Creation of Warehouse Tasks for Warehouse Request [Seite 412].

EWM copies most of the settings that you make in Customizing for process control to the delivery documents, and displays them on the user interface for the outbound delivery order. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery Maintain Outbound Delivery Order. Display an outbound delivery order in the form view. Here you can find the settings from Customizing, for example, in the Corr.Deliv., Scrapping, or Pickup fields.

SAP Extended Warehouse Management (SAP EWM)

510

115

SAP Online Help

20.07.2007

Generation of a Warehouse Request for an Outbound Delivery Order


Use
Extended Warehouse Management (EWM) uses this function to generate a warehouse request for your goods issue process (outbound delivery request).

Integration
When you generate a warehouse request for an outbound delivery order, you can generate value-added service orders (VAS orders) automatically for the warehouse request item [Seite 231]. When you generate a warehouse request for an outbound delivery order, EWM can perform route determination [Seite 638] in accordance with your Customizing.

Prerequisites
The warehouse process type in the warehouse request must be defined. For more information about defining and determining the warehouse process type, see the Implementation Guide (IMG) for EWM under Cross-Process Settings Warehouse Task Define Warehouse Process Type and Determine Warehouse Process Type.

Features
The common functions that run when creating or changing a warehouse request (either inbound or outbound) automatically, as well as for the inbound delivery and outbound delivery order, enable you to do the following: Automatic packing EWM automatically creates handling units according to the packing instruction. It uses the condition technique to do this. You can assign handling units and cross-delivery handling units to an outbound delivery order. ERP copies this information to the corresponding ERP outbound delivery. Connection to SAP Business Information Warehouse When a delivery item has been completed in EWM, EWM sends the current data to SAP Business Information Warehouse. As a prerequisite, you must have activated the update of delivery items in SAP Business Information Warehouse. For more information, see the IMG for EWM under Interfaces SAP Business Information Warehouse General Settings Activate BW Update. The additional functions that run when creating or changing a warehouse request automatically for the outbound delivery order, enables you to do the following: Rough determination of the picking location The system determines the source storage bins for a delivery based on the stock removal strategies. However, it does not make quantity reservations for the products. You can use the activity area that is assigned to the storage bin as a selection criterion.

A delivery contains three delivery items of 10 tires each. The system determines the same source storage bin for each delivery item. It contains 10 tires only. Therefore, the total quantity of 30 tires does not exist at the source storage bin. For fixed storage bins, the system organizes the total quantity using replenishment strategies.

SAP Extended Warehouse Management (SAP EWM)

510

116

SAP Online Help

20.07.2007

For more information about Customizing for stock removal strategies, see the IMG for EWM under Goods Issue Process Strategies. Determination of which products can be packed together for a shipment Determination of staging area Determination of door assignment Determination of warehouse process type For more information, see the IMG for EWM under Cross-Process Settings Warehouse Task Determine Warehouse Process Type. Route determination Determination of staging area group Adding packing items If, for example, you use recyclable packing materials, you can manually add delivery items for the packing material to an outbound delivery order and then post goods issue again for this packing material (see also Processing of Packaging Items [Seite 165]). On the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Maintain Outbound Delivery Order. Select an outbound delivery order, and on the Items tab page, choose with the quick info Create. Use the input help to select a packing item type. You can control processes for outbound delivery orders as part of the configuration. For example, you can create an invoice before goods issue in the outbound delivery process. You can also do this on the basis of other delivery parameters, for example, the export relevance or the route that is determined. As a prerequisite, you have defined process indicators for the delivery document header and for the delivery document items in Customizing for EWM. For more information, see the IMG for EWM under Cross-Process Settings Delivery Processing Process Management and Control. You can enter the account assignment on the user interface for the outbound delivery order in the detail view of the item on the Account Assignments tab page.

A department within your company requests consumable material from your warehouse. Inventory management is no longer required for this consumable material. You update the consumable material, for example, for a cost center or project, by entering the account assignment on the user interface for the outbound delivery order.

Activities
At the same time as an outbound delivery is generated in ERP, ERP sends a message for an outbound delivery request [Seite 90] or posting change request to EWM. EWM automatically generates a warehouse request using the Post Processing Framework (PPF). During automatic creation and saving of the warehouse request, EWM triggers the following: Mapping of delivery data from ERP onto the EWM delivery data Data enrichment using data from the functions described under Features Wave assignment, depending on your Customizing

SAP Extended Warehouse Management (SAP EWM)

510

117

SAP Online Help

20.07.2007

Determination of warehouse process type, which controls the processing of a warehouse task in EWM, such as whether EWM is to immediately confirm a warehouse task

EWM creates the warehouse tasks at the same time as releasing the wave. In accordance with the warehouse tasks, EWM creates warehouse orders to assemble work packages for the individual warehouse workers. For more information, see Warehouse Order Creation [Seite 419] and Creation of Warehouse Tasks for Warehouse Request [Seite 412].

EWM copies most of the settings that you make in Customizing for process control to the delivery documents, and displays them on the user interface for the outbound delivery order. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery Maintain Outbound Delivery Order. Display an outbound delivery order in the form view. Here you can find the settings from Customizing, such as in the field Corr.Deliv., Scrapping or Pickup.

SAP Extended Warehouse Management (SAP EWM)

510

118

SAP Online Help

20.07.2007

Using Inactive and Active Document Versions


Purpose
Extended Warehouse Management (EWM) can accept or reject change messages for inbound deliveries from the ERP system. EWM uses inactive and active document versions for this. If warehouse activities (follow-on activities) have already begun for inbound deliveries, EWM rejects change messages from the ERP system. For example, EWM has already created a warehouse task (WT) for an inbound delivery. In doing so, EWM has also already set the status type Warehouse Activities to the status value Partially Completed. In the case of outbound deliveries, EWM can only accept a reduction of the quantity from the ERP system. If warehouse activities (follow-on activities) have already begun for inbound deliveries, EWM rejects the message from the ERP system.

Prerequisites
You have determined the document type for the Post Processing Framework (PPF) action for activating an inbound delivery notification or the outbound delivery request 3 Immediate Processing. You do this in Customizing for the PPF in the action profile in EWM. To do so, in Customizing for Extended Warehouse Management, choose Cross-Process Settings Delivery Processing Actions Change Actions and Conditions Define Action Profile and Actions. Select the action profile for an inbound delivery notification (/SCDL/IDR) or for an outbound delivery request (SCWM/ODR). Choose Action Definition in the dialog structure and go from there to the Action Definition tab page in the Action Settings screen area for processing time 3 Immediate Processing. In Customizing, you have assigned the defined action profile to a document type. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management under Goods Receipt Process Inbound Delivery Define Document Types for Inbound Delivery Process Using Wizard, or under Goods Issue Process Outbound Delivery Define Document Types for Outbound Delivery Process Using Wizard. In the case of inbound deliveries, the status type Warehouse Activities has the status value Not Started in the document. On the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Inbound Delivery Maintain Inbound Delivery Order. At header level, check whether the status type Warehouse Activities has the status value Not Started. The following conditions have been fulfilled in the case of outbound deliveries: The status type Warehouse Activities has the status value Not Started in the document. On the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery Maintain Outbound Delivery Order or Maintain Outbound Delivery. At item level, check whether the status type Warehouse Activities has the status value Not Started for the respective delivery item. The status type Locked (Overall Status) has the status value No in the document. On the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery Maintain Outbound Delivery Order or Maintain Outbound Delivery. At item level, check whether the staus type Locked (Overall Status) has the status value No. Neither you or the system have assigned a wave [Seite 771] to the delivery item in the document.

SAP Extended Warehouse Management (SAP EWM)

510

119

SAP Online Help

20.07.2007

Process
Creating New Documents in EWM
...

1. You create a new document (for example, an inbound delivery) in the ERP system and you save it. 2. The ERP system informs EWM of this and EWM creates a corresponding inactive document, for example, an inbound delivery notification IDN. 3. Depending on your Customizing settings for the PPF, the following is either performed by you or by EWM. a. If you determined document type 3 Immediate Processing in the PPF Customizing settings in the action profile in EWM, EWM automatically activates the inactive document. As a result of this activation, EWM creates the active successor document. For example, EWM automatically activates an inbound delivery notification IDN and creates an active inbound delivery ID. If EWM cannot perform the PPF action due to an error, EWM creates an inactive document, in other words, an inactive inbound delivery notification or an inactive outbound delivery request. You can manually activate and save these. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing and then one of the following options: Inbound Delivery Maintain Inbound Delivery Notification and the Activate pushbutton. Outbound Delivery Maintain Outbound Delivery Request and the Activate pushbutton.

b. If you have not determined document type 3 Immediate Processing in the PPF Customizing settings in the action profile in EWM, EWM always creates an inactive document. You can manually activate and save these. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing and then one of the following options: Inbound Delivery Maintain Inbound Delivery Notification and the Activate pushbutton. Outbound Delivery Maintain Outbound Delivery Request and the Activate pushbutton.

Accepting Inbound Delivery Changes to ERP Documents in EWM


...

1. You change an ERP inbound delivery, for example, you change the quantity and save this change. The ERP system creates a new document with a temporary document number. 2. The ERP system notifies EWM to replace the inactive inbound delivery. 3. EWM creates a corresponding inactive document for the existing document. In other words, EWM creates an inactive inbound delivery notification for an existing active inbound delivery notification. The inactive document has the same document number as the existing active document. The active inbound delivery notification IDN corresponds to the active inbound delivery ID in EWM that contains the unchanged quantities. 4. EWM carries out one of the following options: a. If EWM has not yet carried out any changes for the active document (that is, the status type Warehouse Activities still has the status value Not Started), EWM accepts the message from the ERP system. Depending on your Customizing settings for the PPF, the inactive document is either activated by you or by EWM. EWM copies the changes to the active

SAP Extended Warehouse Management (SAP EWM)

510

120

SAP Online Help

20.07.2007

document. For example, EWM activates an inactive inbound delivery notification with a quantity change from the ERP system. EWM copies the quantity changes to the inbound delivery, that is, the inactive inbound delivery notification overwrites the active inbound delivery notification. b. If EWM has already carried out changes for the inactive document, or it cannot carry out the quantity change from the ERP system, EWM rejects the change message from the ERP system. EWM does not copy the changes to the active document. For example, EWM has already created a warehouse task for an inbound delivery and has set the status value Partially Started for the status type Warehouse Activities. If you now make another change to the inbound delivery in the ERP system, EWM does not copy this change to the active inbound delivery. 5. EWM informs the ERP system of the rejection or acceptance. 6. The ERP system deletes the temporarily created ERP document number again.

Accepting Outbound Delivery Changes to ERP Documents in EWM


...

1. In SAP Customer Relationship Management (SAP CRM), the quantity of an order is reduced and SAP CRM sends this quantity change to the ERP system. 2. The ERP system then sends the quantity change to EWM.

In contrast to inbound delivery cases, EWM does not create a corresponding inactive document (in other words, an inactive outbound delivery request) for the existing active document in the case of outbound deliveries. 3. EWM carries out one of the following options: a. If EWM has not yet carried out any changes for the active document (that is, the status type Warehouse Activities still has the status value Not Started), and the other prerequisites for outbound delivery cases apply (see Prerequisites), EWM accepts the message from the ERP system. EWM copies the quantity reduction to the active document. b. If EWM has already carried out changes for the inactive document, or it cannot carry out the quantity reduction from the ERP system, EWM rejects the message from the ERP system. EWM does not copy the quantity reduction to the active document. 4. EWM informs the ERP system of the rejection or acceptance. 5. If necessary, the ERP system changes its outbound delivery in accordance with the message.

For more information about document control and processing checked deliveries in the ERP system, see the SAP Library under Documentation SAP ERP Central Component SAP ERP Central Component Logistics General Logistics (LO) Service Parts Management: See Also: Outbound Delivery Notification [Seite 87] Outbound Delivery Request [Seite 91] Architecture and Communication document control. Goods Issue Process processing checked deliveries.

SAP Extended Warehouse Management (SAP EWM)

510

121

SAP Online Help

20.07.2007

Warehouse Request for Internal Stock Transfer


Definition
This warehouse request defines all warehouse-internal goods movements in Extended Warehouse Management (EWM).

Use
You use this document to plan your warehouse process for ad hoc movements, replenishments, and warehouse reorganization in EWM. Since you can only use this document within the warehouse, it does not contain any delivery-based reference documents in other systems (for example, SAP R/3). Your processes in this case are only visible within the warehouse. After completion of the process, EWM informs the connected systems about the process execution. You execute the internal stock transfer directly from storage bin A to storage bin B without an intermediate stop (such as packing station). As a result, there is one picking and putaway bin for every internal stock transfer. You or EWM indicate these storage bins when creating warehouse requests. For more information about warehouse-internal functions, see Ad Hoc Movement [Seite 125], Replenishment [Seite 126], or Warehouse Reorganization [Seite 127].

Structure
For the structural description of a warehouse request, see Warehouse Request [Seite 109].

Integration
EWM sends the posting change which it executes for the internal stock transfer, as a goods movement message to SAP R/3.

SAP Extended Warehouse Management (SAP EWM)

510

122

SAP Online Help

20.07.2007

Internal Stock Transfers


Purpose
With this warehouse process, you can execute the following warehouse-internal product movements in Extended Warehouse Management (EWM): Ad Hoc movement Replenishment Warehouse reorganization

Process
The following figure shows you a sample description for the flow of an internal stock movement:

Wave Planner

User

SAP WM

Create warehouse request

Create warehouse request

Release wave

Create transfer order

Process transfer order

Confirm transfer order

Confirm transfer order

Close warehouse request

...

1. Either you create a warehouse request manually in EWM using the user interface, or EWM does this automatically. 2. When the wave is released, EWM creates the corresponding warehouse tasks (WTs), which reduce the planned open quantity for internal goods movement and block the product. When EWM creates WTs, it simultaneously determines from which stock it fulfills the warehouse request. By creating WTs as late as possible, EWM also blocks the necessary stock of the product as late as possible.

SAP Extended Warehouse Management (SAP EWM)

510

123

SAP Online Help 3. You process the WTs and confirm them. 4. EWM updates the warehouse request. 5. EWM closes the warehouse request if one of the following options applies:

20.07.2007

The reduced quantity [Extern] represents the target quantity of the warehouse request. The quantity offsetting notifies you at the same time that the open quantity is zero.

The quantity reduced by the confirmed WTs does not represent the target quantity of the warehouse request. However, you specify process codes for the difference quantities. Quantity offsetting takes these into account.

WTs for warehouse-internal processes move products from one storage bin to another. They therefore contain a putaway and picking step at the same time, whereas the process step Load, for example, is omitted.

Result
You have executed an internal stock movement. EWM has created, updated, and closed the corresponding warehouse request.

SAP Extended Warehouse Management (SAP EWM)

510

124

SAP Online Help

20.07.2007

Executing an Ad Hoc Movement


Use
You can use this function for the following: An ad hoc decision for a planned stock movement that triggers the creation of a warehouse request.

In the case of a spontaneous decision for a planned stock movement, you can create a warehouse request. You can use this warehouse request in a wave. Once Extended Warehouse Management (EWM) has created the corresponding warehouse task (WT), you can execute the stock movement. An ad hoc decision together with an ad hoc movement that triggers the creation of a WT with immediate, automatic confirmation.

In the case of a spontaneous decision for an immediate stock movement, you can immediately create a warehouse task. Here you execute the stock movement immediately and without a warehouse request.

Features
You can, for example, transfer a product damaged in the storage bin (for example, water damage) to another storage bin. To do this, you create a manual warehouse request that sets the picking and putaway storage bin. On the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Maintain Internal Stock Transfer. EWM transfers these storage bins during WT creation. See also: Ad Hoc Movement [Seite 415]

Activities
You create warehouse requests for ad hoc movements manually through a user interface. On the SAP Easy Access screen, choose Extended Warehouse Management Work Scheduling Create Warehouse Task Without Reference Move Product. Then choose Create (Create Warehouse Request) instead of Create (Create Warehouse Task). Alternatively, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Maintain Internal Stock Transfer.

SAP Extended Warehouse Management (SAP EWM)

510

125

SAP Online Help

20.07.2007

Executing a Replenishment
Use
You can use this function for warehouse-internal replenishment planning. This ensures that you do not fall short of a picking bins minimum quantity. Replenishment fills picking bins from the reserve storage area. Furthermore, you can use this warehouse request to schedule several replenishments in waves, and to plan the execution of replenishments separately from the requirements, for example, only execute replenishments at night. Extended Warehouse Management (EWM) creates this warehouse request with a background job or you can execute the replenishment planning in the dialog.

Features
When creating warehouse requests, EWM specifies possible picking bins and final putaway storage bins. EWM checks the picking bins again before it uses them as final picking bins in the warehouse task. You can change warehouse requests for the replenishment retroactively. For more information about executing replenishments, see the relevant report documentation. On the SAP Easy Access screen, choose Extended Warehouse Management Work Scheduling Schedule Replenishment. On the Execute Replenishment screen that follows, choose Program Documentation to see the report documentation.

Activities
To retroactively change a warehouse request for replenishment, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Maintain Internal Stock Transfer. For replenishment planning in the dialog, on the SAP Easy Access screen, choose Extended Warehouse Management Work Scheduling Schedule Replenishment.

SAP Extended Warehouse Management (SAP EWM)

510

126

SAP Online Help

20.07.2007

Executing a Warehouse Reorganization


Use
You use this function to optimize the access paths within your warehouse. Here, Extended Warehouse Management (EWM) uses a warehouse order to reorganize your stock. Since EWM uses a warehouse request for the warehouse reorganization, you can plan your reorganization and start it in a wave.

Features
EWM executes a temporary storage bin determination, which does not make a reservation. EWM uses the results of the storage bin determination within the wave determination.

Activities
To create this warehouse request, on the SAP Easy Access screen, choose Extended Warehouse Management Work Scheduling Warehouse Reorganization.

SAP Extended Warehouse Management (SAP EWM)

510

127

SAP Online Help

20.07.2007

Warehouse Request for Posting Changes


Definition
This warehouse request defines the changes in stock categories of a product in Extended Warehouse Management (EWM).

Use
The warehouse request for posting changes [Extern] is a document that you use in EWM for the following: For planned posting changes, such as a scrapping request, without reference to a posting change request. In other words, for a process triggered inside the warehouse. For unplanned posting changes, such as a scrapping request, with reference to a posting change request. In other words, for a process triggered outside the warehouse. SAP R/3 triggers this when it sends a delivery output to EWM. For more information, see Interfaces for Communication from EWM to the ERP System [Seite 257]. You can also create posting changes directly, without using a warehouse request.

Structure
For the structural description of a warehouse request, see Warehouse Request [Seite 109].

Integration
You or SAP R/3 trigger the posting change externally. In this case, SAP R/3 sends a delivery output to EWM. EWM then creates a posting change request. EWM can execute the posting change directly upon creation of a warehouse request for a posting change. You can detect this in the goods movement status of the warehouse request. Planned posting changes, which are based on a warehouse request, can also have an associated warehouse task (WT) for a posting change. For example, if you want to execute a posting change from unrestricted-use stock to blocked stock, a physical stock transfer may also be necessary due to the warehouse structure. EWM creates a WT for this stock transfer. If EWM has not executed the posting change, the posting change is executed in one of the following ways: Automatically by EWM through a PPF action, if you have confirmed the WTs Manually by you in the user interface

If you want to create a posting change manually, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Posting Change Maintain Posting Change. If you want to create a posting change directly, in other words without using a warehouse request, on the SAP Easy Access screen, choose Extended Warehouse Management Work Scheduling Make Posting Change for Product. In the transaction, choose the function to create a posting change. If you want to view the goods movement status to check the posting changes created directly upon warehouse request creation, on the SAP Easy Access

SAP Extended Warehouse Management (SAP EWM)

510

128

SAP Online Help

20.07.2007

screen, choose Extended Warehouse Management Delivery Processing Posting Change Maintain Posting Change and then Status, Goods Movement.

SAP Extended Warehouse Management (SAP EWM)

510

129

SAP Online Help

20.07.2007

Performing Scrapping
Use
You can use this function in the following scenarios: Scrapping within the warehouse, if a product is to be disposed of from the warehouse (for example, defective or obsolete product) Scrapping within a returns process

Here you can process warehouse-internal or warehouse-external decisions to scrap a product.

Integration
Only scrapping triggered outside the warehouse, such as from the ERP system, is related to a preceding document (delivery request document). For these types of scrapping, Extended Warehouse Management (EWM) sends a delivery output to the ERP system. For scrapping triggered inside the warehouse, EWM sends the following to the ERP system: If you are using SAP ERP 2007, EWM sends a delivery message. If you are using an older SAP ERP release, EWM sends a goods movement message.

Features
For warehouse-internal processing of products to be scrapped, you create a warehouse request for the posting change. The system thus posts the products to the blocked stock. From there, you can clear the products through goods issue. EWM can execute the goods issue with or without the corresponding outbound delivery document. EWM processes the scrapping in the returns process with a returns delivery, inspection lots, and inspection results. You can trigger the scrapping warehouseinternally in EWM, or warehouse-externally, for example with SAP Customer Relationship Management. A warehouse worker in the quality department can use an inspection procedure to carry out the decision to scrap a product. Based on the inspection results, he or she can decide whether a product is still to be used or should be scrapped.

Activities
You move the products to be scrapped from the different storage bins to a scrapping handling unit (scrapping HU). This represents an internal stock movement that is triggered by the following: Warehouse-internal decision, for example, by a warehouse worker in the quality department Warehouse-external decision when a scrapping message is sent

At the same time, EWM posts the quantity to be scrapped as blocked stock. In other words, it carries out a posting change. EWM uses a warehouse request for the posting change for this step. You can use this warehouse request for the posting change during wave creation. You book the goods issue (GI) for the scrapping HU. EWM can execute the GI with the corresponding outbound delivery document. EWM can also execute the GI without a corresponding outbound delivery document. This represents a GI posting without delivery. 510 130

SAP Extended Warehouse Management (SAP EWM)

SAP Online Help

20.07.2007

SAP Extended Warehouse Management (SAP EWM)

510

131

SAP Online Help

20.07.2007

Warehouse Request for Returns


Definition
This warehouse request defines all product movements to be able to display the goods returned by a customer in Extended Warehouse Management (EWM).

Use
The warehouse request for returns in EWM forms the basis for executing follow-up activities. Follow-up activities for returns include: Reject the inbound delivery after carrying out a rough inspection You first conduct a rough inspection of the inbound delivery. In doing so, if you determine that the forwarding agent does not need to unload the goods, rather can take the goods right back with it because the goods are damaged, for example, you can immediately reject the inbound delivery. On the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Inbound Delivery Maintain Inbound Delivery Notification and then Reject Maintain Inbound Delivery and then Reject

For more information, see also Goods Receipt [Seite 263]. Putaway [Seite 300] Scrapping [Seite 130] Transferring Delivery to internal remanufacturer Delivery (to customer or external remanufacturer)

You cannot change returns deliveries that, for example, SAP Customer Relationship Management sends to EWM. The external system controls the returns process and determines which items in which quantities the customer can send back. In particular, you cannot do the following: Create new delivery items Delete delivery items Split delivery items

Structure
The structure of a warehouse request for returns differs from the generic structure of a warehouse request as follows: Different item types are used Item category RET is used A different configuration of the item types and the item category is used.

SAP Extended Warehouse Management (SAP EWM)

510

132

SAP Online Help

20.07.2007

EWM uses a status profile specifically for the warehouse request for returns: /SCDL/INB_PRD_RET for an inbound delivery /SCDL/INB_REQ_RET for an inbound delivery notification

Thus, EWM can carry out the following: Create the inspection documents automatically (inspection planning) Adjust the status type Q-Inspection automatically when the inspection results are entered The status type Q-Inspection specifies the start and end of the quality inspection. Control the follow-up activities, such as putaway, based on the inspection results SAP CRM determines whether SAP CRM or EWM is to determine followup activities. EWM maps this with status type Blocked According to QM. The status type Blocked After QM specifies that following the quality inspection, the returns stock is blocked from further use until an external system, for example, SAP CRM, makes a usage decision. If status type Blocked According to QM is not set in EWM, you can determine the follow-up activity in EWM. EWM automatically triggers the corresponding logistical processes, such as putaway or returning to the customer. If status type Blocked According to QM is set in EWM, then EWM must first send the inspection result to SAP CRM. After this, SAP CRM determines the follow-up activity and sends it to EWM. EWM triggers the corresponding logistical processes. You can carry out stock transfers in the warehouse during the whole process.

If you carry out a step-by-step inspection in multiple warehouses, then you carry out an individual inspection for each warehouse. If the current warehouse is not the last warehouse in the sequence, EWM sets the status type Blocked QM f. Putaway. Thus, you can only put returns away after the last inspection has been carried out. However, you can scrap or send returns back after each individual inspection. The step-by-step inspection does not affect delivery processing. EWM adopts the effective dates/times from SAP CRM. SAP CRM determines the date and time fort he external and internal validity of the returns and sends this data to EWM. EWM maps the data for external and internal validity to the corresponding date types Internal Validity RMA for Returns and External Validity RMA for Returns and saves them in the delivery item. These date/time types determine whether EWM accepts or rejects returns. If both date/time types have expired, EWM rejects the returns. If the external date/time type has expired, but the internal date/time type is still valid, SAP CRM determines the follow-up activities and decides whether or not to reject the returns. EWM adopts this decision.

For the structural description of a warehouse request, see Warehouse Request [Seite 109].

SAP Extended Warehouse Management (SAP EWM)

510

133

SAP Online Help

20.07.2007

Integration
SAP CRM triggers the returns. It sends a delivery notification to EWM. EWM then creates a warehouse request for returns. EWM conducts inspection planning with quantity offsetting, and saves the inspection results in the warehouse request for returns. In addition, EWM sends the inspection result to SAP CRM.

SAP Extended Warehouse Management (SAP EWM)

510

134

SAP Online Help

20.07.2007

Processing, Deleting, and Archiving Warehouse Requests


Use
You can process, delete, or archive warehouse requests.

Features
The following table gives you an overview of the functions you can execute for the individual warehouse requests. Object for which EWM creates a warehouse request Create (manually by user, automatically by EWM) Manually Process Delete Archive

Inbound Delivery Notification

X Activation possible only: restricted processing X X ----X X X (only header data) ----X X

Automatically

------

Inbound Delivery

Manually Automatically

X X ----X X X ----X X

X X X X X X X X X

Outbound Delivery Request Outbound Delivery Order

Automatically Manually Automatically

Outbound Delivery Manually Posting Change Request Posting Change Stock Transfer (incl. Scrapping) Automatically Manually Manually

The inbound delivery notification [Seite 87] and outbound delivery request [Seite 90] created automatically are messages from a sending system, such as an ERP system. You cannot process or delete these messages. For an inbound delivery notification or outbound delivery request created automatically, you can only activate or reject the document.

SAP Extended Warehouse Management (SAP EWM)

510

135

SAP Online Help

20.07.2007

HU Integration in Delivery Processing


Use
Handling unit integration (HU integration) in delivery processing is used to forward HU data between SAP R/3 and Extended Warehouse Management (EWM). The handling unit has a reference to the delivery.

Integration
All HU-relevant processes of the goods receipt process in EWM are based on the correct and complete forwarding of HU data from SAP R/3 to EWM. If this forwarding is incorrect or incomplete, errors occur in delivery processing. EWM simultaneously creates inbound deliveries and HUs in HU management. To do so, it uses the HU information from the inbound delivery notification. This means that EWM automatically creates HUs that have been defined in the ERP system.

Prerequisites
The mapping of HU data from SAP R/3 to EWM must be defined.

Features
Goods Receipt Process During goods receipt posting (GR posting), delivery processing determines which products exist in which quantities in the handling unit warehouse task. Delivery processing updates these quantities during inbound delivery. You can post the goods receipt (GR) in delivery processing completely or partially. EWM determines the packed quantity from the handling unit information. Delivery processing sets a status for the packed quantity (for example, unpacked, partially packed, completely packed). Goods Issue Process You can only post the goods issue (GI) on delivery basis completely. A partial GI posting is not possible. You post the GI for every delivery separately. If the Cross-Delivery indicator is set in the data for a cross-delivery handling unit, delivery processing posts the GI automatically for all associated deliveries.

The following figure shows an example GI posting process for cross-delivery handling units.

SAP Extended Warehouse Management (SAP EWM)

510

136

SAP Online Help

20.07.2007

Delivery 1
10 pcs 20 pcs 30 pcs HU1 HU1 HU2

Delivery 2
10 pcs 20 pcs HU2 HU3

Delivery 3
10 pcs 40 pcs HU3 HU4

= cross-delivery HU

You have a Delivery1 with HU1 and HU2. If you post the GI for HU2, delivery processing automatically posts the GI for HU1 as well, since it only posts one GI for the complete delivery.

HU2 is cross-delivery. In other words, it is also relevant for Delivery2. You must either post a GI completely for both deliveries using the selected delivery headers for Delivery1 and 2, or select HU1 and 2 and post the GI. If Delivery2 contains a HU3 that is also cross-delivery, you will get an error message.

Activities
If you want to view HU data for the inbound delivery, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Inbound Delivery Process Inbound Delivery. If you want to view, change, or delete HU data for the outbound delivery, choose one of the following options: On the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery Process Outbound Delivery Order. On the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery Process Outbound Delivery.

SAP Extended Warehouse Management (SAP EWM)

510

137

SAP Online Help

20.07.2007

User Interfaces in Delivery Processing


Use
The following user interfaces are available in Extended Warehouse Management (EWM) for the purpose of processing deliveries.

Features
User interfaces for the goods receipt process /SCWM/IDN (Maintain Inbound Delivery Notification) /SCWM/PRDI (Maintain Inbound Delivery)

User interfaces for the goods issue process /SCWM/ODR(Maintain Outbound Delivery Request) /SCWM/PRDO (Maintain Outbound Delivery Order) /SCWM/FD (Maintain Outbound Delivery)

User interfaces for posting changes /SCWM/IM_DR (Maintain Posting Change Request) /SCWM/IM_PC (Maintain Posting Change)

User interfaces for internal stock transfers /SCWM/IM_ST (Maintain Internal Stock Transfer)

Activities
From the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Inbound Delivery, Outbound Delivery or Posting Change, and then the required user interface. On the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Maintain Internal Stock Transfer.

SAP Extended Warehouse Management (SAP EWM)

510

138

SAP Online Help

20.07.2007

Basic Functions in Delivery Processing


Use
Delivery processing provides you with the following basic functions: Delivery note printing [Seite 143] Text management [Seite 145] Delivery quantity adjustment [Seite 147] Validation [Seite 159]

SAP Extended Warehouse Management (SAP EWM)

510

139

SAP Online Help

20.07.2007

Determination of Priority for Inbound Deliveries


Purpose
You use Extended Warehouse Management (EWM) priority points to achieve an optimal unloading sequence for several trucks at transportation unit level in the yard. At the same time, EWM updates the inbound delivery until the Warehouse Activities Status is Completed.

Process
...

1. The ERP system receives an advanced shipping notification (ASN) and creates an inbound delivery. 2. The ERP system notifies SAP APO and EWM about this. 3. Based on the notification, the system executes the following: a. SAP APO calculates the priority points at item level. b. EWM creates an inbound delivery request. EWM or you activate the inbound delivery request. EWM creates an inbound delivery from the active inbound delivery request. The priority points in the inbound delivery are initial (initial value is zero) until SAP APO sends the results of the calculation for an update. 4. SAP APO communicates the calculated priority points to the ERP system, which then communicates them to EWM. 5. EWM updates the priority points in the inbound delivery. EWM saves the priority points for an inbound delivery at item level. EWM calls the Business Add-In (BAdI) /SCWM/EX_DLV_DET_LOAD to display the inbound delivery. This BAdI calculates an aggregated priority at header level. 6. EWM aggregates the priority points at transportation unit level using the BAdI /SCWM/EX_SR_PRIOP. You can see this on the user interface for unloading. You can start the report /SCWM/PRIOP_UPDREQ for the recalculation of priority points from the SAP Easy Access display, under Extended Warehouse Management Delivery Processing Inbound Delivery Update Priority Points. EWM triggers an asynchronous request for the recalculation of priority points in SAP APO via the ERP system. As with the first calculation (step 4), SAP APO sends the result of this recalculation to EWM via the ERP system. EWM updates the priority points in the inbound delivery and aggregates the priority points at transportation unit level.

For more information, see the report documentation.

Results
SAP APO has calculated the priority points and has communicated this to EWM via the ERP system . Provided the Warehouse Activities status is not Completed, EWM has updated priority points in the inbound delivery.

SAP Extended Warehouse Management (SAP EWM)

510

140

SAP Online Help

20.07.2007

Printer Determination in Delivery Processing


Purpose
You can use this process in Extended Warehouse Management (EWM) to print various documents on particular printers in the different storage sections, for example, in the goods receipt area or goods issue area. EWM uses printer determination in the goods receipt process to print unloading instructions and in the goods issue process to print the delivery note and loading instructions.

Prerequisites
If appropriate, you have defined a print profile in the default values. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery Pickup. Choose Default Values and enter a print profile. If appropriate, you have implemented your own printer determination in Business AddIn (BAdI) /SCDL/PPF_ADD_DATA in method GET_PRINTER. For more information, see the BAdI documentation. If appropriate, you have implemented your own print profile determination in BAdI /SCWM/EX_DLV_PRINT_PROFILE. For more information, see the BAdI documentation. If appropriate, you have defined one or more print profiles in Customizing for EWM. For more information, see the Implementation Guide (IMG) for EWM under Extended Warehouse Management Goods Receipt Process Inbound Delivery Print Define Print Profiles for Delivery Processing and Goods Issue Process Outbound Delivery Print Define Print Profiles for Delivery Processing. If appropriate, you have defined one or more Post Processing Framework (PPF) actions in Customizing for the PPF. For more information, see the IMG for EWM under Extended Warehouse Management Cross-Process Settings Delivery Processing Actions Change Actions and Conditions Define Action Profiles and Actions and Define Conditions. You have defined print profile determination for the goods receipt process or goods issue process in Customizing for EWM. For more information, see the IMG for EWM under Extended Warehouse Management Goods Receipt Process Inbound Delivery Print Define Print Profile Determination for Goods Receipt Process or Goods Issue Process Outbound Delivery Print Define Print Profile Determination for Goods Issue Process.

Process
EWM attempts to determine the printer in the following sequence:
...

1. EWM checks whether you have specified a print profile in the default values on the user interface for pickup. If so, it uses the name of the printer from this print profile. 2. If EWM cannot find a printer in step 1, it checks whether you have implemented your own printer determination in BAdI /SCDL/PPF_ADD_DATA. If so, it uses this printer. 3. If EWM cannot find a printer in step 2, it checks whether you have implemented your own print profile determination in BAdI /SCWM/EX_DLV_PRINT_PROFILE. EWM uses the printer from this print profile.

SAP Extended Warehouse Management (SAP EWM)

510

141

SAP Online Help

20.07.2007

4. If EWM cannot find a printer in step 3, it checks whether you have defined a print profile determination for the goods receipt process or the good issue process in Customizing for EWM. EWM uses the printer from this print profile. You can define an access sequence for print profile determination. As a result, EWM considers one or more combinations of different parameters for the print profile, for example, goods receipt office, ship-to location, and warehouse number. 5. If EWM cannot find a printer in step 4, it checks whether you have specified a printer in the user master data. On the SAP Easy Access screen, choose System User Profile Own Data to specify your own output device in the Spool Control group box on the Defaults tab page. If EWM does not find a printer, it does not schedule the PPF action for printing. See also: Print Profile Determination for Invoice Printout [Seite 372] Printing Delivery Notes [Seite 143]

SAP Extended Warehouse Management (SAP EWM)

510

142

SAP Online Help

20.07.2007

Printing Delivery Notes


Use
You use this function in Extended Warehouse Management (EWM) to print delivery notes.

Prerequisites
You have created either an outbound delivery order or an outbound delivery.

Features
EWM prints the delivery note based on the PPF action /SCWM/PRD_OUT_PRINT for an outbound delivery order or /SCWM/FD_OUT_PRINT for an outbound delivery. By default, EWM uses the predefined SAP Smart Form /SCWM/DLV_NOTE. However, you can also create your own SAP Smart Form to use when printing the delivery note and for form determination. You can also print delivery notes using a PDF-based form. To do this, you must change the assigned processing of the PPF action from Smart Forms Print to External Communication in Customizing for EWM. For more information about action conditions, see the Implementation Guide (IMG) for EWM under Extended Warehouse Management Cross-Process Settings Delivery Processing Actions Change Actions and Conditions Define Conditions. EWM automatically prints the delivery note for an outbound delivery as soon as you have posted the goods issue. You can also use a PPF action to manually print a delivery note for an outbound delivery or outbound delivery order.

For more information about Smart Forms, see the SAP Library under SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability Business Services Smart Forms. For more information about form determination, see the IMG for EWM under Extended Warehouse Management Goods Issue Process Outbound Delivery Print Determine Form Determination for Delivery Note Printing. You can display a preview of the delivery note before printing it. EWM issues the dangerous goods data when printing the delivery note. In doing so, EWM uses detailed information about the route and means of transport to determine the relevant dangerous goods master records. For more information about dangerous goods data, see EH&S Services [Seite 967].

Activities
You have the following options for printing or displaying delivery notes manually:
...

Printing or displaying directly using a PPF action a. On the SAP Easy Access screen, choose Extended Warehouse Management Work Scheduling Print Process and Display PPF Actions. b. Specify the document number in the Application Key field. c. Choose Execute.

d. Select the line of the required PPF action (/SCWM/PRD_OUT_PRINT or /SCWM/FD_OUT_PRINT).

SAP Extended Warehouse Management (SAP EWM)

510

143

SAP Online Help

20.07.2007

e. Choose

Process.

f. EWM prints the document.


...

Printing or displaying from the user interface of the delivery a. On the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery and then one of the following transactions: Maintain Outbound Delivery Order (/SCWM/PRDO) Maintain Outbound Delivery (/SCWM/FD)

b. Enter the required document number. c. Choose Change to switch to change mode.

d. Choose the PPF Actions tab page and select the required action (Print Outbound Delivery Order or Print Outbound Delivery). e. Proceed as follows: If you want to display the document, choose EWM displays the document. If you want to print the document, choose EWM prints the document. Execute Action. Preview.

You can only process a PPF action once from within the user interface of the delivery. PPF actions with the status Unprocessed have not been processed yet. If you have already processed the PPF action once, you can choose Repeat Action to generate and then process a new, unprocessed print action.

Example of Switching from Smart Form Print Forms to PDF-Based Print Forms
...

1. Choose the action profile Outbound Delivery and the action Print Outbound Delivery FD_OUT in Customizing for EWM under Extended Warehouse Management CrossProcess Settings Delivery Processing Actions Change Actions and Conditions Define Conditions. 2. Switch to change mode and make sure that the setting Default Settings from Action Definition is not selected in the Action Definition group box. 3. In the Processing Selection group box on the Processing Details tab page, select the assigned processing Smart Forms Print and delete it. 4. Under Available Processings, choose External Communication. 5. Save your entry.

SAP Extended Warehouse Management (SAP EWM)

510

144

SAP Online Help

20.07.2007

Text Management
Use
With this function, you can do the following to texts belonging to deliveries: Display Change Save Delete

In addition, you can create and save new texts for a particular delivery.

Integration
The ERP system sends a message (inbound delivery notification or outbound delivery request) to SAP Extended Warehouse Management (SAP EWM) to create a delivery. This message also contains the data (including existing texts) for this delivery. You can create texts in external systems (such as SAP CRM) and send them with the document via the ERP System to SAP EWM.

Prerequisites
You have made the Customizing settings for text management [Extern]. You have defined text types [Extern]. You have assigned one of the text types to the text objects (such as delivery header, delivery item) delivered by SAP. For example, assign the text type packing text to the delivery header.

For more information about defining text types, see the Implementation Guide (IMG) for EWM under Cross-Process Settings Delivery Processing Text Management Define Text Types for Delivery Document Header and Define Text Types for Delivery Document Item. You have defined a text profile [Extern] containing the following: One or more access sequences The assignment of text types to the text profile The assignment of a document or item type to the text profile

For more information about defining text profiles, see the IMG for EWM under Cross-Process Settings Delivery Processing Text Management Define Text Profiles with Access Sequences. For more information about Customizing the document or item types for the goods receipt process, see the Implementation Guide (IMG) for EWM under Goods Receipt Process Manual Settings Inbound Delivery Define Document Types for Inbound Delivery Process or Define Item Types for Inbound Delivery Process. For more information about Customizing the document or item types for the goods issue process, see the Implementation Guide (IMG) for EWM under

SAP Extended Warehouse Management (SAP EWM)

510

145

SAP Online Help

20.07.2007

Goods Issue Process Outbound Delivery Manual Settings Define Document Types for Outbound Delivery Process or Define Item Types for Outbound Delivery Process.

Features
Text management supports texts: At header level

For example, you can include sales texts that indicate that the delivery A is for the key customer Smith and that the product must therefore be delivered as quickly as possible. At item level

For example, you can create a packing text for a product that indicates to the warehouse employee that the product is fragile and that he/she must therefore always pack it in packing material 123. In SAP EWM, you can display, change, or delete texts belonging to deliveries. Only there can you also create and save new texts directly.

For more information about the connection between documents and services, such as text management, see Delivery Processing [Seite 81].

Activities
...

To process existing texts or create new ones in SAP EWM, select one of the following: For the goods receipt process, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Inbound Delivery Maintain Inbound Delivery Notification or Maintain Inbound Delivery For the goods issue process, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery Maintain Outbound Delivery Notification or Maintain Outbound Delivery For posting changes, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Posting Change Maintain Posting Change Request or Maintain Posting Change

SAP Extended Warehouse Management (SAP EWM)

510

146

SAP Online Help

20.07.2007

Delivery Quantity Adjustment


Use
In Extended Warehouse Management (EWM), you can record physical delivery quantity difference in the inbound delivery for the outbound delivery order or the posting change delivery. Delivery quantity differences can result from damage, loss, or expiration of the shelf life data, for example.

Prerequisites
If you adjust the delivery quantity manually in the user interface of the delivery, the following prerequisites apply: A delivery exists in EWM, which has a status value at item level for status Completion that allows delivery quantity adjustment. That is, it has either status value Not Started or Partially Completed. If you want to use your own process codes, you have defined them in Customizing EWM. For more information, see the IMG for EWM under CrossProcess Settings Delivery Processing Process Codes Define Process Codes. If required, you have assigned the process codes to your own process code profiles in Customizing for EWM. For more information, see the IMG for EWM under Cross-Process Settings Delivery Processing Process Codes Maintain Process Code Profiles. If required, you have assigned the process code profiles to the used document types and items types in Customizing for EWM. For more information, see the IMG for EWM at the following locations: Goods Receipt Process Inbound Delivery Manual Settings Define Document Types for Inbound Delivery Process or Define Item Types for Inbound Delivery Process Goods Issue Process Outbound Delivery Manual Settings Define Document Types for Outbound Delivery Process or Define Item Types for Outbound Delivery Process Internal Warehouse Processes Delivery Processing Posting Changes Define Document Types for the Posting Change Process or Define Item Types for the Posting Change Process

For the availability check, you have not defined any of the following restrictions for the quantity increase in Customizing for EWM. For more information, see the IMG for EWM under Interfaces Availability Check Define Configuration of Availability Check. Under Allowed Quantity Increase, you have not defined A Quantity Increase Not Allowed, meaning that the quantity increase is generally not allowed for the party entitled to dispose, item type, product group type, and product group. Under Allowed Quantity Increase, you have not defined B Special Authorization Required to Increase Quantity, meaning that the user who wants to execute the quantity increase requires authorization for activity 94 (Override) for authorization object /SCWM/DLV.

SAP Extended Warehouse Management (SAP EWM)

510

147

SAP Online Help

20.07.2007 If you still choose this setting, you must assign authorization for activity 94 to the corresponding user for authorization object /SCWM/DLV.

If you adjust the delivery quantity using an exception code for an automatic delivery update, you must also have defined exception codes in Customizing for EWM and assigned them to the process codes. For more information, refer to the IMG for EWM under Cross-Process Settings Exception Handling Define Exception Codes. For both types of delivery quantity adjustment, you have also assigned partner roles to the process codes in Customizing for EWM under Cross-Process Settings Delivery Processing Process Codes Define Process Codes. If you record quantity differences for stock transfer orders [Seite 150] for example, the partner you define here corresponds to the person who caused the delivery quantity difference. EWM saves delivery quantity differences for this partner and sends the information to the ERP system. The only information EWM does not send to ERP is information about delivery quantity differences for posting change deliveries,since these involve internal warehouse differences. For both types of delivery quantity adjustment, you have also defined in Customizing for EWM the partners for which EWM reports exceptions, namely process codes, to ERP. For more information, see the IMG for EWM under Interfaces ERP Integration Delivery Processing Map Partner Roles from ERP System to EWM.

Features
EWM considers the following quantities for delivery quantity adjustment: In the inbound delivery, EWM considers the quantities for goods receipt, packing, and planned putaway, meaning EWM matches the delivery quantity to the largest of these quantities. In the outbound delivery order, EWM considers the quantities for loading, packing, and planned picking, meaning EWM matches the delivery quantity to the largest of these quantities. In the posting change delivery, EWM considers the quantity for planned internal movements, meaning EWM matches the delivery quantity to this quantity.

In Customizing for the process code, you can define one of the following types for the delivery quantity adjustment: EWM does not adjust the delivery quantity, although EWM saves a process code in the delivery that you can also view in the respective user interface of the delivery. EWM adjusts the delivery quantity and saves a process code in the delivery. EWM adjusts both the delivery quantity and the transferred delivery quantity, meaning EWM performs a delivery split in the goods receipt process or goods issue process. EWM also saves a process code in the delivery.

For more information, see Delivery Split for Inbound Deliveries [Seite 154] and Delivery Split for Outbound Deliveries [Seite 156].

Activities
You can adjust delivery quantities in one of the following ways: On the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing and then the corresponding user interface: Inbound Delivery Maintain Inbound Delivery Outbound Delivery Maintain Outbound Delivery Order

SAP Extended Warehouse Management (SAP EWM)

510

148

SAP Online Help Posting Change Maintain Posting Change.

20.07.2007

You adjust the delivery quantity manually in the user interface of the delivery. If you are confirming a warehouse task or recording counting, on the SAP Easy Access screen choose Extended Warehouse Management Execution Confirm Warehouse Task or Execution Quality Inspection and Count, to specify an exception code. EWM assigns this exception code to a process code, corresponding to the settings you have made in Customizing. EWM then uses the delivery update to adjust the delivery quantity for each item, corresponding to the settings of the process code. If you are repacking delivery stock, on the SAP Easy Access screen choose Extended Warehouse Management Execution Packing - General. If you have defined the work center correspondingly in Customizing for EWM, then EWM displays the tab page Differences. For this, you have defined the work center layout in the IMG for EWM under Master Data Work Center Specify Work Center Layout. You record the difference and specify an exception code. EWM maps this exception code to the relevant process code in the background and updates the delivery.

Example
Delivery Split in the Goods Receipt Process
EWM generates an inbound delivery notification for 100 pieces. The document flow also carries a quantity of 100 pieces. EWM generates an inbound delivery with an inbound delivery quantity of 100 pieces. In the user interface of the inbound delivery, you specify that EWM is to adjust the inbound delivery quantity to 90 pieces, since 10 pieces are defective. In Customizing for the process code, you have defined an adjustment for both the delivery quantity and the transferred delivery quantity. EWM adjusts the inbound delivery quantity to 90 pieces. This triggers a quantity adjustment for the transferred delivery quantity in the document flow to 90 pieces, and a delivery split in the goods receipt process, meaning that EWM generates another inbound delivery using the difference quantity of 10 pieces.

SAP Extended Warehouse Management (SAP EWM)

510

149

SAP Online Help

20.07.2007

Quantity Differences for Stock Transfer Orders


Purpose
In Extended Warehouse Management (EWM), you can confirm stock transfer orders with a quantity difference. This enables you to map the following processes: You receive a quantity shortage or quantity excess in the inbound delivery, which was caused by a delivering warehouse; for example, the delivering warehouse has not loaded a pallet onto the vehicle. You receive a quantity shortage or quantity excess in the inbound delivery, which was caused by a carrier; for example, a carrier damaged the goods. In cross-docking [Seite 544], you can confirm quantity excesses or shortages that were caused by the first cross -docking warehouse and not the delivering warehouse.

If a source warehouse caused a quantity excess or shortage, the ERP system sends a correction delivery to EWM in the source warehouse. There, if required, you can execute clearing in the Difference Analyzer [Seite 677] between the receivable quantities and the difference quantities to be cleared. If you are unable to execute clearing, you post the difference to the ERP system.

You deliver 10 pieces of product A. The customer only receives 9 pieces. You post a correction delivery for one piece as a receivable quantity to be cleared. In the physical inventory, you find that one piece of product A is still in the goods issue area. In the Difference Analyzer, you can offset the receivable quantity to be cleared with a difference quantity to be cleared. If a carrier caused a quantity excess or shortage, you perform an adjustment posting directly in the ERP system. The ERP system uses the process code from the last partial goods receipt message of the target warehouse to determine who caused the quantity excess or shortage. For more information, see the SAP Help Portal for SAP ERP under SAP ERP Central Component Logistics Logistics - General (LO) Service Parts Management (LO-SPM) Transfer and Inventory Management Stock Transfers Adjustment of Stock Transport Order Quantity Difference. If quantity differences occur in connection with kits, you always post these differences at the kit header. If the kit itself is not available in the source warehouse, rather the kit components only, you have to clear this difference by posting differences in the inventory quantity.

Prerequisites
You are working in a system landscape that includes an ERP system, central SAP Advanced Planning & Optimization (SAP APO) for the automatic generation of stock transfer orders, and at least one decentralized EWM. You are using interfaces between EWM and the ERP system. For more information, see Communication from EWM to ERP System [Seite 248]. You have defined tolerance groups for the Difference Analyzer in the Customizing settings for EWM. For more information, see the Implementation Guide (IMG) for EWM under Internal Warehouse Processes Physical Inventory Warehouse-Number-Specific Settings Define Tolerance Groups Define Tolerance Group for Difference Analyzer. You have assigned the user to a tolerance group for the Difference Analyzer in the Customizing settings for EWM. To do so, on the SAP Easy Access screen, choose

SAP Extended Warehouse Management (SAP EWM)

510

150

SAP Online Help

20.07.2007

Extended Warehouse Management Settings Physical Inventory Assign User to Tolerance Group for Difference Analyzer.

EWM in the Source Warehouse


You have defined document types for the correction deliveries in Customizing for EWM. EWM finds these using the differentiation attribute DIS (discrepancy process) at header level. For more information, see the Implementation Guide (IMG) for EWM under Interfaces ERP Integration Delivery Processing Define ERP Document Types for Differentiation Attribute.

Make sure that the Customizing settings for EWM for your own document types and for the item types used are correct. If you are defining your own profiles, use the delivered document types and item types and their relevant profiles as a basis. You have defined the mapping of the document types from the ERP system in EWM in Customizing for EWM. For more information, see the IMG for EWM under Interfaces ERP Integration Delivery Processing Map Document Types from ERP System to EWM System.

EWM in the Target Warehouse


In Customizing for EWM, you have defined whether EWM is to execute an automatic or manual goods movement. For more information, see the IMG for EWM, under Cross-Process Settings Delivery Processing Actions Use Assistant to Create Actions. In Customizing for EWM, you have defined process codes and assigned these to your own process code profiles. You have also assigned partner roles to the process codes (see Delivery Quantity Adjustment [Seite 147]). You have defined the mapping of the exception code to the process code of the delivery processing in Customizing for EWM. For more information, refer to the IMG for EWM under Cross-Process Settings Exception Handling Define Exception Codes.

Process
Quantity Differences for Stock Transfer Orders
You work with a central SAP APO and ERP system and two decentralized warehouses managed by EWM. You transport goods from one warehouse to another. In the following, the two EWM systems are referred to as EWM1 for the source warehouse and EWM2 for the target warehouse.
...

1. You create a stock transfer order in SAP APO and SAP APO informs the ERP system about it. 2. The ERP system generates a corresponding stock transfer order and an outbound delivery for this. It informs EWM1 of the source warehouse about this. 3. EWM1 generates a relevant outbound delivery. 4. You perform the required goods issue process steps and post the goods issue. 5. EWM1 informs the ERP system about this. 6. The ERP system generates a corresponding inbound delivery for EWM2 of the target warehouse. It informs EWM2 about this. SAP Extended Warehouse Management (SAP EWM) 510 151

SAP Online Help 7. EWM2 generates a corresponding inbound delivery. 8. You or a carrier transport the products to EWM2.

20.07.2007

9. You execute the goods receipt process steps up to goods receipt posting. When posting goods receipt, you identify a quantity excess or shortage. 10. You post goods receipt with the quantity excess or shortage and specify a process code. EWM2 uses the process code to differentiate who caused the quantity excess or shortage (see Delivery Quantity Adjustment [Seite 147]). 11. EWM2 informs the ERP system about this. 12. The ERP system posts the quantity differences in the proof of delivery. 13. The ERP system generates a correction delivery for EWM1 of the source warehouse. For a quantity shortage, the ERP system generates an inbound delivery for EWM1, and for a quantity excess, an outbound delivery for EWM1. The ERP system informs EWM1 about this. 14. EWM1 generates an inbound or outbound delivery as a correction delivery, based on the notification. It posts the quantity excess or shortage as a receivable quantity to be cleared (external quantity difference). You can reject goods receipt of the inbound delivery or goods issue of the outbound delivery in EWM1. The unassigned stock remains in the ERP system. You have to then process it manually, if necessary. EWM1 posts internal quantity differences from the physical inventory or warehouse task creation as difference quantities to be cleared. For example, if you find a pallet in the physical inventory that has 10 pieces of a product, you post this as a difference quantity to be cleared. 15. In EWM1, you attempt to offset the receivable quantities to be cleared with the difference quantities to be cleared in the Difference Analyzer.

Quantity Differences in Cross-Docking


Unlike the standard process for stock transfer orders, in the cross-docking process (CD process) you work with at least three decentralized warehouses: the source warehouse, the cross-docking warehouse (CD warehouse) and the target warehouse. These warehouses are managed by EWM. You transport goods from the source warehouse to the target warehouse via the CD warehouse. In the cross-docking process, you record quantity differences in the same way as for stock transfer orders. When you record quantity differences, you can use the process code to decide whether these quantity differences are to be debited from or added to the previous warehouse (if exists) or the source warehouse. The following graphic illustrates these two options. For example, if you want to record a quantity shortage in CD warehouse 2, you can use process code PC2A to debit this quantity difference from CD warehouse 1, or process code PC2B to debit the source warehouse.

SAP Extended Warehouse Management (SAP EWM)

510

152

SAP Online Help

20.07.2007

For more information about the cross-docking process, see Cross-Docking [Seite 544].
...

Result
You have posted a quantity difference for a stock transfer order or in the cross-docking process.

SAP Extended Warehouse Management (SAP EWM)

510

153

SAP Online Help

20.07.2007

Delivery Split for Inbound Deliveries


Use
A delivery split can be necessary in various business processes, for example, if a planned inbound delivery arrives in two trucks instead of one. You can either totally delete a delivery item in the inbound delivery or you can split it by using Adjust Delivery Quantity and choosing a process code.

Prerequisites
You have defined process codes that adjust both the delivery quantity and the transferred delivery quantity [Extern], that is, you have chosen the value 2 Adjustment of Delivery Quantity and Del. Quant. Transferred for the quantity adjustment. For more information, see the Implementation Guide (IMG) under Extended Warehouse Management Cross-Process Settings Delivery Processing Process Codes Define Process Codes. You defined process code profiles. If Extended Warehouse Management (EWM) is to use a default process code (for example, /002) for quantity changes, you have chosen a default process code in the Customizing settings. For more information, see the IMG under Extended Warehouse Management Cross-Process Settings Delivery Processing Process Codes Maintain Process Code Profiles. You have defined the item types for the inbound deliveries in which you assigned the corresponding process code profiles. For more information, see the IMG under Extended Warehouse Management Goods Receipt Process Inbound Delivery Manual Settings Define Item Types for Inbound Delivery Process. Either you or the system can split delivery items or partial quantities into a new delivery. The prerequisite for this is that you have not performed a warehouse activity for this delivery item or partial quantity. For example, you have not posted the goods receipt (GR) yet.

Features
You can totally delete a delivery item or reduce the delivery quantity of a delivery item. EWM determines a process code according to your Customizing settings for delivery quantity changes. For example, while you are unloading a truck, you discover that delivery item 20 is missing. However, you know that this delivery item will arrive on another truck the next day. Therefore, you only want to post delivery item 20 the next day, which means that you require a delivery split.

You can book GR for partial quantities, meaning that you have only not yet carried out warehouse activities for the remaining quantity for which you are performing a delivery split. If you choose the delivery item and manually change the delivery quantity in the user interface of the inbound delivery then, if necessary, EWM determines a default process code (for example, I002 Diff). Adjust Supplier, Document and Quantity. To access the user interface, on the SAP Easy Access Screen choose Extended Warehouse Management Delivery Processing Inbound Delivery Maintain Inbound Delivery. If necessary, the default process code has the effect that EWM automatically adjusts the delivery quantities. If you want to work without a default process code, choose Adjust Delivery Quantity for the selected delivery item and specify a process code. When you select the corresponding process code, EWM adjusts the delivery quantity and the transferred delivery quantity. EWM performs a delivery split automatically and creates a new inbound delivery that contains delivery items for the partial quantities that are still missing or for the totally deleted delivery item.

SAP Extended Warehouse Management (SAP EWM)

510

154

SAP Online Help

20.07.2007

If you perform changes in an inbound delivery using a process code that automatically adjusts to the delivery quantity, you cannot undo these changes. When EWM adjusts the delivery quantities, it takes the following quantities of the inbound delivery into account: the quantities of the open warehouse tasks the packed quantity the GR posted quantity the unloaded quantity

This allows EWM to prevent document inconsistencies. If, for example, a delivery item still has open warehouse tasks, you cannot set the quantity of this delivery item to zero. You can process the newly created inbound delivery as in the normal GR process [Seite 263]. You can then post the GR, for example. You can check the automatic adjustment of the delivery quantity for a delivery item in the user interface of the inbound delivery in the Quantity field on the Document Flow tab page. See Also: Delivery Quantity Adjustment [Seite 147]

Example
Example for a Manual Delivery Split
...

1. A delivery item with ten pieces is assigned to a warehouse task with seven pieces. 2. EWM adjusts the delivery quantity and the transferred delivery quantity in accordance with your Customizing settings. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Inbound Delivery Maintain Inbound Delivery Notification and then the Delivery Quantity pushbutton. You specify the process code I002 Diff. Adjust Supplier, Document and Quantity. EWM adjusts the delivery quantity and performs a delivery split. a. Since you have not performed any warehouse activities for the remaining quantity of the delivery item, EWM automatically adjusts the delivery quantity to seven pieces. b. You save the delivery quantity change. c. During the save, EWM creates a new inbound delivery for the remaining quantity of three that contains three pieces for every ten delivery items. In the original inbound delivery, you can check the changed quantity for the original delivery item at item level in the Quantity field on the Document Flow tab page. EWM displays the quantity of seven pieces. Additionally, on the Process Codes tab page, you can see (at item level) that EWM uses the process code I002 for the difference quantity of three pieces.

SAP Extended Warehouse Management (SAP EWM)

510

155

SAP Online Help

20.07.2007

Delivery Split for Outbound Deliveries


Use
You can perform a delivery split in various business processes. For example, you have completely picked an outbound delivery order in Extended Warehouse Management (EWM). You find that you cannot load the complete quantity. You can create an outbound delivery for individual delivery items and therefore perform an outbound delivery split. Either you or the system can split an outbound delivery order or an outbound delivery.

Prerequisites
Prerequisites for the Outbound Delivery Order Split Based on the Outbound Delivery Request
You have performed the Customizing for route determination (see Special Features for Outbound Delivery Objects [Seite 210]). If EWM finds various routes for different delivery items, it performs an outbound delivery order split. You can program a separate logic for route determination in the Business Add-In (BAdI) BAdI: Route Determination and Route Check that causes EWM to perform an outbound delivery order split. For more information, see the Implementation Guide (IMG) for EWM under Business Add-Ins (BAdIs) for Extended Warehouse Management Cross-Process Settings Delivery Processing Determinations in Delivery BAdI: Route Determination and Route Check.

Prerequisites for the Outbound Delivery Order Split


You have defined process codes that adjust both the delivery quantity and the transferred delivery quantity, that is, you have chosen the value 2 Adjustment of Delivery Quantity and Del. Quant. Transferred for the quantity adjustment. For more information, see the IMG for EWM under Cross-Process Settings Delivery Processing Process Codes Define Process Codes. You defined process code profiles. If EWM is to use a default process code (for example, O002) for quantity changes, you have chosen a default process code in the Customizing settings. For more information, see the IMG for EWM under CrossProcess Settings Delivery Processing Process Codes Maintain Process Code Profiles. You have defined the item types for the outbound deliveries in which you assigned the corresponding process code profiles. For more information, see IMG for EWM under Goods Issue Process Outbound Delivery Manual Settings Define Item Types for Outbound Delivery Process. Either you or the system can split delivery items or partial quantities into a new delivery. The prerequisite for this is that you have not performed a warehouse activity for this delivery item or partial quantity. For example, you have not created a warehouse task for picking yet.

Prerequisites for the Outbound Delivery Split


If the delivery item of the outbound delivery is relevant for picking, you have at least picked the delivery quantity that you want to split into a new subitem. You can only create new subitems for this picked quantity. If you have already started loading, that is, the status type Loading for the delivery item has the status value Partially Completed, the delivery quantity that you have split must

SAP Extended Warehouse Management (SAP EWM)

510

156

SAP Online Help

20.07.2007

also be loaded. This means that the status Loading for the subitem has the status value Completed.

Features
Outbound Delivery Order Split Based on Outbound Delivery Request
EWM performs an outbound delivery order split on the basis of route determination. For example, an outbound delivery request consists of delivery items 10, 20, and 30. Delivery items 10 and 20 have route R1 and delivery item 30 has route R2. EWM creates an outbound delivery order for delivery items 10 and 20 and a second outbound delivery order for delivery item 30. For more information, see Route Determination in the Delivery [Seite 202] and Special Features for Outbound Delivery Objects [Seite 210].

Outbound Delivery Order Split


The same functions exist for the outbound delivery order split as for the Delivery Split for Inbound Deliveries [Seite 154]. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery Maintain Outbound Delivery Order. However, when EWM adjusts the delivery quantities, it takes different quantities into account than for the delivery split for inbound deliveries. EWM takes the following quantities of the outbound delivery order into account: The quantities of the open warehouse tasks The packed quantity The loaded quantity The aggregated quantity The picked quantity The number of serial numbers The catch weight quantity assignment

Outbound Delivery Split


If you want to perform an outbound delivery split, you split an outbound delivery order item. EWM creates corresponding subitems. You create outbound deliveries for the individual subitems. You can split delivery items for both packed and unpacked products. EWM displays the subitems that have been created on the Items or HU tab page using + symbols in the Level column. You can also delete an outbound delivery split. To do so, you must first delete the corresponding outbound delivery and then the subitem. You delete the whole subitem when deleting unpacked products. For packed products, you can delete the parts of a subitem that are packed in an HU. When you save a newly created subitem, EWM posts the stock of the delivery item to the subitem, meaning that the stock is item based. You can post goods issue for every subitem. The document flow always displays the quantity of delivery items that have not been split and does not display the corresponding subitems.

Activities
For a description of the activities for the outbound delivery order split, see Route Determination in the Delivery [Seite 202] and Special Features for Outbound Delivery Objects

SAP Extended Warehouse Management (SAP EWM)

510

157

SAP Online Help

20.07.2007

[Seite 210]. For a description of the activities for the outbound delivery order split, see Delivery Split for Inbound Deliveries [Seite 154].

Activities for the Outbound Delivery Split


On the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery Maintain Outbound Delivery Order.
...

If you want to split a delivery item for unpacked products, perform the following steps: a. Go to the Items tab page and select a delivery item. b. Choose the arrow on the right-hand side of Subitem and then choose Split Up Outbound Delivery. c. Specify the number of subitems that are to be created. EWM creates one or more new subitems for which you can specify the desired delivery quantity. d. Choose with the quick info Save.

EWM saves the new subitem, thus splitting the delivery item. e. Choose with the quick info Create Outbound Delivery.

EWM creates an outbound delivery for the subitem.


...

If you want to split a delivery item for packed products, perform the following steps: a. Go to the HU tab page and select an HU item. b. Choose the arrow Create. on the right-hand side of Split Item and then choose

EWM creates a new subitem for the HU, for which you can specify the desired delivery quantity. c. Choose with the quick info Save.

EWM saves the new subitem, thus splitting the delivery item. d. Choose with the quick info Create Outbound Delivery.

EWM creates an outbound delivery for the subitem.


...

If you want to undo a delivery item split, perform the following steps: a. Go to the Items tab page. b. Delete the corresponding outbound delivery first by selecting the outbound with quick info Delete. delivery and choosing If you want to delete the subitem of an unpacked product, select the subitem and choose with the quick info Delete. EWM totally deletes the subitem. If you want to delete the subitem of a packed product, undo the HU split. Go to the HU tab page and select the subitem. Choose the arrow on the right-hand side of Split Item and then choose Undo. EWM totally deletes the subitem.

SAP Extended Warehouse Management (SAP EWM)

510

158

SAP Online Help

20.07.2007

Validation
Use
Extended Warehouse Management (EWM) works with a validation framework and uses various validation methods, for example, for an incompleteness check or a tolerance check. If a document changes, EWM performs a validation.

Features
For more information, see Validation [Seite 101].

Activities
You can call validation directly from the user interface. To do so, on the SAP Easy Access screen, choose the corresponding user interface, for example, Extended Warehouse Management Delivery Processing Inbound Delivery Maintain Inbound Delivery. Check. Select an inbound delivery and choose the function

SAP Extended Warehouse Management (SAP EWM)

510

159

SAP Online Help

20.07.2007

Process Management and Control


Use
Process management and control manages business transactions using process indicators in a delivery document. A process indicator can allow or prohibit a business transaction or it may have no influence at all.

Integration
The process control described here is used in delivery processing exclusively. Process control can influence field control.

Features
A process indicator has multiple values, for example process indicator Scrapping has the value Not Allowed and Required. A process indicator describes the entire business transaction represented by the delivery document. For the document header and document item, SAP delivers a set of process indicators in the system profile and customer profile of process control. The process indicators are linked to the document and item types of delivery processing via a process profile. You can change the settings for the process indicators in the process profile. When Extended Warehouse Management (EWM) creates a delivery document, the system sets the process indicator. You can then no longer make changes to these. However, if you have set the value Allowed for process indicator IBGI (invoice creation before goods issue) in Customizing for EWM, under Cross-Process Settings Delivery Processing Process Management and Control Define Process Profile for Delivery Document, you can change the value of this process indicator in a direct outbound delivery order. However, you can only do this as long as the outbound delivery has not yet been created. You can choose from the following process indicators: Process Indicator Manual creation Meaning Use Certain deliveries, such as direct outbound delivery orders and posting changes, can be created and processed in EWM directly. They do not require a preceding document in ERP. Allows a reference to a preceding document (purchase order, sales order, or production order) Inbound and outbound deliveries usually have a reference to a preceding document, inbound deliveries for purchase orders, and outbound deliveries for sales orders. Posting changes or outbound deliveries without reference, on the other hand, do not refer to a preceding document. If inbound and outbound deliveries are used in a production process, you have a reference to a production 510 160

Preceding document

Production

Allows processes for production, such as kit to stock, goods receipt for

SAP Extended Warehouse Management (SAP EWM)

SAP Online Help production Scrapping Allows subprocesses for scrapping order.

20.07.2007

In the scrapping process, you perform a planned reduction of overstock in two steps: you first post change the stock to locked stock, and then post the locked stock. In this process, you only make goods available for the sales location within the warehouse. You do not perform any transportation activities. You can create the invoice in the early stages of the process flow within the packing or loading goods process step. If you identify warehouseexternal differences, e.g. in a stock transfer process or for a customer delivery, which require warehouse stock to be corrected, you can post these to the stock of the differences to be cleared using a correction delivery.

Pickup

Allows a process for direct sales

Invoice Creation Before Goods Issue

Allows invoice creation before goods issue

Correction delivery

Allows posting differences to the stock of the differences that are to be cleared

Activities
In Customizing for EWM you define the process indicators for the delivery document header and for the delivery document item. For more information, see the Implementation Guide (IMG) for EWM under Cross-Process Settings Delivery Processing Process Management and Control Define Process Profile for Delivery Document Header or Define Process Profile for Delivery Document Item.

SAP Extended Warehouse Management (SAP EWM)

510

161

SAP Online Help

20.07.2007

Processing of Non-Picking-Relevant Delivery Items


Purpose
You can use the processing of non-picking-relevant delivery items to remove goods from your warehouse for a warehouse request for an outbound delivery order [Seite 112]. However, in contrast to picking, Extended Warehouse Management (EWM) does not generate any warehouse tasks for the warehouse request or any warehouse orders.

Prerequisites
The goods movement bin in the warehouse request from which you are booking out the stock for the goods issue must contain a valid storage bin in which a sufficient quantity of the product is available. You use an item type that does not contain any of the following status types in the status profile: Planned Picking Picking

For more information, see the Implementation Guide (IMG) for EWM under CrossProcess Settings Delivery Processing Status Management Define Status Profiles.

Process
...

1. You or EWM create the warehouse request for an outbound delivery order. Either ERP distributes an outbound delivery to EWM and EWM automatically generates a corresponding warehouse request, or you manually generate the warehouse request in EWM as a direct outbound delivery order [Seite 167]. You specify all the relevant stock attributes of the product (for example, the stock type) and a goods movement bin in the warehouse request. If you have configured goods movement bin determination, EWM automatically suggests a goods movement bin. On the SAP Easy Access screen, choose Extended Warehouse Management Settings Maintain Goods Movement Bin Determination. EWM also uses the settings that you specify here to process inbound deliveries that are not relevant to putaway. If you generate the warehouse request manually, choose one of the following options: You specify the items with their stock attributes and quantities on the Items tab page. On the HU tab page, you choose the Create and Save pushbuttons and specify a handling unit (HU) and an item type. Then EWM automatically creates the corresponding items with their stock attributes and quantities.

2. You remove the products from your warehouse and perform any other relevant goods issue steps, for example, loading for transportation. 3. You post the goods issue for the outbound delivery order.

SAP Extended Warehouse Management (SAP EWM)

510

162

SAP Online Help

20.07.2007

Result
EWM has generated a warehouse request for an outbound delivery order. You have removed the products from your warehouse, posted the goods issue (for example in sell from stock) or performed additional goods issue activities, and have then posted goods issue.

SAP Extended Warehouse Management (SAP EWM)

510

163

SAP Online Help

20.07.2007

Processing of Non-Putaway-Relevant Delivery Items


Purpose
You can use the processing of non-putaway-relevant delivery items to book goods for a warehouse request for an inbound delivery into your warehouse stock. However, in contrast to putaway [Seite 300], Extended Warehouse Management (EWM) does not generate any warehouse tasks for the warehouse request or any warehouse orders.

Prerequisites
The goods movement bin in the warehouse request into which you are booking the stock for the goods receipt must contain a valid storage bin into which you can book the product. You use an item type that does not contain any of the following status types in the status profile: Planning Putaway Putaway

For more information, see the Implementation Guide (IMG) for EWM under CrossProcess Settings Delivery Processing Status Management Define Status Profiles.

Process
...

1. You or EWM create the warehouse request for an inbound delivery [Seite 112]. Either ERP distributes an inbound delivery to EWM and EWM automatically generates a corresponding warehouse request, oryou manually generate the warehouse request in EWM. You specify all the relevant stock attributes of the product (for example, the stock type) and a goods movement bin in the warehouse request. If you have configured goods movement bin determination, EWM automatically suggests a goods movement bin. On the SAP Easy Access screen, choose Extended Warehouse Management Settings Maintain Goods Movement Bin Determination. EWM also uses the settings that you specify here to process outbound deliveries that are not relevant to picking. 2. You perform any other relevant goods receipt steps, for example, unloading. 3. You put away the products in your warehouse and you post goods receipt for the inbound delivery.

Result
EWM has generated a warehouse request for an inbound delivery. You have performed any additional goods receipt activities, you have put away the products in your warehouse, and you have posted goods receipt.

SAP Extended Warehouse Management (SAP EWM)

510

164

SAP Online Help

20.07.2007

Processing of Packaging Items


Purpose
You can process packaging items to put away stock-relevant packaging materials [Seite 492] or to remove them from stock. When putting away the packaging material, you use a warehouse request for an inbound delivery. When removing the packaging material from stock, you use a warehouse request for an outbound delivery order (see also Warehouse Request for Inbound Delivery or Outbound Delivery Order [Seite 112]). If the delivery items are relevant to picking or to putaway, Extended Warehouse Management (EWM) creates warehouse tasks for the warehouse request and the corresponding warehouse orders. If not, EWM creates neither warehouse tasks for the warehouse request nor warehouse orders. If packaging items already exist in an inbound or outbound delivery in ERP, ERP distributes them to EWM and EWM adds the packaging items to the inbound or outbound delivery.

Prerequisites
The product of the packaging item is a packaging material. Check the settings for the packaging data in the global view of the product master. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Master Data Product Maintain Product and then choose the Global Data setting in the View group box. Choose the Pkg Data tab page and display the relevant data. In the goods issue process, the goods movement bin in the warehouse request from which you are booking out the stock for the goods issue must contain a valid storage bin in which a sufficient quantity of the product is available.

Process
...

1. You or EWM create the warehouse request for an inbound delivery or an outbound delivery order. Either ERP distributes an inbound or outbound delivery to EWM and EWM automatically generates a corresponding warehouse request, or you manually generate the warehouse request in EWM. You can manually generate packaging items for both the inbound delivery and the outbound delivery. EWM processes these to a large extent in the same way as normal items. Exceptions include the batch split, which is not possible in this case. When you manually generate the packaging items, you specify all the relevant stock attributes of the packaging material, for example, the stock type, in the warehouse request. If the delivery item is not relevant to picking, you specify a goods movement bin. If you have configured goods movement bin determination in Customizing for EWM, EWM automatically suggests a goods movement bin. On the SAP Easy Access screen, choose Extended Warehouse Management Settings Maintain Goods Movement Bin Determination. EWM uses the settings that you specify here to process delivery items that are not relevant to putaway and delivery items that are not relevant to picking. 2. If the delivery items are relevant to picking or to putaway, you generate the warehouse tasks for the warehouse request and confirm them. 3. You perform any other relevant goods receipt or goods issue steps. For example, you pick products and use the packaging material as pick-handling units. 4. You post goods receipt for the inbound delivery or goods issue for the outbound delivery order.

SAP Extended Warehouse Management (SAP EWM)

510

165

SAP Online Help

20.07.2007

Result
EWM has generated the warehouse request for an inbound delivery or an outbound delivery order. You have either put away the packaging material in your warehouse and posted goods receipt, or you have removed it from your warehouse and posted goods issue.

SAP Extended Warehouse Management (SAP EWM)

510

166

SAP Online Help

20.07.2007

Direct Outbound Delivery Order


Definition
Document that is triggered in the warehouse directly. Extended Warehouse Management (EWM) sends the direct outbound delivery order to ERP. The direct outbound delivery order contains the ERP document number. The structure and data of the direct outbound delivery order match those of an outbound delivery order that is triggered in ERP.

Use
Unlike EWM outbound delivery orders, for which ERP generated a reference document previously, you or EWM can also generate direct outbound delivery orders directly and locally in EWM, which EWM then sends to ERP. You can use direct outbound delivery orders in the following scenarios: Pickup [Extern] Direct sales For direct sales, transportation activities do not apply, since the customer asks for the goods and picks them up on-site in the warehouse. You do not need to create a sales order for this. The direct outbound delivery order you generated manually in EWM forms the basis for the delivery in ERP. The delivery in ERP forms the outbound document for billing. You can also trigger direct sales in ERP without generating a sales order. Account assignment For account assignment, transportation activities also do not apply, since the internal or external customer asks for the goods and picks them up on-site in the warehouse. Unlike for direct sales, you post a goods issue with account assignment for the goods, for the cost center, for example. You can also trigger goods issue with account assignment in ERP without generating a sales order. Scrapping [Seite 366] The Direct Outbound Delivery Order for Scrapping [Seite 175] forms the last step in the scrapping process. You post the goods to be scrapped with the goods issue from the warehouse stock. Whereas you can also trigger the preparation for scrapping such as collecting goods in a scrapping container using a posting change request from ERP, you always trigger this last step locally in the warehouse. Immediate Delivery (Push or Pull Procedure) [Seite 172] Kit to stock or reverse kitting For kit to stock, you use a value-added service order [Extern] to create a kit from different components. If you want to reserve the corresponding components, you can use a direct outbound delivery order. When you have created the kit and post goods issue for the direct outbound delivery order, EWM reduces the stock of the respective components. You can use the direct outbound delivery order to execute actions that you require for generating and processing an outbound delivery in the warehouse, such as picking. You can carry out the following for a direct outbound delivery order: Save

SAP Extended Warehouse Management (SAP EWM)

510

167

SAP Online Help

20.07.2007

Validate Archive Delete

Structure
For the structural description of the direct outbound delivery order, see Outbound Delivery Order [Seite 91]. The structure of a direct outbound delivery order also contains the following, differentiating it from the structure of an outbound delivery order: Document categories with different document types You can define the document types in Customizing for delivery processing.

For more information about defining document types in EWM, see the Implementation Guide (IMG) for EWM under Goods Issue Process Outbound Delivery: Define Document Types for Outbound Delivery Process Using Wizard Manual Settings Define Document Types for Outbound Delivery Process

An item category with different item types You can define the item types in Customizing for delivery processing.

For more information about defining item types in EWM, see the Implementation Guide (IMG) for EWM under Goods Issue Process Outbound Delivery: Define Item Types for Outbound Delivery Process Using Wizard Manual Settings Define Item Types for Outbound Delivery Process

Direct outbound delivery orders have the following properties that differentiate them from outbound delivery orders that were generated in EWM based on outbound deliveries created in ERP: Necessity of the availability check, as this check is usually triggered in ERP To avoid endangering the continual ability to deliver, the planning situation must be adjusted with the availability check.

In SAP SCM 5.1, planning-related reservation of the products only takes place if you are using SAP Advanced Planning and Optimization (SAP APO). No reservation takes place for checks in ERP. In exceptional cases, overconfirmation may occur. A lot of organizational and logistically relevant delivery data that is copied to outbound delivery orders from ERP preceding documents must be specified for the direct outbound delivery orders locally in EWM. Either you enter the data directly, such as the product or quantity, or EWM determines the data automatically using configuration data, such as the goods issue bin for items that are not pick-relevant. As you start the goods issue process using direct outbound delivery orders in EWM, the underlying document type must display the process correspondingly. EWM uses the process profile to do this. When generating a direct outbound delivery order, you must select the correct document type to ensure the process flow is correct. For more SAP Extended Warehouse Management (SAP EWM) 510 168

SAP Online Help

20.07.2007

information, see the IMG for EWM under Cross-Process Settings Delivery Processing Process Management and Control. As no outbound delivery request from ERP exists for direct outbound delivery orders, actions such as splitting direct outbound delivery orders are not possible (see Delivery Split for Outbound Deliveries [Seite 156]). Direct outbound delivery orders are also always checked, meaning they have the status type Locked (Unchecked Item) and statusvalue No, and are immediately ready for processing. Direct outbound delivery orders support processing of non-pick-relevant items, for example, or generation of items from handling units.

Integration
As direct outbound delivery orders are created in EWM directly, no availability check is performed in ERP for the required product. Instead, EWM triggers the availability check. Depending on the configuration, the check can be performed in ERP or in SAP APO. For outbound delivery orders replicated from ERP, however, the availability check is triggered in ERP. For more information, see Availability Check [Seite 176]. EWM can send direct outbound delivery orders for scrapping to ERP. Prerequisite for this is that you are using the corresponding Enhancement Package of ERP. For more information, see the Implementation Guide (IMG) for EWM under Interfaces ERP Integration General Settings Set Control Parameters for ERP Version Control. If you are not using a corresponding Enhancement Package, only the goods movement posting takes place. There is no delivery replication. When you generate a direct outbound delivery order, EWM automatically performs a Compliance Check [Seite 222].

See also: Processing of Direct Outbound Delivery Orders [Seite 170]

SAP Extended Warehouse Management (SAP EWM)

510

169

SAP Online Help

20.07.2007

Processing of Direct Outbound Delivery Orders


Use
If you want to use direct outbound delivery orders in any of the scenarios listed under Direct Outbound Delivery Order [Seite 167], on the SAP Easy Access screen choose Extended Warehouse Management Delivery Processing Outbound Delivery Maintain Outbound Delivery Order and choose the function Create. Extended Warehouse Management (EWM) starts the standard goods issue [Seite 314] process and generates if required the necessary documents for billing and shipping.

Integration
For a description of this, see Direct Outbound Delivery Order [Seite 167].

Prerequisites
You are using the corresponding ERP Enhancement Package. Only then does EWM give information about direct outbound delivery orders and perform an availability check. For more information, see the Implementation Guide (IMG) for EWM under Interfaces ERP Integration General Settings Set Control Parameters for ERP Version Control. You have assigned sales organizations. In the SAP Easy Access menu, choose Extended Warehouse Management Interfaces GTS: Assign Sales Organization. If you want EWM to perform automatic determination of the goods movement bin for delivery items that are not pick-relevant, you have defined the goods movement bin determination. EWM defines the goods movement bin depending on the following: Document type Item type Warehouse number Combination of the two product master attributes product group type and product group

On the SAP Easy Access screen, choose Extended Warehouse Management Settings Maintain Goods Movement Bin Determination.

Features
For direct outbound delivery orders, all the functions are available to you that you can perform for outbound deliveries. The following list describes the additional functions or functions that vary: You can also use direct outbound delivery orders for goods issue in the scrapping process (see Performing Scrapping [Seite 130]). You can delete a direct outbound delivery order in EWM. EWM only sends a deletion message for direct outbound delivery orders to ERP. You can add new delivery items with reference to a reference document to a direct outbound delivery order. EWM sends these added delivery items to ERP, and ERP copies these to the relevant ERP outbound delivery. An availability check is also performed for the added items (see Availability Check [Seite 176]). If you want to increase the outbound delivery quantity of an item manually, and ERP has already generated an item for this in the ERP outbound delivery, EWM does not 510 170

SAP Extended Warehouse Management (SAP EWM)

SAP Online Help

20.07.2007

perform another availability check for the difference quantity. When you generate a new item or direct outbound delivery order, EWM can perform an availability check for this quantity. If you want to reduce the outbound delivery quantity, you can do this directly in the direct outbound delivery order. In this case, no further availability check takes place. Only when ERP copies the quantity change into the ERP outbound delivery does SAP Advanced Planning and Optimization (SAP APO) adjust its planned quantity. When you generate a direct outbound delivery order from the user interface of the outbound delivery order, you can manually assign stock to a delivery item that does not have a picking status. Display your direct outbound delivery orders in the form view of the user interface of the outbound delivery order. Choose the input help for Goods Mvt Bin and look for a bin in which stock exists.

Constraints in ERP
You cannot use credit management for direct outbound delivery orders. The price determination in ERP does not provide you with the same functions as the price determination in the sales order. You cannot use any configurable products in direct outbound delivery orders. You cannot perform billing in SAP Customer Relationship Management (SAP CRM) for direct outbound delivery orders. You cannot extend bills of materials in direct outbound delivery orders. ERP does not send messages for a direct outbound delivery order to EWM.

Constraints in EWM
If you are adding packing items to a direct outbound delivery order, EWM cannot perform an availability check for these new delivery items. The kit-to-order process does not support direct outbound delivery orders. Direct outbound delivery orders are not relevant for backorder processing in SAP APO.

SAP Extended Warehouse Management (SAP EWM)

510

171

SAP Online Help

20.07.2007

Fulfilling Immediate Deliveries with Direct Outbound Delivery Orders


Purpose
You can fulfill immediate deliveries and choose between a push and pull procedure: In the push procedure, you make a decision for the outbound delivery without a sales order from the current requirements of the warehouse. For example, you want to use your available transportation capacities as optimally as possible by making use of unused space in a vehicle. Or you have to consider the special requirements of the consumer products industry. For example, you want to distribute a very recent delivery containing fresh goods (lettuce) to outbound deliveries going to different stores. In the pull procedure, the store or customer triggers the process. For example, you only notice later that an article in the last purchase order was not included. You call the warehouse and trigger immediate delivery, so that the goods still delivered on time.

The process flow for the pull procedure is the same as that for direct sales. However, the outbound delivery for the transportation process is relevant here.

Prerequisites
For a description of the prerequisites, see Processing of Direct Outbound Delivery Orders [Seite 170].

Process
The following figure provides an overview of the process flow:

SAP Extended Warehouse Management (SAP EWM)

510

172

SAP Online Help

20.07.2007

Pull Procedure
Customer / Store Check stock and purchase orders

Push Procedure

Warehouse Distribute products without explicit request Check transportation capacities

Generate direct outbound delivery order

Generate direct outbound delivery order

Picking, packing etc.

Picking, packing etc.

Post goods issue and transport

Post goods issue and transport

Post goods receipt

Post goods receipt

...

1. The process starts when one of the following steps is triggered: You want to distribute products to different stores, without an explicit request, or want to make use of available transportation capacities (push procedure). The customer or store checks the stock or purchase orders and notices that stock or products are missing (pull procedure).

2. You then generate a direct outbound delivery order. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery Maintain Outbound Delivery Order and then function Create. Specify ODSH ODO Direct Outbound Delivery as the document type. 3. You continue performing the goods issue steps, such as picking [Seite 322] and packing [Seite 506]. 4. You post goods issue [Seite 314] and transport the products. 5. The customer or store posts goods receipt [Seite 263].

SAP Extended Warehouse Management (SAP EWM)

510

173

SAP Online Help

20.07.2007

Result
You have fulfilled an immediate delivery using a direct outbound delivery order.

SAP Extended Warehouse Management (SAP EWM)

510

174

SAP Online Help

20.07.2007

Scrapping Using a Direct Outbound Delivery Order


Purpose
When scrapping products, you first transport them from a storage bin to the scrapping zone, and then transfer post the products to a scrapping stock type. You then post goods issue for the products that are to be scrapped. For this goods issue posting you use a direct outbound delivery order. Extended Warehouse Management (EWM) generates the direct outbound delivery order corresponding to the handling unit that you are using for the products being scrapped. You do not need to perform picking for this process. For a descriptions of the prerequisites and of the process, see Scrapping [Seite 366].

SAP Extended Warehouse Management (SAP EWM)

510

175

SAP Online Help

20.07.2007

Availability Check
Use
If you generate a direct outbound delivery order and have defined an availability check in Customizing, Extended Warehouse Management (EWM) automatically performs an availability check in one of the following ways, corresponding to your Customizing settings: Call availability check in SAP Advanced Planning and Optimization (SAP APO) Call availability information in ERP Call availability check in EWM

Integration
When SAP APO executes an availability check, SAP APO generates prepersistent temporary quantity assignments (TQAs), which first reserve the quantities temporarily. As soon as EWM saves the respective outbound delivery order, SAP APO changes these prepersistent TQAs to persistent TQAs. ERP then later converts these persistent TQAs into reservations for the delivery quantities. If SAP APO is not available and is able to perform the availability check, EWM continues with the outbound delivery process. Here, EWM confirms the requested delivery quantity and sends the data to ERP. ERP sends this data to SAP APO as soon as it becomes available. If backorder processing is required due to this current data, SAP APO triggers this. If you are not using the availability check in ERP or the availability check in SAP APO, you can perform an availability check in EWM. However, this only works on the basis of the availability known in EWM, and only considers stocks that do not refer to a delivery. If you are using the availability check in SAP APO and have defined scheduling in Customizing for SAP APO, SAP APO also performs scheduling. EWM copies the results of the scheduling into the direct outbound delivery order. If you are not using SAP APO, EWM sets all relevant dates/times to the availability date/time (see section Scheduling).

Prerequisites
If you generate an item manually and want to perform an availability check, you must specify the product, quantity and stock type for the item. If you fail to specify a batch for a product that is subject to batch management, or if EWM is unable to determine one, EWM performs a batch-independent availability check. If you enter the batch at a later time, EWM performs the availability check again, but batch-independently. You have performed Customizing for the availability check in EWM. For more information, see the Implementation Guide (IMG) for EWM under Interfaces Availability Check. If you want EWM to set the picking and loading dates, you have defined a corresponding data profile in Customizing for EWM, under Cross-Process Settings Delivery Processing Dates/Times. You have assigned this data profile to an item type in Customizing for EWM under Goods Issue Process Outbound Delivery Manual Settings Define Item Types for Outbound Delivery Process.

SAP Extended Warehouse Management (SAP EWM)

510

176

SAP Online Help

20.07.2007

Features
If SAP APO, ERP or EWM are able to confirm all quantities and do not change the inspection type automatically, you can check this confirmation by using the status or the additional quantities. In the detailed view of the item, choose the tab page Status. For the status type DAV Availability check, the status value is Confirmed. In the detailed view of the item, choose the tab page Additional Quantities. EWM shows you the quantities in the role for the quantity. For example, you have requested 10 pieces of product A for a delivery item. The reduced quantity [Extern] is 10 pieces, the open quantity [Extern] is zero, and the requested quantity [Extern] is 10 pieces. If SAP APO, ERP or EWM can only partially confirm the requested quantities or change the inspection type automatically, EWM displays a dialog box. Here you can find information such as: Check status, for example Partially Checked Item Product Stock type Inspection type, for example Availability Check in EWM Requested quantity Available quantity Confirmation date/time

For a partial confirmation, EWM also shows you the following: Reduced delivery quantity in the relevant item For example, you requested 10 pieces for an item but only 8 pieces are confirmed. EWM reduces the delivery quantity to 8 pieces. Status value of the checked items as Confirmed In the detailed view of the item, choose the tab page Status. Quantities in the role for quantities Availability Check In the detailed view for the item, choose the tab page Additional Quantities. For example, you have requested 10 pieces of product A for a delivery item. However, only 8 pieces were confirmed. The reduced quantity is 10 pieces, the open quantity is zero, and the requested quantity is 10 pieces. You can display the available stock for a product. In the view for the item on the user Availability Information. interface for the outbound delivery order, choose EWM does not perform an availability check in EWM for the following delivery items: Delivery items that belong to a scrapping process Packing items

For the availability check in SAP APO or ERP, EWM also considers the case where ERP carries a product in a different unit of measure to EWM. For example, you use Catch Weight [Extern] in EWM. In catch weight, you can work with multiple units of measure. In this case, EWM converts the delivery quantities into the unit of measure used in ERP.

SAP Extended Warehouse Management (SAP EWM)

510

177

SAP Online Help

20.07.2007

If the delivery quantity is only partially confirmed, or if you call the availability information, EWM also shows you the delivery quantity in both units of measure in a dialog box.

Scheduling
EWM can set the following dates/times based on the results of the availability check: Dates/times at delivery header level: Delivery date/time

Dates/times at delivery item level: Picking start and finish Loading start and finish Goods issue start and finish

EWM only sets the picking or loading dates/times if you have specified them in the corresponding date profile in Customizing for the item type used. EWM performs scheduling based on the type of availability check it finds: If EWM finds A Availability Check in SAP APO as the type of availability check, and you have defined scheduling in Customizing for SAP APO, EWM copies the results of the scheduling into the direct outbound delivery order. If EWM finds a different type of availability check, the system sets the dates/times of the direct outbound delivery order - such as the delivery date and goods issue start and finish to the confirmation date of the availability check.

For more information, see the Implementation Guide (IMG) for EWM under Interfaces Availability Check.

SAP Extended Warehouse Management (SAP EWM)

510

178

SAP Online Help

20.07.2007

Notification of Expected Goods Receipt


Definition
A document in the inbound delivery process that copies all relevant logistics data from the initiator of the inbound delivery process, such as data of a purchase order or a production order. An expected goods receipt is generated out of a notification of expected goods receipt.

Use
You use notification of expected goods receipt to save logistics data transferred from an open purchase order or production order, and to generate an expected goods receipt from it. For more information, see Using Expected Goods Receipts [Seite 181].

Integration
The execution of the actions depends on the Post Processing Framework (PPF) Settings [Seite 105]. The following configuration exists in the standard system: The delivery process receives a message from a reference document with all the relevant logistics data. Extended Warehouse Management (EWM) automatically generates a notification of expected goods receipt from this message. In the notification, EWM saves the information contained in the message. Changing an existing expected goods receipt:

If an inactive notification (inactive version) exists in EWM, you can generate a new expected goods receipt by activating the inactive notification manually.

SAP Extended Warehouse Management (SAP EWM)

510

179

SAP Online Help

20.07.2007

Expected Goods Receipt


Definition
Document containing the data of an expected goods receipt. The expected goods receipt contains data of an open purchase order or open production order. It represents a template that enables you to copy data from a purchase order or production order when creating a delivery manually.

Use
You can copy or delete an expected goods receipt. For more information, see Using Expected Goods Receipts [Seite 181].

Integration
After Extended Warehouse Management (EWM) has activated the Notification of Expected Goods Receipt [Seite 179], it generates the expected goods receipt. In doing so, EWM copies all relevant data from the notification into the expected goods receipt.

SAP Extended Warehouse Management (SAP EWM)

510

180

SAP Online Help

20.07.2007

Using Expected Goods Receipts


Use
You do not want to use an advanced shipping notification in one of the following instances: For a purchase order or purchase order item For a production order or production order item

In this case, you can use the expected goods receipt to copy data from a purchase order, production order or corresponding item to an inbound delivery. You can also copy single delivery items from an expected goods receipt to an existing inbound delivery. For example, a vendor still has space on his vehicle, and sends you more products than he or she has specified in the advanced shipping notification.

Integration
You usually schedule report /SCWM/ERP_DLV_DELETE so that Extended Warehouse Management (EWM) requests new expected goods receipts from ERP. You use these expected goods receipts as templates to generate an inbound delivery in EWM manually. In exceptional circumstances, you can also use report /SPE/INB_EGR_CREATE in ERP to generate an expected goods receipt. ERP informs EWM about this, and EWM generates an expected goods receipt as well.

Prerequisites
You have scheduled report /SCWM/ERP_DLV_DELETE [Seite 184]. This report deletes the existing expected goods receipts in EWM and requests new expected goods receipts from ERP for a time period that must be entered. If you want to work with expected goods receipts, you have allowed manual generation of single delivery items in Customizing for EWM, under Goods Receipt Process Inbound Delivery Manual Settings Define Item Types for the Inbound Delivery Process. You have made the required settings for the expected goods receipt in Customizing for EWM: Goods Receipt Process Expected Goods Receipt Use Wizard to Define Document Types for Expected Goods Receipt Use Wizard to Define Item Types for Expected Goods Receipt Define Allowed Item Types for Expected Goods Receipt Define Document Type Determination for Expected Goods Receipt Define Item Type Determination for Expected Goods Receipt

In Customizing for EWM, you have defined the document type determination and item type determination for the inbound delivery that EWM is to create: Goods Receipt Process Inbound Delivery Define Document Type Determination for Inbound Delivery Process Define Item Type Determination for Inbound Delivery Process

SAP Extended Warehouse Management (SAP EWM)

510

181

SAP Online Help

20.07.2007

You have defined the required profiles for the document type and item type in Customizing for EWM, under Cross-Process Settings Delivery Processing. You have defined the integration with ERP for expected goods receipt in Customizing for EWM under Interfaces ERP Integration Delivery Processing.

You can use BC Set /SCWM/DLV_EXPGR Delivery Processing in EWM Expected Goods Receipt to make the Customizing settings described above. You have authorization for the activity for creating inbound deliveries from an expected goods receipt for authorization object EWM Warehouse Request, or general authorization for creating inbound deliveries manually. On the SAP Easy Access screen, choose Tools Administration User Maintenance Role Administration Roles, and check the settings for your role.

Features
If you are not using an advanced shipping notification in the purchase order for your delivered products, the following options are available to you for generating an inbound delivery: You generate an inbound delivery in ERP. You send this to EWM, so that you can execute further goods receipt process steps. You generate an expected goods receipt as a template document locally in EWM, which you can use to generate an inbound delivery manually. You switch to ERP from the user interface in EWM to generate an inbound delivery. You use Business Add-Ins (BAdIs) /SCWM/EX_DLV_ERP_CALL and /SCWM/EX_DLV_ERP_CALL_CTRL to define whether you generate an inbound delivery in ERP or locally in EWM. On the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Inbound Delivery Maintain Inbound Delivery. You choose the user interface for the inbound delivery in EWM, and specify the required delivery data without ERP checking this data with the data of the open purchase order.

If you are not using any inbound deliveries in the production for your delivered products, the following options are available to you for generating an inbound delivery: You generate an expected goods receipt as a template document locally in EWM, which you can use to generate an inbound delivery manually. In EWM, you choose the user interface for the inbound delivery, and specify the required delivery data.

If you are using an expected goods receipt to generate an inbound delivery manually in the purchase order or production, this has the following advantages: You can execute the goods receipt process steps in one system only, namely EWM. If ERP is temporarily unavailable, you can still execute the goods receipt process steps. You generate an inbound delivery whose data has been checked by both ERP and EWM. This enables you to make sure that you post goods receipt in ERP as well. As the expected goods receipt is based on the data of the open purchase order or open production order, you can use the expected goods receipt as a preview of the goods receipt.

SAP Extended Warehouse Management (SAP EWM)

510

182

SAP Online Help

20.07.2007

Actions for Expected Goods Receipts


You can generate or delete an expected goods receipt. An expected goods receipt is a temporary document. When EWM no longer requires it, the system deletes the expected goods receipt. You cannot archive the expected goods receipt. When EWM deletes an expected goods receipt, the system makes ERP redefine the expected goods receipts that are still open. As the expected goods receipt only acts as a template for copying existing data, you cannot change any of this data. In the related inbound delivery, however, you are able to change the data as in an inbound delivery with a preceding document, such as changing the quantity. If you want to delete one or more expected goods receipts, use report /SCWM/ERP_DLV_DELETE [Seite 184].

EWM does not update the expected goods receipt and does not offset the quantity for the expected goods receipt. In addition, EWM does not show you the expected goods receipt in the document flow of the inbound delivery. EWM uses the delivery items of the expected goods receipt to calculate the expected workload (see Workload in the Monitor Node [Seite 720]). In the Manual indicator in the header data of the inbound delivery, if the value is set to Y for Generated Manually with Predecessor, this tells you whether EWM has generated an inbound delivery from an expected goods receipt.

See also: Generate Inbound Delivery from Expected Goods Receipt [Seite 187], Generate Inbound Delivery Item from Expected Goods Receipt [Seite 189]

SAP Extended Warehouse Management (SAP EWM)

510

183

SAP Online Help

20.07.2007

Generate and Delete Expected Goods Receipts


Use
You can use report /SCWM/ERP_DLV_DELETE to request expected goods receipts for a purchase order or for a production order from ERP. You can choose between the following options: Select possible expected goods receipts in Extended Warehouse Management (EWM) Delete expected goods receipts in EWM Create expected goods receipts in EWM Delete and create expected goods receipts in EWM

Integration
If you want to delete expected goods receipts from ERP, you can use report /SPE/INB_EGR_CREATE in ERP. This ERP report calls RFC-enabled function modules in EWM, which then delete the expected goods receipts in ERP. If you want to view the deletion log of the RFC-enabled function modules, choose this report in EWM. Logs in

Prerequisites
If you want to use this report to request expected goods receipts from ERP, the following prerequisites must be fulfilled: You are using the corresponding ERP release. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management under Interfaces ERP Integration General Settings Set Control Parameters for ERP Version Control. You are using a logical system that represents the target system, enabling ERP to send the found expected goods receipts to EWM. If EWM is to perform sending using a remote function call (RFC), you have defined an RFC destination for the target system. On the SAP Easy Access screen, choose Tools Administration Administration SM59 - RFC Destinations. You have defined parallel processing in the delivery, in Customizing for EWM. For more information, see the IMG for EWM under Cross-Process Settings Delivery Processing General Settings Parallel Processing in the Delivery.

Features
If you want to select expected goods receipts, you have to specify the mandatory selection parameters. You can also restrict the selection further by specifying optional selection parameters. EWM processes the specified selection parameters as logical AND operations. You can choose from the following selection parameters: General Selection Parameters You must specify an ERP Warehouse Number and a Business System. These selection parameters are mandatory. You can specify all the warehouse numbers that are defined in Customizing. For more information, see the IMG for EWM under Interfaces ERP Integration General Settings Map Warehouse Numbers from ERP System to EWM.

SAP Extended Warehouse Management (SAP EWM)

510

184

SAP Online Help

20.07.2007

If the ERP warehouse number is defined for multiple business systems, the system copies the business system that occurs first in the alphabet. You can manually override this automatic assignment. Special Selection Parameters You can choose either Purchase Order/Deliv. Schedule or Production Order for the selection. By making this selection, you define the type of expected goods receipts that the report is to process. This selection parameter is mandatory. If you want to specify the selection parameter in more detail, you have the following options: You can also specify purchase orders or vendors for Purchase Order/Deliv. Schedule to restrict the selection. These entries are optional. You can also specify orders or vendors for Production Order to restrict the selection. These entries are optional.

If you want to perform the selection across all existing expected goods receipts that are available in the system for a purchase order, delivery schedule or production order, you must leave the fields Purchase Order, Delivery Schedule or Production Order empty. If you do not want to restrict the selection to certain vendors, you must leave the field Vendor empty. Selection Period You must specify an interval start and interval end for the selection. This selection parameter is mandatory. You can choose between a fixed interval, such as running automatically in the background, or a free interval, such as manual execution. Time Zone The system automatically determines the time zone using the warehouse number and business system specified under General Selection Parameters, and displays them to you. It uses the time zone for your time details. Fixed Interval Choose this interval if you do not want to specify a fixed time point for the interval. The system determines the interval dynamically and uses the schedule time for it. Schedule Time (Hours) When you specify the number of hours, the report determines the interval end. The report automatically copies the current system time as the time of execution of the interval start. Time Period The report uses this field to show you calculated interval start and interval end for the selection. Free Interval Choose this interval if you want to specify the interval freely. Time Period You can enter any interval start and interval end for the selection.

SAP Extended Warehouse Management (SAP EWM)

510

185

SAP Online Help

20.07.2007

The interval start and end then give the time period for which the system is to request expected goods receipts from ERP. If the system is to delete expected goods receipts, it only considers the interval end. It deletes all documents between the system start and the specified interval end. Technical Settings Program Mode You can choose between the following program modes: Only Select The report selects all expected goods receipts in EWM that match your selection parameters. Here, the expected goods receipts must lie within the determined time interval. This gives you an overview of the selection quantity. Only Create The report does not select or delete expected goods receipts, it merely transmits the given selection parameters to ERP. ERP sends the expected goods receipts back to EWM. Only Delete The report deletes the expected goods receipts in EWM that match the selection parameters. Here, the expected goods receipts must lie within the time interval that the report determines for the selection. Delete and Create The report first deletes existing expected goods receipts in EWM. It then requests the new expected goods receipts from ERP. Log Availability (Days) You have the option of specifying how long EWM is to save the log to the database.

Logging
The report generates a log for all program modes, apart from Only Select. It saves the following in the log: All expected goods receipts that match your selection criteria and which it can process Selection parameters used Number of expected goods receipts found

We recommend that you delete obsolete logs at regular intervals.

Activities
On the SAP Easy Access screen, choose Tools ABAP Workbench Development SE37 - Function Builder, and schedule the report as a background job.

SAP Extended Warehouse Management (SAP EWM)

510

186

SAP Online Help

20.07.2007

Generate Inbound Delivery from Expected Goods Receipt


Use
In Extended Warehouse Management (EWM), you can generate an inbound deliver from an expected goods receipt.

You order products from an external vendor and generate a purchase order in ERP. ERP generates a corresponding expected goods receipt. The vendors vehicle arrives at the warehouse, and you generate a corresponding inbound delivery in EWM, based on the shipping documents.

Prerequisites
See Prerequisites under Using Expected Goods Receipts [Seite 181].

Procedure
...

1. On the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Inbound Delivery GR Preparation - External Procurement. 2. Choose with the quick info Default Values, and check whether Select Expected GR has been set, enabling EWM to search for expected goods receipts. 3. Look for the expected goods receipt that belongs to your inbound delivery, and generate an inbound delivery from an expected goods receipt. To do this, proceed as follows: Group box Transportation Unit Set Without TU. If you are using a transportation unit (TU), enter a valid TU, a carrier, and the Standard Carrier Alpha Code (SCAC) for the partner. If the specified TU is unique, specifying the carrier and the SCAC is optional. Group box Search Requests i. Under Find, choose either Purchase Order or Expected Goods Receipt, and specify the purchase order number or document number of the expected goods receipt. Choose the function Search.

ii.

EWM displays all the expected goods receipts it finds in the lefthand area of the screen. iii. iv. In the lefthand screen area, set Flag for a delivery item in the expected goods receipt. Choose the function Copy Flagged Item.

EWM generates a new inbound delivery from the expected goods receipt, and copies all data from the selected delivery item of the expected goods receipt. EWM also displays a dialog box containing header data of the new inbound delivery. If you want to copy multiple delivery items at the same time, you must copy the delivery items of the expected goods receipt in exactly one inbound delivery. You can edit the header data, specifying the advanced shipping notification, for example. EWM displays the new delivery items in the righthand screen area. 4. Choose Save and save the new inbound delivery.

SAP Extended Warehouse Management (SAP EWM)

510

187

SAP Online Help

20.07.2007

On the inbound delivery user interface in ERP, you can check whether EWM has sent the new inbound delivery to ERP.

Result
You have generated an inbound delivery locally in EWM from an expected goods receipt, and can now perform further goods receipt steps on the user interface of the inbound delivery, such as posting goods receipt.

SAP Extended Warehouse Management (SAP EWM)

510

188

SAP Online Help

20.07.2007

Generate Inbound Delivery Item from Expected Goods Receipt


Use
In Extended Warehouse Management (EWM), you can add additional delivery items to an existing inbound delivery by copying them from the expected goods receipt.

You order products from an external vendor. The vendor sends an advanced shipping notification for these products. However, the vendor also sends other products in the same inbound delivery, which were not included in the advanced shipping notification. The products are requested for the same day, and a corresponding purchase order and expected goods receipt are present. You add further delivery items for the additional products to the existing inbound delivery by copying these delivery items from the expected goods receipt.

Prerequisites
See Prerequisites under Using Expected Goods Receipts [Seite 181].

Procedure
...

1. On the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Inbound Delivery GR Preparation - External Procurement. 2. Choose with the quick info Default Values, and check whether Select Expected GR and Sel. Inb. Deliveries have been set, enabling EWM to search for expected goods receipts and inbound deliveries. 3. First look for the inbound delivery you require, for example by using the document number of the inbound delivery to which you want to add a delivery item from an expected goods receipt. In a second search, add the expected goods receipts to the result of the first search, for example using the document number of the purchase order. Choose the delivery item that you want to add to your inbound delivery. Group box Transportation Unit Set Without TU. If you are using a transportation unit (TU), enter a valid TU, a carrier, and the Standard Carrier Alpha Code (SCAC) for the partner. If the specified TU is unique, specifying the carrier and the SCAC is optional. Group box Search Requests Look for the inbound delivery you require. i. ii. Select the Inbound Delivery under Find and specify the document number of the inbound delivery. Choose the function Search.

EWM displays a dialog box in which you can choose No to cancel the unspecific search query by expected goods receipts, and can continue by searching by inbound delivery. EWM displays all the delivery items it finds in the righthand screen area.

EWM only displays delivery items whose goods receipt status and warehouse activity status are set to Not Started. Searching by expected goods receipts:
... ...

SAP Extended Warehouse Management (SAP EWM)

510

189

SAP Online Help i. ii.

20.07.2007 Select the Purchase Order under Find and specify the document number of the purchase order. Choose with the quick info Add Search Result.

EWM displays the expected goods receipts for the purchase order in the lefthand screen area, and in addition to the delivery items of the first search also displays delivery items of existing inbound deliveries for this purchase order in the righthand screen area. iii. iv. In the lefthand screen area, set Flag for a delivery item in the expected goods receipt. Copy Flagged Item, and choose Choose to the right of the function Add Flagged Item to Inbound Delivery. EWM displays a dialog box containing numerous document numbers of the two search queries. v. Select the document number you require by choosing Copy.

EWM copies all data from the selected delivery item to the new inbound delivery item, and also displays it in the righthand screen area along with existing inbound delivery items for this purchase order. 4. Choose Save and save the new inbound delivery item.

Result
You have generated a delivery item locally in EWM from an expected goods receipt.

SAP Extended Warehouse Management (SAP EWM)

510

190

SAP Online Help

20.07.2007

Goods Receipt Posting from Production


Purpose
In Extended Warehouse Management (EWM), you can post goods receipt for your finished products.

Process
If you want to post goods receipt from production, you have the following options: Goods Receipt Posting Triggered by ERP [Seite 192] Goods Receipt Posting Triggered by EWM [Seite 195]

You can also use process Goods Receipt Posting Triggered by ERP and Goods Receipt Posting Triggered by EWM at the same time. For example, you can generate inbound deliveries for the same production order at the same time in both EWM and ERP. If you want to avoid duplicate inbound deliveries being generated for a production order, you can set the indicator GR From EWM Only in ERP. This allows only Generation of Expected Goods Receipts [Seite 184] in ERP, and you can only post the goods receipt in EWM.

Result
In both instances, EWM generates an inbound delivery for your finished products, for which you post goods receipt.

SAP Extended Warehouse Management (SAP EWM)

510

191

SAP Online Help

20.07.2007

Goods Receipt Posting Triggered by ERP


Purpose
You want to post goods receipt [Seite 263] for products from production. For this, you work in Extended Warehouse Management (EWM) with inbound deliveries that ERP generates parallel to production. When you confirm the last production step for a product in the production order, meaning a production or process order, ERP generates an inbound delivery instead of a material document. The inbound delivery provides you with information about the material and quantity currently being produced. EWM uses document type IDPD Inbound Delivery from Production to differentiate that an EWM inbound delivery from production takes place. For more information about document type determination, see the Implementation Guide (IMG) for Extended Warehouse Management under Goods Receipt Process Inbound Delivery Define Document Type Determination for Inbound Delivery Process.

Prerequisites
You are using SAP SCM 5.1 and the corresponding ERP release. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management under Interfaces ERP Integration General Settings Set Control Parameters for ERP Version Control. You are using simple transport routes, for example without stock transport orders, so that your goods receipt posting in the central warehouse directly triggers generation of the EWM inbound delivery in the decentralized warehouse.

Process
The following figure provides an overview of the process flow:

SAP Extended Warehouse Management (SAP EWM)

510

192

SAP Online Help

20.07.2007

ERP (Delivery)
User generates production order 1

EWM

ERP (Production)

User releases production order

Confirmation of production end triggers goods receipt posting

2 User confirms production steps and 3 production end

System generates inbound delivery

4 System generates inbound delivery

System posts goods receipt

7 User posts goods receipt

User transports product to warehouse

System updates production order and inbound delivery

7 User puts away product

...

1. You generate a production order, namely a production or process order, and release it. The production order contains a plant / storage location combination that refers to a warehouse in which you are using EWM. In other words, EWM manages the plant and storage location combination. 2. You confirm the end of the designated production steps in the production order. In doing this, ERP updates the finished quantity and marks the completed production steps. 3. When you confirm the last production step for a product in the production order, ERP generates an ERP inbound delivery and transmits it to EWM. Prerequisite for this is that you have made corresponding settings in Customizing for ERP so that ERP automatically executes order confirmation for the goods receipt. This enables the confirmation of the last production step for a product to trigger goods receipt in ERP. For more information, see: Implementation Guide (IMG) for ERP: Production Production Control Master Data Define Production Scheduling Profile Production Basic Data Routing Operation Data Define Control Key

SAP Help Portal, under SAP ERP SAP ERP Central Component Logistics Logistics Execution (LE) Goods Receipt Process for Inbound Deliveries goods Receipt Goods Receipt Posting Posting Partial Goods Receipts for Inbound Deliveries

SAP Extended Warehouse Management (SAP EWM)

510

193

SAP Online Help

20.07.2007

SAP Help Portal, under SAP ERP SAP ERP Central Component Logistics Production Planning and Control (PP) Production Orders (PP-SFC) Order Release SAP Help Portal, under SAP ERP SAP ERP Central Component Logistics Production Planning and Control (PP) Production Orders (PP-SFC) Goods Movement Automatic Goods Receipt

Once you have released the production order you can also generate an ERP inbound delivery manually. For more information, see the Implementation Guide (IMG) for ERP under Logistics Materials Management Purchasing Purchase Order Subsequent Functions MIGO Goods Receipt. If EWM does not manage the plant and storage location combination, ERP generates a material document immediately at goods receipt posting. You put away the product, and ERP updates the stock. 4. EWM receives a corresponding inbound delivery notification from ERP, and generates an EWM inbound delivery corresponding to this. The inbound delivery contains a link to the production order in ERP. 5. You transport the finished product into the warehouse, for example to the goods receiving area. 6. You can use the number of the production order to find the corresponding EWM inbound delivery, post the goods receipt, and put away the product. 7. EWM transmits the goods receipt posting to ERP. ERP also posts goods receipt for the related ERP inbound delivery. ERP also updates the stock in the production order and in the ERP inbound delivery, due to the goods movement.

Result
You have posted goods receipt for your products from production, and updated the stock in ERP.

SAP Extended Warehouse Management (SAP EWM)

510

194

SAP Online Help

20.07.2007

Goods Receipt Posting Triggered by EWM


Purpose
You receive finished products, in the goods receiving area for example, for which you want to post goods receipt [Seite 263]. For this, you are working with expected goods receipts [Extern] in Extended Warehouse Management (EWM). In exceptional circumstances, you generate an EWM inbound delivery manually without a template, meaning without an expected goods receipt. In this case you must make sure that the data in the inbound delivery is validated. You can use the standard implementation of Business Add-In (BAdI) /SCWM/EX_ERP_PROD. EWM uses document type IDPD Inbound Delivery from Production to differentiate that an EWM inbound delivery from production takes place. For more information about document type determination, see the Implementation Guide (IMG) for EWM under Goods Receipt Process Inbound Delivery Define Document Type Determination for Inbound Delivery Process.

Prerequisites
You are using SAP SCM 5.1 and the corresponding ERP release. For more information, see the Implementation Guide (IMG) for EWM under Interfaces ERP Integration General Settings Set Control Parameters for ERP Version Control. You are using simple transport routes, for example without stock transport orders, so that your goods receipt posting in the central warehouse directly triggers generation of the EWM inbound delivery in the decentralized warehouse.

Process
The following figure provides an overview of the process flow:

SAP Extended Warehouse Management (SAP EWM)

510

195

SAP Online Help

20.07.2007

ERP (Delivery)
User generates production order 1

EWM

ERP (Production)

User releases production order

Function module generates new expected goods receipts (GRs)

2 Report call deletes expected GRs

System generates expected GRs

System generates inbound delivery

User generates inbound delivery as copy of expected GR

4 User confirms production end and 5 moves product, e.g. to GR area

System posts goods receipt

User posts goods receipt

System updates production order and inbound delivery

User puts away product

...

1. You generate a production order and release it. The production order contains a plant / storage location combination that refers to a warehouse in which you are using EWM. In other words, EWM manages the plant and storage location combination. If EWM does not manage the plant and storage location combination, ERP generates a material document immediately at goods receipt posting. You put away the product, and ERP updates the stock. ERP does not trigger generation of expected goods receipts. 2. EWM uses report /SCWM/ERP_DLV_DELETE [Seite 184] to delete any existing expected goods receipts in EWM, and calls ERP function module /SPE/INB_EGR_CREATE_PROD. Prerequisite for this is that you execute report /SCWM/ERP_DLV_DELETE. For more information, see Generate Inbound Delivery from Expected Goods Receipt [Seite 187]. When EWM calls the ERP function module, ERP checks whether relevant production orders still exist for which you still have to post goods receipt. ERP identifies the relevance from your selection criteria and from the open quantities. If open quantities still exist, then the goods receipt indicator is set in ERP but the final delivery indicator is not set. 3. For each relevant production order, EWM receives a notification for the expected goods receipt from ERP, and generates a corresponding expected goods receipt in EWM.

SAP Extended Warehouse Management (SAP EWM)

510

196

SAP Online Help

20.07.2007

The expected goods receipt contains a link to the production order in ERP. You can use the expected goods receipt in EWM for planning purposes. It contains the planned times and quantities, for example. 4. You confirm the end of the designated production steps in the production order. In doing this, ERP updates the finished quantity and marks the completed production steps. 5. You transport the finished products into the warehouse, for example to the goods receiving area. 6. You can use the number of the production order to find the expected goods receipt, and generate a corresponding EWM inbound delivery. Here you use the expected goods receipt as a template for the EWM inbound delivery, and can adjust the quantities if required. 7. You post the goods receipt and put away the products. 8. EWM transmits the goods receipt posting to ERP. ERP also posts goods receipt for the related ERP inbound delivery. ERP also updates the stock in the production order and in the ERP inbound delivery, due to the goods movement.

Result
You have posted goods receipt for your products from production, and updated the stock in ERP.

SAP Extended Warehouse Management (SAP EWM)

510

197

SAP Online Help

20.07.2007

Connection of Delivery Processing to Additional Functions


Use
Delivery processing uses the following additional functions: Connection to yard management [Seite 199] Connection to transportation management [Seite 201] Connection to route determination [Seite 202] Connection to serial numbers [Seite 213] Connection to SAP Global Trade Services (SAP GTS) [Seite 214] Connection to Environment, Health & Safety (EH&S) [Seite 967] Connection to determination of country of origin [Seite 224] Connection to the Post Processing Framework [Seite 226] Connection to value-added service order (VAS order) [Seite 230] Kit in the warehouse request for the outbound delivery order [Seite 234] Connection to quality management [Seite 293] Connection to batch management [Seite 245]

SAP Extended Warehouse Management (SAP EWM)

510

198

SAP Online Help

20.07.2007

Connection of Delivery Processing to Yard Management


Use
If you use yard management [Seite 619] in Extended Warehouse Management (EWM), this communicates with delivery processing to exchange relevant information such as status changes. This enables delivery processing to allow follow-up actions, such as statusdependent goods receipt posting. Yard management and delivery processing exchange the following information changes: Status changes in the delivery, such as from In transit to In yard Information about transportation units (TUs)

If you do not use yard management, delivery processing obtains the information about status changes from the user interface of the delivery.

Prerequisites
You use yard management in EWM. See: The Prerequisites section under Yard Management [Seite 619].

Features
As a result of the connection to yard management, EWM is able to send modified TU data from yard management to delivery processing.
...

EWM writes this TU data to delivery processing and the handling unit in the following way: If shipping and receiving is activated, delivery processing changes the status value for the Assign Transportation Unit status of the delivery document item from Not relevant to Not started. EWM updates the TU data with the assignment of transportation unit to a delivery header, delivery document item, or at handling unit level. a. Yard management informs delivery processing about the assignment. b. For shipping and receiving, delivery processing changes the status value for the Assign Transportation Unit status of the delivery document item from Not relevant (default) to Completed. If yard management has not assigned a transportation unit to a delivery document item, it sets the Assign Transportation Unit status of the delivery document item to Not started. c. Delivery processing aggregates the status data of the delivery document items. If all delivery document items have the same status value, namely Not relevant, Not started, or Completed, delivery processing also sets this status value for the delivery document header for shipping and receiving. If one delivery document item has a different status value to the others, for example, Completed rather than Not started, delivery processing sets the status value for the delivery document header for shipping and receiving to In process. As long as the status value of the delivery document header for shipping and receiving has not yet reached In processing or Completed, you can still change the following fields in the delivery document:

SAP Extended Warehouse Management (SAP EWM)

510

199

SAP Online Help

20.07.2007

Delivery document header status In yard or Outside yard Vehicle Door

d. As soon as the Assign Transportation Unit status of the delivery document header has the value In processing or Completed, delivery processing locks the delivery document for assigning transportation units. It then informs yard management about this lock and the status changes that have occurred. This lock prevents data inconsistencies occurring between delivery processing and yard management. Now you can only change the assignment of transportation units in shipping and receiving or in yard management. Using an action for the transportation unit If you execute actions for transportation units, such as Loading Begin, EWM simultaneously updates the delivery documents and handling units that are assigned. In delivery processing, you can only execute the actions In Yard or Leave Yard for transportation units that are assigned to the respective delivery documents or vehicles. To keep the data consistent, EWM distributes the assignment of transportation units to doors using the delivery documents and handling units that are assigned. See also: Assignment of Deliveries to Vehicles and TUs [Seite 617]

SAP Extended Warehouse Management (SAP EWM)

510

200

SAP Online Help

20.07.2007

Connection of Delivery Processing to Transportation Management


Use
EWM sends a shipment output to transportation management when creating a warehouse request for an outbound delivery or outbound delivery order [Seite 112].

Features
For more information about the features of transportation management, see Transportation Management [Seite 629].

SAP Extended Warehouse Management (SAP EWM)

510

201

SAP Online Help

20.07.2007

Route Determination in the Delivery


Use
Delivery processing calls the routing guide [Extern] for automatic route determination [Seite 638]. This determines the route and sends it back to delivery processing. You can also manually enter or change a route on the user interface of the delivery. Delivery processing executes route checks and, in doing so, it determines whether the route found in the routing guide or the route that was manually entered in the delivery is valid for delivery processing. When working with automatic route determination, you can use Extended Warehouse Management (EWM) to automatically find and check the route and transportation information in the outbound delivery request, the outbound delivery order, and the outbound delivery (see Special Features for Outbound Delivery Objects [Seite 210]).

Integration
For actual route determination, EWM uses the routing guide.

Prerequisites
You made the settings for route determination [Seite 205]. The following delivery data has been specified: The supply chain unit of the warehouse at the delivery header Route determination uses this supply chain unit as a source location. At least one item with an entry for product, a quantity, weight and volume At least one item with a planned goods issue date (for forwards scheduling) or a planned delivery date at header level (for backwards scheduling) If you are using your own document types, the route status must be activated at header level so that route determination can set this status. If the following delivery data is available, route determination uses it as an additional constraint during route determination: The carrier, if the determination indicator [Extern] is not initial or the carrier has been specified by EWM. The means of transport, if the determination indicator is not initial or the means of transport has been specified by EWM. The route itself, if the determination indicator is not initial or the route has been specified by EWM. The shipping conditions of all items, if all the items have the same shipping conditions.

Features
Route Determination
Route determination attempts to find a route in delivery processing that corresponds to the delivery data, for example, the product, quantity, or date/time. For this, route determination calls the routing guide, either with a predefined route or it does not supply a route for the routing guide. You either enter the predefined route manually or an external system, such as

SAP Extended Warehouse Management (SAP EWM)

510

202

SAP Online Help

20.07.2007

SAP Customer Relationship Management (SAP CRM) assigns a route to EWM. Route determination in the delivery does not overwrite any routes manually entered. You define the route determination status in Customizing for EWM: Route Determination is Always Active (<blank>). Automatic Route Determination Only in Case of Initial Route Automatic Route Determination Inactive Route Determination Inactive

For more information, see the Implementation Guide (IMG) for EWM under Goods Issue Process Outbound Delivery Route Determination Activate or Deactivate Route Determination. You can directly enter constraints for route determination in the outbound delivery.

Simulation of Route Determination


You can simulate route determiantion [Seite 662], that is, check which routes EWM finds for specific data or which routes EWM approves as valid after the route check.

Priority
If, while using the data of the relevant items (see Execution of Automatic Route Determination [Seite 207]), route determination finds one or more valid routes for the start date/time and the supply chain unit, it uses the route with the highest priority. The routing guide sends the priority together with the route to delivery processing. Die Prioritt wird ausgehend vom verwendeten Kostenprofil gesetzt.

Data Use
If route determination automatically finds a valid route, you specify a valid route, or an external system transfers a valid route to EWM, route determination copies certain data to the delivery and, if necessary, sets further delivery data automatically. The data automatically set can be data that route determination also determines, for example, delivery date/time or means of transport. For more information about the data that delivery processing uses or copies in route determination, see Data Use in Route Determination [Seite 209].

Automatic Route Determination


If you have not yet entered a route (that is, the field for the route is empty) or you have changed data that is route-dependent (for example, item quantities), route determination executes automatic route determination. For more information, see Execution of Automatic Route Determination [Seite 207].

Route Status
Route determination sets a route status at header level depending on the route determination. You can view this on the user interface of the outbound delivery order or the outbound delivery in the detail view on the Status tab page under the Route Determination status type.

Outbound Delivery Objects


In addition to the features mentioned here, route determination handles the various outbound delivery objects differently. For more information, see Special Features for Outbound Delivery Objects [Seite 210].

Route Determination in Transportation Cross-Docking


In a transportation cross-docking process (TCD process), route determination uses the supply chain unit of the final ship-to party as the destination location instead of the supply chain unit of the ship-to party. If the route contains a TCD location, route determination enters this as the ship-to party in the delivery. The previous ship-to party becomes the final ship-to party.

SAP Extended Warehouse Management (SAP EWM)

510

203

SAP Online Help

20.07.2007

Route determination proceeds in the same way with the delivery date, which means that route determination works with a delivery date and a final delivery date. Route determination enters the route to the next TCD location as the route for the delivery. This also applies to a route that is specified manually. Furthermore, route determination also specifies the goods issue date/time at the TCD location in the delivery header. If route determination cannot identify a TCD location during a new route determination, it deletes the TCD-specific data from the delivery. For more information about route determination for transportation cross-docking, see Route Determination as Part of Cross-Docking [Seite 655].

Route Check
EWM checks in delivery processing whether a valid route exists for the delivery data. If you specify a route manually or deactivate automatic route determination, EWM then carries out a further check to determine whether the route that you have specified manually is valid for the delivery data.

Activities
If you want to manually trigger route determination, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery Maintain Outbound Delivery Order or Maintain Outbound Delivery and then the Route pushbutton. For more information about the individual settings for the user interface, see Route Determination on the User Interface [Seite 211].

SAP Extended Warehouse Management (SAP EWM)

510

204

SAP Online Help

20.07.2007

Making Settings for Route Determination


To use route determination, you must make the following settings:

Customizing
You have activated the route determination of transportation management in Customizing in Extended Warehouse Management (EWM). For more information, see the Implementation Guide (IMG) for EWM under Goods Issue Process Transportation Management Route Determination General Settings for Route Determination. You have activated the route determination for the delivery or the warehouse that is being used. For more information, see the IMG for EWM under Goods Issue Process Outbound Delivery Route Determination Activate or Deactivate Route Determination. You also have the option of making additional settings for scheduling. For more information, see the IMG for EWM under Goods Issue Process Outbound Delivery Route Determination Define Scheduling Within Route Determination.

Master Data
You have created a route and a leg from the supply chain unit [Extern] of the sending warehouse (source location) to the supply chain unit of the recipient (ship-to location). Here, the destination location may also be a zone. To do this, on the SAP Easy Access screen, you have chosen Extended Warehouse Management Master Data Shipping and Receiving Route Determination Maintain Route. You have made sure that the goods recipient in the delivery has been assigned to a supply chain unit that is being used for route determination. As a business partner or address is entered in the delivery as a goods recipient, an assignment still has to be made with which the destination location used in a route is determined. This is done in the following way: If a document address is entered in the delivery for the goods recipient, the system attempts to find a supply chain unit zone based on the address data. This zone is then used as the destination location for route determination. If no document address is used, a corresponding supply chain unit is found in the following way: If you are working without an address or without a zone as a destination location in the route, you have created an individual supply chain unit for the ship-to party in the supply chain unit master data. In the Bus.Partner field on the General tab page, you assign this supply chain unit to the business partner (ship-to party) that has been entered in the delivery.

If the goods recipient is a business partner or customer whose master data has been transferred from ERP, the system usually enters the assignment of the business partner to the supply chain unit, and creates a supply chain unit (for example, for the customer). In this case, you are not allowed to enter a business partner in the supply chain unit, and not allowed to change this entry. You are not allowed to change a business partner that has already been entered in a supply chain unit, as it is also used by other processes.

SAP Extended Warehouse Management (SAP EWM)

510

205

SAP Online Help

20.07.2007

Avoid multiple assignments, that is, only assign one supply chain unit of one type to a business partner.

If you assign more than one supply chain unit of one type to a business partner, EWM cannot clearly determine the supply chain unit from the business partner. For master data sent that was sent from the ERP system, and for the case where you have created multiple assignments, EWM uses the following method when attempting to find the supply chain unit for the business partner: EWM checks whether an entry with the identification type R/3 Plant (CRM011) exists for the business partner in the business partner master data on the Identification tab page, and whether a supply chain unit exists for this entry. If EWM finds one distinct entry, it uses this supply chain unit. If EWM does not find an assignment, it checks whether an entry with the identification type R/3 Customer Number (CRM002) exists for the business partner on the Identification tab page, and whether a supply chain unit exists for this entry.

If EWM does not find a distinct assignment, it cannot accurately find the routes and issues a message to this effect. You also determine the following for the supply chain unit master data: On the Bus.Char. (business character) tab page, you assign the business character to the supply chain unit as a planning location [Extern]. You have created a ship-to party or an address for a ship-to party. If you do not use addresses in the delivery, you assign the business partner of the ship-to party in the supply chain unit master data of the supply chain unit. If you want to create a ship-to party or an address for a ship-to party, in the SAP Easy Access screen choose Extended Warehouse Management Delivery Processing Outbound Delivery Maintain Outbound Delivery Order or Maintain Outbound Delivery. Specify the ship-to party as the partner role on the Partner tab page or use the Ordering Address pushbutton to specify the ship-to partys address. You specify the geocoordinates and the country key for the supply chain unit of the source location and the ship-to location in the supply chain master data on the General tab page.

SAP Extended Warehouse Management (SAP EWM)

510

206

SAP Online Help

20.07.2007

Executing Automatic Route Determination


Use
Depending on your Customizing settings and various other settings, Extended Warehouse Management (EWM) may be able to execute automatic route determination. This means that you do not need to enter a route manually and route determination determines a new route when data is changed.

Prerequisites
You made the settings for route determination [Seite 205].

Features
If either you or the system change one of the following fields in the delivery header or a delivery item in the delivery, EWM automatically executes new route determination: Delivery Header Changing the route or setting the determination indicator for the route to Initial or Value Determined by System. Changing the means of transport or setting the determination indicator for the means of transport to Initial or Value Determined by System. Change to Delivery Date Changing the final delivery date/time. Changing the warehouse (of the source location). Changing the ship-to party. Changing the final ship-to party. Changing the freight forwarder.

Delivery item

Delivery processing only executes new route determination for those items that are relevant for the route. This means that delivery processing does not execute new route determination for changes to text items, kit items, or items that are not warehouse-relevant. In addition, delivery processing only executes route determination or new route determination for those items that are not yet assigned to an outbound delivery order. Changing the product. Changing the delivery quantity. Changing the shipping conditions. Changing the weight or volume. Changing the planned goods issue date/time. Creating a new delivery item.

SAP Extended Warehouse Management (SAP EWM)

510

207

SAP Online Help

20.07.2007

If you release a route in the delivery manually, EWM does not execute new route determination. EWM also does not check the validity of the route. EWM only executes route checking again when you change a route. If EWM has already scheduled a document for picking, meaning that the status type Picking has a status value in the delivery other than Not Yet Started, EWM does not execute new route determination or set dependent data. It only checks the validity of the route. As soon as you change a route, EWM sets the dependent data once again.

SAP Extended Warehouse Management (SAP EWM)

510

208

SAP Online Help

20.07.2007

Data Use in Route Determination


Route determination uses various data from the delivery, a change in which also triggers new route determination. From the delivery header, route determination uses the supply chain units of the warehouse and the ship-to party, for example. Route determination uses certain delivery-relevant items (see Executing Automatic Route Determination [Seite 207]). Non delivery-relevant items are text or kit items, or items that are not warehouserelevant. Route determination uses the latest planned goods issue date/time of all the relevant items of the delivery as the start date/time for the forward scheduling of route determination. The planned delivery date is used for backward scheduling. If you manually specify the carrier, the route or the means of transport, or if an external system specifies them, route determination uses them as additional constraints. For example, you manually specify the carrier. Route determination determines routes for this carrier only as valid. Using the determination indicator [Extern], route determination identifies whether it automatically determined the field or whether you or an external system specified the field.

When route determination determines a valid route, it copies the following data to the delivery: Route at header level Means of transport at header level Carrier at header level on the Partner tab page (if route determination automatically determined the carrier) Date/time Departure from Yard at header level Delivery date/time at header level Sequence number at header level Export relevance at header level

SAP Extended Warehouse Management (SAP EWM)

510

209

SAP Online Help

20.07.2007

Special Features for Outbound Delivery Objects


Use
Depending on the outbound delivery object, route determination works differently to the function described under Route Determination in the Delivery [Seite 202]. The differences for the individual outbound delivery objects are described below.

Features
Outbound Delivery Request
With route determination in the outbound delivery request, Extended Warehouse Management (EWM) can execute a delivery split in different outbound delivery orders. If you have activated route determination in Customizing, EWM attempts to determine a common route for all delivery items. If route determination determines a common route, the system does not execute a delivery split. If route determination cannot determine a common route, EWM reexecutes route determination. This time, route determination determines one route for every routerelevant delivery item (see Execution of Automatic Route Determination [Seite 207]). If route determination determines varying routes for the delivery items, delivery processing creates an outbound delivery order for each route. In this way, you can, for example, transport heavy and also smaller products in two outbound delivery orders via separate routes within the same outbound delivery request. However, EWM always processes logically corresponding delivery items together (for example, because of Delivery Groups [Extern]).

If you have deactivated route determination in Customizing, or if an external system manually specifies the route, route determination no longer determines the route. Route determination specifies the same route for all delivery items.

Outbound Delivery Order


Route determination in the delivery only finds a route for an outbound delivery order if you do not enter a route manually. If you manually enter a route, delivery processing only checks if the manually entered route is valid. The only exception is route determination in transportation cross-docking (see Route Determination in the Delivery [Seite 202], section Route Determination in Transportation Cross-Docking). Route determination for an outbound delivery order does not take into account any delivery items that are already assigned to an outbound delivery.

Outbound Delivery
Delivery processing copies the route and the route status from the outbound delivery order to the outbound delivery, meaning that it does not execute route determination, nor does it check if the route is valid. As soon as you change delivery item data or delivery header data that is route-relevant, delivery processing checks if the route is valid. If, however, you manually approve the route, delivery processing does not check the route (even with the data change described above). If you change a route in the outbound delivery, route determination only adjusts the dependent data to the outbound delivery header. The dependent data of the delivery items remains unchanged.

SAP Extended Warehouse Management (SAP EWM)

510

210

SAP Online Help

20.07.2007

Route Determination on the User Interface


Use
In addition to the functions described in Route Determination in the Delivery [Seite 202] and Special Features for Outbound Delivery Objects [Seite 210] (outbound delivery), further functions are available on the user interface for the outbound delivery order and the outbound delivery.

Features
Redetermination of Routes
You can execute route determination for one or more deliveries with the Redetermine pushbutton. For example, you can use an earlier or a later route. If you change your route master data, you can also execute route determination with the new master data using this function. With the Departure Date/Time, Lead Time, and Next Trip fields, you have the option of determining that route determination carries out forward scheduling from a start date/time that is different from the default start date/time. If you use the Departure Date/Time field, route determination attempts to find a route or trip [Extern] with this date and time. If you use the Lead Time field, route determination attempts to find a route or trip that occurs after the current Departure from Yard date/time plus the lead time. This is specified in hours. If you use the Next Trip field, route determination attempts to find a route or trip that occurs (in relation to route or trip) directly after the current Departure from Yard date/time.

Note that you can only ever use one of these fields. Delivery processing saves the information (for Extended Warehouse Management (EWM) to use a changed departure date/time) to the delivery in the planned goods issue date/time of the items. A route redetermination also uses this date/time. You can use the Aggregation field to include the total weight of the selected deliveries in route determination. This means that route determination also determines routes that it does not automatically find, for example, because the weight of the individual deliveries is too low. You can use the Set Route to Determined Automatically indicator if route determination is to address routes specified manually or routes specified by an external system in the same way as it addresses routes that it automatically determines. If delivery processing executes a route redetermination, route determination uses the route that was found automatically. If you set this indicator, route determination also sets the determination indicator [Extern] of the route to Determined Automatically.

Assigning Routes
With the Assign pushbutton, you can assign a route to one or more deliveries. Route determination sets the determination indicator of the route to Manual. As described above, you can use the Departure Date/Time, Lead Time, Next Trip, and Aggregation fields, and the Set Route to Determined Automatically indicator.

SAP Extended Warehouse Management (SAP EWM)

510

211

SAP Online Help

20.07.2007

Checking Routes
You can execute a route redetermination with the Check or Check (Aggregated) pushbutton. With this, you check whether route determination has found a result for the delivery. You also check whether the route determination data agrees with the data in the delivery. If you have made changes to the route master data, you can check, for example, whether the routes are still valid. Delivery processing issues a warning message if the route that was found deviates from the route contained in the delivery. In the transportation cross-docking process (TCD process), delivery processing also issues a warning message if the route that was found contains TCD information that the delivery does not contain. For the route check, route determination uses the total weight and total volume of all selected deliveries in the aggregated check.

Manually Releasing Routes


You can manually release a route with the Release pushbutton. You can also manually approve a route with the status Found Invalid. With this, you can work with deliveries that contain an invalid route, for example, if, in an exceptional situation, you want to use a route that is actually invalid for a delivery. Delivery processing blocks a delivery with an invalid route. Then you cannot post the goods issue for this delivery, for example. If you manually approve a route, route determination changes the status of the route to Manually Released. After a manual approval, delivery processing does not execute automatic route determination, since the invalid route would lead to another blocked delivery. You can cancel a manual route approval. You either set the determination indicator to Initial or Value Calculated by System, or you use the Redetermine pushbutton for route redetermination.

You can only manually approve a route if the route status is Found Invalid. If you want to enter a route manually, the determination indicator must not be Value Calculated by System. If you cannot use a route for a delivery because of dangerous goods data, you can force delivery processing to use this invalid route for a delivery using manual route approval. You can use the BAdI default implementation of the Business Add-In (BAdI) /SCWM/EX_DLV_ACT_ROUTE_RELEASE to execute a general check as to whether a user is authorized to manually approve routes. You can implement further checks in the BAdI. Route determination automatically uses dependent data from a valid route determination (see Data Use in Route Determination [Seite 209]). If you manually enter a route that is invalid for the delivery or has no master record, route determination can no longer automatically determine this data. Route determination sets this data to initial. You can manually set this data or use the BAdI /SCWM/EX_DLV_ACT_ROUTE_RELEASE.

SAP Extended Warehouse Management (SAP EWM)

510

212

SAP Online Help

20.07.2007

Connection of Delivery Processing to Serial Numbers


Use
You can use serial numbers in the delivery so that you can document them for the delivery and flag them in goods receipt.

Features
For more information about using serial numbers in the delivery, see Working with Serial Numbers in the Delivery [Seite 590] and Integration of Serial Number in the Delivery [Seite 592].

SAP Extended Warehouse Management (SAP EWM)

510

213

SAP Online Help

20.07.2007

Connection to SAP Global Trade Services (SAP GTS)


Use
You can use the following functions from SAP Global Trade Services (SAP GTS) in Extended Warehouse Management (EWM): Connection of Delivery Processing to Transit Procedure [Seite 215] Connection of Delivery Processing to Safekeeping [Seite 220] Connection of Delivery Processing to Customs Warehousing Procedure [Seite 221] Connection of Delivery Processing to Checks in SAP GTS [Seite 222]

For more information about SAP GTS, see the SAP Library under SAP xAPPs SAP Global Trade Services.

SAP Extended Warehouse Management (SAP EWM)

510

214

SAP Online Help

20.07.2007

Connection of Delivery Processing to Transit Procedure


Use
In Extended Warehouse Management (EWM), you can execute a transit procedure for all transportations that are relevant to transit procedures. Here EWM differentiates between inbound deliveries and outbound deliveries during the processing. EWM saves the previous document number together with its previous document type as the reference document number and category in the delivery document. Delivery processing uses these to recognize that an inbound delivery is relevant to transit procedures or to customs blocked stock. For more information, see Transit Procedure for Inbound Deliveries [Seite 216] and Transit Procedure for Outbound Deliveries [Seite 218].

SAP Extended Warehouse Management (SAP EWM)

510

215

SAP Online Help

20.07.2007

Transit Procedure for Inbound Deliveries


Purpose
In Extended Warehouse Management (EWM), you can subject complete inbound deliveries that are transit procedure relevant to a transit procedure. In doing so, you can ensure that the customs authority issues an unloading permission for the vehicles with the goods to be delivered.

Prerequisites
You have defined reference document categories in Customizing for EWM under Cross-Process Settings Delivery Processing Reference Documents Define Reference Document Categories. You have assigned these reference document categories that correspond to the previous document types you use to a transit procedure and have set the TrsPrcRel (transit procedure relevance) indicator. You do this in Customizing for EWM under Interfaces GTS Integration Define Previous Document Types.

Process
...

1. In the case of inbound deliveries that are relevant to transit procedures, you find the previous document number [Extern] and previous document type in the transportation papers for the vehicle. You enter these manually in the inbound delivery as the reference document number and reference document category. The ERP system can also send an advanced shipping notification to EWM that already contains the previous document number and previous document type. In this case, you can change the previous document number and previous document type in the user interface. 2. Based on the Customizing settings for the previous document type, EWM determines that the reference document number is a previous document number for which EWM must perform a transit procedure. 3. EWM locks the inbound delivery to prevent additional goods receipt process steps [Seite 263] from being performed, for example, posting goods receipt. 4. If the status type Transit Status does not have the status value Registered in Yard, you set this status manually. By doing so, you ensure that EWM informs SAP Global Trade Services (SAP GTS) [Seite 214] about the inbound delivery. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Inbound Delivery Maintain Inbound Delivery and then the In Yard pushbutton. In the dropdown menu, choose Set Status. 5. EWM informs SAP GTS that an inbound delivery exists for which it must perform a transit procedure. 6. On the basis of this message, SAP GTS performs an EDI communication with the customs authority. SAP GTS asks the customs authority whether it is permitted to unload the vehicle. The customs authority sends a corresponding message to SAP GTS. If the customs authority allows the vehicle to be unloaded, SAP GTS sends a notification of the unloading permission to EWM. EWM sets the status type Transit Procedure of the inbound delivery to the status value Released and unlocks the inbound delivery for additional goods receipt process steps. If the customs authority does not allow the vehicle to be unloaded because it is performing a customs inspection, unloading is delayed.

SAP Extended Warehouse Management (SAP EWM)

510

216

SAP Online Help

20.07.2007

After the customs inspection, SAP GTS sends a notification with the unloading permission to EWM. EWM sets the status type Transit Procedure of the inbound delivery to Released and unlocks the inbound delivery for additional goods receipt process steps.

You can only unload the vehicle and post goods receipt if the inbound delivery has the status value Not Relevant or Released for the status type Transit Procedure. 7. EWM informs the ERP system about the previous document number that you might have changed (see step 1).

Result
You have performed a transit procedure for your inbound delivery. You unload the vehicle and perform additional goods receipt process steps, for example, you post the goods receipt. See also: Loading and Unloading [Seite 608]

SAP Extended Warehouse Management (SAP EWM)

510

217

SAP Online Help

20.07.2007

Transit Procedure for Outbound Deliveries


Purpose
In Extended Warehouse Management (EWM), you can subject complete outbound deliveries that are transit procedure relevant to a transit procedure. In doing so, you can ensure that the customs authority issues a loading permission for the vehicles with the goods to be delivered to the goods recipient.

Prerequisites
You have implemented the enhancement spot /SCWM/ES_GTS_INTEGRATION, as required, to determine the transit procedure relevance.

Process
...

1. Before you load a vehicle for an outbound delivery, you define whether this outbound delivery is relevant to a transit procedure. As the default value, EWM uses the status type Transit Procedure with the status value Not Relevant. You can use the BAdI /SCWM/SHP_PROC_REL_SET to define, for example, that all deliveries for a certain country are relevant to a transit procedure. For more information, see the BAdI documentation. 2. You set the status type Transit Procedure of the outbound delivery to the status value For Checking. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery Maintain Outbound Delivery and then the Transit Procedure pushbutton. In the dropdown menu, choose Set Status to Check. 3. EWM locks the outbound delivery to prevent additional goods issue process steps [Seite 314] from being performed, for example, posting the goods issue. 4. You ask the customs authority for loading permission. If the customs authority allows the vehicle to be loaded, you set the status type Transit Procedure of the outbound delivery in EWM to the status value Released. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery Maintain Outbound Delivery and then the Transit Procedure pushbutton. In the dropdown menu, choose Set Status to Release. EWM releases the locked outbound delivery for additional goods issue process steps. If the customs authority does not allow the vehicle to be loaded because it is performing a customs inspection, loading is delayed. You can set the status type Transit Procedure of the outbound delivery to the status value Customs Insp.. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery Maintain Outbound Delivery and then the Transit Procedure pushbutton. In the dropdown menu, choose Set Status to Blocked for Customs. After the customs inspection, you set the status type Transit Procedure of the outbound delivery in EWM to the status value Released. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery Maintain Outbound Delivery and then the Transit Procedure pushbutton. In the dropdown menu, choose Set Status to Release. EWM releases the outbound delivery for additional goods issue process steps.

SAP Extended Warehouse Management (SAP EWM)

510

218

SAP Online Help

20.07.2007

You can only load the vehicle and post the goods issue if the outbound delivery has the status value Not Relevant or Released for the status type Transit Procedure.

Result
You have performed a transit procedure for your outbound delivery. You load the vehicle and perform additional goods issue process steps, for example, you post the goods issue. See also: Loading and Unloading [Seite 608]

SAP Extended Warehouse Management (SAP EWM)

510

219

SAP Online Help

20.07.2007

Connection of Delivery Processing to Safekeeping


Use
You can use safekeeping [Seite 962] for inbound deliveries in delivery processing.

Delivery processing decides whether a delivery item is relevant to customs procedures on a product-independent basis. The most important aspect is whether the combination of previous document number and previous document type is relevant to customs procedures. This is not dependent on whether the product itself is managed in the customs warehouse.

Prerequisites
You have performed Customizing for the transit procedure [Seite 216] in Extended Warehouse Management (EWM). You have set the Customs Block indicator in Customizing for EWM under Extended Warehouse Management Interfaces GTS Integration Define Previous Document Types. As a result, you have defined that the previous document type is relevant to customs blocked stock. If you want to define a customs block for certain previous document types, you must define stock types with the role Customs Blocked Stock in Customizing for EWM under Extended Warehouse Management Master Data Product Define Stock Types.

Features
EWM copies the previous document number and previous document type from the ERP system before you post goods receipt for an inbound delivery. If there is no previous document number or previous document type in the ERP system, you can specify both directly in the delivery document in EWM. If the previous document type is relevant to customs blocked stock [Extern], EWM posts the stock to a stock type for customs block stock. Otherwise, EWM posts the stock to a different stock type, for example, F1 Unrestricted Use in Putaway. You can put away stock in a normal way in spite of a customs block.

If you change the previous document number or previous document type again before posting goods receipt, EWM automatically changes the stock type. If you have posted the first (partial) goods receipt or EWM has created a warehouse task (unloading warehouse task or putaway warehouse task), you cannot change the previous document number or previous document type in the delivery. If a product is subject to a batch management requirement and is relevant to customs warehousing, you must specify a country of origin in the delivery for goods receipt posting.

SAP Extended Warehouse Management (SAP EWM)

510

220

SAP Online Help

20.07.2007

Connection of Deliv. Proc. to the Customs Warehousing Procedure


Use
If you use the customs warehousing procedure [Seite 964] in Extended Warehouse Management (EWM), the only effect that you have on delivery processing is in the scrapping area. If you work with posting change requests [Seite 128] for scrapping in the scrapping process in the customs warehouse [Seite 965], SAP Global Trade Services (SAP GTS) can apply to the customs authority for permission to scrap.

Prerequisites
For a description of the prerequisites for using the customs warehousing procedure in EWM, see Customs Warehousing Procedure [Seite 964]. You have defined a reference document category SCR Reference Number Scrap in Customizing for EWM under Extended Warehouse Management CrossProcess Settings Delivery Processing Reference Documents Define Reference Document Categories.

Features
When the ERP system sends a posting change delivery for a scrapping to delivery processing, delivery processing automatically creates a posting change request for scrapping, or you do this manually. Delivery processing also checks whether the product in this posting change request is relevant to customs warehousing. If the product is relevant to customs warehousing, delivery processing requests a scrapping reference number from SAP GTS. If SAP GTS sends this number immediately, delivery processing continues to process the posting change request for scrapping. If SAP GTS does not send this number immediately, delivery processing locks the posting change request to prevent further processing, for example, warehouse task creation. SAP GTS asks the customs authority for permission for the scrapping. As soon as SAP GTS gets this permission, it sends the scrapping reference number to delivery processing. Delivery processing unlocks the posting change request and continues with the processing.

If the product is not relevant to customs warehousing, delivery processing immediately continues to process the posting change request.

See also: Performing Scrapping [Seite 130]

SAP Extended Warehouse Management (SAP EWM)

510

221

SAP Online Help

20.07.2007

Connection of Delivery Processing to Checks in SAP GTS


Purpose
Extended Warehouse Management (EWM) uses the compliance check and letter of credit check from SAP Global Trade Services (SAP GTS) to check whether an outbound delivery can be delivered to a certain goods recipient. The connection to SAP GTS means you can make use of the following checking criteria for your deliveries: Checking criteria for the compliance check: Sanctioned Party List [Extern] Embargos, for example, no exports from the USA to Cuba Legal control, meaning licenses For example, a product is only allowed to be exported in a certain quantity and to a certain goods recipient. Letter of credit check: Check for whether letter of credit is still valid

The system performs the checks in the following cases: When you or EWM generate an outbound delivery order. If EWM changes certain fields in an outbound delivery order or outbound delivery, or you manually change certain fields (for example, address, partner, or delivery quantity) in an outbound delivery, EWM checks the outbound delivery order or the outbound delivery. If you determined in Customizing that the outbound delivery is relevant for the legal control, EWM checks the outbound delivery before goods issue.

Prerequisites
In Customizing, you can define the item types for which EWM is to perform the checks: Define a status profile for the checks, and do not set the Inactive indicator for the corresponding status type DGT GTS check. For more information, see the Implementation Guide (IMG) for EWM under Cross-Process Settings Delivery Processing Status Management Define Status Profile. Assign this status profile to an item type. For more information, see the IMG for EWM under Goods Issue Process Outbound Delivery Define Position Types for Outbound Delivery Process Using Wizard .

If you want the system to check outbound deliveries before goods issue, you must set the LegConGTS (GTS Compliance Check: Document Types Relevant for the Legal Control) indicator. To do so, in Customizing for EWM choose Goods Issue Process Outbound Delivery Define EWM-Specific Settings for Document Types.

In the outbound delivery, a letter of credit number from the preceding document exists as a reference document. Only in this instance does EWM perform a letter of credit check.

SAP Extended Warehouse Management (SAP EWM)

510

222

SAP Online Help

20.07.2007

If you are working with direct outbound delivery orders [Seite 167], no data from a preceding document, such as an ERP outbound delivery, is available. As EWM requires the sales organization, you can define it in Customizing for EWM for the corresponding checks. To do so, in Customing for EWM choose Interfaces GTS Integration Assign Sales Organization to Warehouse Number. You can also specify the sales organization manually onthe user interface for the outbound delivery order.

Process
...

1. EWM prepares the data in the outbound delivery for checks and calls SAP GTS. In the standard system, EWM calls the checks for both outbound delivery orders and for outbound deliveries.

If you are working with direct outbound delivery orders, no data from a preceding document is available in EWM. For this reason, EWM performs restricted checks only. EWM does not perform a letter of credit check or a check for licenses for direct outbound delivery orders. If you are working with kit to stock, EWM does not perform any checks in SAP GTS. 2. SAP GTS performs the checks and returns a status. If SAP GTS checks for the outbound delivery order contain errors, SAP GTS returns the relevant status. EWM sets the status GTS Check/Technical Error or GTS Check/Check, NotOK, and does not create an outbound delivery for this outbound delivery order. If SAP GTS checks for the outbound delivery contain errors, SAP GTS returns the relevant status. EWM sets the status GTS Check/Technical Error or GTS Check/Check, NotOK, and does not permit a goods issue posting for this outbound delivery.

If you have the required authorization, you can remove a GTS lock. However, we recommend that you accept the decision from SAP GTS to avoid corrupting any check criteria. If, as an administrator, you want to reset a GTS lock, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery Maintain Outbound Delivery. For more information about SAP GTS, see the SAP Library under SAP xAPPs SAP Global Trade Services. If you use SAP Customer Relationship Management (SAP CRM), you can perform the checks for the corresponding sales order there. To do so, set the GTS Relevance indicator for the transaction type and the item type in Customizing for CRM. For example, you perform these steps for the business transaction category Sales. For more information, see the IMG under Customer Relationship Management Transactions Basic Settings Define Transaction Type or Define Item Type. If you require the checks in your scenario, we recommend that you perform it in both systems (EWM and CRM), or you do not perform it in either system.

SAP Extended Warehouse Management (SAP EWM)

510

223

SAP Online Help

20.07.2007

Connection of Deliv. Processing to Determining Country of Origin


Purpose
You can define the country of origin of your goods in Extended Warehouse Management (EWM). If you specify a batch, for example in the ERP System, EWM looks for the stock for the outbound delivery of this batch. This enables you to have EWM only use stock from a particular country of origin. This process applies for both inbound and outbound delivery. For the inbound delivery, EWM books in the stock, and for the outbound delivery it looks for the relevant stock.

Prerequisites
Since the information about the country of origin is found at batch level, the process described can only occur with products subject to batch management requirements.

Process
SAEWM ...

1. The ERP System sends EWM an inbound or outbound delivery with associated product information, such as batch information. The following diagram illustrates that by using an appropriate master data distribution, EWM has access to the same information as the ERP System.

ERP System
Inbound / Outbound Delivery Product XYZ Batch 123 Country of Origin IT Shelf Life Expir. Date Dec. 30, 2004 IT = Italy

EWM
Inbound / Outbound Delivery Product XYZ Batch 123 Country of Origin IT Shelf Life Expir. Date Dec. 30, 2004

2. EWM activates the inbound delivery notification or outbound delivery request according to your settings in Customizing. When the inbound delivery notification is activated, EWM generates an inbound delivery, and when the outbound delivery request is activated, it generates an outbound delivery order. At the same time, EWM checks whether the product is subject to batch management requirements, in other words, whether you have set the batch management requirement indicator in the ERP System. EWM checks whether the batch information also contains information about the country of origin. EWM copies this information to the delivery item of the inbound or outbound delivery. If no information about the country of origin is available, EWM does not copy anything to the delivery items. EWM keeps the stock separated according to batches (country of origin). 3. You post the goods receipt or goods issue.

Results
EWM has saved the information about the country of origin as a batch characteristic.

SAP Extended Warehouse Management (SAP EWM)

510

224

SAP Online Help

20.07.2007

SAP Extended Warehouse Management (SAP EWM)

510

225

SAP Online Help

20.07.2007

Connection of Delivery Processing to Post Processing Framework


Use
In delivery processing, you use the Post Processing Framework (PPF) to be able to schedule and control actions and messages for processing warehouse requests.

For more information, see Post Processing Framework in Delivery Processing [Seite 105].

SAP Extended Warehouse Management (SAP EWM)

510

226

SAP Online Help

20.07.2007

Configuration of PPF Action Scheduling


Use
You can configure the scheduling of Post Processing Framework actions (PPF actions) in the PPF application /SCDL/DELIVERY. To do this, you define schedule conditions that use the condition technique. The condition technique works with condition records that control the scheduling of the PPF actions Creating Condition Records [Seite 229]).

Prerequisites
You have defined a schedule condition for the PPF action that contains the call of method /SCWM/CL_DLV_PPF_CONF=>EVALUATE. For more information, see the method documentation. For more information about the PPF, see the SAP Help Portal help.sap.com under SAP NetWeaver SAP NetWeaver Library SAP NetWeaver by Key Capability Application Platform by Key Capability Business Services Business Communication Services Generic Business Tools for Application Developers (BC-SRV-GBT) Post Processing Framework (BC-SRVGBT). You have made the following settings for the condition technique in Customizing for Extended Warehouse Management (EWM): a. Create field catalog b. Create condition tables c. Create access sequences d. Create condition types e. Maintain determination procedure f. Assign determination procedure g. Create condition maintenance group h. Register condition maintenance group For more information, see the Implementation Guide (IMG) for EWM under CrossProcess Settings Delivery Processing Actions Configure Action Scheduling.

...

Features
Within the PPF application /SCWM/DELIVERY, you can schedule the PPF action with the Business Add-In (BAdI) EVAL_SCHEDCOND_PPF PPF: Configure Exit for Evaluating Schedule Condition. In this action, you can define conditions that use certain delivery data. For example, you can define that EWM is only to schedule a PPF action if warehouse 001 or partner ABC is affected or if the delivery status has the value Finished. When PPF checks the PPF action to be scheduled, the system uses this configuration. You call method /SCWM/CL_DLV_PPF_CONF=>EVALUATE in your BAdI implementation for the schedule condition for the PPF action. The method returns the return code RV_RC to the schedule condition. The value zero means that a result was found. Other values indicate various error messages. The schedule condition also returns a return code to the PPF. The value zero means that the schedule condition is fulfilled and that the PPF has scheduled the PPF action. Condition record determination in delivery processing only returns the result of whether a condition record was found or not. You cannot specify any values that condition record determination then returns as a results record together with the condition record.

SAP Extended Warehouse Management (SAP EWM)

510

227

SAP Online Help

20.07.2007

SAP provides a default field catalog that contains fields from the delivery document header only and that defines delivery data that you can use in the schedule condition. An exception is the Door field. EWM aggregates this field on header level. If the value in this field is the same for all items, EWM copies the value to the header level too. If the value in this field differs for at least one item, the value for the header field remains empty. You can either use the fields from the default field catalog or you can add your own fields to the field catalog. To fill these additional fields at runtime, you can use BAdI /SCWM/EX_DLV_PPF_CONF BAdI: Determine Delivery Data for Customer-Defined Condition Record Fields. You can also add item fields to the default field catalog. For more information about special fields in the field catalog for the application DPP, see the corresponding field help, for example, for the field /SCWM/DE_DPP_ITEM_REL.

Due to performance reasons, you cannot use placeholders for the values in the condition records. If you want to define a schedule condition for a status value that has not yet been defined in the system, you must define a condition record for each possible combination of status change, for example, Not Started -> In Process.

Activities
If you want to define the configuration of scheduling of PPF actions, perform the IMG activities in the sequence specified under Prerequisites in the Implementation Guide (IMG) for EWM under Cross-Process Settings Delivery Processing Actions Configure Action Scheduling. If you want to view or edit schedule conditions for PPF actions, in the IMG for EWM, choose Cross-Process Settings Delivery Processing Actions Change Actions and Conditions Define Conditions. If you want to edit condition records for the schedule condition of a PPF action, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Actions Maintain Condition Records for PPF Schedule Conditions. If you want to view and edit PPF actions, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Actions Process and Display PPF Actions.

SAP delivers PPF actions whose schedule condition already contains the call of the configuration. The system therefore behaves as follows: If you do not assign a determination procedure in Customizing for SAP EM, the system behaves as in SAP SCM 5.0 with regard to these actions. If you assign a determination procedure that matches a delivery, you must also perform all the Customizing settings described under Prerequisites and you must create a suitable condition record. Only if you do this are the schedule conditions fulfilled for the actions for this delivery.

SAP Extended Warehouse Management (SAP EWM)

510

228

SAP Online Help

20.07.2007

Creating Condition Records


Use
You can use condition records to control how the system schedules Post Processing Framework actions (PPF actions) for delivery processing. The following section describes how you can create condition records to influence the planning of PPF actions in the delivery process.

Prerequisites
See Configuration of PPF Action Scheduling [Seite 227].

Procedure
...

1. On the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Actions Maintain Condition Records for PPF Schedule Conditions (/SCWM/DLVPPFC). 2. Specify the application DPP and the maintenance group that you have defined in Customizing. Choose with the quick info text Execute. 3. In the Condition Type field, use the input help to select a condition type. 4. Complete the fields in the condition record and save. Here, one table row corresponds to one condition record.

For more information about special fields in the field catalog for the application DPP, see the long text of the corresponding field help, for example, for the field /SCWM/DE_DPP_ITEM_REL.

Result
You have created a new condition record.

If a PPF action for the delivery contains the call of method /SCWM/CL_DLV_PPF_CONF=>EVALUATE in the schedule condition, it has the following effect on the scheduling of the PPF action: If the system finds a suitable condition record for a PPF action, it schedules the PPF action since the delivery corresponds to all the delivery data in the condition record. If the system does not find a suitable condition record for a PPF action, it does not schedule the PPF action since the delivery does not correspond to all the delivery data in the condition record. Moreover, the system does not display the PPF action on the user interface for the delivery.

SAP Extended Warehouse Management (SAP EWM)

510

229

SAP Online Help

20.07.2007

Connection to Value-Added Service Order (VAS Order)


Purpose
You can document the value-added services that you are providing in your warehouse using a value-added service order [Extern] (VAS order).

Process
You can either generate a VAS order manually [Seite 536], or have Extended Warehouse Management (EWM) generate one automatically (see also Generating a VAS Order for the Warehouse Request Item Automatically [Seite 231])

SAP Extended Warehouse Management (SAP EWM)

510

230

SAP Online Help

20.07.2007

Automatic Generation of a VAS Order for the Warehouse Request Item


Purpose
You can generate value-added service orders [Extern] (VAS orders) automatically in Extended Warehouse Management (EWM) to document and monitor these value-added services.

Prerequisites
You have defined in your system that you want EWM to create VAS orders automatically. For more information, see the Implementation Guide (IMG) for EWM under Cross-Process Settings Value-Added Services Define Relevance for VAS Order. You have defined a packaging specification [Seite 494].

Process
...

1. You get a delivery from the ERP system or create a delivery manually. 2. EWM checks whether it has to generate a VAS order automatically, and does so if this is the case. In the goods receipt process, you can configure automatic generation of VAS orders in such a way that EWM does not generate the VAS order until the goods receipt is posted. If you have defined in Customizing that EWM is not to generate the VAS order automatically, then the VAS Order status has the value Not Relevant. 3. EWM saves the number of the VAS order as a document flow for the warehouse request item. 4. If you have activated the VAS Order in the status profile of the item type for the warehouse request item, EWM sets the VAS Order status of the warehouse request item to Generated.

Result
EWM has automatically generated the VAS order. You can use it for the confirmation of services [Seite 538]. When you edit the VAS order, EWM changes the status VAS order of the warehouse request item (see also: Updating the Warehouse Request Using the VAS Order [Seite 232]).

SAP Extended Warehouse Management (SAP EWM)

510

231

SAP Online Help

20.07.2007

Updating the Warehouse Request Using the VAS Order


Purpose
When you edit a value-added service order [Extern] (VAS order) in Extended Warehouse Management (EWM), EWM updates the warehouse request item where required. For example, if the status of the VAS order changes, EWM updates the warehouse request item.

Prerequisites
In the Implementation Guide (IMG) for EWM under Cross-Process Settings Delivery Processing Status Management Define Status Profiles, you have activated the status DWV in the respective status profiles, that is, for the status profiles of the item types for which you want to update the warehouse request. In the standard SAP system for example, these are profiles /SCWM/OUT_PRD_DLV_STANDARD and /SCWM/INB_PRD_DLV_STANDARD.

Process
...

Changing a VAS Order 1. You edit the VAS order and with that change the status of the VAS order [Seite 538]. 2. EWM automatically adjusts the VAS Order status of the warehouse request item: If you set the status of the VAS order to In Process, EWM also changes the VAS Order status to In Process. If you set the status of the VAS order to Completed or Completed with Quantity Variance, EWM sets the VAS Order status to Completed.

Deleting a VAS Order


...

1. You delete the VAS order. 2. EWM deletes the document flow for the warehouse request item, and sets the VAS Order status to Relevant. If required, you can generate a new VAS order [Seite 536] manually.

SAP Extended Warehouse Management (SAP EWM)

510

232

SAP Online Help

20.07.2007

Updating the VAS Order Using the Warehouse Request


Purpose
When you change a warehouse request item in Extended Warehouse Management (EWM), EWM also changes the value-added service order [Extern] (VAS order) correspondingly, if required.

Prerequisites
A VAS order exists for the warehouse request item. If you change a warehouse request, and you want EWM to update the status of the relevant VAS order, the VAS order must be completed and the VAS Order status of the delivery item must have the value Completed.

Process
Changing the Warehouse Request
...

If you increase the delivery quantity of a warehouse request item, EWM updates the VAS order. If the VAS Order status currently has the value Completed, EWM changes the status of the VAS order from Completed back to In Process, and changes the VAS Order status of the warehouse request item back to In Process. If you reduce the delivery quantity of a warehouse request item, EWM does nothing. Deleting the Warehouse Request
...

1. You delete an item of a warehouse request for which a VAS order exists.

You can only delete a warehouse request item if the VAS order is not yet in process. 2. If the VAS order is not yet in process, EWM deletes the VAS order.

SAP Extended Warehouse Management (SAP EWM)

510

233

SAP Online Help

20.07.2007

Kit in the Warehouse Request for the Outbound Delivery Order


Definition
Describes a piece list that you always deliver in a complete and assembled form.

Use
Extended Warehouse Management (EWM) uses kits in kitting [Seite 349]. In EWM, the kit information in the outbound delivery forms the basis for kitting.

EWM can only receive information about kits in outbound deliveries. EWM does not support nested kits, that is, kits in kits.

Structure
The outbound delivery contains the following items as kit information, corresponding to the levels of a kit: Kit Header Item [Extern] Kit Component Item [Extern] The kit header item is a direct predecessor of this item. Replaced kit component item [Extern] The kit header item is a direct predecessor of this item, and the kit component item is in turn a subitem of this item. SAP delivers preconfigured item types as standard for these kit items. You can use these to individually control the kit items in an outbound delivery.

If you want to change the settings of the preconfigured item types, you must note the following regarding the profiles. We recommend that you use the standard profiles shipped by SAP. You must make sure that the status profile for the item type of the kit header and of the replaced kit components prevents them from being considered in warehouse processing. For example, you must therefore deactivate the picking relevance and the goods movement relevance. You must configure the quantity offsetting profile of the kit header and of the replaced kit components so that EWM does not calculate any open quantities for picking or goods issue, for example. This means that you must set the corresponding quantity roles in this quantity offsetting profile to inactive.

When EWM generates a warehouse request with kit items, it checks the settings of the item types of the kit header items and of the replaced kit component items. If you follow the settings for the status profile and the quantity offsetting profile, EWM generates these items without an error status and considers these items in warehouse processing.

SAP Extended Warehouse Management (SAP EWM)

510

234

SAP Online Help

20.07.2007

For more information about settings for kits in the delivery, see the Implementation Guide (IMG) for EWM under Goods Issue Process Make Settings for Kitting, section Requirements. If you change the quantities of a kit component item in EWM through a pick denial, for example, EWM recalculates the quantities of the other kit component items and of the kit header item (quantity correlation).

Make sure that the ERP system always sends EWM information about entire kits. That is, the quantities of the kit components must be enough to create entire kits, otherwise the delivery quantity correlation [Seite 238] returns incorrect results. A kit header item and its related subitems can be part of a delivery group [Extern] together with other delivery items. This enables you to be sure that EWM only ships the kit together with the other delivery items.

Integration
Integration with the ERP system EWM receives information about the kit as part of the outbound delivery from the ERP system. The ERP system also saves the kit as items in the outbound delivery (see also Kit to Order [Seite 349]). Integration with value-added service orders (VAS orders) You can create a VAS order for the kit header item. EWM copies the kit component items into the VAS order as items (see also VAS Order for the Kit Header Item of the Warehouse Request [Seite 356]). Integration with warehouse processing Warehouse processing in EWM handles kit component items in the same way as outbound delivery items, in other words, you can pick, pack, and load them.

SAP Extended Warehouse Management (SAP EWM)

510

235

SAP Online Help

20.07.2007

Outbound Delivery Split for Kits


Purpose
You can split kit header items in warehouse requests for outbound delivery orders to then copy the entire kit to an outbound delivery. You perform an item split, for example, if you want to ship finished kits before the remaining kits have been completed. The process flow is the same as for standard outbound delivery items. However, Extended Warehouse Management (EWM) supports you, for example, by calculating the kit component quantities automatically (see Delivery Quantity Correlation for Kits [Seite 238]).

You can only split entire kits. You cannot split kit component items or replaced kit component items. You cannot perform a batch split for the kit header item or a replaced kit component item.

Prerequisites
An outbound delivery with kit header items and kit component items exists. The quantity of the kit header item is greater than one. All kit component items are completely picked. If the system is to automatically generate an HU item for the kit header in the pickhandling unit (pick-HU), set the Create Kit Header Item indicator in Customizing. For more information about the packing profile, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Issue Process Outbound Delivery Define EWM-Specific Settings for Item Types.

Process
Item Split for Unpacked Kits
...

1. You select the warehouse request for the outbound delivery order. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery Maintain Outbound Delivery Order. 2. You select the kit header item and split the warehouse request for the outbound delivery order. To do this, first choose Subitem and the Split Up Outbound Delivery. 3. You specify the number of kit header items that are to be generated. 4. EWM copies the kit, that is, it generates new kit header items and kit component items that are the same as the original kit in EWM. 5. You specify the delivery quantity in the kit header items and confirm your entries by choosing ENTER. 6. EWM calculates the kit component quantities automatically (see Delivery Quantity Correlation for Kits [Seite 238]). 7. You can copy each of the split kits to one separate outbound delivery.

Item Split for Packed Kits


...

1. You select the warehouse request for the outbound delivery order. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery Maintain Outbound Delivery Order.

SAP Extended Warehouse Management (SAP EWM)

510

236

SAP Online Help

20.07.2007

2. You choose the HU tab page and select all the HUs that you want to ship in advance. 3. You create new split items. To do this, first choose Split Item and then Create. 4. EWM aggregates the quantities of the packed kits using the HU dummy item. 5. EWM copies the kit, that is, it generates new kit header items and kit component items matching the original kit in EWM and automatically sets the quantities in these new kit items. 6. You can now copy the split kit to one separate outbound delivery.

Results
You have performed an outbound delivery split and generated split kits. You can ship these kits by generating an outbound delivery for each of the new kit header items.

SAP Extended Warehouse Management (SAP EWM)

510

237

SAP Online Help

20.07.2007

Delivery Quantity Correlation for Kits


Use
If you or the system make changes to the delivery quantity, Extended Warehouse Management (EWM) recalculates the delivery quantity changes for the following items: Kit header items Kit component items Batch subitems Subitems occurring through substitution

EWM uses the delivery quantities to calculate the additionally required delivery quantities, for example, for creating warehouse tasks belonging to the kit. EWM derives open delivery quantities for these additional delivery quantities.

Integration
When calculating the delivery quantity ratios, EWM always bases its calculation on the current delivery quantity ratios between kit header item and kit component items. The original delivery quantity structure, that is, the delivery quantities with their hierarchical dependencies, are already saved in the delivery in the ERP system. The ERP system sends this data to EWM. Either you or the system can execute a batch split for kit component items. If you or the system have already executed this batch split in the ERP system, the system also sends the resulting batch subitems to EWM.

Prerequisites
For EWM to be able to process kits correctly with their hierarchy [Extern], you must have configured the item types for the relevant delivery items appropriately in Customizing. For example, in Customizing, you define the field control profile in such a way that the field cannot be modified for the delivery quantity. For more information, see the Implementation Guide (IMG) for EWM under Cross-Process Settings Delivery Processing Field Control Define Field Control Profiles.

Features
When EWM performs a split, or when you manually change a delivery quantity for a kit header item, EWM recalculates the delivery quantities of all delivery items belonging to the kit. EWM calculates the delivery quantities for new and changed kit header items and kit component items. When EWM performs a pick denial, or when you manually change a delivery quantity for a kit component item, EWM recalculates the delivery quantities from bottom to top through the hierarchy levels.

When EWM recalculates the delivery quantities for kit header items, it may be the case that EWM also recalculates the delivery quantities for the related kit component items that neither you nor EWM changed. You can use Business Add-In (BAdI) /SCWM/EX_DLV_DET_HIER_CORR to influence the results of the delivery quantity correlation at a later time. For example, you can adjust items with fixed quantities or discount in kind on a quantity basis, depending on other items.

SAP Extended Warehouse Management (SAP EWM)

510

238

SAP Online Help

20.07.2007

EWM considers the process code in the delivery quantity correlation.

You have a kit component item 10 for product A with a delivery quantity of 10 pieces. This delivery item 10 consists of batch subitem 15 for batch 1 with 6 pieces, and batch subitem 17 for batch 2 with 4 pieces. During picking, you notice that batch 2 only contains 2 pieces. You perform a pick denial and specify the process code QTY-2. Since the delivery quantity for batch 2 cannot be fulfilled, EWM also adjusts the delivery quantity of the kit component item, and sets the corresponding process code for the missing delivery quantity.

Delivery Quantity Recalculation for the Delivery Split


When you or the system perform a delivery split for a kit header item, EWM calculates and distributes the kit quantities contained in this original kit proportionately across the new kits that have been split up. When you perform the delivery split manually on the user interface, you only have to enter the delivery quantity of the split kit header items. The delivery quantity correlation then automatically calculates the delivery quantities of all other subitems.

Delivery Quantity Recalculation for the Batch Split


When you perform a charge split manually on the user interface prior to picking, or when EWM performs a batch split automatically, EWM performs a corresponding delivery quantity correlation. Here, EWM ensures that the total of the batch subitem delivery quantities is not greater than the delivery quantity of the split kit component item. If the total is the same in the batch split, the delivery quantity is not changed. If the total is less in the batch split, the delivery quantity is again not changed. However, EWM does not distribute the delivery quantity across all batch subitems. This enables you or the system to add additional batch subitems at a later time. If the total is greater in the batch split, the delivery quantity of the batch subitems is changed corresponding to the delivery quantity.

You have a kit component item 10 with batch subitems 65 and 67. The requested delivery quantity of the kit component item is 5. Batch subitem 65 contains a delivery quantity of 2 and batch subitem 67 contains a delivery quantity of 3. You enter a delivery quantity of 4 for both batch subitems. EWM leaves the delivery quantity for batch subitem 65 as 4, but changes the delivery quantity of batch subitem 67 to 1. This fulfils the requested delivery quantity of 5. When you perform a pick denial at batch item level, EWM first recalculates at the level of the kit component item. The correlation function then calculates the delivery quantity of the kit header item. EWM then recalculates the delivery quantities for all kit component items across the hierarchy levels, from top to bottom. When you reduce the delivery quantity of a kit header item, EWM also reduces the delivery quantities of the related kit component items. If these items also contain batch subitems, EWM also recalculates the delivery quantities (such as open pick delivery quantities) for these across all hierarchy levels, from top to bottom.

Recalculation for Delivery Quantity Changes from External Systems


For requests for delivery quantity changes from external systems, EWM expects the delivery quantity correlation to have already been performed in the external system. For this reason, EWM does not recalculate the delivery quantities.

Activities
You can trigger delivery quantity changes that lead to a delivery quantity correlation by:

SAP Extended Warehouse Management (SAP EWM)

510

239

SAP Online Help

20.07.2007

Directly changing the delivery quantity field on the user interface: On the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Inbound Delivery Maintain Inbound Delivery and then choose the Quantity column on the Items tab page. Change the delivery quantity. On the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery Maintain Outbound Delivery Order and then choose the Quantity column on the Items tab page. Change the delivery quantity. On the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery Maintain Outbound Delivery and then choose the Quantity column on the Items tab page. Change the delivery quantity.

Changing the delivery quantity in the pick denial [Seite 327] Changing the delivery quantity using the delivery quantity adjustment [Seite 147] function Either you choose Adjust Delivery Quantity on the user interface, or EWM changes the delivery quantities when the system updates a delivery in the background.

Performing delivery splits [Seite 236] Either you perform a delivery split manually on the user interface, or EWM changes the delivery quantities when the system updates a delivery in the background.

Example
The following figure shows you the hierarchy for a kit in the ERP system together with the respective delivery quantities.

SAP Extended Warehouse Management (SAP EWM)

510

240

SAP Online Help

20.07.2007

You have a delivery item 10 for the kit header with a delivery quantity of 2 pieces. Delivery item 10 consists of kit component items 20 and 30 and delivery item 40 for the replaced kit component. Kit component item 20 for kit component 1 has a delivery quantity of 10 pieces, kit component item 30 for kit component 2 has a delivery quantity of 20 pieces, and delivery item 40 for the replaced kit component has a delivery quantity of 20 pieces. Kit component item 20 consists of batch subitems 25 and 27. Batch subitem 25 for batch 1 has a delivery quantity of 6 pieces, and batch subitem 27 for batch 2 has a delivery quantity of 4 pieces. Replaced kit component item 40 consists of delivery items 50 and 60. Kit component item 50 for kit component 3 has a delivery quantity of 5 pieces, and kit component item 60 for kit component 4 has a delivery quantity of 15 pieces. Kit component item 60 consists of batch subitems 65 and 67. Batch subitem 65 for batch 3 has a delivery quantity of 2 pieces, and batch subitem 67 for batch 4 has a delivery quantity of 13 pieces.
...

1. The ERP system sends the data for the kit to EWM. 2. In EWM, you reduce the delivery quantity of kit component item 30 to 12 pieces, and the delivery quantity of replaced kit component 40 to 10 pieces, due to a pick denial, for example. 3. EWM uses the correlation function to calculate the new delivery quantities. EWM changes the delivery quantities across the hierarchy levels, from bottom to top. In the case of batch subitems, EWM always changes the delivery quantities backwards in terms of the sequence of the items. a. EWM starts by executing the following delivery quantity changes across the hierarchy levels from bottom to top: Batch subitem 67 for batch 4: reduce to 3 pieces

SAP Extended Warehouse Management (SAP EWM)

510

241

SAP Online Help

20.07.2007

Batch subitem 65 for batch 3: no change, remains at 2 pieces Kit component item 60: reduce to 5 pieces Kit component item 50: no change, remains at 5 pieces Kit component item 40: reduce to 10 pieces Kit component item 30: reduce to 10 pieces, although you only reduced the delivery quantity by 8 pieces. However, since a fixed ratio of 1:10 is defined, EWM reduces the delivery quantity of this item by 10 pieces. Kit header item 10: reduce to 1 piece

b. EWM then executes the following delivery quantity change across the hierarchy levels from top to bottom: Kit component item 20: reduce to 5 pieces, since a fixed ratio of 1:5 is defined. The following figure shows you the hierarchy of the kit in EWM following the delivery quantity correlation, together with the respective delivery quantities.

SAP Extended Warehouse Management (SAP EWM)

510

242

SAP Online Help

20.07.2007

Connection of Delivery Processing to Quality Management


Use
Extended Warehouse Management (EWM) groups together all the necessary data for Quality Management [Seite 851] to automatically create inspection documents [Extern] in the background in accordance with the Customizing for quality management. Here, EWM copies the inspection document number to the inbound delivery. In addition, EWM updates the document flow, the status for inspection planning, and, if necessary, the stock type in the inbound delivery.

Integration
See Creation of Inspection Document [Seite 869]

Prerequisites
You have carried out the Customizing for creating inspection documents [Seite 869]. You have defined inspection rules (see Master Data [Seite 855]). In the delivery, you have specified all the data necessary for the creation of an inspection document. If not all of the necessary data exists in the delivery by the time at which EWM is to create the inspection documents, EWM creates the inspection documents later. For example, EWM is to create an inspection document when the inbound delivery is activated. The batch number is required for creation. EWM only creates the inspection document once you have specified the batch number.

Features
In the following cases, EWM creates inspection documents in the background, regardless of Customizing: If you or EWM activate an inbound delivery If EWM sets the status In Yard for an inbound delivery Before EWM creates a warehouse task Before you post the goods receipt

When EWM creates an inspection document, it simultaneously updates the inbound delivery. EWM sets the QM Check Planning status type to the status value Completed and the QM Counting Planning status type to the status value Completed. Regardless of whether you carry out a quality inspection or not, EWM always updates the status data. For example, the result of quality inspection planning could be that EWM is not to carry out a quality inspection. EWM also sets the status data in this case. Once EWM has created the inspection documents, it updates the document flow for the reference document types Q01 and Q03. Thus, you can view all of the inspection documents for an inbound delivery in document flow. If necessary, EWM updates the stock type. For example, EWM changes the stock type in the inbound delivery from unrestricted-use stock to stock in quality inspection. For more information, see Quality Inspection [Seite 866] and Creation of Inspection Document [Seite 869].

SAP Extended Warehouse Management (SAP EWM)

510

243

SAP Online Help

20.07.2007

Activities
If you want to display the statuses QM Inspection Planning and QM Counting Planning, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Maintain Inbound Delivery. Go to the Status tab page.

SAP Extended Warehouse Management (SAP EWM)

510

244

SAP Online Help

20.07.2007

Connection of Delivery Processing to Batch Management


Use
You can work with batch numbers in both inbound and outbound deliveries. This means that you work continuously with homogenous partial quantities that are, for example, required by law or because of hazardous substance directives.

Prerequisites
If you want to create new batch numbers, you have defined number ranges for batches in Customizing for Extended Warehouse Management (EWM). For more information, see the Implementation Guide (IMG) for EWM under Master Data Product Define Number Range for Batch.

Features
A batch number can be specified via a system (an ERP system, for example) or you specify it directly in EWM. Using a determination indicator, EWM determines where the batch information originates from and whether you can still change the batch number. The following options exist: A different system specifies a batch number, for example in a purchase order in the ERP system. You must use this batch number, that is, you cannot change the batch number. A different system proposes a batch. For example, you have entered the batch in the inbound delivery of the ERP system. You can change this batch. You specify a known batch number directly in EWM, that is, it does not originate from another system. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Inbound Delivery Maintain Inbound Delivery Order. Go to the form view and enter a batch number in the Batch field. EWM can also create new batch numbers for inbound deliveries. For this, leave Batch. As soon as you save the the Batch field empty and choose the function inbound delivery, EWM creates a new batch number. You can also directly specify the existing batch number for outbound deliveries. To do so, on the SAP Easy Access screen, choose Delivery Processing Outbound Delivery Maintain Outbound Delivery Order. Go to the form view and specify the batch number. You can only change the batch number before saving. You can also specify the batch in the corresponding warehouse task. EWM copies the batch to the delivery. Here, EWM creates a batch subitem with the confirmed quantity and batch. When you are processing the inbound or outbound delivery, EWM copies the batch characteristics to the delivery, for example, the country of origin, minimum shelf life, or the expiry date. You can split a batch in the inbound delivery. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Inbound Delivery Maintain Inbound Delivery Order. Select a batch and choose the function Batch Subitem. EWM creates a corresponding subitem for the batch.

SAP Extended Warehouse Management (SAP EWM)

510

245

SAP Online Help

20.07.2007

Integration of Delivery Processing with Pickup


Use
Delivery processing supports goods issue for the pickup [Extern]. Goods issue for the pickup can be planned or unplanned.

Integration
If you work with a planned pickup, you generate an outbound delivery in ERP. ERP distributes it to Extended Warehouse Management (EWM). EWM generates a corresponding outbound delivery order. This contains the account assignment information from ERP. You cannot change this account assignment information in EWM. If you work with an unplanned pickup, you generate a direct outbound delivery order [Extern] in EWM. EWM distributes it to ERP. ERP generates a corresponding outbound delivery that contains the account assignment information from EWM. You can change the account assignment information in EWM.

Prerequisites
You have defined the account assignment categories in Customizing for EWM. For more information, see the Implementation Guide (IMG) for EWM under Goods Issue Process Outbound Delivery Define Account Assignment Category and Allow in Warehouse Number. You have defined a process profile for the pickup in Customizing for EWM. For more information, see the IMG for EWM under Cross-Process Settings Delivery Processing Process Management and Control. You have defined a status profile for the pickup in Customizing for EWM. For more information, see the IMG for EWM under Cross-Process Settings Delivery Processing Status Management Define Status Profiles. You have assigned the process profile for the pickup to a document type in Customizing for EWM. For more information, see the IMG for EWM under Goods Issue Process Outbound Delivery Manual Settings Define Document Types for Outbound Delivery Process.

For more information, see the documentation for the Business Configuration Sets (BC Sets) /SCWM/DLV_OUTBOUND_DIRODO_1 and /SCWM/DLV_OUTBOUND_DIRODO_2. On the SAP Easy Access screen, choose Tools Customizing Business Configuration Sets SCPR3 Display and Maintain BC Sets.

Features
Unplanned pickup You can create, change, or delete the account assignment information in unplanned outbound delivery orders for the pickup until goods issue has been posted. When you create or change a direct outbound delivery order, EWM performs a validation. The validation checks the type of account assignment category and its uniqueness. It also checks the type of the existing account assignment object. If you use multiple account assignment objects for a delivery item (multiple account assignment [Extern]), only one account assignment object is permitted to be non-static. This is to avoid a duplicate allocation. The account assignment object always refers to the complete delivery quantity of a delivery item. It does not consider partial quantities. Planned pickup

SAP Extended Warehouse Management (SAP EWM)

510

246

SAP Online Help

20.07.2007

You cannot create, change, or delete the account assignment data in planned outbound delivery orders for the pickup. EWM performs a validation when it activates a planned outbound delivery request. The validation checks the type of account assignment category and whether it occurs only once per delivery item. It also checks the type of the existing account assignment object. As is the case for unplanned pickup, only one account assignment object is permitted to be non-static. This is to avoid a duplicate allocation.

Activities
If you want to generate or edit direct outbound delivery orders for the pickup, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery -> /SCWM/SGI Pickup. If you want to check the account assignment category on the user interface for the outbound delivery order, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery -> /SCWM/SGI Pickup. Display a delivery document. Select a delivery item and choose Expand/Zoom In. EWM displays the details of the item. On the Account Assignment tab page, EWM displays the account assignment category, for example, cost center, and the account assignment object, for example, EEG1.

EWM displays all outbound delivery orders including those that have been marked as relevant for the pickup on the user interface for the outbound delivery (/SCWM/PROD). The indicator comes from the defined document type OPIG. See also: Direct Outbound Delivery Order [Seite 167]

SAP Extended Warehouse Management (SAP EWM)

510

247

SAP Online Help

20.07.2007

Communication from EWM to the ERP System


Use
Communication from Extended Warehouse Management (EWM) to the ERP system uses defined interfaces and enables distribution, changes to, and confirmation of delivery-relevant data. In the ERP system, the interfaces between EWM and the ERP system itself are based on deliveries. In EWM, they are based on the following: Inbound delivery notifications and inbound deliveries in the inbound delivery process Outbound delivery orders and outbound deliveries in the outbound delivery process

Where necessary, the ERP system triggers subsequent communication steps for specific processes. For more information, see Warehouse Request for Inbound Delivery or Outbound Delivery Order [Seite 112], Creation of a Warehouse Request for Inbound Delivery [Seite 113], Creation of a Warehouse Request for Outbound Delivery Order [Seite 116] Communication is asynchronous and uses queued Remote Function Call (qRFC) technology. This technology guarantees serialization of the messages.

Integration
The following figure gives you an overview of the functions supported by the interfaces between EWM and the ERP system:

ERP System
Delivery 1 Changed delivery Delivery 2 Confirmation (goods movement) Executed delivery 1 Warehouse request Delivery change Delivery split Changed warehouse request Executed delivery 2 Change message Completed delivery 1

Delivery

1 Copy

Split message

Completed executed delivery 1

SAP SCM, EWM


...

1. Distribution of deliveries

SAP Extended Warehouse Management (SAP EWM)

510

248

SAP Online Help

20.07.2007

Send from ERP system to EWM Send from EWM to the ERP system (for example, for manual inbound deliveries)

2. Changes to deliveries Send from EWM to the ERP system (for example, confirmation of a pick denial from EWM to the ERP system) Send from the ERP system to EWM (for example, changed ASN from vendor)

3. Confirmation of an inbound and outbound delivery split from EWM to the ERP system 4. Send confirmation of deliveries from EWM for follow-on functions in the ERP system (for example, goods receipt, goods issue, confirmation before goods issue for invoicing before goods issue)

Prerequisites
You are using an ERP system. Here, you define for each plant and storage location whether you manage your warehouse in a separate, decentralized EWM. EWM receives the requests for goods movements from the ERP system. Transmit all information to EWM that EWM requires for the goods movements. These include: Partner master data (for example, customers, vendors, transportation service providers) Location master data (for example, customers, vendors, plants) Product master data

You have made the Customizing settings for ERP integration. In the Implementation Guide (IMG) for EWM, choose Interfaces ERP Integration.

Features
The following functions are available for EWM and the ERP system for the purpose of processing inbound and outbound deliveries. Processing of Inbound Deliveries [Seite 251] Receipt of an inbound delivery from the ERP system to EWM Receipt of a change request for inbound deliveries from the ERP system to EWM Notification of changed data before goods receipt from EWM to the ERP system Confirmation of a goods receipt from EWM to the ERP system Notification of a reversal or correction of the goods receipt from EWM to the ERP system Notification of an inbound delivery split from EWM to the ERP system

Processing of Outbound Deliveries [Seite 253] Receipt of an unchecked outbound delivery from the ERP system to EWM Receipt of a checked outbound delivery from the ERP system to EWM Notification of an outbound delivery change from EWM to the ERP system

SAP Extended Warehouse Management (SAP EWM)

510

249

SAP Online Help

20.07.2007

Quantity change request from EWM to the ERP system Confirmation of a goods issue from EWM to the ERP system Notification of a reversal of the goods issue from EWM to the ERP system Direct billing or invoicing before goods issue Communication of an outbound delivery split from EWM to the ERP system

For more information, see Processing Inbound Deliveries [Seite 251], Processing Outbound Deliveries [Seite 253] , and Interfaces for Communication from EWM to the ERP System [Seite 257].

Activities
In order to create messages, you must perform the relevant processes using the appropriate user interface [Seite 138].

SAP Extended Warehouse Management (SAP EWM)

510

250

SAP Online Help

20.07.2007

Processing of Inbound Deliveries


Use
Extended Warehouse Management (EWM) and the ERP system have access to a range of functions that enable you to distribute, change, and confirm delivery-relevant data.

Integration
To read the integration description, see Communication from EWM to the ERP System [Seite 248].

Prerequisites
To read the description of the prerequisites, see Communication from EWM to the ERP System [Seite 248]. For more information about Customizing the integration between EWM and the ERP system, see the Implementation Guide (IMG) for EWM under Interfaces ERP Integration.

Features
Receipt of an inbound delivery from the ERP system in EWM EWM receives an inbound delivery notification as a result of the following process: The ERP system receives an advanced shipping notification (ASN) and validates this. The ERP system creates an inbound delivery and sends an inbound delivery notification to EWM. EWM can also receive an inbound delivery notification as a result of inbound deliveries created in the ERP system. EWM uses the inbound delivery notification to create an inbound delivery. If errors occur during ASN validation in the ERP system, the ERP system gives the incorrect delivery items an error status before sending the information to EWM. EWM blocks the incorrect delivery items for execution. Delivery items that do not contain errors are open for execution even if the inbound delivery contains other incorrect delivery items. The following rules apply when solving the errors: You can remove the errors in the ERP system. The ERP system sends a change message to EWM. EWM processes this change message as long as the inbound delivery is not yet in processing in EWM. You can remove the errors in EWM. EWM sends the changed data with the goods receipt confirmation to the ERP system. The ERP system decides whether it accepts the data to correct the errors, or whether you need to manually process the inbound delivery again in the ERP system before the system processes the goods receipt confirmation. In this case, the ERP system returns the message, which was originally sent by EWM, to the qRFC inbound queue. After you have solved the error in the ERP system manually, you can start the message again in the qRFC inbound queue in the ERP system. The ERP system then continues processing accordingly.

Inbound delivery notifications that EWM receives can contain handling unit data (HU data). This is taken either from the electronic ASN from the vendor or was entered during manual packing in the ERP system. Only EWM supports automatic packing. You cannot use automatic packing in the ERP system. For more information, see Inbound Delivery Notification [Seite 87]. Receipt of a change request for inbound deliveries from the ERP system in EWM

SAP Extended Warehouse Management (SAP EWM)

510

251

SAP Online Help

20.07.2007

The vendor can send a new ASN or an ASN rejection for an existing inbound delivery. The ERP system receives these messages and validates them. It forwards them to EWM. EWM checks whether it can replace the existing inbound delivery. If it can replace the inbound delivery, it sends a confirmation message to the ERP system. If EWM cannot replace the existing inbound delivery, it sends a rejection message to the ERP system. If the inbound delivery is not yet being processed, in other words, if the status Warehouse Activity does not have the value Not Started, EWM replaces the inbound delivery. Notification of changed data before goods receipt from EWM to the ERP system If you make changes (such as setting the transit status In Yard or entering new items) in EWM, EWM sends these to the ERP system before confirming the goods receipt. If you only change the transit status in EWM, EWM only sends the header data for the inbound delivery to the ERP system. The ERP system replaces the header data accordingly. If you also replace relevant item data in EWM, EWM sends the entire document and the ERP system replaces the entire document with the data from EWM. The ERP system does not overwrite any data that cannot be provided by EWM (for example, the document type or company code). Confirmation of a goods receipt from EWM to the ERP system For inbound deliveries, you can make either partial (partial goods receipt) or complete goods receipt posting. You can specify whether there should be a confirmation to the ERP system for each individual partial goods receipt, or for the entire delivery. You can also specify whether EWM should also transfer the current HU data with the goods receipt confirmation to the ERP system. Notification of a reversal or correction of the goods receipt from EWM to the ERP system This enables you to correct or reverse goods movement postings. EWM creates a material document for these postings, which triggers confirmation of the correction or cancellation to the ERP system. Notification of an inbound delivery split from EWM to the ERP system You can split inbound deliveries in EWM. EWM creates new inbound deliveries for this delivery split, and reports them to the ERP system. EWM determines the document number and item number in the ERP system. You must have defined the number range intervals in Customizing. These number ranges must not overlap with the number ranges in the ERP system. For more information about the interfaces that enable these functions, see Interfaces for Communication from EWM to the ERP System [Seite 257]. For more information, see Inbound Delivery [Seite 88] and Creation of a Warehouse Request for an Inbound Delivery [Seite 113].

Activities
In order to create messages for processing inbound deliveries, you must perform the relevant processes using the appropriate user interface [Seite 138] . If you want to create inbound deliveries manually in the ERP system, on the SAP Easy Access screen, choose Logistics Logistics Execution Inbound Process Goods Receipt Automotive Goods Receipt Transaction.

SAP Extended Warehouse Management (SAP EWM)

510

252

SAP Online Help

20.07.2007

Processing of Outbound Deliveries


Use
Extended Warehouse Management (EWM) and the ERP system have access to a range of functions that enable you to distribute, change, and confirm delivery-relevant data.

Integration
To read the integration description, see Communication from EWM to the ERP System [Seite 248].

Prerequisites
To read the description of the prerequisites, see Communication from EWM to the ERP System [Seite 248].

Features
Receipt of an unchecked outbound delivery from the ERP system If you work with unchecked outbound deliveries in the ERP system, the ERP system can distribute these to EWM. The ERP system creates outbound delivery orders for unchecked deliveries. You cannot process these outbound delivery orders. You can only use them for a preview. EWM creates the following documents for unchecked outbound deliveries: An outbound delivery request An outbound delivery order

In EWM, you cannot create an outbound delivery for an outbound delivery order that EWM has created from an unchecked delivery in the ERP system. Receipt of a checked outbound delivery from the ERP system If the ERP system converts unchecked outbound deliveries into checked outbound deliveries, then it sends two messages to EWM. A deletion message for deleting an outbound delivery request, and an outbound delivery order that EWM created for the unchecked outbound delivery. A message for creating an outbound delivery request and an outbound delivery order for the checked outbound delivery

You can immediately process outbound delivery orders for checked outbound deliveries. EWM creates the following documents for checked outbound deliveries: An outbound delivery request An outbound delivery order

In EWM, you can create an outbound delivery for an outbound delivery order that EWM has created from a checked delivery of the ERP system. Notification of an outbound delivery change to the ERP system If you create a pick denial [Seite 327] in EWM, then EWM reduces the delivery quantity and writes an exception code in the outbound delivery order. This triggers confirmation of the change to the ERP system. The ERP system reports the change to SAP Customer Relationship Management (SAP CRM). The pick denial causes a reduction in the delivered quantity. The message to the ERP system contains an indicator for the SAP Extended Warehouse Management (SAP EWM) 510 253

SAP Online Help

20.07.2007

quantity change due to a pick denial. If you are using the Business Add-In (BAdI), you can use this indicator to perform another round of sourcing. The ERP system can create a new checked delivery for the missing quantity and can distribute this to EWM. This message to EWM contains an indicator for delivery creation, based on a confirmation of a pick denial. EWM sets this indicator in the outbound delivery order in the Wave Priority field. EWM uses this to take the outbound delivery order immediately into account during wave pick creation. To use the BAdI, in Customizing choose Customer Relationship Management Transactions Settings Before Sales Transactions Business Add-Ins Business Add-In for Data Exchange. This BAdI contains the method CRM_DATAEXCH_R3D_MBDOC_FILL, which you can use to set an indicator to trigger a new availability check. For more information about processing waves, see Wave Management [Seite 766]. Quantity change requests from the ERP system EWM can execute quantity change requests for the following: For checked deliveries, based on sales order changes in SAP CRM. For checked deliveries, based on new assignments of order confirmations by SAP Advanced Planning & Optimization.

EWM accepts a quantity change as long as the outbound delivery order is not yet being processed. If EWM accepts the quantity change, it reports the execution of the quantity change to the ERP system. EWM rejects any quantity changes for outbound delivery orders that are already in processing. The Warehouse Activity status for the outbound delivery order in this case is Warehouse Act./Part. Completed. If EWM rejects the quantity change, it reports the rejection of the quantity change to the ERP system. Communication of a goods issue confirmation to the ERP system EWM uses an outbound delivery to report a goods issue posting or reversal to the ERP system. You can only cancel an outbound delivery if it does not have the status In Transit. Direct billing or invoicing before goods issue You can print the invoice in the warehouse, if necessary, even before the goods issue. EWM uses an outbound delivery order to create an outbound delivery before the goods issue posting. If you have defined the status Invoicing Before Goods Issue for a route in Customizing, then EWM sets an indicator for this status that results in direct billing. If an outbound delivery order has this indicator, EWM creates the outbound delivery automatically. For automatic creation, EWM must also have set the Loading status to Started. After automatic creation of the outbound delivery, EWM triggers confirmation of the data to the ERP system for the purpose of direct billing. The ERP system forwards this data to the invoicing system in SAP CRM. Communication of an outbound delivery split to the ERP system EWM can split outbound delivery order, for example, if the requested quantity does not fit onto the means of transport. New outbound deliveries are generated by this split, which EWM reports to the ERP system. EWM determines the document number and item number in the ERP system. You must have defined the number range intervals in Customizing. These number ranges must not overlap with the number ranges in the ERP system.

SAP Extended Warehouse Management (SAP EWM)

510

254

SAP Online Help

20.07.2007

For more information about Customizing for number range intervals, see the Implementation Guide (IMG) for EWM under Interfaces ERP Integration Delivery Processing Define Number Ranges for ERP Documents. Replication of outbound delivery orders that were created manually in EWM, to ERP system If you create and save a direct outbound delivery order [Seite 167] manually in EWM without errors, EWM sends this to the ERP system immediately after saving, using an interface for communicating between EWM and ERP. For more information about the interfaces that enable these functions, see Interfaces for Communication from EWM to the ERP System [Seite 257]. See also: Outbound Delivery Request [Seite 90] Outbound Delivery Order [Seite 91] Outbound Delivery [Seite 93] Creation of a Warehouse Request for an Outbound Delivery Order [Seite 116].

Activities
In order to create messages for processing outbound deliveries, you must perform the relevant processes using the appropriate user interface [Seite 138] .

SAP Extended Warehouse Management (SAP EWM)

510

255

SAP Online Help

20.07.2007

Delivery Processing Administration


Use
The following provides you with technical information for: Interfaces for Communication from EWM to the ERP System [Seite 257] Functional Enhancement Through Business Add-Ins (BAdIs) [Seite 260] Data Enhancement for Warehouse Requests [Seite 261]

SAP Extended Warehouse Management (SAP EWM)

510

256

SAP Online Help

20.07.2007

Interfaces for Communication from EWM to the ERP System


Use
There is a range of interfaces available for communication from Extended Warehouse Management (EWM) to the ERP system.

Features
Interfaces for Inbound Deliveries
Interface Name /SPE/INB_DELIVERY_SAVEREPLICA Description Replication of inbound deliveries EWM to the ERP system (EWM ERP System) Replication of manually created inbound deliveries in the ERP system to EWM (ERP system EWM) Confirmation of the goods receipt in EWM (EWM ERP system) Correction or reversal of the goods receipt in EWM (EWM ERP system) /SPE/INB_DELIVERY_REPLACE Replication of inbound delivery changes before goods receipt (EWM ERP system) Additional Information For more information, see the function module description for /SPE/INB_DELIVERY_SAVEREPLICA.

/SCWM/INB_DLV_SAVEREPLICA

For more information, see the function module description for /SCWM/INB_DLV_SAVEREPLICA.

/SPE/INB_DELIVERY_CONFIRM_DECENTRAL

For more information, see the function module description for /SPE/INB_DELIVERY_CONFIRM_DECENTRAL

For more information, see the function module description for /SPE/INB_DELIVERY_REPLACE

SAP Extended Warehouse Management (SAP EWM)

510

257

SAP Online Help

20.07.2007

Confirmation of deletion of an inbound delivery (EWM ERP system) /SCWM/INB_DELIVERY_REPLACE Replication of changed inbound deliveries (ERP system EWM) Reporting of inbound deliveries that were generated by the split in EWM (EWM ERP system) Reject or confirm replicated inbound delivery changes (EWM ERP system) For more information, see the function module description for /SCWM/INB_DELIVERY_REPLACE.

/SPE/INB_DELIVERY_SPLIT

For more information, see the function module description for /SPE/INB_DELIVERY_SPLIT.

/SPE/INB_DELIVERY_RESPONSE

For more information, see the function module description for /SPE/INB_DELIVERY_RESPONSE.

Interfaces for Outbound Deliveries


Interface Name /SCWM/OUTB_DLV_SAVERE PLICA Description Replication of unchecked and checked deliveries from ERP system to EWM (ERP system EWM) Confirmation of unchecked and checked deliveries for follow-on functions (for example, goods issue, invoicing before goods issue) (EWM ERP system) Confirmation (at delivery item level) of quantity change request for checked deliveries (EWM ERP system) Change checked deliveries (EWM ERP system) Confirm pick denials (EWM Additional Information For more information, see the function module description for /SCWM/OUTB_DLV_SAVERE PLICA. For more information, see the function module description for BAPI_OUTB_DELIVERY_CO NFIRM_DECENTRAL.

BAPI_OUTB_DELIVERY_CO NFIRM_DECENTRAL

BAPI_OUTB_DELIVERY_CH ANGE

For more information, see the function module description for BAPI_OUTB_DELIVERY_CH ANGE.

SAP Extended Warehouse Management (SAP EWM)

510

258

SAP Online Help ERP system) Reversal of goods issue (EWM ERP system) /SCWM/OUTB_DLV_CHANG E Delete unchecked deliveries (ERP system EWM)

20.07.2007

For more information, see the function module description for /SCWM/OUTB_DLV_CHANG E. For more information, see the function module description for BAPI_OUTB_DELIVERY_SPL IT_DECENTRAL. For more information, see the function module /SCWM/OBDL_CHNG_QUAN _MUL. For more information, see the function module description for BAPI_OUTB_DELIVERY_REJ ECT. For more information, see the function module description for /SPE/OUTB_DELIVERY_SAV EREPLICA.

BAPI_OUTB_DELIVERY_SPL IT_DECENTRAL

Confirm outbound delivery split to ERP system (EWM ERP system) Quantity change requests for checked deliveries from ERP system to EWM (ERP system EWM) Reject a quantity change request (EWM ERP system) Replication of outbound delivery orders created manually in EWM, to ERP system (EWM ERP system)

/SCWM/OBDL_CHNG_QUAN _MUL

BAPI_OUTB_DELIVERY_REJ ECT

/SPE/OUTB_DELIVERY_SAV EREPLICA

Activities
If you want to call up the function module documentation or edit an interface, on the SAP Easy Access screen, choose Tools ABAP Workbench Development Function Builder.

SAP Extended Warehouse Management (SAP EWM)

510

259

SAP Online Help

20.07.2007

Functional Enhancement Through Business AddIns (BAdIs)


Use
You use Business Add-Ins [Extern] (BAdIs) in delivery processing to execute user-defined functional enhancements in Extended Warehouse Management (EWM). You can carry out functional enhancements for the following areas: Goods receipt process Goods issue process Warehouse-internal processes Cross-process settings Interfaces

Features
For a description of the individual BAdIs, see the relevant BAdI documentation in the Implementation Guide (IMG) for EWM.

Activities
To call the BAdI documentation, see the Implementation Guide (IMG) for EWM under Business Add-Ins (BAdIs) for Extended Warehouse Management. Select the desired BAdI and choose Documentation for IMG Activity.

EWM shows you the BAdI description of the IMG. To carry out functional enhancements for delivery processing, see the Implementation Guide (IMG) for EWM under Business Add-Ins (BAdIs) for Extended Warehouse Management and then choose the area for which you want to carry out the functional enhancement. For more information about Business Add-Ins (BAdIs), see the SAP Library under SAP NetWeaver Application Platform (SAP Web Application Server) ABAP Technology ABAP Workbench (BC-DWB) ABAP Workbench: Tools Further Concepts Business Add-Ins.

SAP Extended Warehouse Management (SAP EWM)

510

260

SAP Online Help

20.07.2007

Data Enhancement for Warehouse Requests


Use
You can use the data enhancement in Extended Warehouse Management (EWM) to add your own fields to the warehouse request, and therefore to adapt it to your requirements.

Integration
EWM uses the append technique for the data enhancement. You can use this method to add further structures to tables and structures. For more information, see Append Structure [Extern].

Features
For the document categories for the warehouse request, EWM offers extendable structures for the document header and document item. You can extend these structures using append structures. Document categories for the warehouse request and corresponding structures
Document Category Inbound Delivery Notification Inbound Delivery Outbound Delivery Request Outbound Delivery Order Outbound Delivery Stock Transfer Posting Change Request Posting Change Structure for Document Header /SCDL/INCL_EEW_DR_HEAD_STR /SCDL/INCL_EEW_DLV_HEAD_STR /SCDL/INCL_EEW_DR_HEAD_STR /SCDL/INCL_EEW_DLV_HEAD_STR /SCDL/INCL_EEW_DLV_HEAD_STR /SCDL/INCL_EEW_DLV_HEAD_STR /SCDL/INCL_EEW_DR_HEAD_STR /SCDL/INCL_EEW_DLV_HEAD_STR Structure for Document Item /SCDL/INCL_EEW_DR_ITEM_STR /SCDL/INCL_EEW_DLV_ITEM_STR /SCDL/INCL_EEW_DR_ITEM_STR /SCDL/INCL_EEW_DLV_ITEM_STR /SCDL/INCL_EEW_DLV_ITEM_STR /SCDL/INCL_EEW_DLV_ITEM_STR /SCDL/INCL_EEW_DR_ITEM_STR /SCDL/INCL_EEW_DLV_ITEM_STR

Several document categories have the same structure. This means that an enhancement is simultaneously present in more than one document category. EWM offers a range of Business Add-Ins (BAdIs) that you can use to fill the new fields with data.

Activities
1. On the SAP Easy Access screen, choose Tools ABAP Workbench Development Dictionary. The ABAP Dictionary: Initial Screen screen appears. 2. Choose Data Type. 3. In the Data Type field, enter the structure that you want to enhance using an append structure. 4. Choose Change. 5. Create an append structure and enhance the append structure by adding your own fields. For more information, see Extending Tables and Structures [Extern]. 6. Enter data into the new fields. To do this, in Customizing for Extended Warehouse Management under Business Add-Ins (BAdIs) for Extended Warehouse Management enter the relevant BAdIs.

For the data enhancement for messages to the decentralized ERP system, choose the following BAdI: Extended Warehouse Management Business Add-Ins (BAdIs) for Extended Warehouse Management Interfaces ERP Integration Inbound Messages from ERP System to EWM BAdI: Creation of Inbound Deliveries in EWM.

SAP Extended Warehouse Management (SAP EWM)

510

261

SAP Online Help

20.07.2007

SAP Extended Warehouse Management (SAP EWM)

510

262

SAP Online Help

20.07.2007

Goods Receipt
Purpose
Putaway enables you to display your complex putaway process steps and includes the following functions: Unloading [Seite 608] Counting [Seite 295] Deconsolidation [Seite 298] Final Putaway [Seite 300]

It takes into account your warehouse arrangement (for example, putaway using identification points [Seite 408] in a high rack storage area) as well as the process-oriented rules and process flows defined by you (for example, counting requests, repacking). Extended Warehouse Management (EWM) contains putaway strategies [Seite 375] to simplify the search for appropriate storage bins. You can put away your products directly or through storage control [Seite 334]. You can only execute complex putaway processes by using handling units.

Prerequisites
You have defined the following basic settings in Customizing for Extended Warehouse Management (EWM): Basic settings are, for example: IMG Activity Storage types, storage area, storage bins Path in Implementation Guide (IMG) IMG for EWM under Master Data Define Storage Type Define Storage Section Storage Bins Activity Areas Activities if required, work centers [Extern], for example, for deconsolidation Doors Staging areas IMG for EWM under Master Data Activity Areas Define Activity Areas IMG for EWM under Master Data Activity Areas Activities Define Activity Areas For more information about defining putaway steps, see the IMG for EWM under Master Data Work Center Define Work Center. IMG for EWM under Master Data Warehouse Door Define Warehouse Door IMG for EWM under Goods Issue Process Define Staging Areas

You have displayed your putaway steps in the system. For more information about defining putaway steps, see the IMG for EWM under Cross-Process Settings Warehouse Task Layout-Oriented Storage Control or Process-Oriented Storage Control.

SAP Extended Warehouse Management (SAP EWM)

510

263

SAP Online Help

20.07.2007

All required processes are fully integrated. The system updates, for example, the inbound delivery in the warehouse activities.

Process
...

1. The process begins when SAP R/3 receives an advanced shipping notification from an external system (for example, SAP CRM) for a planned inbound delivery. 2. The ERP system uses this advanced shipping notification to create an inbound delivery, and distributes it to EWM. 3. EWM uses the data from this inbound delivery to create a warehouse request. This warehouse request is the starting point for the putaway process. If you reject the inbound delivery in EWM, EWM sets the planned delivery quantity to zero and notifies the ERP system. EWM ends the inbound delivery and sets the status of the warehouse request to Completed.

For more information, see Warehouse Request for Returns [Seite 132].

Result
EWM uses the warehouse request to create one or more warehouse tasks for the putaway (putaway WT). You can use it to put away the products.

SAP Extended Warehouse Management (SAP EWM)

510

264

SAP Online Help

20.07.2007

Storage Control
Use
You can use the process-oriented as well as layout-oriented methods for storage control. The goal of storage control is to display your complex putaway or stock removal process steps based on your processes or your layout data. During putaway or stock removal, an individual process step can be executed on single level basis or on multi level basis (that is, through intermediate storage types). You can combine the process-oriented storage control with the layout-oriented storage control. Here, EWM always executes the process-oriented storage control first. The layoutoriented storage control then checks whether the sequence of putaway process steps is possible in layout view, and if required, adjusts the flow of the putaway or stock removal.

Based on the process-oriented storage control, EWM determined the following putaway process flow: Unloading at door Counting at counting station Checking the quality Executing value-added services Putaway in high rack storage area

The layout-oriented storage control determines that a direct putaway in the high rack storage area is not possible and that the putaway must occur with the use of an identification point. Unloading at door Counting at counting station Identification of goods at the ID point [Extern] Putaway in high rack storage area

Integration
Extended Warehouse Managment (EWM) uses the delivery to determine, via delivery type and delivery item among others, the warehouse process type. This contains the procedure, in other words, the putaway or stock removal process with different activities. EWM transfers this operation to the handling unit to be put away or removed from stock. The handling unit thus contains the information concerning what process steps are required for the putaway or stock removal.

Prerequisites
You have defined the following in Customizing for the putaway: Paramaters that specify the work station determination for the next function (for example, counting) within the goods receipt process The following parameters are possible:

SAP Extended Warehouse Management (SAP EWM)

510

265

SAP Online Help

20.07.2007

Source storage type Destination activity area or destination storage type Warehouse process type Handling unit type

Determination of the warehouse process type, using the delivery type and delivery item type, among others.

Features
For information about the features of storage control, see Process-Oriented Storage Control [Seite 336] and Layout-Oriented Storage Control [Seite 340].

SAP Extended Warehouse Management (SAP EWM)

510

266

SAP Online Help

20.07.2007

Process-Oriented Storage Control


Use
You use this type of storage control to map complex putaways or stock removals. In doing so, you combine your storage process steps into one storage process. You can also trace the status of the individual process steps.

Process-oriented storage control only operates with handling units.

Integration
For more information about integration, see Storage Control [Seite 334].

Prerequisites
For more information about the prerequisites, see Storage Control [Seite 334].

Features
You define the process steps for your complex storage process. A process step is, for example, unloading, counting, or deconsolidating [Seite 298]. Extended Warehouse Management (EWM) recognizes internal process steps predefined by SAP and external steps that you can define yourself. Your external process stesps can base themselves on internal ones. In addition, internal or external process steps can be simple, such as unloading, or combined, such as deconsolidating. For more information, see Direct and Combined Storage Control [Seite 268]. The process steps for the processes Counting and Deconsolidating predefined by SAP can be dynamic [Extern]. During goods receipt or goods issue, EWM copies the predefined process steps from the storage process type to the handling unit. EWM assigns these process steps to a handling unit as soon as it has created or changed them.

Activities
For Customizing of process-oriented storage control, in the Implementation Guide (IMG) for EWM, choose Cross-Process Settings Warehouse Task Define Process-Oriented Storage Control.

SAP Extended Warehouse Management (SAP EWM)

510

267

SAP Online Help

20.07.2007

Direct and Combined Storage Control (Putaway)


Use
If you want to execute a direct putaway, you do not have to define anything in the processoriented storage control [Seite 336]. If you want to define complex putaway processes, you have to use a combined processoriented storage control. Extended Warehouse Management (EWM) uses this during creation of a warehouse task to determine the intermediate storage types (for example, deconsolidation station, counting station). For information about integration and the prerequisites, see Storage Control [Seite 334] .

Features
Direct Storage Control at Putaway If EWM determines that you are to put away a handling unit (HU) directly, it creates a warehouse task for this HU that determines the way from the source storage type to the destination storage type. For more information about updating the status, see Updating the Inbound Delivery in the GR Process [Seite 271]. The following graphic shows you the relationship between direct putaway and creation of warehouse tasks.
Goods Receiving Area

Source Storage Type 9010

Warehouse Task 1

Destination Storage Type 0010

Source Storage Type 9011

Warehouse Task 2

Destination Storage Type 0020

Combined Storage Control at Putaway If EWM determines that you are to put away a HU from stock using one or more intermediate storage types, it creates one warehouse task per route section for this HU. One warehouse task that describes the route from source storage type to intermediate storage type Irrespective of your settings in Customizing, EWM also creates a warehouse task per product contained in the HU. If, for example, an inbound delivery is packed and the HU

SAP Extended Warehouse Management (SAP EWM)

510

268

SAP Online Help

20.07.2007

has no profile for process-oriented storage control, EWM creates product warehouse tasks at putaway. Based on your settings in Customizing, one warehouse task from the intermediate storage type to the next intermediate storage type, or to the final destination storage type. You can carry out different activities at the intermediate storage types. For example, within a putaway process, at an intermediate storage type, you can distribute HUs containing different products to putaway HUs. In combined putaway, you can determine the final destination storage type either right at the beginning of your putaway process, or later. EWM manages the intermediate storage types in the same way as standard storage types. For example, you can break these down into storage sections and storage bins. For more information about updating the status, see Updating the Inbound Delivery in the GR Process [Seite 271]. The following graphic shows you the relationship between combined putaway and creation of warehouse tasks.

Goods Receiving Area

Intermediate Storage Type 8000

Source Storage Type 9010

Warehouse Task 1.1

Intermediate Storage Type 8010

Warehouse Task 1.2

Destination Storage Type 0010

Source Storage Type 9011

Warehouse Task 2.1

Intermediate Storage Type 8020

Warehouse Task 2.2

Intermediate Storage Type 8030

Warehouse Task 2.3

Destination Storage Type 0020

Example
Direct Goods Receipt The following is a sample process flow of a direct goods receipt.
...

1. The truck comes to the loading ramp. 2. You open the truck.

SAP Extended Warehouse Management (SAP EWM)

510

269

SAP Online Help

20.07.2007

3. In EWM, you confirm the arrival of the truck. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Shipping and Receiving. 4. EWM creates a WT for this delivery that directly specifies the destination storage bin. 5. You unload the truck. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Shipping and Receiving Unload. 6. You count the number of pieces of your products and confirm these in the WT. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Execution Confirm Warehouse Task. 7. You execute the putaway. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Execution Confirm Warehouse Task. Combined Goods Receipt The following is a sample process flow of a combined goods receipt.
...

1. The truck comes to the loading ramp. 2. You open the truck. 3. In EWM, you confirm the arrival and opening of the truck. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Shipping and Receiving. 4. EWM creates a WT for this delivery that directly specifies the destination storage bin. 5. You unload the truck. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Shipping and Receiving Unload. 6. You count the number of pieces of your products and confirm these in the WT. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Execution Confirm Warehouse Task. 7. EWM indicates that a deconsolidation of the products is necessary. 8. You store your products at the intermediate storage location and confirm this. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Execution Confirm Warehouse Task. 9. You execute the deconsolidation at the intermediate location. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Execution Deconsolidation in Goods Receipt. 10. You store your products at the destination storage bin. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Execution Confirm Warehouse Task.

SAP Extended Warehouse Management (SAP EWM)

510

270

SAP Online Help

20.07.2007

Updating the Inbound Delivery in the GR Process


Use
Extended Warehouse Management (EWM) updates the inbound delivery corresponding to the goods receipt activities. For the goods receipt process (GR process), EWM maps the warehouse with the goods receipt and interior of the warehouse areas. This allows EWM to determine the point in time from when a putaway is planned, that is, from when a warehouse activity exceeds the limit for the interior of the warehouse. The following information belongs to the goods receipt area: Transportation units (TUs) Storage bins at warehouse doors Staging area groups

All storage types that do not correspond to goods receipt belong to the interior of the warehouse area. For example: Work centers Identification points Final storage types

EWM updates the statuses Unloading, Putaway Planning and Putaway in the inbound delivery, corresponding to this warehouse mapping.

Features
Updating an Inbound Delivery with a Handling Unit Warehouse Task (HU WT) For Packed Stock
The following graphic and description shows you the connection between process steps in GR and updating the inbound delivery with an HU WT for packed stock.
Unloading Putaway Planning Putaway

1
TU / Door Staging Area Group Deconsolidation Final Storage Type

Goods Receipt

Interior of Warehouse

You perform the GR activities for unloading and putaway. EWM updates the inbound delivery and sets the status in the inbound delivery.
Fr ... ...

The following applies for the status Unloading: If you confirm an HU WT that is moving from a door or TU to a staging area group, EWM sets the status Unloading in the inbound delivery (see number 1 in the graphic).

SAP Extended Warehouse Management (SAP EWM)

510

271

SAP Online Help

20.07.2007

If you confirm an HU WT that is moving from a staging area group to a door or a TU, EWM resets the status Unloading in the inbound delivery (see number 2 in the graphic).

The following applies for the status Putaway Planning: If you or the system generate an HU WT that is moving from goods receipt to the interior of the warehouse, EWM sets the status Putaway Planning in the inbound delivery (see number 3 in the graphic). If you cancel an HU WT that is moving from goods receipt to the interior of the warehouse, EWM resets the status Putaway Planning in the inbound delivery (see number 4 in the graphic). If you confirm an HU WT that is moving from the interior of the warehouse to goods receipt, EWM resets the status Putaway Planning in the inbound delivery (see number 5 in the graphic).

The following applies for the status Putaway: If you confirm an HU WT that contains the final storage type, EWM sets the status Putaway in the inbound delivery (see number 6 in the graphic).

Updating an Inbound Delivery with a Product Warehouse Task (Product WT) For Unpacked Stock
You perform the GR activities for unloading and putaway. EWM updates the inbound delivery and sets the status in the inbound delivery.
Fr ... ...

The following applies for the status Unloading: If you confirm a product WT for unpacked stock that is located in a TU or storage bin at the door, EWM sets the status Unloading in the inbound delivery. A prerequisite for this is that the destination location in the product HU is not a TU, or that the destination storage type in the product WT is not a door.

The following applies for the status Putaway Planning: If you or the system generate a product WT that is moving from the goods receipt bin to another storage bin, EWM sets the status Putaway Planning in the inbound delivery. If you cancel a product WT because EWM originally set the status Putaway Planning in the inbound delivery, EWM resets the status Putaway Planning in the inbound delivery. If you move a product back to its original goods receipt bin with a product WT, EWM resets the status Putaway Planning in the inbound delivery.

If you move a product from the goods receipt bin to an HU, and this HU is in the interior of the warehouse, EWM always sets the status Putaway Planning in the inbound delivery. EWM does not update the status Putaway Planning unless the HU is in the interior of the warehouse. The following applies for the status Putaway: If you confirm a product WT that contains the final storage type, EWM sets the status Putaway in the inbound delivery.

Updating an Inbound Delivery with Storage Control


The following graphic and description shows you the connection between process steps in GR and updating the inbound delivery with storage control [Seite 334].

SAP Extended Warehouse Management (SAP EWM)

510

272

SAP Online Help

20.07.2007

Unloading

Putaway Planning

Putaway

1
TU / Door Staging Area Group Deconsolidation Final Storage Type

Goods Receipt

Interior of Warehouse

Handling Unit Warehouse Task Product Warehouse Task

You perform the GR activities for unloading and putaway. EWM updates the inbound delivery and sets the status in the inbound delivery.
...

The following applies for the status Unloading: If you confirm an HU WT that is moving from a door or TU to a staging area group, EWM sets the status Unloading in the inbound delivery (see number 1 in the graphic). If you confirm an HU WT that is moving from a staging area group to a door or a TU, EWM resets the status Unloading in the inbound delivery (see number 2 in the graphic).

The following applies for the status Putaway Planning: If you or the system generate a product WT for putaway and an HU WT for unloading, EWM always sets the status Putaway Planning in the inbound delivery corresponding to the warehouse activities for the product WT. EWM uses the HU WT to update the status Unloading in the inbound delivery (see number 3 in the graphic). If you or the system generate an HU WT into the interior of the warehouse and no product WT for putaway exists, EWM always sets the status Putaway Planning in the inbound delivery corresponding to the warehouse activities for the HU WT (see number 4 in the graphic).

The following applies for the status Putaway: If you confirm a product WT that contains the final storage type, EWM sets the status Putaway in the inbound delivery corresponding to the product WT. If you confirm an HU WT that contains the final storage type, EWM sets the status Putaway in the inbound delivery corresponding to the HU WT. This means that, depending on which WT you confirm first, EWM sets the status Putaway in the inbound delivery with this WT (see number 6 in the graphic).

Updating an Inbound Delivery and Outbound Delivery Order in CrossDocking


EWM performs cross-docking [Seite 544] (CD). For the CD-relevant products, EWM generates one or more pick-warehouse tasks (pick-WTs) for CD and updates the inbound delivery and the outbound delivery order simultaneously. For the other products, EWM generates standard product WTs. The following applies for the status Unloading:

SAP Extended Warehouse Management (SAP EWM)

510

273

SAP Online Help


Fr ... ...

20.07.2007

If you confirm an HU WT that is moving from a door or TU to a staging area group, EWM sets the status Unloading in the inbound delivery. If you confirm an HU WT that is moving from a staging area group to a door or TU, EWM resets the status Unloading in the inbound delivery.

The following applies for the status Putaway Planning in the inbound delivery and the status Picking Planning in the outbound delivery order in CD: If EWM generates a pick-WT for CD, the system sets the status Putaway Planning in the inbound delivery and the status Picking Planning in the outbound delivery order. If you cancel a pick-WT for CD, EWM resets both the status Putaway Planning in the inbound delivery and the status Picking Planning in the outbound delivery order.

The following applies for the status Putaway in the inbound delivery and the status Picking in the outbound delivery order in CD: If you confirm a pick-WT for CD, EWM sets the status Putaway in the inbound delivery and the status Picking in the outbound delivery order.

SAP Extended Warehouse Management (SAP EWM)

510

274

SAP Online Help

20.07.2007

Layout-Oriented Storage Control


Use
You can use the layout-oriented storage control if stock movements in your warehouse do not travel from a source storage bin to a destination location directly, rather travel via intermediate storage bin.

The layout-oriented storage control only operates with handling units. One exception is the process display with picking or identification points. You use layout-oriented storage control in the material flow system [Seite 820] to define conveyor segments.

Integration
For more information about integration, see Storage Control [Seite 334].

Prerequisites
For more information about the prerequisites, see Storage Control [Seite 334].

Features
For layout-oriented storage control, you define external warehouse process steps for your warehouse, including identification points [Extern] and pick points [Extern].

For example, you have a high rack storage area. If you want to move a product pallet from storage bin A (goods receiving area) to storage bin B (high rack storage area), the system should execute a contour and weight check to ensure that the product pallet can be put away in the high rack storage area safely. For this activity, Extended Warehouse Management (EWM) splits the warehouse order into two: one from storage bin A to identification point I, and a second from identification point I to storage bin B. You can move your goods using a pick point during picking.

Activities
For Customizing of layout-oriented storage control, in the Implementation Guide (IMG) for EWM, choose Cross-Process Settings Warehouse Task Layout-Oriented Storage Control.

SAP Extended Warehouse Management (SAP EWM)

510

275

SAP Online Help

20.07.2007

Storage Group
Definition
The storage group is a grouping of storage bins within a storage type [Extern] that is used to determine intermediate storage bins.

Use
Extended Warehouse Management (EWM) uses the storage group in layout-oriented storage control [Seite 340] to determine the intermediate storage bins. The material flow system [Seite 820] also uses layout-oriented storage control and thereby the storage group to define conveyor segments.

Structure
The storage group consists of a four-character identifier that you assign to a warehouse number and a storage type.

Integration
EWM uses storage groups in layout-oriented storage control and in the material flow system.

Example
You group all the storage bins in an aisle into a storage group since you want to take the goods that you remove from this aisle to an interim storage bin at the end of the aisle.

SAP Extended Warehouse Management (SAP EWM)

510

276

SAP Online Help

20.07.2007

Slotting
Use
During slotting, a storage concept is automatically determined for a product. The system determines the underlying storage parameters that are relevant for putaway on the basis of master data, that is, product data, requirement data [Seite 279], and packaging data. These parameters describe the storage section in which the product is to be stored, the properties that the storage bin is to have, and the putaway strategy that is to be used. Slotting takes into account master data that is not dependent on the execution process. If the putaway process for a product is dependent on execution parameters, this dependency is taken into account later on during storage bin determination for putaway [Seite 291]. This does not, however, have an effect on the results of slotting.

Prerequisites
You work with storage bin types. You have defined the attributes in the product master that you want to use to determine the storage parameters. You have defined a number range interval and assigned it to your warehouse in Customizing under Extended Warehouse Management Goods Receipt Process Slotting General Settings. You have defined storage type sequences in Customizing under Extended Warehouse Management Goods Receipt Process Slotting Master Data. You have made the settings for the condition technique in Customizing under Extended Warehouse Management Goods Receipt Process Slotting Condition Technique. You have defined condition records. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Master Data Slotting Condition Maintenance for Slotting.

Features
During slotting, the system determines the following storage parameters and stores them in the product master: 1. Putaway control indicator (and, optionally, stock removal control indicator) 2. Maximum quantity in storage type 3. Storage section indicator 4. Storage bin types The system always performs step 1. Steps 2 to 4 are optional. Steps 1, 3, and 4 are performed using the condition technique. Step 4 can also be performed using storage bin type determination rules [Seite 283]. For more information about the condition technique, see the SAP Library under mySAP Customer Relationship Management CRM Enterprise Enterprise Sales Sales Management for Commercial and Industrial Customers Basic Functions Condition Technique. Slotting is optional. We recommend that you perform it periodically in the background. The results of slotting can be used in storage bin determination. Slotting also forms the basis of rearrangement [Seite 287].

SAP Extended Warehouse Management (SAP EWM)

510

277

SAP Online Help

20.07.2007

Activities
To perform slotting, on the SAP Easy Access screen, choose Extended Warehouse Management Master Data Slotting Slot Products for Warehouse. Then choose the storage parameters that the system is to determine.

SAP Extended Warehouse Management (SAP EWM)

510

278

SAP Online Help

20.07.2007

SAP APO Interface for Transferring Requirement Data


To be able to calculate parameters such as the maximum quantity in the storage type, slotting needs requirement data for the relevant product. This requirement data can come from SAP Advanced Planning and Optimization (SAP APO). Extended Warehouse Management (EWM) stores this information locally in the product master (on the Slotting tab page, Requirement/Demand Data area). You can also fill these local attributes in EWM with data from other sources. To do this, you have several processing options in the product master, for example, manual input or mass maintenance. SAP APO and EWM manage requirement data at different organizational levels. SAP APO performs planning processes for locations of the type Plant. EWM stores requirement data at warehouse number level. Slotting assumes that a 1:1 relationship exists between the SAP APO location and the EWM warehouse number. If the relationship is not 1:1, you can use Business Add-Ins (BAdIs) for the conversion. In most cases, SAP APO and EWM run on different systems. The calling EWM system needs information about the SAP APO instance such as: Logical system Time interval for which the system is to read requirement data Information as to whether the data is forecast data or historical data

You define this information in Customizing for EWM. For more information, see the Implementation Guide (IMG) under Goods Receipt Process Slotting General Settings Change Information for APO Instances. If you have set the following indicators on the selection screen for slotting, the system reads the requirement data from SAP APO when performing slotting: Update Requirement Quantity Update Number of Order Items Update Recommended Storage Qty

You can also read the requirement data as a separate process.

SAP Extended Warehouse Management (SAP EWM)

510

279

SAP Online Help

20.07.2007

Update of Results in Product Master


Use
The system updates the results of the slotting run in the product master.

Features
All the product attributes that form the slotting results exist twice in the product master: As active values As planned values (can be recognized due to their name)

The exact values that are updated when the results are updated depends on the save mode that you chose when you called slotting: Do Not Save Results We recommend that you use this option if you have performed slotting interactively and you want to analyze the results. If you have performed slotting in the background, you can analyze the log, but you cannot see the results directly. Save Results (The system only updates the planned values in the product master.) Depending on the storage bin and stock situations, it can be useful to save the results of slotting as planned values only. The system only keeps the planned values for a possible activation, and does not use them in storage processes. Save and Activate Results (The system updates both the planned values and the active values in the product master.) The system updates the results of slotting in the fields for the planned values and the active values in the product master. These new values are then available immediately for all storage processes.

Product Attribute Levels


The product master has various views that represent various levels of product attributes: Global views Warehouse-number-dependent views Storage-type-dependent views

Before a slotting run, only a global view must exist for the product, in other words, the product must be known in the system. The system either creates the warehouse-number-dependent views and storage-type-dependent views when updating the results in the product master or it updates them if they existed already.

Fixing Values
You can use a relevant indicator to fix all product attributes that can form the results of slotting. In this case, the system does not overwrite these attributes during slotting.

SAP Extended Warehouse Management (SAP EWM)

510

280

SAP Online Help

20.07.2007

Update Attribute Storage Bin Improvable


Use
Slotting determines the optimum storage type, storage section, and storage bin type for a product. The system can determine whether a certain stock (quant) is stored in an optimum way. To do this, it compares these optimum values with the attributes of the storage bin in which the quant is located. Since the attribute Storage Bin Improvable depends on product attributes and on the current storage bin, it exists in both the fixed bin table and in the quant.

Instances of the Attribute Storage Bin Improvable


The attribute has the following instances: Not Improvable ( ) All three attributes (storage type, storage area, and storage bin type) are optimum. Pick with Priority (A) You can use this instance to support campaigns. You must configure this process manually. If a significantly greater demand is expected for a product during a campaign, you can create additional new fixed storage bins (picking bins) and can choose the instance Pick with Priority for these bins. You should also adjust the maximum storage type quantity of the relevant storage type for the product, or deactivate the check. This instance is independent from the other instances and it is never set automatically by slotting. Improvable (B) One of the three attributes (storage type, storage section, or storage bin type) is not optimum. The criteria for the instance Storage Type Improvable (C) are not met. Storage Type Improvable (C) The storage section and storage bin type are optimum. The current storage type belongs to a storage type group. The storage type is optimum for the product within the group but it is not optimum on a global level. In other words, the storage type group is not first in the search sequence.

Update
When you save or activate the results of slotting for a product, the system updates the attribute Storage Bin Improvable for the following in the warehouse number: For all quants of the product within the warehouse number For all existing and any newly-assigned fixed storage bins for the product within the warehouse number

The system determines the attribute Storage Bin Improvable for the new quant in the destination storage bin for each stock movement within the warehouse where the destination storage type has the storage type role Standard Storage Type.

SAP Extended Warehouse Management (SAP EWM)

510

281

SAP Online Help

20.07.2007

Consideration of Storage Types


In slotting, the system determines attributes for a subset of storage types only. These storage types are assigned to a warehouse number. You define the relevant storage types in Customizing for EWM (Extended Warehouse Management) by using the Warehouse No. and PutawayControlInd key fields. For more information, see the Implementation Guide (IMG) under Goods Receipt Process Slotting Master Data Define Putaway Control Indicator. You have assigned a storage type search sequence to the putaway control indicator in Customizing for EWM. The search sequence can contain storage types or storage type groups.

Storage Types
The system interprets each storage type as an independent area in the warehouse (for example, reserve or picking area). It assumes that stock for a product is to be stored in each storage type.

Storage Type Groups


The storage types in a storage type group have an equal weighting. The system assumes that a product is to be stored in one storage type only within a group. If, therefore, the system considers the storage type group for a certain product, there can be a prioritization of the storage types within this group in relation to this product. The system uses the optimum storage bin type per storage type for the prioritization. It determines an optimum storage bin type from the potential storage bin types for each storage type. It then prioritizes the optimum storage bin types again. When doing this, the system uses the same criteria as it used to determine the optimum value within a storage type. The sequence of storage bin types produces the sequence of storage types. The systems updates the position of a storage type in accordance with the prioritization in the product master in the storage type view in the Putaway Sequence attribute. It then uses this information when creating warehouse tasks (WTs).

Skip Storage Type


If the system could not determine the optimum storage section indicator or the optimum storage bin type during slotting, it does not consider the storage type when creating a WT. This system does this by setting the Skip During Putaway indicator in the storage type view of the product master. In this case, the system does not set the following attributes: Min. Replenish. Qty (Minimum Replenishment Quantity) Plnd Min. Replen. Qty (Planned Minimum Replenishment Quantity) Maximum Quantity

This also means that replenishment cannot take place in this storage type.

SAP Extended Warehouse Management (SAP EWM)

510

282

SAP Online Help

20.07.2007

Use of Storage Bin Type Determination Rules


Use
There are two options for determining the optimum storage bin type in slotting: Using the condition technique (in the same way as determining the putaway control indicator and the storage section indicator) Using storage bin type determination rules

The option that the system uses depends on the parameters that you have defined at storage type level for slotting.

Prerequisites
In Customizing for Extended Warehouse Management (EWM), you have defined whether you want to work with the condition technique or with storage bin type determination rules. In the latter case, you have chosen the required storage bin type determination rule. For more information, see the Implementation Guide (IMG) for EWM under Goods Receipt Process Slotting General Settings Define Storage Type Parameters for Slotting.

Features
The following storage bin type determination rules are available: Maximum Weight Capacity Factor: Material Simple Volume Check Simple Dimension Check The system compares the dimensions of the relevant packing level (PL) with the dimensions of the storage bin type (BT) in accordance with the following logical expression: Length (PL) < Length (BT) AND Width (PL) < Width (BT) AND Height (PL) < Height (BT) The system calculates the maximum number of packages by dividing the length, width, and height of the storage bin type by the length, width, and height of the packing level. The result is a maximum number per dimension. The global maximum number is then the product of the three maximum values per dimension. Dimension Check with Z-Axis Rotation The system compares the dimensions of the relevant packing level with the dimensions of the storage bin type in accordance with the following logical expression: Length (PL) < Length (BT) AND Width (PL) < Width (BT) AND Height (PL) < Height (BT) OR Length (PL) < Width (BT) AND Width (PL) < Length (BT) AND Height (PL) < Height (BT) The system calculates the maximum number of packages as described in the section Simple Dimension Check for each of the two orientations allowed. The global maximum number is then the greater of the two maximum values per orientation.

SAP Extended Warehouse Management (SAP EWM)

510

283

SAP Online Help

20.07.2007

Dimension Check with Rotation and Tilt The system compares the dimensions of the relevant packing level with the dimensions of the storage bin type in accordance with the following logical expression: Length (PL) < Length (BT) AND Width (PL) < Width (BT) AND Height (PL) < Height (BT) OR Length (PL) < Length (BT) AND Width (PL) < Height (BT) AND Height (PL) < Width (BT) OR Length (PL) < Width (BT) AND Width (PL) < Length (BT) AND Height (PL) < Height (BT) OR Length (PL) < Width (BT) AND Width (PL) < Height (BT) AND Height (PL) < Length (BT) OR Length (PL) < Height (BT) AND Width (PL) < Length (BT) AND Height (PL) < Width (BT) OR Length (PL) < Height (BT) AND Width (PL) < Width (BT) AND Height (PL) < Length (BT) The system calculates the maximum number of packages as described in the section Simple Dimension Check for each of the six orientations allowed. The global maximum number is then the greatest of the six maximum values per orientation.

Weight Check and Simple Volume Check Weight Check and Simple Dimension Check Weight Check and Dimension Check with Z-Axis Rotation Weight Check and Dimension Check with Rotation and Tilt

Additional Parameter Dimension Ratio


The product master attribute Dimension Ratio (on the Slotting tab page) considers the ratio between the length, width, and height of the relevant packing level. The system calculates all the ratios between length, width, and height that make sense on the basis of the orientations allowed. Orientations are not permitted in cases where the calculated ratio exceeds the parameter value from the product master. The system uses the dimension ratio in the following storage bin type determination rules: Simple dimension check (one orientation) Dimension check with z-axis rotation (two orientations) Dimension check with rotation and tilt (six orientations) Weight check and simple dimension check Weight check and dimension check with z-axis rotation

SAP Extended Warehouse Management (SAP EWM)

510

284

SAP Online Help

20.07.2007

Weight check and dimension check with rotation and tilt

SAP Extended Warehouse Management (SAP EWM)

510

285

SAP Online Help

20.07.2007

Simulation of Slotting
Use
You can use this function to simulate slotting without updating the product master.

Features
You perform the simulation in the test system. There you can change the configuration in any way that you want to without causing errors. You can analyze the results of the simulation step-by-step and can optimize the configuration. When you are satisfied with the result, you must adapt the configuration in the production system in accordance with the configuration in the test system. Part of the configuration is mapped via master data that you must change manually in the production system. We recommend that you then simulate slotting in the production system to check the configuration. Afterwards, you can perform slotting in the production system, and can save and activate the results there.

Activities
To simulate slotting, on the SAP Easy Access screen, choose Extended Warehouse Management Master Data Slotting Slot Products for Warehouse. To activate the plan values or to simulate the activation of plan values, on the SAP Easy Access screen, choose Extended Warehouse Management Master Data Slotting Activate Plan Values. You cannot perform slotting runs in this transaction. You can only display and activate the results from a slotting run that you have performed interactively or in the background. You can also simulate the activation of these results.

SAP Extended Warehouse Management (SAP EWM)

510

286

SAP Online Help

20.07.2007

Rearrangement
Use
You can use rearrangement to optimize the arrangement of your products in the warehouse by moving stock such as fast-moving items to the relevant optimal storage bin.

Prerequisites
You have created products and stocks. You have defined a default warehouse process type in Customizing for Extended Warehouse Management (EWM) under Internal Warehouse Processes Warehouse Optimization Specify Default Warehouse Process Type for Rearrangement. You have made the Customizing settings for putaway. If you want to work with slotting indexes, you must enter a value in the following places in the Evaluate Whse Item field in Customizing for EWM under Goods Receipt Process Strategies: Storage Type Search Assign Storage Types to Storage Type Search Sequence Storage Section Search Maintain Storage Section Search Sequence Storage Bin Determination Alternative Storage Bin Type Sequence or HU Types Define HU Types for Each Storage Bin Type

Features
The system compares the current storage type, storage section, and storage bin type with the optimal parameters from slotting [Seite 277]. When doing this, it analyzes how well suited the current parameters (storage type, storage section, and storage bin type) are to the product. If they are not optimal, the system proposes an optimum storage bin. When searching for an optimum destination storage bin (destination storage bin determination), the system uses search sequences for storage types, storage sections, and storage bin types. The entries in the search sequences are sorted by the slotting index and in descending order. You can assign a slotting index for each step in a search sequence in Customizing. The first entry in a search sequence should not have a slotting index so that a storage bin with an optimum storage type, storage section, and storage bin type has a slotting index of zero. In the case of rearrangement, the system first tries to propose an optimum storage bin (with a slotting index of zero). If this is not possible, the system proposes an alternative storage bin with the next lowest slotting index. The system only proposes an alternative storage bin if its slotting index is lower than that of the current storage bin. You can identify the most urgent stock transfers on the basis of the following data: Slotting index of the current storage bin Difference between the slotting indexes of the proposed storage bin and the current storage bin

The system also displays the number of empty bins per storage type, storage section, and storage bin type as part of the analysis. For an example of rearrangement, see here [Seite 289].

SAP Extended Warehouse Management (SAP EWM)

510

287

SAP Online Help

20.07.2007

Activities
1. To start rearrangement, on the SAP Easy Access screen, choose Extended Warehouse Management Work Scheduling Rearrangement. 2. Choose the required stocks. The system performs the analysis and displays the number of stock items per optimal storage bin type, storage section, and storage bin type/storage section for each current storage bin type, storage section, and storage bin type/storage section. 3. Choose one of the analyses, the required cell, column, or row, and then Details. 4. In the detail view, choose the required stock item and create a warehouse task. The system proposes a destination storage bin and reserves it. Save the warehouse task.

Alternatively, you can create a warehouse request to plan rearrangement as a wave. In this case, the system does not adopt the proposed destination storage bin and does not reserve it.

You can also execute rearrangement in the background. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Work Scheduling Rearrangement (Background).

SAP Extended Warehouse Management (SAP EWM)

510

288

SAP Online Help

20.07.2007

Example of Rearrangement
The first figure shows the warehouse before rearrangement takes place. The warehouse has an area for fast-moving items [Extern] (golden zone). It is positioned along the central aisle of the warehouse to ensure that the picker can reach it easily. The area for slow-moving items [Extern] is positioned behind this area.

Storage Section for Slow-Moving Items Storage Section for Fast-Moving Items (Golden Zone)

Entrance

Exit

The second figure shows a typical pick path before rearrangement takes place. Since some of the storage bins containing the products to be picked are situated a long way from the central aisle in the area for slow-moving items, the picker sometimes has to drive a long way down the side aisles to pick the required products.

Entrance

Exit

SAP Extended Warehouse Management (SAP EWM)

510

289

SAP Online Help

20.07.2007

The third figure shows how the system tries to shorten this long pick path during rearrangement by proposing that the fast-moving products are moved to the area for fastmoving items.

Entrance

Exit

The fourth figure shows the pick path after rearrangement has taken place. During picking, fast-moving items are often picked. Since these are now closer to the central aisle, the pick path is shorter. Now the picker rarely has to drive down a side aisle to pick products.

Entrance

Exit

SAP Extended Warehouse Management (SAP EWM)

510

290

SAP Online Help

20.07.2007

Storage Bin Determination for Putaway


Use
The aim of storage bin determination is to find the best physical destination storage bin for a putaway process or an internal warehouse goods movement. In addition to other data, parameters from the product master that you have defined manually or that were determined in slotting [Seite 277] are used to do this. Storage bin determination for putaway occurs automatically when a warehouse task is generated.

Prerequisites
You have created storage bins. You have made the settings for putaway in Customizing for Extended Warehouse Management (EWM), for example: You have defined storage section search sequences under Goods Receipt Process Strategies Storage Section Search Maintain Storage Section Search Sequence. You have defined HU types for each storage bin type under Goods Receipt Process Strategies Storage Bin Determination HU Types Define HU Types for Each Storage Bin Type.

Features
During storage bin determination, a physical storage bin is determined by means of determining and applying the suitable strategies [Seite 375].

In a fixed storage bin scenario, it could be the case that the fixed storage bin has already been determined for a storage type by slotting. In this case, you do not need to determine and apply additional search sequences. In a putaway process, storage bin determination covers the following steps: Determination of storage types The system first determines the storage type by determining and applying a storage type search sequence. The storage type search sequence defines in which storage types and in which order the system is to search for a destination storage bin for putaway. You can define multiple accesses for determining the storage type search sequence. The system checks these accesses until it finds a suitable storage type search sequence. You assign a putaway rule to each storage type in the storage type search sequence. The putaway rule specifies how a storage bin is to be determined, for example, empty storage bin. In addition to the putaway rule, the storage behavior also plays a role. It describes the type of storage bins, for example, normal, bulk storage, or pallet storage.

If a product has the stock category Quality Inspection, it could be the case that all other parameters are unimportant. You could, therefore, define the first access in such a way that the system is to search for a storage type search sequence where only this stock type is used. Determination of storage sections

SAP Extended Warehouse Management (SAP EWM)

510

291

SAP Online Help

20.07.2007

For each storage type that is found, the system then determines a storage section by determining and applying a storage section search sequence. You can use the Business AddIns in the /SCWM/ES_CORE_PTS enhancement spot to implement a customer-specific logic. Determination of storage bin types Then the system determines a storage bin type for each storage type by determining and applying a storage bin type search sequence. You can use the Business Add-Ins in the /SCWM/ES_CORE_PTS enhancement spot to implement a customer-specific logic. Determination of storage bins Last of all, the system uses a certain priority to evaluate the combinations of storage type, storage section, and storage bin type that have been found. Here it tries to find a storage bin for each combination in accordance with the putaway rule. Slotting and storage bin determination If you use slotting, it could be the case that you want to prevent storage bin determination for products that have not yet been slotted. If, however, you do not use slotting, there is no reason to prevent storage bin determination. You can also use the IMG activity Define Warehouse Number Parameters for Putaway (under Goods Receipt Process Strategies) to control at warehouse level whether storage bin determination is to be permitted if slotting has not yet been performed for a product.

SAP Extended Warehouse Management (SAP EWM)

510

292

SAP Online Help

20.07.2007

Connection of Delivery Processing to Quality Management


Use
Extended Warehouse Management (EWM) groups together all the necessary data for Quality Management [Seite 851] to automatically create inspection documents [Extern] in the background in accordance with the Customizing for quality management. Here, EWM copies the inspection document number to the inbound delivery. In addition, EWM updates the document flow, the status for inspection planning, and, if necessary, the stock type in the inbound delivery.

Integration
See Creation of Inspection Document [Seite 869]

Prerequisites
You have carried out the Customizing for creating inspection documents [Seite 869]. You have defined inspection rules (see Master Data [Seite 855]). In the delivery, you have specified all the data necessary for the creation of an inspection document. If not all of the necessary data exists in the delivery by the time at which EWM is to create the inspection documents, EWM creates the inspection documents later. For example, EWM is to create an inspection document when the inbound delivery is activated. The batch number is required for creation. EWM only creates the inspection document once you have specified the batch number.

Features
In the following cases, EWM creates inspection documents in the background, regardless of Customizing: If you or EWM activate an inbound delivery If EWM sets the status In Yard for an inbound delivery Before EWM creates a warehouse task Before you post the goods receipt

When EWM creates an inspection document, it simultaneously updates the inbound delivery. EWM sets the QM Check Planning status type to the status value Completed and the QM Counting Planning status type to the status value Completed. Regardless of whether you carry out a quality inspection or not, EWM always updates the status data. For example, the result of quality inspection planning could be that EWM is not to carry out a quality inspection. EWM also sets the status data in this case. Once EWM has created the inspection documents, it updates the document flow for the reference document types Q01 and Q03. Thus, you can view all of the inspection documents for an inbound delivery in document flow. If necessary, EWM updates the stock type. For example, EWM changes the stock type in the inbound delivery from unrestricted-use stock to stock in quality inspection. For more information, see Quality Inspection [Seite 866] and Creation of Inspection Document [Seite 869].

SAP Extended Warehouse Management (SAP EWM)

510

293

SAP Online Help

20.07.2007

Activities
If you want to display the statuses QM Inspection Planning and QM Counting Planning, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Maintain Inbound Delivery. Go to the Status tab page.

SAP Extended Warehouse Management (SAP EWM)

510

294

SAP Online Help

20.07.2007

Counting
Use
The aim of counting is to check the quality of a sample of inbound deliveries. This means that counting is a quality assurance measure in the goods receipt process that you can use to ensure consistency between the quantities entered in the system and the actual quantities.

Integration
The Quality Inspection Engine [Seite 888] (QIE), an integral part of the SCM system, provides essential functions that enable a system-supported check (counting) in the inbound delivery process. Integration with an ERP system is required to enable inbound delivery notifications to be created automatically in Extended Warehouse Management (EWM).

Prerequisites
General settings for counting You have implemented the QIE and executed the following in Customizing for EWM under Cross-Process Settings Quality Management: You have assigned decision codes to decision groups. You have defined which of the available properties of the inspection object types the system is to use as dynamic criteria when creating the inspection document. You have defined a percentage that specifies how many delivery items are to be counted. You have checked that the inspection object types and their properties have been activated.

You have defined quantity intervals and value intervals in Customizing for EWM under Goods Receipt Process Counting. You have defined inspection rules. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Master Data Quality Management Maintain Inspection Rule.

Additional settings for explicit counting Storage control You have defined the following in Customizing for EWM under Cross-Process Settings Warehouse Task Define Process-Oriented Storage Control: Storage types and storage bins (basis of the counting station) External storage process steps Definition of the storage process

You have defined warehouse process types and control indicators for determining warehouse process types in Customizing for EWM under Cross-Process Settings Warehouse Task.

SAP Extended Warehouse Management (SAP EWM)

510

295

SAP Online Help

20.07.2007

You have defined warehouse products. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Master Data Product Maintain Warehouse Product.

Counting station You have defined a work center for counting (counting station). To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Master Data Work Center Define Master Data Attributes.

Features
When you change or activate an inbound delivery notification, the system first determines whether the delivery items are to be counted. To do this, it checks if an active inspection object type and inspection rule exist. Inspection object types define the inspection process. You use the inspection rule to define when a delivery item is to be counted. To do this, you draw on certain inbound delivery notification properties: Warehouse number Document type of the delivery Partner (supplier) Product Quantity interval Value interval

If a valid inspection rule exists, the system creates an inspection document, taking into account the dynamic criteria. It marks the relevant delivery item for counting. You then perform counting either explicitly or implicitly: Explicit counting You must enter the count results for the products at the counting station. The system determines the storage bin (storage type) for this counting station on the basis of the storage control settings. You can perform explicit counting only for handling units. Implicit counting The information specifying that a product must be counted is part of the warehouse task data. If a difference is determined, you must confirm the warehouse task with differences (exception code) to end the transaction. You can perform implicit counting only for unpacked products.

Activities
Explicit counting
...

1. You have changed or activated an inbound delivery notification in EWM. The system has found an active inspection object type and an inspection rule, and has created an inspection document. Create a warehouse task with reference to the inbound delivery and confirm it. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Work Scheduling Create Warehouse Task for Warehouse Request Putaway for Inbound Delivery. The system uses the storage control settings to determine the storage bin for counting for all the delivery items with an inspection document. If the system had not created an inspection document because an active inspection object type and inspection rule were not available, the delivery items would be put away immediately at the final storage bin.

SAP Extended Warehouse Management (SAP EWM)

510

296

SAP Online Help

20.07.2007

2. Call the counting station that is assigned to the storage bin for counting and enter the count results. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Execution Quality Inspection and Count. Implicit counting
...

You have changed or activated an inbound delivery notification in EWM. The system has found an active inspection object type and an inspection rule, and has created an inspection document. Create a warehouse task with reference to the inbound delivery, confirm the count results, and confirm the warehouse task. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Work Scheduling Create Warehouse Task for Warehouse Request Putaway for Inbound Delivery. The delivery items are put away immediately at the final storage bin.

SAP Extended Warehouse Management (SAP EWM)

510

297

SAP Online Help

20.07.2007

Deconsolidation
Use
You can use this function to divide up a deconsolidation handling unit (deconsolidation HU) across multiple putaway HUs. This is necessary if a deconsolidation HU contains different products that you want to put away in different storage sections.

Integration
You define the consolidation groups [Extern] in Customizing for storage control [Seite 334]. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Issue Process Define Consolidation Group.

Prerequisites

...

If EWM is to define a deconsolidation, one of the following cases must be present: The activity areas for the products within an HU are different. The activity areas for the products within an HU are the same, but the consolidation groups are different. The activity areas and consolidation groups for the products within an HU are the same, but the maximum number of warehouse tasks for the HU has been exceeded.

In Customizing, you have defined activity areas. For more information, see the IMG for EWM under Master Data Define Activity Area. In Customizing, you have defined deconsolidation rules. For more information, see the IMG for EWM under Goods Receipt Process Deconsolidation. If you want to use deconsolidation in process-oriented storage control, you must have defined the deconsolidation attributes for each activity area. For more information, see the IMG for EWM under Goods Receipt Process Deconsolidation Define Attributes for Deconsolidation for Each Activity Area.

Features
When EWM performs deconsolidation, it creates a warehouse task for each HU item, which deconsolidation then takes into account.

For example, you have a deconsolidation HU HU123 with product PROD1 for the reserve storage area RL, product PROD2 for the bulk storage area BL, and product PROD3 for the high rack storage area HL. EWM creates the following warehouse tasks: A warehouse task for the deconsolidation HU A warehouse task for each product, for deconsolidating the deconsolidation HU into three putaway HUs. Other warehouse tasks, depending on your Customizing settings (Direct or Combined Storage Control [Seite 268]).

SAP Extended Warehouse Management (SAP EWM)

510

298

SAP Online Help

20.07.2007

Special Features for Deconsolidation in Cross-Docking


When you perform deconsolidation in cross-docking, EWM distributes the contents of the deconsolidation HU as follows: EWM distributes the products in the deconsolidation HU that are not relevant for crossdocking across multiple putaway HUs, as in the standard putaway procedure. EWM distributes the products in the deconsolidation HU that are relevant for crossdocking across multiple pick-HUs.

EWM does not determine the consolidation group of the pick-HUs for products that are crossdocking-relevant from the data of the destination storage bin, rather from the data of the outbound delivery. For example, a consolidation group can correspond to the delivery in such a way that EWM assigns all products that belong to a delivery to a consolidation group as well. For more information about cross-docking, see Cross-Docking [Seite 544].

Activities
On the SAP Easy Access screen, choose Extended Warehouse Management Execution Deconsolidation in Goods Receipt.

Example
You receive a deconsolidation HU with 15 warehouse tasks (WTs), where the destination data is all assigned to the same activity area. You have set the Maximum Number of WTs in the Deconsolidation HU to ten, and the Maximum Number of WTs in the Putaway-HU to five. This means that if you are using process-oriented storage control, EWM forwards the HU to a deconsolidation station, due to the HU exceeding the permitted maximum number of WTs in the deconsolidation HU. During deconsolidation at this location, EWM creates putaway-HUs. After you have confirmed the repacking of five product-WTs into the putaway-HU, EWM proposes this HU for closure, due to the parameter Maximum Number of WTs in the Putaway-HU. This means that it also releases the HU for the following process step Putaway.

SAP Extended Warehouse Management (SAP EWM)

510

299

SAP Online Help

20.07.2007

Putaway
Use
The destination of the final putaway is the putaway of products into storage bins in the warehouse. The starting point for this is the warehouse request [Seite 109]. For the putaway, Extended Warehouse Management (EWM) determines a putaway path. EWM uses your settings to define the path that the warehouse employee should take to put the products away. Regardless of how you perform putaways in your company, you can configure EWM in such a way that the putaway activities are performed in one of the following ways: Automatically during creation of an inbound delivery Regularly at specific times Manually using overviews of the daily loads, after a request from an employee

You specify this using the Post Processing Framework. For scheduling and monitoring of the putaway operations, EWM stores a putaway status in each delivery item. This status tells you, for example, for which items putaway has already started.

Integration
Putaway uses the following: Putaway strategies [Seite 375] Slotting [Seite 277] Storage control [Seite 334]

Features
You can perform the final putaway using radio frequency devices (RF devices), or you can print the warehouse orders and enter the information for the final putaway manually. You can then enter and save the manually entered data in EWM. Both on the RF devices display and on the paper printout, the sequence of the warehouse tasks corresponds to the putaway path. If there are unplanned stock movements without a preceding document, you can create a warehouse request without a reference. If, for example, the connection between SAP R/3 and EWM is interrupted, you can create a warehouse request manually. SAP R/3 and EWM compare their data at a later point when the connection is available again. You can use EWM to allow the system to define a putaway path for the putaway, which optimizes the order of the storage bins. Storage bin sorting takes place in a logical section of the warehouse, the Putaway activity area, and refers to specific activities. When defining this path, EWM takes into account both one-way streets as well as differentiations in the various putaway strategies, for example, first drive to all the righthand bins, then to all the left-hand bins, or first drive to the standard bins, then to the reserve bins.

Warehouse Tasks for Putaway Putaway creates warehouse tasks for you, for the purpose of putting away your products. The warehouse tasks can be created in the following ways:

SAP Extended Warehouse Management (SAP EWM)

510

300

SAP Online Help

20.07.2007

Automatically by EWM You can control the time by assigning a schedule condition in the Post Processing Framework Action (PPF Action). For example, Status Packed is Set or Status Goods Receipt is Set.

Manually by a user

Putaway requires warehouse tasks in order to Specify the destination storage types, sections, and bins Specify the storage control for the destination storage type For more information about storage control, see Process- and Layout-Oriented Storage Control [Seite 334]. When EWM creates a warehouse task for putaway, it simultaneously checks whether the product to be put away is a hazardous substance [Extern]. If the product is a hazardous substance, EWM determines (according to your Customizing) the storage type you can use to put away the hazardous substance. For more information, see Hazardous Substance Master [Seite 969].

Activities
If you want to use RF devices, on the SAP Easy Access screen, choose Extended Warehouse Management Execution Log On to RF Environment. If you want to print the warehouse order, you can define this in Customizing. For more information, see the Implementation Guide (IMG) for EWM under Cross-Process Settings Warehouse Order Print.

SAP Extended Warehouse Management (SAP EWM)

510

301

SAP Online Help

20.07.2007

Creation of Warehouse Tasks for Putaway


Use
Extended Warehouse Management (EWM) automatically creates warehouse tasks [Seite 112] for the putaway based on a warehouse request for an inbound delivery [Seite 405], so that you can put away products. EWM uses a warehouse task to specify the following for the putaway: The destination storage types, sections, and bins The path to the destination storage type

Prerequisites
If you want EWM to automatically group warehouse tasks into warehouse orders, you must have made the settings in Customizing for warehouse order creation. In the Implementation Guide (IMG) for EWM, choose Cross-Process Settings Warehouse Order.

Features
EWM can create warehouse tasks for an inbound delivery in the following ways: EWM automatically creates warehouse tasks for an inbound delivery, using an action from the Post Processing Framework (PPF). You create the warehouse tasks manually.

When EWM creates a warehouse task for a warehouse request, it uses putaway strategies [Seite 375] to determine the storage bin. For more information, see Storage Bin Determination for Putaway [Seite 291]. When EWM creates a warehouse task, it uses direct or combined storage control [Seite 268] to determine whether you should put away a handling unit directly or by using interim storage bins. The warehouse task reflects the direct or combined storage control. EWM automatically groups warehouse tasks according to your Customizing settings for warehouse orders. For more information, see Warehouse Order Creation [Seite 419] EWM uses layout-oriented and process-oriented storage control, according to your Customizing settings. For more information, see Process-Oriented Storage Control [Seite 336] and Layout-Oriented Storage Control [Seite 340]. In the warehouse task, EWM specifies various activities for you to perform (for example, deconsolidation [Seite 298]), according to your Customizing settings.

Activities
If you have made settings in Customizing for PPF for the PPF action to create warehouse tasks for putaway, EWM automatically creates the warehouse task for putaway. In the IMG for EWM, choose Cross-Process Settings Delivery Processing Actions Use Assistant to Create Actions.

SAP Extended Warehouse Management (SAP EWM)

510

302

SAP Online Help

20.07.2007

If you want to create a warehouse task manually, on the SAP Easy Access screen, choose Extended Warehouse Management Work Scheduling Create Warehouse Task for Warehouse Request Putaway for Inbound Delivery. If you want to post goods receipts for all deliveries for an inbound delivery, and also want to create warehouse tasks for unloading, on the SAP Easy Access screen, choose Extended Warehouse Management Goods Receipt and Shipping Unload. When EWM creates a warehouse request warehouse task for an outbound delivery, it simultaneously updates this warehouse request. EWM carries out this update by updating the quantity in the document flow. If the quantity update leads to a change in status, EWM updates this change in the warehouse request as well.

You have an inbound delivery of 100 pieces of a product. EWM automatically creates three warehouse tasks (WT1, WT2, and WT3) for the entire quantity, based on the storage bin determination. Following creation of the warehouse tasks, the warehouse request status Putaway Planning changes to Completed. If EWM does not create warehouse tasks for the entire quantity, the Putaway Planning status is set to Partially Completed. The following table gives you an overview of the Putaway Planning status in the warehouse request.
Goods Receipt Process Product description Delivery Item Warehouse Task P-01 10 WT1 for 10 pieces

P-01

20

WT2 for 30 pieces

P-01

30

WT3 for 60 pieces

Putaway Planning Partially Completed Partially Completed Completed


Warehouse Request Status WT1 WT2 , after EWM creates WT3

, after EWM creates

, after EWM creates

SAP Extended Warehouse Management (SAP EWM)

510

303

SAP Online Help

20.07.2007

Specification of the Putaway Path


Use
You can use this function to specify a putaway path for each activity in the activity area. When Extended Warehouse Management (EWM) creates a warehouse request (WT), it specifies this putaway path. During definition of putaway paths, you can assign more than one putaway path, or you can allow activity areas to overlap. However, only one putaway path is active for each WT.

Integration
Specification of the putaway path is integrated into WT processing, which means that EWM sorts the WTs according to the putaway path.

Prerequisites
You have defined the storage bin types, descriptions, and structure. For more information, refer to the Implementation Guide (IMG) for EWM under Master Data Storage Bins. You have defined activity areas and categories, have assigned storage bins to the activity areas, and have specified the sorting sequence of the activity areas. For more information, see the IMG for EWM under Master Data Activity Areas. You have assigned an activity to a warehouse process type. For more information, see the IMG for EWM under Cross-Process Settings Warehouse Task Define Warehouse Process Type.

Features
If EWM has grouped several WTs into a warehouse order, then it sorts the WTs based on the warehouse order. This is not dependent on the product that is contained in the handling unit. If you use radio frequency devices, you can skip a destination storage bin proposed by EWM. EWM places this destination storage bin at the end of the RF display.

You cannot gain access to a destination storage bin because a colleague is currently putting away products in it. You skip the destination storage bin proposed by EWM and process the next one.

Activities
...

For your putaway, you or EWM create the necessary WTs for the warehouse request of the outbound delivery. In so doing, EWM determines the putaway path according to your settings in Customizing and saves this information in the WT. On the radio frequency device, EWM shows the destination storage bins in this predefined sequence.

Example
The following figure shows you an example of specification of the putaway path, based on a warehouse order.

SAP Extended Warehouse Management (SAP EWM)

510

304

SAP Online Help

20.07.2007

EWM has created a warehouse order that contains WTs. It has created a WT for each handling unit item. EWM creates the following putaway path:
Document Item 1 2 3 4 5 Handling Unit 1 2 1 2 3

Therefore, if you simultaneously put away several HUs, EWM sorts these across the warehouse.

SAP Extended Warehouse Management (SAP EWM)

510

305

SAP Online Help

20.07.2007

Putaway Using Radio Frequency


Use
You can execute putaways using a radio frequency presentation device (RF presentation device).

Prerequisites
You have logged on [Seite 790] in the RF environment. The destination storage bins of the warehouse orders [Seite 419] to be processed are always in the same activity area.

Features
Putaway According to Handling Unit (HU) You enter a handling unit number (HU number) and the system searches for the corresponding warehouse order or warehouse orders. Putaway According to HU (Collective) You enter more than one HU number and the system searches for the corresponding warehouse orders. Putaway According to Warehouse Order You enter a warehouse order number and the system displays the warehouse tasks assigned to the warehouse order that are to be executed.

Activities
Putaway According to Handling Unit (HU) 1. You enter a HU number. EWM thus includes the HU in the resource. 2. The system searches for the corresponding warehouse orders. 3. The system displays the following: If the system finds a WT for the entire HU, the system displays the source data (HU number, destination storage bin). If the system finds WTs for the products in the HU, then you are dealing with a distributive putaway [Extern]. The system displays the first WT it has found according to the sort sequence of the destination storage bins. The system displays the following data: Source HU Product Quantity Batch Destination HU

SAP Extended Warehouse Management (SAP EWM)

510

306

SAP Online Help

20.07.2007

Destination storage bin

If a warehouse order has more than one WT, you can do the following: You can skip a WT. You can reverse the sequence in which the system displays the WTs. You can place the displayed WT at the end of the execution.

4. You confirm the data of the HU WT or of the first product WT. 5. If a warehouse order has more than one product WT, the system displays the data of the next product WT and the action repeats itself. Putaway According to Handling Unit (Collective)
...

1. You enter all desired HU numbers. 2. You decide whether you want to putaway further in a guided manner or according to product number or warehouse task. 3. The system searches for the corresponding warehouse task. 4. The further steps correspond to steps three to five for putaway according to handling unit. Putaway According to Warehouse Order
...

1. You enter a warehouse order number. 2. The system searches for the corresponding warehouse tasks. 3. The system displays the source data (product, quantity, batch, and source storage bin) of the first product WT that belongs to the warehouse order, or the source data (HU and source storage bin) of the first HU WT that belongs to the warehouse order. If a warehouse order has more than one WT, you can do the following: You can skip a WT. You can reverse the sequence in which the system displays the WTs. You can place the displayed WT at the end of the execution.

4. You confirm the source data of the first product WT or the source data of the first HU WT. 5. The system displays the destination data of the product WT (product, quantity, batch, and destination storage bin), or the destination data of the HU WT (HU and destination storage bin). 6. You confirm the destination data of the first WT. 7. If a warehouse order has more than one WT, the system displays the source data of the next WT (product WT or HU WT), and the action repeats itself.

Exceptions to Putaway Using RF


HU WT Confirmation You can specify an exception for this process and then: Change the destination storage bin In general, skip the HU WT that is currently to be processed For example, if the aisle is blocked, you cannot get to the source storage bin or destination storage bin. During the putaway process, then, the system no longer shows you this HU WT and you do not need to confirm the source data and destination data.

SAP Extended Warehouse Management (SAP EWM)

510

307

SAP Online Help Product WT Confirmation You can specify an exception for this process and then: Change the destination storage bin Record differences

20.07.2007

For example, if a piece of the product quantity is damaged, you can enter a smaller product quantity rather than confirm the quantity. Change the batch In general, skip the product WT that is currently to be processed For example, if the aisle is blocked, you cannot get to the source storage bin or destination storage bin. During the putaway process, then, the system no longer shows you this HU WT and you do not need to confirm the source data and destination data.

SAP Extended Warehouse Management (SAP EWM)

510

308

SAP Online Help

20.07.2007

Manual Assembly of Warehouse Orders


Use
You use this function in the goods receipt process to delete warehouse tasks of different handling units (HUs) from your warehouse orders, and to group them together in a new warehouse order. This allows you to put away the HUs collectively, and Extended Warehouse Management (EWM) is able to determine the optimal putaway path.

Prerequisites
You have made sure that putaway warehouse tasks exist and are active for the entire contents of the HU. If EWM is to generate a single warehouse order for all warehouse tasks that belong to the HUs you have specified, you have made sure that the warehouse activity area and queue for these warehouse tasks are identical (see Warehouse Order Creation [Seite 419]). If you want to print warehouse orders using a PPF action, you have scheduled a corresponding PPF action.

Features
This function is optimized so that you can operate it using a hand-held scanner that is installed on a keyboard filter. You can specify multiple HUs in the entry field, one after each other. EWM shows you the specified HU in the lower part of the screen, and assigns the HU to a position field, ascending. For example, you scan three HUs. EWM assigns the HU scanned first to position one, the next HU to position two, and the HU scanned last to position three. Make sure that the position of the HU in EWM matches the physical position of the HU in the resource. When you perform putaway, EWM shows you the position in the Radio Frequency dialog (RF dialog). A traffic light shows the status of the warehouse task. Green means that you have specified a valid HU, and that warehouse tasks exist for all products in the HU. EWM has updated screen content for the total weight and total volume, and increased the number of HUs in the new warehouse order that is to be created by one. Red means that you have specified an HU, but that no warehouse task exists for at least one of the products in the HU. EWM does not update the screen content for the total weight and total volume, and does not include the HU in the new warehouse order that is to be created.

Activities
On the SAP Easy Access screen, choose Extended Warehouse Management Execution Manually Assemble Warehouse Orders. After you have specified all the HUs, choose Save. In doing this, EWM deletes all warehouse tasks of the HUs from your warehouse orders. EWM attempts to generate a warehouse order for all warehouse tasks, and saves the warehouse tasks in this order. EWM displays a success message if appropriate. If EWM generates one warehouse order only, you can take the warehouse order number directly from the message. If EWM generates multiple warehouse orders, the message only contains the number of warehouse orders. In this case, you can get the warehouse order number from the log. EWM updates the screen content.

SAP Extended Warehouse Management (SAP EWM)

510

309

SAP Online Help

20.07.2007

You can print the warehouse order in one of the following ways: Using a Post Processing Framework action Manually Choose Work Center Print Last Warehouse Order. Under Create Action, choose the PPF action you require for printing warehouse orders (see Printing Warehouse Orders and Warehouse Tasks [Seite 426]).

SAP Extended Warehouse Management (SAP EWM)

510

310

SAP Online Help

20.07.2007

Confirmation Correction
Use
For example, if you want to change a quantity specification, you can still correct warehouse tasks in the goods receipt process that have already been confirmed.

Prerequisites
You have defined a completion delay for inbound deliveries. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Receipt Process Inbound Delivery Define Delay in Completing Inbound Deliveries. You are using a document type and item type with a status profile for which you have activated the status DWM. For more information, see the IMG for EWM under Cross-Process Settings Delivery Processing Status Management Define Status Profiles.

Features
EWM delays sending a warehouse task that has already been confirmed, corresponding to the completion delay you have specified for inbound deliveries in Customizing. In accordance with the completion delay, you can still correct the actual quantity for the destination storage bin and the batch. You make your correction and specify an exception code in the warehouse task for each delivery item. When the completion delay has passed, EWM sets the status DWM for sending the completion indicator to Completed. By doing this, EWM also indirectly sets the completion status DCO for the inbound delivery to Completed. Only when the completion status DCO for an inbound delivery has status value Completed does EWM forward the confirmed warehouse task to the ERP system. Only now does the ERP system perform any necessary activities, such as for a returns process or a stock transfer order. From this point in time, you cannot make any further corrections in the confirmed warehouse task. You can schedule report /SCWM/R_PRDI_SET_DWM to set the status DWM for sending the completion indicator to Completed. For more information, see the report documentation.

If you do not specify a completion delay for inbound deliveries in Customizing, EWM immediately sets the status DWM for sending the completion indicator to Completed, and you can no longer make a confirmation correction. You can correct a warehouse task that has already been confirmed in both the user interface and in the RF environment [Seite 803]. EWM calculates the difference quantity and posts it.

For example, you have specified 11 pieces as the Act.Qty (Dest.) (destination actual quantity) and already confirmed the warehouse task. You notice that you have made a mistake, and change the Act.Qty (Dest.) to 10 pieces. EWM automatically calculates the Dest.Diff.Qty (destination difference quantity) as 1 piece, and posts this. That is, EWM performs a type of stock adjustment regarding the relevant warehouse task. For displaying the warehouse task in the user interface or in the RF environment, you can use the warehouse order, the stock identification, or the storage bin as a selection criterion.

Activities
...

SAP Extended Warehouse Management (SAP EWM)

510

311

SAP Online Help

20.07.2007

1. If you want to make a confirmation correction using the user interface, on the SAP Easy Access screen choose Extended Warehouse Management Execution Confirm Warehouse Task and then Correct the Confirmation. 2. EWM then does the following: a. Checks whether serial numbers are mandatory for the products of the warehouse task You cannot correct the confirmation for products for which a serial number requirement exists. b. Checks which authorizations you have c. Checks whether the warehouse task is locked d. Checks which inbound delivery belongs to the warehouse task (reference) 3. EWM reads the inbound delivery and checks that the completion status DCO of the inbound delivery does not yet have status value Completed. a. If the status does not yet have the status value Completed, EWM locks the inbound delivery from further warehouse activities until you have made your confirmation correction. The fields for the confirmation correction entry are ready for input, and you can make your correction. b. If the status already has the status value Completed, none of the fields are ready for input, and you cannot make a confirmation correction.

SAP Extended Warehouse Management (SAP EWM)

510

312

SAP Online Help

20.07.2007

Processing of Non-Putaway-Relevant Delivery Items


Purpose
You can use the processing of non-putaway-relevant delivery items to book goods for a warehouse request for an inbound delivery into your warehouse stock. However, in contrast to putaway [Seite 300], Extended Warehouse Management (EWM) does not generate any warehouse tasks for the warehouse request or any warehouse orders.

Prerequisites
The goods movement bin in the warehouse request into which you are booking the stock for the goods receipt must contain a valid storage bin into which you can book the product. You use an item type that does not contain any of the following status types in the status profile: Planning Putaway Putaway

For more information, see the Implementation Guide (IMG) for EWM under CrossProcess Settings Delivery Processing Status Management Define Status Profiles.

Process
...

1. You or EWM create the warehouse request for an inbound delivery [Seite 112]. Either ERP distributes an inbound delivery to EWM and EWM automatically generates a corresponding warehouse request, oryou manually generate the warehouse request in EWM. You specify all the relevant stock attributes of the product (for example, the stock type) and a goods movement bin in the warehouse request. If you have configured goods movement bin determination, EWM automatically suggests a goods movement bin. On the SAP Easy Access screen, choose Extended Warehouse Management Settings Maintain Goods Movement Bin Determination. EWM also uses the settings that you specify here to process outbound deliveries that are not relevant to picking. 2. You perform any other relevant goods receipt steps, for example, unloading. 3. You put away the products in your warehouse and you post goods receipt for the inbound delivery.

Result
EWM has generated a warehouse request for an inbound delivery. You have performed any additional goods receipt activities, you have put away the products in your warehouse, and you have posted goods receipt.

SAP Extended Warehouse Management (SAP EWM)

510

313

SAP Online Help

20.07.2007

Goods Issue
Purpose
A goods issue [Extern] from Extended Warehouse Management (EWM) is a physical departure of products from your warehouse. With a goods issue posting, you reduce the stock in the warehouse. You can use a goods issue to indicate goods deliveries to your customers. A warehouse request goods issue allows you to display your complex stock removal process steps and includes the following functions: Storage Bin Determination for Stock Removal [Seite 343] Stock Removal [Seite 317] Packing [Seite 506] Loading [Seite 608]

When you display the goods issue process using a warehouse request, you can execute the warehouse-internal processes that precede the actual goods issue, such as picking or packing, within the warehouse before you trigger the actual goods issue posting. The goods issue takes into account your warehouse arrangements, such as stock removal using pick points from a high rack storage area, as well as the process-oriented rules and procedures defined by you, such as packing during warehouse task confirmation. To simplify the search for appropriate stock, EWM offers you stock removal strategies [Seite 396]. You can remove your products from stock either directly or by using storage control [Seite 334]. You can only execute complex stock removal processes by using handling units. You can use the warehouse request to automatically trigger the goods issue processing. To do this, you use the warehouse task as the main document upon which you display all goods movements in EWM.

For more information, see Warehouse Request for Inbound Delivery or Outbound Delivery Order [Seite 112].

Prerequisites
The data for the warehouse request for outbound delivery in EWM is complete. You have defined the following basic settings in Customizing for EWM: For examples of basic settings, see Goods Receipt [Seite 263] under Prerequisites. The warehouse request is relevant for picking. You have defined a stock removal strategy in Customizing for EWM under Goods Issue Process Strategies Define Stock Removal Strategy. You have defined a stock removal control indicator in Customizing for EWM under Goods Issue Process Strategies Define Stock Removal Control Indicator.

Process
... ...

1. EWM receives a goods issue request from another system, for example an SAP system.

SAP Extended Warehouse Management (SAP EWM)

510

314

SAP Online Help

20.07.2007

2. EWM creates a warehouse request for an outbound delivery order [Seite 112], which is the starting point for the goods issue. EWM recognizes, on the item level of the warehouse request, which delivery items are relevant for stock removal with EWM.

For more information, see Creation of a Warehouse Request for an Outbound Delivery Order [Seite 116]. The availability check for the goods issue takes place on the level of the prestored components. EWM does not carry out an independent availability check, but instead assumes a purely executional function. 3. You create a warehouse request for the warehouse request for picking from your warehouse. When you create a warehouse task, the system creates corresponding warehouse orders. These warehouse orders group the warehouse tasks in accordance with the rules defined in Customizing. This means that you receive individual work packages that a worker is to carry out at a certain time (see Warehouse Order Creation [Seite 419]). You can create the warehouse task directly or let EWM create it automatically. EWM can create warehouse tasks in the following manner: By default, directly through the release of a wave Automatically, using a Post Processing Framework (PPF) action

You can create the warehouse tasks manually.

For more information, see Creation of Warehouse Tasks for Warehouse Request [Seite 412], Creation of Warehouse Tasks for Stock Removal [Seite 319], or Wave Management [Seite 766]. You can take into account batch information when creating warehouse tasks for picking. If you have not determined the batches to be picked in the warehouse request, and you want to pick one or more batches to cover the required quantity completely, you must verify these batches to the outbound delivery. In doing so, you create a new warehouse request item for each batch. 4. You either print the warehouse request with the warehouse tasks as a list, or you print all individual documents at once. If you remove the goods from the determined source storage bins to the goods issue interface, you can use this printout as the picking document.

For more information, see Printing Warehouse Orders and Warehouse Tasks [Seite 426]. 5. Once you have completed the picking, you confirm the warehouse tasks. 6. You carry out further goods issue activities, such as packing or loading. 7. For each goods issue activity, EWM creates a separate warehouse task, which you confirm after you have completed the physical activity. With this confirmation, you confirm that you have brought the goods to the goods issue interface. This records any stock differences between the required and the picked quantity.

SAP Extended Warehouse Management (SAP EWM)

510

315

SAP Online Help

20.07.2007

For more information, see Handling Differences When Picking for Warehouse Request [Seite 348]. 8. You then post the goods issue for the warehouse request. EWM updates the activity status when a step of the warehouse task processing has been completed. You can inform yourself about the outbound delivery status during the entire goods issue process.

For more information, see Creation of Warehouse Tasks for Warehouse Request [Seite 412].

Using Storage Control

For more information about goods issue processes using storage control, see Storage Control [Seite 334], Layout-Oriented Storage Control [Seite 340] , or Process-Oriented Storage Control [Seite 336].

Results
EWM reduces the storage bin stock in the source storage bin by the picked product quantity and posts this quantity to the destination storage bin.

SAP Extended Warehouse Management (SAP EWM)

510

316

SAP Online Help

20.07.2007

Stock Removal
Purpose
The stock removal process includes the picking of goods from storage bins in the warehouse and preparing them at the destination storage bin. If you use Extended Warehouse Management (EWM) for warehouse management, create a warehouse task [Extern] for all stock movements. You use stock removal transfer orders to execute stock removals. EWM groups stock removal warehouse tasks to warehouse orders. You use the printed warehouse order as a pick list for the stock removal. EWM contains stock removal strategies to simplify your search for the correct product to be removed from stock. According to the stock removal strategy, EWM selects the storage type and exact storage bin from which you can pick the product that is to be removed from stock. Regardless of how you organize stock removals in your company, you can configure EWM in such a way that the stock removal activities are performed in one of the following ways: If EWM creates a warehouse request: automatically, using a Post Processing Framework action. Regularly at set times, using the automatic wave scheduling. For more information, see Automatic Wave Assignment [Seite 773].

Process
...

1. The warehouse request [Seite 109] is a request for EWM to remove goods from stock. For more information, see Warehouse Request for Inbound Delivery or Outbound Delivery Order [Seite 112]. When EWM creates a warehouse request, you can trigger the picking of goods in EWM automatically. In so doing, EWM creates one or more warehouse task items for each item in the warehouse request. EWM automatically transfers the information concerning the picking status to the warehouse order. You then have access to the current data concerning the processing status in the warehouse. 2. You create a warehouse task for the warehouse request. 3. You use a printed warehouse request as the pick list. The warehouse request contains the corresponding warehouse tasks. 4. You confirm the warehouse task. In so doing, you confirm in EWM that the physical removal of goods is concluded. The product that is to be removed from stock is then found at the destination storage bin defined in the warehouse task. At the same time, EWM transfers the picked quantity directly to the corresponding items in the warehouse request. In addition, EWM reduces the storage bin stock in the source storage bin by the picked product quantity and posts this quantity to the destination storage bin.

Example
The following graphic clarifies the process of stock removal from the EWM-managed warehouse using a warehouse request:

SAP Extended Warehouse Management (SAP EWM)

510

317

SAP Online Help

20.07.2007

Warehouse Request

Warehouse Task

Warehouse
Storage Type 1

Item 1

Warehouse Task 1 Source Dest. Warehouse Task 2 Source Dest. Warehouse Task 3 Source Dest. Warehouse Task 4 Source Dest. Warehouse Task 5 Source Dest.

Item 2

Storage Type 2

WT 2

WT 3

Item 3 Warehouse Task 6 Source Dest. WT 4 Goods Issue Zone

To remove the product from stock, you create a warehouse task for a warehouse request to the outbound delivery order. EWM can thus create more than one warehouse task from one item in the warehouse request. This is the case, for example, if you have to pick the product for item 2 of the warehouse request from three different source storage bins to remove the product quantity specified in the warehouse request. Item 2 of the warehouse request results in the three warehouse tasks 2, 3, and 4. You use warehouse tasks 2 and 3 to move the products from storage type 1 to the goods issue zone, and you use warehouse task 4 to move products from storage type 2 to the goods issue zone.

SAP Extended Warehouse Management (SAP EWM)

510

318

SAP Online Help

20.07.2007

Creation of Warehouse Tasks for Stock Removal


Use
Extended Warehouse Management (EWM) creates warehouse tasks [Seite 112] for stock removal based on a warehouse request for outbound delivery request [Seite 405], so that you can remove products from stock. EWM uses a warehouse task to specify the following for the stock removal: The source storage types, sections, and bins The path to the destination storage type

Prerequisites
If you want EWM to automatically group warehouse tasks into warehouse orders, you must have made the settings in Customizing for warehouse order creation. For more information, see the Implementation Guide (IMG) for EWM under Cross-Process Settings Warehouse Order.

Features
EWM can create warehouse tasks for an outbound delivery in the following ways: As default, EWM creates warehouse tasks for an outbound delivery when you or EWM release a wave. EWM automatically creates warehouse tasks for an outbound delivery, using an action from the Post Processing Framework (PPF). You create the warehouse tasks manually.

When EWM creates a warehouse task for a warehouse request, it uses stock removal strategies [Seite 396] to determine the storage bin. For more information, see Storage Bin Determination for Stock Removal [Seite 343]. When EWM creates a warehouse task, it uses direct or combined storage control [Seite 268] to determine whether you should remove a handling unit from stock directly or by using interim storage bins. The warehouse task reflects the direct or combined storage control.

EWM automatically groups warehouse tasks according to your Customizing settings for warehouse orders. For more information, see Warehouse Order Creation [Seite 419] EWM uses layout-oriented and process-oriented storage control, according to your Customizing settings. For more information, see Process-Oriented Storage Control [Seite 336] and Layout-Oriented Storage Control [Seite 340]. In the warehouse task, EWM specifies various activities for you to perform (for example, packing) according to your Customizing settings.

Activities
If you have made settings in Customizing for PPF for the PPF action to create warehouse tasks for stock removal, EWM automatically creates the warehouse task for stock removal.

SAP Extended Warehouse Management (SAP EWM)

510

319

SAP Online Help

20.07.2007

For more information, see the IMG for EWM, under Cross-Process Settings Delivery Processing Actions Use Assistant to Create Actions. By default, you or EWM create warehouse tasks by releasing a wave. After a wave is generated, it can be released immediately, either automatically or manually depending on the release methods you have defined for the wave or wave template. For more information, see Processing of Waves [Seite 771]. If you want to create a warehouse task manually, on the SAP Easy Access screen, choose Extended Warehouse Management Work Scheduling Create Warehouse Task for Warehouse Request Stock Removal for Outbound Delivery Order. If you create warehouse tasks for a delivery for loading, and then want to post the goods issue, on the SAP Easy Access screen, choose Extended Warehouse Management Shipping and Receiving Load. When EWM creates a warehouse request warehouse task for an outbound delivery request, it simultaneously updates this warehouse request. EWM carries out this update by updating the quantity in the document flow. If the quantity update leads to a change in status, EWM updates this change in the warehouse request as well.

You have an outbound delivery of 100 pieces of a product. EWM automatically creates three warehouse tasks (WT1, WT2, and WT3) for the entire quantity, based on the stock determination. Following creation of the warehouse tasks, the warehouse request status Picking Planning changes to Completed. If EWM does not create warehouse tasks for the entire quantity, the Picking Planning status is set to Partially Completed. The following table provides an overview of the Picking Planning status in the warehouse request. Goods Issue Process Product description P-01 P-01 P-01 10 20 30 WT1 for 10 pieces WT2 for 30 pieces WT3 for 60 pieces Delivery Item Warehouse Task Warehouse Request Status Picking Planning Partially Completed Partially Completed Completed

SAP Extended Warehouse Management (SAP EWM)

510

320

SAP Online Help

20.07.2007

Stock Removal Path Determination


Use
You can use this function to specify a stock removal path for each activity in the activity area. When Extended Warehouse Management (EWM) creates a warehouse request (WT), it specifies this stock removal path. During definition of stock removal paths, you can assign more than one stock removal path, or you can allow activity areas to overlap. However, only one stock removal path is active for each WT.

Integration
Specification of the stock removal path is integrated into WT processing, which means that EWM sorts the WTs according to the stock removal path.

Prerequisites
You have defined the storage bin types, descriptions, and structure. For more information, refer to the Implementation Guide (IMG) for EWM under Master Data Storage Bins. You have defined activity areas and categories, have assigned storage bins to the activity areas, and have specified the sorting sequence of the activity areas. For more information, see the IMG for EWM under Master Data Activity Areas. You have assigned an activity to a warehouse process type. For more information, see the IMG for EWM under Cross-Process Settings Warehouse Task Define Warehouse Process Type.

Features
If EWM has grouped several WTs into a warehouse order, then it sorts the WTs based on the warehouse order. This is regardless of which products or HUs are on the storage bins. If you use radio frequency devices, you can skip a source storage bin proposed by EWM. EWM places this source storage bin at the end of the RF display.

You cannot gain access to a source storage bin because a colleague is currently removing products from it. You skip the source storage bin proposed by EWM and process the next one.

Activities
...

For your stock removal, you or EWM create the necessary WTs for the warehouse request for the outbound delivery order. In so doing, EWM determines the stock removal path according to your settings in Customizing and saves this information in the WT. On the radio frequency device, EWM shows the destination storage bins in this predefined sequence.

SAP Extended Warehouse Management (SAP EWM)

510

321

SAP Online Help

20.07.2007

Picking
Purpose
You can use picking to remove goods from your warehouse for a warehouse request for outbound delivery order [Seite 112]. EWM creates the corresponding warehouse tasks for the warehouse request and assigns them to one or more warehouse orders. You can use the warehouse order as the pick list.

Process
...

1. You or EWM create the warehouse tasks for the outbound delivery. In doing so, EWM uses stock determination to find the required stock. For more information, see Creation of Warehouse Tasks for Stock Removal [Seite 319] or Storage Bin Determination for Stock Removal [Seite 343]. 2. EWM allocates the individual warehouse tasks to a warehouse order and thus builds work packages for the individual warehouse workers. It thereby determines the stock removal path. For more information, see Warehouse Order Creation [Seite 419] and Stock Removal Path Determination [Seite 321]. 3. You can process and confirm the warehouse task as follows: a. You can print the individual warehouse order and process it. You can also process the warehouse orders using radio frequency devices. For more information, see Printing Warehouse Orders and Warehouse Tasks [Seite 426] and Processing Using Radio Frequency [Seite 797]. b. You can pack products during the picking process. For more information, see Pick and Pack During Picking [Seite 323]. c. You can carry out a partial picking or a complete picking. For more information, see Partial Picking [Seite 325]. d. You can enter differences that arise during picking. For more information, see Handling Differences When Picking for Warehouse Request [Seite 348].

Result
EWM has created the corresponding warehouse tasks for the warehouse request for an outbound delivery order. You have removed the products from your warehouse, transferred them to the goods issue zone or packing station, for example, and confirmed the associated warehouse tasks.

SAP Extended Warehouse Management (SAP EWM)

510

322

SAP Online Help

20.07.2007

Pick and Pack During Picking


Use
You can generate pick handling units (pick HUs) into which you can pack products during picking. Extended Warehouse Management (EWM) assigns the pick HU to a warehouse task. You or EWM transfer the pick HUs to the delivery. You thus do not need to execute any further packing for the delivery.

Prerequisites
You have created a product that is a packaging material. On the SAP Easy Access screen, choose Master Data Product Maintain Product. You have defined a packaging material. In Customizing for EWM, select Cross-Process Settings Handling Units Basics Define Packaging Material. In Customizing, determine which steps you want to execute automatically using EWM.

For more information about making settings in Customizing for the individual steps, see under Activities. For more information about packaging materials, see Packaging Materials [Seite 492].

Features
In the Implementation Guide (IMG), for the creation of a warehouse order, you can make settings for which packaging material the system should propose for picking. When EWM creates a warehouse order, you can set the packing proposals for any number of combinations of warehouse order, activity area, and movement type, as follows: Automatic creation and assignment of pick HUs When EWM creates a warehouse order, it automatically creates one or more pick HUs with the specified packaging material. It assigns the pick HUs to the warehouse tasks in the warehouse order (optional). When you confirm the associated warehouse tasks, you can manually change the pick HUs and their assignments to the warehouse tasks. Automatic proposal of packaging materials When EWM creates a warehouse order, it automatically proposes the number of pick HUs with the required packaging material. When you confirm the warehouse tasks for the warehouse order, you can confirm the proposals for the packaging materials and manually create your own pick HUs. Manual creation and assignment of pick HUs during warehouse task confirmation EWM does not create any pick HUs, nor does it determine a packaging material. You can create the pick HUs manually. When you confirm the warehouse task, you can manually assign the pick HUs to the warehouse task.

For more information about packing, see Packing During Warehouse Task Confirmation [Seite 511].

SAP Extended Warehouse Management (SAP EWM)

510

323

SAP Online Help

20.07.2007

Warehouse Task Item Split for Pick HUs


If you determine during picking of the warehouse task items that the pick HU is too small for the entire item quantity, you can split the warehouse task item and pick in a newly-created pick HU, in other words, you can execute a partial picking.

Activities
If you want EWM to automatically create and assign the pick HUs, then in Customizing for EWM, choose Cross-Process Settings Warehouse Order Define Packing Profile for Warehouse Order Creation. Define a packing profile. If you want EWM to automatically create pick HUs, select Create HUs. If you want EWM to automatically assign pick HUs to the warehouse tasks in the warehouse order, choose Assign HUs to WTs.

If you want EWM to automatically propose the number of pick HUs with the required packaging material, then in Customizing for EWM, choose Cross-Process Settings Warehouse Order Define Packing Profile for Warehouse Order Creation, and define a packing profile without choosing Create HUs or Assign HUs to WTs. If you want to manually create and assign pick HUs, you do not define a packing profile in Customizing for EWM.

For more information about the packing profile, see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings Warehouse Order Define Packing Profile for Warehouse Order Creation.

SAP Extended Warehouse Management (SAP EWM)

510

324

SAP Online Help

20.07.2007

Partial Picking
Use
In a partial picking, Extended Warehouse Management (EWM) can create a corresponding warehouse task for an outbound delivery, even though it cannot completely fill all items for the outbound delivery.

By default, EWM executes a partial picking. If the available quantity in the warehouse is not sufficient to fill all items of the outbound delivery, you can prevent the creation of a warehouse task.

Prerequisites
If you want to execute a complete picking, you need to have made the settings for complete picking for warehouse order, in Customizing for Extended Warehouse Management (EWM) under Cross-Process Settings Warehouse Task Define Warehouse Process Type.

Features
You use the standard setting (partial picking) so that EWM creates a warehouse task even though it cannot completely fill all items of the outbound delivery. You use the complete picking, so that EWM does not create a warehouse task during a background processing, such as wave release or processing using a Post Processing Framework action (PPF action). so that EWM warns you in the user interface for warehouse task creation for warehouse requests, that the required quantity is underfilled and that a complete picking is required. You can cancel the warehouse task creation or save the warehouse task created internally.

You have created an outbound delivery with two products of 50 pieces each. Since creation of the outbound delivery, you have taken from the warehouse 10 pieces from the product in the second outbound delivery item, so that only 40 pieces remain. If you create a warehouse task for this outbound delivery, EWM notifies you that it cannot completely fill the picking requirements.

Activities
The following table provides an overview of the possibilities within partial picking. Partial picking is allowed EWM automatically adjusts the outbound delivery quantity to the warehouse task quantity. Procedure In Customizing for Extended Warehouse Management, choose Cross-Process Settings Exception Handling Define Exception Codes and then Delivery Adjustment in Case of Results EWM transfers the warehouse task quantity as warehouse request quantity to the corresponding items of the warehouse request.

SAP Extended Warehouse Management (SAP EWM)

510

325

SAP Online Help Differences. Define the delivery adjustment in the case of differences. You manually adjust the outbound delivery quantity to the picked quantity. On the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery Maintain Outbound Delivery Order. Choose Change Mode and then Adjust Delivery Quantity. Adjust the outbound delivery quantity to the warehouse task quantity. Neither you nor EWM adjust the outbound delivery quantity to the picked quantity.

20.07.2007

EWM transfers the warehouse task quantity as warehouse request quantity to the corresponding item of the warehouse request.

EWM has not yet completely picked the outbound delivery. You can create additional warehouse tasks so that EWM can fill all items of the outbound delivery.

SAP Extended Warehouse Management (SAP EWM)

510

326

SAP Online Help

20.07.2007

Pick Denial
Purpose
If Extended Warehouse Management (EWM) creates a warehouse task with reference to a warehouse request for an outbound delivery order, it is possible that EWM cannot create a new warehouse task, or can only create a warehouse task with a partial quantity. This is caused by one of the following reasons: You have performed a storage bin denial. EWM cannot find any, or not enough, stock to fulfill the requested quantity of the warehouse request.

In these cases there is a pick denial.

Prerequisites
For the case that EWM cannot completely fulfill the requested quantity of the warehouse request, you have not specified that warehouse task creation should be canceled. This means that the Business Add-In (BAdI) for the outbound delivery (/SCWM/TO_CREATE) does not use the method ABORT to cancel warehouse task creation. For more information, see the Implementation Guide (IMG) for EWM under Business Add-Ins (BAdIs) for Extended Warehouse Management Cross-Process Settings Warehouse Task BAdI: WT Creation. In Customizing, you have activated pick denial at warehouse number level. For more information, see the IMG for EWM under Goods Issue Process Pick Denial Activate Pick Denial at Warehouse Number Level. In Customizing, you have activated pick denial at warehouse process type level. For more information, see the IMG for EWM under Goods Issue Process Pick Denial Activate Pick Denial at Warehouse Process Type Level. You have defined your own exception codes for calling exception handling, and have assigned these to the internal exception codes defined by SAP. For more information, see the IMG for EWM under Cross-Process Settings Exception Handling Define Exception Codes and under Goods Receipt Process Pick Denial Assign Internal Exception Codes to Exception Codes.

Process
...

1. You or EWM want to create a warehouse task. However, EWM cannot create a new warehouse task, or can only create a warehouse task with a partial quantity. You can create a warehouse task using the user interface for stock removals for the outbound delivery order (online mode) or as a background job (background mode). You can start a background job, for example, using a Post Processing Framework action or a wave release. 2. EWM compares the requested quantity with the warehouse task quantity. If the system determines differences, it performs exception handling according to your Customizing settings. If you have specified an action in Customizing, for example, adjust the quantity in the warehouse request to the picked quantity, EWM triggers an alert and creates a workflow task. You or EWM perform the following:

SAP Extended Warehouse Management (SAP EWM)

510

327

SAP Online Help

20.07.2007

If you create the warehouse task in online mode, EWM displays a warning, depending on your Customizing settings, informing you that a pick denial has occurred. You can proceed as follows: Confirm the action suggested by your Customizing settings by choosing Save . EWM executes a pick denial and executes a workflow in the background. Change the action suggested by your Customizing settings and then choose Save . EWM executes a pick denial and executes a workflow in the background. Execute the workflow using the action proposed by the system suggested by your Customizing settings, by choosing SAP Office Folders Inbox, or delete it and create a new warehouse task, for example if you still have stock in another storage type.

If EWM creates the warehouse task in background mode, it triggers a pick denial according to your Customizing settings, and performs any follow-up activity in the background. If you use wave management, EWM also writes an entry into the wave management log, informing you that EWM could not create a warehouse task, or could only create a warehouse task with a partial quantity.

3. Depending on your Customizing settings, EWM sends a message to ERP about the pick denial.

EWM does not send a message to ERP for a direct outbound delivery order. EWM only adjusts the outbound delivery quantity for the direct outbound delivery order.

Result
Depending on your Customizing settings, EWM has executed the action for pick denial in the background. The system did not execute an action. The system adjusted the quantity in the warehouse request to the picked quantity, and sent a message about the pick denial to ERP if required.

For more information about reporting a change to an outbound delivery, see Processing of Outbound Deliveries [Seite 253] under Notification of an outbound delivery change to the ERP system.

SAP Extended Warehouse Management (SAP EWM)

510

328

SAP Online Help

20.07.2007

Cancellation of Picking
Use
If you have picked too much, for example, or if you require previously picked stock more urgently for another outbound delivery, you can cancel an outbound delivery either partially or completely.

Prerequisites
If you want to release stock and simultaneously create a warehouse task (WT) in the background, you need to have performed the following in the Customizing settings for Extended Warehouse Management (EWM): You have defined the warehouse process type for the cancellation of picking. For more information, see the Implementation Guide (IMG) for EWM under Goods Issue Process Cancel Picking Define Warehouse Process Type for Putback. You have defined the warehouse process type for the cancellation of picking as a default value. For more information, see the IMG for EWM under Goods Issue Process Cancel Picking Define Warehouse Number Control for Putback.

Features
EWM cancels previously picked stock of warehouse request items (WR items) or handling units (HUs), as well as reserved stock of WTs. EWM releases the assignment of picked or reserved stock from the WR items, HUs or WTs. This makes the stock freely available again. For packed stock, EWM can only release stock for the highest-level HU. In addition, EWM can only release stock for complete HUs. If EWM releases the assignment of a stock, the system can also create a new WT at the same time. If EWM is creating the WT in the foreground, the system proceeds as follows:
...

1. EWM starts by releasing the stock. 2. If the stock is unpacked, EWM then calls the transaction for moving products. If the stock is packed, EWM calls the transaction for moving HUs. 3. You define the new WT by creating storage bins or the warehouse process type for the new WT, for example. If EWM is creating the WT in the background, the system releases the stock and simultaneously creates a new WT with the specified warehouse process type.
...

On the Warehouse Request Items tab page, EWM gives you information that is relevant for the cancellation of picking for the WR item. On the Stock tab page, EWM gives you information about the stock, such as where the different stock is located in the warehouse. On the Open Product WT tab page, EWM displays the open product WTs of the WR items.

Activities
Release Stock From One or More WR Items
You can cancel stock that has already been picked for one or more WR items. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Execution Cancel Picking. In the Document Number field for the search, you enter the outbound delivery that contains the WR item that you want to cancel. EWM shows you all WR items that belong to this outbound delivery. You can choose between the following options:
...

SAP Extended Warehouse Management (SAP EWM)

510

329

SAP Online Help

20.07.2007

You can release the entire picked delivery quantity for a WR item. To do this, on the Warehouse Request Items tab page you select the WR item that you want to cancel, and then choose Release Stock. You can cancel the picked delivery quantity of a selected stock in the WR item only. To do this, on the Warehouse Request Items tab page, select the WR item that contains the corresponding stock. On the Stock tab page you then select the stock that you want to cancel, and then choose Release Stock. You can cancel a partial quantity of the picked delivery quantity of a selected stock in the WR item only. To do this, on the Warehouse Request Items tab page, select the WR item that contains the corresponding stock. In the Cancel Quantity field on the Stock tab page, you then specify the delivery quantity that is to be cancelled for this stock. If you are working with serial number requirement Serial Numbers in Inventory Management [Seite 585], you can do the following: You first specify the delivery quantity to be cancelled in the Cancel Quantity field and then choose Serial Numbers. EWM displays the serial numbers corresponding to the cancel quantity. You select the serial numbers that you want to cancel. You start by choosing Serial Numbers. EWM displays all the serial numbers for the selected stock. You select the serial numbers that you want to cancel. EWM automatically calculates the delivery quantity that you have to cancel, and displays it in the Cancel Quantity field.

Release Stock From One or More HUs


You can cancel stock that has already been picked for one or more HUs. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Execution Cancel Picking. In the Handling Unit Identification field for the search, you enter the HU that you want to cancel. You can release the entire picked delivery quantity for an HU. To do this, on the Handling Unit tab page you select the HU that you want to cancel, and then choose Release Stock. If you have packed multiple stocks into an HU, EWM displays the corresponding information on the Stock tab page. However, you cannot edit this data. If you want to cancel a partial quantity of an HU only, you first have to repack the HU. To do this, on the Handling Unit tab page choose Repack HU (see Packing in the Work Center [Seite 506]).

Cancel WTs From One or More WR Items


You can cancel stock that has already been reserved for one or more WTs. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Execution Cancel Picking. In the Document Number field for the search, you enter the outbound delivery that contains the WR item whose WT you want to cancel. EWM shows you all WR items that belong to this outbound delivery. You can choose between the following options:
...

You can cancel the entire reserved delivery quantity for a WR item. To do this, on the Warehouse Request Items tab page you select the WR item whose WTs you want to cancel, and then choose Cancel WT. EWM then cancels all WTs that belong to the selected WR item. You can cancel the reserved delivery quantity of a selected WT in the WR item only. To do this, on the Warehouse Request Items tab page, select the WR item that contains the corresponding WT. On the Open Product WT tab page you then select

SAP Extended Warehouse Management (SAP EWM)

510

330

SAP Online Help

20.07.2007

the WT that you want to cancel, and then choose Cancel WT. EWM then cancels the selected WTs only.

Cancel WTs From One or More HUs


You can cancel stock that has already been reserved for one or more HUs. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management Execution Cancel Picking. In the Handling Unit Identification field for the search, you enter the HU that you want to cancel. On the Handling Unit tab page, you choose the corresponding HUs and then choose Cancel WT. EWM then cancels all open WTs that belong to these HUs.

Release Stock and Create WT Simultaneously (WR Item or HU)


Corresponding to the above descriptions for releasing stock for WR items and HUs, EWM can simultaneously release stock and create new WTs (either in the foreground or in the background). To do this, follow the descriptions above for releasing stock. However, instead of choosing Release Stock, you choose Release Stock + Create WT.. You then select either Release Stock + WT in Foreground or Release Stock + WT in Background from the dropdown box.

SAP Extended Warehouse Management (SAP EWM)

510

331

SAP Online Help

20.07.2007

Processing of Non-Picking-Relevant Delivery Items


Purpose
You can use the processing of non-picking-relevant delivery items to remove goods from your warehouse for a warehouse request for an outbound delivery order [Seite 112]. However, in contrast to picking, Extended Warehouse Management (EWM) does not generate any warehouse tasks for the warehouse request or any warehouse orders.

Prerequisites
The goods movement bin in the warehouse request from which you are booking out the stock for the goods issue must contain a valid storage bin in which a sufficient quantity of the product is available. You use an item type that does not contain any of the following status types in the status profile: Planned Picking Picking

For more information, see the Implementation Guide (IMG) for EWM under CrossProcess Settings Delivery Processing Status Management Define Status Profiles.

Process
...

1. You or EWM create the warehouse request for an outbound delivery order. Either ERP distributes an outbound delivery to EWM and EWM automatically generates a corresponding warehouse request, or you manually generate the warehouse request in EWM as a direct outbound delivery order [Seite 167]. You specify all the relevant stock attributes of the product (for example, the stock type) and a goods movement bin in the warehouse request. If you have configured goods movement bin determination, EWM automatically suggests a goods movement bin. On the SAP Easy Access screen, choose Extended Warehouse Management Settings Maintain Goods Movement Bin Determination. EWM also uses the settings that you specify here to process inbound deliveries that are not relevant to putaway. If you generate the warehouse request manually, choose one of the following options: You specify the items with their stock attributes and quantities on the Items tab page. On the HU tab page, you choose the Create and Save pushbuttons and specify a handling unit (HU) and an item type. Then EWM automatically creates the corresponding items with their stock attributes and quantities.

2. You remove the products from your warehouse and perform any other relevant goods issue steps, for example, loading for transportation. 3. You post the goods issue for the outbound delivery order.

SAP Extended Warehouse Management (SAP EWM)

510

332

SAP Online Help

20.07.2007

Result
EWM has generated a warehouse request for an outbound delivery order. You have removed the products from your warehouse, posted the goods issue (for example in sell from stock) or performed additional goods issue activities, and have then posted goods issue.

SAP Extended Warehouse Management (SAP EWM)

510

333

SAP Online Help

20.07.2007

Storage Control
Use
You can use the process-oriented as well as layout-oriented methods for storage control. The goal of storage control is to display your complex putaway or stock removal process steps based on your processes or your layout data. During putaway or stock removal, an individual process step can be executed on single level basis or on multi level basis (that is, through intermediate storage types). You can combine the process-oriented storage control with the layout-oriented storage control. Here, EWM always executes the process-oriented storage control first. The layoutoriented storage control then checks whether the sequence of putaway process steps is possible in layout view, and if required, adjusts the flow of the putaway or stock removal.

Based on the process-oriented storage control, EWM determined the following putaway process flow: Unloading at door Counting at counting station Checking the quality Executing value-added services Putaway in high rack storage area

The layout-oriented storage control determines that a direct putaway in the high rack storage area is not possible and that the putaway must occur with the use of an identification point. Unloading at door Counting at counting station Identification of goods at the ID point [Extern] Putaway in high rack storage area

Integration
Extended Warehouse Managment (EWM) uses the delivery to determine, via delivery type and delivery item among others, the warehouse process type. This contains the procedure, in other words, the putaway or stock removal process with different activities. EWM transfers this operation to the handling unit to be put away or removed from stock. The handling unit thus contains the information concerning what process steps are required for the putaway or stock removal.

Prerequisites
You have defined the following in Customizing for the putaway: Paramaters that specify the work station determination for the next function (for example, counting) within the goods receipt process The following parameters are possible:

SAP Extended Warehouse Management (SAP EWM)

510

334

SAP Online Help

20.07.2007

Source storage type Destination activity area or destination storage type Warehouse process type Handling unit type

Determination of the warehouse process type, using the delivery type and delivery item type, among others.

Features
For information about the features of storage control, see Process-Oriented Storage Control [Seite 336] and Layout-Oriented Storage Control [Seite 340].

SAP Extended Warehouse Management (SAP EWM)

510

335

SAP Online Help

20.07.2007

Process-Oriented Storage Control


Use
You use this type of storage control to map complex putaways or stock removals. In doing so, you combine your storage process steps into one storage process. You can also trace the status of the individual process steps.

Process-oriented storage control only operates with handling units.

Integration
For more information about integration, see Storage Control [Seite 334].

Prerequisites
For more information about the prerequisites, see Storage Control [Seite 334].

Features
You define the process steps for your complex storage process. A process step is, for example, unloading, counting, or deconsolidating [Seite 298]. Extended Warehouse Management (EWM) recognizes internal process steps predefined by SAP and external steps that you can define yourself. Your external process stesps can base themselves on internal ones. In addition, internal or external process steps can be simple, such as unloading, or combined, such as deconsolidating. For more information, see Direct and Combined Storage Control [Seite 268]. The process steps for the processes Counting and Deconsolidating predefined by SAP can be dynamic [Extern]. During goods receipt or goods issue, EWM copies the predefined process steps from the storage process type to the handling unit. EWM assigns these process steps to a handling unit as soon as it has created or changed them.

Activities
For Customizing of process-oriented storage control, in the Implementation Guide (IMG) for EWM, choose Cross-Process Settings Warehouse Task Define Process-Oriented Storage Control.

SAP Extended Warehouse Management (SAP EWM)

510

336

SAP Online Help

20.07.2007

Direct and Combined Storage Control (Stock Removal)


Use
If you want to execute a direct stock removal, you do not have to define anything in the process-oriented storage control [Seite 336]. If you want to define complex stock removal processes, you have to use a combined processoriented storage control. Extended Warehouse Management (EWM) uses this during creation of a warehouse task to determine the intermediate storage types (for example, packing station). For information about integration and the prerequisites, see Storage Control [Seite 334] .

Features
Direct Storage Control for Stock Removal If EWM determines that you are to pick a handling unit (HU) directly, it creates a warehouse task for this HU that determines the way from the source storage type to the destination storage type. For more information about updating the status, see Updating the Outbound Delivery Order in the GI Process [Seite 339]. The following graphic shows you the relationship between direct putaway and creation of warehouse tasks.
Goods Issue Area

Source Storage Type 0010

Warehouse Task 1

Destination Storage Type 9020

Source Storage Type 0020

Warehouse Task 2

Destination Storage Type 9021

Combined Storage Control for Stock Removal If EWM determines that you are to pick a HU from stock using one or more intermediate storage types, it creates one warehouse task per route section for this HU. One warehouse task that describes the route from source storage type to intermediate storage type

SAP Extended Warehouse Management (SAP EWM)

510

337

SAP Online Help

20.07.2007

Irrespective of your settings in Customizing, EWM also creates a warehouse task per product contained in the HU. Based on your settings in Customizing, one warehouse task from the intermediate storage type to the next intermediate storage type, or to the final destination storage type.

You can carry out different activities at the intermediate storage types. For example, within a stock removal process, at an intermediate storage type, you can distribute HUs containing different products to stock removal HUs. In combined stock removal, you can determine the final destination storage type either right at the beginning of your stock removal process, or later. EWM manages the intermediate storage types in the same way as standard storage types. For example, you can break these down into storage sections and storage bins. For more information about updating the status, see Updating the Outbound Delivery Order in the GI Process [Seite 339]. The following graphic shows you the relationship between combined stock removal and creation of warehouse tasks.

Intermediate Storage Type 8000

Goods Issue Area

Source Storage Type 0010

Warehouse Task 1.1

Intermediate Storage Type 8010

Warehouse Task 1.2

Destination Storage Type 9020

Source Storage Type 0020

Warehouse Intermediate Task 2.1 Storage Type 8020

Warehouse Task 2.2

Intermediate Storage Type 8030

Warehouse Task 2.3

Destination Storage Type 9021

SAP Extended Warehouse Management (SAP EWM)

510

338

SAP Online Help

20.07.2007

Updating the Outbound Delivery Order in the GI Process


Use
Extended Warehouse Management (EWM) updates the outbound delivery order corresponding to the goods issue activities (GI activities).

Features
EWM updates the outbound delivery order for the following GI processes:
You:

Unpacked stock a. You or EWM generate the first product warehouse task (product WT). EWM sets the status Picking Planning in the outbound delivery order. b. You confirm the first product WT for picking. EWM sets the status Picking in the outbound delivery order. If the destination location in the product WT is a storage bin at the door or a transportation unit (TU), EWM sets the status Unloading in the outbound delivery order.

...

Packed stock a. You or EWM generate the first product WT. EWM sets the status Picking Planning in the outbound delivery order. b. You confirm the first product WT for picking. EWM sets the status Picking in the outbound delivery order. c. You pack the stock. d. You or EWM generate the related loading warehouse task (loading WT), meaning the destination location corresponds to a bin at the door or to a TU. e. You confirm the loading WT. f. EWM sets the status Loading in the outbound delivery order.

SAP Extended Warehouse Management (SAP EWM)

510

339

SAP Online Help

20.07.2007

Layout-Oriented Storage Control


Use
You can use the layout-oriented storage control if stock movements in your warehouse do not travel from a source storage bin to a destination location directly, rather travel via intermediate storage bin.

The layout-oriented storage control only operates with handling units. One exception is the process display with picking or identification points. You use layout-oriented storage control in the material flow system [Seite 820] to define conveyor segments.

Integration
For more information about integration, see Storage Control [Seite 334].

Prerequisites
For more information about the prerequisites, see Storage Control [Seite 334].

Features
For layout-oriented storage control, you define external warehouse process steps for your warehouse, including identification points [Extern] and pick points [Extern].

For example, you have a high rack storage area. If you want to move a product pallet from storage bin A (goods receiving area) to storage bin B (high rack storage area), the system should execute a contour and weight check to ensure that the product pallet can be put away in the high rack storage area safely. For this activity, Extended Warehouse Management (EWM) splits the warehouse order into two: one from storage bin A to identification point I, and a second from identification point I to storage bin B. You can move your goods using a pick point during picking.

Activities
For Customizing of layout-oriented storage control, in the Implementation Guide (IMG) for EWM, choose Cross-Process Settings Warehouse Task Layout-Oriented Storage Control.

SAP Extended Warehouse Management (SAP EWM)

510

340

SAP Online Help

20.07.2007

Stock Determination
Use
You use stock determination to apply stock removal strategies during picking and stock transfers, based on predefined settings in Customizing. Based on the recorded product requirements, Extended Warehouse Management (EWM) determines in which sequence and from which storage types and stocks you should remove the desired product. EWM executes stock determination during creation of the warehouse task. In so doing, EWM takes into account own stocks, consignment stocks, and, in the case of internal movements, different stock types.

Prerequisites
You have set stock determination groups in Customizing for EWM under Cross-Process Settings Stock Determination Maintain Stock Determination Groups, and have saved these groups in the master record so that EWM can execute stock determination for a product. You have made the settings in Customizing for EWM under Cross-Process Settings Stock Determination Set Stock Determination, for a stock determination strategy that the system uses to reduce stock. In so doing, you define a valuation to evaluate stocks of different owners or different stock types in a different manner.

For more information about Customizing for stock determination, see the Implementation Guide (IMG) for EWM under Cross-Process Settings Stock Determination Maintain Stock Determination Groups Cross-Process Settings Stock Determination Set Stock Determination

Features
In EWM, stock determination occurs in the background during creation of warehouse tasks.

Stock Determination Strategies


You can define the following stock determination strategies: Stock Determination Dominates During stock removal, EWM considers the warehouse number stock characteristics Owner and Stock Type as defined by you. In doing so, it uses the stock removal sequence to check the existing stocks for the corresponding stock. The stock removal sequence arises from prioritizing individual stocks according to the valuation you have defined. EWM first searches through existing stocks according to the stock characteristics that have the highest number of points. If the required stock is larger than the stock found, EWM searches the existing stocks according to the stock characteristics that have the next highest number of points. EWM continues this process until it finds enough stocks for the required stock, or it notifies you that it can only find a portion of the required stock.

SAP Extended Warehouse Management (SAP EWM)

510

341

SAP Online Help EWM Dominates

20.07.2007

During stock removal, EWM considers all allowed stocks, regardless of the stock characteristic of the warehouse number. It stores the required quantities and in so doing, only takes into account the stock removal rule defined in EWM, such as FIFO [Extern]. In this case, EWM removes the oldest quant from stock, irrespective of whether this is an own stock or a consignment stock. You can also use the stock determinations number of points as sort criterion in the stock removal rule, so that for example, the stocks found per storage type are removed from stock according to descending number of points.

Activities
In Customizing for EWM under Cross-Process Settings Stock Determination Maintain Stock Determination Groups, define the stock determination strategy (stock determination dominates or EWM dominates).

Example
You define a stock determination strategy that you use during replenishment activities to firstly remove own stock (owner GLENN) and then to remove consignation stock for owner SCHMIDT (owner SCHMIDT). To do this, you define the following in Customizing for EWM: Maintain stock determination group You define the stock determination group 01 for warehouse 001, using the stock determination strategy Stock Determination Dominates. Set stock determination Party Entitled to Dispose GLENN GLENN Activity Replenish ment Replenish ment Stock Determination Group 01 01 Current Number 1 2

Warehouse Number 001 001

Stock Ch Owner Owner

The system uses your stock determination strategy to search for the stock determination group 01. If you have defined the strategy Stock Determination Dominates for the stock determination group 01, EWM first searches the warehouse for own stock according to the set stock removal strategy. If EWM cannot fill the required quantity for the warehouse task, it also searches for stocks from owner SCHMIDT and uses stocks found here as well, to fill the warehouse tasks required quantity. If you have defined the strategy EWM Dominates for the stock determination group 01, EWM searches the warehouse for own stock and for stock from owner SCHMIDT, according to the set stock removal strategy. You define the stock removal sequence by using the storage type search sequence and the stock removal strategy, such as FIFO. You have made settings in Customizing for stock determination to define valuation points for the individual owners, and thus have undertaken a prioritization. You can use this prioritization to sort stocks for a storage type or storage type group.

SAP Extended Warehouse Management (SAP EWM)

510

342

SAP Online Help

20.07.2007

Storage Bin Determination for Stock Removal


Use
The aim of storage bin determination for stock removal is to determine storage bins and stock for stock removals and internal movements. Here, for example, the system uses parameters from the product master that you have defined manually or those that the system has determined in slotting [Seite 277]. You can define the business strategy according to which the storage bin determination for stock removal is to run, for example, FIFO (First In, First Out). You make the settings for these stock removal strategies [Seite 396] in Customizing. Storage bin determination for stock removal occurs automatically when warehouse tasks (WTs) are created.

Prerequisites
You have defined a stock removal rule in Customizing for Extended Warehouse Management (EWM) under Goods Issue Process Strategies Specify Stock Removal Rule. You have defined a storage type search sequence in Customizing for EWM under Goods Issue Process Strategies Specify Storage Type Search Sequence. You have assigned the storage type search sequence in Customizing for EWM under Goods Issue Process Strategies Determine Storage Type Search Sequence for Stock Removal. You have assigned the stock removal rule to the storage type in Customizing for EWM under Master Data Define Storage Type. Alternatively, you can assign the stock removal rule under Goods Issue Process Strategies Determine Storage Type Search Sequence for Stock Removal.

Features
Determination of Stock Removal Search Sequence and Stock Removal Rule
The stock removal search sequence contains information about the storage types in which the system is to search for stock and the order in which it is to sort the stock found. The stock removal rule specifies the order in which the system is to sort the individual quants. The system determines the stock removal search sequence on the basis of the parameters from the WT. In Customizing, you can link a stock removal rule to a stock removal search sequence. This means that the stock removal rule is fixed for all storage types belonging to the stock removal search sequence. If you have not linked the stock removal rule and the stock removal search sequence to one another, the system uses the stock removal rule that you have defined for the storage type or the storage type group. If you enter the storage type or the storage type group manually, the system calls the determination of stock removal search sequences to determine the stock removal rule. You can use the BAdIs in the /SCWM/ES_CORE_RMS enhancement spot to make changes to the result.

Determination of Storage Type or Storage Type Group


The system uses the stock removal search sequence that was found to determine the storage type or the storage type group in which it is to search for stock.

SAP Extended Warehouse Management (SAP EWM)

510

343

SAP Online Help

20.07.2007

Selection of Quants
The system uses the storage type or the storage type group that was found to select the stock. You can use the BAdIs in the /SCWM/ES_CORE_RMS enhancement spot to make changes to the result.

Sorting the Quants


The system uses the stock removal rule that was found to sort the stock that was determined. You can use the BAdIs in the /SCWM/ES_CORE_RMS enhancement spot to make changes to the result.

Selection of a Quant
The system chooses the first quant that was found, and checks it. If it cannot use this quant, for example, because the quantity is insufficient or the storage bin is locked for stock removal, the system takes the next quant, and so on.

SAP Extended Warehouse Management (SAP EWM)

510

344

SAP Online Help

20.07.2007

Work Center Determination in Goods Issue


Use
In Extended Warehouse Management (EWM), you can have the system determine a work center [Seite 35] in goods issue. You can specify various criteria for this determination.

Prerequisites
In Customizing for EWM, you have set the Determine WkCtr indicator in the used warehouse order creation rule, under Extended Warehouse Management Cross-Process Settings Warehouse Order Define Creation Rule for Warehouse Orders.

Features
You can define the following criteria for the determination: Warehouse number Route Activity area Consolidation group

If you have set the indicator Determine WkCtr in the used warehouse order creation rule, EWM uses your criteria during warehouse order creation [Seite 419]. You can specify any number of criteria for the determination. EWM first attempts to find a work center matching your criteria. If it cannot find a work center, it uses the optimization that you have specified in Customizing for EWM under Extended Warehouse Management Master Data Work Center Optimize Work Center Determination in Goods Issue. You also specify at least the storage bin for the work center determination. You can also specify the storage type or storage section. If you specify the storage type or storage section, the storage type must have the storage type role Work center. If you only specify a storage type, this has to have the putaway rule Consolidation Group. EWM checks these settings when you save your details. If you do not specify a storage type or storage section, EWM determines these values when you save your details.

Activities
On the SAP Easy Access screen, choose Extended Warehouse Management Master Data Work Center Determine Work Center in Goods Issue (/SCWM/PACKSTDT).

Result
EWM analyzes the details that you enter here. EWM assigns the determined destination data storage type, storage section and storage bin to the warehouse tasks that it bundles using the warehouse order creation rule used here. This enables you to have the system determine a special work center for packing, depending on the route, for example.

SAP Extended Warehouse Management (SAP EWM)

510

345

SAP Online Help

20.07.2007

Replenishment Control
Use
You use replenishment control to fill up a picking area in accordance with the demand for products that you pick in this area. The data can come from the following sources: Slotting [Seite 277]

Calculation of the minimum quantity [Extern] and the maximum quantity [Extern] as well as the minimum replenishment quantity [Extern] at storage type level or at fixed storage bin level Open warehouse requests in accordance with selection Manually entering the minimum and maximum quantity as well as the minimum replenishment quantity

Prerequisites
You have executed the following in Customizing under Extended Warehouse Management Internal Warehouse Processes Replenishment Control Activate Replenishment Strategies in Storage Types: You have activated the required replenishment strategy. If you want to work with picker-directed replenishment, you have set the PckrDrvn Repl. indicator for direct replenishment and have, optionally, restricted storage types. If the system is to automatically create a warehouse task when executing replenishment, you have set the WT Immed. indicator. Otherwise, the system creates a warehouse request or changes an existing warehouse request.

You have defined a stock removal control indicator for the warehouse number in Customizing under Extended Warehouse Management Goods Issue Process Strategies Define Stock Removal Control Indicator. You have defined tolerances and replenishment levels (fixed storage bin level or storage type level) in Customizing under Extended Warehouse Management Master Data Define Storage Type. You have also defined the following: If you want to work with replenishment at storage type level, you have defined the minimum quantity and the maximum quantity in the warehouse product master. If you want to work with replenishment at fixed storage bin level, you have defined fixed storage bins for your products as well as a minimum and a maximum quantity for each bin in the master data for Extended Warehouse Management under Storage Bin Maintain Fixed Storage Bin.

If the system is to round replenishment quantities [Extern], you have defined a minimum replenishment quantity in the warehouse product master. You can only define the minimum replenishment quantity at storage type level, but the system can also use it at fixed storage bin level. You have defined a default stock type for replenishment in Customizing under Extended Warehouse Management Master Data Define Warehouse Number Control.

SAP Extended Warehouse Management (SAP EWM)

510

346

SAP Online Help

20.07.2007

Features
The following types of replenishment control are available: Planned replenishment You can start planned replenishment either interactively or in the background. The system calculates the replenishment in accordance with the defined minimum quantity and maximum quantity. Replenishment control is triggered when the stock is less than the minimum quantity. The system rounds down the replenishment quantity, in other words, the quantity of the warehouse task or the warehouse request, to a multiple of the minimum replenishment quantity. Order-related replenishment You can start order-related replenishment either interactively or in the background. The system calculates the replenishment in accordance with the quantity of the selected open warehouse requests. Replenishment control is triggered when the stock is less than the required quantity. The system rounds up the replenishment quantity to a multiple of the minimum replenishment quantity. The maximum quantity can be exceeded. Automatic replenishment The system starts automatic replenishment in the background when you confirm a warehouse task. It calculates the replenishment in accordance with the maximum and minimum quantity. Replenishment control is triggered when the stock is less than the minimum quantity. The system rounds down the replenishment quantity to a multiple of the minimum replenishment quantity. Direct replenishment Direct replenishment is only possible in fixed storage bin scenarios. It is started during a bin denial when an exception code refers to the internal process code Replenishment. The system calculates the replenishment in accordance with the maximum and minimum quantity. Here it assumes that the quantity at the storage bin is zero. The system rounds down the replenishment quantity to a multiple of the minimum replenishment quantity. Direct replenishment can be performed by the picker (picker-directed replenishment). In this case, a warehouse task is displayed for the replenishment as the next item to be processed in the pickers warehouse order. As a prerequisite, the system must have found stock in the permitted storage types. Picker-directed replenishment is only possible in radio frequency scenarios.

We recommend that you use picker-directed replenishment if the reserve storage area is situated close to the picking area.

Activities
To start planned replenishment or order-related replenishment, on the SAP Easy Access screen, choose Extended Warehouse Management Work Scheduling Schedule Replenishment.

SAP Extended Warehouse Management (SAP EWM)

510

347

SAP Online Help

20.07.2007

Handling Differences When Picking for Warehouse Request


Purpose
When you confirm a warehouse task, differences between the product quantity requested and the product quantity available may result.

According to the warehouse task for a warehouse request, you are to pick 50 pieces of the product PROD-01 from the storage bin 02-03-44. However, you find only 45 pieces of the product in the storage bin. You confirm the warehouse task with a difference of 5 pieces.

Process
...

1. You want to remove a product from stock. 2. You pick a quantity smaller than the quantity specified on the corresponding warehouse task. 3. You record the quantity difference in the warehouse task by entering the quantity you have actually picked. 4. You confirm the warehouse task difference. 5. EWM updates the quantity to be picked in the warehouse request. 6. You decide how to proceed: You want to conduct another picking for the warehouse request. You create a further warehouse task for the warehouse request. After you have confirmed the further warehouse task for the warehouse request, the picking for the warehouse request is closed completely.

You do not want to conduct a further picking for the warehouse request. EWM uses Adjust Delivery Quantity to equate the delivery quantity with the picked quantity. Through this adjustment, the pick status changes from Partially Completed to Completed. You can post the delivery for goods issue.

Results
The warehouse request is completely picked. You can post the goods issue for the warehouse request.

SAP Extended Warehouse Management (SAP EWM)

510

348

SAP Online Help

20.07.2007

Kit to Order
Purpose
With this process, you can have the system automatically assemble kits to order if there is no kit [Extern] in stock. The following rules apply to kits: A kit is always delivered in full to a customer. The kit header and the kit components are always scheduled for the same date. All components of a kit must come from the same warehouse (this can be achieved by means of internal transfer between warehouses). Kit prices are always calculated at kit header level. The kit header and kit component have a quantity ratio defined by the kit structure to each other. This quantity ratio is recalculated as soon as there are changes at kit header level or at kit component level.

If the kit is in stock, the SPM goods issue process takes place. For more information about the SPM Goods Issue Process, see the SAP Library for SAP ECC under Logistics Logistics - General (LO) SAP Service Parts Management (LO-SPM) Goods Issue Process.

Prerequisites
You are using the following systems: SAP CRM 5.0 For more information, see the SAP Library for mySAP Customer Relationship Management under Components and Functions Availability Check Availability Check using SAP APO Additional ATP Functions in Service Parts Management Kits in the Sales Order. SAP ECC 6.0 For more information about the required Customizing settings, see the SAP Library for SAP ECC under Logistics Logistics - General (LO) SAP Service Parts Management (SPM) Goods Issue Process Kit to Order Customizing Settings. SAP SCM 5.0 Extended Warehouse Management (EWM): For more information about the required Customizing settings, see the Implementation Guide (IMG) for SCM under Extended Warehouse Management Goods Issue Process Make Settings for Kitting. Advanced Planning and Optimization (APO): For more information, see Availability Check for Kits [Extern].

SAP Extended Warehouse Management (SAP EWM)

510

349

SAP Online Help

20.07.2007

Process

...

1. You create a sales order (SAP CRM) a. The system triggers the rule-based ATP check in SAP SCM for a requirement from the sales order. The system determines one or more rules with substitutions. One of the substitutions is a kit. b. A requirement for a kit originates as an input product from the sales order. The system then triggers the ATP check in SAP SCM. c. The system initiates the credit check in SAP ECC. d. The system performs the price determination and checks for the sales order, as well as checks for foreign trade determination. e. The system transfers the data from the sales order to SAP ECC. For more information about editing sales orders, see the SAP Library for mySAP Customer Relationship Management under Components and Functions Process Sales Orders. 2. The system performs an ATP check and confirms quantities (SAP SCM-APO) The system checks whether the kit is in stock. If the kit is not in stock, the production that is activated in the validation rule creates a kit structure that contains the kit components that the system requires to assemble the kit. The system then performs the ATP check for the kit components and confirms the quantities for the sales order. 3. The system creates an unchecked delivery (SAP ECC-SPM) without creating an order. For more information, see the SAP Library for SAP ECC under Logistics Logistics General (LO) SAP Service Parts Management (SPM) Goods Issue Process Creation and Update of Unchecked Deliveries.

SAP Extended Warehouse Management (SAP EWM)

510

350

SAP Online Help 4. You convert the unchecked delivery to a checked delivery (SAP ECC-SPM).

20.07.2007

For more information, see the SAP Library for SAP ECC under Logistics Logistics General (LO) SAP Service Parts Management (SPM) Goods Issue Process Conversion of Unchecked to Checked Deliveries. 5. The system performs another ATP check for the various kit components and confirms the quantities from the checked delivery (SAP SCM-APO) For more information, see Availability Check for Kits [Extern]. 6. EWM creates a warehouse request for the outbound delivery (SAP SCM-EWM). When it receives notification from SAP ECC, EWM uses the checked delivery to automatically create an outbound delivery order, that is, a warehouse request for an outbound delivery. For more information, see Creation of a Warehouse Request for an Outbound Delivery Order [Seite 116]. 7. You pick the outbound delivery order (SAP SCM-EWM). For more information, see Creation of a Warehouse Request for an Outbound Delivery Order [Seite 116]. 8. The system changes/confirms the outbound delivery (SAP ECC-SPM) The system changes the delivery if quantity shortages are reported by EWM and then confirms the delivery. The system confirms the delivery if exact delivery fulfillment is reported by EWM.

For more information, see the SAP Library for SAP ECC under Logistics Logistics General (LO) SAP Service Parts Management (SPM) Goods Issue Process Processing of Checked Deliveries. 9. The system posts the goods issue for the kits (SAP ECC-SPM). For more information about posting goods issue, see the SAP Library for SAP ECC under Logistics Logistics - General (LO) SAP Service Parts Management (SPM) Goods Issue Process Transfer Posting for Kits. 10. The system clears ATP-confirmed quantities (SAP SCM-APO). 11. The system updates the stock (SAP SCM-APO). 12. The system updates the data in the sales order (SAP CRM). For more information about editing sales orders, see the SAP Library for mySAP Customer Relationship Management under Components and Functions Process Sales Orders. 13. The system executes billing (SAP CRM).

SAP Extended Warehouse Management (SAP EWM)

510

351

SAP Online Help

20.07.2007

Kit
Definition
Describes a piece list that you always deliver in a complete and assembled form.

Use
Extended Warehouse Management (EWM) does not save the kits as master data, instead it receives the information about the structure of a kit in the form of items of an outbound delivery from the ERP system (see also Kit in the Warehouse Request for the Outbound Delivery Order [Seite 234]). You can use the structure containing the kit in the outbound delivery in combination with a packaging specification as a basis for assembling or producing a kit in EWM.

Structure
A kit can consist of the following levels: Kit header

Kit component [Extern] Replaced kit component [Extern] (optional)

EWM does not support nested kits, that is, kits in kits.

Integration
EWM supports kits in the kit to order [Seite 349] process.

SAP Extended Warehouse Management (SAP EWM)

510

352

SAP Online Help

20.07.2007

Kitting at a Work Center with a VAS Order


Purpose
You can use this process to create a kit with a value-added service order [Seite 528] (VAS order). This provides you with the following VAS order options: Working with a special kitting work center Automatic determination of the kitting work center

Documentation about efforts and status tracking for kitting [Extern] Integrating VAS processing into the delivery

You can use an indicator for the item type of the kit header to make the system generate an item for the kit header in the pick-handling unit (pick-HU). You can print out this HU item in a HU list, display it in the packing transaction, and confirm it to the ERP system. In EWM, a kitting instruction can exist in one of the following forms: As free text from the SAP Customer Relationship Management sales order that forms the basis for the outbound delivery. As free text that you have created in the warehouse request in EWM.

You can display this text in the work center as additional information.

Prerequisites
You have made all the required settings for kitting in Customizing. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Issue Process Make Settings for Kitting. An outbound delivery with kit items exists in EWM. You have created a packaging specification for the product of the kit header item as master data, so that you can create a VAS order. This packaging specification must have a level of the level type Kitting. If you are using process-oriented storage control, you must assign the corresponding warehouse process step (such as KIT) of the warehouse process used to the kitting level (see also: Process-Oriented Storage Control [Seite 336]).

Note that a packaging specification (and therefore a VAS order) can only have one level of the type Kitting. You can assign a packaging material to the kitting level as a proposal for packing the kit. If the system is to automatically generate an HU item for the kit header in the pick-HU, set the Create Kit Item indicator in Customizing. For more information about the packing profile, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Issue Process Outbound Delivery Define EWM-Specific Settings for Item Types.

Process
...

1. EWM receives an outbound delivery with kit component items from the ERP system. 2. Depending on your Customizing settings, either you manually create a VAS order or you have the system create one automatically (see also: VAS Order for the Kit Header Item of the Warehouse Reqeust [Seite 356]). 3. You generate warehouse tasks for the kit component items in EWM. 4. You pick the kit component into a pick-HU and confirm the warehouse tasks. The kit components are then at the kitting work center.

SAP Extended Warehouse Management (SAP EWM)

510

353

SAP Online Help

20.07.2007

If you have set the Create Kit Item indicator in Customizing and are working with pick-HUs, the system generates the kit header item in the pick-HU. You can then use these items in the work center to repack the entire kit into another HU. If you have not set the Create Kit Item indicator in Customizing, you can generate the kit header item in the work center manually.

5. You assemble the kit in accordance with the kitting instructions where required. a. You can display the kitting instruction. b. You can report the work progress in the VAS order. 6. You pack the kit into an HU and generate the HU item for the kit header.

If the ERP system is dependent on an HU item for the confirmation, and you have not set the Create Kit Item indicator in Customizing, then you must generate the item manually after packing the kits in the work center at the latest. If a transfer posting of the stock from the kit components to the kit header takes place in the ERP system when processing the goods issue confirmation from EWM, the ERP system is dependent on this item (see also: Kit to Order [Seite 349]). 1. You generate an HU warehouse task to transport the HU to the goods issue zone. 2. You confirm the HU warehouse task. 3. You then post the goods issue for the warehouse request. If you have set the Create Kit Item indicator, the system uses this HU item in goods issue posting to check whether the packed kits are complete, meaning the system can therefore post these kits for goods issue.

The system only performs this check if the indicator is set in the item type of the kit header. This process allows you to use the following options: Process-oriented storage control Integrating the VAS order into storage control Creating VAS orders based on a packaging specification

This enables you to provide additional steps in the warehouse process, such as loading. You can also define your own warehouse process steps for packing kits into an HU, such as in the following instances: If you are not performing this step during kitting, but as an additional step at the same work center. If you are packing the kits into an HU at a different work center after kitting.

The decision as to whether you map additional steps as a step in the warehouse process only, or as a level of the packaging specification as well, depends on whether you want to document this step in the VAS order. The system only generates a VAS activity where you can report effort and consumption of the packaging material if you have mapped this step as a level of the packaging specification.

Result
You can ship the kit.

SAP Extended Warehouse Management (SAP EWM)

510

354

SAP Online Help

20.07.2007

SAP Extended Warehouse Management (SAP EWM)

510

355

SAP Online Help

20.07.2007

VAS Order for the Kit Header Item of the Warehouse Request
Purpose
You can generate value-added service orders [Seite 528] (VAS orders) automatically or manually in Extended Warehouse Management (EWM), to document and monitor these value-added services. VAS orders that are generated for a kit header item have a special structure.

Prerequisites
You have made the required settings in Customizing for generating VAS orders automatically or manually. If you want to create a VAS order for kit items in the delivery, make the settings for the item type of the kit header only. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings Value-Added Services Define Relevance for VAS Order. An outbound delivery with kit items exists in EWM. You have defined a packaging specification [Seite 494] with a level of type Kitting. Note that a packaging specification (and therefore a VAS order) can only have one level of the type Kitting.

Process
Automatic Generation
...

1. You receive an outbound delivery with kit items from the ERP system. 2. EWM checks whether it is to generate a VAS order for the kit header item automatically, and generates it where appropriate. 3. EWM saves the number of the VAS order as a document flow for all kit items of the warehouse request. 4. If you have activated the VAS Order status in the status profile of the item type for the warehouse request item, EWM sets the VAS Order status of the kit items to one of the following entries: Generated If you have defined in Customizing that EWM is to generate the VAS order automatically. Not Relevant If you have defined in Customizing that EWM is not to generate the VAS order automatically.

Manual Generation
...

1. You receive an outbound delivery with kit items from the ERP system. 2. You create a VAS order for the kit header item manually (see also: Create and Edit VAS Orders [Seite 536]). 3. EWM creates the VAS order. When you save the VAS order, EWM saves the number of the VAS order as a document flow for all kit items of the warehouse request. 4. If you have activated the VAS Order status in the status profile of the item type for the warehouse request item, EWM sets the VAS Order status of the kit items to Generated.

SAP Extended Warehouse Management (SAP EWM)

510

356

SAP Online Help

20.07.2007

Result
The system has created a VAS order for the kit header. You can use this VAS order for confirming services in the process Kitting at a Work Center with a VAS Order [Seite 353]. When you edit the VAS order, EWM changes the VAS Order status of the warehouse request item (see also: Updating the Warehouse Request Using the VAS Order [Seite 232]). The VAS order for the kit header has the following special features. For example, you have defined a packaging specification with the levels Oiling, Kitting, and Packing. The VAS order for the kit header has the following special features: All activities prior to the kitting activity (such as oiling) and the kitting activity itself have kit component items of the delivery as their items. This is based on the assumption that you perform all activities prior to assembling the kits and the kitting activity itself in the kit components. All activities after the kitting activity (such as packing) have the kit header item as their item. This is based on the assumption that you perform all activities after assembling the kits in the kit itself.

SAP Extended Warehouse Management (SAP EWM)

510

357

SAP Online Help

20.07.2007

Kitting at a Work Center Without a VAS Order


Purpose
You can use this process in Extended Warehouse Management (EWM) to create a kit without a value-added service order [Seite 528] (VAS order). Here you can configure a work center where you also pack in such a way that you can confirm generated kits there. This process is suitable for the following cases: You do not require detailed documentation of the kitting procedure in EWM. You are not performing kitting in one special kitting work center, but at a work center where you are also packing.

You can only find information about kitting in the information for the kit in the outbound delivery and in the kitting instruction that may exist in the form of free text for the warehouse request item of the kit. You can use an indicator for the item type of the kit header to make the system generate an item for the kit header in the pick-handling unit (pick-HU). You can print out this HU item in an HU list, display it in the packing transaction, and confirm it to the ERP system. In EWM, a kitting instruction can exist in one of the following forms: As free text from the SAP Customer Relationship Management sales order that forms the basis for the outbound delivery. As free text that you have created in the warehouse request in EWM.

You can display this text in the work center as additional information.

Prerequisites
You have made all the required settings for kitting in Customizing. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Issue Process Make Settings for Kitting. An outbound delivery with kit items exists in EWM. If the system is to automatically generate an HU item for the kit header in the pick-HU, set the Create Kit Item indicator in Customizing. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Issue Process Outbound Delivery Define EWM-Specific Settings for Item Types.

Process
1. EWM receives an outbound delivery with kit component items from the ERP system. 2. You generate warehouse tasks for the kit component items. 3. You pick the kit components into a pick-HU and confirm the warehouse tasks. The kit component items are then in the packing work center. If you have set the Create Kit Item indicator in Customizing and are working with pick-HUs, the system generates the kit header item in the pick-HU. You can then repack these items into other HUs in the work center. If you have not set the Create Kit Item indicator in Customizing, you can generate the kit header item in the work center manually.

4. You assemble the kit in the packing work center. 5. You pack the kit into an HU and generate the HU item for the kit header. 6. You generate an HU warehouse task to transport the HU to the goods issue zone.

SAP Extended Warehouse Management (SAP EWM)

510

358

SAP Online Help 7. You confirm the HU warehouse task. 8. You then post the goods issue for the warehouse request.

20.07.2007

If you have set the Create Kit Item indicator, the system uses this HU item in goods issue posting to check whether the packed kits are complete, and therefore whether the system can post goods issue for these kits.

The system only performs this check if the indicator is set in the item type of the kit header. If the ERP system is dependent on an HU item for the confirmation, and you have not set the Create Kit Item indicator in Customizing, you must generate the item manually after packing the kits in the work center at the latest. If a transfer posting of the stock from the kit components to the kit header takes place in the ERP system when processing the goods issue confirmation from EWM, the ERP system is dependent on this item (see also: Kit to Order [Seite 349]).
...

Result
You can ship the kit.

SAP Extended Warehouse Management (SAP EWM)

510

359

SAP Online Help

20.07.2007

Kitting During Picking Without a VAS Order


Purpose
You can use this process in Extended Warehouse Management (EWM) to create a kit during picking. This process is suitable for the following cases: You do not require detailed documentation of the kitting procedure in EWM. You assemble the kits during picking, that is, you do not perform kitting at special work centers.

You can only find information about kitting in the information for the kit in the outbound delivery and in the kitting instruction that may exist in the form of free text for the warehouse request item of the kit header. You can use an indicator for the item type of the kit header to make the system generate an item for the kit header in the pick-handling unit (pick-HU). You can print out this HU item in an HU list, display it in the packing transaction, and confirm it to the ERP system. In EWM, a kitting instruction can exist in one of the following forms: As free text from the SAP Customer Relationship Management sales order that forms the basis for the outbound delivery. As free text that you have created in the warehouse request in EWM.

You can display this text in the work center as additional information.

Prerequisites
You have made all the required settings for kitting in Customizing. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management under Goods Issue Process Make Settings for Kitting. An outbound delivery with kit items exists in EWM. If the system is to automatically generate an HU item for the kit header in the pick-HU, set the Create Kit Item indicator in Customizing. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Issue Process Outbound Delivery Define EWM-Specific Settings for Item Types.

If the ERP system is dependent on an HU item for the kit header in the confirmation of goods issue, you must make this setting. If a transfer posting of the stock from the kit components to the kit header takes place in the ERP system when processing the goods issue confirmation from EWM, the ERP system is dependent on this item (see also: Kit to Order [Seite 349]).
...

Process
...

1. EWM receives an outbound delivery with kit component items from the ERP system. 2. You generate warehouse tasks for the kit component items. 3. You pick the kit components and assemble the kit, where required in accordance with the kitting instruction. 4. You confirm the warehouse tasks.

SAP Extended Warehouse Management (SAP EWM)

510

360

SAP Online Help

20.07.2007

If you have set the Create Kit Item indicator in Customizing and are working with pickHUs, the system generates the kit header item in the pick-HU. You can then repack these items into other HUs in the work center. 5. You then post the goods issue for the warehouse request. If you have set the Create Kit Item indicator, the system uses this HU item in goods issue posting to check whether the packed kits are complete, and therefore whether the system can post goods issue for these kits.

The system only performs this check if the indicator is set in the item type of the kit header.

Results
You can ship the kit.

SAP Extended Warehouse Management (SAP EWM)

510

361

SAP Online Help

20.07.2007

Packing at the Work Center


Use
Using packing in the work center, you can pack products into handling units (HU), and handling units into other handling units. For packing, there are various restriction options (filters) available for selection on the initial screen, for example, storage bin, handling unit, or delivery, which enable each user to optimize their worklist. On the left side of the work center screen, for example, you can use simple Drag&Drop to repack entire handling units, or to pack products into other handling units. The upper right screen area consists of tab pages that you can mainly use without a mouse. This transaction is particularly aimed at those users who physically pack products at work centers in the warehouse. The system supports entries using the keyboard or a scanner (where the necessary information is available as a bar code). You can also transmit the exact weight to the SAP system, using scales connected to the system, or you can print handling unit documents.

Prerequisites
Ensure that you have made the required settings for packing in the work center, in Customizing and the SAP menu. For example, in the SAP menu you need to specify which storage bin is assigned to a work center. In Customizing, you specify which functions are executed at the relevant work center. The display for the different work centers is configurable. For example, in Customizing you can decide which of the available tab pages should be displayed for the user in the relevant work center. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management Master Data Work Center Define Work Center Layout and Define Work Center.

Features
Packing in the work center offers you the following range of functions: Scanning of HU Identification Product Warehouse Task Storage Section

Creation of handling units Repacking of handling units Repacking of products Post Differences Changing handling units Deconsolidation of handling units

You can configure packing in the work center in such a way that the system copies over frequently required data as default values for packing. In the Control area, you can make the following settings: Standard storage bin

SAP Extended Warehouse Management (SAP EWM)

510

362

SAP Online Help

20.07.2007

Standard exception code Propose Destination HU indicator Propose Packaging Material indicator External number assignment on/off

The display is divided into the left and right screen areas. You use the left screen area mainly for navigation, and for quick repacking of handling units and products (only using the mouse). In the right screen area, you can request various detailed information about the individual entries. The left screen area groups the display according to the following objects: Storage section (displayed as Storage bin (displayed as symbol) symbol) or , with or without system lock)

Handling units (displayed as symbol Storage section (displayed as

symbol) symbol)

Open warehouse task (displayed as

Detailed Information
In the right screen area, you can edit or request the following detailed information for the individual objects. Storage Bin Storage bin product (if unpacked products are present in the storage bin) Storage bin information (warehouse number, section, storage type)

Handling unit Capacity (weight, volume, and dimensions) Detail data 1 (internal warehouse data, such as warehouse process and process step, deconsolidation group, and so on) Detail data 2 (status, assignment to deliveries, alternative HU identification) Contents (list of the packed products and additional packaging materials contained in the HU) Possible destination HUs (for example, for open warehouse tasks) Open warehouse tasks (lists all warehouse tasks that exist for a HU) Confirmed warehouse tasks

Product Product data Possible destination HUs Open warehouse tasks Confirmed warehouse tasks Texts 510 363

SAP Extended Warehouse Management (SAP EWM)

SAP Online Help o Quality inspections

20.07.2007

Warehouse Task Possible destination HUs

Note that you edit and/or assign additional packaging materials in the Product area.

Functions for Objects


In addition, you can execute the following functions from the right screen area: Handling Units Weigh Close Putback Print Delete Empty Aggregate

Product Repack Post Differences

Warehouse Task Repack Post Differences

Activities
Since you can assign various work center categories to the work centers in Customizing, you also have the option of calling up the various work centers separately in the menu. The corresponding input help is then restricted, depending on the work center, to the data you have configured in Customizing. For more information, see the IMG under Define Work Center.
...

1. To access the various types of work center, choose one of the following menu paths:
...

a. From the SAP menu, choose Extended Warehouse Management Execution Packing - General b. From the SAP menu, choose Extended Warehouse Management Execution Quality Inspection and Count c. From the SAP menu, choose Extended Warehouse Management Execution Deconsolidation in Goods Receipt 2. Enter the relevant warehouse number, and use the input help to select the work center you require, if you have not assigned a work center to your terminal.

SAP Extended Warehouse Management (SAP EWM)

510

364

SAP Online Help

20.07.2007

You can assign a work center to your terminal in the system, so that during packing, the system automatically fills in the correct warehouse number and your work center. To do this, from the SAP menu choose Extended Warehouse Management Master Data Work Center Define Master Data Attributes, and assign your terminal to the work center. You can also assign any scales that are connected to your work center.

Packing Using Drag and Drop


In the area on the left, you can pack or unpack products in HUs, or pack HUs in other HUs as follows: If you want to repack products in other HUs, select the product and drag it into another HU. If you want to unpack products from other HUs, select the product and drag it to the storage bin. If you want to pack an HU in another HU, select an HU and drag it into another HU.

Packing Partial Quantities Using Drag and Drop


...

1. If you want to repack just one partial quantity of a product, double click a higher-level node (HU or storage bin) in the area on the left. 2. Choose the tab page Contents in the area on the lower right. All the product items of the HU or storage bin are now visible. 3. Enter the quantity that you want to repack in the Partial Quantity field and choose Enter. 4. Drag the item from the area on the right into the target HU or target storage bin in which you want to repack these partial quantities. a. To do this, click any cell in this row that is not ready for input. b. Then use drag and drop to drag this cell to the target area (destination HU or destination storage bin).

SAP Extended Warehouse Management (SAP EWM)

510

365

SAP Online Help

20.07.2007

Scrapping
Purpose
In your warehouse you sometimes find products that are damaged, or that are unusable for some other reason. You often notice this, for example, during picking or physical inventory. Since you cannot normally sell these products on, you have to scrap them. You can use this process to create posting change notices for scrapping, and can remove these products from stock and post goods issue as usual.

Prerequisites
...

You have defined the following different document types for the posting change process, so that you can begin the scrapping process: Document type for scrapping the entire quantity of a product Document type for scrapping the entire quantity of a product except for a fixed remaining quantity Document type for scrapping a partial quantity of a product

For more information, see the Implementation Guide (IMG) for Extended Warehouse Management under Internal Warehouse Processes Delivery Processing Posting Changes Manual Settings Define Document Types for Posting Change Process. You have defined the warehouse process types for scrapping, in which you enter the work center for scrapping as the destination storage bin. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings Warehouse Task Define Warehouse Process Type. You have defined the stock removal strategies for determining the stock to be scrapped. For more information, see the Implementation Guide (IMG) for Extended Warehouse Managements under Goods Receipt Process Strategies. You have defined the work center for scrapping, where you can pack the products to be scrapped together into a collection container. For more information, see the Implementation Guide (IMG) for Extended Warehouse Managements under Master Data Work Center. You have defined a non-picking-relevant document type and item type for the outbound delivery of the scrapping container. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management under Goods Issue Process Outbound Delivery Manual Settings Define Document Types for the Outbound Delivery Process and Define Item Types for the Outbound Delivery Process.

Process
...

1. Create the posting change notice for scrapping.


...

a. For the entire quantity of a product b. For the entire quantity of a product except for a fixed remaining quantity

SAP Extended Warehouse Management (SAP EWM)

510

366

SAP Online Help

20.07.2007

c. For a partial quantity of a product (unsaleable or damaged products in the warehouse) 2. Create a warehouse task for scrapping with reference to the posting change notice 3. You can use a stock removal strategy to determine the stock to be scrapped. You can use different stock removal strategies for the entire quantity of a product and for the entire quantity of a product except for a fixed remaining quantity. 4. Remove the products to scrap from stock. You pick these products and confirm the warehouse tasks to the work center for scrapping. 5. You use the packing transaction to pack the products to scrap, and to construct handling units. 6. Use the handling units to create a non-picking-relevant outbound delivery. 7. Post the goods issue for the outbound delivery.

SAP Extended Warehouse Management (SAP EWM)

510

367

SAP Online Help

20.07.2007

Invoice Creation Before Goods Issue


Use
You can define when billing for SAP Customer Relationship Management (CRM billing) or billing for ERP (ERP billing) is to create an invoice for one single delivery or multiple deliveries. In the standard system, CRM billing or ERP billing creates the invoice after goods issue. However, if you require the invoice printout before the end of the loading and transportation process, such as for international transportation, you can create the current invoice before goods issue posting. You do this by sending an invoice request from Extended Warehouse Management (EWM) to CRM billing or ERP billing. You can request an invoice for each delivery or one or more invoices for the contents of a vehicle or transportation unit. If you want to print invoices for the contents of a vehicle or transportation unit, EWM triggers the invoice printout in CRM billing or ERP billing by sending the message Print Billing Document. If you want to create one invoice for each delivery, EWM triggers the creation and invoice printing automatically when it generates an outbound delivery.

Integration
To be able to create and print invoices, you have performed the following: If you are using CRM billing, you have connected an ERP and an SAP CRM system. If you are using ERP billing, you have connected an ERP system.

EWM sends the invoice-relevant data to ERP. ERP copies the data to CRM billing or ERP billing. The following applies for invoice creation: In the case of direct outbound delivery orders, the invoice is always created through ERP billing. In the case of CRM orders, the invoice is always created through CRM billing. In the case of ERP orders, the invoice is always created through ERP billing.

Prerequisites
If you are using CRM billing, you have set the IBGI (Invoicing Before Goods Issue) indicator in the data relevant to the business partner. You can override this indicator in the sales order. For more information, see the SAP Library under SAP CRM Components and Functions Sales Sales Transaction Sales Orders Additional Functions for Service Parts Management. If you are using ERP billing, you have set the IBGI (Invoicing Before Goods Issue) indicator in Customizing for ERP under Logistics Execution Extended Warehouse Management Integration Settings for Billing Determine Invoicing Before Goods Issue. You have defined specific characteristics in the route, such as the GTS geography group at header level, to determine whether a delivery must be checked by the customs authority. On the SAP Easy Access screen, choose Extended Warehouse

SAP Extended Warehouse Management (SAP EWM)

510

368

SAP Online Help

20.07.2007

Management Master Data Shipping and Receiving Transportation Route Determination Maintain Route. You have determined that EWM requests CRM billing or ERP billing for single deliveries and also for groups of deliveries in accordance with the contents of a vehicle or a transportation unit. If, for example, a vehicle is carrying a delivery of 50 different regulators, EWM requests at least 50 invoices from CRM billing. In the SAP Easy Access screen, choose Extended Warehouse Management Interfaces Invoice Before Goods Issue. In Customizing for EWM, you have defined the following for the document type and item type of the outbound delivery: You have defined a process profile for the document type of the outbound delivery that allows invoicing before goods issue. For example, you are using document type OUTB Outbound Delivery Order with process profile /SCWM/OUT_PRD Outbound Delivery Order Standard for the delivery header, and process profile /SCWM/OUT_PRD_DLV Outbound Delivery Order Standard Item EWM for the delivery item. For more information, see IMG for EWM under Goods Issue Process Outbound Delivery Manual Settings Define Document Types for Outbound Delivery Process. For more information about the individual process indicators, see the IMG for EWM under Cross-Process Settings Delivery Processing Process Profile for Delivery Document Header in the field help for the individual process indicator. You have defined a process profile for the item types of the outbound delivery that allows invoicing before goods issue. For example, you use item type ODLV Standard Item Outbound Delivery with process profile /SCWM/OUT_PRD_DLV Outbound Delivery Order Standard Item. For more information, see the IMG for EWM under Cross-Process Settings Delivery Processing Process Control Define Process Profile for Delivery Document Header or Define Process Profile for Delivery Document Item. If you do not use routes in the outbound delivery, you can define the following in Customizing for EWM for the document type of the outbound delivery: EWM triggers invoice creation and invoice printing automatically when it generates an outbound delivery You trigger invoice creation and invoice printing manually on the user interface of the outbound delivery later

For the routes that you want to use in the invoice before goods issue process, you have defined one of the following options: The invoice for the outbound deliveries is to be created individually The invoice for the outbound deliveries is to be created as a group per transportation unit or per vehicle, or manually on the user interface for the outbound delivery.

In the SAP Easy Access screen, choose Extended Warehouse Management Interfaces Invoice Before Goods Issue.

Features
For single requests from EWM, CRM billing or ERP billing directly creates single invoices that you cannot change. For changes, you have to delete the outbound delivery. This automatically cancels the invoice. If you then generate a new outbound delivery, the invoice is automatically created and printed again.

SAP Extended Warehouse Management (SAP EWM)

510

369

SAP Online Help

20.07.2007

For group requests from EWM, CRM billing or ERP billing creates one or more invoices for each vehicle or transportation unit. CRM billing creates corresponding billing due list items. ERP billing does not create any billing due list items. You can make changes to these deliveries in EWM. If these occur before invoice creation, ERP or SAP CRM updates its deliveries or the invoice-relevant data in accordance with the input from EWM. After you have posted the goods issue, you can only trigger the invoice printout from CRM billing or ERP billing. If more than one vehicle forwards the material for a sales order, you can create related outbound deliveries for each vehicle and request invoices for them.

Invoice Relevance
With your settings at sales order level or delivery level, you can control the global relevance for invoice creation before goods issue at delivery item level. You can determine a print profile after CRM billing or ERP billing has selected the printer [Seite 372]. EWM finds the print profile and informs CRM billing or ERP billing accordingly. For printing single requests, the billing system uses the print profile found. For the printing of group requests, the billing system uses the profile of the first delivery that was found.

You must determine the same print profile in CRM billing or ERP billing and EWM, so that CRM billing or ERP billing can print invoices.

Invoice Cancellation
You cannot change an invoice once it has been created. If, for example, you have loaded a handling unit on to a different transportation unit and want to change the invoice that has already been created, you have to perform an invoice cancellation. EWM sends the cancellation for the invoice that was created to CRM billing or ERP billing. You can then request invoice creation and invoice printing again for the changed shipment document or delivery.

Activities
Among other things, SAP CRM determines whether EWM sends an invoice request for a delivery before the goods issue posting to CRM billing via ERP, due to the business partner status Invoice Creation Before Goods Issue Posting Allowed. You can override this setting in the sales order of SAP CRM. ERP uses the Customizing entries to determine whether the outbound delivery is relevant for the Invoice Before Goods Issue process. In ERP, you can configure for the sales document type and sales organization the indicator with which the document items are sent to EWM. If the IBGI indicator on the delivery item allows invoice before goods issue depending on the route, EWM decides which type of request it sends to CRM billing or ERP billing for invoice creation and invoice printing: Single request for an immediate invoice creation and invoice printing Group request for an invoice creation and invoice printing

If you want to request, print or cancel an invoice for a group request, on the SAP Easy Access screen, choose Extended Warehouse Management Shipping and Receiving Process Vehicle or Process Transportation Unit. If you are not using a vehicle or transportation unit in the outbound delivery, on the SAP Easy Access screen choose Extended Warehouse Management Delivery Processing Outbound Delivery Maintain Outbound Delivery or Pickup and then choose one of the following options: Request Invoice EWM sends the message Create Invoice to SAP CRM or ERP.

SAP Extended Warehouse Management (SAP EWM)

510

370

SAP Online Help

20.07.2007

Cancel Invoice EWM sends the message Cancel Invoice to SAP CRM or ERP. Print Invoice EWM sends the message Print Invoice to SAP CRM or ERP. Get Status The system requests and displays the status of the invoice creation for the ERP delivery.

SAP Extended Warehouse Management (SAP EWM)

510

371

SAP Online Help

20.07.2007

Print Profile Determination for Invoice Printout


Purpose
You can use this process to define print profile determination for invoice creation before goods issue [Seite 368] in Extended Warehouse Management (EWM). Here, every goods issue area can have multiple printers for various document types, for example, for freight lists, bills of lading, or invoices. EWM always sends the print profile names for invoice printouts to ERP, irrespective of whether you print from ERP or from SAP Customer Relationship Management (SAP CRM).

Prerequisites
If appropriate, you have defined a print profile in the default values. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Delivery Processing Outbound Delivery Pickup. Choose Default Values and enter a print profile. If appropriate, you have implemented your own print profile determination in Business Add-In (BAdI) /SCWM/EX_DLV_PRINT_PROFILE. For more information, see the BAdI documentation. If appropriate, you have defined one or more print profiles in Customizing for EWM. For more information, see the Implementation Guide (IMG) for EWM under Extended Warehouse Management Goods Receipt Process Inbound Delivery Print Define Print Profiles for Delivery Processing and Goods Issue Process Outbound Delivery Print Define Print Profiles for Delivery Processing. You have defined print profile determination for the goods receipt process or goods issue process in Customizing for EWM. For more information, see the IMG for EWM under Extended Warehouse Management Goods Receipt Process Inbound Delivery Print Define Print Profile Determination for Goods Receipt Process or Goods Issue Process Outbound Delivery Print Define Print Profile Determination for Goods Issue Process.

Process
EWM attempts to determine the print profile in the following sequence:
...

1. EWM checks whether you have specified a print profile in the default values on the user interface for pickup. If so, it uses the name of this print profile. 2. If EWM cannot find a print profile in step 1, it checks whether you have implemented your own print profile determination in BAdI /SCWM/EX_DLV_PRINT_PROFILE. EWM uses the name of this print profile. 3. If EWM cannot find a print profile in step 2, it checks whether you have defined a print profile determination for the goods receipt process or the goods issue process in Customizing for EWM. EWM uses the name of this print profile. You can define an access sequence for print profile determination. As a result, EWM considers one or more combinations of different parameters for the print profile, for example, goods receipt office, ship-to location, and warehouse number. If EWM cannot determine a print profile, it does not send a print profile name to ERP. If EWM requests a single print from CRM billing, CRM billing uses the print profile that EWM sends. EWM determines this print profile in the sequence described above.

SAP Extended Warehouse Management (SAP EWM)

510

372

SAP Online Help

20.07.2007

If EWM requests a grouped print for multiple deliveries from CRM billing, EWM always sends the first print profile that is found by delivery processing. For information about invoice relevance, the invoice printout, and invoice cancellation, see Invoice Creation Before Goods Issue [Seite 368].

If you want to synchronize invoice printing with delivery note printing, you must ensure that EWM determines the printer for delivery note printing using a print profile (see Printer Determination in Delivery Processing [Seite 141]). This is because EWM only sends the print profile name to ERP and not the printer name. See also: Printing Delivery Notes [Seite 143]

SAP Extended Warehouse Management (SAP EWM)

510

373

SAP Online Help

20.07.2007

Putaway and Stock Removal Strategies


Use
In Extended Warehouse Management (EWM), the system uses putaway strategies [Seite 375] and stock removal strategies [Seite 396] to determine storage bins and stock. Each time that a warehouse task (WT) is created, the system reverts to putaway and stock removal strategies. Goods receipts The system uses putaway strategies and parameters defined in the product master to utilize the available warehouse capacity by automatically determining suitable storage bins for the new products. Goods Issues The system uses stock removal strategies to determine the optimal picking bin. If you decide to manually process certain goods movements, you can change source and destination storage bins that are automatically proposed by the system. Internal stock transfers The system uses putaway and stock removal strategies, for example, for rearrangement [Seite 287], posting changes, and replenishment control [Seite 346].

Prerequisites
You make the settings for putaway and stock removal strategies in Customizing for EWM under Goods Receipt Process Strategies or Goods Issue Process Strategies. For more information, see the Implementation Guide (IMG) and the documentation for the individual strategies. See also: Storage Bin Determination for Putaway [Seite 291] Storage Bin Determination for Stock Removal [Seite 343]

SAP Extended Warehouse Management (SAP EWM)

510

374

SAP Online Help

20.07.2007

Putaway Strategies
Use
In Extended Warehouse Management (EWM), you use putaway strategies [Extern] to optimize the storage of products.

Prerequisites
You make the settings for the putaway strategies in Customizing for Extended Warehouse Management (EWM) under Goods Receipt Process Strategies. For more information, see the Implementation Guide (IMG) and the documentation for the individual strategies.

Features
The following table shows possible putaway strategies: Strategy Manual Entry [Seite 376] Fixed Storage Bin [Seite 377] General Storage [Seite 379] Addition to Existing Stock [Seite 380] Empty Storage Bin [Seite 381] Near Fixed Picking Bin [Seite 382] Comment The system uses the storage bin that you have entered. The system searches for a fixed storage bin. The system searches in the general storage area. The system searches for a storage bin that already contains stock. The system searches for an empty storage bin. The system searches for a storage bin in the reserve storage type near to the fixed picking bin of the picking storage type. The system determines the storage bin on the basis of the handling unit type. The system searches for a storage bin in the bulk storage area.

Pallet Storage (by HU Type) [Seite 383] Bulk Storage [Seite 387]

You can use the BAdIs in the /SCWM/ES_CORE_PTS enhancement spot to make changes to these putaway strategies. See Also: Storage Bin Determination for Putaway [Seite 291]

SAP Extended Warehouse Management (SAP EWM)

510

375

SAP Online Help

20.07.2007

Manual Entry
Use
The system does not determine a storage section or a storage bin. You enter the destination storage bin manually when the warehouse task is created. You use this procedure if the search for a suitable storage bin is performed on-site by the warehouse worker. First the warehouse worker searches for the suitable storage bin. Then the system automatically determines the data using the storage bin (for example, the storage type) in the warehouse task.

We recommend that you manually enter the storage bin in the case of mixed storage and storage types with the role Staging Area Group. You can use manual entry in the following transactions: Putaway for inbound delivery (/SCWM/TODLV_I) Stock removal for outbound delivery order (/SCWM/TODLV_O) Stock transfer for internal stock transfer (/SCWM/TODLV_M) Stock transfer for posting change (/SCWM/TODLV_T) Move handling unit (/SCWM/ADHU) Move product (/SCWM/ADPROD)

Prerequisites
You have made the following settings for the storage type in Customizing for Extended Warehouse Management (EWM) under Master Data Define Storage Type: You have chosen the Standard Warehouse value in the Storage Behavior field. You have chosen the Empty Bin or Addition to Existing Stock/Empty Bin value in the Putaway Rules field. You have chosen the Only Storage Type value in the WT Generic field.

SAP Extended Warehouse Management (SAP EWM)

510

376

SAP Online Help

20.07.2007

Strategy: Fixed Storage Bin


Use
You apply this strategy if you want to put away a product in fixed storage bins in a storage type. You use this strategy primarily in storage types from which picking is done manually. You assign fixed storage bins manually. If you want to put away a product without fixed bin assignment in a storage type for which you have defined the strategy Fixed Storage Bin, the system determines a suitable storage bin and assigns it to the product as a fixed storage bin. The following figure is an example of a fixed bin assignment. In this example, warehouse 0001 has several fixed storage bins: FIX-AA, FIX-BB, and FIX-DD. Multiple fixed storage bins can be available for a product, for example, FIX-1-BB and FIX-2-BB for product BB.

AA

B-B

FIX-AA

FIX-1-BB

FIX-2-BB

FIX-1-DD

FIX-2-DD

Warehouse No. 0001 Party Ent. to Disp. BP0001 Product AA Fixed Bin: Fix-AA

Prerequisites
You have defined fixed storage bins in the master data for Extended Warehouse Management (EWM) under Storage Bin Maintain Fixed Storage Bin. You have made the following settings for the storage type in Customizing for EWM under Master Data Define Storage Type: You have chosen the Standard Warehouse value in the Storage Behavior field. You have chosen the Addition to Existing Stock/Empty Bin value in the Putaway Rules field. You have set the Fixed Bins Allowed indicator. You have defined a maximum number of fixed storage bins in the Max. Fixed Bins field (you can also make this setting in the product master). You have chosen the Addition to existing stock permitted value in the Addn.Stock Forbidden field.

SAP Extended Warehouse Management (SAP EWM)

510

377

SAP Online Help

20.07.2007

You have chosen a method in the Capacity Check field to activate the capacity check.

SAP Extended Warehouse Management (SAP EWM)

510

378

SAP Online Help

20.07.2007

Strategy: General Storage


Use
The system uses this strategy to find a storage bin in a general storage area. General storage is a type of warehouse organization in which you define a single storage bin per storage section. The quants in the storage bin can also be in the form of mixed storage. For each storage type, you can define one or more general storage areas. The following figure illustrates general storage. Two general storage areas (bin XXX and bin YYY) are available with mixed storage in storage type 0005. This means that you can put away product F in bin XXX even though product X has already been put away there.
Storage Type 0005 Y Product X Bin XXX Bin YYY B

Product F

Prerequisites
You have made the following settings in Customizing for Extended Warehouse Management (EWM) under Master Data Define Storage Type: You have chosen the Standard Warehouse value in the Storage Behavior field. You have chosen the General Storage Area value in the Putaway Rules field. You have chosen the Mixed Storage Without Limitations value in the Mixed Storage field.

SAP Extended Warehouse Management (SAP EWM)

510

379

SAP Online Help

20.07.2007

Strategy: Addition to Existing Stock


Use
With this strategy, the system prefers to put away stock in storage bins that already contain stock of the relevant product. A prerequisite for addition to existing stock is that sufficient free capacity still exists in the relevant storage bin. If the system cannot find a storage bin with the same product or if the storage bin does not have sufficient free capacity to store additional quants, the system searches for the next empty storage bin. This strategy violates the FIFO principle. For this reason, you should only use this strategy in situations where you have insufficient space. The following figure shows an example of addition to existing stock. You want to put away product AA. Since AA is already occupying a storage bin and free capacity is still available, you can add the product to the existing stock.

BB

AA

AA

Prerequisites
You have made the following settings for the storage type in Customizing for EWM under Master Data Define Storage Type: You have chosen the Standard Warehouse value in the Storage Behavior field. You have chosen the Addition to Existing Stock/Empty Bin value in the Putaway Rules field. You have specified in the Addn.Stock Forbidden field whether or not you want to allow additions to existing stock. If you want to allow additions to existing stock, choose (Addition to existing stock permitted) or M (Addition to existing stock via addtn ID in product master). If you choose M, you must choose the required value for the Addit.to Exist.Stock indicator in the product master. You have chosen a method in the Capacity Check field to activate the capacity check. You have chosen the value 3 in the Mixed Storage field (one HU allowed per bin, in other words, mixed storage is not permitted).

SAP Extended Warehouse Management (SAP EWM)

510

380

SAP Online Help

20.07.2007

Strategy: Empty Storage Bin


Use
With this strategy, the system proposes an empty storage bin. You can use this strategy to support warehouses that are organized randomly, where products are stored in individual storage sections. This strategy is especially suited for high rack storage and shelf storage.

Prerequisites
You have made the following settings for the storage type in Customizing for Extended Warehouse Management (EWM) under Master Data Define Storage Type: You have chosen the Standard Warehouse value in the Storage Behavior field. You have chosen the Empty Bin value in the Putaway Rules field. Optionally, you can change the sort sequence of the storage bins that has an effect on the determination of the empty storage bin under SrchRule EmptyBin.

SAP Extended Warehouse Management (SAP EWM)

510

381

SAP Online Help

20.07.2007

Strategy: Near Fixed Picking Bin


Use
You use this strategy when you put away products in a reserve storage area. This strategy is intended for situations where reserve storage bins of a reserve storage type are located directly above the fixed storage bins in a picking storage type (nearby reserve). You can configure whether the system checks if a fixed storage bin is available. You can set up your system in such a way that it first searches for a fixed storage bin in a picking storage type. If it does not find an empty bin, it then uses the "Near Fixed Picking Bin strategy to search for a bin in a reserve storage type that is as close as possible to the fixed storage bin of the product. The system first tries to find a reserve storage bin in the stack where the fixed storage bin is located. Here the system starts on the lowest level and works its way up. If it does not find an empty bin, it searches to the right of the fixed storage bin and then to the left in the same aisle, before searching in the adjoining aisles. Here it always searches from the bottom upwards. If multiple fixed storage bins are available for the product in the picking storage type, the system takes the first fixed storage bin that it finds as the starting point.

Prerequisites
You have made the following settings for the storage type in Customizing for Extended Warehouse Management (EWM) under Master Data Define Storage Type: You have chosen the Standard Warehouse value in the Storage Behavior field. You have chosen the Empty Bin value in the Putaway Rules field. You have chosen the Near to Fixed Bin value in the SrchRule EmptyBin field. You have given the storage bins in the picking storage type and the reserve storage type the same names.

SAP Extended Warehouse Management (SAP EWM)

510

382

SAP Online Help

20.07.2007

Strategy: Pallet Storage (by HU Type)


Use
Using this putaway strategy, the system processes different HU types (for example, pallets) and allocates them to a suitable storage bin section. One storage bin is often divided into several smaller sections. You can only put away the same HU types in a storage bin.

Explanation of the Strategy


High rack storage is frequently designed so that a storage bin can accommodate several different HU types. The following figure shows the Pallet Storage by HU Type strategy. For example, a storage bin can accommodate multiple pallets depending on the size of the pallet, such as three europallets (80 x 120) or two industrial pallets (100 x 120). A storage bin may be able to accommodate a single oversized pallet or several very narrow pallets.
1 Bin Type PA Europallet 02-10-01 2 3
HU Type P2

A Bin Type PA Industrial Pallet

B
HU Type P1

02-09-01 1 Bin Type PA 02-08-01 Industrial Pallet 2 3

With this strategy, you define the maximum number of quants for each combination of storage bin type and HU type. The first time that the system puts away products in this storage bin, it determines the storage bin sectioning that it assigns to the storage bin. The system also determines which and how many HUs it can put away in the storage bins.

Prerequisites
You have made the following settings for the storage type in Customizing for EWM under Master Data Define Storage Type: You have chosen the Pallet Storage value in the Storage Behavior field. You have chosen the Empty Bin value in the Putaway Rules field. You have activated the HU type check. You have chosen the Mixed Storage Without Limitations value in the Mixed Storage field.

SAP Extended Warehouse Management (SAP EWM)

510

383

SAP Online Help

20.07.2007

Definition of Storage Bin Sections


The following table shows the number of storage bin sections that you can define for a storage bin. This means that you use this number to control the number of HUs that can occupy a storage bin.

Define Storage Bin Sections


WNr Type SecKey No. Bin Functional 1 Secs Location Category 0007 A 0007 B 2 3 BT01 BT01 A 1 2 3 4 5 6 .... (Bin Secs)

0001 0001

B 2 3

Section Key
The storage bin sectioning determines which HU types and how many handling units (HUs) of each type you can put into a storage bin. The storage bin sectioning is determined dynamically on the basis of the first HU that you put away. The system deletes the storage bin sectioning as soon as you have removed the last HU from the storage bin.

Nomenclature of Storage Bin Sections


To name each individual section of a storage bin, you enter either a one-digit or a two-digit suffix (for example, A1, BB, 12) in one of the columns numbered from 1 to 99 under the heading Sections. The system displays the total number of storage bin sections that you have defined in the Number of Sections field. The system attaches this suffix to the name of the storage bin and separates it with a slash (/). Note that the name of the storage bin sections is 2-3 digits longer than that of the main storage bins. Therefore, the length of the name of the main storage bin must be 2-3 digits shorter than the permitted length for the storage bin name.

The storage bin sections that you have defined for warehouse 0001 and storage type 0007 (shown in the following table) form the basis of the example. Assuming that the storage bin is named 02-10-01, the system identifies the three storage bin sections in the main storage bin as follows: 02-10-01/1 02-10-01/2 02-10-01/3

Once you have defined storage bin sections for a storage type, you cannot change them.

Assignment of Storage Bins and HU Types


For each storage type, you assign the appropriate storage bin sectioning to each allowed combination of storage bin type (Storage Bin Type field) and HU type (HU Type field).

Assign Storage Bin Types and HU Types


WNr 0001 0001 Type 0007 0007 BinTy PA PA HU Type E1 IP SecKey B A No. Bin Secs 3 2

SAP Extended Warehouse Management (SAP EWM)

510

384

SAP Online Help

20.07.2007

When you create storage bins for this strategy, you must specify a storage bin type. This storage bin type must match the storage bin type in the table for assigning storage bin types and HU types (see above). Once you have made these assignments, you cannot change them later. When you put away products into a storage type for which storage bin sectioning has been defined, you must enter the HU type in the preparation screen of the warehouse task. The system uses this HU type to search for suitable empty storage bins. At the same time, the system ensures that you put away only one HU type per storage bin.

Additional Option
If you assign the same storage bin type and a different HU type to the same section key, you can also put away more than one pallet type into the same storage bin.

Assign Storage Bin Types and HU Types


WNr 0001 0001 0001 Type 0007 0007 0007 BinTy PA PA PA HU Type E1 IP E2 SecKey B A A No. Bin Secs 3 2 2

If you define the table as shown above, you can place an industrial pallet (IP) into the first section of the storage bin and an HU with the type E2 into the second section of the storage bin.

SAP Extended Warehouse Management (SAP EWM)

510

385

SAP Online Help

20.07.2007

Example: Optional HU Check When Creating a WT


The system can only find the appropriate storage bins for a handling unit type when creating warehouse tasks (WT) if you have activated the HU type check. You can enter *** as an allowed HU type in this table. This entry means that all the HU types in this storage type are allowed. The system then searches for a suitable storage bin for the HU type on the basis of the allowed storage bin types per HU type.

Before you activate the optional HU type check, you should check the table parameters carefully. If the configuration settings are not optimal, you may encounter performance problems.
The following example outlines the performance problems associated with the optional HU type check and their solutions:

Storage bin types P1, P2, P3, P4, and P5 are allowed for HU type E1. The system is to put away HU type E1 in storage type 0001. However, only storage bins of the type P0 are available in this storage type. The system is not allowed to put away HU type E1 in storage type 0001. A system that has been configured optimally recognizes this (since access to a completely buffered table is possible) and searches for a suitable storage bin in the next storage type. In the optional HU type check, the system tries to access the database five times without success. If you work with different storage sections, this number increases accordingly.

You can easily check the Customizing settings by viewing the log for the storage bin search. The greater the number of unsuccessful attempts that the system has made, the more ineffective the process for storage bin determination becomes. You should reduce the number of attempts by optimizing the storage type search.

SAP Extended Warehouse Management (SAP EWM)

510

386

SAP Online Help

20.07.2007

Strategy: Bulk Storage


Use
Products such as tires, glass products, and drinks that come in large quantities and require a large amount of storage space are often stored in bulk storage. The advantages of bulk storage include: Reduced need for physical storage bins Fast access to the containers Clear structuring of the warehouse (into blocks and rows)

This strategy searches for storage bins in bulk storage. The figure below shows bulk storage:
HU Type E1

XX Row 02

Bin: A05-01 A05-02 Quant: XX XX HU Type: I1 E1

A05-03 A05-04 ZZ E1

The most important features of bulk storage processing are: Freely-defined coordinate structure When you define the storage bins in bulk storage, you do not have to take any technical prerequisites of the system into account. The warehouse is divided into blocks, which in turn are divided into individual rows. One storage bin per row In practice, a row is selected as the sort characteristic in bulk storage. In the system, a row is created and managed as a storage bin. The storage bins (rows) are classified according to storage bin types. For example, rows 2 and 3 in block A05 (illustrated in the above figure) can hold up to 16 pallets. However the 4th row can only hold a maximum of 12 pallets, due to a structural column in the row. You can enter this exception (reduced capacity of a row) when defining the block structure (see section Prerequisites). Different HU types In bulk storage, you often manage different HU types with different dimensions, for example, standard pallets and industrial pallets with clip-on mounts. Extended Warehouse Management (EWM) supports the management of different HU types in bulk storage. Mixed storage

SAP Extended Warehouse Management (SAP EWM)

510

387

SAP Online Help

20.07.2007

You do not put away HUs with different products in the same row. However, in general, all combinations of mixed storage are allowed in bulk storage. You can also define that all products in the storage bin must have the same batch. Automatic blocking per row To optimize the putaway and stock removal processes in bulk storage, you can set a blocking indicator for each row separately.

Prerequisites
You have made the following settings for the storage type in Customizing for Extended Warehouse Management (EWM) under Master Data Define Storage Type: You have chosen the Bulk Storage value in the Storage Behavior field. You have chosen the Addition to Existing Stock/Empty Bin value in the Putaway Rules field. You have chosen the Addition to existing stock permitted value in the Addn.Stock Forbidden field. Do not activate the HU type check and do not choose a capacity check method. A capacity check and HU type check are not necessary in bulk storage because an internal check is carried out based on the block structure definition. Choose the required option in the Mixed Storage field. For more information about the permitted combinations, see the relevant field help.

When defining the storage type control for this strategy, you must take into consideration the following indicators, among others, to control the putaway of products into bulk storage: Putaway blocking for row Time limit for blocking

For more information about these control options, see the Implementation Guide (IMG) for EWM under Goods Receipt Process Strategies Putaway Rules Putaway Behavior: Bulk Storage Storage Type Control for Bulk Storage.

Definition of Bulk Storage Indicators


For this strategy, you can enter bulk storage indicators together with a description. Using the bulk storage indicator, you define how you want to store a particular product in bulk storage. To do this, you enter the bulk storage indicator in the product master record and again in the bulk storage sectioning table when defining the structure of a block.

Block Structure Definition


You can define various characteristics of bulk storage such as storage bin types, HU types, maximum number of stacks, and stacking height. When you define storage bins for bulk storage you must enter a storage bin type.

Other Control Options


In the product master record (in the Warehouse Management view), you can Define up to three HU types Set the bulk storage indicator Set the indicator allowing addition to existing stock

SAP Extended Warehouse Management (SAP EWM)

510

388

SAP Online Help

20.07.2007

SAP Extended Warehouse Management (SAP EWM)

510

389

SAP Online Help

20.07.2007

Cross-Line Stock Putaway


Use
In the case of this function, a sort sequence supports the system when searching for suitable storage bins. You can use sort sequences to prevent one part of the warehouse from being overburdened and to optimize the putaway of goods. If you have not defined a sort sequence, the system sorts by storage bin name.

We recommend cross-line stock putaway for storage types with the following settings: Storage behavior Standard Warehouse and putaway rule Empty Bin Storage behavior Pallet Storage

If the system cannot find a storage bin for the addition to existing stock, it uses sort sequences to search for a storage bin. This means that you can also define cross-line stock putaway for storage types with the storage behavior Standard Warehouse and putaway rule Addition to Existing Stock/Empty Bin or with the storage behavior Bulk Storage.

Prerequisites
You have defined a sort sequence for cross-line stock putaways in Customizing for Extended Warehouse Management (EWM). To do so, you have performed the following steps: a. You have defined an activity for cross-line stock putaway in your warehouse number for the activity CLSP with warehouse process category 8 (Cross-Line Stock Putaway) under Master Data Activity Areas Activities Define Activities. b. You have generated an activity area for the storage type in which you want to perform the cross-line stock putaway under Master Data Activity Areas Generate Activity Area from Storage Type. The activity area must match the storage type, in other words, it must contain the same storage bins. The system gives the generated activity area the same name as the storage type. c. You have defined a sort sequence for cross-line stock putaway under Master Data Activity Areas Define Sort Sequence for Cross-Line Stock Putaway.

You have created a storage bin sorting on the SAP Easy Access screen under Extended Warehouse Management Master Data Storage Bin Sort Storage Bins.

SAP Extended Warehouse Management (SAP EWM)

510

390

SAP Online Help

20.07.2007

Capacity Check
Use
In the case of some putaway strategies, it is useful to perform a capacity check for the storage bin when searching for a suitable storage bin. If you have activated the capacity check, the system checks whether the selected storage bin can accept the quantity to be put away when it creates a warehouse task (WT).

Prerequisites
You can set up the capacity check in Customizing for Extended Warehouse Management (EWM) under Master Data Define Storage Type (Putaway Control, Capacity Check field). By default, the checks are predefined in accordance with weight and volume. To control the capacity check in accordance with weight or volume, you have defined the following: You have defined the weight or volume consumption for each storage bin. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Master Data Storage Bin Create Storage Bin (Stor. Bin tab page, Weight Usage or Volume Usage field). You have defined a weight or volume consumption per unit of measure for each product in the product master. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Master Data Product Maintain Warehouse Product (Units of Meas. tab page).

To control the capacity check in accordance with the capacity key figure, you have defined the following: You have defined a capacity that is independent of a dimension or a unit for each storage bin. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Master Data Storage Bin Create Storage Bin (Stor. Bin tab page, Capacity Usage field). You have defined a capacity consumption per unit of measure for each product in the product master. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Master Data Product Maintain Warehouse Product (Units of Meas. tab page, Capacity Consumption field). You have defined a capacity consumption per unit of measure for each packaging material in the product master. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Master Data Product Maintain Warehouse Product (Units of Meas. tab page).

Features
Extended Warehouse Management (EWM) can check the capacity of a storage bin using the following factors: Weight The system checks the weight of the product to be put away against the available weight of the storage bin. Volume The system checks the volume of the product to be put away against the available volume of the storage bin. SAP Extended Warehouse Management (SAP EWM) 510 391

SAP Online Help

20.07.2007

Capacity key figure (see below) Capacity check in accordance with product This capacity check is recommended if you can stack products in the storage bin in any way you like. You can also apply this capacity check if different batches of the product exist that result in mixed storage. Capacity check in accordance with handling unit (HU) This capacity check is recommended if the HUs lie next to one another and you can remove the products one after another from each container. Capacity check in accordance with product and HU

If you work with fixed storage bins or use the putaway strategy Addition to Existing Stock, we recommend a capacity check. In bulk storage, the capacity check is performed via the block definition.

Capacity Check in Accordance with Capacity Key Figure


You can also use a capacity key figure to control how a product is put away in a storage bin. Here the system calculates the capacity consumption in different ways, depending on the capacity check chosen: Capacity check in accordance with product The system calculates the capacity consumption for the product on the basis of the quant (quantity of a product with the same attributes). Capacity check in accordance with HU In the case of HU checks, the system calculates the capacity consumption on the basis of the HU. Capacity check in accordance with product and HU In the case of mixed storage, we recommend the capacity check in accordance with the product and HU.

Example 1

Example 2

Example 3

The capacity consumption of a product refers to the product quantity and is therefore specified as a variable in the system, and updated in the quant. The capacity consumption of an HU is specified as a constant capacity consumption, and is updated in the HU.

SAP Extended Warehouse Management (SAP EWM)

510

392

SAP Online Help Quant and HU data is updated for each storage bin as remaining capacity.

20.07.2007

You have to define the type of capacity check as well as the capacity consumption of the product and HU before the first putaway. Subsequent changes to these parameters result in automatic changes to storage bins, HUs, and quants. You must not make such changes when the system is running in productive mode since they result in inconsistencies. For more information about the capacity check in accordance with the capacity key figure, see Examples of Capacity Check in Accordance with Capacity Key Figure [Seite 394].

SAP Extended Warehouse Management (SAP EWM)

510

393

SAP Online Help

20.07.2007

Examples of Capacity Check in Accordance with Capacity Key Figure


In the following section, you find an example of each of the three types of capacity check in accordance with the capacity key figure.

Capacity check in accordance with product


The storage bin 01-01-01 has a total capacity of 100. Each piece of product 4711 has a capacity consumption of 11. This means that you can put away nine pieces of product 4711 in this storage bin. Here you have a remaining capacity of one.
Storage Bin 01-01-01 Total Capacity = 100 Product 4711 Capacity Consumption = 11

9 x 11 = 99 Remaining Capacity = 1

Capacity check in accordance with HU


The storage bin 01-01-01 has a total capacity of 100. Each wire basket has a capacity consumption of 12. This means that you can put away eight wire baskets in the storage bin. Here you have a remaining capacity of four.
Storage Bin 01-01-01 Total Capacity = 100

Product 4711 HU Capacity Consumption = 12

8 x 12 = 96 Remaining Capacity = 4

SAP Extended Warehouse Management (SAP EWM)

510

394

SAP Online Help

20.07.2007

Capacity check in accordance with product and HU


The storage bin 01-01-01 has a total capacity of 100. Each piece of product 4711 has a capacity consumption of eleven. Each pallet has a capacity consumption of 12. You can put way one pallet with eight pieces of product 4711 in the storage bin. As a result, the storage bin no longer has any available capacity.
Storage Bin 01-01-01 Total Capacity = 100

Product 4711 Capacity Consumption = 11 HU Capacity Consumption = 12

(8 x 11) + (1 x 12) = 100 Cubic Meters, for example Remaining Capacity = 0

SAP Extended Warehouse Management (SAP EWM)

510

395

SAP Online Help

20.07.2007

Stock Removal Strategies


Use
You use stock removal strategies [Extern] to define where the system is to search for stock, in other words, in which storage types, and how it is to sort the stock that has been determined. Stock is determined in the following cases: Warehouse task (WT) creation Creation of warehouse requests Changing warehouse request items

Prerequisites
You make the settings for the stock removal strategies in Customizing for Extended Warehouse Management (EWM) under Goods Issue Process Strategies. For more information, see the Implementation Guide (IMG) and the documentation for the individual strategies.

Features
The following table shows possible stock removal strategies: Strategy FIFO (First In, First Out) [Seite 397] Stringent FIFO for All Storage Types [Seite 398] LIFO (Last In, First Out) [Seite 399] Partial Quantities First [Seite 400] Stock Removal Suggestion According to Quantity [Seite 402] Shelf Life Expiration Date [Seite 403] Comment With FIFO, the system searches for the oldest quant. With stringent FIFO, the system searches across all storage types. With LIFO, the system searches for the most recent quant. The system first searches for partial quantities and then for standard quantities. The system determines the storage bin on the basis of the quantity. The system searches for products with the shortest remaining time before the expiration date. The system searches for a fixed storage bin.

Fixed Storage Bin [Seite 404]

You can use the BAdIs in the /SCWM/ES_CORE_RMS enhancement spot to make changes to these putaway strategies. See Also: Storage Bin Determination for Stock Removal [Seite 343]

SAP Extended Warehouse Management (SAP EWM)

510

396

SAP Online Help

20.07.2007

Strategy: FIFO (First In, First Out)


Use
In the case of this strategy, the system first proposes the oldest quant from the storage type from which you want to remove products from stock. The system calculates the age of a quant (its retention period in the warehouse) from the date when goods receipt was posted. The goods receipt date is set automatically in the quant and in the warehouse request for each goods receipt posting. You can accept the goods receipt date that the system sets or you can enter a different date. Regardless of whether you adopt the goods receipt date or enter a new one, the system uses this date to calculate the age of the quant. This date influences the sort sequence for each product.

Prerequisites
You have defined a stock removal rule in Customizing for Extended Warehouse Management (EWM) under Goods Issue Process Strategies Specify Stock Removal Rule. You have specified the goods receipt date (sort ascending) as the sort criterion. You have defined a storage type search sequence in Customizing for EWM under Goods Issue Process Strategies Specify Storage Type Search Sequence. You have assigned the storage type search sequence in Customizing for EWM under Goods Issue Process Strategies Determine Storage Type Search Sequence for Stock Removal. You have assigned the stock removal rule to the storage type in Customizing for EWM under Master Data Define Storage Type. Alternatively, you can assign the stock removal rule under Goods Issue Process Strategies Determine Storage Type Search Sequence for Stock Removal.

SAP Extended Warehouse Management (SAP EWM)

510

397

SAP Online Help

20.07.2007

Strategy: Stringent FIFO Across All Storage Types


Use
In Extended Warehouse Management (EWM), you can remove stock according to the FIFO principle where you take into consideration all quants within a warehouse number. In this case, the system does not scan individual storage types in sequence but instead it proposes the oldest quant in the entire warehouse as the quant to be removed from stock.

Prerequisites
See Strategy: FIFO (First In, First Out) [Seite 397] You have also defined storage type groups and assigned all relevant storage types to them in Customizing for EWM under Master Data Define Storage Type Groups.

SAP Extended Warehouse Management (SAP EWM)

510

398

SAP Online Help

20.07.2007

Strategy: LIFO (Last In, First Out)


Use
For some warehouse organizations or sectors of industry, you cannot use the FIFO principle. For example, in the building material industry, products that are to be removed from stock and are therefore being stored temporarily are stacked on products that are already stored in the warehouse. When using the FIFO strategy, the warehouse worker would first have to remove the products lying on top to get to the product with the oldest goods receipt date. The LIFO strategy is provided for such situations. When the system searches for a suitable quant to remove from stock, it always suggests the last quant that was placed into stock.

Prerequisites
See Strategy: FIFO (First In, First Out) [Seite 397] with the exception that you have specified the goods receipt date (sort descending) as the sort criterion.

SAP Extended Warehouse Management (SAP EWM)

510

399

SAP Online Help

20.07.2007

Strategy: Partial Quantities First


Use
With this strategy, the system overrides the FIFO principle to optimize the management of stock in the warehouse. It keeps the number of partial handling units (partial HUs) in one storage type as low as possible. This strategy is only suitable if putaway meets one of the following conditions: It takes place in the form of standard HU types (always the same quantity of a product for a certain HU type). It takes place in the form of partial pallet quantities (quantities smaller than a standard HU).

There are two different types of quant within a storage type: Quants in the quantity of the standard HU in accordance with packaging specification Quants in a quantity that is smaller than the standard HU. This is known as a partial pallet quantity. Quants that are larger than a standard HU should not occur.
...

When the system searches for a quant, it proceeds as follows:

1. If the required quantity in the warehouse task is the same as or greater than the quantity of a standard HU, the system attempts to remove a standard HU from stock. 2. If no standard HUs exist, the system takes partial pallet quantities. 3. If the required quantity in the warehouse task is less than the quantity of the standard HU, the system first tries to remove partial pallet quantities from stock. 4. If no partial pallet quantities exist, the system breaks into complete HUs.

Prerequisites
You have defined a stock removal rule with ascending quantity (piece) and a stock removal rule with descending quantity (standard HU) in Customizing for Extended Warehouse Management (EWM) under Goods Issue Process Strategies Specify Stock Removal Rule. You have assigned the stock removal rules in Customizing for EWM under Goods Issue Process Strategies Determine Storage Type Search

Sequence for Stock Removal:


Stock removal rule piece quantity classification group piece Stock removal rule standard HU quantity classification group standard HU

You have defined a storage type search sequence in Customizing for EWM under Goods Issue Process Strategies Specify Storage Type Search Sequence. You have assigned the stock removal rules in Customizing for EWM under Goods Issue Process Strategies Determine Storage Type Search Sequence for Stock Removal: You have defined quantity classifications for the warehouse in Customizing for EWM under Cross-Process Settings Warehouse Task Define Quantity Classifications. You have defined a packaging specification for the product in Customizing for SCM Basis under Packing Packaging Specification.

SAP Extended Warehouse Management (SAP EWM)

510

400

SAP Online Help

20.07.2007

Example
You use two packaging specification levels, pallet and piece, and you have defined a quantity classification and a stock removal rule for each of them. The system uses the stock removal rule for piece to sort the stock by quantity in an ascending order. The system uses the stock removal rule for pallet to sort the stock by quantity in an descending order. If the quantity required is greater than or equal to the quantity of the complete HU, the system sorts the stock in a descending order, in other words, it removes a full pallet from stock. If the required quantity is smaller than a complete HU, the system sorts the stock in an ascending order, in other words, since a complete HU is not required, the system searches for a partial HU.

SAP Extended Warehouse Management (SAP EWM)

510

401

SAP Online Help

20.07.2007

Strategy: Stock Removal Suggestion According to Quantity


Use
This strategy is based on whether the quantity required in the warehouse task is large or small. For example, you have a storage type in a warehouse in which you store small quantities of products (a storage type with a fixed storage bin structure). You also have a reserve storage area where you store larger quantities. The system decides whether it is dealing with a small quantity or a large quantity, depending on the quantity required in the warehouse task. It proposes that stock be removed from either the storage bin of the small quantity storage type or from the storage bin of the large quantity storage type. The system uses the quantity of the standard HU in accordance with the packaging specification as the criterion.

Processing Small and Large Quantities


The following figure shows the processing of small and large quantities:
Quantity to Be Removed from Stock Smaller Than/Equal to Qty of Standard HU Acc. to Packaging Specification

Yes

No

Fixed Bin Storage

High Rack Storage

Small Quantities

Large Quantities

In the example shown in the figure, two storage types are used to fill delivery notes from Sales and Distribution: Fixed bin storage High Rack Storage Area

The system selects the quant from a storage bin in fixed bin storage, if the required quantity is less than or equal to the quantity of the standard HU in accordance with the packaging specification. If the required quantity is greater than the quantity of the standard HU in accordance with the packaging specification, the system searches for the quant in high rack storage.

Prerequisites
See Strategy: Partial Quantities First [Seite 400] with the exception that you have defined and assigned two storage type search sequences.

SAP Extended Warehouse Management (SAP EWM)

510

402

SAP Online Help

20.07.2007

Strategy: Shelf Life Expiration Date


Use
With this strategy, the system ensures that the products with the oldest shelf life expiration date are removed from stock first.

Prerequisites
See FIFO (First In, First Out) [Seite 397] with the exception that you have specified the shelf life expiration date as the sort criterion.

SAP Extended Warehouse Management (SAP EWM)

510

403

SAP Online Help

20.07.2007

Strategy: Fixed Storage Bin


Use
In the case of this strategy, the system uses the storage bin that was entered in the product master to find stock. If you have allowed fixed storage bin assignments for a storage type, the system also takes into consideration the storage bins that do not contain any stock when determining the stock. In this way, it is possible that the system creates warehouse tasks (WTs) for which no stock exists. You use replenishment control to ensure that products are available in the storage bin at the time of picking. Negative available stock is allowed with this strategy. To clear the pick items or the pick quantity per storage bin, you can specify that the system is to sort the stock by open stock removal items per storage bin or by open quantity to remove per storage bin.

Prerequisites
You have defined a stock removal rule and, optionally, specified the open stock removal items or the open quantity to remove per storage bin as the sort criterion in Customizing for Extended Warehouse Management (EWM) under Goods Issue Process Strategies Specify Stock Removal Rule. You have defined a storage type search sequence in Customizing for EWM under Goods Issue Process Strategies Specify Storage Type Search Sequence. You have assigned the storage type search sequence in Customizing for EWM under Goods Issue Process Strategies Determine Storage Type Search Sequence for Stock Removal. You have defined fixed storage bins in the master data for EWM under Storage Bin Maintain Fixed Storage Bin. You have set the Fixed Bins Allowed indicator in Customizing for EWM under Master Data Define Storage Type. Optionally, you have set the Negative Stock indicator if you want to permit negative available stock.

SAP Extended Warehouse Management (SAP EWM)

510

404

SAP Online Help

20.07.2007

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 Internal goods movements Posting changes Goods receipt postings Goods issue postings

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]
PROD WT

HU WT

HU WT

PROD WT HU WT

Product Warehouse Task Handling Unit Warehouse Task

You or the system use product warehouse tasks, for example, for deconsolidation [Seite 298] and handling unit warehouse tasks, for example, for unloading [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, see Pick Point [Seite 410]. EWM also submits hazardous substance texts [Seite 969] in the warehouse task. When you confirm a warehouse task, you can also perform a physical inventory at the same time [Seite 670]. Here, EWM can work with the low-stock physical inventory.

SAP Extended Warehouse Management (SAP EWM)

510

405

SAP Online Help

20.07.2007

Product Warehouse Task


Definition
Document that helps Extended Warehouse Management (EWM) move products. A product warehouse task (product WT) can be based on physical goods movements or changes in stock.

Use
The product WT contains all the information required to execute the physical transfer of products into the warehouse, out of the warehouse, or within the warehouse from one storage bin to another storage bin. When you confirm a product WT, you inform EWM what you have processed this product WT and that the goods have arrived at their destination. If the planned quantity (target quantity) differs from the actual quantity of stock that is moved, a difference quantity exists. If you confirm a product WT with a difference, the system automatically posts the difference quantity to a difference interface. Once confirmed, the product WTs also have a documentation function, since they document movements in the warehouse.

Structure
A product WT contains all necessary information about a goods movement to be executed. What should be moved? Which quantity should be moved? From where (source storage bin) should the product be moved, and to where (destination storage bin)?

When you create a product WT, it consists of an item with the source storage bin and destination storage bin. When you confirm a product WT, it consists of either an item with the source destination bin or destination storage bin, or it consists of more than one item in the case of partial confirmations. For goods receipt postings, the product WT consists of an item that increases the stock. For goods issue postings, the product WT consists of an item that decreases the stock. For transfer postings, the product WT consists of two items. One item that decreases the stock, and one item that increases the stock. In the case of partial confirmations, EWM creates one item for each partial confirmation. You create partial confirmations, for example, when you partially pick from a nested handling unit, or when you confirm different pick handling units.

A product WT reserves the quantities, so that these are no longer available for other product WTs.

SAP Extended Warehouse Management (SAP EWM)

510

406

SAP Online Help

20.07.2007

Handling Unit Warehouse Task


Definition
Document that helps Extended Warehouse Management (EWM) to move handling units (HUs). A handling unit warehouse task (HU WT) is based on goods movements.

Use
The HU WT contains all the information required to execute the physical transfer of HUs within the warehouse from one storage bin to another storage bin. As an exception, you can also use the HU WT for the loading and unloading process. When you confirm a HU WT, you inform EWM what you have processed this HU WT and that the goods have arrived at their destination. Once confirmed, the HU WTs also have a documentation function, since they document movements in the warehouse.

Structure
An HU WT contains all necessary information about a goods movement to be executed. Which HU should be moved? From where (source storage bin) should the HU be moved, and to where (destination storage bin)?

The HU WT always consists of an item with the source destination bin and destination storage bin. It does not reserve any quantities.

SAP Extended Warehouse Management (SAP EWM)

510

407

SAP Online Help

20.07.2007

Identification Point
Definition
Place in an automated warehouse at which you identify newly-arrived goods.

Use
In many warehouses, certain storage types (such as high rack storage areas) require identification points (ID points). In these warehouse types, you have to use the ID point to execute the putaway of all handling units (HUs). In Extended Warehouse Management (EWM), the ID point is a physical place in a HU-managed warehouse at which you identify goods receipts for further processing. The following figure illustrates the transfer of products from the goods receiving zone to a high rack storage area using an ID point.

GR Zone

High Rack Storage Area

ID Point

For example, if you have assigned the ID point storage type 0081 to the storage type 0080, and want to put away goods in the storage type 0080, then EWM proposes the ID point storage type 0081.

Structure
The purpose of an Identification Point includes the following: Contour control A contour check often occurs at an ID point to determine whether the HU was built correctly. Changing the mode of transport A conveyor equipment change can occur at an ID point. For example, the HUs are loaded from a forklift onto a conveyor. To determine the final destination EWM determines the destination storage bin in the final storage type at the ID point. Since EWM only assigns the destination storage bin after the HU arrives at the ID point, EWM determines the location of the storage bin based on the most current information about the storage type's space availability.

SAP Extended Warehouse Management (SAP EWM)

510

408

SAP Online Help

20.07.2007

Integration
You define an ID point in EWM as the storage type identification point in Customizing for EWM under Master Data Define Storage Types, by setting the storage role Storage Type Is ID Point. You connect the ID point to the HU-managed storage type in which the putaways from the ID point are to occur: a. In Customizing, choose Master Data Define Storage Types. b. Select the storage type to which you want to assign the ID point. c. Choose ID Point Active. d. In Customizing for EWM, assign your IDpoint to a storage type, by choosing Cross-Process Settings Warehouse Task Define Layout-Oriented Storage Control.

...

For more information about layout-oriented storage control, see Layout-Oriented Storage Control [Seite 340]. For more information about Customizing for layout-oriented storage control, see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings Warehouse Task Define Layout-Oriented Storage Control.

SAP Extended Warehouse Management (SAP EWM)

510

409

SAP Online Help

20.07.2007

Pick Point
Definition
The pick point is the actual place in the warehouse at which you pick items for a partial stock pick from a handling unit (HU).

In an automated high rack storage area (HRSA), the pick point can be a certain point on the conveyor line along which you move the HUs for picking. A pick point can also be a marked floor area to which you bring entire pallets for removal of products.

Use
If you cannot execute partial stock picks in a storage type, for example due to physical restrictions in a high rack storage area, you use pick points to pick partial quantities or to repack. The following graphic illustrates how a partial stock pick occurs using a pick point.
Shelf Storage

Pick Point

Goods Issue Zone

Remainder

If you only want to pick a portion of the product quantity from the HU, you bring the HU to the HU-managed pick point to carry out the actual picking.
...

1. At the pick point, you pick the required product quantity from the HU and remove the required products to the goods issue zone. 2. After picking, you put away the HU with the remaining product quantity from the pick point back into the warehouse and confirm the HU warehouse task.

Return Transfer of HUs


You can putaway partial HUs back into the warehouse after picking at the pick point. You have determined a fixed storage type for the return transfer of HUs, because you have a special storage type for partial HUs, for example. In the Implementation Guide (IMG) for Extended Warehouse Management (EWM), choose Master Data Work Center Define Work Center. EWM determines a new storage bin in the storage type and creates a corresponding HU warehouse task with the destination storage bin. You putaway the partial HU back into the same storage type in which you previously removed it.

SAP Extended Warehouse Management (SAP EWM)

510

410

SAP Online Help

20.07.2007

You do not determine a fixed storage type for the return transfer of HUs. EWM determines the storage type as well as the destination storage bin by using putaway strategies [Seite 375].

Integration
You define a pick-point in EWM as the pick point storage type in Customizing for EWM, under Master Data Define Storage Type, by setting the storage role Storage Type Is Pick Point. You link the pick point to the HU-managed storage type from which the stock removals to the pick point are to occur: a. In Customizing for EWM, choose Master Data Define Storage Type. b. Select the storage type to which you want to assign the pick point. c. Specify Pick Point Active. d. In Customizing for EWM, assign your pick point to a storage type, by choosing Cross-Process Settings Warehouse Task Define Layout-Oriented Storage Control.

For more information about layout-oriented storage control, see Layout-Oriented Storage Control [Seite 340]. For more information about Customizing for layout-oriented storage control, see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings Warehouse Task Define Layout-Oriented Storage Control. You set your pick point as work center. In Customizing for EWM, choose Master Data Work Center Define Work Center.

SAP Extended Warehouse Management (SAP EWM)

510

411

SAP Online Help

20.07.2007

Creation of Warehouse Tasks for Warehouse Request


Use
Extended Warehouse Management (EWM) uses this function so that when you or EWM release a wave, EWM simultaneously creates warehouse tasks [Seite 405] for stock removal or internal stock movements. EWM creates warehouse orders pursuant to the warehouse tasks, to assemble work packages for the individual warehouse workers. Instead of this standard creation of warehouse tasks through wave release, you can also create a warehouse task as follows: Manually, with the user interface Automatically, by calling a Post Processing Framework action (PPF action)

Features
When EWM creates a warehouse task for a warehouse request, it uses putaway strategies [Seite 375] to determine the storage bin, or stock removal strategies [Seite 396] to determine the stock. For more information, see Storage Bin Determination for Putaway [Seite 291] or Stock Determination [Seite 341]. Extract Time Determination The extract time determination calculates the target time effort to execute a stock movement. EWM determines this time for each warehouse task. Warehouse order creation [Seite 419] adds up the extract time of the individual warehouse tasks for a warehouse order. Optionally, warehouse order creation supplements the extract time determination with a setup time that is defined in the warehouse order creation rule. In addition, if resource management is used, a route time is determined based on the resource used. The warehouse order includes the sum of these times. Based on this, EWM determines the latest start time of a warehouse order. The parameters of extract time determination formulas for a warehouse task are dependent on the product, the quantity, the unit to be transported, and geographical dependencies. For more information about Customizing for extract time determination, see the implementation guide (IMG) for EWM under Cross-Process Settings Warehouse Task Define Extract Time Determination.

Activities
When EWM creates a warehouse task for a warehouse request, it simultaneously updates this warehouse request. EWM carries out this update by updating the document flow. If the document flow update leads to a change in status, EWM updates this change in the warehouse request as well. By default, you or EWM create warehouse tasks by releasing a wave. After a wave is generated, it can be released immediately, either automatically or manually depending on the release methods you have defined for the wave or wave template. For more information, see Processing of Waves [Seite 771]. Instead of this standard creation of warehouse tasks through wave release, you can also create a warehouse task as follows:

SAP Extended Warehouse Management (SAP EWM)

510

412

SAP Online Help

20.07.2007

If you want to create warehouse tasks manually using the user interface, on the SAP Easy Access screen, choose Extended Warehouse Management Work Scheduling Create Warehouse Task for Warehouse Request and then the desired action (for example, Putaway for Inbound Delivery). If you want to create warehouse tasks automatically by calling a PPF action, on the SAP Easy Access screen, choose Extended Warehouse Management Print Display and Process PPF Actions.

SAP Extended Warehouse Management (SAP EWM)

510

413

SAP Online Help

20.07.2007

Determination of Priority for Inbound Deliveries


Purpose
You use Extended Warehouse Management (EWM) priority points to achieve an optimal unloading sequence for several trucks at transportation unit level in the yard. At the same time, EWM updates the inbound delivery until the Warehouse Activities Status is Completed.

Process
...

1. The ERP system receives an advanced shipping notification (ASN) and creates an inbound delivery. 2. The ERP system notifies SAP APO and EWM about this. 3. Based on the notification, the system executes the following: a. SAP APO calculates the priority points at item level. b. EWM creates an inbound delivery request. EWM or you activate the inbound delivery request. EWM creates an inbound delivery from the active inbound delivery request. The priority points in the inbound delivery are initial (initial value is zero) until SAP APO sends the results of the calculation for an update. 4. SAP APO communicates the calculated priority points to the ERP system, which then communicates them to EWM. 5. EWM updates the priority points in the inbound delivery. EWM saves the priority points for an inbound delivery at item level. EWM calls the Business Add-In (BAdI) /SCWM/EX_DLV_DET_LOAD to display the inbound delivery. This BAdI calculates an aggregated priority at header level. 6. EWM aggregates the priority points at transportation unit level using the BAdI /SCWM/EX_SR_PRIOP. You can see this on the user interface for unloading. You can start the report /SCWM/PRIOP_UPDREQ for the recalculation of priority points from the SAP Easy Access display, under Extended Warehouse Management Delivery Processing Inbound Delivery Update Priority Points. EWM triggers an asynchronous request for the recalculation of priority points in SAP APO via the ERP system. As with the first calculation (step 4), SAP APO sends the result of this recalculation to EWM via the ERP system. EWM updates the priority points in the inbound delivery and aggregates the priority points at transportation unit level.

For more information, see the report documentation.

Results
SAP APO has calculated the priority points and has communicated this to EWM via the ERP system . Provided the Warehouse Activities status is not Completed, EWM has updated priority points in the inbound delivery.

SAP Extended Warehouse Management (SAP EWM)

510

414

SAP Online Help

20.07.2007

Ad Hoc Movement
Use
Ad hoc movements are unplanned goods movements that you create manually within a warehouse. This means that the decision to make an ad hoc movement is not controlled by the system. Instead, it is triggered manually. Ad hoc movements do not have a preceding document. An ad hoc movement may be necessary for the following reasons: The wrong product is located in the storage bin. You have to take the product to another storage bin due to damage, for example for a quality inspection. You want to take a product to the appropriate storage bin for scrapping. You have to empty an aisle or storage bin for safety reasons. You want to perform unplanned rearrangement movements. You have to clear away stock lying around in the warehouse.

Prerequisites
Stock is available for the product to be moved. You have defined a warehouse process type in Customizing for EWM under CrossProcess Settings Warehouse Task Define Warehouse Process Type. If you do not enter a source or destination storage bin for ad hoc movement and want the system to determine this automatically, you can control this using stock removal and putaway strategies. For more information about prerequisites, see Putaway and Stock Removal Strategies [Seite 374].

Features
In an ad hoc movement, you move the stock of products from one storage bin to another. To be able to reproduce these movements, you manually create a product warehouse task (product WT) or a handling unit warehouse task (HU WT). If you work with HUs, you can also unpack or repack the products belonging to an HU by creating a product WT in the HU WT. The following table shows the significant data for manually creating product WTs and HU WTs: Product WT The system uses the product and source storage data from the stock overview that you have displayed by entering selection criteria. If you do not want the product to be removed from a specific storage bin, you can control the determination of the source storage data using stock removal strategies. Warehouse process type Destination storage data (optional) Reason (optional) Source quantity HU WT The system takes the HUs and source storage data from the overview.

Warehouse process type Destination storage data (optional) Reason (optional)

SAP Extended Warehouse Management (SAP EWM)

510

415

SAP Online Help

20.07.2007

You can manually overwrite the values determined by the system. For the values entered manually, the system checks if they match the configuration of the storage type, storage section, and storage bin in question, for example, if mixed storage or receipts are allowed. Immediate confirmation of the WTs is optional. Depending on the warehouse process type, you can confirm WTs directly after they have been created. While a WT is still open, in other words, until you have confirmed it, the assigned product quantity is not available at the source storage bin nor at the destination storage bin, but belongs to reserved stock. After you have confirmed a WT you can no longer delete it. You can, however, cancel it. Radio Frequency Environment In a radio frequency environment, you can also perform ad hoc movements for products and HUs. For more information, see Ad Hoc Movements Using Radio Frequency [Seite 809].

Actions
To create a product WT, on the SAP Easy Access screen, choose Extended Warehouse Management Work Scheduling Create Warehouse Task Without Reference Move Product. To create an HU WT, on the SAP Easy Access screen, choose Extended Warehouse Management Work Scheduling Create Warehouse Task Without Reference Move Handling Unit.

SAP Extended Warehouse Management (SAP EWM)

510

416

SAP Online Help

20.07.2007

Posting Change for Stocks


Use
In Extended Warehouse Management (EWM), you can make a posting change for stock, for example: From available stock to blocked stock (for example, in the case of a complaint) From available stock to customs blocked stock [Extern]

Prerequisites
You have made the settings for posting changes in the warehouse process type in Customizing for EWM under Cross-System Settings Warehouse Task Define Warehouse Process Type. Here you define, for example, whether a warehouse task (WT) is created automatically during the posting change, or whether it is to be created before or after the posting change. You have optionally defined destination data for stocks in conjunction with the warehouse process type that the system is to suggest for posting changes. You make these settings in Customizing for EWM under Internal Warehouse Processes Default Values for Posting Changes.

Features
You make a posting change for stock by changing the relevant stock attributes and then creating the posting change. You can change the following stock attributes, for example: Storage bin Stock type Batch Sales order or project

You want to move stock from available stock to quality inspection stock. You have the following options that you can configure in Customizing. The stock is to remain in the storage bin, but is no longer to be available for picking. In this case, the system does not create a WT and the stock is simply given a different stock type. You want to take the stock to the quality department. In this case, the system creates a WT. There are two options: The system creates the WT and then a posting change is made automatically for the stock when the destination storage bin is confirmed. The stock is booked out of the source storage bin and then the WT is created automatically.

You can make posting changes for stock for which serial numbers exist on a serial number basis. For more information about serial numbers, see Serial Number [Seite 571].

SAP Extended Warehouse Management (SAP EWM)

510

417

SAP Online Help

20.07.2007

Activities
To post stocks, on the SAP Easy Access screen, choose Extended Warehouse Management Work Scheduling Make Posting Change for Product.

In this transaction, you can choose and make a posting change for both available stock and the entire stock.

SAP Extended Warehouse Management (SAP EWM)

510

418

SAP Online Help

20.07.2007

Warehouse Order Creation


Use
This function groups together warehouse tasks into warehouse orders, according to your settings in Customizing for warehouse orders [Seite 423], and thus creates optimum work packages for you. For warehouse order creation, you define rules with their relevant criteria. Warehouse order creation is particularly suitable for optimizing processes for picking.

Integration
You assign warehouse orders to warehouse workers in resource management.

Prerequisites
You have defined the following in Customizing for Extended Warehouse Management (EWM): Number Ranges for Warehouse Orders For more information about defining number ranges for warehouse orders, see the Implementation Guide (IMG) for EWM under Cross-Process Settings Warehouse Order Define Number Ranges for Warehouse Order. Storage Bins For more information about defining number ranges for warehouse orders, see the IMG for EWM under Master Data Storage Bins. Activity Areas For more information about defining number ranges for warehouse orders, see the IMG for EWM under Master Data Activity Areas Define Activity Area. Start Bins To do so, on the SAP Easy Access screen, choose Extended Warehouse Management Master Data Storage Bin Assign Start/End Storage Bin for Activity Area.

Features
A wave consists of a number of deliveries. After the wave and wave item have been released (either automatically by EWM or manually by a user), EWM creates warehouse tasks. EWM joins the warehouse tasks together into warehouse orders, according to the warehouse order creation rules (WO creation rules) you have defined. A warehouse order can contain warehouse tasks from more than one delivery. You can create locked warehouse orders resulting from the wave release. You cannot initially continue to process these warehouse orders. You can use a method in the warehouse management monitor [Seite 878] to release the lock on the warehouse orders. If you want to release the lock on a warehouse order, you can select the Unlock WO method, for example, in the warehouse management monitor in the dialog structure under the node Documents Warehouse Order using the More Methods action menu (see Processing Waves [Seite 771]). During this summarization of the warehouse tasks into warehouse orders, EWM uses the search sequence for WO creation, for example, first rule A, then B, then C. EWM works through the WO creation rules in sequence, as you have defined for each activity area. You can change the sequence subsequently. Filters and limit values control which warehouse tasks and how many warehouse tasks EWM groups together into a warehouse order.

SAP Extended Warehouse Management (SAP EWM)

510

419

SAP Online Help

20.07.2007

The individual WO creation rule can contain sort rules [Extern]. As soon as EWM applies a WO creation rule, it sorts the warehouse tasks according to these sort rules. Since the work packages for the warehouse employee are based on the complete summarization of warehouse tasks into warehouse orders, then after all user-defined WO creation rules have been applied, no warehouse tasks must be left over that are not assigned to a warehouse order. If EWM has applied all the user-defined WO creation rules for the search sequence, and there are still unprocessed warehouse tasks, the system uses a remainder rule [Extern] . This rule creates warehouse orders for the remaining warehouse tasks. EWM summarizes these warehouse tasks according to the following criteria: For each activity area For each queue For each consolidation group [Extern]

If you do not define your own WO creation rules for the current activity area, then warehouse order creation uses a standard rule [Extern] . This rule attempts to group deliveries according to the following criteria: For each activity area For each queue For each delivery

You can use the following parameters to define creation of warehouse orders in detail for your warehouse processes: Sorting rule For more information about defining sorting rules, see the IMG for EWM under CrossProcess Settings Warehouse Order Define Sorting Rules for Warehouse Tasks. Filters For more information about item filters or subtotal filters, see Filters for Warehouse Order Creation Rules [Seite 424]. Limit value For more information, see Limit Values for Warehouse Order Creation Rules [Seite 425]. Parameters for packing You use these parameters to specify the number of handling units for a warehouse order. You specify these parameters in a packing profile, which you assign to a packaging specification. For more information about defining packing profiles, see the IMG for EWM under Cross-Process Settings Warehouse Order Define Packing Profile for Warehouse Order Creation. Packing mode Consolidation group During warehouse order creation, the consolidation group influences which warehouse tasks you are permitted to pack together. EWM determines the consolidation group in the delivery, and transmits it to the relevant warehouse tasks.

You define the maximum number of consolidation groups in a warehouse order as the definition of a limit value.

SAP Extended Warehouse Management (SAP EWM)

510

420

SAP Online Help You can simulate creation of warehouse orders for your warehouse tasks.

20.07.2007

You can define control parameters for warehouse order creation. For example, you can activate the log for WO creation for each warehouse number, activity area or warehouse order creation rule, or specify the number of work processes depending on the warehouse number.

Activities
EWM creates a list of warehouse requests. EWM groups the warehouse requests into a wave (for example, a wave pick) and releases it. EWM starts warehouse order creation, and uses the wave as a basis for creating a suitable number of warehouse tasks. EWM creates warehouse orders for each warehouse task, according to your Customizing settings, which contain the relevant warehouse tasks. For more information about making settings for the sorting rules, filters, limit values, parameters for packing, and the packing mode, see the IMG for EWM under Cross-Process Settings Warehouse Order Define Sort Rules for Warehouse Tasks Define Filters for Warehouse Order Creation Rules Define Limit Values for the Size of Warehouse Order Define Packing Profile for Warehouse Order Creation, and select an option for Split WT. Define Packing Profile for Warehouse Order Creation, and select an option for Split TO.

For more information about setting the consolidation group, see the IMG for EWM under Goods Receipt Deconsolidation Define Number Ranges for Consolidation Group or Extended Warehouse Management Goods Issue Define Number Range for Consolidation Groups.

If you want to simulate warehouse order creation for your warehouse tasks, then on the SAP Easy Access screen choose Extended Warehouse Management Monitoring Warehouse Management Monitor.

... ...

i. ii. iii. iv. v.

Choose warehouse number 0001, the monitor SAP and Open Documents Warehouse Tasks.

Execute.

In the dialog box, choose the warehouse task status Open and Execute. Select one or more open warehouse tasks and choose Other Methods Simulate Warehouse Order. The WO Create Rule dialog box appears. Enter a warehouse order creation rule. If you do not make an entry, then EWM executes the warehouse order creation rules according to the search sequence for warehouse order creation rules.

SAP Extended Warehouse Management (SAP EWM)

510

421

SAP Online Help

20.07.2007

If you want to define control parameters for warehouse order creation, from the SAP Easy Access choose Extended Warehouse Management Settings Warehouse Order Set Up Control Parameters for Warehouse Order Creation.

SAP Extended Warehouse Management (SAP EWM)

510

422

SAP Online Help

20.07.2007

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
EWM creates warehouse tasks for an outbound delivery with four delivery items. EWM uses warehouse order creation to assign the resulting four warehouse tasks to a new warehouse order. A warehouse employee receives this warehouse order as a work package to pick the items listed in the delivery.

SAP Extended Warehouse Management (SAP EWM)

510

423

SAP Online Help

20.07.2007

Filters for Warehouse Order Creation Rules


Definition
The filter for a warehouse order creation rule decides whether Extended Warehouse Management (EWM) processes a warehouse task using a creation rule. Warehouse order creation uses the filters on all warehouse tasks that you have not yet assigned to a warehouse order, and which WO creation should process.

Use
You can define two types of filters: Item Filters [Extern] and Subtotal Filters [Extern]. Item Filter You define item filters, so that EWM checks the individual warehouse task against the filter criteria defined in your Customizing settings. During processing of a warehouse task, EWM checks whether the given item filter fits. If the filter fits the warehouse task, then EWM continues processing for the warehouse task. If it does not fit, EWM stops processing the warehouse task. EWM checks, according to your Customizing settings, whether it should use another warehouse order creation rule to check the warehouse task that has not yet been processed. For more information about Customizing for filter parameters for warehouse tasks, see the Implementation Guide (IMG) for EWM under Cross-Process Settings Warehouse Order Define Filters for Warehouse Order Creation Rules. Subtotal Filter You define subtotal filters, so that EWM can use the filter criteria defined in your Customizing settings to compare several warehouse tasks against a subtotal, containing values you have defined. During this, EWM works out the subtotal for each consolidation group. You must have defined sorting rules with the sort field DSTGRP (consolidation group), for the warehouse tasks to process. For more information about defining sorting rules, see the IMG for EWM under Cross-Process Settings Warehouse Order Define Sorting Rules for Warehouse Tasks. During processing of several warehouse tasks, EWM checks whether the given item or subtotal filter fits. If the filter fits the transfer orders, then EWM continues processing for the warehouse tasks. If it does not fit, EWM stops processing the warehouse tasks. In the case of a subtotal filter, this means that EWM does not process the entire group of warehouse tasks for a consolidation group using the current filter. EWM checks, according to your Customizing settings, whether it should use another warehouse order creation rule to check the warehouse tasks that have not yet been processed. For more information about Customizing for filter parameters for warehouse tasks, see the IMG for EWM under Cross-Process Settings Warehouse Order Define Filters for Warehouse Order Creation Rules.

SAP Extended Warehouse Management (SAP EWM)

510

424

SAP Online Help

20.07.2007

Limit Values for Warehouse Order Creation Rules


Definition
The limit value of a warehouse order creation rule specifies the size of a warehouse order.

Use
During warehouse order creation, Extended Warehouse Management (EWM) compares the warehouse tasks that passed the checks in the warehouse order creation rule (for example, filter criteria), against the limit values defined in your Customizing settings. As soon as the transfer orders exceed one of the limit values, EWM creates a warehouse order containing all the warehouse tasks that do not exceed the limit value. EWM creates new warehouse orders for the remaining warehouse tasks. It continues with this process until it has processed all the warehouse tasks. For more information about Customizing for limit values for warehouse orders, see the Implementation Guide (IMG) for EWM under Cross-Process Settings Warehouse Order Define Limit Values for the Size of a Warehouse Order.

SAP Extended Warehouse Management (SAP EWM)

510

425

SAP Online Help

20.07.2007

Printing Warehouse Orders and Warehouse Tasks


Use
Extended Warehouse Management (EWM) can use this function to automatically print lists during creation of warehouse orders and warehouse tasks, according to your Customizing settings. These lists contain information about the storage bin to and from which a warehouse employee should move specific goods. You can use this function in the warehouse management monitor, from the user interface for warehouse tasks, to manually print a warehouse order, which also prints all corresponding warehouse tasks. For example, the first printout is damaged, or your require a second printout.

Integration
Printing of warehouse orders and warehouse tasks is based on SAPscript texts and SAP Smart Forms as form templates. EWM uses the Post Processing Framework (PPF) for message control. Additionally, EWM uses condition technique in the schedule condition for PPF, in order to determine the printer, the form type, and the spool parameter.

For more information about the structure and Customizing for the Post Processing Framework, see the SAP Library under SAP NetWeaver Components SAP Web Application Server Basis Services/Communication Interface (BC-SRV) SAP Communication: Configuration (BC-SRV) Business Workplace and Services (BC-SRV-OFC) Generic Business Tools for Application Developers (BC-SRV-GBT) Post Processing Framework (BCSRV-GBT). For more information about the condition technique, see the SAP Library under mySAP Customer Relationship Management CRM Enterprise Enterprise Sales Sales Management for Commercial and Industrial Customers Basic Functions Condition Technique.

Prerequisites
You have made the settings in Customizing for PPF: You have defined the PPF action definitions with the relevant processing types. In Customizing for the PPF action definition, you have defined the following data: Processing time Scheduling Determination Technique Rule type Action Merging

You have specified the PPF conditions for the defined PPF action definitions. In Customizing for the condition technique, you have defined the condition tables.

SAP Extended Warehouse Management (SAP EWM)

510

426

SAP Online Help

20.07.2007

In Customizing, you have defined your condition tables from the field catalog, which SAP delivers. You have selected fields from the field catalog as key fields. These fields represent the condition under which the condition technique finds the condition record. If a data record transferred by EWM matches your key fields, then condition technique finds the matching condition record. In Customizing, you have defined condition types, and therefore the access sequence to the condition tables to search. In Customizing, you have assigned the relevant condition schemas to your condition types. The condition schema specifies the conditions that you permit for determining data (such as printer, form type) and specifies the sequence (access sequence) in which condition technique should consider them. In Customizing, you have assigned the condition schema to the application object (warehouse process type, packaging material type, work center). In Customizing, you have defined the condition maintenance group. The condition maintenance group is required for creating condition records. The condition maintenance group specifies the condition tables and therefore the key fields. You have defined the logical conditions that you want to use in the condition records. You have defined warehouse-number-specific print settings (in particular the spool parameters).

Features
For printing warehouse orders, the following action definitions are supported in PPF in the application /SCWM/WME in the action profile /SCWM/HU. These action definitions were created for each form type, and thus enable you to simultaneously print several different documents, for example, printing a warehouse order list and printing individual documents for the warehouse order. For each action definition there is also an SAP Smart Forms form. The system only supports printing of SAP Smart Forms. The following table gives you an overview of the action definitions and their corresponding SAP Smart Forms forms. The assignment between action definition and SAP Smart Forms form is specified in the created condition records. Action Definition WO_MULTIPLE WO_SINGLE Description Print list for warehouse order with serial numbers Print single document for warehouse order with serial numbers Print shipping label Print loading instruction with warehouse tasks Print unloading instruction with warehouse tasks SAP Smart Forms Form /SCWM/WO_MULTIPLE /SCWM/WO_SINGLE

WO_HUSHIP WO_LOAD WO_UNLOAD

/SCWM/WO_HUSHIP /SCWM/WO_LOAD /SCWM/WO_UNLOAD

During warehouse order creation, transfer order confirmation, and activation of product warehouse tasks, if you attempt to print during storage control, then you automatically call up PPF. The decision whether to print is dependent on the condition records that are found in the schedule condition. In the following circumstances, PPF triggers the executing method and therefore printing:

SAP Extended Warehouse Management (SAP EWM)

510

427

SAP Online Help

20.07.2007

There is a condition record in which the PPF action definition matches the current PPF action definition. The logical condition is entered in the condition record, and is fulfilled.

During printing or repeat printing, you can also execute PPF action definitions for which there are no defined condition records. In this case, the system cannot determine the necessary data such as printer, form name, and spool parameters, and you must enter this data manually. During printing, PPF writes a determination log and a processing log. Since these logs can become extremely large, you can switch them on and off. To do this, use parameter /SCWM/WO_PRT_PROT.

Activities
EWM automatically triggers the print run from processing, or you trigger it manually. EWM calls the PPF and transmits the application data. The PPF determines the PPF action definitions you have defined in Customizing for the PPF application /SCWM/WME and the PPF action profile /SCWM/WO. The PPF calls the schedule condition that corresponds to the PPF action definition. In the schedule condition, the PPF calls determination in the condition technique. Determination of the condition technique returns the relevant condition record. This determines the printer, spool parameters, and the SAP Smart Forms form. PPF reads the current application data. PPF determines the function module that corresponds to the SAP Smart Form form, and calls up the application data. PPF saves the action that was executed and the logs that were written.

SAP Extended Warehouse Management (SAP EWM)

510

428

SAP Online Help

20.07.2007

Manual Assembly of Warehouse Orders


Use
You use this function in the goods receipt process to delete warehouse tasks of different handling units (HUs) from your warehouse orders, and to group them together in a new warehouse order. This allows you to put away the HUs collectively, and Extended Warehouse Management (EWM) is able to determine the optimal putaway path.

Prerequisites
You have made sure that putaway warehouse tasks exist and are active for the entire contents of the HU. If EWM is to generate a single warehouse order for all warehouse tasks that belong to the HUs you have specified, you have made sure that the warehouse activity area and queue for these warehouse tasks are identical (see Warehouse Order Creation [Seite 419]). If you want to print warehouse orders using a PPF action, you have scheduled a corresponding PPF action.

Features
This function is optimized so that you can operate it using a hand-held scanner that is installed on a keyboard filter. You can specify multiple HUs in the entry field, one after each other. EWM shows you the specified HU in the lower part of the screen, and assigns the HU to a position field, ascending. For example, you scan three HUs. EWM assigns the HU scanned first to position one, the next HU to position two, and the HU scanned last to position three. Make sure that the position of the HU in EWM matches the physical position of the HU in the resource. When you perform putaway, EWM shows you the position in the Radio Frequency dialog (RF dialog). A traffic light shows the status of the warehouse task. Green means that you have specified a valid HU, and that warehouse tasks exist for all products in the HU. EWM has updated screen content for the total weight and total volume, and increased the number of HUs in the new warehouse order that is to be created by one. Red means that you have specified an HU, but that no warehouse task exists for at least one of the products in the HU. EWM does not update the screen content for the total weight and total volume, and does not include the HU in the new warehouse order that is to be created.

Activities
On the SAP Easy Access screen, choose Extended Warehouse Management Execution Manually Assemble Warehouse Orders. After you have specified all the HUs, choose Save. In doing this, EWM deletes all warehouse tasks of the HUs from your warehouse orders. EWM attempts to generate a warehouse order for all warehouse tasks, and saves the warehouse tasks in this order. EWM displays a success message if appropriate. If EWM generates one warehouse order only, you can take the warehouse order number directly from the message. If EWM generates multiple warehouse orders, the message only contains the number of warehouse orders. In this case, you can get the warehouse order number from the log. EWM updates the screen content.

SAP Extended Warehouse Management (SAP EWM)

510

429

SAP Online Help

20.07.2007

You can print the warehouse order in one of the following ways: Using a Post Processing Framework action Manually Choose Work Center Print Last Warehouse Order. Under Create Action, choose the PPF action you require for printing warehouse orders (see Printing Warehouse Orders and Warehouse Tasks [Seite 426]).

SAP Extended Warehouse Management (SAP EWM)

510

430

SAP Online Help

20.07.2007

Interface Between EWM and Non-SAP Systems


Use
Extended Warehouse Management (EWM) has an interface (EWM-WCU interface) that you can use to connect automated warehouse systems such as warehouse control units (WCU) to EWM.

Integration
The interface allows communication between the connected systems on the basis of the transactional Remote Function Call [Extern] (tRFC). In contrast to synchronous Remote Function Call (RFC), the system saves the data in an intermediate storage area, before sending it to the connected system. This leads to the decoupling of application and communication.

Features
Interface Between EWM and Non-SAP Systems (WMS-WCU Interface)
You use the EWM-WCU interface to connect automated warehouse systems, such as warehouse control units (WCU) to Extended Warehouse Management (EWM). For more information, see Scenarios for Connecting Non-SAP Systems [Seite 432] and Description of the IDocs [Seite 459].

SAP Extended Warehouse Management (SAP EWM)

510

431

SAP Online Help

20.07.2007

Scenarios for Connecting Non-SAP Systems


Use
You can use the interface between Extended Warehouse Management (EWM) and non-SAP systems (EWM-WCU interface) to connect different non-SAP systems to EWM. The following scenarios give you an overview of typical ways in which this interface can be used. Non-SAP systems include warehouse systems dependent on EWM, such as warehouse control units (WCU).

Features
The EWM-WCU interface supports the following communcation transactions between the systems: Transfer warehouse tasks from EWM to non-SAP system Transfer release of multiple processing from EWM to non-SAP system Transfer cancellation requests from EWM to non-SAP system Create transfer orders in EWM for warehouse tasks reported by non-SAP system Confirm transfer orders in EWM for warehouse tasks reported as complete by nonSAP system Move handling units [Seite 490] Blocking storage units or aisles Cancel transfer orders in EWM for warehouse tasks not reported as complete by nonSAP system

EWM takes on all tasks related to warehouse management. However, warehouse control and execution of driving commands are not part of EWM's tasks. For this reason, the non-SAP systems always represent standalone systems for the SAP system, which can take on control of the product flow, as well as other tasks such as optimizing the stock movenents or additional control mechanisms. The scenarios focus on the task distribution between EWM and the relevant connected nonSAP system. The flexibility of the EWM-WCU interface enables you to make customerspecific adjustments and enhancements. For more information, see Modification Concepts: IDoc Receipt [Seite 484] and Modification Concepts: IDoc Issue [Seite 487].

Activities
You determine the task distribution, according to your own requirements, between EWM and the non-SAP system.

SAP Extended Warehouse Management (SAP EWM)

510

432

SAP Online Help

20.07.2007

Connecting a Semi-Automated Warehouse


Purpose
In a semiautomatic warehouse, you manage the warehouse using Extended Warehouse Management (EWM), whilst a linked non-SAP system performs the actual stock movements. EWM performs all tasks relevant to warehouse management, including: Managing product stocks and storage bins Triggering warehouse movements (stock removal, putaway, stock transfers and posting changes) Determining the storage bins for warehouse movements based on fixed putaway and stock removal strategies Carrying out the inventory

To optimize the processes in the warehouse you use EWM and a non-SAP system to: Connect forklift systems Control automatic conveyors or conveyor equipment Allow picking without any documents, using RF devices Control the product flow

The following describes two variations of the scenario: EWM does not transfer any data using the EWM-WCU interface to the non-SAP system. You can only use this interface to tell EWM that stock movements have been performed. The EWM-WCU interface is used to transfer pending stock movements to the non-SAP system, as well as to report the execution of stock movements to EWM.

Prerequisites
You have configured the interface between EWM and the non-SAP system in Customizing for Extended Warehouse Management under Interfaces Non-SAP Systems Connect Subsystem.

SAP Extended Warehouse Management (SAP EWM)

510

433

SAP Online Help

20.07.2007

Process
Reporting Using EWM-WCU Interface: Putaway
EWM
Triggers stock movement

Non-SAP System

Creates WTs for putaway

Prints WT for putaway

Scan pallet slip in non-SAP system Performs stock movement

Reports goods movement


WCU Interface /SCWM/WMTOCO

Confirms reported WTs

...

1. EWM creates warehouse tasks (WTs) for the goods movements. 2. You print the warehouse tasks to use as a pallet receipt/issue slip. The destination storage bin for putaway is printed on the pallet slip in the form of a barcode. 3. You transport the pallet to the automatic conveyor. 4. You scan in the barcode with the destination storage bin at the automatic conveyor. 5. The automatic conveyor carries the pallet to the storage bin and puts it away. 6. If the Customizing settings are such that the WT transferred from EWM must be reported to EWM, then the non-SAP system reports the stock movement for the WT using the message type /SCWM/WMTOCO to EWM. The non-SAP system constructs the warehouse task data in the form of an IDoc for the forklift guidance system, and sends this IDoc to EWM. 7. EWM confirms the warehouse task using the data reported using message type /SCWM/WMTOCO.

SAP Extended Warehouse Management (SAP EWM)

510

434

SAP Online Help

20.07.2007

Reporting Using EWM-WCU Interface: Stock Removal


EWM
Triggers stock movements

Non-SAP System

Creates WTs for putaway

Prints WT for stock removal

Scan in non-SAP system

Performs stock movement

Reports goods movement


WCU Interface /SCWM/WMOCO

Confirms reported WTs

...

1. EWM creates warehouse tasks (WTs) for the stock removal. 2. You print the warehouse tasks to use as a stock removal list. The source storage bin for stock removal is printed on the stock removal list in the form of a barcode. 3. You scan the barcode with the source storage bins into the automatic conveyor. 4. The automatic conveyor removes the pallet from storage. If picking takes place directly at the storage bin, the automatic conveyor goes directly to the relevant source storage bin when you scan in the stock removal slip. 5. If the Customizing settings are such that the WT transferred from EWM must be reported to EWM, then the non-SAP system reports the stock movement for the WT using the message type /SCWM/WMTOCO to EWM. The non-SAP system constructs the warehouse task data in the form of an IDoc for the forklift guidance system, and sends this IDoc to EWM. 6. EWM confirms the warehouse task using the data reported using message type /SCWM/WMTOCO.

SAP Extended Warehouse Management (SAP EWM)

510

435

SAP Online Help

20.07.2007

Transferring warehouse tasks for warehouse movements to the external system


EWM
Triggers stock movements

Non-SAP System

Creates WTs for the stock movements Transfers WTs to non-SAP system WCU Interface /SCWM/WMTORD Optimizes stock movements

Performs stock movements

Checks any stock movements

Reports goods movements WCU Interface /SCWM/WMTOCO Confirms reported WTs

...

1. EWM creates warehouse tasks (WTs) for the goods movements. 2. EWM transfers the warehouse tasks using the message type /SCWM/WMTORD to the non-SAP system. 3. The external system executes the goods movements in the warehouse on the basis of the transferred data. The forklift control system monitors all of the movements. 4. If the Customizing settings are such that the warehouse task transmitted from EWM must be reported to EWM, then the non-SAP system reports the stock movement for the warehouse task using the message type /SCWM/WMTOCO to EWM. The non-SAP system constructs the warehouse task data in the form of an IDoc for the forklift guidance system, and sends this IDoc to EWM. 5. EWM confirms the warehouse task using the data reported using message type /SCWM/WMTOCO.

Triggering warehouse movements manually via the external system


...

1. If you trigger stock movements manually (for example, due to a stock transfer within a warehouse, or because you are collating remainder quantities to make more room), then you enter the stock movement in the forklift guidance system. 2. The forklift guidance system reports the stock movement to EWM using message type /SCWM/WMTOCO. The non-SAP system constructs the warehouse task data in the form of an IDoc for the forklift guidance system, and sends this IDoc to EWM.

SAP Extended Warehouse Management (SAP EWM)

510

436

SAP Online Help

20.07.2007

3. EWM creates a warehouse task using the data reported using message type /SCWM/WMTOCO, and updates the stock data in the warehouse management system.

SAP Extended Warehouse Management (SAP EWM)

510

437

SAP Online Help

20.07.2007

Connecting a Fully Automated Warehouse


Purpose
If you want to use Extended Warehouse Management (EWM) in a fully automatic warehouse, consider the warehouse structure and the automatic warehouse functions when deciding how to distribute the warehouse management tasks suitably between EWM and the non-SAP system. In fully automatic warehouses too, EWM takes on the most important tasks of warehouse management: Managing the product stocks Managing storage bins Triggering warehouse movements (stock removal, putaway, stock transfers and posting changes) Carrying out the inventory Determining the storage bins for warehouse movements based on fixed putaway and stock removal strategies

The external system takes over the entire warehouse controlling: Controlling the conveyor equipment Controlling the product flow Optimizing resources

If you want to use EWM with a fully automatic non-SAP system, you should also take account of the scenario Connecting a Fully Automatic Warehouse as a Black Box [Seite 442].

Prerequisites
You have configured the interface between EWM and the non-SAP system in Customizing for Extended Warehouse Management under Interfaces Non-SAP Systems Connect Subsystem. You have specified how warehouse management tasks will be distributed between EWM and the non-SAP system. Here, the level of automation in the warehouse plays an important role: In simple automatic warehouses, EWM takes on all warehouse management tasks. The non-SAP system only takes on warehouse control, where the warehouse control can be used to optimize the stock movements triggered by EWM. For more information, see Connecting a Semiautomatic Warehouse [Seite 433]. For warehouses with more complex warehouse automation, you should take account of the warehouse technology at warehouse task creation. The external system then takes on some of the warehouse management tasks. For this reason, you move products in this kind of storage type using identification points (ID points) and pick points.

SAP Extended Warehouse Management (SAP EWM)

510

438

SAP Online Help

20.07.2007

Process
Putaway via ID points
EWM
Triggers stock movements Determines destination storage type Creates WT from GR zone to ID point Prints pallet slip with bar code Transfers WT to non-SAP system

Non-SAP System

WCU Interface /SCWM/WMTORD

Scan pallet slip in non-SAP system Determines pallet type Assigns destination storage type Performs stock movement Reports goods movement

WCU Interface

Creates WT for goods movement

/SCWM/WMSUMO

...

1. You receive an inbound delivery in the goods receipt interim storage area. You post the goods receipt for the inbound delivery, and enter the pallet (handling unit) in EWM. 2. EWM determines the destination storage type for the delivered handling unit [Seite 490] (HU). 3. If putaway is performed using an ID point, then EWM creates a warehouse task (WT) from the goods receipt interface to the ID point. 4. EWM transmits the WT with the required data (including the pallet number) for putaway using the message type [Extern] /SCWM/WMTORD to the non-SAP system. 5. You print the WTs to use as a pallet receipt/issue slip. The destination storage bin for putaway is printed on the pallet slip in the form of a barcode. 6. You transport the HU to the ID point. 7. The non-SAP system identifies the HU at the ID point using the bar code on the pallet slip. 8. To optimize capacity utilization of the conveyor vehicles during putaway, the non-SAP system assigns the destination storage bin for the HU. 9. The non-SAP system moves the HU to the destination storage bin and puts the HU away. 10. The non-SAP system reports execution of the stock movement for the handling unit to EWM, using message type /SCWM/WMSUMO.

SAP Extended Warehouse Management (SAP EWM)

510

439

SAP Online Help

20.07.2007

The non-SAP system constructs the warehouse task data in the form of an IDoc for the non-SAP system, and sends this IDoc to EWM. 11. EWM creates the warehouse task for putaway using the data reported using message type /SCWM/WMSUMO, to post the stock movement triggered by the non-SAP system.

Stock removal via a pick point


EWM
Triggers stock movements Determines type and scope of stock removal Creates WT from warehouse to GI area Transfers WT to non-SAP system

Non-SAP System

WCU Interface /SCWM/WMTORD

Determines optimum stock removal sequence Removes handling units to pick point Visualizes the items to pick Reports picking to EWM

Sends group release

WCU Interface /SCWM/WMRREF

WCU Interface /SCWM/WMTOCO

Confirms reported WTs

Determines return transfer storage bin for HU with remaining quantity Return transfers HU

Creates WTs for reported return transfer

WCU Interface /SCWM/WMSUMO

Reports return transfer to EWM

...

1. You trigger a stock removal or picking in EWM by, for example, collating the picking of several outbound deliveries into one collective action. 2. EWM creates warehouse tasks (WTs) for the outbound deliveries. 3. EWM transfers the WTs using the message type /SCWM/WMTORD to the non-SAP system. If you want to execute picking on the basis of outbound deliveries, the system treats each warehouse task that is transferred as an independent pick order. If you want to control picking based on other criteria (for example, based on a route), you must ensure that the non-SAP system only picks the transmitted warehouse tasks after EWM has transmitted all the relevant WTs to the non-SAP system.

The non-SAP system can only collate the WTs into a wave after EWM has transmitted the wave release using message type /SCWM/WMRREF. 4. The external system processes the pick order, which can consist of one or more transferred WTs. 5. The non-SAP system optimizes the individual stock movements from the pick order, by specifying the sequence in which the required handling units should be removed from storage.

SAP Extended Warehouse Management (SAP EWM)

510

440

SAP Online Help

20.07.2007

If there is more than one ID point in the system, then the non-SAP system also specifies the assignment of the individual picking transactions and HUs to the available pick points. Only the external system can ensure optimal pick point assignment, since the utilization of the warehousing equipment is at the fore. 6. You execute picking at the pick point. The external system displays the items to be picked on the screen at the pick point. 7. You confirm the pick and enter any differences that occured. 8. The non-SAP system reports execution of picking for the handling units to EWM, using message type /SCWM/WMTOCO. The non-SAP system constructs the warehouse task data in the form of an IDoc for the forklift guidance system, and sends this IDoc to EWM. 9. EWM confirms the warehouse task using the data reported using message type /SCWM/WMTOCO. Return Transfer for Handling Units with Remaining Quantity
...

1. After picking, you take the HUs with remaining quantities to the ID point for return transfer into the warehouse. 2. The external system identifies the HU at the ID point, by way of a contour control. 3. To optimize capacity utilization of the conveyor vehicles during putaway, the non-SAP system assigns the destination storage bin for the HU. 4. The non-SAP system moves the HU to the destination storage bin and puts the HU away. 5. The non-SAP system reports execution of the stock movement for the HU to EWM, using message type /SCWM/WMSUMO. The non-SAP system constructs the warehouse task data in the form of an IDoc for the non-SAP system, and sends this IDoc to EWM. 6. EWM creates the warehouse task for putaway using the data reported using message type /SCWM/WMSUMO, to post the stock movement triggered by the non-SAP system.

Blocking Storage Bins


In automatic warehouses, conveyor vehicles often cannot access certain storage bins.

Certain routes for the vehicles are no longer valid, or some bins cannot be reached by the warehouse technology. Since you are performing warehouse management using EWM, you must block these storage bins as quickly as possible in EWM, so that EWM cannot schedule any more stock movements for these storage bins. The non-SAP system transmits the storage bins to block using the message type /SCWM/WMBBIN to EWM. To tell EWM to unblock blocked storage bins, the non-SAP system transmits the storage bins or aisles affected to EWM using message type /SCWM/WMBBIN.

SAP Extended Warehouse Management (SAP EWM)

510

441

SAP Online Help

20.07.2007

Connecting a Fully Automated Warehouse as a Black Box


Purpose
In your warehouse complex (Warehouse Number [Seite 23]) that you manage using Extended Warehouse Management (EWM), you have set up several different storage types [Seite 25] . For one or more of these storage types, an external system executes all of the warehouse functions and thus takes over the entire warehouse management and warehouse control for this storage type. The automated storage type is connected as a black box to EWM. In this storage type, EWM hands over the entire warehouse management and warehouse control to the non-SAP system. It does this because the storage type is highly automated and so accurate and timely information about the current status of the warehouse technology is required for the stock movements.

If you want to connect this kind of storage type to your warehouse, we recommend that you implement a system that combines warehouse controlling and warehouse management. Since the automated storage type is only a part of your warehouse complex, you can manage the entire warehouse complex (the warehouse number) using EWM. EWM distributes the individual putaway and stock removal transactions to the various sub-storage-types. In storage types not managed by the non-SAP system, EWM takes on all the standard functions. In storage types managed by the non-SAP system, EWM takes on the following functions: Management of summary stocks for each product Triggering and creating warehouse movements

On the other hand, the external system takes over the entire warehouse management and warehouse control within the storage type: Determining the storage bins for the individual warehouse movements Creating warehouse movements within the storage type Carrying out the inventory Controlling the conveyor equipment Controlling the product flow Optimizing resources

When making your decision concerning the type of interface connection, you should also take account of the scenario for Connecting a Fully-Automated Warehouse [Seite 438].

Prerequisites
You have defined the automated section of your warehouse as a separate storage type in EWM.

SAP Extended Warehouse Management (SAP EWM)

510

442

SAP Online Help

20.07.2007

You can define a fixed storage bin [Extern] for each product in this storage type, to manage the stocks of product in this storage type and to support physical inventory operations. Alternatively, you define several storage bins in the warehouse type, which do not correspond to the physical storage bins. You allow addition to existing stock for this storage type, so that the system always places a product into this storage type. The system cumulates the stocks of a product in a storage bin. This means that a new product always occupies a new storage bin.

The storage bins that you created in EWM for individual products have no meaning for the non-SAP system.

Process
EWM
Communicates with other SAP application components Triggers goods movement Creates WT (storage bin is not relevant) Transfers WT to non-SAP system

Non-SAP System

WCU Interface /SCWM/WMTORD

Determines storage bins for putaway and stock rem. Optimizes material flow Performs goods movement Reports goods movement to EWM Performs physical inventory Reports differences to EWM Triggers and performs whse-int. movements

WCU Interface /SCWM/WMTOCO

Confirms reported WTs Creates WTs for reported differences


WCU Interface /SCWM/WMTOCO

EWM takes on communication with other SAP application components for the entire warehouse number.

Putaway
...

1. You post the goods receipt of the goods in Inventory Management. 2. EWM creates warehouse tasks for putaway and specifies in which storage type the goods are put away. 3. If you have selected the storage type managed by the non-SAP system for putaway, EWM transmits the relevant WT items using the message type [Extern] /SCWM/WMTORD to the non-SAP system.

SAP Extended Warehouse Management (SAP EWM)

510

443

SAP Online Help

20.07.2007

4. The non-SAP system identifies the goods to put away using either the WT number and WT items, or using the transmitted HU number. 5. If EWM reports execution goods movements, then the non-SAP system reports the putaway to EWM using message type /SCWM/WMTOCO.

Stock Removal
...

1. EWM creates a warehouse task (WT) for the stock removal. 2. EWM sends all stock removal WTs relevant for the storage type managed by the nonSAP system to the non-SAP system, using message type /SCWM/WMTORD. 3. The non-SAP system decides the storage bin from which the required products should be removed. 4. The non-SAP system transfers the transfer orders using the message type /SCWM/WMTORD to EWM. 5. EWM confirms the individual items in the warehouse task, using the reported data and actual quantities from the non-SAP system.

Handling Differences
If differences occur in the storage type managed by the non-SAP system during physical inventory or during productive operations, the non-SAP system reports these differences to EWM using the message type /SCWM/WMTOCO. EWM uses the reported differences to create a warehouse task, to post the reported differences to a difference interface.

The non-SAP system must not send product movements within the storage type managed by the non-SAP system, because EWM only manages the summary stocks for this storage type.

SAP Extended Warehouse Management (SAP EWM)

510

444

SAP Online Help

20.07.2007

Data Flow: EWM Transmits Data


Purpose
The data flow via the interface between the non-SAP system and Extended Warehouse Management (EWM-WCU interface) is explained using an example communication process flow for transmitting warehouse task data from EWM to the non-SAP system. For more information about the business background, see Scenarios for Connecting Non-SAP Systems [Seite 432].

Prerequisites
You have made the required TCP/IP settings [Seite 448]. For more information, see BC SAP Communication: Configuration [Extern]. In Customizing, you have defined the ALE interface. In Customizing, you have specified the circumstances in which a warehouse task (WT) is relevant for transmission to the non-SAP system. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management under Interfaces Non-SAP Systems Connect Subsystem. For each warehouse number, you can specify that WT items for the following criteria are relevant for transmission to the non-SAP system: For a storage type For a warehouse process type or For combination of storage type and warehouse process type

You define the external system, which receives the WT item.

Process
...

1. When you create a warehouse task (WT) in EWM, the Customizing settings define that the WT or WT item is relevant for transmission to the non-SAP system. 2. During creation of the WT, the system prepares the data to be transmitted, in the form of an IDoc.

For more information about IDocs and their construction, see Description of the IDocs [Seite 459]. 3. The system saves the created IDoc to the database. 4. Asynchronously to creation of the IDoc, the system uses ALE to trigger transmission of this IDoc to the non-SAP system. The system can transfer individual IDocs or collect several IDocs and then transfer them to the external system later. The transmission is based on Remote Function Call. 5. The non-SAP system must be ready to receive the transmitted data with a relevant program. For more information, see Basis Basis Services/Communication Interface Remote Communications The RFC API Programming with the RFC API [Extern]. 6. The non-SAP system saves the received IDoc data, and sends a receipt confirmation to the SAP system.

SAP Extended Warehouse Management (SAP EWM)

510

445

SAP Online Help

20.07.2007

We recommend that you save the transmitted data in the non-SAP system first, to ensure that transmission of the IDoc and processing of the transmitted data occur separately. 7. Status management for the data received should prevent the external system from processing the data twice. The external system should be able to recognize IDocs that have been transferred by the SAP system before. This is made possible by the unique transaction identification number (transaction ID), which the SAP system assigns for each communication process. For more information, see Basis Basis Services/Communication Interface Remote Communications The RFC API Transactional RFC Client Programs.

The external system can also recognize double transfers from the IDoc number external system can also use the IDoc number to identify duplicate transfers. Note that an IDoc number is only unique within a single client in an SAP system. If several clients of an SAP system or several SAP systems are involved in the communication with the external system, the IDoc number is no longer unique. In this case the external system cannot recognize IDocs that have been transferred twice from this number.

Error Processing
If you receive an IDoc from EWM to a non-SAP system, the following problems can occur: Troubleshooting Symptom Update termination in the SAP system during the application What You Should Know An update termination during creation of a warehouse task does not affect communication with the external system, because the system only creates an IDoc once the source SAP system document exists. The WT and the IDoc are creates in the same LUW, therefore they are updated synchronously. Error in the ALE interface: Transferred data is syntactically incorrect ALE adopts the IDoc and saves it, but cannot transfer the IDoc to the external system. For more information, see IDoc Error Processing [Seite 477]. For more information, see IDoc Error Processing [Seite 477].

Error in the ALE interface: The outbound partner profile for the receiving system The IDoc message type

are not defined There is no connection between the SAP system and the external system The SAP system tries to set up the connection to the external system by running a report in the background at a later time. As soon as the connection between the two systems exists again, the SAP system automatically transfers all IDocs, which have not yet been sent. You can also start this

SAP Extended Warehouse Management (SAP EWM)

510

446

SAP Online Help

20.07.2007 report manually. For more information, see Processing Technical IDoc Errors [Seite 478].

SAP Extended Warehouse Management (SAP EWM)

510

447

SAP Online Help

20.07.2007

Managing TCP/IP Settings


As a prerequisite for communication, you make the following TCP/IP settings: In order for the SAP system to find the target system, you must fulfill the TCP/IP prerequisites, in particular the IP addresses must be known in the relevant hosts file. You have entered the name of the gateway and the dispatcher in the services file, for example, sapgw00 and sapdp00. In the standard system, IDocs are sent from the update transaction. Ensure that the TCP/IP link was also created for the update machine. You work in registration mode. This means that the connection between the non-SAP system program and the gateway remains open. For more information, see Registering Server Programs with the SAP Gateway [Extern]. If you do not work in registration mode, then the SAP gateway must have the authorization to start the external program (RFC server) using Remote Shell. For details on the TCP/IP settings, see the documentation SAP Communication: Configuration [Extern].

SAP Extended Warehouse Management (SAP EWM)

510

448

SAP Online Help

20.07.2007

Managing Transaction Identifiers (TID)


Purpose
To ensure the security of the data to transfer, you must work with a unique identifier for a communication transaction. This ID allows the receiving system to recognize whether this data has already been received and processed.

Process
The following diagram shows th