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

2

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

3

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

5

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

6

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

7

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

8

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

9

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

or if there is a 1:1 relationship between storage type and activity area. or can concatenate bins from several storage types. you define the warehouse structures in EWM in Customizing.. where you can store products.07.. Storage Bins → Define Storage Bin Types 5... Activity Areas → Assign Storage Bins to Activity Areas . 1.. We recommend that you use the following sequence when configuring the warehouse structure in the system. ● ● 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. SAP Extended Warehouse Management (SAP EWM) 510 22 . In the Implementation Guide (IMG) for EWM. . Activity Areas → Define Activity Area 6. The coordinates of the storage bin tell you the exact position in the warehouse.. To map the structure of your physical warehouse in the system. Define Storage Section 4. you can have the system generate the assignment. choose Extended Warehouse Management → Master Data → . It can refer to a storage bin.SAP Online Help ● 20. Define Storage Type 3. You can either assign storage bins manually to the activity areas. Define Warehouse Numbers 2.2007 Storage bin Each storage type and storage section consists of a selection of storage compartments that are called storage bins in EWM.

07. 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 . The system uses the time zone for the warehouse number when displaying all date and time fields. You should not change these settings at a later time. You can create a supply chain unit in the SAP menu under Extended Warehouse Management → Master Data → Maintain Supply Chain Unit. Use The organizational and physical attributes of a warehouse complex are collected together under the warehouse number. see the Implementation Guide (IMG) for Extended Warehouse Management under Master Data → Define Warehouse Number Control. We recommend using one warehouse number for each group of storage areas or buildings (warehousing complex) in the same geographical area.2007 Warehouse Number Definition In Extended Warehouse Management (EWM). for example because you have already created a warehouse number product. that you must make this assignment in the production system. You can also define determination procedures for palletization data and packaging specifications [Seite 494] here. For more information.SAP Online Help 20. and time unit are defined at warehouse number level. it is appropriate to assign a separate warehouse number to each warehouse complex. the weight unit. For this reason. such as country. Doing so can result in follow-on errors. however. Note. you should no longer change the assignment of the supply chain unit to the warehouse number. see the IMG for Extended Warehouse Management under Master Data → Assign Warehouse Numbers. region. 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. which together form the complete warehouse complex. and time zone. you combine an entire physical warehouse under one warehouse number. volume unit. For more information about defining a warehouse number. For example. If your warehousing facilities are located in different cities or are physically separated by a longer distance. 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. As soon as you actively use a warehouse number. You can use the warehouse number to manage several storage facilities.

SAP Extended Warehouse Management (SAP EWM) 510 24 .07.SAP Online Help ● 20. EWM groups these facilities together under a warehouse number.2007 Storage space outdoors for special substances Each of the storage facilities listed above is called a storage type [Seite 25] in EWM.

2007 Storage Type Definition A storage type is a storage space. 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. The standard system for EWM comes configured with several complete storage types that you can use straightaway. or function. which you define for a warehouse number in Extended Warehouse Management (EWM). space required. before you release them in the production system. 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. or storage zone. You manage all storage types under a single warehouse number. These include the control indicators for: ● ● Putaway Stock removal (picking) Some control indicators for storage types are mutually exclusive. You can use the standard storage types as the basis for your individual settings. Defining Control Indicators in the Storage Type At storage type level. In these cases.07.SAP Online Help 20. We recommend that you check and test all new combinations carefully. which is characterized by its warehouse technologies. and certain combinations of indicators cannot be permitted for legal reasons or due to internal guidelines. SAP Extended Warehouse Management (SAP EWM) 510 25 . A storage type consists of one or more storage bins. The storage type is a physical or logical subdivision of a warehouse complex. the system generates an error message. storage facility. or you can create your own storage types to meet the special requirements of your company. organizational form. you must specify the control indicators that control the material flow (putaway and picking) in each storage type.

see the Implementation Guide (IMG) for EWM under Extended Warehouse Management → Master Data → Define Storage Type. if there are no stocks present within a storage type. Example You can define several storage types for each warehouse number.SAP Online Help 20. In the storage type. 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.2007 You can only activate or deactivate the level of the available quantities and handling unit management requirement. there are indicators that you can override in the warehouse process category. 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 .07. We recommend that you only change the capacity check for a storage type if no more stocks are present within the storage type. This means that specific functions. For more information about changing the predefined storage types or creating new storage types. Particular care should be taken if you subsequently change the putaway behavior for putaway. but are not valid for a specific posting.

SAP Online Help 20. 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. You create activity-dependent bin sortings within an activity area. 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. For more information. 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. SAP Extended Warehouse Management (SAP EWM) 510 27 . Structure An activity area consists of one or more assigned storage bins. such as putaway or picking.07. In these activity areas. Extended Warehouse Management (EWM) uses these bin sortings to optimize the execution of warehouse tasks. You can generate activity areas from storage types in Customizing. To be able to work with activity areas. For more information. and assign as many activities to them as you require. choose Extended Warehouse Management → Master Data → Storage Bin → Sort Storage Bins. different warehouse workers execute certain warehouse activities.2007 Activity Area Definition Logical section of the warehouse that groups storage bins based on defined warehouse activities. In this case. see the IMG for EWM under Master Data → Activity Area → Generate Activity Area from Storage Type. the activity area has the same storage bins as the storage type. you have to generate the bin sorting. On the SAP Easy Access screen.

it considers the activity area and copies attributes from this activity area. such as the deconsolidation group. When EWM generates warehouse tasks.SAP Online Help 20.07. SAP Extended Warehouse Management (SAP EWM) 510 28 .2007 Integration EWM generates warehouse orders [Seite 419] for each activity area.

Use You can use the storage section as an organizational aid for putting away goods in the warehouse. 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 . Example High rack storage areas frequently consist of many storage bins that vary in size. a storage section is an organizational subdivision of a storage type. while those in the upper levels are smaller. heavy parts. the bins in the lower level are larger for especially large and heavy parts. and the back storage section for slowmoving items. which joins together storage bins with similar attributes for the purpose of putaway. you must create at least one storage section for each storage type. see the Implementation Guide (IMG) for Extended Warehouse Management under Master Data → Define Storage Sections.2007 Storage Section Definition In Extended Warehouse Management (EWM). The physical location is the main organizational factor. You use the front storage section for fast-moving items. However. When you use storage types and storage sections. for example. fast-moving items.SAP Online Help 20. You can only define control parameters and control values in the storage type. you must define the organizational aims clearly.07. in many such storage areas. The following figure shows a high-rack storage area divided into two storage sections. For information on how to define a storage section for a storage type. For example. bulky parts. The criteria for joining these bins together can be defined in any way. slow-moving items. It is not absolutely mandatory that you subdivide a storage type into two or more storage sections.

you assign the warehouse number in which the storage bin is located.SAP Online Help 20. 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. in connection with the pallet type. and so on.2007 Storage Bin Definition A storage type consists of a selection of storage spaces. The storage bin is the smallest spatial unit in a warehouse. However. which are called storage bins in Extended Warehouse Management (EWM). SAP Extended Warehouse Management (SAP EWM) 510 30 . Since the address of a storage bin is frequently derived from a coordinate system. the storage bin type plays an important role during optimization of the automatic search for a storage bin. for large or small pallets) In some putaway strategies. stack 2. you should ensure that you orient the parts of the structure to the indicators defined for the warehouse for aisle. You can also define the following additional attributes for a storage bin: ● ● ● ● Maximum weight Total capacity Fire-containment section Storage bin type (for example. stack. For example. the storage bin represents the exact position in the warehouse where products are and/or can be stored. Use To each storage bin. Therefore. For example. a storage bin is often referred to as a coordinate. You just also assign a storage type [Seite 25] and storage section [Seite 29] to each storage bin.07. and level 3. 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. For information about defining storage bins. the coordinate 01-02-03 could be a storage bin in aisle 1. level.

07. resource [Seite 752].SAP Online Help 20. Use Quants are used to manage stocks at storage bin level. You can increase the quantity of a quant by adding to the existing stock. the system generates a quant in this storage bin. The system manages different batches of a product as different quants. and transportation units. When you remove the quantity from storage. the system manages the data for the products collected together in the quant. When you put a product away into an empty bin in Extended Warehouse Management (EWM). In the quant record. This data includes: ● ● ● ● ● ● Quant identification Number Batch number Stock category type Stock category Stock usage SAP Extended Warehouse Management (SAP EWM) 510 31 .2007 Quant Definition Stock of a specific product with the same characteristics in one storage bin [Seite 30]. resources. and transportation unit [Seite 613]. the system automatically deletes the quant. Quants can only be created and deleted using movements.

You assign staging areas and staging area/door determination groups to your doors under Master Data → Warehouse Door.2007 Door Definition Location in the warehouse where the goods arrive at or leave the warehouse. The doors are in close proximity to the relevant staging areas [Seite 33]. You can also assign doors to supply chain units [Seite 53] to control authorization checks.SAP Online Help 20. You assign this storage bin to a storage type with the storage type role F. Use To control putaway and stock removal processes in your warehouse. 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.07. Structure You assign each door to a storage bin that you can use to post goods receipts or goods issues. You define doors in Customizing for Extended Warehouse Management (EWM) under Master Data → Warehouse Door → Define Warehouse Door. 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 . 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 door is an organizational unit that you assign to the warehouse number. you can define doors and staging areas within a warehouse number. The system updates the delivery at item level with the values that it finds.

For more information.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. for example. See also: Staging Area and Door Determination [Seite 615] SAP Extended Warehouse Management (SAP EWM) 510 33 . The staging area group corresponds to a storage type (storage type role “D”). 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. you define staging areas and assign the staging areas to the relevant doors. if you want to define a loading sequence. You need multiple storage bins. They are located in close proximity to the doors [Seite 32] assigned to them.SAP Online Help 20. Use Staging areas are used for the interim storage of goods in the warehouse.07. Structure You can group multiple staging areas into staging area groups. 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. while the staging area corresponds to a storage section. You can divide each staging area into one or more storage bins.

2007 SAP Extended Warehouse Management (SAP EWM) 510 34 .SAP Online Help 20.07.

Work center 2 represents the deconsolidation work center. which has an outbound section but no inbound section. see the Implementation Guide (IMG) for EWM under Extended Warehouse Management → Master Data → Work Center.SAP Online Help 20. ‘Pick Point’ (B). You must assign each work center to a warehouse number. for example. ● Quality Inspection and Count This transaction type is for entering count and inspection results.2007 Work Center Definition The work center is a physical unit in the warehouse. which has no inbound section and no outbound section. Deconsolidation This transaction type is for distributing mixed handling units (HUs) into HUs for nonmixed deconsolidation groups. and storage bin. storage type. 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. SAP Extended Warehouse Management (SAP EWM) 510 35 . You can configure more than once work center for each storage type in the system. Work center 3 represents the deconsolidation work center. on how a work center for deconsolidation can be structured: Work center 1 represents the deconsolidation work center.07. For more information about setting up work centers. distribution. in which you can perform warehouse activities such as packing. and for confirming inspection results. Example The following example shows you various options. You can assign an inbound and outbound section to each work section. or ‘Identification and Pick Point’ (C). or weighing. Note that you can only use storage types that have the storage type role ‘Work Center’ (E). ● Packing in the Staging Area This transaction type is for packing together HUs according to the criterion Stop on Route. which has both an inbound section and an outbound section.

This means that you can send individual products or HUs to a work center group. Section Work Center Work Center 0001 0001 0001 Outb. when you confirm the warehouse task. which corresponds to a storage section. 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. In the above example. SAP Extended Warehouse Management (SAP EWM) 510 36 . and thus the work center.SAP Online Help 20.07. The system only determines the final storage bin. this would be a warehouse task to storage section 0001.2007 Work Center WC1 Work Center WC2 Work Center WC3 WC3I Deconsolidation HU Putaway-HU WC3I-01 WC3I-02 WC1 WC2 WC3 Inb.

see Assignment of Warehouse Order to Resource [Seite 755].2007 Resource Definition A resource is an entity representing a user or equipment. Once the resource is logged on to the system. Resource). it can receive work for execution. For more information about logging on to an RF environment. and can be tracked and displayed in the warehouse management monitor [Seite 878].07. You define a resource in the transaction for resource maintenance.SAP Online Help 20. For more information about how resources receive work. see Logon [Seite 790]. choose Extended Warehouse Management → Master Data → Resource Management → /SCWM/RSRC – Maintain Resource. SAP Extended Warehouse Management (SAP EWM) 510 37 . Alternatively you can define a resource by using the warehouse management monitor (method [Seite 882] Maint. Structure A resource belongs to a resource type [Seite 753] and resource group [Seite 754]. Use A resource can log on to a radio frequency (RF) or non-RF environment. To do so on the SAP Easy Access screen. which can execute work in the warehouse.

07. see Position Management [Seite 795]. accessed on the SAP Easy Access screen (Extended Warehouse Management → Master Data → Resource Management → /SCWM/EXECPR .2007 Resource Type Definition A resource type is a grouping of resources with similar technical or physical qualifications. and assign to them qualifications. 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.SAP Online Help 20. see Latest Starting Date (LSD) [Seite 760].Maintain Execution Priorities). in Customizing for Extended Warehouse Management → Cross-Process Settings → Resource Management → Define Resource Types. You define resource types. see Warehouse Order Selection [Seite 757]. 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). ● ● Applicability of position management For more information. You maintain the qualification priority values using the execution priority maintenance transaction. For more information. For more information. SAP Extended Warehouse Management (SAP EWM) 510 38 .

SAP Extended Warehouse Management (SAP EWM) 510 39 . see Warehouse Order Selection [Seite 757]. accessed on the SAP Easy Access screen (Extended Warehouse Management → Master Data → Resource Management → /SCWM/QSEQ . which can influence which WOs are selected for a resource.Maintain Queue Sequence for Resource Group). For more information.2007 Resource Group Definition A resource group is a grouping of resources for queue [Seite 764] assignment purposes.SAP Online Help 20. Use The resource group determines the sequence of allowed queues for its corresponding resources [Seite 752]. or from the warehouse management monitor [Seite 878] (Assign Queue/Unassign Queue methods [Seite 882]). You assign/unassign a resource group to/from a queue using the queue sequence for resource group transaction.07.

Storage type data Here you maintain data on the type of facility in which the product is stored. ● ● ● ● ● ● 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. Slotting For more information. SAP Extended Warehouse Management (SAP EWM) 510 40 .SAP Online Help 20. 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. You can create or change a warehouse product via the SAP menu under Extended Warehouse Management → Master Data → Maintain Warehouse Product. For more information. see the Implementation Guide (IMG) for EWM under Master Data → Product → Settings in the ERP System.07. warehouse-number-independent data pertaining to the storage of the product can be found on the Storage tab page. such as the putaway control indicator. Entry of the warehouse number [Seite 23] and the ‘party entitled to dispose’ is mandatory. Integration Global. see Slotting [Seite 277].2007 Warehouse Product Definition Warehouse-number-dependent view of the product master data. 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. The following warehouse-number-independent data on the storage of a product is adopted in EWM from the ERP system. 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). because the warehouse-number-dependent data pertaining to the warehouse product applies only to this warehouse number and this party. see Storage Type [Seite 25]. This tab page is also displayed in product master maintenance.

2007 SAP Extended Warehouse Management (SAP EWM) 510 41 .07.SAP Online Help 20.

Health and Safety (EHS) → Hazardous Substance Management (EHS-HSM) → Hazardous Substance Master → Hazardous Substance. SAP Extended Warehouse Management (SAP EWM) 510 42 . animals. or the environment when being handled or stored.2007 Hazardous Substance Definition Substance that can pose a danger to humans. The handling and storage of hazardous substances is governed by law.07. see the SAP Help Portal under SAP ERP Central Component → Logistics → Environment. For more information.SAP Online Help 20.

2007 Packaging Specification Definition A packaging specification is master data. Work step ● Header Attributes such as the name of the packaging specification. Pack. SAP Extended Warehouse Management (SAP EWM) 510 43 .07. mat. mat. mat. a packaging specification is a set of instructions for the employee in the warehouse. to put away or transport the product.SAP Online Help 20. More specifically. mat. Processes that determine packaging specifications use only parts or specific attributes from the packaging specification. or how a product should be stacked onto a pallet. ● Structure Header Product Contents OR or Packaging specification Level 1 EG 1 Element 1 Element 2 Level 2 EG 2 Element 1 Pack. Pack. In this way you can. user name of the creation user. for example. The system can determine packaging specifications during various processes (see below). Use ● In printed form. for example. give the employee exact instructions as to where to place the label on a box. Work step Work step Work step Level n EG n Element 1 Pack. and so on. status. a packaging specification mainly describes in which quantities you can pack the product into which packaging materials in which sequence. The packaging specification defines all the necessary packing levels for a product in order. For a product. the work steps that you enter in a packaging specification are intended as information for the employee.

element group EG2 Element group EG2: ● Element E3: packaging material ‘Pallet’. ● Packaging material A product that is defined with a packaging material type in the product master. ● Level You can map various packing levels in a packaging specification. work step ‘Place boxes layer by layer onto pallet’ Integration The following figure shows which processes use the packaging specification. Example for a Packaging Specification and Its Structure: Header: Name: PS1. However. Each level contains a target quantity.SAP Online Help ● 20. some packaging specifications contain more than one product. work step ‘Place label on upper left’ Level 2: Target quantity 50. which you can use in one or more packaging specifications. 1 piece Level 1: Target quantity one. ● Element group For each level there is exactly one element group.07.2007 Contents A packaging specification contains a product. which defines how many times you can pack the previous level into this level. you can reuse element groups in several packaging specifications. However. and using which components: SAP Extended Warehouse Management (SAP EWM) 510 44 . Step A text with an identification. or refer to other packaging specifications. Status: New Contents: product A. work step ‘Place 1 piece upright in each box’ Element E2: additional packaging material ‘Label’. element group EG1 Element group EG1: ● ● Element E1: packaging material ‘Small box’. ● ● Elements Elements consist of a packaging material and/or a work step. shift quantity 10.

Example Palletization data in EWM In your warehouse. For this level. the system splits the quantity in the inbound delivery across multiple warehouse tasks. technique In both the Inventory Collaboration Hub (ICH) and in Extended Warehouse Management (EWM).2007 Processes for the Packaging Specification Inb. delivery/ASN Putaway-WT Stock-removal-WT Slotting Palletization Whse-int.07. copy. For example. due to this packaging specification. then the system creates two warehouse tasks for 50 pieces. SAP Extended Warehouse Management (SAP EWM) 510 45 . In the process ‘Putaway’ for the inbound delivery. if a quantity of 100 pieces is delivered. 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. processes Pick-HU proposal ATP sourcing MM deployment Automatic packing Warehouse order Rounding rules ICH EWM APO Packaging Specification iPPE Cond. Create a packaging specification with a level that contains the main packaging material Pallet and the contents Product A.SAP Online Help 20. you put away product A onto pallets for 50 pieces. enter the target quantity 50. Functions of the Packaging Specification The following functions are possible for packaging specifications: ● ● ● Create. and activate (see also: Creation of Packaging Specifications [Seite 497]) Determine (see also: Packaging Specification Determination [Seite 499]) in mehrere Systeme verteilen.

The system does not check if the mode of transport semantically matches the means of transport used for the leg of this location. in other words.SAP Online Help 20. 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. You assign exactly one means of transport to each leg. The system uses routes to determine trips in route determination [Seite 638]. You define legs as a sequence of stops.07.2007 Route Definition Sequence of legs that are connected by transshipment locations [Extern]. it does not permit you to define a mode of transport for such stops. The system then takes into account this mode of transport for outbound shipments in the case of exports. in most cases. in most cases. it cannot be part of multiple routes. The value that represents this mode of transport is dependent on the country in which the location lies. By specifying whether the stop-offs are optional or mandatory. the system cannot define a unique country for zones. Use The route represents a framework or corridor that comprises a multitude of trips. The following figure shows a route with three legs that are connected by the transshipment locations P and M. SAP Extended Warehouse Management (SAP EWM) 510 46 . adjacent legs of a route have different means of transport. a location or zone [Seite 646]. in other words. Structure Leg A leg is assigned uniquely to a route. possible concrete itineraries. you define which locations the carrier is to serve in which order. Nonetheless. 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. in other words. In most cases. the legs of a route represent its unimodal parts. However. Since. it might also be necessary to change legs due to various properties of the legs. Each stop is a supply chain unit (SCU) [Seite 53]. you can assign a mode of transport for foreign trade to each location. Stop At stop level. The stops that connect two consecutive legs must be locations.

SAP Online Help 20. You can specify whether dangerous goods can be transported for each such combination of leg. In static route determination. means of transport. Request types at stop level have a higher priority than those 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. 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. and for which you have defined the lowest costs for transportation along this leg in the carrier profile. ● ● Permitted transportation groups that the system compares with the transportation groups of the products in a single request. for example). The request types at stop level must be part of the request types that you specify at header level. ● Dimension limits (length. 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. and carrier. You can specify permitted request types at the header level of the route and for each stop within the leg (customer. 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. If the departures for a specific request type do not correspond with the departure calendar for the leg. Part of the location sequence of the trip that runs from the first location within this country 3. the system defines the carrier for a trip as the carrier for the first leg who can transport dangerous goods. the location that lies closest to the border. if required. the request types at header level are valid for those stops for which you have not defined separate request types. in other words. and height) SAP Extended Warehouse Management (SAP EWM) 510 47 . Accordingly. Permitted request types that the system compares with the request type of a single request. Permitted shipping conditions that the system compares with the shipping conditions of a single request. width. you can also define a specific departure calendar for this request type. Country of first location 2. 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.07. 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.2007 In static route determination. Departure Calendar Assignment You can define a departure calendar for the leg. the system determines the mode of transport for foreign trade for outbound shipments (trips) in the following sequence: 1. These limits overwrite the relevant limits that you specify for the route at header level. These limits overwrite the relevant limits that you specify for the route at header level.

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. SAP Extended Warehouse Management (SAP EWM) 510 48 .SAP Online Help 20. You can also define various lead times for the different request types.07. These influence the start time of a trip in scheduling.

By specifying a different CD route as the inbound or outbound route. for the route pairs that consist of inbound and outbound routes.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). you define the required attributes. You define CD routes in the master data for Extended Warehouse Management (EWM) under Master Data → Shipping and Receiving → Route Determination → Maintain Route. You specify one or more outbound routes on the CD Routes tab page.SAP Online Help 20. The system takes into account CD routes when you use route determination [Seite 638] as part of cross-docking [Seite 544]. Use You use cross-docking routes (CD routes) to link routes to route networks. Example The following figure shows a route network consisting of two CD routes: SAP Extended Warehouse Management (SAP EWM) 510 49 . 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. Structure To define a CD route. 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. Here an outbound CD route from CD location 1 must have at least one inbound route with the start location CD location 1. Here the start location of all these routes must be identical with the CD location. for example. whether transshipment is not required (goods remain on the same vehicle). you can create a route network with multiple CD locations. An inbound CD route to CD location 2 must have at least one outbound route with the destination location CD location 2.07. you must make the following settings: ● ● ● You specify a CD location for the route at header level. ● On the CD Attributes tab page.

2007 Cross-Docking Route 2 CrossDocking Location 2 e6 Rout Rou (Inb te 1 oun d) 3 ute Ro Rou te 5 ute Ro 2 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 .07.SAP Online Help 20.

and are used as the planned size.SAP Online Help 20. The dimensions of the vehicle come from the means of transport that you assign to the vehicle.07. you can create the current invoice via an invoice request to SAP CRM Billing (see Invoice Creation Before Goods Issue [Seite 368]).2007 Vehicle Definition A specialization of a particular means of transport. data that you define for the vehicle is also valid for the assigned transportation units. In this case. Before goods issue posting. This means that it consists of two transportation units: The cargo area and the trailer. 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]). SAP Extended Warehouse Management (SAP EWM) 510 51 . Use You define vehicles in the master data for transportation. ● Example The truck with the license plate number HSK-116 has a trailer. Integration ● When the loading process has been completed. If you assign transportation units to a vehicle in a fixed way. you cannot assign these transportation units to another vehicle. A vehicle can comprise one or more transportation units [Seite 613]. You use vehicles to group deliveries and to communicate with invoicing and Transportation Management (TM) [Seite 629].

how many transportation units a vehicle is supposed to have and the order in which they are to be arranged.07. 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. The following figure shows different transportation units: ● ● ● Vehicle 1: Semitrailer truck with one transportation unit Vehicle 2: Truck with cargo area and trailer. for example. You cannot assign them to another vehicle. for example. Use You define transportation units in the master data for transportation. You use them for inventory management in the yard. two transportation units Vehicle 3: Train with four wagons. in other words. Example The following are additional examples of transportation units: ● ● Compartment in a tank truck Container SAP Extended Warehouse Management (SAP EWM) 510 52 . You can assign optional transportation units to other vehicles. for example.SAP Online Help 20. truck cargo area. 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). By linking these packaging materials to means of transport. trailer for a truck. you define. The transportation unit (TU) can be a fixed part of the vehicle.2007 Transportation Unit Definition The smallest loadable unit of a vehicle [Seite 612] that is used to transport goods. In this way. in other words. you define construction rules for your vehicles.

If the SCU has further business characters. If you create an SCU with the business character Warehouse. You will find this SCU data on the following tab pages: ● General General header data of the SCU/location. it remains in the system with the same name. You can use an SCU with different business characters. Integration When a location is created in SAP SCM either manually or by transfer via the core interface (CIF). if you create an SCU with the business character planning location.07. such as door or warehouse. the system does not create a corresponding location. for example. you can replicate certain business characters of locations. The technical name of an SCU must be unique in the system. You can create hierarchies of SCUs to represent the organization of a supply chain. Structure The SCU contains general data and address data of the corresponding location. Conversely. To delete the SCU from the system. the system automatically creates a location with identical general and address data. The SCU also has one or more business characters.SAP Online Help 20.2007 Supply Chain Unit (SCU) Definition Physical or organizational unit that is used with one or more business characters within a logistical process. however. the system automatically creates an SCU with identical general and address data and the business character planning location. Use With the SCU. That is to say. such as the global location number (GLN) and geographical data. change. ● ● Address Data Address data of the location/SCU Business Character One or more business characters of the SCU. which you need in the processes of Extended Warehouse Management (EWM). the system only deletes the business character planning location of the corresponding SCU. it does not contain any further global or application-specific data. In contrast to the latter. and delete SCUs via the SAP menu. for example. SAP Extended Warehouse Management (SAP EWM) 510 53 . This relationship is of significance when a location is deleted. When you delete a location. under Extended Warehouse Management → Master Data → Maintain Supply Chain Unit. An organizational unit may be a goods receiving office or a shipping office. An SCU can simultaneously be used as a planning location and a shipping office. The business characters are predefined by SAP. you must first delete all other existing business characters. it must not conflict with the technical name of a location. You can create.

07.2007 SAP Extended Warehouse Management (SAP EWM) 510 54 .SAP Online Help 20.

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. 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 more information about the simultaneous use of product warehouse tasks and handling unit warehouse tasks. for example. EWM can work with the low-stock physical inventory. you can also perform a physical inventory at the same time [Seite 670]. for example. for deconsolidation [Seite 298] and handling unit warehouse tasks. When you confirm a warehouse task. EWM also submits hazardous substance texts [Seite 969] in the warehouse task. SAP Extended Warehouse Management (SAP EWM) 510 55 .07. for example for internal goods movements. You can identify the type of the warehouse task from the warehouse process type in the warehouse task.2007 Warehouse Task Definition Document that uses Extended Warehouse Management (EWM) to execute goods movements.SAP Online Help 20. Here. for unloading [Seite 608]. see Pick Point [Seite 410]. Logical or physical goods movements or even stock changes can be the basis for a warehouse task.

Example EWM creates warehouse tasks for an outbound delivery with four delivery items. and makes them available for processing. 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. SAP Extended Warehouse Management (SAP EWM) 510 56 . A warehouse employee receives this warehouse order as a work package to pick the items listed in the delivery. then EWM groups these warehouse tasks together into warehouse orders. Integration The warehouse groups together warehouse tasks or physical inventory items.2007 Warehouse Order Definition Document that represents an executable work package that a warehouse employee should perform at a specific time. EWM also groups these physical inventory items together into warehouse orders. see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Warehouse Order → Define Creation Rule for Warehouse Orders.SAP Online Help 20. EWM uses warehouse order creation to assign the resulting four warehouse tasks to a new warehouse order. The warehouse order consists of warehouse tasks or physical inventory items. in other words you create physical inventory items. When you perform a physical inventory.07. Use When you move products. in other words you or Extended Warehouse Management (EWM) create warehouse tasks.

A handling unit has a unique. scannable identification number that you can construct according to industry standards such as EAN 128 or SSCC.SAP Online Help 20.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]. for example. It receives a unique number that is used for identification purposes.07. 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. 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 . Handling units can be nested. All the information contained in the product items. and you can create a new handling unit from several other handling units. is retained in the handling units and is always available. about batches. 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.

Handling Unit Item The items of a handling unit can consist of products. or other handling units. which are displayed in an overview. auxiliary packaging materials. For more information about this overview. weighed. or posted for GI) for a handling unit.SAP Online Help 20. you can store a user schema for the packaging material type. 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.07. see Packing at the Work Center [Seite 506]. SAP Extended Warehouse Management (SAP EWM) 510 58 . If you want to use your own status. blocked. loaded.2007 For more information about the different detailed information.

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.

The warehouse management monitor contains nodes for object classes relating to the following: ● Documents such as warehouse requests (WRs) [Extern]. and physical inventory documents 510 60 SAP Extended Warehouse Management (SAP EWM) .. Choosing Execute. The tree is used solely for navigation purposes. warehouse orders (WOs).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. The warehouse management monitor also contains alert monitoring capabilities. and to enable them to initiate appropriate responses in light of this situation. 1.. 3. 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. which highlight to warehouse managers actual and potential problematic situations in the warehouse. 2. Prerequisites You have accessed the warehouse management monitor by: . You can use the hierarchy tree to display in the upper view area object information for a specific node. based on selection criteria. Entering the warehouse number and name of the monitor. Choosing Extended Warehouse Management → Monitoring → /SCWM/MON Warehouse Management Monitor on the SAP Easy Access screen. warehouse tasks (WTs). and provide exception handling tools.07.SAP Online Help 20.

● SAP Extended Warehouse Management (SAP EWM) 510 61 . via designated pushbuttons. which are based on the standard nodes. and provides more detailed information than the list view. If you use the standard SAP monitor. you can drill down and display the object information for its lower-level nodes. Methods After object information is displayed in either view area. and offers all standard ALV functionalities. The form view provides a focused view of the object. 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. but with specific selection criteria. The list view is displayed in an ALV grid. Customizing Options You can use the standard SAP monitor or you can create your own monitor in Customizing. or with a specific layout.SAP Online Help ● ● 20. The variant-node assignments are lost when you close the monitor session. List and Form Views By default. see Monitor Methods [Seite 882]. including sorting. Variant nodes are always available when the user utilizes the monitor.07.2007 Processes such as stock and bin. you can tailor it to your needs by either creating variants for the standard nodes. For more information about the available methods. ● Creating variants for the standard nodes enables you to use predefined selection criteria while running a session of the monitor. You can similarly drill down to the lower-level nodes from the lower view area. object information is displayed as a list view [Extern]. based on the standard nodes. Creating variant nodes enables you to create your own nodes. You also have the option of toggling to form view [Extern] for a selected object. filtering and printing. you can call methods to perform actions on selected objects. For more information about creating your own monitor. or creating new variant nodes. The form view is displayed in an HTML viewer. see the Implementation Guide (IMG) for EWM under Extended Warehouse Management → Monitoring → Warehouse Management Monitor.

SAP Online Help 20.07. the node icon changes to (regular node) or (variant node).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 node’s context menu. This operation is invoked either by double-clicking the node. as well as all of the same lower-level nodes as are contained in the source node After creating the variant node. This operation is invoked by choosing the Rename Node option in the node’s context menu. previously hidden nodes are displayed in the icon. as well as assign to it a layout variant. This operation is invoked by choosing Show Hidden Nodes. hierarchy tree. on the same level as the node’s category When creating the variant node. with the Unhide a selected node in the hierarchy tree This operation is invoked by choosing the Unhide Node option in the node’s context menu. 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. or choosing the Set Selection Criteria option in the node’s context menu. Change variant node text Display in list view object information for a node SAP Extended Warehouse Management (SAP EWM) 510 62 . you can create a variant for selection criteria. Create a variant node in the hierarchy tree There are two options from the node’s context menu: Create Variant Node for Current Level – creates a variant node directly underneath the original node Create Variant Node for Category Level – creates a variant node under the original node. Delete variant node This operation is invoked by choosing the Remove Node option in the node’s context menu. After choosing this option. After choosing this option.

such as warehouse task (WT). SAP Extended Warehouse Management (SAP EWM) 510 63 . wave. The display transaction is shown in a new session. This operation is invoked by choosing in the top tool bar. by choosing Show display transaction for object For some objects. You call this function by choosing the required object in the ALV. Toggle between list and form views You call this operation by selecting one or more rows in the ALV. you can go directly to the relevant display transaction. outbound delivery.07. This operation is invoked by selecting a row in the ALV. to list view. you can select multiple rows. and storage bin. the display is started in the same session. inbound delivery. and choosing from the list view tool bar.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 node’s list view This operation is invoked by choosing in the top tool bar. If you set parameter /SCWM/MONNAV to “X“ in the user profile. warehouse order (WO). and choosing the pushbutton corresponding to the lower-level node. For some objects. which in this case is indicated by a hotspot.SAP Online Help 20. Information on the lower-level objects appears in the bottom list view. and use the ALV tool bar to branch to the display transaction of multiple objects of the same type. You can toggle back from form view again.

07. 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 . Prerequisites You have defined object class methods. 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. Methods are included in the standard delivery. and their presentation. The methods are assigned to object classes. They are implemented by utilizing function modules from content providers responsible for the object classes. Activities Standard Monitor Methods Method Name Display Bin BIN Change Bin Print HU WO Reprint HU WT WO Display HU Display PI Doc. and carried out on specific objects within the object classes. 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.2007 Monitor Methods Use The warehouse management monitor methods enable you to manage and control warehouse objects and processes. The methods are displayed as standard with the accumulated methods menu buttons.SAP Online Help 20. in Customizing for Extended Warehouse Management → Monitoring → Warehouse Management Monitor → Define Object Class Methods.

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 . Using this method. 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. If none is specified. and group them into a newly-created WO. Confirm Backgr. you can determine the warehouse creation rule. which is stored in the exception log for WOs.07. 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. based on a specified WO creation rule. You can also specify a reason for the split. Cancel WT Confirm Foregr. If none is specified. the system will attempt to determine one pursuant to the search sequence for WO creation rules per activity area.2007 PIHSTK PISLOC Maint. you will need to assign them to a WO. 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. the system will attempt to determine one pursuant to the search sequence for WO creation rules per activity area.SAP Online Help 20.

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.SAP Online Help 20. All the wave items are unassigned from the waves Merges the selected waves into one wave. 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.07.2007 Hold Wave Sets the status of the selected waves [Seite 769] to On Hold.Doc WHRI WHRO WHRITI WHRITO Display WO Log WO SAP Extended Warehouse Management (SAP EWM) 510 66 . 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. Insp. Delete Wave WAVE Merge Wave Wave Deletes the selected waves. 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.

Using this method. The WO cannot be executed until its status is set to Open.2007 Merge WOs Enables you to merge selected open WOs.07. Hold WO Sets the status of one or more selected WOs to Waiting. which is stored in the exception log for WOs. You can also specify a reason for the merge. If none is specified. you can determine the warehouse creation rule. which unassigns the WTs from the WOs. Open WO Add WO Assign Rsrce Unassign Rsrce Queue ändern Change LSD Sets the status of one or more selected WOs to Open. the system will attempt to determine one pursuant to the search sequence for WO creation rules per activity area. 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 . and groups them into a newly-created WO.SAP Online Help 20.

you must have installed Microsoft Internet Explorer version 5 or higher. Multiple users can work with the EGF cockpit at the same time. which you can use in addition to text-based monitors and to display your data graphically. see Warehouse Cockpit [Seite 741]. Integration ● By default.sap.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).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. To ensure that the EGF can be displayed without errors.sap. see SAP Help Portal under help. the EGF uses SAP Internet Graphics Server (SAP IGS) as its graphics provider to generate graphics from data.40 or later installed. 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]). you must have SAP GUI 6. You can however use any other graphics provider that generates graphics from data. Implementation Considerations If you are implementing the standard EGF graphics. see the Implementation Guide (IMG) for EWM under Monitoring → Easy Graphics Framework. For more information about an example implementation.07. The service provider defines which data the EGF displays for an EGF object. see SAP Service Marketplace under service. For more information about security settings in Internet Explorer. ● ● Features The following figure provides an overview of the simplified process flow in the EGF: SAP Extended Warehouse Management (SAP EWM) 510 68 .com/patches.SAP Online Help 20. For more information. For more information.

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

and define authorizations correspondingly. 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. You have the EGF objects Door Assignment and Unconfirmed Warehouse Tasks in a cockpit. ● You can define a cross-user or a user-specific EGF cockpit layout. You can define EGF object data. for example. such as resource or utilization data. You want user B to see only unconfirmed warehouse task data for warehouse numbers 0001 and 0002. or functions in the context menu. For an EGF cockpit menu. In Customizing for the EGF. You can define these authorizations for each EGF object or for each function using an authorization group.2007 In the graphic. you can define a changed structure in the navigation tree with newly created structure nodes (see Definition of EGF Cockpit Layouts [Seite 71]). For more information. select a data value.SAP Online Help ○ ● 20. Input data for an EGF object Follow-up activities for each EGF object ● SAP Extended Warehouse Management (SAP EWM) 510 70 . see the IMG for EWM under Monitoring → Easy Graphics Framework → Define Authorization Groups. and define authorizations correspondingly. Users can only see EGF objects in the navigation tree. for which they have authorization (see Make Settings for the Easy Graphics Framework [Seite 73]). which a user can display as a graphic.07. You want user A to be able to see only the EGF object for unconfirmed warehouse tasks in the navigation tree of the cockpit. from which you can drill-down.

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.07. grid layout. ● Size of the displayed graphic If you change the display size of a displayed EGF object. Prerequisites For more information about EGF prerequisites. You can reload a cockpit layout at any time. If you choose with the quick info Regenerate Graphics.SAP Online Help 20. ● ● ● Grouping of EGF objects in the navigation tree. Integration For more information about EGF integration. the EGF displays both the standard SAP EGF objects and your own EGF objects. for example if you have deleted EGF objects from the navigation tree and want to display them again. see Easy Graphics Framework [Seite 68]. to display your EGF objects in a clearer way Saving input data. and input data SAP Extended Warehouse Management (SAP EWM) 510 71 . Activities If you want to define a cross-user or user-specific EGF cockpit layout. The system displays a modeless dialog box. choose the EGF cockpit (transaction /SCWM/EGF) and define your EGF cockpit layout. the EGF automatically adjusts the size of the displayed graphic as soon as the next refresh interval [Seite 76] has occurred. Choose Save Layout.2007 Definition of EGF Cockpit Layouts Use You can define different EGF cockpit layouts either user-specifically or cross-user. You can also insert a grid within a grid. see Easy Graphics Framework [Seite 68]. or define the size of the individual viewers. the EGF adjusts the display size for EGF objects that are already displayed straight away. 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. 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.

2007 Depending on your authorizations. choose the secondary mouse button.07. 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. SAP Extended Warehouse Management (SAP EWM) 510 72 .SAP Online Help 20.

To do this. in Customizing for EWM. To do this. define your own chart types and assign these or existing chart types to EGF objects. you have to perform an authorization check yourself. see the IMG for EWM under Monitoring → Easy Graphics Framework → Define Cockpits. Settings for EGF Objects ● If you want to display a graphic in a cockpit. execute the IMG activity Define Functions. in Customizing for EWM. execute the IMG activity Define Chart Types and Define Objects. in Customizing for EWM. you must make the following Customizing settings. To do this. For more information. To do this. You define the number of EGF objects for each cockpit. execute the IMG activity Define Authorization Groups and Define Objects. in Customizing for EWM. and want to use the Post Processing Framework or a workflow. To do this. see the IMG for EWM under Monitoring → Easy Graphics Framework → Define Cockpits. You define input data for an EGF cockpit. For more information. specify the number in dialog structure Cockpits → Input Data in IMG activity Define Cockpits. To do this. If you define a navigation to follow-up activities and follow-up objects. For more information. ● ● The EGF only performs the authorization check for EGF objects. If you want to define authorizations for each EGF object or function. in Customizing for EWM. ● 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. in Customizing for EWM. For more information. in Customizing for EWM. specify the number in dialog structure Cockpits → Objects in IMG activity Define Cockpits. If you navigate from a displayed EGF object to follow-up activities. you specify the default chart type for an EGF object in the Chart Type field of IMG activity Define Objects. ● ● SAP Extended Warehouse Management (SAP EWM) 510 73 . execute the IMG activity Define Cockpits. see the IMG for EWM under Monitoring → Easy Graphics Framework → Define Objects. in Customizing for EWM. For more information. For more information.2007 Make Settings for the Easy Graphics Framework To be able to use the Easy Graphics Framework (EGF). define authorization groups and assign these to an EGF object or function. see the IMG for EWM under Monitoring → Easy Graphics Framework → Define Functions.07. see the Implementation Guide (IMG) for EWM under Monitoring → Easy Graphics Framework → Define Chart Types and Define Objects. see the IMG for EWM under Monitoring → Easy Graphics Framework → Define Cockpits. see the IMG for EWM under Monitoring → Easy Graphics Framework → Define Objects.SAP Online Help 20. define follow-up activities. For more information. define your own refresh rate. To do this. ● You define the default chart type for an EGF object. 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]). see the IMG for EWM under Monitoring → Easy Graphics Framework → Define Objects. If you want to change the predefined refresh rate. To do this. For more information.

and all EGF objects. and save them. or that EGF is to always use blue. you are responsible for which data the EGF displays with the URL. in Customizing for EWM. Settings for Your Own Graphics ● If you want to use something other than SAP Internet Graphics Server (SAP IGS) as your graphics provider. The EGF receives the data from which a graphic is to be generated from the service provider. We recommend that you make the following settings in your Browser: Make Browser Settings for the Easy Graphics Framework [Seite 79] For more information. You can activate a virus check with the SAP Web Repository to check documents and graphics before an upload. The EGF then calls your graphics provider instead of the SAP IGS. and allow it as a default chart type for all users. such as per resource or warehouse task. for example. you can choose between User-Specific and Cross-User. red and green to display pie charts. allowing you to return a Uniform Resource Locator (URL) to the EGF. see the IMG for EWM under Monitoring → Easy Graphics Framework → Define Cockpits. on the SAP Easy Access screen. You have defined the authorizations per EGF object or user if required. EGF cockpit COCKPIT2. for example. execute the IMG activity Define Chart Types. Make your changes. choose Extended Warehouse Management → Monitoring → Process Chart Template. you define the graphic attributes for each EGF object in dialog structure Cockpits of IMG activity Define Settings. We recommend that you use SAP Web Repository to save and display graphics using a URL with the EGF. and allow it as a default chart type for user USER1. For more information. all EGF cockpits. This calls the GET_URL method of your service provider. or per user. you can define that the background color in graphics is always blue. You can define a chart type.SAP Online Help 20. You can assign the following authorizations: ○ ○ ○ User * USER1 USER2 You can define a chart type. yellow. in Customizing for EWM. Calling a URL outside of the SAP system and calling a graphics provider within an SAP system may not be safe.2007 Settings for Graphics ● You define the attributes of a graphic for each EGF object. The EGF uses an HTML Viewer to display a URL that links to a graphic. You can define a third chart type. For more information. For example. and EGF object OBJECT2. define your own graphic types and set the URL indicator. To do this. 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). see: SAP Extended Warehouse Management (SAP EWM) 510 74 . EGF cockpits. see the IMG for EWM under Monitoring → Easy Graphics Framework → Define Chart Types. and allow it as a default chart type for user USER2. EGF Cockpit * * COCKPIT2 EGF Object * * OBJECT2 Chart Type PIE CHART PIE CHART PIE CHART Default Chart Type DEFAULT DEFAULT1 DEFAULT2 To do this.07. since data can enter the system without undergoing a virus check. In this situation. To do so. and EGF objects. When saving.

you executed the IMG activity Define Chart Types and Define Cockpit Settings.sap. SAP Service Marketplace under service. in Customizing for EWM.sap.70 → SAP NetWeaver Components → SAP Internet Transaction Server → ITS Implementation Models → WebRFC Programming ### Web Reporting.com/securityguide → SAP Supply Chain Management → SAP Supply Chain Management Security Guide SCM 5.sap. SAP Help Portal under help.com → SAP R/3 Enterprise Release 4.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.2007 The IMG for EWM under SAP NetWeaver → Application Server → System Administration → Virus Scan Interface.07. see the IMG for EWM under Monitoring → Easy Graphics Framework → Define Chart Types and Define Cockpits. SAP Extended Warehouse Management (SAP EWM) 510 75 .1 ■ SAP Help Portal at help. To do this. For more information.SAP Online Help ■ ■ 20.

See also: Make Settings for the Easy Graphics Framework [Seite 73] SAP Extended Warehouse Management (SAP EWM) 510 76 . the EFG only checks after ten minutes whether a refresh is required for the second cell in the grid. If this is the case.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. for example. The refresh rate is located at EGF object level. 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. If you are using the EGF for planning purposes or for forecasts. If the service provider only responds after ten minutes. You can change the refresh rate at runtime.SAP Online Help 20. such as a trend for the coming year. such as daily resource requirements for a warehouse task. enabling you to display trends. or in the context menu for the object at runtime. You can also refresh all displayed objects by choosing Refresh Data in the SAP GUI. the EGF calls the service provider and waits for its response. Features The default refresh rate is set to one minute. Activities You deactivate the refresh rate by setting the refresh rate value to zero either in Customizing for the EGF for the object.07. The EGF checks to see whether a refresh is required for the first cell in the grid. You can define the refresh rate for each EGF object. or forecasts. you can deactivate the refresh rate.

this interface method enters the function code for the chart. This URL forms the link to the graphic that the EGF is to display. Methods and Function Modules in the EGF Use The Easy Graphics Framework (EGF) allows you to work with various interfaces. /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. Interface /SCWM/IF_EGF_SP Method GET_DATA Description Gets chart data from the application. and function modules. You must enter the cockpit ID as an import parameter. Features Interfaces and Methods The following table gives you an overview of the methods in the EGF. Generates graphic of a graphics provider in the EGF. Gets a URL from the application. only sets the color of the traffic light. Function Module /SCWM/EGF_COCKPIT Description Starts an EGF cockpit implementation. see the interface documentation. methods. such as a traffic light.SAP Online Help 20. A simple chart.07. If the application receives a function code for a follow-up activity. SAP Extended Warehouse Management (SAP EWM) 510 77 . Function Modules The following table gives you an overview of the function modules in the EGF. Most charts require a group of row values and a group of data categories as data format. such as for all EGF graphics of class /SCWM/CL_EGF_IGS_SERVICES in interface /SCWM/IF_EGF_CHART.2007 Interfaces.

see the function module documentation. For more information.SAP Online Help 20. The EGF object definition is done dynamically using the interface of the function module.07. You transfer a container instance to the function module. such as to class CL_GUI_CUSTOM_CONTAINER. No Customizing is required here. The system generates a modeless dialog box in which the required EGF object is displayed. /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. No Customizing is required here. No Customizing is required here. in which the required EGF object is displayed.2007 /SCWM/EGF_CONTAINER You transfer a container instance to the function module. such as to class CL_GUI_CUSTOM_CONTAINER. SAP Extended Warehouse Management (SAP EWM) 510 78 . All the data required for generating the cockpit is transferred using the interfaces of the function module. choose the following in Customizing for EWM: Monitoring → Easy Graphics Framework → Define Chart Types and Define Cockpits. 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. The EGF object definition is done dynamically using the interface of the function module. To do this.

Choose Custom Level. 4. We cannot recommend Internet. Choose the Web content zone: Under Internet Options.. Prerequisites To ensure that the EGF can be displayed without errors. In the Internet Explorer menu. 2. In the Security Settings window.07. 3. 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 . You must also make the security settings listed below in your Microsoft Internet Explorer. you can choose from different options. Trusted Sites is safer.. you must have installed Microsoft Internet Explorer version 5 or higher.2007 Make Browser Settings for the Easy Graphics Framework Use If you work with a Microsoft Internet Explorer in the Easy Graphics Framework (EGF). but Local Intranet offers better performance (see also SAP Note 785308).. Procedures . choose Tools → Internet Options. 1. you must meet the following prerequisites and make the following security settings.SAP Online Help 20. 5.. Choose the Security tab page..

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

from any ship-from party or from any ship-from location. Information about planning is saved in the inbound delivery. a difference is made in delivery processing between the inbound delivery process and the outbound delivery process. are triggered and the data generated by the shipping processing is recorded. the status is monitored. 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 delivery process covers the notification. 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. Features In delivery processing. On creation of the delivery. It provides functions for executing goods receipt and goods issue activities. From the purchase order. and all the data collected during the inbound delivery is recorded. see the documentation for the relevant SAP application (for example. documents [Seite 83] are provided which represent the delivery process in the system. mySAP Supply Chain Management → SAP Extended Warehouse Management).2007 Delivery Processing Purpose Delivery processing plays a significant role in the logistics chain. packing. and all the data collected during the inbound delivery is recorded. Returns to the supplier.SAP Online Help 20. The outbound delivery process covers all shipping activities such as picking. activities such as the putaway or scheduling. to any ship-to party. transportation and goods issue. On creation of the delivery. Information about shipping planning is saved in the inbound delivery. the delivery the subsequent putaway and the goods receipt posting of the ordered goods. the status is monitored. Corresponding to the goods receipt and goods issue processing. to the warehouse. 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. Inbound delivery process The following inbound delivery scenarios are supported by delivery processing: ● ● Deliveries to the customer.07. Returns from the customer. shipping activities such as picking or shipment scheduling. to any ship-to party or to any ship-to location. ● Field control [Seite 99] 510 81 SAP Extended Warehouse Management (SAP EWM) . or to any ship-to location.

SAP Extended Warehouse Management (SAP EWM) 510 82 . mySAP Supply Chain Management → Data Archiving). see the documentation for the relevant SAP application (for example.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.

Header e. The execution of the actions depends on the settings in the Post Processing Framework (PPF) [Seite 105]. This data is relevant for the complete document.SAP Online Help 20. quantity Item 2 Item 3 Document header The document header contains the general data for the inbound or outbound delivery.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. Material. It includes: ● ● ● ● Goods receiving point or shipping point Scheduling data (for example. Shipping point. shipping or delivery date) Weights and volumes for the complete inbound/outbound delivery Supplier.g. sold-to party and goods recipient numbers SAP Extended Warehouse Management (SAP EWM) 510 83 . goods recipient Item 1 e. Structure A document comprises a document header and any number of document items. The following figure shows the structure of a delivery document.g. 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.

Document items In the document items. In this case. only one document type (Z100) is used for the complete inbound delivery process. The document type determination defines that document types Z200 and Z300 are to be derived from document type Z100 in the inbound delivery process.07. The document category classifies the different documents that can be processed by the system in delivery processing. 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. PDI Inbound delivery Document type Z100 Inbound delivery process Using the document type determination. IDR Inbound delivery notification Document cat. Document cat. The following figure shows a possible relationship between the document category and the document type in the inbound delivery process. Document types Z200 and Z300 are defined for the document category inbound delivery. In Customizing for Delivery Processing [Seite 108]. 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. The document type defines the business aspects of a document. It is defined by the system and cannot be changed.2007 The document header is defined in the system by the document category and the document type. IDR Inbound delivery notification Document cat.SAP Online Help 20. you can define your own document types and document type determination. Document cat. The document type classifies the documents with regard to the complete delivery process. This includes: SAP Extended Warehouse Management (SAP EWM) 510 84 . you find the data relevant to the individual items. you can derive several document types from a document category and therefore define certain delivery processes.

you can define more customer profiles and therefore adjust the documents to suit your business process. text profile and incompleteness profile) The system profile is not configurable and is linked to the document categories and item categories. 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. The item category classifies the different items that can be processed by the system for delivery processing. status profile.07. you can also configure your business process via the item type and the item type determination in Customizing for Delivery Processing. In Customizing for Delivery Processing. It is defined by the system and cannot be changed. 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.2007 Material number Delivery quantity Location specifications (goods receiving point. for the document items. 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. Service profiles Service profiles define how a document is processed in the system as well as its business scope. The customer profiles are linked to the document types and to the item types. Two types of service profile exist: ● ● System profile Customer profile (for example. As for the document header.

07.SAP Online Help ● 20.2007 Date types SAP delivers predefined status profiles for the standard processes in delivery processing. SAP Extended Warehouse Management (SAP EWM) 510 86 . 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]. General Settings The general settings for the documents in delivery process are not controlled by the service profiles.

An inbound delivery notification is created automatically as a result of this message. 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]. All the information contained in the message is saved in the inbound delivery notification. SAP Extended Warehouse Management (SAP EWM) 510 87 . An inbound delivery is created automatically from the inbound delivery notification. you can define your own document types.SAP Online Help 20. you can also process or reject incoming changes to an existing inbound delivery. The following configuration exists in the standard system: ● The delivery process receives a message from a reference document with all the relevant logistics data. delivery note or purchase order. 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 process the data in the inactive inbound delivery notification and you can create a new inbound delivery by activating the request manually. Integration The execution of the actions depends on the settings in the Post Processing Framework (PPF) [Seite 105]. an inactive inbound delivery notification (inactive version) is created in addition to the existing active inbound delivery notification. item types and service profiles and therefore you can adapt the document to suit your business process. Using the inbound delivery notification. The shipping notification from the supplier is saved in the inbound delivery notification.07. for example). ● Changing an existing inbound delivery: If a change to an existing inbound delivery is rejected.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.

Adjusting the delivery quantity and the transferred quantity In this case. validate and delete an inbound delivery. Use The inbound delivery is used as a working object in the inbound delivery process. production or outbound delivery. 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. The quantity in the inbound delivery notification is also adjusted and a new inbound delivery is created. item types and service profiles and therefore you can adapt the document to suit your business process. you can define your own document types.SAP Online Help 20. ● ● ● ● Posting a goods movement Canceling a goods movement Creating items Deleting items You can save. the delivery quantity is adjusted to the quantity posted in the goods receipt. This process starts on receipt of the goods in the yard and ends on transferal of the goods at the final putaway. 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].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. SAP Extended Warehouse Management (SAP EWM) 510 88 .07.

SAP Online Help 20.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. SAP Extended Warehouse Management (SAP EWM) 510 89 .07. The execution of the actions depends on the settings in the Post Processing Framework (PPF) [Seite 105].

you can also process or reject incoming changes to an existing outbound delivery order. The delivery process saves the information from the message in the outbound delivery request. 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].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. Using the outbound delivery request. you can define your own document types. an inactive outbound delivery request (inactive version) is created in addition to the existing active outbound delivery request. 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.07. An outbound delivery order is created automatically from the outbound delivery request.SAP Online Help 20. 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]. item types and service profiles and therefore you can adapt the document to suit your business process. for example). The message itself is not saved. ● Changing an existing outbound delivery order: If a change to an existing outbound delivery order is rejected. 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 . An outbound delivery request is created automatically as a result of this message.

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. validate. 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. item types and service profiles and therefore you can adapt the document to suit your business process. 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. This process starts with the first planning activities for the outbound delivery and continues until the finished goods have been loaded and sent. 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].SAP Online Help 20.07. you can define your own document types. The following configuration exists in the standard system: SAP Extended Warehouse Management (SAP EWM) 510 91 . Integration The execution of the actions depends on the settings in the Post Processing Framework (PPF) [Seite 105].

07. This status is determined via the corresponding outbound delivery request from the reference document. you cannot create a delivery. SAP Extended Warehouse Management (SAP EWM) 510 92 . One or several outbound deliveries are created from the outbound delivery order. In this case.SAP Online Help ● 20. Here. ● The outbound delivery order has the status Locked (Preceding Document) when only used as a preview for planning warehouse activities. all the relevant data is copied from the outbound delivery request.2007 The outbound delivery order is created automatically after activating the outbound delivery request [Seite 90].

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. 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 . delete and archive an outbound delivery.SAP Online Help 20. Use The outbound delivery is used as the basis for printing the delivery note or for sending a shipping notification. 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].2007 Outbound Delivery Definition The outbound delivery is a document [Seite 83] representing the goods to be delivered together to a goods recipient. you can define your own document types.07. item types and service profiles and therefore you can adapt the document to suit your business process. process.

You cannot change these attributes in Customizing. for example in a display or change transaction. Integration The status management described here is used in delivery processing exclusively. Several of these status types are indicated by special attributes which are displayed in the following table. 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. 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. On the other hand. goods receipt status. It changes along with the business transactions. A status can allow or prohibit a business transaction or it may have no influence at all.2007 Status Management Use Status Management controls business transactions (also called activities) by assigning one or several statuses to a delivery document. A status value can disallow a business transaction. The status types are linked to the document and item types of delivery processing via a status profile. header or item). You can change the settings for the status types using this status profile. a business transaction can set a new status. The status value defines the delivery document status with regard to the status type (for example. Projected status Overall status SAP Extended Warehouse Management (SAP EWM) 510 94 . No status value may disallow the transaction. 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. This attribute has a purely technical meaning.07. Yes/No or Not Started/In Process/Completed). The system calculates the status value of such a status type from the status type with the same name from higher document levels. SAP delivers predefined status types for the standard processes in delivery processing. The field control [Seite 99] for delivery processing also depends on status management.SAP Online Help 20. 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 following conditions must be fulfilled before a business transaction can be carried out: ● ● At least one status value must allow the transaction. An overall status provides compact information on a certain quantity of statuses for the same partial object (for example. 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.

20. several status profiles for the configuration of document and item types can be derived from one system profile. therefore. 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. However. overall status.07. The following graphic shows the relationships between the individual objects in status management. In the status management for delivery processing. the user statuses can only have two values (Yes/No). The user status profile in the general status management is linked to the system profile for delivery processing via an object type. you cannot assign several user status profiles to one object type. SAP Extended Warehouse Management (SAP EWM) 510 95 . The user statuses are grouped via the user status profile in the general status management. You can increase the number of available status types by adding your own user statuses. You cannot change this indicator for these status types. to several system profiles. The status type is not saved permanently.2007 This indicator is only set for derived status types (aggregated status. User Status Profile of General Status Management Ux User Status Ux Sx Predefined Sx 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. Transient status The system only calculates this status type for the runtime. header or item). a user status profile in the general status management can be assigned to several object types and.SAP Online Help example. for example). The object type and system profile have a one-to-one relationship. On the other hand. You use this indicator to activate or deactivate several status types in each status profile. Here. there are also status types which always have to be active. As opposed to the status types predefined by SAP.

07.2007 Actions In Customizing for Delivery Processing [Seite 108].SAP Online Help 20. 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 .

Features The quantity offsetting is executed at item level and at schedule line level of a document. 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. 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. In delivery processing. you can offset quantities consistently independently of the application. the schedule line level is not supported by the documents in delivery processing. You therefore define how the reduced quantity of a document is determined and which algorithm is to be used to calculate this quantity. At present. Quantity offsetting The quantity offsetting determines the function (quantity offsetting rule) with which the different quantities are calculated. for example.2007 Quantity offsetting Use Using the quantity offsetting function. SAP Extended Warehouse Management (SAP EWM) 510 97 .07. for example. The data in Handling Unit Management (HUM) is used for the packed quantity.SAP Online Help 20. for example). If you use the document flow for the quantity calculation algorithm. Integration The quantity offsetting is a cross-application service within Logistics. you have to define which links are relevant in Customizing for delivery processing. 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. This means that you can check whether you actually delivered the agreed quantity on a certain date. The relevant data for the quantity calculation algorithm comes from either the document flow or from a different source (from a service.

SAP Online Help 20. Quantity role The quantity role is used to group quantity calculation or quantity offsetting rules for certain applications or processes. A quantity role can exist of several quantity types. a quantity offsetting profile exists in the quantity offsetting. In this way.2007 Depending on how it is used. Activities In Customizing for Delivery Processing. SAP delivers predefined quantity offsetting profiles types for the standard processes in delivery processing. Quantity offsetting profile If you want to execute quantity offsetting automatically. you can access the quantity offsetting with or without quantity calculation. 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 . The quantity offsetting profile is linked to the document type and item type of a document. This profile contains the quantity calculation and quantity offsetting rules to be used by the quantity offsetting to calculate the quantities automatically. you can define the quantity calculation or quantity offsetting rules according to the application or the process. You can find more information in Customizing for Delivery Processing [Seite 108].07.

During the delivery process. goods receipt status. One field may have different settings for different statuses. 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]. the field is displayed as a non-changeable field depending on the assigned status (status type and status value). Every component in a structure is uniquely identified by the logical field name and can therefore be addressed directly. If this indicator is set. The field control supports fields at header and item level of a document. the system defines the status for which a field is displayed and can be changed for each logical field name. If this indicator is set. 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. the field remains changeable and is not hidden. the system controls which fields can be displayed and changed via the status of the document and item type. Defines the delivery document status with regard to the status type (for example. Integration Field control depends on status management [Seite 94]. When accessing the field control. If no consistencies are found. the table of field attributes is read sequentially by the system. Here. Every time this information is consistent.SAP Online Help 20. Status value Display field Hide Several statuses can be assigned to one field. Field attributes In the field attributes of the field control. the field is not displayed depending on the assigned status (status type and status value). the system assigns the corresponding attributes from the field attributes (display or hide field) to the field. the system compares the status information in the table with the current status information of the document.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. unloading status or putaway status). SAP Extended Warehouse Management (SAP EWM) 510 99 . Yes/No or Not Started/In Process/Completed).

Field control profile A field control profile contains all the allowed fields and their field attributes for a certain document or item type. You cannot change the field attributes of the system profiles delivered by SAP.SAP Online Help 20. When accessing the field control.07. system profiles and field control profiles for the standard processes in delivery processing.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. SAP delivers predefined logical field names. 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. you can add new field attributes. you can include new logical field names in the field control. The incompleteness profile also depends on the system profile of the field control. you can add new field attributes. The assignment to the document or item type is carried out via the field control profile. You cannot change these field attributes in the system profile nor in the assigned field control profiles. The field attributes saved in the system profile are valid for all assigned field control profiles. Via the system profile. ● ● 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 . Activities In Customizing for Delivery Processing [Seite 108]. the system determines the assigned field control profile via the document and item type. Every field control profile is assigned to a system profile. It uses the list of all allowed fields. However. However.

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.

the action is terminated and an appropriate message is issued. ● ● 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 . A mandatory field is defined by a logical field name in the system. 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. When accessing the incompleteness check. Activities The incompleteness check is executed automatically by 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. In Customizing for Delivery Processing [Seite 108]. you can add new field attributes.SAP Online Help 20. However. you can add new field attributes. However.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. SAP delivers predefined logical field names and incompleteness profiles for the standard processes in delivery processing. If the incompleteness check determines a mandatory field that has not been filled. You cannot change the field attributes delivered by SAP. the corresponding field is automatically checked for completeness. Every time this action is executed. the system determines the assigned completeness profile via the document and item types and therefore the corresponding settings for the mandatory fields. The incompleteness profile is assigned to the document and item types. Every logical field name that represents a mandatory field is assigned an action. Incompleteness profile The settings for the incompleteness check are saved in an incompleteness profile.07.

Check whether the delivery date lies in the past. Check whether the location data corresponds to the location master. Check whether partial deliveries are allowed. If a document is inconsistent. ● Activities The consistency check is executed automatically by the system. The consistency check uses these specifications to determine whether partial deliveries are allowed. Delivery processing determines the number of allowed partial deliveries from the reference document. Example If you want to compare the delivery quantity of the inbound and outbound delivery with the tolerance defined in Customizing. Check whether the specifications for the Incoterms. the system issues a message and you cannot split the delivery. document category. ● Check whether the retention period is expired. reference documents and date types correspond to the settings in Customizing for delivery processing. SAP Extended Warehouse Management (SAP EWM) 510 103 . Customizing and master data. the system issues an appropriate message. You can also trigger the consistency check manually by choosing the delivery document in the maintenance transaction. Check whether the product data corresponds to the product master (for example.SAP Online Help 20.2007 Consistency Check Use The consistency check determines whether any data inconsistencies exists between the delivery document [Seite 83]. process codes. Check whether the document contains items. you can perform a Tolerance Check [Seite 104]. product ID and allowed units of measure). item type and item category correspond to the settings in Customizing for delivery processing.07. partner roles. If no partial deliveries are allowed. Features The consistency check contains the following checks: ● ● ● ● ● ● Check whether the document type.

You cannot change the tolerances in the delivery process. the delivery process checks to see whether the changed delivery quantity still lies within the defined tolerances. SAP Extended Warehouse Management (SAP EWM) 510 104 .07.2007 Tolerance Check Use The tolerance check determines whether the delivery quantity lies within the given tolerances for both inbound and outbound deliveries. 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. As soon as the delivery quantity changes in a document. Features The tolerance check is split into the underdelivery tolerance and the overdelivery tolerance.SAP Online Help 20. The system does not issue any message. overdeliveries of any size are allowed. Integration You define the tolerances for the delivery quantity in the reference document that is used to trigger the delivery process. It is specified as a percentage. If the goods quantity lies below or above the tolerance values. ● ● Underdelivery tolerance The minimum allowed delivery quantity. the system issues a warning message. Overdelivery tolerance The maximum allowed delivery quantity. Activities The tolerance check is executed automatically by the system. It is specified as a percentage.

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 . Activities In Customizing for Delivery Processing [Seite 108]. You use the schedule conditions to determine when an action is scheduled. For more information. see Post Processing Framework (BC-SRV-GBT) [Extern]. Integration The PPF provides basic functions that are delivered with pre-defined settings depending on the application. You assign the actions to a document type via the action profile. The action profile is linked to the document type.SAP Online Help 20. Note that to what extend it is recommended to make changes to the presettings depends on the application. Delivery processing only uses the schedule conditions.07. Conditions In the PPF there are schedule conditions and start conditions. 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.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]. You can adjust the settings as you require.

SAP Online Help 20.07.2007 SAP Extended Warehouse Management (SAP EWM) 510 106 .

SAP Online Help 20.2007 Change Documents in Delivery Processing Use You can use change documents to access information on changes made to a delivery document. 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. 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 . 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. However.07.

General Settings: To define the cross-process settings such as Services in the SAP Reference IMG. For the outbound delivery start from the Implementation Guide (IMG) and choose Extended Warehouse Management → Goods Issue Process → Outbound Delivery. choose Extended Warehouse Management → Business Add-Ins (BAdIs) for the Extended Warehouse Management → Goods Issue Process → 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.SAP Online Help 20. For the cross-process settings such as services.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.07. Business Add-Ins (BAdIs): For the inbound delivery. Menu Paths For the inbound delivery. For the outbound delivery. 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 → Cross-Process Settings → Delivery Processing. in the Implementation Guide (IMG). start from the SAP Easy Access screen and choose Extended Warehouse Management → Delivery Processing → Outbound Delivery. in the Implementation Guide (IMG). start from the SAP Easy Access screen and choose Extended Warehouse Management → Delivery Processing → Inbound Delivery. SAP Extended Warehouse Management (SAP EWM) 510 108 . choose Extended Warehouse Management → Cross-Process Settings → Delivery Processing.

07. EWM works with both inactive and active document versions [Seite 119]. You can create. Structure A warehouse request consists of ● Document categories with different document types.2007 Warehouse Request Definition A warehouse request is a document that enables the processing of warehouse activities for a specific product. 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 . You can define the document types in Customizing for delivery processing. For more information about defining document types in EWM. It creates warehouse tasks [Extern] to fulfill the warehouse requests. 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.SAP Online Help 20. process. for putaway or picking). or archive warehouse requests [Seite 135]. delete. Create posting changes [Seite 128] Process internal goods movements [Seite 122] Process scrappings [Seite 130] EWM uses warehouse requests to build waves [Seite 773].

You can define the item types in Customizing for delivery processing.07. 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.SAP Online Help ● 20.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. These include: ○ ○ Text management [Seite 145] Quantity offsetting [Seite 97] SAP Extended Warehouse Management (SAP EWM) 510 110 .

For a goods receipt process. this is a sales order system. this is an ERP system.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. see the Implementation Guide (IMG) for EWM under Interfaces → ERP Integration.SAP Online Help ○ ○ ○ 20. For a goods issue process. For more information about Customizing of integration between an Enterprise Resource Planning (ERP) system and EWM.07. SAP Extended Warehouse Management (SAP EWM) 510 111 .

2007 Warehouse Req. EWM uses the inbound delivery notification or outbound delivery request. However. In the case of outbound deliveries. The warehouse request for inbound and outbound deliveries includes additional fields and functions. 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 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. See also: Determination of Priority for Inbound Deliveries [Seite 414] SAP Extended Warehouse Management (SAP EWM) 510 112 .SAP Online Help 20. The inbound delivery only displays these priority points. The priority points are calculated in SAP Advanced Planning & Optimization. EWM uses a warehouse request to create warehouse tasks for putaway or picking. See also: Creation of a Warehouse Request for an Inbound Delivery [Seite 113]. EWM can automatically create the corresponding warehouse requests for inbound or outbound deliveries. you can also create these warehouse requests manually. manual creation is limited to the warehouse requests for the scrapping process. Integration EWM receives inbound delivery notifications [Seite 87] or outbound delivery requests [Seite 90] from other systems. and Scrapping [Seite 130]. see Warehouse Request [Seite 109]. to create a warehouse request for an inbound delivery [Seite 88] or an outbound delivery order [Seite 91]. compared to an inbound delivery or outbound delivery order. EWM executes the posting of goods movements for the goods receipt or goods issue based on the warehouse request. in other words the messages from the ERP system. Based on these messages. Structure For a description of the structure of a warehouse request.07. Warehouse Request for Inbound Delivery or Outbound Delivery Order [Seite 116]. As well. For example.

For this to occur. It uses the condition technique to do this. EWM sends the current data to SAP Business Information Warehouse. The additional functions that run when creating or changing a warehouse request automatically for the inbound delivery. Prerequisites The warehouse process type in the warehouse request must be defined. see the IMG for SCM Basis under Packing → Packaging Specification. A prerequisite for this is that you must have activated the update of delivery items in SAP Business Information Warehouse. see the SAP Library under SAP Web Application Server → Business Management (BC-BMT) → WebFlow Engine (BCBMT-WFM). Features The common functions that run when creating or changing a warehouse request (either inbound or outbound) automatically. When you generate a warehouse request for an inbound delivery. For more information. For more information about Alert Management. ● Connection to SAP Business Information Warehouse When a delivery item has been completed in EWM. For more information about defining and determining the warehouse process type. EWM can automatically trigger a WebFlow or SAP Alert Framework to notify someone. see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Warehouse Task → Define Warehouse Process Type and Determine Warehouse Process Type. Integration When EWM creates a warehouse task for a warehouse request. you must have defined the WebFlow or SAP Alert Framework accordingly. 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). as well as for the inbound delivery and outbound delivery order.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). For more information about the WebFlow Engine.SAP Online Help 20. enable you to do the following: ● Automatic Packing EWM automatically creates handling units according to the packing instruction. you can generate valueadded service orders (VAS orders) automatically for the warehouse request item [Seite 231]. see the IMG for EWM under Interfaces → SAP Business Information Warehouse → General Settings → Activate BW Update. enables you to do the following: ● If no packaging specification [Extern] exists for the packing of products during goods receipt. SAP Extended Warehouse Management (SAP EWM) 510 113 .07. For more information. it updates the document flow for the warehouse request for the delivery.

● Creation of batches ○ Before you create batches. depending on your Customizing Determination of warehouse process type. minimum shelf life) to the batch class. you can carry out partial goods receipt postings using the warehouse task confirmation. ● Goods receipt posting ○ If EWM automatically creates a delivery based on a warehouse request from ERP.07. ERP sends a message for an inbound delivery notification [Seite 87] or posting change request to EWM. EWM automatically executes a corresponding partial goods receipt posting. It reports this to ERP. such as whether EWM is to immediately confirm a warehouse task SAP Extended Warehouse Management (SAP EWM) 510 114 . you can specify this batch manually in the inbound delivery.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. Activities ● ● ● At the same time as an inbound delivery is generated in ERP. If the batch is known in ERP. you must assign a batch class of the class type 023 to the product subject to a batch management requirement in SAP ERP. delivery processing checks whether the handling unit is permissible for the warehouse in question. 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. A batch of the product must also exist already in EWM. EWM automatically generates a warehouse request using the Post Processing Framework (PPF). When you confirm a warehouse task. For more information. you can either post the goods receipt for individual handling units only. ○ ● Wave assignment For more information about Customizing.SAP Online Help ● ● 20. During automatic creation and saving of the warehouse request. see the IMG for EWM under Goods Issue Process → Wave Management. You have also assigned the object characteristics LOBM_HERKL (country of origin) and LOBM_VFDAT (shelf life expiration date. or you can post it completely. which controls the processing of a warehouse task in EWM. If a batch is unknown in EWM. ○ ○ For more information. With the delivery UI. EWM automatically provides this in the delivery. the ERP system sends this information to EWM. see Connection of Delivery Processing to Batch Management [Seite 245]. see the IMG for EWM under Goods Receipt Process → Slotting → Influencing Parameters → HU Types → Define HU Types per Warehouse Number.

For more information. Scrapping.2007 EWM creates the warehouse tasks at the same time as releasing the wave.SAP Online Help ● 20. To do this. on the SAP Easy Access screen. choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order. in the Corr. see Warehouse Order Creation [Seite 419] and Creation of Warehouse Tasks for Warehouse Request [Seite 412].Deliv. ● EWM copies most of the settings that you make in Customizing for process control to the delivery documents. EWM creates warehouse orders to assemble work packages for the individual warehouse workers. Display an outbound delivery order in the form view. In accordance with the warehouse tasks. Here you can find the settings from Customizing. SAP Extended Warehouse Management (SAP EWM) 510 115 .. and displays them on the user interface for the outbound delivery order.07. for example. or Pickup fields.

Therefore. ERP copies this information to the corresponding ERP outbound delivery.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). Features The common functions that run when creating or changing a warehouse request (either inbound or outbound) automatically. You can assign handling units and cross-delivery handling units to an outbound delivery order. SAP Extended Warehouse Management (SAP EWM) 510 116 . EWM can perform route determination [Seite 638] in accordance with your Customizing. Prerequisites The warehouse process type in the warehouse request must be defined. the system organizes the total quantity using replenishment strategies. you can generate value-added service orders (VAS orders) automatically for the warehouse request item [Seite 231]. see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Warehouse Task → Define Warehouse Process Type and Determine Warehouse Process Type. For more information about defining and determining the warehouse process type. You can use the activity area that is assigned to the storage bin as a selection criterion. it does not make quantity reservations for the products. However. For fixed storage bins. For more information. It contains 10 tires only. 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. It uses the condition technique to do this. as well as for the inbound delivery and outbound delivery order.07. As a prerequisite. you must have activated the update of delivery items in SAP Business Information Warehouse. The additional functions that run when creating or changing a warehouse request automatically for the outbound delivery order. EWM sends the current data to SAP Business Information Warehouse. When you generate a warehouse request for an outbound delivery order. Integration When you generate a warehouse request for an outbound delivery order. The system determines the same source storage bin for each delivery item. A delivery contains three delivery items of 10 tires each.SAP Online Help 20. see the IMG for EWM under Interfaces → SAP Business Information Warehouse → General Settings → Activate BW Update. the total quantity of 30 tires does not exist at the source storage bin. enable you to do the following: ● Automatic packing EWM automatically creates handling units according to the packing instruction. ● Connection to SAP Business Information Warehouse When a delivery item has been completed in EWM.

07. 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. see the IMG for EWM under Cross-Process Settings → Delivery Processing → Process Management and Control. On the SAP Easy Access screen. 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. EWM automatically generates a warehouse request using the Post Processing Framework (PPF). Use the input help to select a packing item type. see the IMG for EWM under Cross-Process Settings → Warehouse Task → Determine Warehouse Process Type. Select an outbound delivery order. ● You can control processes for outbound delivery orders as part of the configuration. Inventory management is no longer required for this consumable material. choose with the quick info Create. you can create an invoice before goods issue in the outbound delivery process. the export relevance or the route that is determined. for example.SAP Online Help 20. ● ● ● Route determination Determination of staging area group Adding packing items If. choose Extended Warehouse Management → Delivery Processing → Maintain Outbound Delivery Order. you have defined process indicators for the delivery document header and for the delivery document items in Customizing for EWM. ERP sends a message for an outbound delivery request [Seite 90] or posting change request to EWM. For more information. depending on your Customizing SAP Extended Warehouse Management (SAP EWM) 510 117 .2007 For more information about Customizing for stock removal strategies. During automatic creation and saving of the warehouse request. As a prerequisite. 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. ● A department within your company requests consumable material from your warehouse. for example. for a cost center or project. and on the Items tab page. for example. You can also do this on the basis of other delivery parameters. For example. You update the consumable material. ● ● ● ● 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. you use recyclable packing materials. see the IMG for EWM under Goods Issue Process → Strategies. 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]).

see Warehouse Order Creation [Seite 419] and Creation of Warehouse Tasks for Warehouse Request [Seite 412].Deliv. Scrapping or Pickup. choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order. SAP Extended Warehouse Management (SAP EWM) 510 118 . EWM creates warehouse orders to assemble work packages for the individual warehouse workers.2007 Determination of warehouse process type. ● EWM copies most of the settings that you make in Customizing for process control to the delivery documents. For more information.SAP Online Help ○ 20. and displays them on the user interface for the outbound delivery order. which controls the processing of a warehouse task in EWM.. To do this.07. such as in the field Corr. Here you can find the settings from Customizing. on the SAP Easy Access screen. Display an outbound delivery order in the form view. In accordance with the warehouse tasks. 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 Customizing. At header level. ● In the case of inbound deliveries. On the SAP Easy Access screen. 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. If warehouse activities (follow-on activities) have already begun for inbound deliveries. 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. in Customizing for Extended Warehouse Management. For example. EWM rejects the message from the ERP system. EWM rejects change messages from the ERP system.SAP Online Help 20. For more information. choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order or Maintain Outbound Delivery.07. EWM has also already set the status type Warehouse Activities to the status value Partially Completed. In the case of outbound deliveries. Neither you or the system have assigned a wave [Seite 771] to the delivery item in the document. check whether the staus type Locked (Overall Status) has the status value No. ● ● ○ ○ SAP Extended Warehouse Management (SAP EWM) 510 119 . The status type Locked (Overall Status) has the status value No in the document. you have assigned the defined action profile to a document type. see the Implementation Guide (IMG) for Extended Warehouse Management under Goods Receipt Process → Inbound Delivery → Define Document Types for Inbound Delivery Process Using Wizard.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. choose Extended Warehouse Management → Delivery Processing → Inbound Delivery → Maintain Inbound Delivery Order. On the SAP Easy Access screen. To do so. In doing so. If warehouse activities (follow-on activities) have already begun for inbound deliveries. 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. At item level. choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order or Maintain Outbound Delivery. EWM uses inactive and active document versions for this. choose Cross-Process Settings → Delivery Processing → Actions → Change Actions and Conditions → Define Action Profile and Actions. EWM has already created a warehouse task (WT) for an inbound delivery. At item level. check whether the status type Warehouse Activities has the status value Not Started. the status type Warehouse Activities has the status value Not Started in the document. or under Goods Issue Process → Outbound Delivery → Define Document Types for Outbound Delivery Process Using Wizard. EWM can only accept a reduction of the quantity from the ERP system. You do this in Customizing for the PPF in the action profile in EWM. On the SAP Easy Access screen. Select the action profile for an inbound delivery notification (/SCDL/IDR) or for an outbound delivery request (SCWM/ODR). check whether the status type Warehouse Activities has the status value Not Started for the respective delivery item.

The active inbound delivery notification IDN corresponds to the active inbound delivery ID in EWM that contains the unchanged quantities. EWM automatically activates the inactive document. To do so. You create a new document (for example. EWM creates the active successor document.07. If EWM cannot perform the PPF action due to an error. on the SAP Easy Access screen. the inactive document is either activated by you or by EWM. an inactive inbound delivery notification or an inactive outbound delivery request. You can manually activate and save these. If you have not determined document type 3 Immediate Processing in the PPF Customizing settings in the action profile in EWM. EWM accepts the message from the ERP system. an inbound delivery) in the ERP system and you save it. b. Accepting Inbound Delivery Changes to ERP Documents in EWM . 1. If EWM has not yet carried out any changes for the active document (that is. Outbound Delivery → Maintain Outbound Delivery Request and the Activate pushbutton. EWM carries out one of the following options: a. 3. choose Extended Warehouse Management → Delivery Processing and then one of the following options: ■ ■ Inbound Delivery → Maintain Inbound Delivery Notification and the Activate pushbutton. In other words.. on the SAP Easy Access screen. The ERP system notifies EWM to replace the inactive inbound delivery. To do so. Outbound Delivery → Maintain Outbound Delivery Request and the Activate pushbutton. 1. EWM creates an inactive inbound delivery notification for an existing active inbound delivery notification. 2. you change the quantity and save this change. The ERP system creates a new document with a temporary document number. 3. EWM always creates an inactive document. You can manually activate and save these.. As a result of this activation. For example.2007 Process Creating New Documents in EWM . the following is either performed by you or by EWM. Depending on your Customizing settings for the PPF. the status type Warehouse Activities still has the status value Not Started). for example. Depending on your Customizing settings for the PPF. in other words. 4. EWM creates a corresponding inactive document for the existing document.. The ERP system informs EWM of this and EWM creates a corresponding inactive document. a. choose Extended Warehouse Management → Delivery Processing and then one of the following options: ■ ■ Inbound Delivery → Maintain Inbound Delivery Notification and the Activate pushbutton. If you determined document type 3 Immediate Processing in the PPF Customizing settings in the action profile in EWM. EWM automatically activates an inbound delivery notification IDN and creates an active inbound delivery ID. for example. The inactive document has the same document number as the existing active document. EWM creates an inactive document.SAP Online Help 20. EWM copies the changes to the active SAP Extended Warehouse Management (SAP EWM) 510 120 . an inbound delivery notification IDN. You change an ERP inbound delivery. 2..

For example. 4. → Goods Issue Process → processing checked deliveries.2007 document. If necessary. EWM informs the ERP system of the rejection or acceptance. EWM does not copy the changes to the active document. EWM does not create a corresponding inactive document (in other words.07. an inactive outbound delivery request) for the existing active document in the case of outbound deliveries. or it cannot carry out the quantity change from the ERP system. EWM rejects the message from the ERP system.. b. the quantity of an order is reduced and SAP CRM sends this quantity change to the ERP system. 5. Accepting Outbound Delivery Changes to ERP Documents in EWM . The ERP system then sends the quantity change to EWM. For more information about document control and processing checked deliveries in the ERP system. EWM copies the quantity reduction to the active document. 5.. EWM does not copy the quantity reduction to the active document. If EWM has already carried out changes for the inactive document. 1. EWM rejects the change message from the ERP system. EWM carries out one of the following options: a. b. 2. For example. EWM informs the ERP system of the rejection or acceptance. EWM activates an inactive inbound delivery notification with a quantity change from the ERP system. 3. In SAP Customer Relationship Management (SAP CRM). or it cannot carry out the quantity reduction from the ERP system. The ERP system deletes the temporarily created ERP document number again. 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. If EWM has not yet carried out any changes for the active document (that is. If EWM has already carried out changes for the inactive document. 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. the ERP system changes its outbound delivery in accordance with the message. 6. EWM does not copy this change to the active inbound delivery. In contrast to inbound delivery cases. SAP Extended Warehouse Management (SAP EWM) 510 121 . EWM copies the quantity changes to the inbound delivery. that is. the status type Warehouse Activities still has the status value Not Started). EWM accepts the message from the ERP system. the inactive inbound delivery notification overwrites the active inbound delivery notification. and the other prerequisites for outbound delivery cases apply (see ‘Prerequisites’).SAP Online Help 20. If you now make another change to the inbound delivery in the ERP system.

as a goods movement message to SAP R/3. As a result. Integration EWM sends the posting change which it executes for the internal stock transfer. Replenishment [Seite 126].07. see Ad Hoc Movement [Seite 125]. it does not contain any delivery-based reference documents in other systems (for example. or Warehouse Reorganization [Seite 127]. SAP R/3). and warehouse reorganization in EWM. For more information about warehouse-internal functions. After completion of the process. SAP Extended Warehouse Management (SAP EWM) 510 122 . Structure For the structural description of a warehouse request. EWM informs the connected systems about the process execution. You or EWM indicate these storage bins when creating warehouse requests.SAP Online Help 20. Since you can only use this document within the warehouse. Your processes in this case are only visible within the warehouse. You execute the internal stock transfer directly from storage bin A to storage bin B without an intermediate stop (such as packing station).2007 Warehouse Request for Internal Stock Transfer Definition This warehouse request defines all warehouse-internal goods movements in Extended Warehouse Management (EWM). see Warehouse Request [Seite 109]. replenishments. there is one picking and putaway bin for every internal stock transfer. Use You use this document to plan your warehouse process for ad hoc movements.

When the wave is released. SAP Extended Warehouse Management (SAP EWM) 510 123 . EWM also blocks the necessary stock of the product as late as possible.. Either you create a warehouse request manually in EWM using the user interface. which reduce the planned open quantity for internal goods movement and block the product.07. 1. 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 . EWM creates the corresponding warehouse tasks (WTs). When EWM creates WTs. By creating WTs as late as possible. 2.2007 Internal Stock Transfers Purpose With this warehouse process.. or EWM does this automatically. it simultaneously determines from which stock it fulfills the warehouse request.SAP Online Help 20.

Quantity offsetting takes these into account. and closed the corresponding warehouse request. you specify process codes for the difference quantities. 4. The quantity offsetting notifies you at the same time that the open quantity is zero. EWM closes the warehouse request if one of the following options applies: ○ 20.07. 5. However. EWM updates the warehouse request. They therefore contain a putaway and picking step at the same time. SAP Extended Warehouse Management (SAP EWM) 510 124 . is omitted. You process the WTs and confirm them. EWM has created. Result You have executed an internal stock movement. for example. WTs for warehouse-internal processes move products from one storage bin to another. ○ The quantity reduced by the confirmed WTs does not represent the target quantity of the warehouse request. updated.SAP Online Help 3.2007 The reduced quantity [Extern] represents the target quantity of the warehouse request. whereas the process step Load.

water damage) to another storage bin. SAP Extended Warehouse Management (SAP EWM) 510 125 . You can use this warehouse request in a wave. Alternatively. Here you execute the stock movement immediately and without a warehouse request. for example. transfer a product damaged in the storage bin (for example. On the SAP Easy Access screen. you can immediately create a warehouse task. On the SAP Easy Access screen. you can create a warehouse request. choose Extended Warehouse Management → Work Scheduling → Create Warehouse Task Without Reference → Move Product. on the SAP Easy Access screen. See also: Ad Hoc Movement [Seite 415] Activities You create warehouse requests for ad hoc movements manually through a user interface.07. Then choose Create (Create Warehouse Request) instead of Create (Create Warehouse Task). ● An ad hoc decision together with an ad hoc movement that triggers the creation of a WT with immediate.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. Once Extended Warehouse Management (EWM) has created the corresponding warehouse task (WT). choose Extended Warehouse Management → Delivery Processing → Maintain Internal Stock Transfer. In the case of a spontaneous decision for a planned stock movement. Features You can.SAP Online Help 20. choose Extended Warehouse Management → Delivery Processing → Maintain Internal Stock Transfer. In the case of a spontaneous decision for an immediate stock movement. automatic confirmation. EWM transfers these storage bins during WT creation. To do this. you create a manual warehouse request that sets the picking and putaway storage bin. you can execute the stock movement.

see the relevant report documentation. choose Program Documentation to see the report documentation. On the SAP Easy Access screen. For more information about executing replenishments. on the SAP Easy Access screen. SAP Extended Warehouse Management (SAP EWM) 510 126 . choose Extended Warehouse Management → Work Scheduling → Schedule Replenishment. For replenishment planning in the dialog. on the SAP Easy Access screen. Features When creating warehouse requests. you can use this warehouse request to schedule several replenishments in waves. choose Extended Warehouse Management → Delivery Processing → Maintain Internal Stock Transfer. On the Execute Replenishment screen that follows.07. This ensures that you do not fall short of a picking bin’s minimum quantity. Activities To retroactively change a warehouse request for replenishment. Replenishment fills picking bins from the reserve storage area. Furthermore. EWM specifies possible picking bins and final putaway storage bins.SAP Online Help 20. You can change warehouse requests for the replenishment retroactively.2007 Executing a Replenishment Use You can use this function for warehouse-internal replenishment planning. EWM checks the picking bins again before it uses them as final picking bins in the warehouse task. only execute replenishments at night. and to plan the execution of replenishments separately from the requirements. for example. Extended Warehouse Management (EWM) creates this warehouse request with a background job or you can execute the replenishment planning in the dialog. choose Extended Warehouse Management → Work Scheduling → Schedule Replenishment.

Extended Warehouse Management (EWM) uses a warehouse order to reorganize your stock. on the SAP Easy Access screen. Since EWM uses a warehouse request for the warehouse reorganization. EWM uses the results of the storage bin determination within the wave determination. Activities To create this warehouse request. choose Extended Warehouse Management → Work Scheduling → Warehouse Reorganization. SAP Extended Warehouse Management (SAP EWM) 510 127 . Here. you can plan your reorganization and start it in a wave. which does not make a reservation.07.2007 Executing a Warehouse Reorganization Use You use this function to optimize the access paths within your warehouse.SAP Online Help 20. Features EWM executes a temporary storage bin determination.

Use The warehouse request for posting changes [Extern] is a document that you use in EWM for the following: ● ● For planned posting changes. in other words without using a warehouse request. Planned posting changes. such as a scrapping request. without reference to a posting change request. choose Extended Warehouse Management → Delivery Processing → Posting Change → Maintain Posting Change. choose Extended Warehouse Management → Work Scheduling → Make Posting Change for Product. on the SAP Easy Access SAP Extended Warehouse Management (SAP EWM) 510 128 . In other words. SAP R/3 sends a delivery output to EWM. For unplanned posting changes. if you want to execute a posting change from unrestricted-use stock to blocked stock. For example. if you have confirmed the WTs Manually by you in the user interface If you want to create a posting change manually. for a process triggered inside the warehouse. with reference to a posting change request. Integration You or SAP R/3 trigger the posting change externally.SAP Online Help 20. for a process triggered outside the warehouse. In the transaction. You can also create posting changes directly. see Interfaces for Communication from EWM to the ERP System [Seite 257].2007 Warehouse Request for Posting Changes Definition This warehouse request defines the changes in stock categories of a product in Extended Warehouse Management (EWM). without using a warehouse request. SAP R/3 triggers this when it sends a delivery output to EWM. on the SAP Easy Access screen. If you want to create a posting change directly. on the SAP Easy Access screen. EWM creates a WT for this stock transfer. You can detect this in the goods movement status of the warehouse request. which are based on a warehouse request. In other words. If EWM has not executed the posting change. EWM then creates a posting change request. a physical stock transfer may also be necessary due to the warehouse structure. Structure For the structural description of a warehouse request. EWM can execute the posting change directly upon creation of a warehouse request for a posting change. For more information. such as a scrapping request. In this case. the posting change is executed in one of the following ways: ● ● Automatically by EWM through a PPF action.07. If you want to view the goods movement status to check the posting changes created directly upon warehouse request creation. choose the function to create a posting change. see Warehouse Request [Seite 109]. can also have an associated warehouse task (WT) for a posting change.

2007 screen.SAP Online Help 20. SAP Extended Warehouse Management (SAP EWM) 510 129 . Goods Movement. choose Extended Warehouse Management → Delivery Processing → Posting Change → Maintain Posting Change and then Status.07.

A warehouse worker in the quality department can use an inspection procedure to carry out the decision to scrap a product. EWM sends a goods movement message. inspection lots. and inspection results. you create a warehouse request for the posting change. This represents a GI posting without delivery. EWM can execute the goods issue with or without the corresponding outbound delivery document. EWM posts the quantity to be scrapped as blocked stock.07. or warehouse-externally. Integration Only scrapping triggered outside the warehouse. For scrapping triggered inside the warehouse. You can trigger the scrapping warehouseinternally in EWM. This represents an internal stock movement that is triggered by the following: ○ ○ ● Warehouse-internal decision. Extended Warehouse Management (EWM) sends a delivery output to the ERP system. From there. for example with SAP Customer Relationship Management. ● Activities ● You move the products to be scrapped from the different storage bins to a scrapping handling unit (scrapping HU). You book the goods issue (GI) for the scrapping HU.SAP Online Help 20. EWM sends the following to the ERP system: ● ● If you are using SAP ERP 2007.2007 Performing Scrapping Use You can use this function in the following scenarios: ● ● Scrapping within the warehouse. Features ● For warehouse-internal processing of products to be scrapped. Based on the inspection results. you can clear the products through goods issue. EWM uses a warehouse request for the posting change for this step. The system thus posts the products to the blocked stock. For these types of scrapping. In other words. it carries out a posting change. EWM processes the scrapping in the returns process with a returns delivery. is related to a preceding document (delivery request document). 510 130 ● SAP Extended Warehouse Management (SAP EWM) . If you are using an older SAP ERP release. he or she can decide whether a product is still to be used or should be scrapped. defective or obsolete product) Scrapping within a returns process Here you can process warehouse-internal or warehouse-external decisions to scrap a product. EWM can execute the GI with the corresponding outbound delivery document. for example. such as from the ERP system. EWM can also execute the GI without a corresponding outbound delivery document. You can use this warehouse request for the posting change during wave creation. EWM sends a delivery message. by a warehouse worker in the quality department Warehouse-external decision when a scrapping message is sent At the same time. if a product is to be disposed of from the warehouse (for example.

07.2007 SAP Extended Warehouse Management (SAP EWM) 510 131 .SAP Online Help 20.

SAP Online Help 20. ● ● ● ● ● Putaway [Seite 300] Scrapping [Seite 130] Transferring Delivery to internal remanufacturer Delivery (to customer or external remanufacturer) You cannot change returns deliveries that. SAP Customer Relationship Management sends to EWM. for example. see also Goods Receipt [Seite 263]. In doing so. The external system controls the returns process and determines which items in which quantities the customer can send back. 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. On the SAP Easy Access screen. SAP Extended Warehouse Management (SAP EWM) 510 132 .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). you can immediately reject the inbound delivery. if you determine that the forwarding agent does not need to unload the goods. Use The warehouse request for returns in EWM forms the basis for executing follow-up activities.07. rather can take the goods right back with it because the goods are damaged. for example. 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. choose Extended Warehouse Management → Delivery Processing → Inbound Delivery ○ ○ → Maintain Inbound Delivery Notification and then Reject → Maintain Inbound Delivery and then Reject For more information. In particular.

Putaway. SAP Extended Warehouse Management (SAP EWM) 510 133 .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. such as putaway or returning to the customer. such as putaway. you can only put returns away after the last inspection has been carried out. After this. These date/time types determine whether EWM accepts or rejects returns. ● If you carry out a step-by-step inspection in multiple warehouses. EWM sets the status type Blocked QM f. based on the inspection results SAP CRM determines whether SAP CRM or EWM is to determine followup activities. You can carry out stock transfers in the warehouse during the whole process. makes a usage decision. EWM automatically triggers the corresponding logistical processes. SAP CRM determines the date and time fort he external and internal validity of the returns and sends this data to EWM. then you carry out an individual inspection for each warehouse. The step-by-step inspection does not affect delivery processing. for example. However. ○ EWM adopts the effective dates/times from SAP CRM. then EWM must first send the inspection result to SAP CRM. the returns stock is blocked from further use until an external system. ■ Control the follow-up activities. If the external date/time type has expired. If the current warehouse is not the last warehouse in the sequence. see Warehouse Request [Seite 109]. SAP CRM determines the follow-up activity and sends it to EWM. The status type Blocked After QM specifies that following the quality inspection. 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. 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. SAP CRM determines the follow-up activities and decides whether or not to reject the returns. EWM triggers the corresponding logistical processes. Thus. SAP CRM. EWM adopts this decision. ● If status type Blocked According to QM is not set in EWM. EWM rejects the returns. you can scrap or send returns back after each individual inspection. EWM maps this with status type Blocked According to QM. If status type Blocked According to QM is set in EWM. ■ ■ If both date/time types have expired.SAP Online Help ○ 20. you can determine the follow-up activity in EWM. For the structural description of a warehouse request. but the internal date/time type is still valid.07.

EWM sends the inspection result to SAP CRM. It sends a delivery notification to EWM. EWM then creates a warehouse request for returns. In addition.07. SAP Extended Warehouse Management (SAP EWM) 510 134 . and saves the inspection results in the warehouse request for returns.2007 Integration SAP CRM triggers the returns. EWM conducts inspection planning with quantity offsetting.SAP Online Help 20.

2007 Processing. and Archiving Warehouse Requests Use You can process.07.SAP Online Help 20. such as an ERP system. delete. Deleting. For an inbound delivery notification or outbound delivery request created automatically. Features The following table gives you an overview of the functions you can execute for the individual warehouse requests. Scrapping) Automatically Manually Manually The inbound delivery notification [Seite 87] and outbound delivery request [Seite 90] created automatically are messages from a sending system. or archive warehouse requests. 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 X X Automatically ------ X 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. You cannot process or delete these messages. Object for which EWM creates a warehouse request Create (manually by user. you can only activate or reject the document. SAP Extended Warehouse Management (SAP EWM) 510 135 .

completely packed). Features Goods Receipt Process During goods receipt posting (GR posting). it uses the HU information from the inbound delivery notification. partially packed. The following figure shows an example GI posting process for cross-delivery handling units. The handling unit has a reference to the delivery. You post the GI for every delivery separately. delivery processing posts the GI automatically for all associated deliveries. To do so. Delivery processing updates these quantities during inbound 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. You can post the goods receipt (GR) in delivery processing completely or partially. Prerequisites The mapping of HU data from SAP R/3 to EWM must be defined. EWM simultaneously creates inbound deliveries and HUs in HU management. This means that EWM automatically creates HUs that have been defined in the ERP system. Goods Issue Process You can only post the goods issue (GI) on delivery basis completely. If the Cross-Delivery indicator is set in the data for a cross-delivery handling unit. EWM determines the packed quantity from the handling unit information.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). delivery processing determines which products exist in which quantities in the handling unit warehouse task.07. SAP Extended Warehouse Management (SAP EWM) 510 136 . unpacked. A partial GI posting is not possible. Delivery processing sets a status for the packed quantity (for example. If this forwarding is incorrect or incomplete.SAP Online Help 20. errors occur in delivery processing.

change.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. on the SAP Easy Access screen. Activities If you want to view HU data for the inbound delivery. delivery processing automatically posts the GI for HU1 as well. On the SAP Easy Access screen. SAP Extended Warehouse Management (SAP EWM) 510 137 . it is also relevant for Delivery2. If you post the GI for HU2. choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Process Outbound Delivery. since it only posts one GI for the complete delivery. choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Process Outbound Delivery Order.07. or select HU1 and 2 and post the GI. If Delivery2 contains a HU3 that is also cross-delivery. If you want to view. choose one of the following options: ● ● On the SAP Easy Access screen. You must either post a GI completely for both deliveries using the selected delivery headers for Delivery1 and 2. you will get an error message. HU2 is cross-delivery. or delete HU data for the outbound delivery. choose Extended Warehouse Management → Delivery Processing → Inbound Delivery → Process Inbound Delivery.SAP Online Help 20. In other words.

Outbound Delivery or Posting Change. On the SAP Easy Access screen. 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. SAP Extended Warehouse Management (SAP EWM) 510 138 . and then the required user interface.07.SAP Online Help 20.2007 User Interfaces in Delivery Processing Use The following user interfaces are available in Extended Warehouse Management (EWM) for the purpose of processing deliveries. choose Extended Warehouse Management → Delivery Processing → Maintain Internal Stock Transfer.

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 .07.SAP Online Help 20.

This BAdI calculates an aggregated priority at header level. EWM creates an inbound delivery request.SAP Online Help 20. EWM or you activate the inbound delivery request. Based on the notification. under Extended Warehouse Management → Delivery Processing → Inbound Delivery → Update Priority Points.. 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. SAP Extended Warehouse Management (SAP EWM) 510 140 . EWM updates the priority points in the inbound delivery and aggregates the priority points at transportation unit level. 4. EWM creates an inbound delivery from the active inbound delivery request. For more information. b.. SAP APO sends the result of this recalculation to EWM via the ERP system. As with the first calculation (step 4). SAP APO communicates the calculated priority points to the ERP system. The ERP system receives an advanced shipping notification (ASN) and creates an inbound delivery. EWM triggers an asynchronous request for the recalculation of priority points in SAP APO via the ERP system. The ERP system notifies SAP APO and EWM about this. EWM updates the inbound delivery until the Warehouse Activities Status is Completed. EWM has updated priority points in the inbound delivery. 1. EWM aggregates the priority points at transportation unit level using the BAdI /SCWM/EX_SR_PRIOP.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. see the report documentation. 6. Provided the Warehouse Activities status is not Completed. EWM calls the Business Add-In (BAdI) /SCWM/EX_DLV_DET_LOAD to display the inbound delivery. You can see this on the user interface for unloading. 2. EWM saves the priority points for an inbound delivery at item level. You can start the report /SCWM/PRIOP_UPDREQ for the recalculation of priority points from the SAP Easy Access display. EWM updates the priority points in the inbound delivery. Process .07. the system executes the following: a. 5. which then communicates them to EWM. 3. SAP APO calculates the priority points at item level. At the same time. Results SAP APO has calculated the priority points and has communicated this to EWM via the ERP system .

If EWM cannot find a printer in step 2. ● If appropriate. SAP Extended Warehouse Management (SAP EWM) 510 141 . you have defined a print profile in the default values. you have implemented your own printer determination in Business AddIn (BAdI) /SCDL/PPF_ADD_DATA in method GET_PRINTER. see the BAdI documentation. For more information. you have defined one or more print profiles in Customizing for EWM.07. For more information. 2. For more information. 3. choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Pickup. 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. 1. For more information. ● ● ● Process EWM attempts to determine the printer in the following sequence: . 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. it checks whether you have implemented your own print profile determination in BAdI /SCWM/EX_DLV_PRINT_PROFILE. Choose Default Values and enter a print profile. for example. on the SAP Easy Access screen. To do so. it uses the name of the printer from this print profile. EWM checks whether you have specified a print profile in the default values on the user interface for pickup. If so. EWM uses the printer from this print profile. For more information. ● You have defined print profile determination for the goods receipt process or goods issue process in Customizing for EWM. If so. you have defined one or more Post Processing Framework (PPF) actions in Customizing for the PPF. see the BAdI documentation. If appropriate. Prerequisites ● If appropriate. If appropriate. If EWM cannot find a printer in step 1.. If appropriate. 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.. it checks whether you have implemented your own printer determination in BAdI /SCDL/PPF_ADD_DATA.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. you have implemented your own print profile determination in BAdI /SCWM/EX_DLV_PRINT_PROFILE. 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. it uses this printer.SAP Online Help 20. in the goods receipt area or goods issue area.

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

● By default. You can display a preview of the delivery note before printing it. Activities You have the following options for printing or displaying delivery notes manually: ● . choose Extended Warehouse Management → Work Scheduling → Print → Process and Display PPF Actions.. EWM automatically prints the delivery note for an outbound delivery as soon as you have posted the goods issue. For more information about action conditions. see EH&S Services [Seite 967]. Prerequisites You have created either an outbound delivery order or an outbound delivery. see the SAP Library under SAP NetWeaver Library → SAP NetWeaver by Key Capability → Application Platform by Key Capability → Business Services → Smart Forms. Printing or displaying directly using a PPF action a. On the SAP Easy Access screen.07. EWM issues the dangerous goods data when printing the delivery note.2007 Printing Delivery Notes Use You use this function in Extended Warehouse Management (EWM) to print delivery notes. For more information about form determination. Select the line of the required PPF action (/SCWM/PRD_OUT_PRINT or /SCWM/FD_OUT_PRINT). For more information about dangerous goods data. EWM uses the predefined SAP Smart Form /SCWM/DLV_NOTE. see the Implementation Guide (IMG) for EWM under Extended Warehouse Management → Cross-Process Settings → Delivery Processing → Actions → Change Actions and Conditions → Define Conditions. you must change the assigned processing of the PPF action from Smart Forms Print to External Communication in Customizing for EWM.SAP Online Help 20. Specify the document number in the Application Key field. you can also create your own SAP Smart Form to use when printing the delivery note and for form determination. You can also use a PPF action to manually print a delivery note for an outbound delivery or outbound delivery order. However. You can also print delivery notes using a PDF-based form. Choose Execute. In doing so. EWM uses detailed information about the route and means of transport to determine the relevant dangerous goods master records. SAP Extended Warehouse Management (SAP EWM) 510 143 . 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.. d. To do this. c. see the IMG for EWM under Extended Warehouse Management → Goods Issue Process → Outbound Delivery → Print → Determine Form Determination for Delivery Note Printing. b. ● For more information about Smart 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. Save your entry. choose External Communication. PPF actions with the status Unprocessed have not been processed yet. Printing or displaying from the user interface of the delivery a. e. Execute Action. ● .. Preview. unprocessed print action. In the Processing Selection group box on the Processing Details tab page. 2.2007 e. choose EWM displays the document. Proceed as follows: ■ ■ If you want to display the document. EWM prints the document. Enter the required document number.07. You can only process a PPF action once from within the user interface of the delivery. On the SAP Easy Access screen. 5. Example of Switching from Smart Form Print Forms to PDF-Based Print Forms ..SAP Online Help 20. SAP Extended Warehouse Management (SAP EWM) 510 144 . If you want to print the document.. select the assigned processing Smart Forms Print and delete it. Switch to change mode and make sure that the setting Default Settings from Action Definition is not selected in the Action Definition group box. 4. 3. Choose Change to switch to change mode. 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. Under Available Processings. Choose the PPF Actions tab page and select the required action (Print Outbound Delivery Order or Print Outbound Delivery). you can choose Repeat Action to generate and then process a new. f. c.. If you have already processed the PPF action once. Choose Process. d. choose EWM prints the document.

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 can create and save new texts for a particular delivery. ● 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.07.SAP Online Help 20. 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.2007 Text Management Use With this function. For example. Prerequisites You have made the Customizing settings for text management [Extern]. assign the text type packing text to the delivery header. You have assigned one of the text types to the text objects (such as delivery header. For more information about defining text types. ● You have defined text types [Extern]. delivery item) delivered by SAP. you can do the following to texts belonging to deliveries: ● ● ● ● Display Change Save Delete In addition. For more information about Customizing the document or item types for the goods issue process. For more information about Customizing the document or item types for the goods receipt process. see the Implementation Guide (IMG) for EWM under SAP Extended Warehouse Management (SAP EWM) 510 145 . see the IMG for EWM under Cross-Process Settings → Delivery Processing → Text Management → Define Text Profiles with Access Sequences. 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. You can create texts in external systems (such as SAP CRM) and send them with the document via the ERP System to SAP EWM. This message also contains the data (including existing texts) for this delivery.

To process existing texts or create new ones in SAP EWM. choose Extended Warehouse Management → Delivery Processing → Inbound Delivery → Maintain Inbound Delivery Notification or Maintain Inbound Delivery For the goods issue process. select one of the following: ● For the goods receipt process.. Features Text management supports texts: ● At header level For example.. In SAP EWM. 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. change. on the SAP Easy Access screen. ● At item level For example. Only there can you also create and save new texts directly. on the SAP Easy Access screen. For more information about the connection between documents and services. choose Extended Warehouse Management → Delivery Processing → Posting Change → Maintain Posting Change Request or Maintain Posting Change ● ● SAP Extended Warehouse Management (SAP EWM) 510 146 . choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Notification or Maintain Outbound Delivery For posting changes. or delete texts belonging to deliveries. on the SAP Easy Access screen.2007 Goods Issue Process → Outbound Delivery → Manual Settings → Define Document Types for Outbound Delivery Process or Define Item Types for Outbound Delivery Process. you can display.07. Activities . 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.SAP Online Help 20. such as text management. see Delivery Processing [Seite 81].

you can record physical delivery quantity difference in the inbound delivery for the outbound delivery order or the posting change delivery. For more information. you have defined them in Customizing EWM. For more information. loss. product group type. For more information. Under Allowed Quantity Increase. you have not defined A Quantity Increase Not Allowed. That is. Prerequisites ● If you adjust the delivery quantity manually in the user interface of the delivery. you have assigned the process codes to your own process code profiles in Customizing for EWM. ■ SAP Extended Warehouse Management (SAP EWM) 510 147 . you have assigned the process code profiles to the used document types and items types in Customizing for EWM. you have not defined B Special Authorization Required to Increase Quantity. for example.07.SAP Online Help 20. see the IMG for EWM under CrossProcess Settings → Delivery Processing → Process Codes → Define Process Codes. Delivery quantity differences can result from damage. or expiration of the shelf life data. meaning that the quantity increase is generally not allowed for the party entitled to dispose. see the IMG for EWM under Interfaces → Availability Check → Define Configuration of Availability Check. 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. meaning that the user who wants to execute the quantity increase requires authorization for activity 94 (Override) for authorization object /SCWM/DLV. For more information. it has either status value Not Started or Partially Completed. the following prerequisites apply: ○ A delivery exists in EWM. ■ Under Allowed Quantity Increase. item type. you have not defined any of the following restrictions for the quantity increase in Customizing for EWM. If required. see the IMG for EWM under Cross-Process Settings → Delivery Processing → Process Codes → Maintain Process Code Profiles. If you want to use your own process codes.2007 Delivery Quantity Adjustment Use In Extended Warehouse Management (EWM). and product group. If required. which has a status value at item level for status Completion that allows delivery quantity adjustment.

see the IMG for EWM under Interfaces → ERP Integration → Delivery Processing → Map Partner Roles from ERP System to EWM. packing. meaning EWM matches the delivery quantity to the largest of these quantities. the partner you define here corresponds to the person who caused the delivery quantity difference. you can define one of the following types for the delivery quantity adjustment: ● ● ● EWM does not adjust the delivery quantity. If you record quantity differences for stock transfer orders [Seite 150] for example.07.2007 If you still choose this setting. and planned putaway. For more information. you must also have defined exception codes in Customizing for EWM and assigned them to the process codes.SAP Online Help 20. 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 . although EWM saves a process code in the delivery that you can also view in the respective user interface of the delivery. For both types of delivery quantity adjustment. meaning EWM matches the delivery quantity to this quantity. For more information. ● If you adjust the delivery quantity using an exception code for an automatic delivery update. to ERP. ● ● In Customizing for the process code. EWM also saves a process code in the delivery. In the outbound delivery order. EWM adjusts the delivery quantity and saves a process code in the delivery. EWM considers the quantity for planned internal movements. For both types of delivery quantity adjustment.since these involve internal warehouse differences. ● ● Features EWM considers the following quantities for delivery quantity adjustment: ● In the inbound delivery. and planned picking. For more information. you have also defined in Customizing for EWM the partners for which EWM reports exceptions. EWM adjusts both the delivery quantity and the transferred delivery quantity. refer to the IMG for EWM under Cross-Process Settings → Exception Handling → Define Exception Codes. EWM considers the quantities for loading. Activities You can adjust delivery quantities in one of the following ways: ● On the SAP Easy Access screen. EWM considers the quantities for goods receipt. In the posting change delivery. meaning EWM performs a delivery split in the goods receipt process or goods issue process. you must assign authorization for activity 94 to the corresponding user for authorization object /SCWM/DLV. 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. The only information EWM does not send to ERP is information about delivery quantity differences for posting change deliveries. EWM saves delivery quantity differences for this partner and sends the information to the ERP system. packing. see Delivery Split for Inbound Deliveries [Seite 154] and Delivery Split for Outbound Deliveries [Seite 156]. namely process codes. meaning EWM matches the delivery quantity to the largest of these quantities.

This triggers a quantity adjustment for the transferred delivery quantity in the document flow to 90 pieces. meaning that EWM generates another inbound delivery using the difference quantity of 10 pieces. corresponding to the settings you have made in Customizing.General. you have defined the work center layout in the IMG for EWM under Master Data → Work Center → Specify Work Center Layout. If you are confirming a warehouse task or recording counting.SAP Online Help ○ ● Posting Change → Maintain Posting Change. to specify an exception code. 20. You record the difference and specify an exception code. EWM adjusts the inbound delivery quantity to 90 pieces. you have defined an adjustment for both the delivery quantity and the transferred delivery quantity. on the SAP Easy Access screen choose Extended Warehouse Management → Execution → Confirm Warehouse Task or Execution → Quality Inspection and Count. on the SAP Easy Access screen choose Extended Warehouse Management → Execution → Packing . since 10 pieces are defective. EWM maps this exception code to the relevant process code in the background and updates the delivery. EWM assigns this exception code to a process code. For this. The document flow also carries a quantity of 100 pieces. EWM then uses the delivery update to adjust the delivery quantity for each item. EWM generates an inbound delivery with an inbound delivery quantity of 100 pieces. ● Example Delivery Split in the Goods Receipt Process EWM generates an inbound delivery notification for 100 pieces. then EWM displays the tab page Differences. If you have defined the work center correspondingly in Customizing for EWM.2007 You adjust the delivery quantity manually in the user interface of the delivery. and a delivery split in the goods receipt process. corresponding to the settings of the process code.07. SAP Extended Warehouse Management (SAP EWM) 510 149 . If you are repacking delivery stock. In the user interface of the inbound delivery. In Customizing for the process code. you specify that EWM is to adjust the inbound delivery quantity to 90 pieces.

In the physical inventory. you can confirm quantity excesses or shortages that were caused by the first cross -docking warehouse and not the delivering warehouse. ● You have assigned the user to a tolerance group for the Difference Analyzer in the Customizing settings for EWM. If you are unable to execute clearing. In the Difference Analyzer.SAP Online Help 20. You receive a quantity shortage or quantity excess in the inbound delivery. which was caused by a delivering warehouse. the delivering warehouse has not loaded a pallet onto the vehicle. you perform an adjustment posting directly in the ERP system. central SAP Advanced Planning & Optimization (SAP APO) for the automatic generation of stock transfer orders.07.2007 Quantity Differences for Stock Transfer Orders Purpose In Extended Warehouse Management (EWM). If a carrier caused a quantity excess or shortage. 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. This enables you to map the following processes: ● You receive a quantity shortage or quantity excess in the inbound delivery. you always post these differences at the kit header. You are using interfaces between EWM and 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. If the kit itself is not available in the source warehouse. To do so. on the SAP Easy Access screen. and at least one decentralized EWM. Prerequisites ● You are working in a system landscape that includes an ERP system. The customer only receives 9 pieces. In cross-docking [Seite 544]. you can execute clearing in the Difference Analyzer [Seite 677] between the receivable quantities and the difference quantities to be cleared. the ERP system sends a correction delivery to EWM in the source warehouse. see the SAP Help Portal for SAP ERP under SAP ERP Central Component → Logistics → Logistics . you can confirm stock transfer orders with a quantity difference. You have defined tolerance groups for the Difference Analyzer in the Customizing settings for EWM. you post the difference to the ERP system.General (LO) → Service Parts Management (LO-SPM) → Transfer and Inventory Management → Stock Transfers → Adjustment of Stock Transport Order Quantity Difference. you have to clear this difference by posting differences in the inventory quantity. you can offset the receivable quantity to be cleared with a difference quantity to be cleared. There. If quantity differences occur in connection with kits. For more information. for example. a carrier damaged the goods. which was caused by a carrier. if required. For more information. you find that one piece of product A is still in the goods issue area. ● ● If a source warehouse caused a quantity excess or shortage. rather the kit components only. for example. see Communication from EWM to ERP System [Seite 248]. choose ● ● SAP Extended Warehouse Management (SAP EWM) 510 150 . You post a correction delivery for one piece as a receivable quantity to be cleared. You deliver 10 pieces of product A.

You transport goods from one warehouse to another. You perform the required goods issue process steps and post the goods issue. the two EWM systems are referred to as EWM1 for the source warehouse and EWM2 for the target warehouse. EWM1 generates a relevant outbound delivery. EWM in the Source Warehouse ● You have defined document types for the correction deliveries in Customizing for EWM. For more information. 1. 6. EWM1 informs the ERP system about this. you have defined whether EWM is to execute an automatic or manual goods movement. It informs EWM1 of the source warehouse about this. The ERP system generates a corresponding stock transfer order and an outbound delivery for this.SAP Online Help 20. see the Implementation Guide (IMG) for EWM under Interfaces → ERP Integration → Delivery Processing → Define ERP Document Types for Differentiation Attribute. You have defined the mapping of the exception code to the process code of the delivery processing in Customizing for EWM.07. The ERP system generates a corresponding inbound delivery for EWM2 of the target warehouse. 3. For more information. . see the IMG for EWM under Interfaces → ERP Integration → Delivery Processing → Map Document Types from ERP System to EWM System. EWM finds these using the differentiation attribute DIS (discrepancy process) at header level. under Cross-Process Settings → Delivery Processing → Actions → Use Assistant to Create Actions.2007 Extended Warehouse Management → Settings → Physical Inventory → Assign User to Tolerance Group for Difference Analyzer. refer to the IMG for EWM under Cross-Process Settings → Exception Handling → Define Exception Codes. SAP Extended Warehouse Management (SAP EWM) 510 151 . 4. see the IMG for EWM. In the following.. ● You have defined the mapping of the document types from the ERP system in EWM in Customizing for EWM. use the delivered document types and item types and their relevant profiles as a basis. 2. EWM in the Target Warehouse ● In Customizing for EWM. It informs EWM2 about this. ● In Customizing for EWM. Make sure that the Customizing settings for EWM for your own document types and for the item types used are correct. ● 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 create a stock transfer order in SAP APO and SAP APO informs the ERP system about it. For more information. 5. You have also assigned partner roles to the process codes (see Delivery Quantity Adjustment [Seite 147]).. If you are defining your own profiles. you have defined process codes and assigned these to your own process code profiles. For more information.

you record quantity differences in the same way as for stock transfer orders. The unassigned stock remains in the ERP system. The ERP system posts the quantity differences in the proof of delivery. an outbound delivery for EWM1. EWM2 generates a corresponding inbound delivery. For example. You can reject goods receipt of the inbound delivery or goods issue of the outbound delivery in EWM1. 14. You have to then process it manually. Quantity Differences in Cross-Docking Unlike the standard process for stock transfer orders. 20.SAP Online Help 7. you attempt to offset the receivable quantities to be cleared with the difference quantities to be cleared in the Difference Analyzer. if you find a pallet in the physical inventory that has 10 pieces of a product. 10. 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. or process code PC2B to debit the source warehouse. You execute the goods receipt process steps up to goods receipt posting. For a quantity shortage. You transport goods from the source warehouse to the target warehouse via the CD warehouse. In EWM1. if you want to record a quantity shortage in CD warehouse 2. When posting goods receipt. 13. if necessary. 12.07. 8. You or a carrier transport the products to EWM2. in the cross-docking process (CD process) you work with at least three decentralized warehouses: the source warehouse. you post this as a difference quantity to be cleared. the cross-docking warehouse (CD warehouse) and the target warehouse. 11. The ERP system generates a correction delivery for EWM1 of the source warehouse. EWM1 generates an inbound or outbound delivery as a correction delivery. SAP Extended Warehouse Management (SAP EWM) 510 152 . It posts the quantity excess or shortage as a receivable quantity to be cleared (external quantity difference). In the cross-docking process. For example. When you record quantity differences. These warehouses are managed by EWM. EWM1 posts internal quantity differences from the physical inventory or warehouse task creation as difference quantities to be cleared. and for a quantity excess. the ERP system generates an inbound delivery for EWM1. EWM2 uses the process code to differentiate who caused the quantity excess or shortage (see Delivery Quantity Adjustment [Seite 147]). The following graphic illustrates these two options. EWM2 informs the ERP system about this. you identify a quantity excess or shortage. The ERP system informs EWM1 about this.2007 9. based on the notification. you can use process code PC2A to debit this quantity difference from CD warehouse 1. You post goods receipt with the quantity excess or shortage and specify a process code. 15.

07. 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 .. see Cross-Docking [Seite 544].2007 For more information about the cross-docking process.SAP Online Help 20..

choose Adjust Delivery Quantity for the selected delivery item and specify a process code. on the SAP Easy Access Screen choose Extended Warehouse Management → Delivery Processing → Inbound Delivery → Maintain Inbound Delivery. 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. If you want to work without a default process code. However. 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. EWM determines a process code according to your Customizing settings for delivery quantity changes. you know that this delivery item will arrive on another truck the next day. I002 Diff). which means that you require a delivery split. Either you or the system can split delivery items or partial quantities into a new delivery. see the Implementation Guide (IMG) under Extended Warehouse Management → Cross-Process Settings → Delivery Processing → Process Codes → Define Process Codes. if necessary. If necessary. EWM adjusts the delivery quantity and the transferred delivery quantity.SAP Online Help 20. You defined process code profiles. the default process code has the effect that EWM automatically adjusts the delivery quantities. for example. you only want to post delivery item 20 the next day. You can book GR for partial quantities.2007 Delivery Split for Inbound Deliveries Use A delivery split can be necessary in various business processes. For more information. For more information. you have chosen a default process code in the Customizing settings.07. you discover that delivery item 20 is missing. SAP Extended Warehouse Management (SAP EWM) 510 154 . while you are unloading a truck. Prerequisites ● You have defined process codes that adjust both the delivery quantity and the transferred delivery quantity [Extern]. see the IMG under Extended Warehouse Management → Cross-Process Settings → Delivery Processing → Process Codes → Maintain Process Code Profiles. If you choose the delivery item and manually change the delivery quantity in the user interface of the inbound delivery then. see the IMG under Extended Warehouse Management → Goods Receipt Process → Inbound Delivery → Manual Settings → Define Item Types for Inbound Delivery Process. For more information. To access the user interface. When you select the corresponding process code. The prerequisite for this is that you have not performed a warehouse activity for this delivery item or partial quantity. ● ● ● Features You can totally delete a delivery item or reduce the delivery quantity of a delivery item. Transferred for the quantity adjustment. EWM determines a default process code (for example. that is. meaning that you have only not yet carried out warehouse activities for the remaining quantity for which you are performing a delivery split. Quant. you have chosen the value 2 Adjustment of Delivery Quantity and Del. Document and Quantity. Therefore. if a planned inbound delivery arrives in two trucks instead of one. If Extended Warehouse Management (EWM) is to use a default process code (for example. Adjust Supplier. For example. For example. You have defined the item types for the inbound deliveries in which you assigned the corresponding process code profiles. you have not posted the goods receipt (GR) yet. /002) for quantity changes.

You specify the process code I002 Diff.2007 If you perform changes in an inbound delivery using a process code that automatically adjusts to the delivery quantity. on the Process Codes tab page. You save the delivery quantity change. 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 adjusts the delivery quantity and the transferred delivery quantity in accordance with your Customizing settings. choose Extended Warehouse Management → Delivery Processing → Inbound Delivery → Maintain Inbound Delivery Notification and then the Delivery Quantity pushbutton. you cannot set the quantity of this delivery item to zero. Adjust Supplier. Additionally. 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. 2. You can process the newly created inbound delivery as in the normal GR process [Seite 263]. If. for example. In the original inbound delivery. You can then post the GR. you can see (at item level) that EWM uses the process code I002 for the difference quantity of three pieces. a delivery item still has open warehouse tasks. See Also: Delivery Quantity Adjustment [Seite 147] Example Example for a Manual Delivery Split . a. EWM adjusts the delivery quantity and performs a delivery split. Document and Quantity. b.. c. During the save. for example.07. EWM creates a new inbound delivery for the remaining quantity of three that contains three pieces for every ten delivery items. 1. When EWM adjusts the delivery quantities. on the SAP Easy Access screen. A delivery item with ten pieces is assigned to a warehouse task with seven pieces. SAP Extended Warehouse Management (SAP EWM) 510 155 . Since you have not performed any warehouse activities for the remaining quantity of the delivery item. you cannot undo these changes. To do so.SAP Online Help 20. EWM automatically adjusts the delivery quantity to seven pieces. EWM displays the quantity of seven pieces.. 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.

you have not created a warehouse task for picking yet. that is. Prerequisites for the Outbound Delivery Order Split ● You have defined process codes that adjust both the delivery quantity and the transferred delivery quantity. You have defined the item types for the outbound deliveries in which you assigned the corresponding process code profiles.SAP Online Help 20. that is. you have completely picked an outbound delivery order in Extended Warehouse Management (EWM). see IMG for EWM under Goods Issue Process → Outbound Delivery → Manual Settings → Define Item Types for Outbound Delivery Process. see the IMG for EWM under Cross-Process Settings → Delivery Processing → Process Codes → Define Process Codes. For more information. For example. For more information. The prerequisite for this is that you have not performed a warehouse activity for this delivery item or partial quantity. ● ● ● Prerequisites for the Outbound Delivery Split ● If the delivery item of the outbound delivery is relevant for picking. You find that you cannot load the complete quantity. You can only create new subitems for this picked quantity. it performs an outbound delivery order split.07. You can create an outbound delivery for individual delivery items and therefore perform an outbound delivery split. 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. see the IMG for EWM under CrossProcess Settings → Delivery Processing → Process Codes → Maintain Process Code Profiles. you have at least picked the delivery quantity that you want to split into a new subitem. Either you or the system can split an outbound delivery order or an outbound delivery. For more information. O002) for quantity changes. the delivery quantity that you have split must ● SAP Extended Warehouse Management (SAP EWM) 510 156 . Either you or the system can split delivery items or partial quantities into a new delivery. You defined process code profiles. you have chosen the value 2 Adjustment of Delivery Quantity and Del. Transferred for the quantity adjustment. the status type Loading for the delivery item has the status value Partially Completed. If EWM is to use a default process code (for example. Quant.2007 Delivery Split for Outbound Deliveries Use You can perform a delivery split in various business processes. 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. If EWM finds various routes for different delivery items. If you have already started loading. 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]). you have chosen a default process code in the Customizing settings. For more information. For example.

see Route Determination in the Delivery [Seite 202] and Special Features for Outbound Delivery Objects [Seite 210]. EWM displays the subitems that have been created on the Items or HU tab page using + symbols in the Level column. EWM posts the stock of the delivery item to the subitem. you can delete the parts of a subitem that are packed in an HU. For more information.07. Delivery items 10 and 20 have route R1 and delivery item 30 has route R2.2007 also be loaded. on the SAP Easy Access screen. You create outbound deliveries for the individual subitems.SAP Online Help 20. and 30. see Route Determination in the Delivery [Seite 202] and Special Features for Outbound Delivery Objects SAP Extended Warehouse Management (SAP EWM) 510 157 . it takes different quantities into account than for the delivery split for inbound deliveries. Features Outbound Delivery Order Split Based on Outbound Delivery Request EWM performs an outbound delivery order split on the basis of route determination. EWM creates an outbound delivery order for delivery items 10 and 20 and a second outbound delivery order for delivery item 30. 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 can also delete an outbound delivery split. You delete the whole subitem when deleting unpacked products. For packed products. meaning that the stock is item based. You can post goods issue for every subitem. choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order. This means that the status Loading for the subitem has the status value Completed. 20. To do this. EWM creates corresponding subitems. Activities For a description of the activities for the outbound delivery order split. an outbound delivery request consists of delivery items 10. The document flow always displays the quantity of delivery items that have not been split and does not display the corresponding subitems. However. For example. You can split delivery items for both packed and unpacked products. 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 so. you must first delete the corresponding outbound delivery and then the subitem. When you save a newly created subitem. when EWM adjusts the delivery quantities. you split an outbound delivery order item.

c. perform the following steps: a. d. ● . select the subitem and choose with the quick info Delete. If you want to split a delivery item for unpacked products. Choose with the quick info Create Outbound Delivery. e. EWM creates one or more new subitems for which you can specify the desired delivery quantity.. perform the following steps: a. choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order. EWM creates an outbound delivery for the subitem. If you want to undo a delivery item split.2007 [Seite 210].SAP Online Help 20. Choose with the quick info Save. thus splitting the delivery item. ■ If you want to delete the subitem of a packed product. b. Activities for the Outbound Delivery Split On the SAP Easy Access screen. b.. on the right-hand side of Split Item and then choose EWM creates a new subitem for the HU. Specify the number of subitems that are to be created.. If you want to split a delivery item for packed products. SAP Extended Warehouse Management (SAP EWM) 510 158 . Go to the HU tab page and select an HU item. thus splitting the delivery item. EWM totally deletes the subitem. ● . For a description of the activities for the outbound delivery order split. see Delivery Split for Inbound Deliveries [Seite 154].07. Go to the Items tab page. undo the HU split. Choose the arrow on the right-hand side of Split Item and then choose Undo.. perform the following steps: a. EWM totally deletes the subitem. Choose with the quick info Save. for which you can specify the desired delivery quantity. d. EWM saves the new subitem. EWM saves the new subitem. Choose the arrow on the right-hand side of Subitem and then choose Split Up Outbound Delivery.. ● . b. Choose with the quick info Create Outbound Delivery. EWM creates an outbound delivery for the subitem. Delete the corresponding outbound delivery first by selecting the outbound with quick info Delete. Go to the HU tab page and select the subitem.. Choose the arrow Create. Go to the Items tab page and select a delivery item. delivery and choosing ■ If you want to delete the subitem of an unpacked product. c.

SAP Online Help 20.07. To do so. If a document changes. choose the corresponding user interface. EWM performs a validation. Extended Warehouse Management → Delivery Processing → Inbound Delivery → Maintain Inbound Delivery. for example. for example. Check. for an incompleteness check or a tolerance check. on the SAP Easy Access screen. see Validation [Seite 101]. Features For more information. Select an inbound delivery and choose the function SAP Extended Warehouse Management (SAP EWM) 510 159 . Activities You can call validation directly from the user interface.2007 Validation Use Extended Warehouse Management (EWM) works with a validation framework and uses various validation methods.

The process indicators are linked to the document and item types of delivery processing via a process profile. If inbound and outbound deliveries are used in a production process. the system sets the process indicator. on the other hand. When Extended Warehouse Management (EWM) creates a delivery document. or production order) Inbound and outbound deliveries usually have a reference to a preceding document. such as kit to stock. goods receipt for SAP Extended Warehouse Management (SAP EWM) . Features A process indicator has multiple values. sales order. A process indicator can allow or prohibit a business transaction or it may have no influence at all. SAP delivers a set of process indicators in the system profile and customer profile of process control. 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.SAP Online Help 20. Allows a reference to a preceding document (purchase order. Integration The process control described here is used in delivery processing exclusively. you have a reference to a production 510 160 Preceding document Production Allows processes for production. 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. do not refer to a preceding document. A process indicator describes the entire business transaction represented by the delivery document. You can change the settings for the process indicators in the process profile. inbound deliveries for purchase orders. Process control can influence field control. They do not require a preceding document in ERP. and outbound deliveries for sales orders. can be created and processed in EWM directly. you can change the value of this process indicator in a direct outbound delivery order. For the document header and document item.2007 Process Management and Control Use Process management and control manages business transactions using process indicators in a delivery document. Posting changes or outbound deliveries without reference. You can then no longer make changes to these. for example process indicator Scrapping has the value Not Allowed and Required. However. such as direct outbound delivery orders and posting changes.07.

and then post the locked stock. e. For more information. In this process.2007 In the scrapping process. you can post these to the stock of the differences to be cleared using a correction delivery. SAP Extended Warehouse Management (SAP EWM) 510 161 . you perform a planned reduction of overstock in two steps: you first post change the stock to locked stock. you only make goods available for the sales location within the warehouse.SAP Online Help production Scrapping Allows subprocesses for scrapping order. You do not perform any transportation activities. which require warehouse stock to be corrected. 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. 20.g. in a stock transfer process or for a customer 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. You can create the invoice in the early stages of the process flow within the packing or loading goods process step.07. If you identify warehouseexternal differences.

choose one of the following options: ■ ■ You specify the items with their stock attributes and quantities on the Items tab page. choose Extended Warehouse Management → Settings → Maintain Goods Movement Bin Determination. loading for transportation. 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. Then EWM automatically creates the corresponding items with their stock attributes and quantities. You remove the products from your warehouse and perform any other relevant goods issue steps. You specify all the relevant stock attributes of the product (for example. Either ERP distributes an outbound delivery to EWM and EWM automatically generates a corresponding warehouse request. for example. EWM also uses the settings that you specify here to process inbound deliveries that are not relevant to putaway. Extended Warehouse Management (EWM) does not generate any warehouse tasks for the warehouse request or any warehouse orders. EWM automatically suggests a goods movement bin. see the Implementation Guide (IMG) for EWM under CrossProcess Settings → Delivery Processing → Status Management → Define Status Profiles. If you generate the warehouse request manually. ○ If you have configured goods movement bin determination. However. 3. 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. 1.07. the stock type) and a goods movement bin in the warehouse request.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]. On the SAP Easy Access screen. You post the goods issue for the outbound delivery order.. ○ 2.. You or EWM create the warehouse request for an outbound delivery order. Process . or you manually generate the warehouse request in EWM as a direct outbound delivery order [Seite 167].SAP Online Help 20. On the HU tab page. SAP Extended Warehouse Management (SAP EWM) 510 162 . in contrast to picking. you choose the Create and Save pushbuttons and specify a handling unit (HU) and an item type.

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 .2007 Result EWM has generated a warehouse request for an outbound delivery order.SAP Online Help 20.07. You have removed the products from your warehouse.

EWM also uses the settings that you specify here to process outbound deliveries that are not relevant to picking. Result EWM has generated a warehouse request for an inbound delivery. You specify all the relevant stock attributes of the product (for example. You have performed any additional goods receipt activities. If you have configured goods movement bin determination. However. oryou manually generate the warehouse request in EWM. in contrast to putaway [Seite 300]. Extended Warehouse Management (EWM) does not generate any warehouse tasks for the warehouse request or any warehouse orders.. You or EWM create the warehouse request for an inbound delivery [Seite 112]. 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. and you have posted goods receipt. Process .. You perform any other relevant goods receipt steps. unloading. On the SAP Easy Access screen. you have put away the products in your warehouse. Either ERP distributes an inbound delivery to EWM and EWM automatically generates a corresponding warehouse request.SAP Online Help 20. 1. choose Extended Warehouse Management → Settings → Maintain Goods Movement Bin Determination. SAP Extended Warehouse Management (SAP EWM) 510 164 . see the Implementation Guide (IMG) for EWM under CrossProcess Settings → Delivery Processing → Status Management → Define Status Profiles. the stock type) and a goods movement bin in the warehouse request. 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. EWM automatically suggests a goods movement bin. You put away the products in your warehouse and you post goods receipt for the inbound delivery.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. 2.07. for example. 3.

for example. If the delivery item is not relevant to picking. You or EWM create the warehouse request for an inbound delivery or an outbound delivery order. On the SAP Easy Access screen. ERP distributes them to EWM and EWM adds the packaging items to the inbound or outbound delivery. the stock type. 1. 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. in the warehouse request. 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. Choose the Pkg Data tab page and display the relevant data. SAP Extended Warehouse Management (SAP EWM) 510 165 . EWM automatically suggests a goods movement bin. you specify a goods movement bin. choose Extended Warehouse Management → Settings → Maintain Goods Movement Bin Determination. When putting away the packaging material. Either ERP distributes an inbound or outbound delivery to EWM and EWM automatically generates a corresponding warehouse request. you use a warehouse request for an outbound delivery order (see also Warehouse Request for Inbound Delivery or Outbound Delivery Order [Seite 112]). You can manually generate packaging items for both the inbound delivery and the outbound delivery. on the SAP Easy Access screen. You post goods receipt for the inbound delivery or goods issue for the outbound delivery order. You perform any other relevant goods receipt or goods issue steps. In the goods issue process. For example. choose Extended Warehouse Management → Master Data → Product → Maintain Product and then choose the Global Data setting in the View group box. Prerequisites ● The product of the packaging item is a packaging material. you use a warehouse request for an inbound delivery. When removing the packaging material from stock. you specify all the relevant stock attributes of the packaging material. If the delivery items are relevant to picking or to putaway.. ● Process . 4. To do so. Check the settings for the packaging data in the global view of the product master. 2.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.07. or you manually generate the warehouse request in EWM. If packaging items already exist in an inbound or outbound delivery in ERP..SAP Online Help 20. Extended Warehouse Management (EWM) creates warehouse tasks for the warehouse request and the corresponding warehouse orders. 3. If not. If the delivery items are relevant to picking or to putaway. When you manually generate the packaging items. EWM creates neither warehouse tasks for the warehouse request nor warehouse orders. you pick products and use the packaging material as pick-handling units. If you have configured goods movement bin determination in Customizing for EWM. EWM processes these to a large extent in the same way as normal items. which is not possible in this case. you generate the warehouse tasks for the warehouse request and confirm them. Exceptions include the batch split.

SAP Online Help 20.07. or you have removed it from your warehouse and posted goods issue. You have either put away the packaging material in your warehouse and posted goods receipt.2007 Result EWM has generated the warehouse request for an inbound delivery or an outbound delivery order. SAP Extended Warehouse Management (SAP EWM) 510 166 .

The direct outbound delivery order contains the ERP document number. You can carry out the following for a direct outbound delivery order: ○ Save SAP Extended Warehouse Management (SAP EWM) 510 167 . you use a value-added service order [Extern] to create a kit from different components. for example. you post a goods issue with account assignment for the goods. You can also trigger direct sales in ERP without generating a sales order. transportation activities do not apply. Unlike for direct sales.2007 Direct Outbound Delivery Order Definition Document that is triggered in the warehouse directly. When you have created the kit and post goods issue for the direct outbound delivery order. transportation activities also do not apply. Whereas you can also trigger the preparation for scrapping – such as collecting goods in a scrapping container – using a posting change request from ERP. ● ● Immediate Delivery (Push or Pull Procedure) [Seite 172] Kit to stock or reverse kitting For kit to stock. for which ERP generated a reference document previously. You can use the direct outbound delivery order to execute actions that you require for generating and processing an outbound delivery in the warehouse. Extended Warehouse Management (EWM) sends the direct outbound delivery order to ERP. Use Unlike EWM outbound delivery orders. you or EWM can also generate direct outbound delivery orders directly and locally in EWM.07. such as picking. You post the goods to be scrapped with the goods issue from the warehouse stock. 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. The structure and data of the direct outbound delivery order match those of an outbound delivery order that is triggered in ERP. you always trigger this last step locally in the warehouse.SAP Online Help 20. you can use a direct outbound delivery order. which EWM then sends to ERP. since the customer asks for the goods and picks them up on-site in the warehouse. ○ Account assignment For account assignment. since the internal or external customer asks for the goods and picks them up on-site in the warehouse. for the cost center. EWM reduces the stock of the respective components. The delivery in ERP forms the outbound document for billing. You do not need to create a sales order for this. If you want to reserve the corresponding components. The direct outbound delivery order you generated manually in EWM forms the basis for the delivery in ERP. You can use direct outbound delivery orders in the following scenarios: ● Pickup [Extern] ○ Direct sales For direct sales.

The structure of a direct outbound delivery order also contains the following. or EWM determines the data automatically using configuration data. 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. overconfirmation may occur. the underlying document type must display the process correspondingly. see Outbound Delivery Order [Seite 91]. 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. 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. as this check is usually triggered in ERP To avoid endangering the continual ability to deliver. For more SAP Extended Warehouse Management (SAP EWM) 510 168 . you must select the correct document type to ensure the process flow is correct.07. In SAP SCM 5. such as the goods issue bin for items that are not pick-relevant. When generating a direct outbound delivery order. As you start the goods issue process using direct outbound delivery orders in EWM. Either you enter the data directly.2007 Validate Archive Delete Structure For the structural description of the direct outbound delivery order. No reservation takes place for checks in ERP. the planning situation must be adjusted with the availability check. For more information about defining document types in EWM.SAP Online Help ○ ○ ○ 20. EWM uses the process profile to do this.1. such as the product or quantity. In exceptional cases. planning-related reservation of the products only takes place if you are using SAP Advanced Planning and Optimization (SAP APO). ● 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. For more information about defining item types in EWM.

If you are not using a corresponding Enhancement Package. and are immediately ready for processing.SAP Online Help 20. no availability check is performed in ERP for the required product. see Availability Check [Seite 176]. When you generate a direct outbound delivery order. ● 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. ● Integration ● As direct outbound delivery orders are created in EWM directly. Instead. For more information. For outbound delivery orders replicated from ERP. or generation of items from handling units. see the Implementation Guide (IMG) for EWM under Interfaces → ERP Integration → General Settings → Set Control Parameters for ERP Version Control. the check can be performed in ERP or in SAP APO. There is no delivery replication. however. ● As no outbound delivery request from ERP exists for direct outbound delivery orders. meaning they have the status type Locked (Unchecked Item) and statusvalue No. see the IMG for EWM under Cross-Process Settings → Delivery Processing → Process Management and Control. For more information. actions such as splitting direct outbound delivery orders are not possible (see Delivery Split for Outbound Deliveries [Seite 156]). ● See also: Processing of Direct Outbound Delivery Orders [Seite 170] SAP Extended Warehouse Management (SAP EWM) 510 169 . Direct outbound delivery orders are also always checked.2007 information. only the goods movement posting takes place. Depending on the configuration. EWM triggers the availability check.07. for example. Direct outbound delivery orders support processing of non-pick-relevant items. the availability check is triggered in ERP. EWM automatically performs a Compliance Check [Seite 222].

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. Features For direct outbound delivery orders. Extended Warehouse Management (EWM) starts the standard goods issue [Seite 314] process and generates – if required – the necessary documents for billing and shipping. 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]). For more information. You have assigned sales organizations. see Direct Outbound Delivery Order [Seite 167].SAP Online Help 20. EWM sends these added delivery items to ERP. In the SAP Easy Access menu. on the SAP Easy Access screen choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order and choose the function Create. Only then does EWM give information about direct outbound delivery orders and perform an availability check. you have defined the goods movement bin determination. and ERP copies these to the relevant ERP outbound delivery.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]. choose Extended Warehouse Management → Interfaces → GTS: Assign Sales Organization. EWM does not 510 170 ● SAP Extended Warehouse Management (SAP EWM) . If you want to increase the outbound delivery quantity of an item manually. all the functions are available to you that you can perform for outbound deliveries. If you want EWM to perform automatic determination of the goods movement bin for delivery items that are not pick-relevant. You can delete a direct outbound delivery order in EWM. 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. Prerequisites ● You are using the corresponding ERP Enhancement Package. and ERP has already generated an item for this in the ERP outbound delivery. see the Implementation Guide (IMG) for EWM under Interfaces → ERP Integration → General Settings → Set Control Parameters for ERP Version Control. choose Extended Warehouse Management → Settings → Maintain Goods Movement Bin Determination. Integration For a description of this. An availability check is also performed for the added items (see Availability Check [Seite 176]).07.

● Constraints in ERP ● ● ● ● ● ● You cannot use credit management for direct outbound delivery orders. ● If you want to reduce the outbound delivery quantity.07.2007 perform another availability check for the difference quantity. Only when ERP copies the quantity change into the ERP outbound delivery does SAP Advanced Planning and Optimization (SAP APO) adjust its planned quantity.SAP Online Help 20. When you generate a direct outbound delivery order from the user interface of the outbound delivery order. Direct outbound delivery orders are not relevant for backorder processing in SAP APO. Constraints in EWM ● ● ● If you are adding packing items to a direct outbound delivery order. you can manually assign stock to a delivery item that does not have a picking status. You cannot extend bills of materials in direct outbound delivery orders. EWM cannot perform an availability check for these new delivery items. The kit-to-order process does not support direct outbound delivery orders. ERP does not send messages for a direct outbound delivery order to EWM. SAP Extended Warehouse Management (SAP EWM) 510 171 . The price determination in ERP does not provide you with the same functions as the price determination in the sales order. you can do this directly in the direct outbound delivery order. In this case. Choose the input help for Goods Mvt Bin and look for a bin in which stock exists. EWM can perform an availability check for this quantity. no further availability check takes place. You cannot use any configurable products in direct outbound delivery orders. Display your direct outbound delivery orders in the form view of the user interface of the outbound delivery order. When you generate a new item or direct outbound delivery order. You cannot perform billing in SAP Customer Relationship Management (SAP CRM) for direct outbound delivery orders.

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 vendor’s 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

In doing this.07. 2. 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. The production order contains a plant / storage location combination that refers to a warehouse in which you are using 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. EWM manages the plant and storage location combination. 3. You confirm the end of the designated production steps in the production order..2007 ERP (Delivery) User generates production order 1 EWM ERP (Production) User releases production order 1 Confirmation of production end triggers goods receipt posting 3 2 User confirms production steps and 3 production end System generates inbound delivery 3 4 System generates inbound delivery System posts goods receipt 7 User posts goods receipt 6 User transports product to warehouse 5 System updates production order and inbound delivery 7 User puts away product 6 . ERP generates an ERP inbound delivery and transmits it to EWM. This enables the confirmation of the last production step for a product to trigger goods receipt in ERP. 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 . ERP updates the finished quantity and marks the completed production steps. You generate a production order.SAP Online Help 20. When you confirm the last production step for a product in the production order. namely a production or process order.. and release it. 1. In other words.

ERP also posts goods receipt for the related ERP inbound delivery.SAP Online Help ○ 20. and generates an EWM inbound delivery corresponding to this. You put away the product. ERP also updates the stock in the production order and in the ERP inbound delivery. Result You have posted goods receipt for your products from production. due to the goods movement. for example to the goods receiving area. SAP Extended Warehouse Management (SAP EWM) 510 194 . and updated the stock in ERP. 5. You transport the finished product into the warehouse. 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. ERP generates a material document immediately at goods receipt posting. 6. 4. post the goods receipt. EWM receives a corresponding inbound delivery notification from ERP. You can use the number of the production order to find the corresponding EWM inbound delivery. see the Implementation Guide (IMG) for ERP under Logistics → Materials Management → Purchasing → Purchase Order → Subsequent Functions → MIGO – Goods Receipt. 7. EWM transmits the goods receipt posting to ERP. and put away the product. If EWM does not manage the plant and storage location combination. and ERP updates the stock.07.2007 SAP Help Portal. The inbound delivery contains a link to the production order in ERP.

For more information about document type determination.2007 Goods Receipt Posting Triggered by EWM Purpose You receive finished products. so that your goods receipt posting in the central warehouse directly triggers generation of the EWM inbound delivery in the decentralized warehouse. For more information. In this case you must make sure that the data in the inbound delivery is validated. Prerequisites ● You are using SAP SCM 5. EWM uses document type IDPD Inbound Delivery from Production to differentiate that an EWM inbound delivery from production takes place. for example without stock transport orders. You can use the standard implementation of Business Add-In (BAdI) /SCWM/EX_ERP_PROD. see the Implementation Guide (IMG) for EWM under Goods Receipt Process → Inbound Delivery → Define Document Type Determination for Inbound Delivery Process. you generate an EWM inbound delivery manually without a template. in the goods receiving area for example. see the Implementation Guide (IMG) for EWM under Interfaces → ERP Integration → General Settings → Set Control Parameters for ERP Version Control.1 and the corresponding ERP release. You are using simple transport routes. you are working with expected goods receipts [Extern] in Extended Warehouse Management (EWM). for which you want to post goods receipt [Seite 263].07. meaning without an expected goods receipt. In exceptional circumstances. For this. ● Process The following figure provides an overview of the process flow: SAP Extended Warehouse Management (SAP EWM) 510 195 .SAP Online Help 20.

SAP Online Help 20. You generate a production order and release it..g. 2.2007 ERP (Delivery) User generates production order 1 EWM ERP (Production) User releases production order 1 Function module generates new expected goods receipts (GRs) 2 Report call deletes expected GRs 2 System generates expected GRs 3 System generates inbound delivery 6 User generates inbound delivery as copy of expected GR 6 4 User confirms production end and 5 moves product. ERP identifies the relevance from your selection criteria and from the open quantities. to GR area System posts goods receipt 8 User posts goods receipt 7 System updates production order and inbound delivery 8 User puts away product 7 . ERP does not trigger generation of expected goods receipts. ERP checks whether relevant production orders still exist for which you still have to post goods receipt. and ERP updates the stock. 1. and calls ERP function module /SPE/INB_EGR_CREATE_PROD. EWM uses report /SCWM/ERP_DLV_DELETE [Seite 184] to delete any existing expected goods receipts in EWM. 3. ERP generates a material document immediately at goods receipt posting.. For more information. When EWM calls the ERP function module. EWM manages the plant and storage location combination.07. Prerequisite for this is that you execute report /SCWM/ERP_DLV_DELETE. and generates a corresponding expected goods receipt in EWM. For each relevant production order. If open quantities still exist. see Generate Inbound Delivery from Expected Goods Receipt [Seite 187]. In other words. EWM receives a notification for the expected goods receipt from ERP. e. The production order contains a plant / storage location combination that refers to a warehouse in which you are using EWM. then the goods receipt indicator is set in ERP but the final delivery indicator is not set. If EWM does not manage the plant and storage location combination. SAP Extended Warehouse Management (SAP EWM) 510 196 . You put away the product.

2007 The expected goods receipt contains a link to the production order in ERP. ERP also posts goods receipt for the related ERP inbound delivery. It contains the planned times and quantities. and updated the stock in ERP. and can adjust the quantities if required. In doing this. ERP updates the finished quantity and marks the completed production steps. You can use the number of the production order to find the expected goods receipt. EWM transmits the goods receipt posting to ERP. and generate a corresponding EWM inbound delivery. Result You have posted goods receipt for your products from production.SAP Online Help 20. for example. You transport the finished products into the warehouse. due to the goods movement. You can use the expected goods receipt in EWM for planning purposes. 4. 8.07. ERP also updates the stock in the production order and in the ERP inbound delivery. 7. Here you use the expected goods receipt as a template for the EWM inbound delivery. You post the goods receipt and put away the products. 6. SAP Extended Warehouse Management (SAP EWM) 510 197 . You confirm the end of the designated production steps in the production order. 5. for example to the goods receiving area.

SAP Online Help 20. 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 .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.

EWM is able to send modified TU data from yard management to delivery processing. delivery processing obtains the information about status changes from the user interface of the delivery. such as from In transit to In yard Information about transportation units (TUs) If you do not use yard management. . If yard management has not assigned a transportation unit to a delivery document item. Features As a result of the connection to yard management. Delivery processing aggregates the status data of the delivery document items. Completed rather than Not started. As long as the status value of the delivery document header for shipping and receiving has not yet reached In processing or Completed. it sets the Assign Transportation Unit status of the delivery document item to Not started.. If all delivery document items have the same status value. you can still change the following fields in the delivery document: ● SAP Extended Warehouse Management (SAP EWM) 510 199 . EWM updates the TU data with the assignment of transportation unit to a delivery header. Prerequisites You use yard management in EWM. Yard management and delivery processing exchange the following information changes: ● ● Status changes in the delivery.07. Not started. See: The “Prerequisites“ section under Yard Management [Seite 619]. delivery processing also sets this status value for the delivery document header for shipping and receiving. EWM writes this TU data to delivery processing and the handling unit in the following way: ● If shipping and receiving is activated.SAP Online Help 20. or Completed. For shipping and receiving. delivery document item. namely Not relevant. such as statusdependent goods receipt posting. a. or at handling unit level. delivery processing changes the status value for the Assign Transportation Unit status of the delivery document item from Not relevant to Not started. This enables delivery processing to allow follow-up actions. delivery processing changes the status value for the Assign Transportation Unit status of the delivery document item from Not relevant (default) to Completed.2007 Connection of Delivery Processing to Yard Management Use If you use yard management [Seite 619] in Extended Warehouse Management (EWM). for example. Yard management informs delivery processing about the assignment. this communicates with delivery processing to exchange relevant information such as status changes. c.. If one delivery document item has a different status value to the others. delivery processing sets the status value for the delivery document header for shipping and receiving to In process. b.

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

SAP Online Help 20. Features For more information about the features of transportation management. SAP Extended Warehouse Management (SAP EWM) 510 201 . see Transportation Management [Seite 629].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].

The route itself. When working with automatic route determination. quantity.SAP Online Help 20. if all the items have the same shipping conditions. route determination uses it as an additional constraint during route determination: ■ ■ ■ ■ The carrier. for example. either with a predefined route or it does not supply a route for the routing guide. such as SAP Extended Warehouse Management (SAP EWM) 510 202 . if the determination indicator [Extern] is not initial or the carrier has been specified by EWM. You either enter the predefined route manually or an external system. 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. The means of transport. 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. You can also manually enter or change a route on the user interface of the delivery. EWM uses the routing guide. 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. Features Route Determination Route determination attempts to find a route in delivery processing that corresponds to the delivery data. Delivery processing executes route checks and. At least one item with an entry for product. This determines the route and sends it back to delivery processing. or date/time. 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. The shipping conditions of all items.2007 Route Determination in the Delivery Use Delivery processing calls the routing guide [Extern] for automatic route determination [Seite 638]. in doing so. For this. Integration For actual route determination. if the determination indicator is not initial or the means of transport has been specified by EWM. the route status must be activated at header level so that route determination can set this status. route determination calls the routing guide. If the following delivery data is available. and the outbound delivery (see Special Features for Outbound Delivery Objects [Seite 210]). if the determination indicator is not initial or the route has been specified by EWM. a quantity.07. Prerequisites ● ● You made the settings for route determination [Seite 205]. the product.

that is. Die Priorität wird ausgehend vom verwendeten Kostenprofil gesetzt. Route Determination in Transportation Cross-Docking In a transportation cross-docking process (TCD process). If the route contains a TCD location. You define the route determination status in Customizing for EWM: ● ● ● ● Route Determination is Always Active (<blank>). check which routes EWM finds for specific data or which routes EWM approves as valid after the route check.2007 SAP Customer Relationship Management (SAP CRM) assigns a route to EWM. route determination enters this as the ship-to party in the delivery. the field for the route is empty) or you have changed data that is route-dependent (for example. route determination executes automatic route determination. it uses the route with the highest priority. sets further delivery data automatically. SAP Extended Warehouse Management (SAP EWM) 510 203 . The previous ship-to party becomes the final ship-to party. Outbound Delivery Objects In addition to the features mentioned here. For more information. you specify a valid route. for example. delivery date/time or means of transport.07. Automatic Route Determination If you have not yet entered a route (that is. For more information about the data that delivery processing uses or copies in route determination. see Execution of Automatic Route Determination [Seite 207]. You can directly enter constraints for route determination in the outbound delivery. Route determination in the delivery does not overwrite any routes manually entered. 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. while using the data of the relevant items (see Execution of Automatic Route Determination [Seite 207]). item quantities). see the Implementation Guide (IMG) for EWM under Goods Issue Process → Outbound Delivery → Route Determination → Activate or Deactivate Route Determination. route determination handles the various outbound delivery objects differently. Automatic Route Determination Only in Case of Initial Route Automatic Route Determination Inactive Route Determination Inactive For more information. The data automatically set can be data that route determination also determines. 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. The routing guide sends the priority together with the route to delivery processing. route determination copies certain data to the delivery and. Route Status Route determination sets a route status at header level depending on the route determination. For more information. if necessary. route determination finds one or more valid routes for the start date/time and the supply chain unit. Priority If. see Data Use in Route Determination [Seite 209].SAP Online Help 20. see Special Features for Outbound Delivery Objects [Seite 210]. or an external system transfers a valid route to EWM. Simulation of Route Determination You can simulate route determiantion [Seite 662]. Data Use If route determination automatically finds a valid route.

Route Check EWM checks in delivery processing whether a valid route exists for the delivery data. If route determination cannot identify a TCD location during a new route determination. see Route Determination as Part of Cross-Docking [Seite 655]. For more information about route determination for transportation cross-docking. If you specify a route manually or deactivate automatic route determination. route determination also specifies the goods issue date/time at the TCD location in the delivery header. choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order or Maintain Outbound Delivery and then the Route pushbutton. which means that route determination works with a delivery date and a final delivery date. it deletes the TCD-specific data from the delivery. Furthermore. Route determination enters the route to the next TCD location as the route for the delivery.07. This also applies to a route that is specified manually. EWM then carries out a further check to determine whether the route that you have specified manually is valid for the delivery data. SAP Extended Warehouse Management (SAP EWM) 510 204 . For more information about the individual settings for the user interface.SAP Online Help 20.2007 Route determination proceeds in the same way with the delivery date. Activities If you want to manually trigger route determination. see Route Determination on the User Interface [Seite 211]. on the SAP Easy Access screen.

In this case. As a business partner or address is entered in the delivery as a goods recipient. the system attempts to find a supply chain unit zone based on the address data. This is done in the following way: ○ If a document address is entered in the delivery for the goods recipient. you assign this supply chain unit to the business partner (ship-to party) that has been entered in the delivery.07. 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). For more information. as it is also used by other processes. see the Implementation Guide (IMG) for EWM under Goods Issue Process → Transportation Management → Route Determination → General Settings for Route Determination. To do this. ● You have activated the route determination for the delivery or the warehouse that is being used. ● ○ If the goods recipient is a business partner or customer whose master data has been transferred from ERP. see the IMG for EWM under Goods Issue Process → Outbound Delivery → Route Determination → Activate or Deactivate Route Determination. SAP Extended Warehouse Management (SAP EWM) 510 205 .2007 Making Settings for Route Determination To use route determination. In the Bus. Here. If no document address is used. For more information. you must make the following settings: Customizing ● You have activated the route determination of transportation management in Customizing in Extended Warehouse Management (EWM). see the IMG for EWM under Goods Issue Process → Outbound Delivery → Route Determination → Define Scheduling Within Route Determination. you have created an individual supply chain unit for the ship-to party in the supply chain unit master data. You are not allowed to change a business partner that has already been entered in a supply chain unit.SAP Online Help 20.Partner field on the General tab page. and creates a supply chain unit (for example. and not allowed to change this entry. you are not allowed to enter a business partner in the supply chain unit. for the customer). the destination location may also be a zone. the system usually enters the assignment of the business partner to the supply chain unit. ● You also have the option of making additional settings for scheduling. on the SAP Easy Access screen. 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 chosen Extended Warehouse Management → Master Data → Shipping and Receiving → Route Determination → Maintain Route. For more information. an assignment still has to be made with which the destination location used in a route is determined. This zone is then used as the destination location for route determination. 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.

If EWM does not find a distinct assignment. 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. ○ ○ If EWM finds one distinct entry. (business character) tab page. it uses this supply chain unit. ○ 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. only assign one supply chain unit of one type to a business partner. If you want to create a ship-to party or an address for a ship-to party. If you do not use addresses in the delivery.SAP Online Help 20. If you assign more than one supply chain unit of one type to a business partner. 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 party’s address. in the SAP Easy Access screen choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order or Maintain Outbound Delivery. you assign the business character to the supply chain unit as a planning location [Extern]. If EWM does not find an assignment. EWM cannot clearly determine the supply chain unit from the business partner. For master data sent that was sent from the ERP system. that is. ● You also determine the following for the supply chain unit master data: ○ ○ On the Bus.2007 Avoid multiple assignments. You have created a ship-to party or an address for a ship-to party.Char. 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 for the case where you have created multiple assignments.07. it cannot accurately find the routes and issues a message to this effect. and whether a supply chain unit exists for this entry. SAP Extended Warehouse Management (SAP EWM) 510 206 . you assign the business partner of the ship-to party in the supply chain unit master data of the supply chain unit. and whether a supply chain unit exists for this entry.

Changing the final ship-to party. Changing the shipping conditions. Changing the means of transport or setting the determination indicator for the means of transport to Initial or Value Determined by System. delivery processing only executes route determination or new route determination for those items that are not yet assigned to an outbound delivery order. Delivery item Delivery processing only executes new route determination for those items that are relevant for the route. Changing the warehouse (of the source location). kit items. Prerequisites You made the settings for route determination [Seite 205]. Change to Delivery Date Changing the final delivery date/time. Extended Warehouse Management (EWM) may be able to execute automatic route determination. In addition. 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 planned goods issue date/time. Changing the ship-to party. This means that delivery processing does not execute new route determination for changes to text items. This means that you do not need to enter a route manually and route determination determines a new route when data is changed. SAP Extended Warehouse Management (SAP EWM) 510 207 . Changing the freight forwarder.07. Creating a new delivery item. or items that are not warehouse-relevant. Changing the delivery quantity.SAP Online Help 20. ● ● ● ● ● ● Changing the product. Changing the weight or volume. Features If either you or the system change one of the following fields in the delivery header or a delivery item in the delivery.2007 Executing Automatic Route Determination Use Depending on your Customizing settings and various other settings.

EWM also does not check the validity of the route. As soon as you change a route.SAP Online Help 20. EWM only executes route checking again when you change a route. EWM does not execute new route determination.07. EWM sets the dependent data once again. It only checks the validity of the route. 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. SAP Extended Warehouse Management (SAP EWM) 510 208 . If EWM has already scheduled a document for picking.2007 If you release a route in the delivery manually.

Using the determination indicator [Extern]. 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 . Route determination uses certain delivery-relevant items (see Executing Automatic Route Determination [Seite 207]). or if an external system specifies them. route determination uses them as additional constraints. ● When route determination determines a valid route. ● ● From the delivery header. Route determination determines routes for this carrier only as valid.07. a change in which also triggers new route determination. you manually specify the carrier.SAP Online Help 20.2007 Data Use in Route Determination Route determination uses various data from the delivery. route determination identifies whether it automatically determined the field or whether you or an external system specified the field. route determination uses the supply chain units of the warehouse and the ship-to party. Non delivery-relevant items are text or kit items. or items that are not warehouserelevant. the route or the means of transport. ● 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. For example. for example.

However. for example. Route determination for an outbound delivery order does not take into account any delivery items that are already assigned to an outbound delivery. If route determination cannot determine a common route. route determination no longer determines the route.SAP Online Help 20. because of Delivery Groups [Extern]). delivery processing does not check the route (even with the data change described above). EWM reexecutes route determination. meaning that it does not execute route determination. The dependent data of the delivery items remains unchanged. delivery processing creates an outbound delivery order for each route. If you change a route in the outbound delivery. ● ● If route determination determines a common route. the system does not execute a delivery split. EWM attempts to determine a common route for all delivery items. Features Outbound Delivery Request With route determination in the outbound delivery request. 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. The only exception is route determination in transportation cross-docking (see Route Determination in the Delivery [Seite 202]. Route determination specifies the same route for all delivery items. If. you manually approve the route. Extended Warehouse Management (EWM) can execute a delivery split in different outbound delivery orders. nor does it check if the route is valid. If you have deactivated route determination in Customizing. This time. If you have activated route determination in Customizing. In this way. you can. route determination only adjusts the dependent data to the outbound delivery header. delivery processing checks if the route is valid. EWM always processes logically corresponding delivery items together (for example. however. transport heavy and also smaller products in two outbound delivery orders via separate routes within the same outbound delivery request. Outbound Delivery Delivery processing copies the route and the route status from the outbound delivery order to the outbound delivery. section Route Determination in Transportation Cross-Docking).07. The differences for the individual outbound delivery objects are described below. If route determination determines varying routes for the delivery items. As soon as you change delivery item data or delivery header data that is route-relevant. SAP Extended Warehouse Management (SAP EWM) 510 210 . or if an external system manually specifies the route. If you manually enter a route.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]. delivery processing only checks if the manually entered route is valid. route determination determines one route for every routerelevant delivery item (see Execution of Automatic Route Determination [Seite 207]).

Lead Time. As described above. Route determination sets the determination indicator of the route to Manual. ● With the Departure Date/Time. and the Set Route to Determined Automatically indicator. you can also execute route determination with the new master data using this function. 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. Features Redetermination of Routes You can execute route determination for one or more deliveries with the Redetermine pushbutton. you can use an earlier or a later route. SAP Extended Warehouse Management (SAP EWM) 510 211 . This means that route determination also determines routes that it does not automatically find.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. This is specified in hours. route determination attempts to find a route or trip [Extern] with this date and time. ● You can use the Aggregation field to include the total weight of the selected deliveries in route determination. 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. A route redetermination also uses this date/time.07. route determination attempts to find a route or trip that occurs after the current Departure from Yard date/time plus the lead time. and Aggregation fields. you can use the Departure Date/Time. Lead Time. ● Assigning Routes With the Assign pushbutton. If you use the Next Trip field. If you use the Departure Date/Time field. route determination uses the route that was found automatically. for example.SAP Online Help 20. route determination also sets the determination indicator [Extern] of the route to Determined Automatically. Note that you can only ever use one of these fields. If you set this indicator. because the weight of the individual deliveries is too low. If you use the Lead Time field. If you change your route master data. 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. and Next Trip fields. If delivery processing executes a route redetermination. For example. you can assign a route to one or more deliveries. Next Trip. 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.

Delivery processing issues a warning message if the route that was found deviates from the route contained in the delivery. route determination can no longer automatically determine this data. you can force delivery processing to use this invalid route for a delivery using manual route approval. In the transportation cross-docking process (TCD process). for example. the determination indicator must not be Value Calculated by System. if. 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 only manually approve a route if the route status is Found Invalid. You can implement further checks in the BAdI.SAP Online Help 20. Manually Releasing Routes You can manually release a route with the Release pushbutton. After a manual approval. If you manually enter a route that is invalid for the delivery or has no master record.07. route determination changes the status of the route to Manually Released. You either set the determination indicator to Initial or Value Calculated by System. route determination uses the total weight and total volume of all selected deliveries in the aggregated check. whether the routes are still valid. For the route check. If you cannot use a route for a delivery because of dangerous goods data. you check whether route determination has found a result for the delivery.2007 Checking Routes You can execute a route redetermination with the Check or Check (Aggregated) pushbutton. you can work with deliveries that contain an invalid route. You can manually set this data or use the BAdI /SCWM/EX_DLV_ACT_ROUTE_RELEASE. If you want to enter a route manually. Delivery processing blocks a delivery with an invalid route. Route determination sets this data to initial. or you use the Redetermine pushbutton for route redetermination. You can also manually approve a route with the status Found Invalid. If you have made changes to the route master data. for example. With this. You can cancel a manual route approval. With this. You also check whether the route determination data agrees with the data in the delivery. If you manually approve a route. you want to use a route that is actually invalid for a delivery. in an exceptional situation. delivery processing does not execute automatic route determination. you can check. for example. since the invalid route would lead to another blocked delivery. delivery processing also issues a warning message if the route that was found contains TCD information that the delivery does not contain. SAP Extended Warehouse Management (SAP EWM) 510 212 . Route determination automatically uses dependent data from a valid route determination (see Data Use in Route Determination [Seite 209]). Then you cannot post the goods issue for this delivery.

SAP Online Help 20. SAP Extended Warehouse Management (SAP EWM) 510 213 . see Working with Serial Numbers in the Delivery [Seite 590] and Integration of Serial Number in the Delivery [Seite 592]. Features For more information about using serial numbers in the delivery.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.

see the SAP Library under SAP xAPPs → SAP Global Trade Services.07. SAP Extended Warehouse Management (SAP EWM) 510 214 .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.SAP Online Help 20.

SAP Extended Warehouse Management (SAP EWM) 510 215 .SAP Online Help 20.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.07. Delivery processing uses these to recognize that an inbound delivery is relevant to transit procedures or to customs blocked stock. Here EWM differentiates between inbound deliveries and outbound deliveries during the processing. For more information. EWM saves the previous document number together with its previous document type as the reference document number and category in the delivery document. see Transit Procedure for Inbound Deliveries [Seite 216] and Transit Procedure for Outbound Deliveries [Seite 218].

you set this status manually. The ERP system can also send an advanced shipping notification to EWM that already contains the previous document number and previous document type. You enter these manually in the inbound delivery as the reference document number and reference document category.. 6. In doing so. 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.. 3. you can subject complete inbound deliveries that are transit procedure relevant to a transit procedure. you can change the previous document number and previous document type in the user interface. ○ If the customs authority allows the vehicle to be unloaded. on the SAP Easy Access screen. If the customs authority does not allow the vehicle to be unloaded because it is performing a customs inspection. Based on the Customizing settings for the previous document type. In the case of inbound deliveries that are relevant to transit procedures. You do this in Customizing for EWM under Interfaces → GTS Integration → Define Previous Document Types. choose Extended Warehouse Management → Delivery Processing → Inbound Delivery →Maintain Inbound Delivery and then the In Yard pushbutton. ○ SAP Extended Warehouse Management (SAP EWM) 510 216 . SAP GTS asks the customs authority whether it is permitted to unload the vehicle. EWM determines that the reference document number is a previous document number for which EWM must perform a transit procedure. EWM informs SAP GTS that an inbound delivery exists for which it must perform a transit procedure. unloading is delayed. The customs authority sends a corresponding message to SAP GTS. 4. By doing so.2007 Transit Procedure for Inbound Deliveries Purpose In Extended Warehouse Management (EWM). If the status type Transit Status does not have the status value Registered in Yard. ● Process . SAP GTS sends a notification of the unloading permission to EWM. 1. In this case. 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. In the dropdown menu. for example. you ensure that EWM informs SAP Global Trade Services (SAP GTS) [Seite 214] about the inbound delivery. you can ensure that the customs authority issues an unloading permission for the vehicles with the goods to be delivered. To do so.07. you find the previous document number [Extern] and previous document type in the transportation papers for the vehicle. EWM locks the inbound delivery to prevent additional goods receipt process steps [Seite 263] from being performed. Prerequisites ● You have defined reference document categories in Customizing for EWM under Cross-Process Settings → Delivery Processing → Reference Documents → Define Reference Document Categories. SAP GTS performs an EDI communication with the customs authority. 2.SAP Online Help 20. posting goods receipt. choose Set Status. 5. On the basis of this message.

for example. See also: Loading and Unloading [Seite 608] SAP Extended Warehouse Management (SAP EWM) 510 217 . You unload the vehicle and perform additional goods receipt process steps. you post the goods receipt. EWM informs the ERP system about the previous document number that you might have changed (see step 1). SAP GTS sends a notification with the unloading permission to EWM.2007 After the customs inspection.07.SAP Online Help 20. Result You have performed a transit procedure for your inbound delivery. EWM sets the status type Transit Procedure of the inbound delivery to Released and unlocks the inbound delivery for additional goods receipt process steps. 7. 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.

on the SAP Easy Access screen. on the SAP Easy Access screen.SAP Online Help 20. EWM locks the outbound delivery to prevent additional goods issue process steps [Seite 314] from being performed. choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery and then the Transit Procedure pushbutton. you set the status type Transit Procedure of the outbound delivery in EWM to the status value Released. 1. on the SAP Easy Access screen. EWM releases the locked outbound delivery for additional goods issue process steps. you can subject complete outbound deliveries that are transit procedure relevant to a transit procedure. choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery and then the Transit Procedure pushbutton. for example.. You ask the customs authority for loading permission. posting the goods issue. EWM uses the status type Transit Procedure with the status value Not Relevant. To do so. Process .. you set the status type Transit Procedure of the outbound delivery in EWM to the status value Released. 2. As the default value. After the customs inspection. as required.2007 Transit Procedure for Outbound Deliveries Purpose In Extended Warehouse Management (EWM). ○ If the customs authority allows the vehicle to be loaded. choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery and then the Transit Procedure pushbutton. that all deliveries for a certain country are relevant to a transit procedure. In the dropdown menu. for example. choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery and then the Transit Procedure pushbutton. you define whether this outbound delivery is relevant to a transit procedure. EWM releases the outbound delivery for additional goods issue process steps. choose Set Status to “Blocked for Customs”. see the BAdI documentation. 3. In the dropdown menu. You can set the status type Transit Procedure of the outbound delivery to the status value Customs Insp. In the dropdown menu. you can ensure that the customs authority issues a loading permission for the vehicles with the goods to be delivered to the goods recipient. To do so. on the SAP Easy Access screen. You can use the BAdI /SCWM/SHP_PROC_REL_SET to define. If the customs authority does not allow the vehicle to be loaded because it is performing a customs inspection. 4. In the dropdown menu. choose Set Status to “Release”.. loading is delayed. Prerequisites You have implemented the enhancement spot /SCWM/ES_GTS_INTEGRATION. choose Set Status to Check. In doing so. For more information. You set the status type Transit Procedure of the outbound delivery to the status value For Checking.07. ○ SAP Extended Warehouse Management (SAP EWM) 510 218 . To do so. choose Set Status to “Release”. Before you load a vehicle for an outbound delivery. To do so. to determine the transit procedure relevance.

for example. You load the vehicle and perform additional goods issue process steps.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. See also: Loading and Unloading [Seite 608] SAP Extended Warehouse Management (SAP EWM) 510 219 .07. you post the goods issue. Result You have performed a transit procedure for your outbound delivery.SAP Online Help 20.

Otherwise. EWM posts the stock to a stock type for customs block stock. The most important aspect is whether the combination of previous document number and previous document type is relevant to customs procedures. If the previous document type is relevant to customs blocked stock [Extern]. • If you change the previous document number or previous document type again before posting goods receipt.SAP Online Help 20. EWM automatically changes the stock type.07. You can put away stock in a normal way in spite of a customs block. • • SAP Extended Warehouse Management (SAP EWM) 510 220 . you can specify both directly in the delivery document in EWM. This is not dependent on whether the product itself is managed in the customs warehouse. Delivery processing decides whether a delivery item is relevant to customs procedures on a product-independent basis. F1 Unrestricted Use in Putaway. you have defined that the previous document type is relevant to customs blocked stock. you must specify a country of origin in the delivery for goods receipt posting. As a result. EWM posts the stock to a different stock type. ● 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 you want to define a customs block for certain previous document types. Prerequisites ● ● You have performed Customizing for the transit procedure [Seite 216] in Extended Warehouse Management (EWM). If you have posted the first (partial) goods receipt or EWM has created a warehouse task (unloading warehouse task or putaway warehouse task). for example.2007 Connection of Delivery Processing to Safekeeping Use You can use safekeeping [Seite 962] for inbound deliveries in delivery processing. 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. If a product is subject to a batch management requirement and is relevant to customs warehousing. You have set the Customs Block indicator in Customizing for EWM under Extended Warehouse Management → Interfaces → GTS Integration → Define Previous Document Types. you cannot change the previous document number or previous document type in the delivery. If there is no previous document number or previous document type in the ERP system.

● If the product is relevant to customs warehousing. delivery processing continues to process the posting change request for scrapping. see Customs Warehousing Procedure [Seite 964]. delivery processing automatically creates a posting change request for scrapping. ○ ○ If SAP GTS sends this number immediately. it sends the scrapping reference number to delivery processing. Proc. As soon as SAP GTS gets this permission. for example. If you work with posting change requests [Seite 128] for scrapping in the scrapping process in the customs warehouse [Seite 965]. Delivery processing also checks whether the product in this posting change request is relevant to customs warehousing. or you do this manually. If SAP GTS does not send this number immediately. Features When the ERP system sends a posting change delivery for a scrapping to delivery processing. the only effect that you have on delivery processing is in the scrapping area.SAP Online Help 20. delivery processing locks the posting change request to prevent further processing. warehouse task creation. delivery processing immediately continues to process the posting change request. SAP GTS asks the customs authority for permission for the scrapping. SAP Global Trade Services (SAP GTS) can apply to the customs authority for permission to scrap. to the Customs Warehousing Procedure Use If you use the customs warehousing procedure [Seite 964] in Extended Warehouse Management (EWM).2007 Connection of Deliv. 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. Prerequisites For a description of the prerequisites for using the customs warehousing procedure in EWM. ● If the product is not relevant to customs warehousing.07. delivery processing requests a scrapping reference number from SAP GTS. Delivery processing unlocks the posting change request and continues with the processing. See also: Performing Scrapping [Seite 130] SAP Extended Warehouse Management (SAP EWM) 510 221 .

and do not set the Inactive indicator for the corresponding status type DGT GTS check. no exports from the USA to Cuba Legal control. To do so. meaning licenses For example.SAP Online Help 20. address. For more information. see the IMG for EWM under Goods Issue Process → Outbound Delivery → Define Position Types for Outbound Delivery Process Using Wizard . you can define the item types for which EWM is to perform the checks: ○ Define a status profile for the checks. you must set the LegConGTS (GTS Compliance Check: Document Types Relevant for the Legal Control) indicator. or delivery quantity) in an outbound delivery. For more information. If you determined in Customizing that the outbound delivery is relevant for the legal control. If EWM changes certain fields in an outbound delivery order or outbound delivery.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. or you manually change certain fields (for example. a product is only allowed to be exported in a certain quantity and 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. ○ ● If you want the system to check outbound deliveries before goods issue. Assign this status profile to an item type. ● Prerequisites ● In Customizing. partner.07. SAP Extended Warehouse Management (SAP EWM) 510 222 . ● ● ● 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. ● In the outbound delivery. see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Delivery Processing → Status Management → Define Status Profile. EWM checks the outbound delivery order or the outbound delivery. in Customizing for EWM choose Goods Issue Process → Outbound Delivery → Define EWM-Specific Settings for Document Types. EWM checks the outbound delivery before goods issue. Only in this instance does EWM perform a letter of credit check. a letter of credit number from the preceding document exists as a reference document. for example.

To do so. see the IMG under Customer Relationship Management → Transactions → Basic Settings → Define Transaction Type or Define Item Type. SAP Extended Warehouse Management (SAP EWM) 510 223 . 2.07. we recommend that you perform it in both systems (EWM and CRM). EWM sets the status GTS Check/Technical Error or GTS Check/Check. Process . no data from a preceding document. no data from a preceding document is available in EWM. such as an ERP outbound delivery. EWM does not perform a letter of credit check or a check for licenses for direct outbound delivery orders. EWM does not perform any checks in SAP GTS. is available. choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery. In the standard system. For example.2007 If you are working with direct outbound delivery orders [Seite 167]. 1. you want to reset a GTS lock. However. you can remove a GTS lock. see the SAP Library under SAP xAPPs → SAP Global Trade Services. You can also specify the sales organization manually onthe user interface for the outbound delivery order. For more information. If SAP GTS checks for the outbound delivery contain errors.. As EWM requires the sales organization. SAP GTS returns the relevant status.SAP Online Help ● 20. For more information about SAP GTS. If you are working with kit to stock. NotOK. you can define it in Customizing for EWM for the corresponding checks. To do so. NotOK. or you do not perform it in either system. If you use SAP Customer Relationship Management (SAP CRM). EWM sets the status GTS Check/Technical Error or GTS Check/Check. EWM calls the checks for both outbound delivery orders and for outbound deliveries. EWM performs restricted checks only. in Customing for EWM choose Interfaces → GTS Integration → Assign Sales Organization to Warehouse Number.. ○ If you have the required authorization. If you require the checks in your scenario. we recommend that you accept the decision from SAP GTS to avoid corrupting any check criteria. If you are working with direct outbound delivery orders. ○ If SAP GTS checks for the outbound delivery order contain errors. set the GTS Relevance indicator for the transaction type and the item type in Customizing for CRM. EWM prepares the data in the outbound delivery for checks and calls SAP GTS. SAP GTS performs the checks and returns a status. as an administrator. on the SAP Easy Access screen. you perform these steps for the business transaction category Sales. you can perform the checks for the corresponding sales order there. For this reason. If. SAP GTS returns the relevant status. and does not create an outbound delivery for this outbound delivery order. and does not permit a goods issue posting for this outbound delivery.

EWM looks for the stock for the outbound delivery of this batch. Date Dec. EWM books in the stock. SAP Extended Warehouse Management (SAP EWM) 510 224 . This process applies for both inbound and outbound delivery. If no information about the country of origin is available. If you specify a batch. For the inbound delivery. EWM has access to the same information as the ERP System. At the same time.2007 Connection of Deliv.SAP Online Help 20. 2004 IT = Italy EWM Inbound / Outbound Delivery Product XYZ Batch 123 Country of Origin IT Shelf Life Expir. Process SAEWM . it generates an outbound delivery order. EWM checks whether the product is subject to batch management requirements. Results EWM has saved the information about the country of origin as a batch characteristic. and for the outbound delivery it looks for the relevant stock. EWM checks whether the batch information also contains information about the country of origin.07. 1. EWM generates an inbound delivery. Processing to Determining Country of Origin Purpose You can define the country of origin of your goods in Extended Warehouse Management (EWM). EWM copies this information to the delivery item of the inbound or outbound delivery. The ERP System sends EWM an inbound or outbound delivery with associated product information. 2004 2. 30. Prerequisites Since the information about the country of origin is found at batch level. and when the outbound delivery request is activated. When the inbound delivery notification is activated. in other words. This enables you to have EWM only use stock from a particular country of origin. EWM activates the inbound delivery notification or outbound delivery request according to your settings in Customizing. EWM does not copy anything to the delivery items. 30. The following diagram illustrates that by using an appropriate master data distribution. for example in the ERP System. 3. such as batch information. whether you have set the batch management requirement indicator in the ERP System. the process described can only occur with products subject to batch management requirements. Date Dec.. You post the goods receipt or goods issue. ERP System Inbound / Outbound Delivery Product XYZ Batch 123 Country of Origin IT Shelf Life Expir. EWM keeps the stock separated according to batches (country of origin)..

2007 SAP Extended Warehouse Management (SAP EWM) 510 225 .07.SAP Online Help 20.

see Post Processing Framework in Delivery Processing [Seite 105].2007 Connection of Delivery Processing to Post Processing Framework Use In delivery processing. For more information.07. you use the Post Processing Framework (PPF) to be able to schedule and control actions and messages for processing warehouse requests. SAP Extended Warehouse Management (SAP EWM) 510 226 .SAP Online Help 20.

For more information.SAP Online Help 20. The method returns the return code RV_RC to the schedule condition. see the Implementation Guide (IMG) for EWM under CrossProcess Settings → Delivery Processing → Actions → Configure Action Scheduling. Create condition types e. Create condition tables c. ● . To do this. When PPF checks the PPF action to be scheduled. Create field catalog b. The value zero means that the schedule condition is fulfilled and that the PPF has scheduled the PPF action. Prerequisites ● You have defined a schedule condition for the PPF action that contains the call of method /SCWM/CL_DLV_PPF_CONF=>EVALUATE.. The value zero means that a result was found.sap. you can schedule the PPF action with the Business Add-In (BAdI) EVAL_SCHEDCOND_PPF PPF: Configure Exit for Evaluating Schedule Condition. For more information about the PPF. For example. You have made the following settings for the condition technique in Customizing for Extended Warehouse Management (EWM): a. Create condition maintenance group h. the system uses this configuration. Assign determination procedure g. The condition technique works with condition records that control the scheduling of the PPF actions Creating Condition Records [Seite 229]). Condition record determination in delivery processing only returns the result of whether a condition record was found or not. you can define conditions that use certain delivery data. SAP Extended Warehouse Management (SAP EWM) 510 227 . In this action. Maintain determination procedure f. 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. Create access sequences d. You call method /SCWM/CL_DLV_PPF_CONF=>EVALUATE in your BAdI implementation for the schedule condition for the PPF action. You cannot specify any values that condition record determination then returns as a results record together with the condition record.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). Register condition maintenance group For more information.. you define schedule conditions that use the condition technique. see the SAP Help Portal help. Features Within the PPF application /SCWM/DELIVERY.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. see the method documentation.07. The schedule condition also returns a return code to the PPF. Other values indicate various error messages.

If you want to view or edit schedule conditions for PPF actions. To fill these additional fields at runtime. Not Started -> In Process. The system therefore behaves as follows: If you do not assign a determination procedure in Customizing for SAP EM. 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. EWM aggregates this field on header level. ● ● ● SAP delivers PPF actions whose schedule condition already contains the call of the configuration. If the value in this field differs for at least one item. you must define a condition record for each possible combination of status change. You can either use the fields from the default field catalog or you can add your own fields to the field catalog. for example. in the IMG for EWM. you can use BAdI /SCWM/EX_DLV_PPF_CONF BAdI: Determine Delivery Data for Customer-Defined Condition Record Fields. If you want to view and edit PPF actions. see the corresponding field help. you cannot use placeholders for the values in the condition records. choose Extended Warehouse Management → Delivery Processing → Actions → Process and Display PPF Actions. If you assign a determination procedure that matches a delivery. An exception is the Door field.SAP Online Help 20. For more information about special fields in the field catalog for the application DPP. you must also perform all the Customizing settings described under Prerequisites and you must create a suitable condition record. You can also add item fields to the default field catalog. on the SAP Easy Access screen. EWM copies the value to the header level too. the system behaves as in SAP SCM 5. for example. If the value in this field is the same for all items. on the SAP Easy Access screen. the value for the header field remains empty. Due to performance reasons.0 with regard to these actions. choose Extended Warehouse Management → Delivery Processing → Actions → Maintain Condition Records for PPF Schedule Conditions.07. Only if you do this are the schedule conditions fulfilled for the actions for this delivery. for the field /SCWM/DE_DPP_ITEM_REL. If you want to edit condition records for the schedule condition of a PPF action. SAP Extended Warehouse Management (SAP EWM) 510 228 . choose Cross-Process Settings → Delivery Processing → Actions → Change Actions and Conditions → Define Conditions. If you want to define a schedule condition for a status value that has not yet been defined in the system.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. Activities ● If you want to define the configuration of scheduling of PPF actions.

it schedules the PPF action since the delivery corresponds to all the delivery data in the condition record.07. 2. 3. Prerequisites See Configuration of PPF Action Scheduling [Seite 227]. For more information about special fields in the field catalog for the application DPP.SAP Online Help 20. Procedure . Complete the fields in the condition record and save. use the input help to select a condition type. If a PPF action for the delivery contains the call of method /SCWM/CL_DLV_PPF_CONF=>EVALUATE in the schedule condition. for example. choose Extended Warehouse Management → Delivery Processing → Actions → Maintain Condition Records for PPF Schedule Conditions (/SCWM/DLVPPFC). On the SAP Easy Access screen. the system does not display the PPF action on the user interface for the delivery. If the system does not find a suitable condition record for a PPF action.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. it has the following effect on the scheduling of the PPF action: If the system finds a suitable condition record for a PPF action... Result You have created a new condition record. Choose with the quick info text Execute. one table row corresponds to one condition record. it does not schedule the PPF action since the delivery does not correspond to all the delivery data in the condition record. Moreover. SAP Extended Warehouse Management (SAP EWM) 510 229 . Here. In the Condition Type field. 4. 1. see the long text of the corresponding field help. Specify the application DPP and the maintenance group that you have defined in Customizing. for the field /SCWM/DE_DPP_ITEM_REL.

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

1. For more information. 2.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.. 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. Result EWM has automatically generated the VAS order. 3. EWM changes the status VAS order of the warehouse request item (see also: Updating the Warehouse Request Using the VAS Order [Seite 232]). EWM saves the number of the VAS order as a document flow for the warehouse request item. 4. You have defined a packaging specification [Seite 494]. In the goods receipt process. Prerequisites You have defined in your system that you want EWM to create VAS orders automatically. SAP Extended Warehouse Management (SAP EWM) 510 231 . If you have defined in Customizing that EWM is not to generate the VAS order automatically. see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Value-Added Services → Define Relevance for VAS Order. EWM sets the VAS Order status of the warehouse request item to Generated. When you edit the VAS order.SAP Online Help 20. then the VAS Order status has the value Not Relevant. and does so if this is the case. EWM checks whether it has to generate a VAS order automatically. If you have activated the VAS Order in the status profile of the item type for the warehouse request item. You can use it for the confirmation of services [Seite 538]. You get a delivery from the ERP system or create a delivery manually.

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). that is. SAP Extended Warehouse Management (SAP EWM) 510 232 . If required. 1. Deleting a VAS Order . for the status profiles of the item types for which you want to update the warehouse request. Changing a VAS Order 1. EWM updates the warehouse request item.. EWM updates the warehouse request item where required. you have activated the status DWV in the respective status profiles.SAP Online Help 20. If you set the status of the VAS order to Completed or Completed with Quantity Variance. these are profiles /SCWM/OUT_PRD_DLV_STANDARD and /SCWM/INB_PRD_DLV_STANDARD.. if the status of the VAS order changes. EWM also changes the VAS Order status to In Process.. 2. EWM deletes the document flow for the warehouse request item. EWM sets the VAS Order status to Completed. Prerequisites In the Implementation Guide (IMG) for EWM under Cross-Process Settings → Delivery Processing → Status Management → Define Status Profiles. and sets the VAS Order status to Relevant. 2. You edit the VAS order and with that change the status of the VAS order [Seite 538]. Process .07.. For example. You delete the VAS order. EWM automatically adjusts the VAS Order status of the warehouse request item: ○ ○ If you set the status of the VAS order to In Process. you can generate a new VAS order [Seite 536] manually. In the standard SAP system for example.

EWM also changes the value-added service order [Extern] (VAS order) correspondingly. and changes the VAS Order status of the warehouse request item back to In Process. You can only delete a warehouse request item if the VAS order is not yet in process.2007 Updating the VAS Order Using the Warehouse Request Purpose When you change a warehouse request item in Extended Warehouse Management (EWM). EWM updates the VAS order. the VAS order must be completed and the VAS Order status of the delivery item must have the value Completed. SAP Extended Warehouse Management (SAP EWM) 510 233 . EWM does nothing. EWM deletes the VAS order.SAP Online Help 20. 1. You delete an item of a warehouse request for which a VAS order exists. if required.. EWM changes the status of the VAS order from Completed back to In Process. If the VAS Order status currently has the value Completed. and you want EWM to update the status of the relevant VAS order. 2. Deleting the Warehouse Request ...07. If you increase the delivery quantity of a warehouse request item.. Prerequisites ● ● A VAS order exists for the warehouse request item. If you change a warehouse request. Process Changing the Warehouse Request . If the VAS order is not yet in process. If you reduce the delivery quantity of a warehouse request item.

SAP Extended Warehouse Management (SAP EWM) 510 234 . If you want to change the settings of the preconfigured item types. the kit information in the outbound delivery forms the basis for kitting. 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. EWM generates these items without an error status and considers these items in warehouse processing. We recommend that you use the standard profiles shipped by SAP. In EWM. ● 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. ● When EWM generates a warehouse request with kit items.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]. for example. You can use these to individually control the kit items in an outbound delivery. you must note the following regarding the profiles.07. kits in kits. EWM can only receive information about kits in outbound deliveries.SAP Online Help 20. that is. 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. Structure The outbound delivery contains the following items as kit information. and the kit component item is in turn a subitem of this item. EWM does not support nested kits. If you follow the settings for the status profile and the quantity offsetting profile. SAP delivers preconfigured item types as standard for these kit items. Replaced kit component item [Extern] The kit header item is a direct predecessor of this item. This means that you must set the corresponding quantity roles in this quantity offsetting profile to inactive. you must therefore deactivate the picking relevance and the goods movement relevance. it checks the settings of the item types of the kit header items and of the replaced kit component items.

see the Implementation Guide (IMG) for EWM under Goods Issue Process → Make Settings for Kitting. otherwise the delivery quantity correlation [Seite 238] returns incorrect results. SAP Extended Warehouse Management (SAP EWM) 510 235 . That is.07.SAP Online Help 20. pack. The ERP system also saves the kit as items in the outbound delivery (see also Kit to Order [Seite 349]). This enables you to be sure that EWM only ships the kit together with the other delivery items. Make sure that the ERP system always sends EWM information about entire kits. in other words. you can pick. for example. A kit header item and its related subitems can be part of a delivery group [Extern] together with other delivery items. ● Integration with warehouse processing Warehouse processing in EWM handles kit component items in the same way as outbound delivery items. 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]). section Requirements. ● Integration with value-added service orders (VAS orders) You can create a VAS order for the kit header item. the quantities of the kit components must be enough to create entire kits. If you change the quantities of a kit component item in EWM through a pick denial.2007 For more information about settings for kits in the delivery. EWM recalculates the quantities of the other kit component items and of the kit header item (quantity correlation). and load them. Integration ● Integration with the ERP system EWM receives information about the kit as part of the outbound delivery from the ERP system.

first choose Subitem and the Split Up Outbound Delivery. 4. set the Create Kit Header Item indicator in Customizing. To do this. Item Split for Packed Kits . You can only split entire kits. You select the kit header item and split the warehouse request for the outbound delivery order... if you want to ship finished kits before the remaining kits have been completed. it generates new kit header items and kit component items that are the same as the original kit in EWM. If the system is to automatically generate an HU item for the kit header in the pickhandling unit (pick-HU). The quantity of the kit header item is greater than one. Extended Warehouse Management (EWM) supports you. choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order. 2. for example. To do this. EWM copies the kit. The process flow is the same as for standard outbound delivery items.SAP Online Help 20. You cannot perform a batch split for the kit header item or a replaced kit component item. You can copy each of the split kits to one separate outbound delivery. on the SAP Easy Access screen.. To do this. EWM calculates the kit component quantities automatically (see Delivery Quantity Correlation for Kits [Seite 238]).. for example.07. 7. 6. 1. You select the warehouse request for the outbound delivery order. by calculating the kit component quantities automatically (see Delivery Quantity Correlation for Kits [Seite 238]). Prerequisites ● ● ● ● An outbound delivery with kit header items and kit component items exists. 1. see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Issue Process → Outbound Delivery → Define EWM-Specific Settings for Item Types. You cannot split kit component items or replaced kit component items. choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order.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. All kit component items are completely picked. 5. on the SAP Easy Access screen. You select the warehouse request for the outbound delivery order. However. Process Item Split for Unpacked Kits . SAP Extended Warehouse Management (SAP EWM) 510 236 . You perform an item split. that is. You specify the number of kit header items that are to be generated. 3. For more information about the packing profile. You specify the delivery quantity in the kit header items and confirm your entries by choosing ENTER.

4. You can now copy the split kit to one separate outbound delivery. first choose Split Item and then Create. 3. You choose the HU tab page and select all the HUs that you want to ship in advance. You can ship these kits by generating an outbound delivery for each of the new kit header items. Results You have performed an outbound delivery split and generated split kits. that is. EWM aggregates the quantities of the packed kits using the HU dummy item.07.SAP Online Help 20. 6. 5. 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.2007 2. You create new split items. SAP Extended Warehouse Management (SAP EWM) 510 237 . To do this. EWM copies the kit.

it may be the case that EWM also recalculates the delivery quantities for the related kit component items that neither you nor EWM changed. EWM always bases its calculation on the current delivery quantity ratios between kit header item and kit component items. see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Delivery Processing → Field Control → Define Field Control Profiles. depending on other items. When EWM recalculates the delivery quantities for kit header items. If you or the system have already executed this batch split in the ERP system. 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. the delivery quantities with their hierarchical dependencies. that is. The ERP system sends this data to EWM. EWM derives open delivery quantities for these additional delivery quantities. SAP Extended Warehouse Management (SAP EWM) 510 238 . for creating warehouse tasks belonging to the kit. the system also sends the resulting batch subitems to EWM. 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. you define the field control profile in such a way that the field cannot be modified for the delivery quantity. or when you manually change a delivery quantity for a kit component item. you can adjust items with fixed quantities or discount in kind on a quantity basis. EWM recalculates the delivery quantities of all delivery items belonging to the kit. in Customizing. or when you manually change a delivery quantity for a kit header item. for example. Either you or the system can execute a batch split for kit component items. The original ‘delivery quantity structure’. you must have configured the item types for the relevant delivery items appropriately in Customizing. For example. For more information. EWM calculates the delivery quantities for new and changed kit header items and kit component items. Prerequisites For EWM to be able to process kits correctly with their hierarchy [Extern]. are already saved in the delivery in the ERP system. ● When EWM performs a pick denial. For example. Integration When calculating the delivery quantity ratios.2007 Delivery Quantity Correlation for Kits Use If you or the system make changes to the delivery quantity.SAP Online Help 20. Features ● When EWM performs a split. EWM recalculates the delivery quantities from bottom to top through the hierarchy levels.07.

When you perform a pick denial at batch item level. If the total is greater in the batch split. You have a kit component item 10 for product A with a delivery quantity of 10 pieces. This enables you or the system to add additional batch subitems at a later time. If these items also contain batch subitems.07. you notice that batch 2 only contains 2 pieces. When you perform the delivery split manually on the user interface. EWM ensures that the total of the batch subitem delivery quantities is not greater than the delivery quantity of the split kit component item. EWM does not distribute the delivery quantity across all batch subitems. Recalculation for Delivery Quantity Changes from External Systems For requests for delivery quantity changes from external systems. or when EWM performs a batch split automatically. EWM leaves the delivery quantity for batch subitem 65 as 4. Activities You can trigger delivery quantity changes that lead to a delivery quantity correlation by: SAP Extended Warehouse Management (SAP EWM) 510 239 . The requested delivery quantity of the kit component item is 5. For this reason. the delivery quantity is again not changed. you only have to enter the delivery quantity of the split kit header items. Batch subitem 65 contains a delivery quantity of 2 and batch subitem 67 contains a delivery quantity of 3. EWM first recalculates at the level of the kit component item. EWM expects the delivery quantity correlation to have already been performed in the external system. You enter a delivery quantity of 4 for both batch subitems. the delivery quantity is not changed. ● You have a kit component item 10 with batch subitems 65 and 67. You perform a pick denial and specify the process code QTY-2. When you reduce the delivery quantity of a kit header item. and sets the corresponding process code for the missing delivery quantity. the delivery quantity of the batch subitems is changed corresponding to the delivery quantity. EWM then recalculates the delivery quantities for all kit component items across the hierarchy levels. but changes the delivery quantity of batch subitem 67 to 1. Here. Delivery Quantity Recalculation for the Delivery Split When you or the system perform a delivery split for a kit header item. EWM also adjusts the delivery quantity of the kit component item. This delivery item 10 consists of batch subitem 15 for batch 1 with 6 pieces. This fulfils the requested delivery quantity of 5. The delivery quantity correlation then automatically calculates the delivery quantities of all other subitems. EWM performs a corresponding delivery quantity correlation. The correlation function then calculates the delivery quantity of the kit header item. However.2007 EWM considers the process code in the delivery quantity correlation. Delivery Quantity Recalculation for the Batch Split When you perform a charge split manually on the user interface prior to picking. EWM also recalculates the delivery quantities (such as open pick delivery quantities) for these across all hierarchy levels. Since the delivery quantity for batch 2 cannot be fulfilled.SAP Online Help ● 20. and batch subitem 17 for batch 2 with 4 pieces. EWM calculates and distributes the kit quantities contained in this ‘original’ kit proportionately across the new kits that have been split up. EWM does not recalculate the delivery quantities. from top to bottom. ● ● If the total is the same in the batch split. EWM also reduces the delivery quantities of the related kit component items. During picking. from top to bottom. If the total is less in the batch split.

Change the delivery quantity. or EWM changes the delivery quantities when the system updates a delivery in the background. Change the delivery quantity.07. choose Extended Warehouse Management → Delivery Processing → Inbound Delivery → Maintain Inbound Delivery and then choose the Quantity column on the Items tab page. choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery and then choose the Quantity column on the Items tab page. choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order and then choose the Quantity column on the Items tab page. or EWM changes the delivery quantities when the system updates a delivery in the background. Change the delivery quantity. Example The following figure shows you the hierarchy for a kit in the ERP system together with the respective delivery quantities.SAP Online Help ● 20. ○ ○ ● ● 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. ● Performing delivery splits [Seite 236] Either you perform a delivery split manually on the user interface. SAP Extended Warehouse Management (SAP EWM) 510 240 . On the SAP Easy Access screen.2007 Directly changing the delivery quantity field on the user interface: ○ On the SAP Easy Access screen. On the SAP Easy Access screen.

and the delivery quantity of replaced kit component 40 to 10 pieces. and kit component item 60 for kit component 4 has a delivery quantity of 15 pieces. In EWM. Kit component item 20 consists of batch subitems 25 and 27. Kit component item 50 for kit component 3 has a delivery quantity of 5 pieces. Replaced kit component item 40 consists of delivery items 50 and 60. 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 . and batch subitem 27 for batch 2 has a delivery quantity of 4 pieces. kit component item 30 for kit component 2 has a delivery quantity of 20 pieces. 1. from bottom to top. 2. EWM uses the correlation function to calculate the new delivery quantities. . for example.. Batch subitem 25 for batch 1 has a delivery quantity of 6 pieces. due to a pick denial. 3. and batch subitem 67 for batch 4 has a delivery quantity of 13 pieces. a.07.2007 You have a delivery item 10 for the kit header with a delivery quantity of 2 pieces. In the case of batch subitems.. and delivery item 40 for the replaced kit component has a delivery quantity of 20 pieces.SAP Online Help 20. Batch subitem 65 for batch 3 has a delivery quantity of 2 pieces. The ERP system sends the data for the kit to EWM. you reduce the delivery quantity of kit component item 30 to 12 pieces. Kit component item 60 consists of batch subitems 65 and 67. Kit component item 20 for kit component 1 has a delivery quantity of 10 pieces. EWM always changes the delivery quantities “backwards“ in terms of the sequence of the items. Delivery item 10 consists of kit component items 20 and 30 and delivery item 40 for the replaced kit component. EWM changes the delivery quantities across the hierarchy levels.

since a fixed ratio of 1:10 is defined. The following figure shows you the hierarchy of the kit in EWM following the delivery quantity correlation. However.07.SAP Online Help ■ ■ ■ ■ ■ 20. together with the respective delivery quantities. Kit header item 10: reduce to 1 piece ■ b. remains at 2 pieces Kit component item 60: reduce to 5 pieces Kit component item 50: no change. since a fixed ratio of 1:5 is defined. EWM reduces the delivery quantity of this item by 10 pieces. remains at 5 pieces Kit component item 40: reduce to 10 pieces Kit component item 30: reduce to 10 pieces. EWM then executes the following delivery quantity change across the hierarchy levels from top to bottom: Kit component item 20: reduce to 5 pieces. although you only reduced the delivery quantity by 8 pieces.2007 Batch subitem 65 for batch 3: no change. SAP Extended Warehouse Management (SAP EWM) 510 242 .

EWM changes the stock type in the inbound delivery from unrestricted-use stock to stock in quality inspection. the stock type in the inbound delivery. EWM updates the document flow.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. EWM creates inspection documents in the background.07. For example. EWM creates the inspection documents later. see Quality Inspection [Seite 866] and Creation of Inspection Document [Seite 869]. 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. Once EWM has created the inspection documents. Integration See Creation of Inspection Document [Seite 869] Prerequisites ● ● ● You have carried out the Customizing for creating inspection documents [Seite 869]. If necessary. SAP Extended Warehouse Management (SAP EWM) 510 243 . Here. EWM only creates the inspection document once you have specified the batch number. EWM copies the inspection document number to the inbound delivery. In the delivery. EWM always updates the status data. You have defined inspection rules (see Master Data [Seite 855]). and. EWM is to create an inspection document when the inbound delivery is activated. you can view all of the inspection documents for an inbound delivery in document flow. you have specified all the data necessary for the creation of an inspection document.SAP Online Help 20. For example. EWM updates the stock type. it updates the document flow for the reference document types Q01 and Q03. Features In the following cases. For more information. it simultaneously updates the inbound delivery. Thus. EWM also sets the status data in this case. the result of quality inspection planning could be that EWM is not to carry out a quality inspection. Regardless of whether you carry out a quality inspection or not. The batch number is required for creation. the status for inspection planning. In addition. if necessary. If not all of the necessary data exists in the delivery by the time at which EWM is to create the inspection documents. For example. 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.

2007 Activities If you want to display the statuses QM Inspection Planning and QM Counting Planning. Go to the Status tab page. choose Extended Warehouse Management → Delivery Processing → Maintain Inbound Delivery.SAP Online Help 20. on the SAP Easy Access screen.07. SAP Extended Warehouse Management (SAP EWM) 510 244 .

You can change this batch. see the Implementation Guide (IMG) for EWM under Master Data → Product → Define Number Range for Batch. As soon as you save the the Batch field empty and choose the function inbound delivery. leave Batch. or the expiry date. Features A batch number can be specified via a system (an ERP system. ● ● SAP Extended Warehouse Management (SAP EWM) 510 245 . choose Extended Warehouse Management → Delivery Processing → Inbound Delivery → Maintain Inbound Delivery Order. This means that you work continuously with homogenous partial quantities that are. You can also directly specify the existing batch number for outbound deliveries. it does not originate from another system.2007 Connection of Delivery Processing to Batch Management Use You can work with batch numbers in both inbound and outbound deliveries. You can also specify the batch in the corresponding warehouse task. minimum shelf life. Go to the form view and specify the batch number. When you are processing the inbound or outbound delivery. EWM creates a batch subitem with the confirmed quantity and batch. on the SAP Easy Access screen. Here. For more information. that is. on the SAP Easy Access screen. You specify a known batch number directly in EWM. EWM creates a corresponding subitem for the batch. for example) or you specify it directly in EWM. EWM determines where the batch information originates from and whether you can still change the batch number. Go to the form view and enter a batch number in the Batch field. Select a batch and choose the function Batch Subitem. for example. required by law or because of hazardous substance directives. You can split a batch in the inbound delivery. EWM copies the batch characteristics to the delivery. The following options exist: ● A different system specifies a batch number. To do so.SAP Online Help 20. For example. you cannot change the batch number. You can only change the batch number before saving. EWM creates a new batch number. Using a determination indicator. EWM copies the batch to the delivery. choose Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order. on the SAP Easy Access screen. for example. the country of origin. for example in a purchase order in the ERP system.07. you have entered the batch in the inbound delivery of the ERP system. Prerequisites If you want to create new batch numbers. you have defined number ranges for batches in Customizing for Extended Warehouse Management (EWM). that is. A different system proposes a batch. For this. To do this. To do this. EWM can also create new batch numbers for inbound deliveries. choose Extended Warehouse Management → Delivery Processing → Inbound Delivery → Maintain Inbound Delivery Order. You must use this batch number.

see the IMG for EWM under Cross-Process Settings → Delivery Processing → Status Management → Define Status Profiles. ERP generates a corresponding outbound delivery that contains the account assignment information from EWM. You have defined a process profile for the pickup in Customizing for EWM.SAP Online Help 20. see the documentation for the Business Configuration Sets (BC Sets) /SCWM/DLV_OUTBOUND_DIRODO_1 and /SCWM/DLV_OUTBOUND_DIRODO_2.07. EWM generates a corresponding outbound delivery order. ● ● ● For more information. Goods issue for the pickup can be planned or unplanned. Prerequisites ● You have defined the account assignment categories in Customizing for EWM. If you use multiple account assignment objects for a delivery item (multiple account assignment [Extern]). see the Implementation Guide (IMG) for EWM under Goods Issue Process → Outbound Delivery → Define Account Assignment Category and Allow in Warehouse Number. For more information. It does not consider partial quantities. For more information. For more information. The account assignment object always refers to the complete delivery quantity of a delivery item. ● Planned pickup SAP Extended Warehouse Management (SAP EWM) 510 246 . You have defined a status profile for the pickup in Customizing for EWM. This contains the account assignment information from ERP. Integration If you work with a planned pickup. When you create or change a direct outbound delivery order. see the IMG for EWM under Cross-Process Settings → Delivery Processing → Process Management and Control.2007 Integration of Delivery Processing with Pickup Use Delivery processing supports goods issue for the pickup [Extern]. On the SAP Easy Access screen. You cannot change this account assignment information in EWM. change. you generate a direct outbound delivery order [Extern] in EWM. you generate an outbound delivery in ERP. EWM distributes it to ERP. or delete the account assignment information in unplanned outbound delivery orders for the pickup until goods issue has been posted. This is to avoid a duplicate allocation. You have assigned the process profile for the pickup to a document type in Customizing for EWM. only one account assignment object is permitted to be non-static. see the IMG for EWM under Goods Issue Process → Outbound Delivery → Manual Settings → Define Document Types for Outbound Delivery Process. The validation checks the type of account assignment category and its uniqueness. For more information. ERP distributes it to Extended Warehouse Management (EWM). choose Tools → Customizing → Business Configuration Sets → SCPR3 → Display and Maintain BC Sets. It also checks the type of the existing account assignment object. If you work with an unplanned pickup. You can change the account assignment information in EWM. Features ● Unplanned pickup You can create. EWM performs a validation.

for example. for example.07. and the account assignment object. EWM performs a validation when it activates a planned outbound delivery request. on the SAP Easy Access screen. or delete the account assignment data in planned outbound delivery orders for the pickup. only one account assignment object is permitted to be non-static. As is the case for unplanned pickup.SAP Online Help 20. The validation checks the type of account assignment category and whether it occurs only once per delivery item. ● 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). See also: ● Direct Outbound Delivery Order [Seite 167] SAP Extended Warehouse Management (SAP EWM) 510 247 . choose Extended Warehouse Management → Delivery Processing → Outbound Delivery -> /SCWM/SGI – Pickup. Activities ● If you want to generate or edit direct outbound delivery orders for the pickup.2007 You cannot create. EWM displays the account assignment category. choose Extended Warehouse Management → Delivery Processing → Outbound Delivery -> /SCWM/SGI – Pickup. change. This is to avoid a duplicate allocation. EWM displays the details of the item. on the SAP Easy Access screen. cost center. Select a delivery item and choose Expand/Zoom In. EEG1. On the Account Assignment tab page. The indicator comes from the defined document type OPIG. It also checks the type of the existing account assignment object. If you want to check the account assignment category on the user interface for the outbound delivery order. Display a delivery document.

. Creation of a Warehouse Request for Outbound Delivery Order [Seite 116] Communication is asynchronous and uses queued Remote Function Call (qRFC) technology. In EWM. 1. 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 interfaces between EWM and the ERP system itself are based on deliveries.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. For more information. 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 2 Split message 3 4 Completed executed delivery 1 SAP SCM. EWM . see Warehouse Request for Inbound Delivery or Outbound Delivery Order [Seite 112].07. Creation of a Warehouse Request for Inbound Delivery [Seite 113]. Distribution of deliveries SAP Extended Warehouse Management (SAP EWM) 510 248 . changes to. This technology guarantees serialization of the messages. and confirmation of delivery-relevant data..SAP Online Help 20. the ERP system triggers subsequent communication steps for specific processes. In the ERP system.

Send confirmation of deliveries from EWM for follow-on functions in the ERP system (for example. goods issue. customers. plants) Product master data ● You have made the Customizing settings for ERP integration. Confirmation of an inbound and outbound delivery split from EWM to the ERP system 4. decentralized EWM.2007 Send from ERP system to EWM Send from EWM to the ERP system (for example.07. vendors. transportation service providers) Location master data (for example.SAP Online Help ○ ○ 20. changed ASN from vendor) 3. Features The following functions are available for EWM and the ERP system for the purpose of processing inbound and outbound deliveries. confirmation before goods issue for invoicing before goods issue) Prerequisites ● You are using an ERP system. customers. Changes to deliveries ○ ○ Send from EWM to the ERP system (for example. vendors. confirmation of a pick denial from EWM to the ERP system) Send from the ERP system to EWM (for example. choose Interfaces → ERP Integration. for manual inbound deliveries) 2. EWM receives the requests for goods movements from the ERP system. goods receipt. In the Implementation Guide (IMG) for EWM. These include: ○ ○ ○ ● Partner master data (for example. you define for each plant and storage location whether you manage your warehouse in a separate. ● 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 . Transmit all information to EWM that EWM requires for the goods movements. Here.

and Interfaces for Communication from EWM to the ERP System [Seite 257]. SAP Extended Warehouse Management (SAP EWM) 510 250 . see Processing Inbound Deliveries [Seite 251].07. you must perform the relevant processes using the appropriate user interface [Seite 138].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.SAP Online Help ○ ○ ○ ○ ○ 20. Processing Outbound Deliveries [Seite 253] . Activities In order to create messages.

○ Inbound delivery notifications that EWM receives can contain handling unit data (HU data). you can start the message again in the qRFC inbound queue in the ERP system. and confirm delivery-relevant data. see Communication from EWM to the ERP System [Seite 248]. Only EWM supports automatic packing. Prerequisites To read the description of the prerequisites. The ERP system then continues processing accordingly. ● Receipt of a change request for inbound deliveries from the ERP system in EWM SAP Extended Warehouse Management (SAP EWM) 510 251 . change. Delivery items that do not contain errors are open for execution even if the inbound delivery contains other incorrect delivery items. see Communication from EWM to the ERP System [Seite 248]. This is taken either from the electronic ASN from the vendor or was entered during manual packing in the ERP system. EWM uses the inbound delivery notification to create an inbound delivery. EWM blocks the incorrect delivery items for execution. EWM can also receive an inbound delivery notification as a result of inbound deliveries created in the ERP system. The following rules apply when solving the errors: ○ You can remove the errors in the ERP system. If errors occur during ASN validation in the ERP system.SAP Online Help 20. EWM processes this change message as long as the inbound delivery is not yet in processing in EWM. For more information about Customizing the integration between EWM and the ERP system. Integration To read the integration description. After you have solved the error in the ERP system manually. which was originally sent by EWM. see Inbound Delivery Notification [Seite 87]. The ERP system sends a change message to EWM. You can remove the errors in EWM. the ERP system returns the message.07. The ERP system creates an inbound delivery and sends an inbound delivery notification to EWM. the ERP system gives the incorrect delivery items an error status before sending the information to EWM. see the Implementation Guide (IMG) for EWM under Interfaces → ERP Integration. You cannot use automatic packing in the ERP system. to the qRFC inbound queue. For more information. 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.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. 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. In this case. or whether you need to manually process the inbound delivery again in the ERP system before the system processes the goods receipt confirmation.

you must perform the relevant processes using the appropriate user interface [Seite 138] . You can specify whether there should be a confirmation to the ERP system for each individual partial goods receipt. These number ranges must not overlap with the number ranges in the ERP system. EWM determines the document number and item number in the ERP system. EWM creates a material document for these postings. If the inbound delivery is not yet being processed. SAP Extended Warehouse Management (SAP EWM) 510 252 . it sends a rejection message to the ERP system. EWM sends the entire document and the ERP system replaces the entire document with the data from EWM. It forwards them to EWM. Activities In order to create messages for processing inbound deliveries. if the status Warehouse Activity does not have the value Not Started.SAP Online Help 20. If you want to create inbound deliveries manually in the ERP system. the document type or company code). choose Logistics → Logistics Execution → Inbound Process → Goods Receipt Automotive → Goods Receipt Transaction. EWM sends these to the ERP system before confirming the goods receipt.07. and reports them to the ERP system. ● 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. it sends a confirmation message to the ERP system. The ERP system replaces the header data accordingly. ● Notification of an inbound delivery split from EWM to the ERP system You can split inbound deliveries in EWM. on the SAP Easy Access screen. If EWM cannot replace the existing inbound delivery. For more information about the interfaces that enable these functions. The ERP system does not overwrite any data that cannot be provided by EWM (for example. you can make either partial (partial goods receipt) or complete goods receipt posting. EWM only sends the header data for the inbound delivery to the ERP system. which triggers confirmation of the correction or cancellation to the ERP system. If it can replace the inbound delivery. or for the entire delivery. EWM replaces the inbound delivery. You must have defined the number range intervals in Customizing. ● Confirmation of a goods receipt from EWM to the ERP system For inbound deliveries. If you also replace relevant item data in EWM. The ERP system receives these messages and validates them. For more information. see Interfaces for Communication from EWM to the ERP System [Seite 257]. EWM creates new inbound deliveries for this delivery split. in other words.2007 The vendor can send a new ASN or an ASN rejection for an existing inbound delivery. see Inbound Delivery [Seite 88] and Creation of a Warehouse Request for an Inbound Delivery [Seite 113]. If you only change the transit status in EWM. ● 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 checks whether it can replace the existing inbound delivery. You can also specify whether EWM should also transfer the current HU data with the goods receipt confirmation to the ERP system.

the ERP system can distribute these to EWM. You cannot process these outbound delivery orders.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. you cannot create an outbound delivery for an outbound delivery order that EWM has created from an unchecked delivery in the ERP system.07.SAP Online Help 20. see Communication from EWM to the ERP System [Seite 248]. ○ ○ A deletion message for deleting an outbound delivery request. ● Notification of an outbound delivery change to the ERP system If you create a pick denial [Seite 327] in EWM. then it sends two messages to EWM. 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. change. Integration To read the integration description. ● Receipt of a checked outbound delivery from the ERP system If the ERP system converts unchecked outbound deliveries into checked outbound deliveries. Features ● Receipt of an unchecked outbound delivery from the ERP system If you work with unchecked outbound deliveries in the ERP system. The message to the ERP system contains an indicator for the SAP Extended Warehouse Management (SAP EWM) 510 253 . The pick denial causes a reduction in the delivered quantity. The ERP system creates outbound delivery orders for unchecked deliveries. The ERP system reports the change to SAP Customer Relationship Management (SAP CRM). This triggers confirmation of the change to the ERP system. you can create an outbound delivery for an outbound delivery order that EWM has created from a checked delivery of the ERP system. You can only use them for a preview. and confirm delivery-relevant data. see Communication from EWM to the ERP System [Seite 248]. and an outbound delivery order that EWM created for the unchecked outbound delivery. EWM creates the following documents for unchecked outbound deliveries: ○ ○ An outbound delivery request An outbound delivery order In EWM. EWM creates the following documents for checked outbound deliveries: ○ ○ An outbound delivery request An outbound delivery order In EWM. then EWM reduces the delivery quantity and writes an exception code in the outbound delivery order. Prerequisites To read the description of the prerequisites.

If EWM rejects the quantity change. SAP Extended Warehouse Management (SAP EWM) 510 254 . The Warehouse Activity status for the outbound delivery order in this case is Warehouse Act.SAP Online Help 20. even before the goods issue. it reports the rejection of the quantity change to the ERP system. The ERP system forwards this data to the invoicing system in SAP CRM.07.2007 quantity change due to a pick denial./Part. for example. For automatic creation. You must have defined the number range intervals in Customizing. if the requested quantity does not fit onto the means of transport. EWM triggers confirmation of the data to the ERP system for the purpose of direct billing. ● Communication of an outbound delivery split to the ERP system EWM can split outbound delivery order. EWM determines the document number and item number in the ERP system. if necessary. For more information about processing waves. ● 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. This message to EWM contains an indicator for delivery creation. You can only cancel an outbound delivery if it does not have the status In Transit. For checked deliveries. These number ranges must not overlap with the number ranges in the ERP system. Completed. it reports the execution of the quantity change to the ERP system. ● Direct billing or invoicing before goods issue You can print the invoice in the warehouse. which EWM reports to the ERP system. EWM sets this indicator in the outbound delivery order in the Wave Priority field. New outbound deliveries are generated by this split. This BAdI contains the method CRM_DATAEXCH_R3D_MBDOC_FILL. EWM accepts a quantity change as long as the outbound delivery order is not yet being processed. EWM rejects any quantity changes for outbound delivery orders that are already in processing. based on sales order changes in SAP CRM. based on new assignments of order confirmations by SAP Advanced Planning & Optimization. see Wave Management [Seite 766]. in Customizing choose Customer Relationship Management → Transactions → Settings Before Sales Transactions → Business Add-Ins → Business Add-In for Data Exchange. If EWM accepts the quantity change. ● Quantity change requests from the ERP system EWM can execute quantity change requests for the following: ○ ○ For checked deliveries. based on a confirmation of a pick denial. EWM uses an outbound delivery order to create an outbound delivery before the goods issue posting. After automatic creation of the outbound delivery. 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 you are using the Business Add-In (BAdI). EWM must also have set the Loading status to Started. The ERP system can create a new checked delivery for the missing quantity and can distribute this to EWM. If an outbound delivery order has this indicator. which you can use to set an indicator to trigger a new availability check. you can use this indicator to perform another round of sourcing. EWM creates the outbound delivery automatically. To use the BAdI. EWM uses this to take the outbound delivery order immediately into account during wave pick creation.

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]. SAP Extended Warehouse Management (SAP EWM) 510 255 . using an interface for communicating between EWM and ERP. EWM sends this to the ERP system immediately after saving.2007 For more information about Customizing for number range intervals.07. Activities In order to create messages for processing outbound deliveries. to ERP system If you create and save a direct outbound delivery order [Seite 167] manually in EWM without errors.SAP Online Help 20. you must perform the relevant processes using the appropriate user interface [Seite 138] . see the Implementation Guide (IMG) for EWM under Interfaces → ERP Integration → Delivery Processing → Define Number Ranges for ERP Documents. see Interfaces for Communication from EWM to the ERP System [Seite 257]. For more information about the interfaces that enable these functions. ● Replication of outbound delivery orders that were created manually in EWM.

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.

see the function module description for /SCWM/INB_DLV_SAVEREPLICA. /SPE/INB_DELIVERY_CONFIRM_DECENTRAL For more information.SAP Online Help 20. see the function module description for /SPE/INB_DELIVERY_CONFIRM_DECENTRAL For more information.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. /SCWM/INB_DLV_SAVEREPLICA For more information. see the function module description for /SPE/INB_DELIVERY_SAVEREPLICA. 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_REPLACE SAP Extended Warehouse Management (SAP EWM) 510 257 .07.

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. BAPI_OUTB_DELIVERY_CO NFIRM_DECENTRAL BAPI_OUTB_DELIVERY_CH ANGE For more information. see the function module description for /SPE/INB_DELIVERY_SPLIT.07. see the function module description for BAPI_OUTB_DELIVERY_CO NFIRM_DECENTRAL.SAP Online Help 20. see the function module description for BAPI_OUTB_DELIVERY_CH ANGE. see the function module description for /SPE/INB_DELIVERY_RESPONSE. see the function module description for /SCWM/INB_DELIVERY_REPLACE. goods issue. For more information. see the function module description for /SCWM/OUTB_DLV_SAVERE PLICA.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. /SPE/INB_DELIVERY_SPLIT For more information. 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. /SPE/INB_DELIVERY_RESPONSE For more information. SAP Extended Warehouse Management (SAP EWM) 510 258 .

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. For more information.SAP Online Help ERP system) Reversal of goods issue (EWM → ERP system) /SCWM/OUTB_DLV_CHANG E Delete unchecked deliveries (ERP system → EWM) 20. choose Tools → ABAP Workbench → Development → Function Builder. SAP Extended Warehouse Management (SAP EWM) 510 259 . see the function module description for BAPI_OUTB_DELIVERY_REJ ECT. see the function module description for BAPI_OUTB_DELIVERY_SPL IT_DECENTRAL. see the function module description for /SPE/OUTB_DELIVERY_SAV EREPLICA. For more information. 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. For more information. see the function module /SCWM/OBDL_CHNG_QUAN _MUL. see the function module description for /SCWM/OUTB_DLV_CHANG E.2007 For more information.07. For more information.

● To carry out functional enhancements for delivery processing. see the Implementation Guide (IMG) for EWM under Business Add-Ins (BAdIs) for Extended Warehouse Management. 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. Select the desired BAdI and choose Documentation for IMG Activity.SAP Online Help 20. 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. For more information about Business Add-Ins (BAdIs).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). EWM shows you the BAdI description of the IMG. see the relevant BAdI documentation in the Implementation Guide (IMG) for EWM. 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. SAP Extended Warehouse Management (SAP EWM) 510 260 . Activities ● To call the BAdI documentation.07.

Activities 1. and therefore to adapt it to your requirements. 6.07. You can extend these structures using append structures. 5. EWM offers a range of Business Add-Ins (BAdIs) that you can use to fill the new fields with data. see Extending Tables and Structures [Extern]. Create an append structure and enhance the append structure by adding your own fields.SAP Online Help 20. 3. enter the structure that you want to enhance using an append structure. The ABAP Dictionary: Initial Screen screen appears. Features For the document categories for the warehouse request. In the Data Type field. You can use this method to add further structures to tables and structures. Choose Data Type. 2. For more information. 4. in Customizing for Extended Warehouse Management under Business Add-Ins (BAdIs) for Extended Warehouse Management enter the relevant BAdIs. On the SAP Easy Access screen. choose Tools → ABAP Workbench → Development → Dictionary. Integration EWM uses the append technique for the data enhancement. see Append Structure [Extern]. 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. For the data enhancement for messages to the decentralized ERP system. This means that an enhancement is simultaneously present in more than one document category. Enter data into the new fields. Choose Change. SAP Extended Warehouse Management (SAP EWM) 510 261 . EWM offers extendable structures for the document header and document item.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. To do this. For more information. 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 Online Help 20.07.2007 SAP Extended Warehouse Management (SAP EWM) 510 262 .

see the IMG for EWM under Cross-Process Settings → Warehouse Task → Layout-Oriented Storage Control or Process-Oriented Storage Control. You can only execute complex putaway processes by using handling units. 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. 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. Extended Warehouse Management (EWM) contains putaway strategies [Seite 375] to simplify the search for appropriate storage bins. repacking). SAP Extended Warehouse Management (SAP EWM) 510 263 . Prerequisites ● You have defined the following basic settings in Customizing for Extended Warehouse Management (EWM): Basic settings are. for example. for example: IMG Activity Storage types. You can put away your products directly or through storage control [Seite 334]. 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. counting requests. 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. work centers [Extern]. For more information about defining putaway steps. storage area.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.07.SAP Online Help 20.

The system updates. If you reject the inbound delivery in EWM. The process begins when SAP R/3 receives an advanced shipping notification from an external system (for example. EWM sets the planned delivery quantity to zero and notifies the ERP system. EWM uses the data from this inbound delivery to create a warehouse request. The ERP system uses this advanced shipping notification to create an inbound delivery. and distributes it to EWM. Process . see Warehouse Request for Returns [Seite 132].2007 All required processes are fully integrated. EWM ends the inbound delivery and sets the status of the warehouse request to Completed. the inbound delivery in the warehouse activities. 2. 1.07. SAP Extended Warehouse Management (SAP EWM) 510 264 . for example..SAP Online Help ● 20.. Result EWM uses the warehouse request to create one or more warehouse tasks for the putaway (putaway WT). 3. SAP CRM) for a planned inbound delivery. You can use it to put away the products. For more information. This warehouse request is the starting point for the putaway process.

The goal of storage control is to display your complex putaway or stock removal process steps based on your processes or your layout data. the putaway or stock removal process with different activities. an individual process step can be executed on single level basis or on multi level basis (that is. via delivery type and delivery item among others. adjusts the flow of the putaway or stock removal. through intermediate storage types). counting) within the goods receipt process The following parameters are possible: SAP Extended Warehouse Management (SAP EWM) 510 265 . EWM always executes the process-oriented storage control first. You can combine the process-oriented storage control with the layout-oriented storage control.07. the warehouse process type. Based on the process-oriented storage control.SAP Online Help 20.2007 Storage Control Use You can use the process-oriented as well as layout-oriented methods for storage control. ● ● ● ● 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. This contains the procedure. and if required. The handling unit thus contains the information concerning what process steps are required for the putaway or stock removal. 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. The layoutoriented storage control then checks whether the sequence of putaway process steps is possible in layout view. in other words. EWM transfers this operation to the handling unit to be put away or removed from stock. During 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. Here.

2007 Source storage type Destination activity area or destination storage type Warehouse process type Handling unit type Determination of the warehouse process type.07. see Process-Oriented Storage Control [Seite 336] and Layout-Oriented Storage Control [Seite 340]. among others. SAP Extended Warehouse Management (SAP EWM) 510 266 . using the delivery type and delivery item type. Features For information about the features of storage control.SAP Online Help ○ ○ ○ ○ ● 20.

Your external process stesps can base themselves on internal ones.07. Integration For more information about integration. in the Implementation Guide (IMG) for EWM. For more information. you combine your storage process steps into one storage process. Prerequisites For more information about the prerequisites. unloading. counting. see Direct and Combined Storage Control [Seite 268]. In addition. see Storage Control [Seite 334].SAP Online Help 20. Features You define the process steps for your complex storage process. The process steps for the processes Counting and Deconsolidating predefined by SAP can be dynamic [Extern]. for example. choose Cross-Process Settings → Warehouse Task → Define Process-Oriented Storage Control. You can also trace the status of the individual process steps. or deconsolidating [Seite 298]. SAP Extended Warehouse Management (SAP EWM) 510 267 . such as deconsolidating. internal or external process steps can be simple.2007 Process-Oriented Storage Control Use You use this type of storage control to map complex putaways or stock removals. such as unloading. A process step is. In doing so. see Storage Control [Seite 334]. Process-oriented storage control only operates with handling units. Activities For Customizing of process-oriented storage control. Extended Warehouse Management (EWM) recognizes internal process steps predefined by SAP and external steps that you can define yourself. EWM assigns these process steps to a handling unit as soon as it has created or changed them. EWM copies the predefined process steps from the storage process type to the handling unit. During goods receipt or goods issue. or combined.

EWM also creates a warehouse task per product contained in the HU. you have to use a combined processoriented storage control. it creates a warehouse task for this HU that determines the way from the source storage type to the destination storage type. for example.2007 Direct and Combined Storage Control (Putaway) Use If you want to execute a direct putaway. 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. deconsolidation station. see Updating the Inbound Delivery in the GR Process [Seite 271]. an inbound delivery is packed and the HU SAP Extended Warehouse Management (SAP EWM) 510 268 . • One warehouse task that describes the route from source storage type to intermediate storage type Irrespective of your settings in Customizing.SAP Online Help 20. For more information about updating the status. you do not have to define anything in the processoriented storage control [Seite 336]. If you want to define complex putaway processes. If. Features Direct Storage Control at Putaway If EWM determines that you are to put away a handling unit (HU) directly. Extended Warehouse Management (EWM) uses this during creation of a warehouse task to determine the intermediate storage types (for example. it creates one warehouse task per route section for this HU. see Storage Control [Seite 334] .07. For information about integration and the prerequisites. The following graphic shows you the relationship between direct putaway and creation of warehouse tasks. counting station).

you can break these down into storage sections and storage bins.1 Intermediate Storage Type 8010 Warehouse Task 1. see Updating the Inbound Delivery in the GR Process [Seite 271]. The truck comes to the loading ramp. or to the final destination storage type. you can distribute HUs containing different products to putaway HUs.2007 has no profile for process-oriented storage control. For more information about updating the status. You can carry out different activities at the intermediate storage types.07. at an intermediate storage type. You open the truck.SAP Online Help 20.. For example. Based on your settings in Customizing. In combined putaway. SAP Extended Warehouse Management (SAP EWM) 510 269 .3 Destination Storage Type 0020 Example Direct Goods Receipt The following is a sample process flow of a direct goods receipt.1 Intermediate Storage Type 8020 Warehouse Task 2. .. The following graphic shows you the relationship between combined putaway and creation of warehouse tasks. EWM creates product warehouse tasks at putaway. you can determine the final destination storage type either right at the beginning of your putaway process. EWM manages the intermediate storage types in the same way as standard storage types. within a putaway process.2 Destination Storage Type 0010 Source Storage Type 9011 Warehouse Task 2. 2.2 Intermediate Storage Type 8030 Warehouse Task 2. one warehouse task from the intermediate storage type to the next intermediate storage type. or later. For example. 1. • Goods Receiving Area Intermediate Storage Type 8000 Source Storage Type 9010 Warehouse Task 1.

To do this. choose Extended Warehouse Management → Execution → Confirm Warehouse Task. SAP Extended Warehouse Management (SAP EWM) 510 270 . 8. 3. choose Extended Warehouse Management → Execution → Confirm Warehouse Task. on the SAP Easy Access screen. on the SAP Easy Access screen. on the SAP Easy Access screen. 2. choose Extended Warehouse Management → Execution → Confirm Warehouse Task. choose Extended Warehouse Management → Execution → Confirm Warehouse Task. on the SAP Easy Access screen. 1. To do this. To do this. you confirm the arrival and opening of the truck. To do this. EWM creates a WT for this delivery that directly specifies the destination storage bin. on the SAP Easy Access screen. In EWM. choose Extended Warehouse Management → Shipping and Receiving. 9.07. on the SAP Easy Access screen. In EWM. choose Extended Warehouse Management → Shipping and Receiving → Unload. EWM indicates that a deconsolidation of the products is necessary. The truck comes to the loading ramp. You store your products at the destination storage bin. Combined Goods Receipt The following is a sample process flow of a combined goods receipt.SAP Online Help 20. You count the number of pieces of your products and confirm these in the WT.. EWM creates a WT for this delivery that directly specifies the destination storage bin. 5. To do this. 10. choose Extended Warehouse Management → Execution → Deconsolidation in Goods Receipt. You execute the deconsolidation at the intermediate location. To do this.. 5. . You count the number of pieces of your products and confirm these in the WT. To do this. You execute the putaway. you confirm the arrival of the truck. on the SAP Easy Access screen. choose Extended Warehouse Management → Shipping and Receiving. You store your products at the intermediate storage location and confirm this. 7. on the SAP Easy Access screen. 6. 4. 7. 4. You unload the truck.2007 3. To do this. choose Extended Warehouse Management → Shipping and Receiving → Unload. on the SAP Easy Access screen. 6. You open the truck. choose Extended Warehouse Management → Execution → Confirm Warehouse Task. on the SAP Easy Access screen. To do this. You unload the truck. To do this.

● 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. Putaway Planning and Putaway in the inbound delivery. For the goods receipt process (GR process). from when a warehouse activity exceeds the limit for the interior of the warehouse.. EWM sets the status Unloading in the inbound delivery (see number 1 in the graphic). EWM updates the inbound delivery and sets the status in the inbound delivery. that is. SAP Extended Warehouse Management (SAP EWM) 510 271 . corresponding to this warehouse mapping..07. 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. 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. 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. ..2007 Updating the Inbound Delivery in the GR Process Use Extended Warehouse Management (EWM) updates the inbound delivery corresponding to the goods receipt activities. Unloading Putaway Planning Putaway 1 TU / Door Staging Area Group Deconsolidation Final Storage Type 2 3 4 5 6 Goods Receipt Interior of Warehouse You perform the GR activities for unloading and putaway.SAP Online Help 20.. Für . For example: ● ● ● Work centers Identification points Final storage types EWM updates the statuses Unloading.

EWM resets the status Putaway Planning in the inbound delivery.. A prerequisite for this is that the destination location in the product HU is not a TU. If you cancel a product WT because EWM originally set the status Putaway Planning in the inbound delivery. EWM sets the status Putaway in the inbound delivery. ● The following applies for the status Putaway: If you confirm a product WT that contains the final storage type. 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]. ○ ○ ● The following applies for the status Putaway: If you confirm an HU WT that contains the final storage type. ○ ○ If you move a product from the goods receipt bin to an HU. EWM resets the status Putaway Planning in the inbound delivery. EWM sets the status Putaway Planning in the inbound delivery.2007 If you confirm an HU WT that is moving from a staging area group to a door or a TU. EWM does not update the status Putaway Planning unless the HU is in the interior of the warehouse. 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 (see number 5 in the graphic). or that the destination storage type in the product WT is not a door. ● 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 updates the inbound delivery and sets the status in the inbound delivery.SAP Online Help ○ 20. EWM sets the status Unloading in the inbound delivery. Für . EWM resets the status Putaway Planning in the inbound delivery (see number 4 in the graphic).. and this HU is in the interior of the warehouse.07. . EWM sets the status Putaway in the inbound delivery (see number 6 in the graphic)... 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 that is moving from the goods receipt bin to another storage bin. EWM always sets the status Putaway Planning in the inbound delivery. SAP Extended Warehouse Management (SAP EWM) 510 272 . Updating an Inbound Delivery with a Product Warehouse Task (Product WT) For Unpacked Stock You perform the GR activities for unloading and putaway. If you confirm an HU WT that is moving from the interior of the warehouse to goods receipt. 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. ● 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.

This means that. EWM sets the status Unloading in the inbound delivery (see number 1 in the graphic). 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). EWM uses the HU WT to update the status Unloading in the inbound delivery (see number 3 in the graphic). Updating an Inbound Delivery and Outbound Delivery Order in CrossDocking EWM performs cross-docking [Seite 544] (CD). EWM sets the status Putaway in the inbound delivery corresponding to the product WT. If you or the system generate an HU WT into the interior of the warehouse and no product WT for putaway exists. . ● The following applies for the status Unloading: SAP Extended Warehouse Management (SAP EWM) 510 273 . EWM sets the status Putaway in the inbound delivery with this WT (see number 6 in the graphic).07. ○ ● The following applies for the status Putaway: If you confirm a product WT that contains the final storage type. If you confirm an HU WT that is moving from a staging area group to a door or a TU. EWM updates the inbound delivery and sets the status in the inbound delivery. For the other products. EWM always sets the status Putaway Planning in the inbound delivery corresponding to the warehouse activities for the product WT. If you confirm an HU WT that contains the final storage type. depending on which WT you confirm first.. ○ ● 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.SAP Online Help 20.2007 Unloading Putaway Planning Putaway 1 TU / Door Staging Area Group Deconsolidation Final Storage Type 2 3 4 5 6 Goods Receipt Interior of Warehouse Handling Unit Warehouse Task Product Warehouse Task You perform the GR activities for unloading and putaway. EWM generates one or more pick-warehouse tasks (pick-WTs) for CD and updates the inbound delivery and the outbound delivery order simultaneously. EWM generates standard product WTs.. EWM resets the status Unloading in the inbound delivery (see number 2 in the graphic). ● 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. For the CD-relevant products. EWM sets the status Putaway in the inbound delivery corresponding to the HU WT.

EWM resets both the status Putaway Planning in the inbound delivery and the status Picking Planning in the outbound delivery order.SAP Online Help ○ ○ Für . 20. SAP Extended Warehouse Management (SAP EWM) 510 274 . If you confirm an HU WT that is moving from a staging area group to a door or TU. If you cancel 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. .. EWM sets the status Putaway in the inbound delivery and the status Picking in the outbound delivery order.2007 If you confirm an HU WT that is moving from a door or TU to a staging area group... ● 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. EWM sets the status Unloading in the inbound delivery. EWM resets the status Unloading in the inbound delivery.. ○ ● 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.07.

Extended Warehouse Management (EWM) splits the warehouse order into two: one from storage bin A to identification point I. you define external warehouse process steps for your warehouse. You can move your goods using a pick point during picking. in the Implementation Guide (IMG) for EWM. For this activity. One exception is the process display with picking or identification points. rather travel via intermediate storage bin. choose Cross-Process Settings → Warehouse Task → Layout-Oriented Storage Control. and a second from identification point I to storage bin B. see Storage Control [Seite 334]. For example. SAP Extended Warehouse Management (SAP EWM) 510 275 .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. If you want to move a product pallet from storage bin A (goods receiving area) to storage bin B (high rack storage area). see Storage Control [Seite 334]. Integration For more information about integration. 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. Activities For Customizing of layout-oriented storage control. including identification points [Extern] and pick points [Extern]. Prerequisites For more information about the prerequisites.07. you have a high rack storage area.SAP Online Help 20. The layout-oriented storage control only operates with handling units. You use layout-oriented storage control in the material flow system [Seite 820] to define conveyor segments. Features For layout-oriented storage control.

The material flow system [Seite 820] also uses layout-oriented storage control and thereby the storage group to define conveyor segments. Use Extended Warehouse Management (EWM) uses the storage group in layout-oriented storage control [Seite 340] to determine the intermediate storage bins.SAP Online Help 20. 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.07. Structure The storage group consists of a four-character identifier that you assign to a warehouse number and a storage type. SAP Extended Warehouse Management (SAP EWM) 510 276 .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. Integration EWM uses storage groups in layout-oriented storage control and in the material flow system.

You have defined condition records. and 4 are performed using the condition technique. and the putaway strategy that is to be used. on the SAP Easy Access screen. Prerequisites ● ● ● You work with storage bin types. Maximum quantity in storage type 3. For more information about the condition technique. You have defined storage type sequences in Customizing under Extended Warehouse Management → Goods Receipt Process → Slotting → Master Data. Storage section indicator 4. These parameters describe the storage section in which the product is to be stored. 3.07. You have defined the attributes in the product master that you want to use to determine the storage parameters. The results of slotting can be used in storage bin determination. If the putaway process for a product is dependent on execution parameters. choose Extended Warehouse Management → Master Data → Slotting → Condition Maintenance for Slotting. ● ● ● Features During slotting. and packaging data. optionally. product data. Slotting also forms the basis of rearrangement [Seite 287]. We recommend that you perform it periodically in the background. Steps 1. SAP Extended Warehouse Management (SAP EWM) 510 277 . Putaway control indicator (and. requirement data [Seite 279]. The system determines the underlying storage parameters that are relevant for putaway on the basis of master data. This does not. Slotting is optional. stock removal control indicator) 2.SAP Online Help 20.2007 Slotting Use During slotting. however. see the SAP Library under mySAP Customer Relationship Management → CRM Enterprise → Enterprise Sales → Sales Management for Commercial and Industrial Customers → Basic Functions → Condition Technique. a storage concept is automatically determined for a product. To do this. Step 4 can also be performed using storage bin type determination rules [Seite 283]. the system determines the following storage parameters and stores them in the product master: 1. the properties that the storage bin is to have. Steps 2 to 4 are optional. this dependency is taken into account later on during storage bin determination for putaway [Seite 291]. You have made the settings for the condition technique in Customizing under Extended Warehouse Management → Goods Receipt Process → Slotting → Condition Technique. have an effect on the results of slotting. 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. that is. Slotting takes into account master data that is not dependent on the execution process. Storage bin types The system always performs step 1.

2007 Activities To perform slotting.07.SAP Online Help 20. on the SAP Easy Access screen. SAP Extended Warehouse Management (SAP EWM) 510 278 . Then choose the storage parameters that the system is to determine. choose Extended Warehouse Management → Master Data → Slotting → Slot Products for Warehouse.

Extended Warehouse Management (EWM) stores this information locally in the product master (on the Slotting tab page.07. 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 Online Help 20. for example. For more information.2007 SAP APO Interface for Transferring Requirement Data To be able to calculate parameters such as the maximum quantity in the storage type. Requirement/Demand Data area). SAP APO performs planning processes for locations of the type Plant. If you have set the following indicators on the selection screen for slotting. If the relationship is not 1:1. 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. This requirement data can come from SAP Advanced Planning and Optimization (SAP APO). see the Implementation Guide (IMG) under Goods Receipt Process → Slotting → General Settings → Change Information for APO Instances. In most cases. slotting needs requirement data for the relevant product. SAP APO and EWM manage requirement data at different organizational levels. manual input or mass maintenance. you can use Business Add-Ins (BAdIs) for the conversion. Slotting assumes that a 1:1 relationship exists between the SAP APO location and the EWM warehouse number. EWM stores requirement data at warehouse number level. SAP APO and EWM run on different systems. you have several processing options in the product master. SAP Extended Warehouse Management (SAP EWM) 510 279 . To do this. You can also fill these local attributes in EWM with data from other sources.

The system only keeps the planned values for a possible activation. you can analyze the log. Fixing Values You can use a relevant indicator to fix all product attributes that can form the results of slotting.07. ● Save and Activate Results (The system updates both the planned values and the active values in the product master. the system does not overwrite these attributes during slotting.) Depending on the storage bin and stock situations. it can be useful to save the results of slotting as planned values only.) The system updates the results of slotting in the fields for the planned values and the active values in the product master. If you have performed slotting in the background. ● Save Results (The system only updates the planned values in the product master. in other words. These new values are then available immediately for all storage processes. only a global view must exist for the product.SAP Online Help 20. In this case. 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. 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. but you cannot see the results directly. 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.2007 Update of Results in Product Master Use The system updates the results of the slotting run in the product master. and does not use them in storage processes. SAP Extended Warehouse Management (SAP EWM) 510 280 .

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. you can create additional new fixed storage bins (picking bins) and can choose the instance Pick with Priority for these bins. Since the attribute Storage Bin Improvable depends on product attributes and on the current storage bin. the storage type group is not first in the search sequence. The criteria for the instance Storage Type Improvable (C) are not met. storage section. ● Storage Type Improvable (C) The storage section and storage bin type are optimum. and storage bin type for a product.07. 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. and storage bin type) are optimum.SAP Online Help 20. Update When you save or activate the results of slotting for a product. SAP Extended Warehouse Management (SAP EWM) 510 281 . The current storage type belongs to a storage type group. To do this. The storage type is optimum for the product within the group but it is not optimum on a global level.2007 Update Attribute Storage Bin Improvable Use Slotting determines the optimum storage type. If a significantly greater demand is expected for a product during a campaign. or deactivate the check. it exists in both the fixed bin table and in the quant. or storage bin type) is not optimum. You must configure this process manually. In other words. storage area. Instances of the Attribute Storage Bin Improvable The attribute has the following instances: ● ● Not Improvable ( ) All three attributes (storage type. The system can determine whether a certain stock (quant) is stored in an optimum way. You should also adjust the maximum storage type quantity of the relevant storage type for the product. it compares these optimum values with the attributes of the storage bin in which the quant is located. storage section. Pick with Priority (A) You can use this instance to support campaigns.

there can be a prioritization of the storage types within this group in relation to this product. Storage Type Groups The storage types in a storage type group have an equal weighting. The sequence of storage bin types produces the sequence of storage types.2007 Consideration of Storage Types In slotting.07. The search sequence can contain storage types or storage type groups. You have assigned a storage type search sequence to the putaway control indicator in Customizing for EWM. SAP Extended Warehouse Management (SAP EWM) 510 282 . Skip Storage Type If the system could not determine the optimum storage section indicator or the optimum storage bin type during slotting. Replen. It then uses this information when creating warehouse tasks (WTs). These storage types are assigned to a warehouse number. Qty (Minimum Replenishment Quantity) Plnd Min. The system uses the optimum storage bin type per storage type for the prioritization. When doing this. Qty (Planned Minimum Replenishment Quantity) Maximum Quantity This also means that replenishment cannot take place in this storage type. In this case. It determines an optimum storage bin type from the potential storage bin types for each storage type.SAP Online Help 20. Replenish. It then prioritizes the optimum storage bin types again. Storage Types The system interprets each storage type as an independent area in the warehouse (for example. the system uses the same criteria as it used to determine the optimum value within a storage type. the system considers the storage type group for a certain product. It assumes that stock for a product is to be stored in each storage type. 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. and PutawayControlInd key fields. it does not consider the storage type when creating a WT. see the Implementation Guide (IMG) under Goods Receipt Process → Slotting → Master Data → Define Putaway Control Indicator. For more information. therefore. the system does not set the following attributes: ● ● ● Min. the system determines attributes for a subset of storage types only. The system assumes that a product is to be stored in one storage type only within a group. This system does this by setting the Skip During Putaway indicator in the storage type view of the product master. You define the relevant storage types in Customizing for EWM (Extended Warehouse Management) by using the Warehouse No. reserve or picking area). If.

you have defined whether you want to work with the condition technique or with storage bin type determination rules. In the latter case.07. see the Implementation Guide (IMG) for EWM under Goods Receipt Process → Slotting → General Settings → Define Storage Type Parameters for Slotting. SAP Extended Warehouse Management (SAP EWM) 510 283 . width. The global maximum number is then the product of the three maximum values per dimension. and height of the packing level. For more information. you have chosen the required storage bin type determination rule. ● 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.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.SAP Online Help 20. The global maximum number is then the greater of the two maximum values per orientation. Prerequisites In Customizing for Extended Warehouse Management (EWM). 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. The result is a maximum number per dimension. and height of the storage bin type by the length. width.

width. Orientations are not permitted in cases where the calculated ratio exceeds the parameter value from the product master. and height of the relevant packing level.SAP Online Help ● 20. width.07. The global maximum number is then the greatest of the six maximum values per orientation.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. ● ● ● ● 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. and height that make sense on the basis of the orientations allowed. 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 . The system calculates all the ratios between length.

SAP Online Help ● 20.2007 Weight check and dimension check with rotation and tilt SAP Extended Warehouse Management (SAP EWM) 510 285 .07.

To activate the plan values or to simulate the activation of plan values. on the SAP Easy Access screen.07. There you can change the configuration in any way that you want to without causing errors. When you are satisfied with the result. you can perform slotting in the production system. on the SAP Easy Access screen. You can analyze the results of the simulation step-by-step and can optimize the configuration. You can only display and activate the results from a slotting run that you have performed interactively or in the background. 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.SAP Online Help 20. You can also simulate the activation of these results. choose Extended Warehouse Management → Master Data → Slotting → Activate Plan Values. SAP Extended Warehouse Management (SAP EWM) 510 286 . Activities ● ● To simulate slotting. Features You perform the simulation in the test system. Afterwards.2007 Simulation of Slotting Use You can use this function to simulate slotting without updating the product master. choose Extended Warehouse Management → Master Data → Slotting → Slot Products for Warehouse. you must adapt the configuration in the production system in accordance with the configuration in the test system. and can save and activate the results there. You cannot perform slotting runs in this transaction.

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. storage section. and storage bin types.SAP Online Help 20. If this is not possible. The first entry in a search sequence should not have a slotting index so that a storage bin with an optimum storage type. For an example of rearrangement. The entries in the search sequences are sorted by the slotting index and in descending order. The system only proposes an alternative storage bin if its slotting index is lower than that of the current storage bin. storage section. When doing this. the system uses search sequences for storage types. You have made the Customizing settings for putaway. the system proposes an optimum storage bin. see here [Seite 289]. and storage bin type has a slotting index of zero. When searching for an optimum destination storage bin (destination storage bin determination). Prerequisites ● ● You have created products and stocks. storage section. storage sections. You can assign a slotting index for each step in a search sequence in Customizing. and storage bin type) are to the product. and storage bin type as part of the analysis. 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. SAP Extended Warehouse Management (SAP EWM) 510 287 .07. it analyzes how well suited the current parameters (storage type. the system proposes an alternative storage bin with the next lowest slotting index. and storage bin type with the optimal parameters from slotting [Seite 277].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. storage section. 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. the system first tries to propose an optimum storage bin (with a slotting index of zero). If they are not optimal. In the case of rearrangement. If you want to work with slotting indexes.

You can also execute rearrangement in the background. storage section. The system proposes a destination storage bin and reserves it. and then Details. you can create a warehouse request to plan rearrangement as a wave. Save the warehouse task. and storage bin type/storage section for each current storage bin type. 4. on the SAP Easy Access screen. the system does not adopt the proposed destination storage bin and does not reserve it.07. choose Extended Warehouse Management → Work Scheduling → Rearrangement (Background). SAP Extended Warehouse Management (SAP EWM) 510 288 . Choose the required stocks. To start rearrangement. To do so. choose the required stock item and create a warehouse task. 3. In the detail view. The system performs the analysis and displays the number of stock items per optimal storage bin type. column. Choose one of the analyses. and storage bin type/storage section. choose Extended Warehouse Management → Work Scheduling → Rearrangement. In this case. Alternatively.SAP Online Help 20. storage section. on the SAP Easy Access screen.2007 Activities 1. or row. 2. the required cell.

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. 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 area for slow-moving items [Extern] is positioned behind this area. The warehouse has an area for fast-moving items [Extern] (golden zone). 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.2007 Example of Rearrangement The first figure shows the warehouse before rearrangement takes place. It is positioned along the central aisle of the warehouse to ensure that the picker can reach it easily.07.

07. Entrance Exit SAP Extended Warehouse Management (SAP EWM) 510 290 . Now the picker rarely has to drive down a side aisle to pick products.SAP Online Help 20. Entrance Exit The fourth figure shows the pick path after rearrangement has taken place. the pick path is shorter. fast-moving items are often picked. Since these are now closer to the central aisle. During picking.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.

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. you do not need to determine and apply additional search sequences. Storage bin determination for putaway occurs automatically when a warehouse task is generated. it could be the case that all other parameters are unimportant. normal. for example. You could. the storage behavior also plays a role. In addition to other data. empty storage bin. therefore. for example: ○ You have defined storage section search sequences under Goods Receipt Process → Strategies → Storage Section Search → Maintain Storage Section Search Sequence. 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.SAP Online Help 20. It describes the type of storage bins. 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 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. or pallet storage. You have made the settings for putaway in Customizing for Extended Warehouse Management (EWM). parameters from the product master that you have defined manually or that were determined in slotting [Seite 277] are used to do this. a physical storage bin is determined by means of determining and applying the suitable strategies [Seite 375]. In addition to the putaway rule.07. If a product has the stock category Quality Inspection. Prerequisites ● ● You have created storage bins. Determination of storage sections SAP Extended Warehouse Management (SAP EWM) 510 291 . In a putaway process. In this case. ○ Features During storage bin determination. it could be the case that the fixed storage bin has already been determined for a storage type by slotting. The putaway rule specifies how a storage bin is to be determined. You can define multiple accesses for determining the storage type search sequence. In a fixed storage bin scenario. bulk storage.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. 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. for example.

and storage bin type that have been found. You can use the Business AddIns in the /SCWM/ES_CORE_PTS enhancement spot to implement a customer-specific logic. Here it tries to find a storage bin for each combination in accordance with the putaway rule. 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 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. You can use the Business Add-Ins in the /SCWM/ES_CORE_PTS enhancement spot to implement a customer-specific logic. it could be the case that you want to prevent storage bin determination for products that have not yet been slotted.SAP Online Help 20. the system uses a certain priority to evaluate the combinations of storage type. SAP Extended Warehouse Management (SAP EWM) 510 292 . storage section. however. you do not use slotting.07. the system then determines a storage section by determining and applying a storage section search sequence. there is no reason to prevent storage bin determination.2007 For each storage type that is found. Determination of storage bins Last of all. Slotting and storage bin determination If you use slotting. If.

if necessary. EWM creates the inspection documents later. The batch number is required for creation. 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. 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. it simultaneously updates the inbound delivery. and. the stock type in the inbound delivery. EWM is to create an inspection document when the inbound delivery is activated.SAP Online Help 20. it updates the document flow for the reference document types Q01 and Q03. see Quality Inspection [Seite 866] and Creation of Inspection Document [Seite 869]. For more information. the result of quality inspection planning could be that EWM is not to carry out a quality inspection. EWM creates inspection documents in the background. you can view all of the inspection documents for an inbound delivery in document flow. In the delivery. you have specified all the data necessary for the creation of an inspection document. Regardless of whether you carry out a quality inspection or not. For example. If necessary. For example. Thus.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. SAP Extended Warehouse Management (SAP EWM) 510 293 . You have defined inspection rules (see Master Data [Seite 855]). EWM changes the stock type in the inbound delivery from unrestricted-use stock to stock in quality inspection. Once EWM has created the inspection documents. For example. EWM only creates the inspection document once you have specified the batch number. Here. EWM also sets the status data in this case. EWM always updates the status data. the status for inspection planning. Integration See Creation of Inspection Document [Seite 869] Prerequisites ● ● ● You have carried out the Customizing for creating inspection documents [Seite 869]. Features In the following cases. EWM updates the document flow. EWM copies the inspection document number to the inbound delivery. In addition. If not all of the necessary data exists in the delivery by the time at which EWM is to create the inspection documents. EWM updates the stock type.

on the SAP Easy Access screen.SAP Online Help 20.2007 Activities If you want to display the statuses QM Inspection Planning and QM Counting Planning. SAP Extended Warehouse Management (SAP EWM) 510 294 .07. Go to the Status tab page. choose Extended Warehouse Management → Delivery Processing → Maintain Inbound Delivery.

You have defined inspection rules. Integration with an ERP system is required to enable inbound delivery notifications to be created automatically in Extended Warehouse Management (EWM). choose Extended Warehouse Management → Master Data → Quality Management → Maintain Inspection Rule. Integration ● The Quality Inspection Engine [Seite 888] (QIE). on the SAP Easy Access screen. 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. SAP Extended Warehouse Management (SAP EWM) 510 295 . provides essential functions that enable a system-supported check (counting) in the inbound delivery process. To do so. 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. ● 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 quantity intervals and value intervals in Customizing for EWM under Goods Receipt Process → Counting.07. You have checked that the inspection object types and their properties have been activated.2007 Counting Use The aim of counting is to check the quality of a sample of inbound deliveries. an integral part of the SCM system. 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 Online Help 20. You have defined a percentage that specifies how many delivery items are to be counted.

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. Inspection object types define the inspection process. choose Extended Warehouse Management → Work Scheduling → Create Warehouse Task for Warehouse Request → Putaway for Inbound Delivery. You have changed or activated an inbound delivery notification in EWM. The system uses the storage control settings to determine the storage bin for counting for all the delivery items with an inspection document.. To do so. the system first determines whether the delivery items are to be counted. Activities Explicit counting . Create a warehouse task with reference to the inbound delivery and confirm it. Features When you change or activate an inbound delivery notification. The system has found an active inspection object type and an inspection rule. To do this.. To do so. on the SAP Easy Access screen. SAP Extended Warehouse Management (SAP EWM) 510 296 . To do this. on the SAP Easy Access screen. It marks the relevant delivery item for counting. ● Implicit counting The information specifying that a product must be counted is part of the warehouse task data. If a difference is determined. the delivery items would be put away immediately at the final storage bin.SAP Online Help ● 20. it checks if an active inspection object type and inspection rule exist. You can perform explicit counting only for handling units. The system determines the storage bin (storage type) for this counting station on the basis of the storage control settings. choose Extended Warehouse Management → Master Data → Product → Maintain Warehouse Product.07. and has created an inspection document. You use the inspection rule to define when a delivery item is to be counted.2007 You have defined warehouse products. you must confirm the warehouse task with differences (exception code) to end the transaction. To do this. 1. choose Extended Warehouse Management → Master Data → Work Center → Define Master Data Attributes. You can perform implicit counting only for unpacked products. taking into account the dynamic criteria. on the SAP Easy Access screen. 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 creates an inspection document. If the system had not created an inspection document because an active inspection object type and inspection rule were not available. Counting station ● You have defined a work center for counting (counting station).

To do this. You have changed or activated an inbound delivery notification in EWM. The system has found an active inspection object type and an inspection rule. SAP Extended Warehouse Management (SAP EWM) 510 297 . The delivery items are put away immediately at the final storage bin. on the SAP Easy Access screen. Call the counting station that is assigned to the storage bin for counting and enter the count results.SAP Online Help 20. To do this. choose Extended Warehouse Management → Work Scheduling → Create Warehouse Task for Warehouse Request → Putaway for Inbound Delivery. choose Extended Warehouse Management → Execution → Quality Inspection and Count. on the SAP Easy Access screen. and confirm the warehouse task.07.. confirm the count results.2007 2. Implicit counting . and has created an inspection document. Create a warehouse task with reference to the inbound delivery..

and product PROD3 for the high rack storage area HL. see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Issue Process → Define Consolidation Group. SAP Extended Warehouse Management (SAP EWM) 510 298 . you must have defined the deconsolidation attributes for each activity area. see the IMG for EWM under Master Data → Define Activity Area. For example.SAP Online Help 20. see the IMG for EWM under Goods Receipt Process → Deconsolidation → Define Attributes for Deconsolidation for Each Activity Area. you have defined deconsolidation rules. If you want to use deconsolidation in process-oriented storage control. For more information.2007 Deconsolidation Use You can use this function to divide up a deconsolidation handling unit (deconsolidation HU) across multiple putaway HUs. ● ● ● In Customizing. see the IMG for EWM under Goods Receipt Process → Deconsolidation. for deconsolidating the deconsolidation HU into three putaway HUs.. one of the following cases must be present: ○ ○ ○ The activity areas for the products within an HU are different. This is necessary if a deconsolidation HU contains different products that you want to put away in different storage sections. If EWM is to define a deconsolidation. but the maximum number of warehouse tasks for the HU has been exceeded. Prerequisites ● . but the consolidation groups are different. product PROD2 for the bulk storage area BL.07. Other warehouse tasks. In Customizing. EWM creates the following warehouse tasks: ● ● ● A warehouse task for the deconsolidation HU A warehouse task for each product.. you have a deconsolidation HU HU123 with product PROD1 for the reserve storage area RL. For more information. The activity areas for the products within an HU are the same. which deconsolidation then takes into account. you have defined activity areas. For more information. For more information. depending on your Customizing settings (Direct or Combined Storage Control [Seite 268]). Integration You define the consolidation groups [Extern] in Customizing for storage control [Seite 334]. Features When EWM performs deconsolidation. The activity areas and consolidation groups for the products within an HU are the same. it creates a warehouse task for each HU item.

Activities On the SAP Easy Access screen. This means that if you are using process-oriented storage control. due to the HU exceeding the permitted maximum number of WTs in the deconsolidation HU. After you have confirmed the repacking of five product-WTs into the putaway-HU. EWM distributes the products in the deconsolidation HU that are relevant for crossdocking across multiple pick-HUs. where the destination data is all assigned to the same activity area. rather from the data of the outbound delivery. EWM forwards the HU to a deconsolidation station. choose Extended Warehouse Management → Execution → Deconsolidation in Goods Receipt.SAP Online Help 20.2007 Special Features for Deconsolidation in Cross-Docking When you perform deconsolidation in cross-docking. Example You receive a deconsolidation HU with 15 warehouse tasks (WTs). 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. SAP Extended Warehouse Management (SAP EWM) 510 299 . EWM proposes this HU for closure.07. as in the standard putaway procedure. due to the parameter Maximum Number of WTs in the Putaway-HU. 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]. You have set the Maximum Number of WTs in the Deconsolidation HU to ten. 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. During deconsolidation at this location. and the Maximum Number of WTs in the Putaway-HU to five. For example. EWM creates putaway-HUs. This means that it also releases the HU for the following process step Putaway.

the sequence of the warehouse tasks corresponds to the putaway path. Storage bin sorting takes place in a logical section of the warehouse.SAP Online Help 20. The warehouse tasks can be created in the following ways: SAP Extended Warehouse Management (SAP EWM) 510 300 .2007 Putaway Use The destination of the final putaway is the putaway of products into storage bins in the warehouse. for the purpose of putting away your products. the Putaway activity area. which optimizes the order of the storage bins. then to the reserve bins. for which items putaway has already started. SAP R/3 and EWM compare their data at a later point when the connection is available again. EWM takes into account both one-way streets as well as differentiations in the various putaway strategies.07. then to all the left-hand bins. 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). For scheduling and monitoring of the putaway operations. ● ● If there are unplanned stock movements without a preceding document. For the putaway. for example. you can create a warehouse request without a reference. The starting point for this is the warehouse request [Seite 109]. EWM uses your settings to define the path that the warehouse employee should take to put the products away. You can use EWM to allow the system to define a putaway path for the putaway. or first drive to the standard bins. the connection between SAP R/3 and EWM is interrupted. Regardless of how you perform putaways in your company. first drive to all the righthand bins. and refers to specific activities. This status tells you. Extended Warehouse Management (EWM) determines a putaway path. for example. ● Warehouse Tasks for Putaway Putaway creates warehouse tasks for you. You can then enter and save the manually entered data in EWM. or you can print the warehouse orders and enter the information for the final putaway manually. 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. When defining this path. If. you can create a warehouse request manually. after a request from an employee You specify this using the Post Processing Framework. for example. Both on the RF device’s display and on the paper printout. EWM stores a putaway status in each delivery item.

Status Packed is Set or Status Goods Receipt is Set. and bins Specify the storage control for the destination storage type For more information about storage control. For example. it simultaneously checks whether the product to be put away is a hazardous substance [Extern]. ● ● ● Manually by a user Putaway requires warehouse tasks in order to Specify the destination storage types. on the SAP Easy Access screen. choose Extended Warehouse Management → Execution → Log On to RF Environment. SAP Extended Warehouse Management (SAP EWM) 510 301 . see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Warehouse Order → Print. sections. When EWM creates a warehouse task for putaway. If you want to print the warehouse order.2007 Automatically by EWM You can control the time by assigning a schedule condition in the Post Processing Framework Action (PPF Action). see Hazardous Substance Master [Seite 969].07. For more information.and Layout-Oriented Storage Control [Seite 334]. If the product is a hazardous substance.SAP Online Help ● 20. Activities If you want to use RF devices. For more information. you can define this in Customizing. EWM determines (according to your Customizing) the storage type you can use to put away the hazardous substance. see Process.

deconsolidation [Seite 298]). When EWM creates a warehouse task. For more information. so that you can put away products. The warehouse task reflects the direct or combined storage control. When EWM creates a warehouse task for a warehouse request. EWM uses a warehouse task to specify the following for the putaway: ● ● The destination storage types. using an action from the Post Processing Framework (PPF).SAP Online Help 20. see Process-Oriented Storage Control [Seite 336] and Layout-Oriented Storage Control [Seite 340]. In the IMG for EWM. You create the warehouse tasks manually. sections. according to your Customizing settings. see Warehouse Order Creation [Seite 419] EWM uses layout-oriented and process-oriented storage control. For more information. it uses putaway strategies [Seite 375] to determine the storage bin. Features ● EWM can create warehouse tasks for an inbound delivery in the following ways: ○ ○ ● EWM automatically creates warehouse tasks for an inbound delivery. you must have made the settings in Customizing for warehouse order creation. In the Implementation Guide (IMG) for EWM. according to your Customizing settings. In the 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. ● ● ● ● 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.07. For more information. EWM specifies various activities for you to perform (for example. SAP Extended Warehouse Management (SAP EWM) 510 302 . choose Cross-Process Settings → Delivery Processing → Actions → Use Assistant to Create Actions.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]. and bins The path to the destination storage type Prerequisites If you want EWM to automatically group warehouse tasks into warehouse orders. choose Cross-Process Settings → Warehouse Order. see Storage Bin Determination for Putaway [Seite 291]. EWM automatically groups warehouse tasks according to your Customizing settings for warehouse orders.

Following creation of the warehouse tasks. If you want to post goods receipts for all deliveries for an inbound delivery.2007 If you want to create a warehouse task manually. the Putaway Planning status is set to Partially Completed. the warehouse request status Putaway Planning changes to Completed. If the quantity update leads to a change in status. on the SAP Easy Access screen. choose Extended Warehouse Management → Goods Receipt and Shipping → Unload. and WT3) for the entire quantity. choose Extended Warehouse Management → Work Scheduling → Create Warehouse Task for Warehouse Request → Putaway for Inbound Delivery. it simultaneously updates this warehouse request.SAP Online Help ● 20. on the SAP Easy Access screen. WT2. EWM updates this change in the warehouse request as well. If EWM does not create warehouse tasks for the entire quantity. after EWM creates . 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 . The following table gives you an overview of the Putaway Planning status in the warehouse request. ● ● You have an inbound delivery of 100 pieces of a product. When EWM creates a warehouse request warehouse task for an outbound delivery. EWM carries out this update by updating the quantity in the document flow. after EWM creates SAP Extended Warehouse Management (SAP EWM) 510 303 . after EWM creates WT3 .07. EWM automatically creates three warehouse tasks (WT1. based on the storage bin determination. and also want to create warehouse tasks for unloading.

You skip the destination storage bin proposed by EWM and process the next one. EWM places this destination storage bin at the end of the RF display. or you can allow activity areas to overlap. EWM determines the putaway path according to your settings in Customizing and saves this information in the WT. and have specified the sorting sequence of the activity areas. During definition of putaway paths. EWM shows the destination storage bins in this predefined sequence. which means that EWM sorts the WTs according to the putaway path. only one putaway path is active for each WT. it specifies this putaway path. Integration Specification of the putaway path is integrated into WT processing. you can assign more than one putaway path. have assigned storage bins to the activity areas. SAP Extended Warehouse Management (SAP EWM) 510 304 . and structure. descriptions. You cannot gain access to a destination storage bin because a colleague is currently putting away products in it. ● You have defined activity areas and categories.2007 Specification of the Putaway Path Use You can use this function to specify a putaway path for each activity in the activity area. Activities . On the radio frequency device. Prerequisites ● You have defined the storage bin types. For your putaway. refer to the Implementation Guide (IMG) for EWM under Master Data → Storage Bins. For more information. then it sorts the WTs based on the warehouse order. Features If EWM has grouped several WTs into a warehouse order. However. For more information. you or EWM create the necessary WTs for the warehouse request of the outbound delivery..SAP Online Help 20. If you use radio frequency devices.07. This is not dependent on the product that is contained in the handling unit. see the IMG for EWM under Master Data → Activity Areas. you can skip a destination storage bin proposed by EWM. In so doing. For more information. When Extended Warehouse Management (EWM) creates a warehouse request (WT). based on a warehouse order. ● You have assigned an activity to a warehouse process type. see the IMG for EWM under Cross-Process Settings → Warehouse Task → Define Warehouse Process Type. Example The following figure shows you an example of specification of the putaway path..

EWM sorts these across the warehouse.2007 EWM has created a warehouse order that contains WTs.SAP Online Help 20. EWM creates the following putaway path: Document Item 1 2 3 4 5 … Handling Unit 1 2 1 2 3 … Therefore. SAP Extended Warehouse Management (SAP EWM) 510 305 .07. if you simultaneously put away several HUs. It has created a WT for each handling unit item.

destination storage bin).SAP Online Help 20.07. EWM thus includes the HU in the resource. Activities Putaway According to Handling Unit (HU) 1. The system displays the following: ○ ○ If the system finds a WT for the entire HU. then you are dealing with a distributive putaway [Extern]. 3.2007 Putaway Using Radio Frequency Use You can execute putaways using a radio frequency presentation device (RF presentation device). Putaway According to HU (Collective) You enter more than one HU number and the system searches for the corresponding warehouse orders. 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. The system displays the following data: ■ ■ ■ ■ ■ Source HU Product Quantity Batch Destination HU SAP Extended Warehouse Management (SAP EWM) 510 306 . The system searches for the corresponding warehouse orders. The destination storage bins of the warehouse orders [Seite 419] to be processed are always in the same activity area. If the system finds WTs for the products in the HU. Prerequisites You have logged on [Seite 790] in the RF environment. You enter a HU number. The system displays the first WT it has found according to the sort sequence of the destination storage bins. 2. 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. the system displays the source data (HU number.

quantity. you cannot get to the source storage bin or destination storage bin. 1. You enter all desired HU numbers.. batch. 3. If a warehouse order has more than one WT. or the destination data of the HU WT (HU and destination storage bin).2007 Destination storage bin If a warehouse order has more than one WT. and the action repeats itself. During the putaway process. 1. You can reverse the sequence in which the system displays the WTs. 4. Putaway According to Warehouse Order . You can place the displayed WT at the end of the execution. if the aisle is blocked. SAP Extended Warehouse Management (SAP EWM) 510 307 .SAP Online Help ■ ○ ○ ○ 20. The system displays the source data (product. skip the HU WT that is currently to be processed For example.. and source storage bin) of the first product WT that belongs to the warehouse order. If a warehouse order has more than one product WT. If a warehouse order has more than one WT. you can do the following: You can skip a WT. 5. quantity. The system searches for the corresponding warehouse task.07. Putaway According to Handling Unit (Collective) . You confirm the destination data of the first WT. 5.. 2. you can do the following: ○ ○ ○ You can skip a WT. or the source data (HU and source storage bin) of the first HU WT that belongs to the warehouse order.. 3. You enter a warehouse order number. batch. and destination storage bin). 2. The further steps correspond to steps three to five for putaway according to handling unit. The system searches for the corresponding warehouse tasks. You can place the displayed WT at the end of the execution. You confirm the source data of the first product WT or the source data of the first HU WT. the system no longer shows you this HU WT and you do not need to confirm the source data and destination data. then. You decide whether you want to putaway further in a guided manner or according to product number or warehouse task. 4. 6. 4. You confirm the data of the HU WT or of the first product WT. the system displays the data of the next product 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. 7. You can reverse the sequence in which the system displays the WTs. the system displays the source data of the next WT (product WT or HU WT). The system displays the destination data of the product WT (product.

skip the product WT that is currently to be processed For example. if a piece of the product quantity is damaged. then.07. the system no longer shows you this HU WT and you do not need to confirm the source data and destination data.2007 For example. During the putaway process. ● ● Change the batch In general. SAP Extended Warehouse Management (SAP EWM) 510 308 . you cannot get to the source storage bin or destination storage bin.SAP Online Help Product WT Confirmation You can specify an exception for this process and then: ● ● Change the destination storage bin Record differences 20. if the aisle is blocked. you can enter a smaller product quantity rather than confirm the quantity.

and increased the number of HUs in the new warehouse order that is to be created by one. If EWM generates one warehouse order only. and that warehouse tasks exist for all products in the HU. EWM assigns the HU scanned first to position one. EWM displays a success message if appropriate. ● Features This function is optimized so that you can operate it using a hand-held scanner that is installed on a keyboard filter. A traffic light shows the status of the warehouse task. Make sure that the position of the HU in EWM matches the physical position of the HU in the resource. the next HU to position two. 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]). EWM shows you the position in the Radio Frequency dialog (RF dialog). EWM attempts to generate a warehouse order for all warehouse tasks. you have scheduled a corresponding PPF action. choose Save. choose Extended Warehouse Management → Execution → Manually Assemble Warehouse Orders. ● Activities ● ● On the SAP Easy Access screen. This allows you to put away the HUs collectively. and Extended Warehouse Management (EWM) is able to determine the optimal putaway path. If EWM generates multiple warehouse orders. and does not include the HU in the new warehouse order that is to be created. Red means that you have specified an HU. For example. and the HU scanned last to position three. In doing this. EWM does not update the screen content for the total weight and total volume. and saves the warehouse tasks in this order.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. EWM deletes all warehouse tasks of the HUs from your warehouse orders. SAP Extended Warehouse Management (SAP EWM) 510 309 . but that no warehouse task exists for at least one of the products in the HU. Prerequisites ● ● You have made sure that putaway warehouse tasks exist and are active for the entire contents of the HU. You can specify multiple HUs in the entry field. you scan three HUs. ● Green means that you have specified a valid HU. In this case.07. EWM updates the screen content. and assigns the HU to a position field. the message only contains the number of warehouse orders. EWM has updated screen content for the total weight and total volume. you can get the warehouse order number from the log. you can take the warehouse order number directly from the message. When you perform putaway. one after each other. and to group them together in a new warehouse order. After you have specified all the HUs. ascending. EWM shows you the specified HU in the lower part of the screen.SAP Online Help 20. If you want to print warehouse orders using a PPF action.

SAP Extended Warehouse Management (SAP EWM) 510 310 . Under Create Action.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. choose the PPF action you require for printing warehouse orders (see Printing Warehouse Orders and Warehouse Tasks [Seite 426]).SAP Online Help ● 20.07.

EWM calculates the difference quantity and posts it. if you want to change a quantity specification. Features EWM delays sending a warehouse task that has already been confirmed. you can still correct warehouse tasks in the goods receipt process that have already been confirmed. For more information. Only now does the ERP system perform any necessary activities. You notice that you have made a mistake. you have specified 11 pieces as the Act. such as for a returns process or a stock transfer order.07. Prerequisites You have defined a completion delay for inbound deliveries. and you can no longer make a confirmation correction.SAP Online Help 20.Qty (Dest. SAP Extended Warehouse Management (SAP EWM) 510 311 . and change the Act. corresponding to the completion delay you have specified for inbound deliveries in Customizing. see the IMG for EWM under Cross-Process Settings → Delivery Processing → Status Management → Define Status Profiles. From this point in time. 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..Qty (destination difference quantity) as 1 piece. or the storage bin as a selection criterion. You can schedule report /SCWM/R_PRDI_SET_DWM to set the status DWM for sending the completion indicator to Completed. For more information.. EWM automatically calculates the Dest. EWM also indirectly sets the completion status DCO for the inbound delivery to Completed.) (destination actual quantity) and already confirmed the warehouse task. Activities .2007 Confirmation Correction Use For example. For more information. and posts this. For displaying the warehouse task in the user interface or in the RF environment. you can use the warehouse order. EWM immediately sets the status DWM for sending the completion indicator to Completed. you can still correct the actual quantity for the destination storage bin and the batch. For example. In accordance with the completion delay. When the completion delay has passed. EWM sets the status DWM for sending the completion indicator to Completed. You can correct a warehouse task that has already been confirmed in both the user interface and in the RF environment [Seite 803]. By doing this.Qty (Dest.Diff. see the report documentation. If you do not specify a completion delay for inbound deliveries in Customizing. You are using a document type and item type with a status profile for which you have activated the status DWM. That is. you cannot make any further corrections in the confirmed warehouse task. see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Receipt Process → Inbound Delivery → Define Delay in Completing Inbound Deliveries. the stock identification.) to 10 pieces. EWM performs a type of stock adjustment regarding the relevant warehouse task. You make your correction and specify an exception code in the warehouse task for each delivery item.

a. EWM locks the inbound delivery from further warehouse activities until you have made your confirmation correction. none of the fields are ready for input.2007 1. b. If you want to make a confirmation correction using the user interface.07. 2. b. The fields for the confirmation correction entry are ready for input. EWM then does the following: a. SAP Extended Warehouse Management (SAP EWM) 510 312 . Checks which inbound delivery belongs to the warehouse task (reference) 3. and you can make your correction. 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. EWM reads the inbound delivery and checks that the completion status DCO of the inbound delivery does not yet have status value Completed. If the status already has the status value Completed. Checks whether the warehouse task is locked d. Checks which authorizations you have c. on the SAP Easy Access screen choose Extended Warehouse Management → Execution → Confirm Warehouse Task and then Correct the Confirmation. If the status does not yet have the status value Completed.SAP Online Help 20. and you cannot make a confirmation correction.

If you have configured goods movement bin determination. and you have posted goods receipt. EWM also uses the settings that you specify here to process outbound deliveries that are not relevant to picking. see the Implementation Guide (IMG) for EWM under CrossProcess Settings → Delivery Processing → Status Management → Define Status Profiles. 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. choose Extended Warehouse Management → Settings → Maintain Goods Movement Bin Determination. the stock type) and a goods movement bin in the warehouse request. You put away the products in your warehouse and you post goods receipt for the inbound delivery.SAP Online Help 20. for example. Extended Warehouse Management (EWM) does not generate any warehouse tasks for the warehouse request or any warehouse orders. you have put away the products in your warehouse. EWM automatically suggests a goods movement bin. in contrast to putaway [Seite 300]. 2. 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. SAP Extended Warehouse Management (SAP EWM) 510 313 .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. Process . You perform any other relevant goods receipt steps. On the SAP Easy Access screen. oryou manually generate the warehouse request in EWM. Either ERP distributes an inbound delivery to EWM and EWM automatically generates a corresponding warehouse request. However.. You specify all the relevant stock attributes of the product (for example.07. Result EWM has generated a warehouse request for an inbound delivery. You have performed any additional goods receipt activities. You or EWM create the warehouse request for an inbound delivery [Seite 112]. 3. 1.. unloading.

for example an SAP system.2007 Goods Issue Purpose A goods issue [Extern] from Extended Warehouse Management (EWM) is a physical departure of products from your warehouse. see Goods Receipt [Seite 263] under Prerequisites. EWM receives a goods issue request from another system.. you can execute the warehouse-internal processes that precede the actual goods issue. You can remove your products from stock either directly or by using storage control [Seite 334]. such as stock removal using pick points from a high rack storage area. You have defined a stock removal strategy in Customizing for EWM under Goods Issue Process → Strategies → Define Stock Removal Strategy.. For more information. you use the warehouse task as the main document upon which you display all goods movements in EWM. Prerequisites ● ● ● ● ● The data for the warehouse request for outbound delivery in EWM is complete. To simplify the search for appropriate stock. 1. You can only execute complex stock removal processes by using handling units... To do this.07. such as packing during warehouse task confirmation. You have defined the following basic settings in Customizing for EWM: For examples of basic settings. see Warehouse Request for Inbound Delivery or Outbound Delivery Order [Seite 112].SAP Online Help 20. as well as the process-oriented rules and procedures defined by you. such as picking or packing. within the warehouse before you trigger the actual goods issue posting. EWM offers you stock removal strategies [Seite 396]. The warehouse request is relevant for picking. The goods issue takes into account your warehouse arrangements. 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 reduce the stock in the warehouse. You can use a goods issue to indicate goods deliveries to your customers. With a goods issue posting. SAP Extended Warehouse Management (SAP EWM) 510 314 . You have defined a stock removal control indicator in Customizing for EWM under Goods Issue Process → Strategies → Define Stock Removal Control Indicator. You can use the warehouse request to automatically trigger the goods issue processing. Process . .

2007 2. You carry out further goods issue activities. you create a new warehouse request item for each batch. EWM creates a warehouse request for an outbound delivery order [Seite 112]. using a Post Processing Framework (PPF) action You can create the warehouse tasks manually. In doing so. For more information. see Printing Warehouse Orders and Warehouse Tasks [Seite 426]. EWM creates a separate warehouse task. see Creation of a Warehouse Request for an Outbound Delivery Order [Seite 116]. such as packing or loading. you confirm that you have brought the goods to the goods issue interface. 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]). EWM does not carry out an independent availability check. which you confirm after you have completed the physical activity. You create a warehouse request for the warehouse request for picking from your warehouse. but instead assumes a purely executional function. you confirm the warehouse tasks. 5. For each goods issue activity. 4.SAP Online Help 20. ○ You can take into account batch information when creating warehouse tasks for picking. SAP Extended Warehouse Management (SAP EWM) 510 315 . 7. see Creation of Warehouse Tasks for Warehouse Request [Seite 412].07. 6. You either print the warehouse request with the warehouse tasks as a list. which delivery items are relevant for stock removal with EWM. Once you have completed the picking. which is the starting point for the goods issue. and you want to pick one or more batches to cover the required quantity completely. 3. If you remove the goods from the determined source storage bins to the goods issue interface. you must verify these batches to the outbound delivery. For more information. When you create a warehouse task. If you have not determined the batches to be picked in the warehouse request. the system creates corresponding warehouse orders. you can use this printout as the picking document. With this confirmation. Creation of Warehouse Tasks for Stock Removal [Seite 319]. or Wave Management [Seite 766]. directly through the release of a wave Automatically. These warehouse orders group the warehouse tasks in accordance with the rules defined in Customizing. ○ You can create the warehouse task directly or let EWM create it automatically. For more information. on the item level of the warehouse request. or you print all individual documents at once. EWM recognizes. EWM can create warehouse tasks in the following manner: ■ ■ ○ By default. The availability check for the goods issue takes place on the level of the prestored components. This records any stock differences between the required and the picked quantity.

see Creation of Warehouse Tasks for Warehouse Request [Seite 412].2007 For more information. EWM updates the activity status when a step of the warehouse task processing has been completed. Using Storage Control For more information about goods issue processes using storage control. Layout-Oriented Storage Control [Seite 340] .07. You can inform yourself about the outbound delivery status during the entire goods issue process. 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. see Storage Control [Seite 334]. SAP Extended Warehouse Management (SAP EWM) 510 316 . see Handling Differences When Picking for Warehouse Request [Seite 348].SAP Online Help 20. 8. You then post the goods issue for the warehouse request. or Process-Oriented Storage Control [Seite 336]. For more information.

In so doing.07. 1. When EWM creates a warehouse request. For more information. EWM selects the storage type and exact storage bin from which you can pick the product that is to be removed from stock. EWM creates one or more warehouse task items for each item in the warehouse request. using a Post Processing Framework action. using the automatic wave scheduling. You use a printed warehouse request as the pick list. EWM contains stock removal strategies to simplify your search for the correct product to be removed from stock. If you use Extended Warehouse Management (EWM) for warehouse management. For more information. In so doing. The product that is to be removed from stock is then found at the destination storage bin defined in the warehouse task. 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. At the same time. 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 . create a warehouse task [Extern] for all stock movements. You then have access to the current data concerning the processing status in the warehouse. EWM groups stock removal warehouse tasks to warehouse orders. EWM automatically transfers the information concerning the picking status to the warehouse order. You create a warehouse task for the warehouse request. EWM transfers the picked quantity directly to the corresponding items in the warehouse request..SAP Online Help 20. see Warehouse Request for Inbound Delivery or Outbound Delivery Order [Seite 112]. Process . In addition. 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.. You confirm the warehouse task.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. Regardless of how you organize stock removals in your company. The warehouse request [Seite 109] is a request for EWM to remove goods from stock. see Automatic Wave Assignment [Seite 773]. You use stock removal transfer orders to execute stock removals. The warehouse request contains the corresponding warehouse tasks. You use the printed warehouse order as a pick list for the stock removal. Regularly at set times. you can trigger the picking of goods in EWM automatically. 2. you confirm in EWM that the physical removal of goods is concluded. According to the stock removal strategy. 3. 4.

for example. EWM can thus create more than one warehouse task from one item in the warehouse request. You use warehouse tasks 2 and 3 to move the products from storage type 1 to the goods issue zone.07. and 4. 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. Warehouse Task 3 Source – Dest. Warehouse Task 5 Source – Dest. Warehouse Task 2 Source – Dest. you create a warehouse task for a warehouse request to the outbound delivery order. and you use warehouse task 4 to move products from storage type 2 to the goods issue zone.SAP Online Help 20. Item 2 of the warehouse request results in the three warehouse tasks 2. Warehouse Task 4 Source – Dest. 3. Item 2 Storage Type 2 WT 2 WT 3 Item 3 Warehouse Task 6 Source – Dest. SAP Extended Warehouse Management (SAP EWM) 510 318 .2007 Warehouse Request Warehouse Task Warehouse Storage Type 1 Item 1 Warehouse Task 1 Source – Dest. This is the case. WT 4 Goods Issue Zone To remove the product from stock.

EWM automatically creates the warehouse task for stock removal. see Storage Bin Determination for Stock Removal [Seite 343]. Features ● EWM can create warehouse tasks for an outbound delivery in the following ways: ○ ○ ○ ● As default. sections. 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.SAP Online Help 20. In the warehouse task. You create the warehouse tasks manually. For more information. When EWM creates a warehouse task. see Warehouse Order Creation [Seite 419] EWM uses layout-oriented and process-oriented storage control. so that you can remove products from stock. EWM specifies various activities for you to perform (for example. ● ● EWM automatically groups warehouse tasks according to your Customizing settings for warehouse orders. EWM creates warehouse tasks for an outbound delivery when you or EWM release a wave. For more information. The warehouse task reflects the direct or combined storage control. see Process-Oriented Storage Control [Seite 336] and Layout-Oriented Storage Control [Seite 340]. you must have made the settings in Customizing for warehouse order creation. For more information.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]. For more information. and bins The path to the destination storage type Prerequisites If you want EWM to automatically group warehouse tasks into warehouse orders. EWM uses a warehouse task to specify the following for the stock removal: ● ● The source storage types. packing) according to your Customizing settings. When EWM creates a warehouse task for a warehouse request. it uses stock removal strategies [Seite 396] to determine the storage bin.07. SAP Extended Warehouse Management (SAP EWM) 510 319 . see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Warehouse Order. according to your Customizing settings. using an action from the Post Processing Framework (PPF). EWM automatically creates warehouse tasks for an outbound delivery. ● ● Activities ● If you have made settings in Customizing for PPF for the PPF action to create warehouse tasks for stock removal.

EWM carries out this update by updating the quantity in the document flow. you or EWM create warehouse tasks by releasing a wave. For more information. and then want to post the goods issue. and WT3) for the entire quantity. on the SAP Easy Access screen. the warehouse request status Picking Planning changes to Completed. it simultaneously updates this warehouse request. After a wave is generated.07. choose Extended Warehouse Management → Work Scheduling → Create Warehouse Task for Warehouse Request → Stock Removal for Outbound Delivery Order. choose Extended Warehouse Management → Shipping and Receiving → Load. ● If you want to create a warehouse task manually. When EWM creates a warehouse request warehouse task for an outbound delivery request.SAP Online Help 20. either automatically or manually depending on the release methods you have defined for the wave or wave template. ● ● You have an outbound delivery of 100 pieces of a product. The following table provides an overview of the Picking Planning status in the warehouse request. If EWM does not create warehouse tasks for the entire quantity. ● By default. it can be released immediately. based on the stock determination. Following creation of the warehouse tasks. see the IMG for EWM. If you create warehouse tasks for a delivery for loading. If the quantity update leads to a change in status. the Picking Planning status is set to Partially Completed. EWM automatically creates three warehouse tasks (WT1. WT2. see Processing of Waves [Seite 771]. 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 . on the SAP Easy Access screen.2007 For more information. EWM updates this change in the warehouse request as well. under Cross-Process Settings → Delivery Processing → Actions → Use Assistant to Create Actions.

Integration Specification of the stock removal path is integrated into WT processing. SAP Extended Warehouse Management (SAP EWM) 510 321 . and have specified the sorting sequence of the activity areas. it specifies this stock removal path. For more information. Activities . EWM determines the stock removal path according to your settings in Customizing and saves this information in the WT. For more information.07. On the radio frequency device. ● You have assigned an activity to a warehouse process type. see the IMG for EWM under Master Data → Activity Areas. ● You have defined activity areas and categories. You skip the source storage bin proposed by EWM and process the next one. Features If EWM has grouped several WTs into a warehouse order. EWM places this source storage bin at the end of the RF display. refer to the Implementation Guide (IMG) for EWM under Master Data → Storage Bins. which means that EWM sorts the WTs according to the stock removal path. you can skip a source storage bin proposed by EWM. In so doing. If you use radio frequency devices. This is regardless of which products or HUs are on the storage bins. you or EWM create the necessary WTs for the warehouse request for the outbound delivery order. EWM shows the destination storage bins in this predefined sequence. For your stock removal. Prerequisites ● You have defined the storage bin types. For more information.SAP Online Help 20. You cannot gain access to a source storage bin because a colleague is currently removing products from it. However. descriptions.2007 Stock Removal Path Determination Use You can use this function to specify a stock removal path for each activity in the activity area.. only one stock removal path is active for each WT. When Extended Warehouse Management (EWM) creates a warehouse request (WT). see the IMG for EWM under Cross-Process Settings → Warehouse Task → Define Warehouse Process Type. During definition of stock removal paths. you can assign more than one stock removal path. then it sorts the WTs based on the warehouse order. have assigned storage bins to the activity areas. or you can allow activity areas to overlap. and structure..

c. b. 3. d.. see Partial Picking [Seite 325]. For more information. see Pick and Pack During Picking [Seite 323]. transferred them to the goods issue zone or packing station. You can enter differences that arise during picking.07. For more information. 1.. It thereby determines the stock removal path. You can use the warehouse order as the pick list. Process . EWM creates the corresponding warehouse tasks for the warehouse request and assigns them to one or more warehouse orders. SAP Extended Warehouse Management (SAP EWM) 510 322 . 2. You can carry out a partial picking or a complete picking. You can also process the warehouse orders using radio frequency devices. You have removed the products from your warehouse.SAP Online Help 20. For more information. see Printing Warehouse Orders and Warehouse Tasks [Seite 426] and Processing Using Radio Frequency [Seite 797]. for example. For more information. You can process and confirm the warehouse task as follows: a. 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 can print the individual warehouse order and process it. In doing so. For more information. EWM uses stock determination to find the required stock. You can pack products during the picking process. EWM allocates the individual warehouse tasks to a warehouse order and thus builds work packages for the individual warehouse workers. You or EWM create the warehouse tasks for the outbound delivery. and confirmed the associated warehouse tasks. For more information. see Creation of Warehouse Tasks for Stock Removal [Seite 319] or Storage Bin Determination for Stock Removal [Seite 343]. see Warehouse Order Creation [Seite 419] and Stock Removal Path Determination [Seite 321].2007 Picking Purpose You can use picking to remove goods from your warehouse for a warehouse request for outbound delivery order [Seite 112].

When EWM creates a warehouse order. select Cross-Process Settings → Handling Units → Basics → Define Packaging Material. choose Master Data → Product → Maintain Product. ● You have defined a packaging material. see under “Activities“. determine which steps you want to execute automatically using EWM. ● Manual creation and assignment of pick HUs during warehouse task confirmation EWM does not create any pick HUs. Features In the Implementation Guide (IMG). as follows: ● Automatic creation and assignment of pick HUs When EWM creates a warehouse order. For more information about making settings in Customizing for the individual steps. for the creation of a warehouse order. activity area. nor does it determine a packaging material. SAP Extended Warehouse Management (SAP EWM) 510 323 . you can confirm the proposals for the packaging materials and manually create your own pick HUs. you can manually change the pick HUs and their assignments to the warehouse tasks. It assigns the pick HUs to the warehouse tasks in the warehouse order (optional).SAP Online Help 20. see Packing During Warehouse Task Confirmation [Seite 511]. For more information about packaging materials. you can set the packing proposals for any number of combinations of warehouse order. ● Automatic proposal of packaging materials When EWM creates a warehouse order. you can manually assign the pick HUs to the warehouse task.2007 Pick and Pack During Picking Use You can generate pick handling units (pick HUs) into which you can pack products during picking. When you confirm the warehouse tasks for the warehouse order. you can make settings for which packaging material the system should propose for picking. and movement type. In Customizing for EWM.07. ● In Customizing. it automatically proposes the number of pick HUs with the required packaging material. When you confirm the warehouse task. see Packaging Materials [Seite 492]. On the SAP Easy Access screen. Extended Warehouse Management (EWM) assigns the pick HU to a warehouse task. You thus do not need to execute any further packing for the delivery. it automatically creates one or more pick HUs with the specified packaging material. You or EWM transfer the pick HUs to the delivery. When you confirm the associated warehouse tasks. Prerequisites ● You have created a product that is a packaging material. You can create the pick HUs manually. For more information about packing.

07. ● For more information about the packing profile. If you want to manually create and assign pick HUs. If you want EWM to automatically assign pick HUs to the warehouse tasks in the warehouse order. SAP Extended Warehouse Management (SAP EWM) 510 324 . If you want EWM to automatically propose the number of pick HUs with the required packaging material.SAP Online Help 20. choose Cross-Process Settings → Warehouse Order → Define Packing Profile for Warehouse Order Creation. choose Cross-Process Settings → Warehouse Order → Define Packing Profile for Warehouse Order Creation. ○ ○ ○ ● Define a packing profile. then in Customizing for EWM. in other words. choose Assign HUs to WTs. Activities ● If you want EWM to automatically create and assign the pick HUs. If you want EWM to automatically create pick HUs.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 do not define a packing profile in Customizing for EWM. you can split the warehouse task item and pick in a newly-created pick HU. and define a packing profile without choosing Create HUs or Assign HUs to WTs. you can execute a partial picking. see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings → Warehouse Order → Define Packing Profile for Warehouse Order Creation. then in Customizing for EWM. select Create HUs.

2007 Partial Picking Use In a partial picking. ● You have created an outbound delivery with two products of 50 pieces each. 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. so that EWM warns you in the user interface for warehouse task creation for warehouse requests. Prerequisites If you want to execute a complete picking. 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. such as wave release or processing using a Post Processing Framework action (PPF action). EWM executes a partial picking. ● so that EWM does not create a warehouse task during a background processing. even though it cannot completely fill all items for the outbound delivery. Extended Warehouse Management (EWM) can create a corresponding warehouse task for an outbound delivery. so that only 40 pieces remain. Activities The following table provides an overview of the possibilities within partial picking. that the required quantity is underfilled and that a complete picking is required.SAP Online Help 20. EWM notifies you that it cannot completely fill the picking requirements. You can cancel the warehouse task creation or save the warehouse task created internally. you have taken from the warehouse 10 pieces from the product in the second outbound delivery item. You use the complete picking. Partial picking is allowed EWM automatically adjusts the outbound delivery quantity to the warehouse task quantity.07. SAP Extended Warehouse Management (SAP EWM) 510 325 . If the available quantity in the warehouse is not sufficient to fill all items of the outbound delivery. If you create a warehouse task for this outbound delivery. you need to have made the settings for complete picking for warehouse order. Since creation of the outbound delivery. By default. in Customizing for Extended Warehouse Management (EWM) under Cross-Process Settings → Warehouse Task → Define Warehouse Process Type. Procedure In Customizing for Extended Warehouse Management. you can prevent the creation of a warehouse task.

On the SAP Easy Access screen. You can create additional warehouse tasks so that EWM can fill all items of the outbound delivery.SAP Online Help Differences.2007 EWM transfers the warehouse task quantity as warehouse request quantity to the corresponding item of the warehouse request.07. EWM has not yet completely picked the outbound delivery. 20. Neither you nor EWM adjust the outbound delivery quantity to the picked quantity. Adjust the outbound delivery quantity to the warehouse task quantity. You manually adjust the outbound delivery quantity to the picked quantity. Choose Change Mode and then Adjust Delivery Quantity. Define the delivery adjustment in the case of differences. SAP Extended Warehouse Management (SAP EWM) 510 326 . choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order.

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.2007 Pick Denial Purpose If Extended Warehouse Management (EWM) creates a warehouse task with reference to a warehouse request for an outbound delivery order. In these cases there is a pick denial. or not enough. adjust the quantity in the warehouse request to the picked quantity. You can start a background job. Process . 1. or can only create a warehouse task with a partial quantity. see the IMG for EWM under Goods Issue Process → Pick Denial → Activate Pick Denial at Warehouse Number Level. and have assigned these to the internal exception codes defined by SAP. see the Implementation Guide (IMG) for EWM under Business Add-Ins (BAdIs) for Extended Warehouse Management → Cross-Process Settings → Warehouse Task → BAdI: WT Creation. If you have specified an action in Customizing. ● You have defined your own exception codes for calling exception handling. You or EWM perform the following: SAP Extended Warehouse Management (SAP EWM) 510 327 . it performs exception handling according to your Customizing settings. using a Post Processing Framework action or a wave release. For more information. you have activated pick denial at warehouse process type level. or can only create a warehouse task with a partial quantity. For more information. you have not specified that warehouse task creation should be canceled. for example. For more information. it is possible that EWM cannot create a new warehouse task. However. stock to fulfill the requested quantity of the warehouse request.. EWM compares the requested quantity with the warehouse task quantity. EWM triggers an alert and creates a workflow task. 2. Prerequisites ● For the case that EWM cannot completely fulfill the requested quantity of the warehouse request. If the system determines differences. ● In Customizing. for example. You or EWM want to create a warehouse task. see the IMG for EWM under Goods Issue Process → Pick Denial → Activate Pick Denial at Warehouse Process Type Level. ● In Customizing.SAP Online Help 20. EWM cannot create a new warehouse task.07. For more information.. This is caused by one of the following reasons: ● ● You have performed a storage bin denial. EWM cannot find any. you have activated pick denial at warehouse number level. 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. 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 proceed as follows: ■ Confirm the action suggested by your Customizing settings by choosing Save . or delete it and create a new warehouse task.“ SAP Extended Warehouse Management (SAP EWM) 510 328 . ■ Change the action suggested by your Customizing settings and then choose Save . informing you that a pick denial has occurred. EWM does not send a message to ERP for a direct outbound delivery order. ■ Execute the workflow using the action proposed by the system suggested by your Customizing settings. Result Depending on your Customizing settings. by choosing SAP Office → Folders → Inbox. ● ● The system did not execute an action. 3. for example if you still have stock in another storage type.07. and sent a message about the pick denial to ERP if required. ○ If EWM creates the warehouse task in background mode. EWM sends a message to ERP about the pick denial. Depending on your Customizing settings. it triggers a pick denial according to your Customizing settings. and performs any follow-up activity in the background. informing you that EWM could not create a warehouse task. EWM only adjusts the outbound delivery quantity for the direct outbound delivery order. The system adjusted the quantity in the warehouse request to the picked quantity. see Processing of Outbound Deliveries [Seite 253] under “Notification of an outbound delivery change to the ERP system.2007 If you create the warehouse task in online mode.SAP Online Help ○ 20. For more information about reporting a change to an outbound delivery. EWM has executed the action for pick denial in the background. or could only create a warehouse task with a partial quantity. EWM executes a pick denial and executes a workflow in the background. If you use wave management. EWM also writes an entry into the wave management log. EWM displays a warning. depending on your Customizing settings. EWM executes a pick denial and executes a workflow in the background.

HUs or WTs. In addition. EWM calls the transaction for moving HUs. You can choose between the following options: ... you enter the outbound delivery that contains the WR item that you want to cancel.2007 Cancellation of Picking Use If you have picked too much. You define the new WT by creating storage bins or the warehouse process type for the new WT. Activities Release Stock From One or More WR Items You can cancel stock that has already been picked for one or more WR items. On the Open Product WT tab page. For more information. If the stock is packed. EWM gives you information that is relevant for the cancellation of picking for the WR item. 2. for example. . This makes the stock freely available again. ● Features EWM cancels previously picked stock of warehouse request items (WR items) or handling units (HUs). see the IMG for EWM under Goods Issue Process → Cancel Picking → Define Warehouse Number Control for Putback. 3. If the stock is unpacked. To do this. the system can also create a new WT at the same time. You have defined the warehouse process type for the cancellation of picking as a default value. choose Extended Warehouse Management → Execution → Cancel Picking. EWM starts by releasing the stock. EWM can only release stock for the highest-level HU. If EWM releases the assignment of a stock. you can cancel an outbound delivery either partially or completely. For more information. On the Stock tab page. If EWM is creating the 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.SAP Online Help 20. such as where the different stock is located in the warehouse. see the Implementation Guide (IMG) for EWM under Goods Issue Process → Cancel Picking → Define Warehouse Process Type for Putback. For packed stock. In the Document Number field for the search. the system proceeds as follows: . EWM can only release stock for complete HUs. Prerequisites If you want to release stock and simultaneously create a warehouse task (WT) in the background.07. EWM shows you all WR items that belong to this outbound delivery. 1. for example.. EWM releases the assignment of picked or reserved stock from the WR items.. the system releases the stock and simultaneously creates a new WT with the specified warehouse process type.. If EWM is creating the WT in the foreground.. EWM gives you information about the stock. or if you require previously picked stock more urgently for another outbound delivery. EWM displays the open product WTs of the WR items. EWM then calls the transaction for moving products. On the Warehouse Request Items tab page. as well as reserved stock of WTs. SAP Extended Warehouse Management (SAP EWM) 510 329 . on the SAP Easy Access screen.

SAP Online Help ● 20. You can cancel a partial quantity of the picked delivery quantity of a selected stock in the WR item only. You can cancel the reserved delivery quantity of a selected WT in the WR item only. To do this. ● You can release the entire picked delivery quantity for an HU. 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. You select the serial numbers that you want to cancel. On the Stock tab page you then select the stock that you want to cancel. ● ● ○ Release Stock From One or More HUs You can cancel stock that has already been picked for one or more HUs. To do this. However. EWM then cancels all WTs that belong to the selected WR item. on the Handling Unit tab page choose Repack HU (see Packing in the Work Center [Seite 506]). You start by choosing Serial Numbers. on the SAP Easy Access screen. On the Open Product WT tab page you then select ● SAP Extended Warehouse Management (SAP EWM) 510 330 . In the Cancel Quantity field on the Stock tab page. you enter the HU that you want to cancel. In the Handling Unit Identification field for the search. and then choose Release Stock. on the Warehouse Request Items tab page you select the WR item whose WTs you want to cancel. on the Warehouse Request Items tab page you select the WR item that you want to cancel. EWM displays the corresponding information on the Stock tab page. To do this. you can do the following: ○ You first specify the delivery quantity to be cancelled in the Cancel Quantity field and then choose Serial Numbers.07. on the Warehouse Request Items tab page. and then choose Release Stock. select the WR item that contains the corresponding WT. on the Warehouse Request Items tab page. select the WR item that contains the corresponding stock. you then specify the delivery quantity that is to be cancelled for this stock. and then choose Release Stock. To do this. To do this. ● You can cancel the entire reserved delivery quantity for a WR item. To do this. If you are working with serial number requirement Serial Numbers in Inventory Management [Seite 585]. you cannot edit this data. To do this. In the Document Number field for the search. select the WR item that contains the corresponding stock. You select the serial numbers that you want to cancel.. ● If you want to cancel a partial quantity of an HU only. on the Warehouse Request Items tab page. you enter the outbound delivery that contains the WR item whose WT you want to cancel.2007 You can release the entire picked delivery quantity for a WR item.. EWM displays all the serial numbers for the selected stock. If you have packed multiple stocks into an HU. and then choose Cancel WT. on the SAP Easy Access screen. EWM automatically calculates the delivery quantity that you have to cancel. You can cancel the picked delivery quantity of a selected stock in the WR item only. choose Extended Warehouse Management → Execution → Cancel Picking. You can choose between the following options: . choose Extended Warehouse Management → Execution → Cancel Picking. on the Handling Unit tab page you select the HU that you want to cancel. EWM displays the serial numbers corresponding to the cancel quantity. To do this. and displays it in the Cancel Quantity field. you first have to repack the HU. EWM shows you all WR items that belong to this outbound delivery.

you choose Release Stock + Create WT. instead of choosing Release Stock. Release Stock and Create WT Simultaneously (WR Item or HU) Corresponding to the above descriptions for releasing stock for WR items and HUs. on the SAP Easy Access screen. However. In the Handling Unit Identification field for the search. On the Handling Unit tab page. To do this.07. EWM can simultaneously release stock and create new WTs (either in the foreground or in the background). choose Extended Warehouse Management → Execution → Cancel Picking. To do this. SAP Extended Warehouse Management (SAP EWM) 510 331 . you enter the HU that you want to cancel. Cancel WTs From One or More HUs You can cancel stock that has already been reserved for one or more HUs. follow the descriptions above for releasing stock.2007 the WT that you want to cancel. You then select either Release Stock + WT in Foreground or Release Stock + WT in Background from the dropdown box. and then choose Cancel WT.SAP Online Help 20. EWM then cancels all open WTs that belong to these HUs.. you choose the corresponding HUs and then choose Cancel WT. EWM then cancels the selected WTs only.

or you manually generate the warehouse request in EWM as a direct outbound delivery order [Seite 167]. However. 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. loading for transportation. On the SAP Easy Access screen. On the HU tab page. ○ If you have configured goods movement bin determination. choose Extended Warehouse Management → Settings → Maintain Goods Movement Bin Determination. choose one of the following options: ■ ■ You specify the items with their stock attributes and quantities on the Items tab page. You specify all the relevant stock attributes of the product (for example. 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. EWM automatically suggests a goods movement bin.. 1. 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. Process . 3.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].. ○ 2. in contrast to picking.07. Extended Warehouse Management (EWM) does not generate any warehouse tasks for the warehouse request or any warehouse orders.SAP Online Help 20. for example. see the Implementation Guide (IMG) for EWM under CrossProcess Settings → Delivery Processing → Status Management → Define Status Profiles. You post the goods issue for the outbound delivery order. You remove the products from your warehouse and perform any other relevant goods issue steps. SAP Extended Warehouse Management (SAP EWM) 510 332 . 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. Then EWM automatically creates the corresponding items with their stock attributes and quantities. you choose the Create and Save pushbuttons and specify a handling unit (HU) and an item type. the stock type) and a goods movement bin in the warehouse request.

posted the goods issue (for example in sell from stock) or performed additional goods issue activities. SAP Extended Warehouse Management (SAP EWM) 510 333 .SAP Online Help 20. and have then posted goods issue.07.2007 Result EWM has generated a warehouse request for an outbound delivery order. You have removed the products from your warehouse.

This contains the procedure. The handling unit thus contains the information concerning what process steps are required for the putaway or stock removal. via delivery type and delivery item among others. counting) within the goods receipt process The following parameters are possible: SAP Extended Warehouse Management (SAP EWM) 510 334 . During putaway or stock removal. an individual process step can be executed on single level basis or on multi level basis (that is. The layoutoriented storage control then checks whether the sequence of putaway process steps is possible in layout view.SAP Online Help 20. adjusts the flow of the putaway or stock removal. Based on the process-oriented storage control. Here. in other words. You can combine the process-oriented storage control with the layout-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. the warehouse process type. through intermediate storage types). The goal of storage control is to display your complex putaway or stock removal process steps based on your processes or your layout data. ● ● ● ● 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.07. and if required. EWM transfers this operation to the handling unit to be put away or removed from stock. EWM always executes the process-oriented storage control first. the putaway or stock removal process with different activities. Prerequisites You have defined the following in Customizing for the putaway: ● Paramaters that specify the work station determination for the next function (for example.2007 Storage Control Use You can use the process-oriented as well as layout-oriented methods for storage control.

Features For information about the features of storage control.SAP Online Help ○ ○ ○ ○ ● 20. among others.07. SAP Extended Warehouse Management (SAP EWM) 510 335 . see Process-Oriented Storage Control [Seite 336] and Layout-Oriented Storage Control [Seite 340].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.

In addition. see Storage Control [Seite 334]. EWM assigns these process steps to a handling unit as soon as it has created or changed them. In doing so. or deconsolidating [Seite 298]. choose Cross-Process Settings → Warehouse Task → Define Process-Oriented Storage Control. such as unloading.2007 Process-Oriented Storage Control Use You use this type of storage control to map complex putaways or stock removals. SAP Extended Warehouse Management (SAP EWM) 510 336 . internal or external process steps can be simple. Activities For Customizing of process-oriented storage control. EWM copies the predefined process steps from the storage process type to the handling unit.07. During goods receipt or goods issue. Extended Warehouse Management (EWM) recognizes internal process steps predefined by SAP and external steps that you can define yourself. Prerequisites For more information about the prerequisites. for example. The process steps for the processes Counting and Deconsolidating predefined by SAP can be dynamic [Extern]. or combined. For more information. you combine your storage process steps into one storage process. counting. Integration For more information about integration. Features You define the process steps for your complex storage process. unloading. see Direct and Combined Storage Control [Seite 268]. Your external process stesps can base themselves on internal ones. see Storage Control [Seite 334]. You can also trace the status of the individual process steps. A process step is. such as deconsolidating. in the Implementation Guide (IMG) for EWM. Process-oriented storage control only operates with handling units.SAP Online Help 20.

see Storage Control [Seite 334] . you do not have to define anything in the process-oriented storage control [Seite 336]. see Updating the Outbound Delivery Order in the GI Process [Seite 339]. For information about integration and the prerequisites. packing station).SAP Online Help 20. If you want to define complex stock removal processes. it creates one warehouse task per route section for this HU.07. 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. The following graphic shows you the relationship between direct putaway and creation of warehouse tasks. you have to use a combined processoriented storage control. For more information about updating the status. 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. Extended Warehouse Management (EWM) uses this during creation of a warehouse task to determine the intermediate storage types (for example.2007 Direct and Combined Storage Control (Stock Removal) Use If you want to execute a direct stock removal. ● One warehouse task that describes the route from source storage type to intermediate storage type SAP Extended Warehouse Management (SAP EWM) 510 337 .

For example. or to the final destination storage type. you can determine the final destination storage type either right at the beginning of your stock removal process. ● Based on your settings in Customizing. or later. you can distribute HUs containing different products to stock removal HUs.3 Destination Storage Type 9021 SAP Extended Warehouse Management (SAP EWM) 510 338 .1 Storage Type 8020 Warehouse Task 2.07. You can carry out different activities at the intermediate storage types.2007 Irrespective of your settings in Customizing.2 Intermediate Storage Type 8030 Warehouse Task 2. see Updating the Outbound Delivery Order in the GI Process [Seite 339].1 Intermediate Storage Type 8010 Warehouse Task 1. you can break these down into storage sections and storage bins. The following graphic shows you the relationship between combined stock removal and creation of warehouse tasks. EWM also creates a warehouse task per product contained in the HU. EWM manages the intermediate storage types in the same way as standard storage types. For more information about updating the status. Intermediate Storage Type 8000 Goods Issue Area Source Storage Type 0010 Warehouse Task 1.2 Destination Storage Type 9020 Source Storage Type 0020 Warehouse Intermediate Task 2. one warehouse task from the intermediate storage type to the next intermediate storage type. at an intermediate storage type. In combined stock removal. For example.SAP Online Help 20. within a stock removal process.

07. You confirm the first product WT for picking. EWM sets the status Picking in the outbound delivery order. ● . You or EWM generate the first product warehouse task (product WT). c.. You or EWM generate the first product WT.. EWM sets the status Picking Planning in the outbound delivery order. SAP Extended Warehouse Management (SAP EWM) 510 339 . You confirm the first product WT for picking. d. b. Features EWM updates the outbound delivery order for the following GI processes: ● You: Unpacked stock a. Packed stock a. 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. e. b. f.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). EWM sets the status Loading in the outbound delivery order. You pack the stock. EWM sets the status Picking Planning in the outbound delivery order. You confirm the loading WT. meaning the destination location corresponds to a bin at the door or to a TU. You or EWM generate the related loading warehouse task (loading WT). EWM sets the status Picking in the outbound delivery order.SAP Online Help 20.

SAP Extended Warehouse Management (SAP EWM) 510 340 . You use layout-oriented storage control in the material flow system [Seite 820] to define conveyor segments. Features For layout-oriented storage control. Prerequisites For more information about the prerequisites. 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.07. For this activity. Activities For Customizing of layout-oriented storage control. see Storage Control [Seite 334]. you define external warehouse process steps for your warehouse. and a second from identification point I to storage bin B. Integration For more information about integration. The layout-oriented storage control only operates with handling units.SAP Online Help 20. including identification points [Extern] and pick points [Extern]. see Storage Control [Seite 334]. You can move your goods using a pick point during picking. rather travel via intermediate storage bin.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. Extended Warehouse Management (EWM) splits the warehouse order into two: one from storage bin A to identification point I. choose Cross-Process Settings → Warehouse Task → Layout-Oriented Storage Control. If you want to move a product pallet from storage bin A (goods receiving area) to storage bin B (high rack storage area). For example. One exception is the process display with picking or identification points. you have a high rack storage area. in the Implementation Guide (IMG) for EWM.

stock determination occurs in the background during creation of warehouse tasks. EWM takes into account own stocks. If the required stock is larger than the stock found. For more information about Customizing for stock determination. in the case of internal movements. EWM executes stock determination during creation of the warehouse task.07. it uses the stock removal sequence to check the existing stocks for the corresponding stock. EWM considers the warehouse number stock characteristics Owner and Stock Type as defined by you. and. you define a valuation to evaluate stocks of different owners or different stock types in a different manner. or it notifies you that it can only find a portion of the required stock. and have saved these groups in the master record so that EWM can execute stock determination for a product. different stock types. Extended Warehouse Management (EWM) determines in which sequence and from which storage types and stocks you should remove the desired product. 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.SAP Online Help 20. The stock removal sequence arises from prioritizing individual stocks according to the valuation you have defined. for a stock determination strategy that the system uses to reduce stock. consignment stocks. EWM continues this process until it finds enough stocks for the required stock. You have made the settings in Customizing for EWM under Cross-Process Settings → Stock Determination → Set Stock Determination. EWM first searches through existing stocks according to the stock characteristics that have the highest number of points. In doing so. EWM searches the existing stocks according to the stock characteristics that have the next highest number of points. Stock Determination Strategies You can define the following stock determination strategies: Stock Determination Dominates During stock removal. In so doing.2007 Stock Determination Use You use stock determination to apply stock removal strategies during picking and stock transfers. SAP Extended Warehouse Management (SAP EWM) 510 341 . Prerequisites You have set stock determination groups in Customizing for EWM under Cross-Process Settings → Stock Determination → Maintain Stock Determination Groups. Based on the recorded product requirements. In so doing. based on predefined settings in Customizing.

07. It stores the required quantities and in so doing. to fill the warehouse task’s required quantity. and thus have undertaken a prioritization. ● If you have defined the strategy Stock Determination Dominates for the stock determination group 01. the stocks found per storage type are removed from stock according to descending number of points. according to the set stock removal strategy. If you have defined the strategy EWM Dominates for the stock determination group 01. such as FIFO.SAP Online Help EWM Dominates 20. Activities In Customizing for EWM under Cross-Process Settings → Stock Determination → Maintain Stock Determination Groups. You have made settings in Customizing for stock determination to define valuation points for the individual owners. EWM searches the warehouse for own stock and for stock from owner SCHMIDT. To do this. only takes into account the stock removal rule defined in EWM. it also searches for stocks from owner SCHMIDT and uses stocks found here as well. EWM removes the oldest quant from stock. ● 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. 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). using the stock determination strategy Stock Determination Dominates. irrespective of whether this is an own stock or a consignment stock. EWM considers all allowed stocks. You can also use the stock determination’s number of points as sort criterion in the stock removal rule. You define the stock removal sequence by using the storage type search sequence and the stock removal strategy. you define the following in Customizing for EWM: ● Maintain stock determination group You define the stock determination group 01 for warehouse 001. You can use this prioritization to sort stocks for a storage type or storage type group. so that for example. In this case. ● SAP Extended Warehouse Management (SAP EWM) 510 342 . 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.2007 During stock removal. regardless of the stock characteristic of the warehouse number. define the stock determination strategy (stock determination dominates or EWM dominates). such as FIFO [Extern].

for example. You make the settings for these stock removal strategies [Seite 396] in Customizing. The system determines the stock removal search sequence on the basis of the parameters from the WT. You have assigned the stock removal rule to the storage type in Customizing for EWM under Master Data → Define Storage Type. First Out). ● ● ● 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 system uses the stock removal rule that you have defined for the storage type or the storage type group. Here. the system calls the determination of stock removal search sequences to determine the stock removal rule. 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. Prerequisites ● You have defined a stock removal rule in Customizing for Extended Warehouse Management (EWM) under Goods Issue Process → Strategies → Specify Stock Removal Rule. In Customizing. If you enter the storage type or the storage type group manually. The stock removal rule specifies the order in which the system is to sort the individual quants. you can link a stock removal rule to a stock removal search sequence. Storage bin determination for stock removal occurs automatically when warehouse tasks (WTs) are created.SAP Online Help 20.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. You can use the BAdIs in the /SCWM/ES_CORE_RMS enhancement spot to make changes to the result. FIFO (First In. You can define the business strategy according to which the storage bin determination for stock removal is to run. If you have not linked the stock removal rule and the stock removal search sequence to one another. for example. 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 343 . This means that the stock removal rule is fixed for all storage types belonging to the stock removal search sequence. You have defined a storage type search sequence in Customizing for EWM under Goods Issue Process → Strategies → Specify Storage Type Search Sequence. Alternatively.07. the system uses parameters from the product master that you have defined manually or those that the system has determined in slotting [Seite 277]. 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.

Sorting the Quants The system uses the stock removal rule that was found to sort the stock that was determined. and so on. You can use the BAdIs in the /SCWM/ES_CORE_RMS enhancement spot to make changes to the result. the system takes the next quant. Selection of a Quant The system chooses the first quant that was found. SAP Extended Warehouse Management (SAP EWM) 510 344 . If it cannot use this quant. for example. because the quantity is insufficient or the storage bin is locked for stock removal. and checks it.SAP Online Help 20.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.07.

You can also specify the storage type or storage section. EWM determines these values when you save your details. you have set the Determine WkCtr indicator in the used warehouse order creation rule. EWM checks these settings when you save your details. ● Activities On the SAP Easy Access screen. under Extended Warehouse Management → Cross-Process Settings → Warehouse Order → Define Creation Rule for Warehouse Orders. You also specify at least the storage bin for the work center determination.2007 Work Center Determination in Goods Issue Use In Extended Warehouse Management (EWM). 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. storage section and storage bin to the warehouse tasks that it bundles using the warehouse order creation rule used here. Prerequisites In Customizing for EWM. the storage type must have the storage type role Work center.07. EWM first attempts to find a work center matching your criteria. You can specify various criteria for this determination. you can have the system determine a work center [Seite 35] in goods issue. This enables you to have the system determine a special work center for packing. You can specify any number of criteria for the determination. this has to have the putaway rule Consolidation Group. for example. If you do not specify a storage type or storage section. choose Extended Warehouse Management → Master Data → Work Center → Determine Work Center in Goods Issue (/SCWM/PACKSTDT). If it cannot find a work center. ● If you specify the storage type or storage section. Result EWM analyzes the details that you enter here. SAP Extended Warehouse Management (SAP EWM) 510 345 . EWM uses your criteria during warehouse order creation [Seite 419]. EWM assigns the determined destination data storage type. depending on the route.SAP Online Help 20. If you only specify a storage type. 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.

Otherwise. optionally. you have defined a minimum replenishment quantity in the warehouse product master.SAP Online Help 20. but the system can also use it at fixed storage bin level. restricted storage types. You have also defined the following: ○ If you want to work with replenishment at storage type level. ● You have defined a default stock type for replenishment in Customizing under Extended Warehouse Management → Master Data → Define Warehouse Number Control. ● ○ If the system is to round replenishment quantities [Extern]. indicator for direct replenishment and have. 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. the system creates a warehouse request or changes an existing warehouse request. SAP Extended Warehouse Management (SAP EWM) 510 346 . you have set the WT Immed. ○ ● 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. 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. 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 automatically create a warehouse task when executing replenishment. You can only define the minimum replenishment quantity at storage type level.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. If you want to work with replenishment at fixed storage bin level.07. you have defined the minimum quantity and the maximum quantity in the warehouse product master. If you want to work with picker-directed replenishment. you have set the PckrDrvn Repl. indicator.

Replenishment control is triggered when the stock is less than the minimum quantity. the system must have found stock in the permitted storage types. The system rounds down the replenishment quantity to a multiple of the minimum replenishment quantity. As a prerequisite. We recommend that you use picker-directed replenishment if the reserve storage area is situated close to the picking area. Automatic replenishment The system starts automatic replenishment in the background when you confirm a warehouse task. The system rounds down the replenishment quantity. Picker-directed replenishment is only possible in radio frequency scenarios. It is started during a bin denial when an exception code refers to the internal process code Replenishment. on the SAP Easy Access screen. In this case. a warehouse task is displayed for the replenishment as the next item to be processed in the picker’s warehouse order. The system rounds up the replenishment quantity to a multiple of the minimum replenishment quantity. Activities To start planned replenishment or order-related replenishment. Replenishment control is triggered when the stock is less than the required quantity. SAP Extended Warehouse Management (SAP EWM) 510 347 .2007 Features The following types of replenishment control are available: Planned replenishment You can start planned replenishment either interactively or in the background.07. The system calculates the replenishment in accordance with the quantity of the selected open warehouse requests. in other words. to a multiple of the minimum replenishment quantity. Direct replenishment can be performed by the picker (picker-directed replenishment). the quantity of the warehouse task or the warehouse request. It 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. Order-related replenishment You can start order-related replenishment either interactively or in the background. The maximum quantity can be exceeded. The system calculates the replenishment in accordance with the defined minimum quantity and maximum quantity.SAP Online Help 20. The system calculates the replenishment in accordance with the maximum and minimum quantity. Replenishment control is triggered when the stock is less than the minimum quantity. choose Extended Warehouse Management → Work Scheduling → Schedule Replenishment. Direct replenishment Direct replenishment is only possible in fixed storage bin scenarios.

You confirm the warehouse task with a difference of 5 pieces. You pick a quantity smaller than the quantity specified on the corresponding warehouse task. 1. You do not want to conduct a further picking for the warehouse request. You confirm the warehouse task difference. 6.2007 Handling Differences When Picking for Warehouse Request Purpose When you confirm a warehouse task.. you find only 45 pieces of the product in the storage bin. You want to remove a product from stock. Process .07.. Through this adjustment. You can post the goods issue for the warehouse request. you are to pick 50 pieces of the product PROD-01 from the storage bin 02-03-44. SAP Extended Warehouse Management (SAP EWM) 510 348 . After you have confirmed the further warehouse task for the warehouse request. 3. You can post the delivery for goods issue. the picking for the warehouse request is closed completely. 5. You record the quantity difference in the warehouse task by entering the quantity you have actually picked. You decide how to proceed: ○ You want to conduct another picking for the warehouse request.SAP Online Help 20. the pick status changes from Partially Completed to Completed. 4. According to the warehouse task for a warehouse request. EWM updates the quantity to be picked in the warehouse request. 2. EWM uses Adjust Delivery Quantity to equate the delivery quantity with the picked quantity. ■ ■ ○ You create a further warehouse task for the warehouse request. However. differences between the product quantity requested and the product quantity available may result. Results The warehouse request is completely picked.

see the SAP Library for SAP ECC under Logistics → Logistics .0 For more information. see the SAP Library for SAP ECC under Logistics → Logistics . ○ Advanced Planning and Optimization (APO): For more information. For more information about the SPM Goods Issue Process. All components of a kit must come from the same warehouse (this can be achieved by means of internal transfer between warehouses).2007 Kit to Order Purpose With this process. see the Implementation Guide (IMG) for SCM under Extended Warehouse Management → Goods Issue Process → Make Settings for Kitting. The kit header and kit component have a quantity ratio – defined by the kit structure – to each other.General (LO) → SAP Service Parts Management (SPM) → Goods Issue Process → Kit to Order → Customizing Settings. The following rules apply to kits: ● ● ● ● ● A kit is always delivered in full to a customer.07. you can have the system automatically assemble kits to order if there is no kit [Extern] in stock.General (LO) → SAP Service Parts Management (LO-SPM) → Goods Issue Process. Prerequisites You are using the following systems: ● SAP CRM 5. Kit prices are always calculated at kit header level. 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 Extended Warehouse Management (SAP EWM) 510 349 .0 For more information about the required Customizing settings. ● SAP SCM 5. This quantity ratio is recalculated as soon as there are changes at kit header level or at kit component level.0 ○ Extended Warehouse Management (EWM): For more information about the required Customizing settings. The kit header and the kit components are always scheduled for the same date. the SPM goods issue process takes place. see Availability Check for Kits [Extern]. If the kit is in stock. ● SAP ECC 6.SAP Online Help 20.

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. 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. 3. If the kit is not in stock.SAP Online Help 20. b.. e. For more information about editing sales orders. You create a sales order (SAP CRM) a. The system creates an unchecked delivery (SAP ECC-SPM) without creating an order.2007 Process . d. The system triggers the rule-based ATP check in SAP SCM for a requirement from the sales order. For more information. A requirement for a kit originates as an input product from the sales order. see the SAP Library for mySAP Customer Relationship Management under Components and Functions → Process Sales Orders. SAP Extended Warehouse Management (SAP EWM) 510 350 .07. The system then performs the ATP check for the kit components and confirms the quantities for the sales order. The system transfers the data from the sales order to SAP ECC. as well as checks for foreign trade determination. The system performs an ATP check and confirms quantities (SAP SCM-APO) The system checks whether the kit is in stock. One of the substitutions is a kit. 2. The system determines one or more rules with substitutions. The system initiates the credit check in SAP ECC. c.. The system then triggers the ATP check in SAP SCM. 1. The system performs the price determination and checks for the sales order.

11. 8.SAP Online Help 4. The system updates the data in the sales order (SAP CRM).07. For more information. 13. EWM uses the checked delivery to automatically create an outbound delivery order. When it receives notification from SAP ECC. The system confirms the delivery if exact delivery fulfillment is reported by EWM. 10. 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 updates the stock (SAP SCM-APO). 7. 12. You convert the unchecked delivery to a checked delivery (SAP ECC-SPM). SAP Extended Warehouse Management (SAP EWM) 510 351 . 6. see the SAP Library for mySAP Customer Relationship Management under Components and Functions → Process Sales Orders. a warehouse request for an outbound delivery. see the SAP Library for SAP ECC under Logistics → Logistics . 5. 9. that is. see the SAP Library for SAP ECC under Logistics → Logistics General (LO) → SAP Service Parts Management (SPM) → Goods Issue Process → Processing of Checked Deliveries. 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. 20. For more information. 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.2007 For more information. You pick the outbound delivery order (SAP SCM-EWM). see Availability Check for Kits [Extern]. For more information.General (LO) → SAP Service Parts Management (SPM) → Goods Issue Process → Transfer Posting for Kits. EWM creates a warehouse request for the outbound delivery (SAP SCM-EWM). For more information about posting goods issue. see Creation of a Warehouse Request for an Outbound Delivery Order [Seite 116]. The system posts the goods issue for the kits (SAP ECC-SPM). see Creation of a Warehouse Request for an Outbound Delivery Order [Seite 116]. The system executes billing (SAP CRM). For more information about editing sales orders. The system clears ATP-confirmed quantities (SAP SCM-APO).

SAP Extended Warehouse Management (SAP EWM) 510 352 . 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]).SAP Online Help 20. 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. Integration EWM supports kits in the kit to order [Seite 349] process.07.2007 Kit Definition Describes a piece list that you always deliver in a complete and assembled form. that is. kits in kits. 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.

2. You can print out this HU item in a HU list. 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).SAP Online Help 20. You generate warehouse tasks for the kit component items in EWM. 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. and confirm it to the ERP system. 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]). 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]). As free text that you have created in the warehouse request in EWM.07. Process . You have created a packaging specification for the product of the kit header item as master data. see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Issue Process → Make Settings for Kitting. 1. Prerequisites You have made all the required settings for kitting in Customizing. Depending on your Customizing settings. 4. You can assign a packaging material to the kitting level as a proposal for packing the kit. so that you can create a VAS order. You pick the kit component into a pick-HU and confirm the warehouse tasks. set the Create Kit Item indicator in Customizing. 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. In EWM. display it in the packing transaction. EWM receives an outbound delivery with kit component items from the ERP system.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 packaging specification must have a level of the level type Kitting. An outbound delivery with kit items exists in EWM.. SAP Extended Warehouse Management (SAP EWM) 510 353 . If you are using process-oriented storage control. For more information. You can display this text in the work center as additional information. 3. If the system is to automatically generate an HU item for the kit header in the pick-HU. The kit components are then at the kitting work center. Note that a packaging specification (and therefore a VAS order) can only have one level of the type Kitting.

If you have set the Create Kit Item indicator. 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. such as in the following instances: ● ● If you are not performing this step during kitting. 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.2007 If you have set the Create Kit Item indicator in Customizing and are working with pick-HUs. If you have not set the Create Kit Item indicator in Customizing. b. 1. You can report the work progress in the VAS order. or as a level of the packaging specification as well. and you have not set the Create Kit Item indicator in Customizing. You can also define your own warehouse process steps for packing kits into an HU. You can then use these items in the work center to repack the entire kit into another HU.07. but as an additional step at the same work center. 6. the system uses this HU item in goods issue posting to check whether the packed kits are complete. The decision as to whether you map additional steps as a step in the warehouse process only.SAP Online Help ○ 20. You can display the kitting instruction. 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. 3. You pack the kit into an HU and generate the HU item for the kit header. You generate an HU warehouse task to transport the HU to the goods issue zone. then you must generate the item manually after packing the kits in the work center at the latest. If the ERP system is dependent on an HU item for the confirmation. the system generates the kit header item in the pick-HU. Result You can ship the kit. 2. such as loading. you can generate the kit header item in the work center manually. ○ 5. The system only performs this check if the indicator is set in the item type of the kit header. depends on whether you want to document this step in the VAS order. If you are packing the kits into an HU at a different work center after kitting. meaning the system can therefore post these kits for goods issue. a. SAP Extended Warehouse Management (SAP EWM) 510 354 . You assemble the kit in accordance with the kitting instructions where required. You then post the goods issue for the warehouse request. the ERP system is dependent on this item (see also: Kit to Order [Seite 349]). You confirm the HU warehouse task.

2007 SAP Extended Warehouse Management (SAP EWM) 510 355 .SAP Online Help 20.07.

4. EWM checks whether it is to generate a VAS order for the kit header item automatically. see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings → Value-Added Services → Define Relevance for VAS Order.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). 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. Note that a packaging specification (and therefore a VAS order) can only have one level of the type Kitting.07. 1. EWM sets the VAS Order status of the kit items to Generated. VAS orders that are generated for a kit header item have a special structure.SAP Online Help 20. If you have activated the VAS Order status in the status profile of the item type for the warehouse request item. 3. Prerequisites You have made the required settings in Customizing for generating VAS orders automatically or manually. 2. You receive an outbound delivery with kit items from the ERP system. 3.. An outbound delivery with kit items exists in EWM. 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.. Manual Generation . You receive an outbound delivery with kit items from the ERP system. Process Automatic Generation . 1. If you want to create a VAS order for kit items in the delivery. SAP Extended Warehouse Management (SAP EWM) 510 356 .. to document and monitor these value-added services.. For more information. 4. and generates it where appropriate. EWM saves the number of the VAS order as a document flow for all kit items of the warehouse request. If you have activated the VAS Order status in the status profile of the item type for the warehouse request item. ○ Not Relevant If you have defined in Customizing that EWM is not to generate the VAS order automatically. 2. make the settings for the item type of the kit header only. You have defined a packaging specification [Seite 494] with a level of type Kitting. You create a VAS order for the kit header item manually (see also: Create and Edit VAS Orders [Seite 536]).

You can use this VAS order for confirming services in the process Kitting at a Work Center with a VAS Order [Seite 353]. All activities after the kitting activity (such as packing) have the kit header item as their item. For example. 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.2007 Result The system has created a VAS order for the kit header. When you edit the VAS order. 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. Kitting. you have defined a packaging specification with the levels Oiling. 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. ● SAP Extended Warehouse Management (SAP EWM) 510 357 . and Packing.SAP Online Help 20. This is based on the assumption that you perform all activities after assembling the kits in the kit itself.07.

5.07. You can then repack these items into other HUs in the work center. Here you can configure a work center where you also pack in such a way that you can confirm generated kits there. ○ If you have set the Create Kit Item indicator in Customizing and are working with pick-HUs. If you have not set the Create Kit Item indicator in Customizing. This process is suitable for the following cases: ● ● You do not require detailed documentation of the kitting procedure in EWM. display it in the packing transaction. the system generates the kit header item in the pick-HU. As free text that you have created in the warehouse request in EWM. Prerequisites You have made all the required settings for kitting in Customizing. You pack the kit into an HU and generate the HU item for the kit header. EWM receives an outbound delivery with kit component items from the ERP system. SAP Extended Warehouse Management (SAP EWM) 510 358 . You can display this text in the work center as additional information. You are not performing kitting in one special kitting work center. 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). 6.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). You generate warehouse tasks for the kit component items. see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Issue Process → Outbound Delivery → Define EWM-Specific Settings for Item Types. You can print out this HU item in an HU list. For more information. You assemble the kit in the packing work center. ○ 4. you can generate the kit header item in the work center manually. see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Issue Process → Make Settings for Kitting. The kit component items are then in the packing 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. 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. and confirm it to the ERP system. set the Create Kit Item indicator in Customizing. 2. Process 1. You generate an HU warehouse task to transport the HU to the goods issue zone.SAP Online Help 20. 3. If the system is to automatically generate an HU item for the kit header in the pick-HU. For more information. You pick the kit components into a pick-HU and confirm the warehouse tasks. An outbound delivery with kit items exists in EWM.

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 system uses this HU item in goods issue posting to check whether the packed kits are complete. SAP Extended Warehouse Management (SAP EWM) 510 359 .2007 If you have set the Create Kit Item indicator.. You then post the goods issue for the warehouse request. . The system only performs this check if the indicator is set in the item type of the kit header. 8.07.SAP Online Help 7. and therefore whether the system can post goods issue for these kits. you must generate the item manually after packing the kits in the work center at the latest. You confirm the HU warehouse task.. the ERP system is dependent on this item (see also: Kit to Order [Seite 349]). If the ERP system is dependent on an HU item for the confirmation. 20. Result You can ship the kit. and you have not set the Create Kit Item indicator in Customizing.

.. An outbound delivery with kit items exists in EWM. Prerequisites You have made all the required settings for kitting in Customizing. EWM receives an outbound delivery with kit component items from the ERP system.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. see the Implementation Guide (IMG) for Extended Warehouse Management under Goods Issue Process → Make Settings for Kitting. set the Create Kit Item indicator in Customizing. 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. display it in the packing transaction. If the ERP system is dependent on an HU item for the kit header in the confirmation of goods issue. For more information. You can display this text in the work center as additional information. 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). and confirm it to the ERP system. the ERP system is dependent on this item (see also: Kit to Order [Seite 349]). If the system is to automatically generate an HU item for the kit header in the pick-HU. You can print out this HU item in an HU list.SAP Online Help 20. 2. Process . you must make this setting. 4. This process is suitable for the following cases: ● ● You do not require detailed documentation of the kitting procedure in EWM. 1. You pick the kit components and assemble the kit. You assemble the kits during picking.. 3.07. You confirm the warehouse tasks. 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 generate warehouse tasks for the kit component items. where required in accordance with the kitting instruction. In EWM. you do not perform kitting at special work centers. 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 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. SAP Extended Warehouse Management (SAP EWM) 510 360 . that is.

You can then repack these items into other HUs in the work center. SAP Extended Warehouse Management (SAP EWM) 510 361 . the system generates the kit header item in the pick-HU. You then post the goods issue for the warehouse request. Results You can ship the kit. the system uses this HU item in goods issue posting to check whether the packed kits are complete.2007 If you have set the Create Kit Item indicator in Customizing and are working with pickHUs. The system only performs this check if the indicator is set in the item type of the kit header.SAP Online Help 20. 5. If you have set the Create Kit Item indicator. and therefore whether the system can post goods issue for these kits.07.

for example. see the Implementation Guide (IMG) for Extended Warehouse Management → Master Data → Work Center → Define Work Center Layout and Define Work Center. you specify which functions are executed at the relevant work center. you can pack products into handling units (HU). handling unit. For example. For packing. in Customizing and the SAP menu. storage bin. On the left side of the work center screen. In Customizing. there are various restriction options (filters) available for selection on the initial screen. you can make the following settings: ● Standard storage bin SAP Extended Warehouse Management (SAP EWM) 510 362 . For example. using scales connected to the system.SAP Online Help 20. or delivery.2007 Packing at the Work Center Use Using packing in the work center. The display for the different work centers is configurable. You can also transmit the exact weight to the SAP system. The system supports entries using the keyboard or a scanner (where the necessary information is available as a bar code). in Customizing you can decide which of the available tab pages should be displayed for the user in the relevant work center. in the SAP menu you need to specify which storage bin is assigned to a work center. for example. or to pack products into other handling units. 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. you can use simple Drag&Drop to repack entire handling units. For more information.07. which enable each user to optimize their worklist. The upper right screen area consists of tab pages that you can mainly use without a mouse. and handling units into other handling units. In the Control area. This transaction is particularly aimed at those users who physically pack products at work centers in the warehouse. Prerequisites Ensure that you have made the required settings for packing in the work center. or you can print handling unit documents.

● Storage Bin ○ ○ ● Storage bin product (if unpacked products are present in the storage bin) Storage bin information (warehouse number. you can edit or request the following detailed information for the individual objects. assignment to deliveries. The left screen area groups the display according to the following objects: ● ● ● ● ● Storage section (displayed as Storage bin (displayed as symbol) symbol) or . In the right screen area. storage type) Handling unit ○ ○ ○ ○ ○ ○ ○ Capacity (weight. you can request various detailed information about the individual entries. alternative HU identification) Contents (list of the packed products and additional packaging materials contained in the HU) Possible destination HUs (for example.07. 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) .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. deconsolidation group. and for quick repacking of handling units and products (only using the mouse).SAP Online Help ● ● ● ● 20. section. and dimensions) Detail data 1 (internal warehouse data. such as warehouse process and process step. You use the left screen area mainly for navigation. 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. and so on) Detail data 2 (status. volume.

. you also have the option of calling up the various work centers separately in the menu. if you have not assigned a work center to your terminal.2007 Warehouse Task ○ Possible destination HUs Note that you edit and/or assign additional packaging materials in the Product area.General b. and use the input help to select the work center you require.. 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. From the SAP menu. SAP Extended Warehouse Management (SAP EWM) 510 364 . a.07. . Enter the relevant warehouse number. depending on the work center.. choose Extended Warehouse Management → Execution → Quality Inspection and Count c. From the SAP menu. From the SAP menu. 1. choose Extended Warehouse Management → Execution → Deconsolidation in Goods Receipt 2.. choose Extended Warehouse Management → Execution → Packing . The corresponding input help is then restricted. see the IMG under Define Work Center. choose one of the following menu paths: . to the data you have configured in Customizing. Functions for Objects In addition. To access the various types of work center.SAP Online Help o ● Quality inspections 20. For more information.

and assign your terminal to the work center. If you want to repack just one partial quantity of a product.07. select an HU and drag it into another HU. Then use drag and drop to drag this cell to the target area (destination HU or destination storage bin). select the product and drag it to the storage bin. so that during packing. If you want to pack an HU in another HU. b. To do this. or pack HUs in other HUs as follows: ● ● ● If you want to repack products in other HUs. double click a higher-level node (HU or storage bin) in the area on the left. 3. a. Packing Using Drag and Drop In the area on the left.. 4. 2. Packing Partial Quantities Using Drag and Drop . You can also assign any scales that are connected to your work center. select the product and drag it into another HU. To do this. SAP Extended Warehouse Management (SAP EWM) 510 365 . from the SAP menu choose Extended Warehouse Management → Master Data → Work Center → Define Master Data Attributes.. Enter the quantity that you want to repack in the Partial Quantity field and choose Enter.SAP Online Help 20. the system automatically fills in the correct warehouse number and your work center. All the product items of the HU or storage bin are now visible. you can pack or unpack products in HUs.2007 You can assign a work center to your terminal in the system. If you want to unpack products from other HUs. Choose the tab page Contents in the area on the lower right. click any cell in this row that is not ready for input. 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. 1.

. For more information.. ● You have defined the work center for scrapping.. ● You have defined the stock removal strategies for determining the stock to be scrapped. 1. Prerequisites . see the Implementation Guide (IMG) for Extended Warehouse Managements under Goods Receipt Process → Strategies. ● You have defined the warehouse process types for scrapping. For the entire quantity of a product b. see the Implementation Guide (IMG) for Extended Warehouse Managements under Master Data → Work Center. You can use this process to create posting change notices for scrapping. for example. where you can pack the products to be scrapped together into a collection container. or that are unusable for some other reason.. a. and can remove these products from stock and post goods issue as usual.. For more information. see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings → Warehouse Task → Define Warehouse Process Type.2007 Scrapping Purpose In your warehouse you sometimes find products that are damaged.SAP Online Help 20. 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.07. For the entire quantity of a product except for a fixed remaining quantity SAP Extended Warehouse Management (SAP EWM) 510 366 . you have to scrap them. . 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. ● You have defined the following different document types for the posting change process. during picking or physical inventory. You often notice this. Since you cannot normally sell these products on. For more information. 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. Process . in which you enter the work center for scrapping as the destination storage bin.. ● You have defined a non-picking-relevant document type and item type for the outbound delivery of the scrapping container. Create the posting change notice for scrapping. For more information.

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.2007 c. Create a warehouse task for scrapping with reference to the posting change notice 3. and to construct handling units.07. 5. You use the packing transaction to pack the products to scrap. 6.SAP Online Help 20. You pick these products and confirm the warehouse tasks to the work center for scrapping. Remove the products to scrap from stock. For a partial quantity of a product (unsaleable or damaged products in the warehouse) 2. 4. Use the handling units to create a non-picking-relevant outbound delivery. You can use a stock removal strategy to determine the stock to be scrapped. SAP Extended Warehouse Management (SAP EWM) 510 367 . 7. Post the goods issue for the outbound delivery.

The following applies for invoice creation: ● ● ● In the case of direct outbound delivery orders. In the case of CRM orders. the invoice is always created through CRM billing. CRM billing or ERP billing creates the invoice after goods issue.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. Prerequisites ● If you are using CRM billing.07. such as the GTS geography group at header level. You can override this indicator in the sales order. to determine whether a delivery must be checked by the customs authority. You have defined specific characteristics in the route. such as for international transportation. see the SAP Library under SAP CRM → Components and Functions → Sales → Sales Transaction → Sales Orders → Additional Functions for Service Parts Management. you have performed the following: ● ● If you are using CRM billing. ● Integration To be able to create and print invoices. In the standard system. ● If you are using ERP billing. EWM triggers the creation and invoice printing automatically when it generates an outbound delivery. the invoice is always created through ERP billing. you have connected an ERP system. For more information. 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. if you require the invoice printout before the end of the loading and transportation process.SAP Online Help 20. On the SAP Easy Access screen. If you want to create one invoice for each delivery. You do this by sending an invoice request from Extended Warehouse Management (EWM) to CRM billing or ERP billing. EWM triggers the invoice printout in CRM billing or ERP billing by sending the message Print Billing Document. In the case of ERP orders. If you are using ERP billing. ● If you want to print invoices for the contents of a vehicle or transportation unit. EWM sends the invoice-relevant data to ERP. However. you can create the current invoice before goods issue posting. the invoice is always created through ERP billing. you have set the IBGI (Invoicing Before Goods Issue) indicator in the data relevant to the business partner. you have connected an ERP and an SAP CRM system. choose Extended Warehouse ● SAP Extended Warehouse Management (SAP EWM) 510 368 . You can request an invoice for each delivery or one or more invoices for the contents of a vehicle or transportation unit. ERP copies the data to CRM billing or ERP billing.

If. For example. CRM billing or ERP billing directly creates single invoices that you cannot change. If you then generate a new outbound delivery. you use item type ODLV Standard Item Outbound Delivery with process profile /SCWM/OUT_PRD_DLV Outbound Delivery Order Standard Item. In the SAP Easy Access screen. choose Extended Warehouse Management → Interfaces → Invoice Before Goods Issue.SAP Online Help 20. you are using document type OUTB Outbound Delivery Order with process profile /SCWM/OUT_PRD Outbound Delivery Order Standard for the delivery header. the invoice is automatically created and printed again. For example. For more information. and process profile /SCWM/OUT_PRD_DLV Outbound Delivery Order Standard Item EWM for the delivery item. choose Extended Warehouse Management → Interfaces → Invoice Before Goods Issue. For more information. Features For single requests from EWM. EWM requests at least 50 invoices from CRM billing. for example. or manually on the user interface for 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. For more information about the individual process indicators. For changes. In the SAP Easy Access screen. ● 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. 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. 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. ○ You have defined a process profile for the item types of the outbound delivery that allows invoicing before goods issue.07. ● If you do not use routes in the outbound delivery. 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. 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 to delete the outbound delivery. SAP Extended Warehouse Management (SAP EWM) 510 369 . a vehicle is carrying a delivery of 50 different regulators. This automatically cancels the invoice. ● In Customizing for EWM.2007 Management → Master Data → Shipping and Receiving→ Transportation → Route Determination → Maintain Route. see IMG for EWM under Goods Issue Process → Outbound Delivery → Manual Settings → Define Document Types for Outbound Delivery Process.

2007 For group requests from EWM.SAP Online Help 20. You can determine a print profile after CRM billing or ERP billing has selected the printer [Seite 372]. EWM sends the cancellation for the invoice that was created to CRM billing or ERP billing. print or cancel an invoice for a group request. You can make changes to these deliveries in EWM. CRM billing creates corresponding billing due list items. After you have posted the goods issue. CRM billing or ERP billing creates one or more invoices for each vehicle or transportation unit. you can only trigger the invoice printout from CRM billing or ERP billing. Invoice Cancellation You cannot change an invoice once it has been created. SAP CRM determines whether EWM sends an invoice request for a delivery before the goods issue posting to CRM billing via ERP. ERP or SAP CRM updates its deliveries or the invoice-relevant data in accordance with the input from EWM. 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. on the SAP Easy Access screen. the billing system uses the print profile found. you can configure for the sales document type and sales organization the indicator with which the document items are sent to EWM. You must determine the same print profile in CRM billing or ERP billing and EWM. you can create related outbound deliveries for each vehicle and request invoices for them. the billing system uses the profile of the first delivery that was found. If the IBGI indicator on the delivery item allows invoice before goods issue depending on the route. ERP billing does not create any billing due list items.07. If more than one vehicle forwards the material for a sales order. If these occur before invoice creation. You can then request invoice creation and invoice printing again for the changed shipment document or delivery. Invoice Relevance With your settings at sales order level or delivery level. choose Extended Warehouse Management → Shipping and Receiving → Process Vehicle or Process Transportation Unit. SAP Extended Warehouse Management (SAP EWM) 510 370 . due to the business partner status Invoice Creation Before Goods Issue Posting Allowed. If you are not using a vehicle or transportation unit in the outbound delivery. In ERP. you have loaded a handling unit on to a different transportation unit and want to change the invoice that has already been created. For the printing of group requests. you can control the global relevance for invoice creation before goods issue at delivery item level. You can override this setting in the sales order of SAP CRM. Activities Among other things. ERP uses the Customizing entries to determine whether the outbound delivery is relevant for the Invoice Before Goods Issue process. 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. so that CRM billing or ERP billing can print invoices. EWM finds the print profile and informs CRM billing or ERP billing accordingly. If. for example. For printing single requests. you have to perform an invoice cancellation.

2007 Cancel Invoice EWM sends the message Cancel Invoice to SAP CRM or ERP.07. Get Status The system requests and displays the status of the invoice creation for the ERP delivery. Print Invoice EWM sends the message Print Invoice to SAP CRM or ERP. SAP Extended Warehouse Management (SAP EWM) 510 371 .SAP Online Help ● ● ● 20.

If EWM cannot determine a print profile. or invoices. and warehouse number. you have defined a print profile in the default values. Here. for example. If appropriate. EWM uses the name of this print profile. 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. 3. Prerequisites ● If appropriate. ● You have defined print profile determination for the goods receipt process or goods issue process in Customizing for EWM.. For more information. for example.07. irrespective of whether you print from ERP or from SAP Customer Relationship Management (SAP CRM). every goods issue area can have multiple printers for various document types. EWM always sends the print profile names for invoice printouts to ERP. it uses the name of this print profile. Choose Default Values and enter a print profile. see the BAdI documentation.SAP Online Help 20. 1. it checks whether you have implemented your own print profile determination in BAdI /SCWM/EX_DLV_PRINT_PROFILE. 2. If EWM cannot find a print profile in step 1. As a result. If so. To do so. you have defined one or more print profiles in Customizing for EWM. If EWM cannot find a print profile in step 2. on the SAP Easy Access screen.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). For more information. choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Pickup. it does not send a print profile name to ERP. goods receipt office. 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. You can define an access sequence for print profile determination. ● ● Process EWM attempts to determine the print profile in the following sequence: . for freight lists. If EWM requests a single print from CRM billing. For more information. ship-to location. you have implemented your own print profile determination in Business Add-In (BAdI) /SCWM/EX_DLV_PRINT_PROFILE. 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 considers one or more combinations of different parameters for the print profile. bills of lading. SAP Extended Warehouse Management (SAP EWM) 510 372 . CRM billing uses the print profile that EWM sends. EWM uses the name of this print profile.. EWM checks whether you have specified a print profile in the default values on the user interface for pickup. EWM determines this print profile in the sequence described above.

2007 If EWM requests a grouped print for multiple deliveries from CRM billing. This is because EWM only sends the print profile name to ERP and not the printer name. For information about invoice relevance. see Invoice Creation Before Goods Issue [Seite 368].SAP Online Help 20.07. you must ensure that EWM determines the printer for delivery note printing using a print profile (see Printer Determination in Delivery Processing [Seite 141]). See also: Printing Delivery Notes [Seite 143] SAP Extended Warehouse Management (SAP EWM) 510 373 . If you want to synchronize invoice printing with delivery note printing. EWM always sends the first print profile that is found by delivery processing. the invoice printout. and invoice cancellation.

If you decide to manually process certain goods movements. for example. ● Goods Issues The system uses stock removal strategies to determine the optimal picking bin. Each time that a warehouse task (WT) is created. for rearrangement [Seite 287].2007 Putaway and Stock Removal Strategies Use In Extended Warehouse Management (EWM). ● 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. posting changes. the system reverts to putaway and stock removal strategies. ● Internal stock transfers The system uses putaway and stock removal strategies. 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. and replenishment control [Seite 346].07. the system uses putaway strategies [Seite 375] and stock removal strategies [Seite 396] to determine storage bins and stock. For more information.SAP Online Help 20. 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 . you can change source and destination storage bins that are automatically proposed by the system.

The system searches in the general storage area. The system determines the storage bin on the basis of the handling unit type.SAP Online Help 20. The system searches for a storage bin that already contains stock. you use putaway strategies [Extern] to optimize the storage of products. For more information. 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. The system searches for an empty storage bin.2007 Putaway Strategies Use In Extended Warehouse Management (EWM). see the Implementation Guide (IMG) and the documentation for the individual strategies. Prerequisites You make the settings for the putaway strategies in Customizing for Extended Warehouse Management (EWM) under Goods Receipt Process → Strategies. The system searches for a fixed storage bin. 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. See Also: Storage Bin Determination for Putaway [Seite 291] SAP Extended Warehouse Management (SAP EWM) 510 375 . 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 searches for a storage bin in the bulk storage area.07.

SAP Extended Warehouse Management (SAP EWM) 510 376 .2007 Manual Entry Use The system does not determine a storage section or a storage bin. We recommend that you manually enter the storage bin in the case of mixed storage and storage types with the role “Staging Area Group”. Then the system automatically determines the data using the storage bin (for example. You have chosen the Empty Bin or Addition to Existing Stock/Empty Bin value in the Putaway Rules field. First the warehouse worker searches for the suitable storage bin. You have chosen the Only Storage Type value in the WT Generic field. 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 use this procedure if the search for a suitable storage bin is performed on-site by the warehouse worker. the storage type) in the warehouse task. You enter the destination storage bin manually when the warehouse task is created.07.SAP Online Help 20.

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. Fixed Bins field (you can also make this setting in the product master). AA B-B FIX-AA FIX-1-BB FIX-2-BB FIX-1-DD FIX-2-DD Warehouse No.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 assign fixed storage bins manually. FIX-BB. You have chosen the Addition to Existing Stock/Empty Bin value in the Putaway Rules field. You have defined a maximum number of fixed storage bins in the Max. You have chosen the Addition to existing stock permitted value in the Addn. 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”. In this example. Multiple fixed storage bins can be available for a product. for example. FIX-1-BB and FIX-2-BB for product BB. You use this strategy primarily in storage types from which picking is done manually. The following figure is an example of a fixed bin assignment. and FIX-DD.Stock Forbidden field. warehouse 0001 has several fixed storage bins: FIX-AA. the system determines a suitable storage bin and assigns it to the product as a fixed storage bin. SAP Extended Warehouse Management (SAP EWM) 510 377 . 0001 Party Ent. You have set the Fixed Bins Allowed indicator. 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. to Disp.SAP Online Help 20.07.

SAP Online Help ○ 20.2007 You have chosen a method in the Capacity Check field to activate the capacity check. SAP Extended Warehouse Management (SAP EWM) 510 378 .07.

The quants in the storage bin can also be in the form of mixed storage. You have chosen the General Storage Area value in the Putaway Rules field. you can define one or more general storage areas. 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. The following figure illustrates general storage.07. SAP Extended Warehouse Management (SAP EWM) 510 379 .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. For each storage type. You have chosen the Mixed Storage Without Limitations value in the Mixed Storage field.SAP Online Help 20. 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.

to Exist. you can add the product to the existing stock. A prerequisite for addition to existing stock is that sufficient free capacity still exists in the relevant storage bin. The following figure shows an example of addition to existing stock. If you want to allow additions to existing stock. SAP Extended Warehouse Management (SAP EWM) 510 380 . Since AA is already occupying a storage bin and free capacity is still available.2007 Strategy: Addition to Existing Stock Use With this strategy.Stock Forbidden field whether or not you want to allow additions to existing stock. you must choose the required value for the Addit. 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 specified in the Addn. This strategy violates the FIFO principle.07. the system searches for the next empty storage bin. you should only use this strategy in situations where you have insufficient space. choose “ ” (Addition to existing stock permitted) or “M” (Addition to existing stock via addtn ID in product master). You have chosen the value 3 in the Mixed Storage field (one HU allowed per bin.SAP Online Help 20. 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. ● ● You have chosen a method in the Capacity Check field to activate the capacity check. the system prefers to put away stock in storage bins that already contain stock of the relevant product. If you choose “M”. mixed storage is not permitted).Stock indicator in the product master. in other words. For this reason. You have chosen the Addition to Existing Stock/Empty Bin value in the Putaway Rules field. You want to put away product AA.

SAP Online Help 20. where products are stored in individual storage sections. 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. This strategy is especially suited for high rack storage and shelf storage.07. Optionally. You can use this strategy to support warehouses that are organized randomly. 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. SAP Extended Warehouse Management (SAP EWM) 510 381 . the system proposes an empty storage bin.2007 Strategy: Empty Storage Bin Use With this strategy.

You have chosen the Empty Bin value in the Putaway Rules field. If it does not find an empty bin. If it does not find an empty bin.SAP Online Help 20. SAP Extended Warehouse Management (SAP EWM) 510 382 . Here the system starts on the lowest level and works its way up. 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). If multiple fixed storage bins are available for the product in the picking storage type. Here it always searches from the bottom upwards.07. it searches to the right of the fixed storage bin and then to the left in the same aisle. You have chosen the Near to Fixed Bin value in the SrchRule EmptyBin field. 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. You can set up your system in such a way that it first searches for a fixed storage bin in a picking storage type. The system first tries to find a reserve storage bin in the stack where the fixed storage bin is located.2007 Strategy: Near Fixed Picking Bin Use You use this strategy when you put away products in a reserve storage area. You have given the storage bins in the picking storage type and the reserve storage type the same names. before searching in the adjoining aisles. 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 can configure whether the system checks if a fixed storage bin is available.

2007 Strategy: Pallet Storage (by HU Type) Use Using this putaway strategy. For example. you define the maximum number of quants for each combination of storage bin type and HU type. Explanation of the Strategy High rack storage is frequently designed so that a storage bin can accommodate several different HU types. A storage bin may be able to accommodate a single oversized pallet or several very narrow pallets. The system also determines which and how many HUs it can put away in the storage bins. You have activated the HU type check. a storage bin can accommodate multiple pallets depending on the size of the pallet. 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. One storage bin is often divided into several smaller sections. it determines the storage bin sectioning that it assigns to the storage bin.07. The following figure shows the “Pallet Storage by HU Type” strategy.SAP Online Help 20. 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. The first time that the system puts away products in this storage bin. You have chosen the Mixed Storage Without Limitations value in the Mixed Storage field. the system processes different HU types (for example. SAP Extended Warehouse Management (SAP EWM) 510 383 . You have chosen the Empty Bin value in the Putaway Rules field. You can only put away the same HU types in a storage bin. pallets) and allocates them to a suitable storage bin section. such as three europallets (80 x 120) or two industrial pallets (100 x 120).

The system displays the total number of storage bin sections that you have defined in the Number of Sections field. 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). Note that the name of the storage bin sections is 2-3 digits longer than that of the main storage bins.SAP Online Help 20..2007 Definition of Storage Bin Sections The following table shows the number of storage bin sections that you can define for a storage bin. Bin Functional 1 Secs Location Category 0007 A 0007 B 2 3 BT01 BT01 A 1 2 3 4 5 6 . The system deletes the storage bin sectioning as soon as you have removed the last HU from the storage bin. Therefore. BB. 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. 12) in one of the columns numbered from 1 to 99 under the heading Sections. Assign Storage Bin Types and HU Types WNr 0001 0001 Type 0007 0007 BinTy PA PA HU Type E1 IP SecKey B A No. This means that you use this number to control the number of HUs that can occupy a storage bin.. 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.07. you enter either a one-digit or a two-digit suffix (for example. Assuming that the storage bin is named 02-10-01. A1. Assignment of Storage Bins and HU Types For each storage type. (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. Bin Secs 3 2 SAP Extended Warehouse Management (SAP EWM) 510 384 . you cannot change them. The system attaches this suffix to the name of the storage bin and separates it with a slash (/). Define Storage Bin Sections WNr Type SecKey No. Nomenclature of Storage Bin Sections To name each individual section of a storage bin. 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..

07. Bin Secs 3 2 2 If you define the table as shown above.SAP Online Help 20. the system ensures that you put away only one HU type per storage bin. you cannot change them later. you must enter the HU type in the preparation screen of the warehouse task. 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. Additional Option If you assign the same storage bin type and a different HU type to the same section key. The system uses this HU type to search for suitable empty storage bins. When you put away products into a storage type for which storage bin sectioning has been defined. SAP Extended Warehouse Management (SAP EWM) 510 385 . you must specify a storage bin type. 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.2007 When you create storage bins for this strategy. Once you have made these assignments. This storage bin type must match the storage bin type in the table for assigning storage bin types and HU types (see above). At the same time. you can also put away more than one pallet type into the same storage bin.

only storage bins of the type P0 are available in this storage type. ■ ■ You can easily check the Customizing settings by viewing the log for the storage bin search. P2. you should check the table parameters carefully.SAP Online Help 20. The system is not allowed to put away HU type E1 in storage type 0001. The following example outlines the performance problems associated with the optional HU type check and their solutions: ■ Storage bin types P1. This entry means that all the HU types in this storage type are allowed. Before you activate the optional HU type check. SAP Extended Warehouse Management (SAP EWM) 510 386 . However. The system is to put away HU type E1 in storage type 0001. the system tries to access the database five times without success. The greater the number of unsuccessful attempts that the system has made. P3. You should reduce the number of attempts by optimizing the storage type search. You can enter *** as an allowed HU type in this table. you may encounter performance problems. 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.07. If you work with different storage sections. If the configuration settings are not optimal. 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. and P5 are allowed for HU type E1.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. this number increases accordingly. In the optional HU type check. P4. the more ineffective the process for storage bin determination becomes.

for example. You can enter this exception (reduced capacity of a row) when defining the block structure (see section “Prerequisites”). ● Mixed storage SAP Extended Warehouse Management (SAP EWM) 510 387 . you often manage different HU types with different dimensions. due to a structural column in the row. 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. Extended Warehouse Management (EWM) supports the management of different HU types in bulk storage. The storage bins (rows) are classified according to storage bin types. you do not have to take any technical prerequisites of the system into account.07. glass products. The warehouse is divided into blocks. a row is selected as the sort characteristic in bulk storage. which in turn are divided into individual rows. rows 2 and 3 in block A05 (illustrated in the above figure) can hold up to 16 pallets.2007 Strategy: Bulk Storage Use Products such as tires. 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. and drinks that come in large quantities and require a large amount of storage space are often stored in bulk storage. ● Different HU types In bulk storage. For example. a row is created and managed as a storage bin. standard pallets and industrial pallets with clip-on mounts. In the system.SAP Online Help 20. ● One storage bin per row In practice. However the 4th row can only hold a maximum of 12 pallets.

see the Implementation Guide (IMG) for EWM under Goods Receipt Process → Strategies → Putaway Rules → Putaway Behavior: Bulk Storage → Storage Type Control for Bulk Storage. You can also define that all products in the storage bin must have the same batch. When you define storage bins for bulk storage you must enter a storage bin type. in general. You have chosen the Addition to existing stock permitted value in the Addn.SAP Online Help 20. Do not activate the HU type check and do not choose a capacity check method.2007 You do not put away HUs with different products in the same row. 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. Definition of Bulk Storage Indicators For this strategy. ○ ● When defining the storage type control for this strategy. all combinations of mixed storage are allowed in bulk storage. 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. and stacking height. For more information about the permitted combinations. among others. you define how you want to store a particular product in bulk storage. Using the bulk storage indicator. to control the putaway of products into bulk storage: ○ ○ Putaway blocking for row Time limit for blocking For more information about these control options. To do this. see the relevant field help. you can set a blocking indicator for each row separately. Other Control Options In the product master record (in the Warehouse Management view). you must take into consideration the following indicators. You have chosen the Addition to Existing Stock/Empty Bin value in the Putaway Rules field. 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. However. ● Automatic blocking per row To optimize the putaway and stock removal processes in bulk storage.07. you can enter bulk storage indicators together with a description. maximum number of stacks.Stock Forbidden field. HU types. 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 . Block Structure Definition You can define various characteristics of bulk storage such as storage bin types. Choose the required option in the Mixed Storage field.

2007 SAP Extended Warehouse Management (SAP EWM) 510 389 .07.SAP Online Help 20.

SAP Online Help 20. b. The system gives the generated activity area the same name as the storage type. 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. To do so. it must contain the same storage bins. If you have not defined a sort sequence. The activity area must match the storage type. in other words. 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. you have performed the following steps: a. SAP Extended Warehouse Management (SAP EWM) 510 390 . the system sorts by storage bin name. c. You can use sort sequences to prevent one part of the warehouse from being overburdened and to optimize the putaway of goods. a sort sequence supports the system when searching for suitable storage bins. You have defined a sort sequence for cross-line stock putaway under Master Data → Activity Areas → Define Sort Sequence for Cross-Line Stock Putaway.2007 Cross-Line Stock Putaway Use In the case of this function.07. 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. ● You have created a storage bin sorting on the SAP Easy Access screen under Extended Warehouse Management → Master Data → Storage Bin → Sort Storage Bins. Prerequisites ● You have defined a sort sequence for cross-line stock putaways in Customizing for Extended Warehouse Management (EWM). 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. it uses sort sequences to search for a storage bin.

choose Extended Warehouse Management → Master Data → Storage Bin → Create Storage Bin (Stor. you have defined the following: ○ You have defined the weight or volume consumption for each storage bin. By default. Bin tab page. choose Extended Warehouse Management → Master Data → Product → Maintain Warehouse Product (Units of Meas. choose Extended Warehouse Management → Master Data → Product → Maintain Warehouse Product (Units of Meas. on the SAP Easy Access screen. it is useful to perform a capacity check for the storage bin when searching for a suitable storage bin. tab page. To do so. To do so. Capacity Check field). Weight Usage or Volume Usage field). choose Extended Warehouse Management → Master Data → Storage Bin → Create Storage Bin (Stor. You have defined a capacity consumption per unit of measure for each product in the product master.07.2007 Capacity Check Use In the case of some putaway strategies. the system checks whether the selected storage bin can accept the quantity to be put away when it creates a warehouse task (WT). To do so. tab page). on the SAP Easy Access screen. You have defined a capacity consumption per unit of measure for each packaging material in the product master. SAP Extended Warehouse Management (SAP EWM) 510 391 .SAP Online Help 20. Prerequisites ● You can set up the capacity check in Customizing for Extended Warehouse Management (EWM) under Master Data → Define Storage Type (Putaway Control. You have defined a weight or volume consumption per unit of measure for each product in the product master. ● ○ ● To control the capacity check in accordance with the capacity key figure. ● Volume The system checks the volume of the product to be put away against the available volume of the storage bin. To do so. on the SAP Easy Access screen. ○ ○ 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. choose Extended Warehouse Management → Master Data → Product → Maintain Warehouse Product (Units of Meas. Capacity Usage field). the checks are predefined in accordance with weight and volume. on the SAP Easy Access screen. tab page). If you have activated the capacity check. To control the capacity check in accordance with weight or volume. To do so. Capacity Consumption field). on the SAP Easy Access screen. Bin tab page. you have defined the following: ○ You have defined a capacity that is independent of a dimension or a unit for each storage bin.

and updated in the quant. 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. ● Capacity check in accordance with product and HU In the case of mixed storage. 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. You can also apply this capacity check if different batches of the product exist that result in mixed storage.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. SAP Extended Warehouse Management (SAP EWM) 510 392 . the capacity check is performed via the block definition. The capacity consumption of an HU is specified as a constant capacity consumption. Here the system calculates the capacity consumption in different ways. In bulk storage. we recommend the capacity check in accordance with the product and HU.07. 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). the system calculates the capacity consumption on the basis of the HU. ● Capacity check in accordance with HU In the case of HU checks. we recommend a capacity check. and is updated in the HU.SAP Online Help ● 20. ○ 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.

You must not make such changes when the system is running in productive mode since they result in inconsistencies.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. SAP Extended Warehouse Management (SAP EWM) 510 393 . see Examples of Capacity Check in Accordance with Capacity Key Figure [Seite 394]. 20.SAP Online Help Quant and HU data is updated for each storage bin as remaining capacity.07. For more information about the capacity check in accordance with the capacity key figure. and quants. HUs.

Each wire basket has a capacity consumption of 12. you find an example of each of the three types of capacity check in accordance with the capacity key figure. 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. 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 .2007 Examples of Capacity Check in Accordance with Capacity Key Figure In the following section. This means that you can put away nine pieces of product 4711 in this storage bin. Here you have a remaining capacity of one. Here you have a remaining capacity of four.SAP Online Help 20.07. This means that you can put away eight wire baskets in the storage bin. Each piece of product 4711 has a capacity consumption of 11. Capacity check in accordance with product The storage bin 01-01-01 has a total capacity of 100.

for example Remaining Capacity = 0 SAP Extended Warehouse Management (SAP EWM) 510 395 . 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.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.07.SAP Online Help 20.

The system searches for products with the shortest remaining time before the expiration date. The system first searches for partial quantities and then for standard quantities. See Also: Storage Bin Determination for Stock Removal [Seite 343] SAP Extended Warehouse Management (SAP EWM) 510 396 .2007 Stock Removal Strategies Use You use stock removal strategies [Extern] to define where the system is to search for stock. Features The following table shows possible stock removal strategies: Strategy FIFO (First In. With LIFO.07. First Out) [Seite 397] Stringent FIFO for All Storage Types [Seite 398] LIFO (Last In. the system searches for the most recent quant. 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. 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. see the Implementation Guide (IMG) and the documentation for the individual strategies. 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. With stringent FIFO. in other words. the system searches for the oldest quant. For more information. and how it is to sort the stock that has been determined. the system searches across all storage types. in which storage types.SAP Online Help 20. The system determines the storage bin on the basis of the quantity.

Regardless of whether you adopt the goods receipt date or enter a new one. You can accept the goods receipt date that the system sets or you can enter a different date. 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. the system uses this date to calculate the age of the quant.SAP Online Help 20. You have assigned the stock removal rule to the storage type in Customizing for EWM under Master Data → Define Storage Type. Alternatively. You have defined a storage type search sequence in Customizing for EWM under Goods Issue Process → Strategies → Specify Storage Type Search Sequence. you can assign the stock removal rule under Goods Issue Process → Strategies → Determine Storage Type Search Sequence for Stock Removal. This date influences the sort sequence for each product.07. You have specified the goods receipt date (sort ascending) as the sort criterion. Prerequisites ● You have defined a stock removal rule in Customizing for Extended Warehouse Management (EWM) under Goods Issue Process → Strategies → Specify Stock Removal Rule.2007 Strategy: FIFO (First In. The system calculates the age of a quant (its retention period in the warehouse) from the date when goods receipt was posted. First Out) Use In the case of this strategy. ● ● ● SAP Extended Warehouse Management (SAP EWM) 510 397 . the system first proposes the oldest quant from the storage type from which you want to remove products from stock. The goods receipt date is set automatically in the quant and in the warehouse request for each goods receipt posting.

you can remove stock according to the FIFO principle where you take into consideration all quants within a warehouse number. Prerequisites See Strategy: FIFO (First In. SAP Extended Warehouse Management (SAP EWM) 510 398 . In this case.2007 Strategy: Stringent FIFO Across All Storage Types Use In Extended Warehouse Management (EWM). 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.SAP Online Help 20. 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.07.

it always suggests the last quant that was placed into stock. Prerequisites See Strategy: FIFO (First In. 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. For example. First Out) Use For some warehouse organizations or sectors of industry. When using the FIFO strategy. you cannot use the FIFO principle. SAP Extended Warehouse Management (SAP EWM) 510 399 . First Out) [Seite 397] with the exception that you have specified the goods receipt date (sort descending) as the sort criterion. in the building material industry.SAP Online Help 20.07.2007 Strategy: LIFO (Last In. The LIFO strategy is provided for such situations. When the system searches for a suitable quant to remove from stock. the warehouse worker would first have to remove the products lying on top to get to the product with the oldest goods receipt date.

You have defined a packaging specification for the product in Customizing for SCM Basis under Packing → Packaging Specification. it proceeds as follows: 1.2007 Strategy: Partial Quantities First Use With this strategy. 2. It keeps the number of partial handling units (partial HUs) in one storage type as low as possible. It takes place in the form of partial pallet quantities (quantities smaller than a standard HU). 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.SAP Online Help 20. the system overrides the FIFO principle to optimize the management of stock in the warehouse. the system takes partial pallet quantities. 3. 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. 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. Quants that are larger than a standard HU should not occur. If no standard HUs exist.. 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. If no partial pallet quantities exist. the system breaks into complete HUs. If the required quantity in the warehouse task is the same as or greater than the quantity of a standard HU. ● ● SAP Extended Warehouse Management (SAP EWM) 510 400 . 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).07. . the system attempts to remove a standard HU from stock.. This is known as a partial pallet quantity. When the system searches for a quant. 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.

since a complete HU is not required. in other words.2007 Example You use two packaging specification levels. in other words. pallet and piece. the system sorts the stock in a descending order. and you have defined a quantity classification and a stock removal rule for each of them. it removes a full pallet from stock. the system searches for a partial HU. If the quantity required is greater than or equal to the quantity of the complete HU. If the required quantity is smaller than a complete HU. the system sorts the stock in an ascending order.07. The system uses the stock removal rule for piece to sort the stock by quantity in an ascending order. SAP Extended Warehouse Management (SAP EWM) 510 401 .SAP Online Help 20. The system uses the stock removal rule for pallet to sort the stock by quantity in an descending order.

If the required quantity is greater than the quantity of the standard HU in accordance with the packaging specification. For example. 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. depending on the quantity required in the warehouse task. Prerequisites See Strategy: Partial Quantities First [Seite 400] with the exception that you have defined and assigned two storage type search sequences.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. the system searches for the quant in high rack storage. 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. 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. You also have a reserve storage area where you store larger quantities. 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). SAP Extended Warehouse Management (SAP EWM) 510 402 .SAP Online Help 20. if the required quantity is less than or equal to the quantity of the standard HU in accordance with the packaging specification. The system decides whether it is dealing with a small quantity or a large quantity.07. The system uses the quantity of the standard HU in accordance with the packaging specification as the criterion.

Prerequisites See FIFO (First In.SAP Online Help 20.2007 Strategy: Shelf Life Expiration Date Use With this strategy. 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 .07. the system ensures that the products with the oldest shelf life expiration date are removed from stock first.

you have set the Negative Stock indicator if you want to permit negative available stock. the system also takes into consideration the storage bins that do not contain any stock when determining the stock. ● ● ● ● SAP Extended Warehouse Management (SAP EWM) 510 404 .07. 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. it is possible that the system creates warehouse tasks (WTs) for which no stock exists.SAP Online Help 20. 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. optionally. You have set the Fixed Bins Allowed indicator in Customizing for EWM under Master Data → Define Storage Type. Prerequisites ● You have defined a stock removal rule and. If you have allowed fixed storage bin assignments for a storage type.2007 Strategy: Fixed Storage Bin Use In the case of this strategy. You use replenishment control to ensure that products are available in the storage bin at the time of picking. In this way. the system uses the storage bin that was entered in the product master to find stock. To clear the pick items or the pick quantity per storage bin. 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 fixed storage bins in the master data for EWM under Storage Bin → Maintain Fixed Storage Bin. Negative available stock is allowed with this strategy. You have defined a storage type search sequence in Customizing for EWM under Goods Issue Process → Strategies → Specify Storage Type Search Sequence.

07. You can identify the type of the warehouse task from the warehouse process type in the warehouse task. for deconsolidation [Seite 298] and handling unit warehouse tasks. for unloading [Seite 608]. 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. you can also perform a physical inventory at the same time [Seite 670]. Here.2007 Warehouse Task Definition Document that uses Extended Warehouse Management (EWM) to execute goods movements.SAP Online Help 20. see Pick Point [Seite 410]. Logical or physical goods movements or even stock changes can be the basis for a warehouse task. When you confirm a warehouse task. EWM can work with the low-stock physical inventory. for example. EWM also submits hazardous substance texts [Seite 969] in the warehouse task. for example for internal goods movements. SAP Extended Warehouse Management (SAP EWM) 510 405 . For more information about the simultaneous use of product warehouse tasks and handling unit warehouse tasks. for example. 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.

Once confirmed. A product warehouse task (product WT) can be based on physical goods movements or changes in stock.2007 Product Warehouse Task Definition Document that helps Extended Warehouse Management (EWM) move products. the product WTs also have a documentation function. One item that decreases the stock.SAP Online Help 20. for example. the product WT consists of an item that decreases the stock. When you confirm a product WT. or when you confirm different pick handling units. the product WT consists of an item that increases the stock. For transfer postings. Use The product WT contains all the information required to execute the physical transfer of products into the warehouse. it consists of either an item with the source destination bin or destination storage bin. A product WT reserves the quantities. For goods issue postings. when you partially pick from a nested handling unit. ● ● ● What should be moved? Which quantity should be moved? From where (source storage bin) should the product be moved. You create partial confirmations. a difference quantity exists. since they document movements in the warehouse. If you confirm a product WT with a difference. you inform EWM what you have processed this product WT and that the goods have arrived at their destination. and one item that increases the stock. and to where (destination storage bin)? When you create a product WT. EWM creates one item for each partial confirmation. In the case of partial confirmations. out of the warehouse. or it consists of more than one item in the case of partial confirmations. the product WT consists of two items. When you confirm a product WT.07. it consists of an item with the source storage bin and destination storage bin. If the planned quantity (target quantity) differs from the actual quantity of stock that is moved. the system automatically posts the difference quantity to a “difference interface”. or within the warehouse from one storage bin to another storage bin. ● ● ● ● For goods receipt postings. so that these are no longer available for other product WTs. Structure A product WT contains all necessary information about a goods movement to be executed. SAP Extended Warehouse Management (SAP EWM) 510 406 .

2007 Handling Unit Warehouse Task Definition Document that helps Extended Warehouse Management (EWM) to move handling units (HUs). Once confirmed. It does not reserve any quantities. A handling unit warehouse task (HU WT) is based on goods movements. and to where (destination storage bin)? The HU WT always consists of an item with the source destination bin and destination storage bin.SAP Online Help 20. you inform EWM what you have processed this HU WT and that the goods have arrived at their destination. When you confirm a HU WT. Structure An HU WT contains all necessary information about a goods movement to be executed. you can also use the HU WT for the loading and unloading process. ● ● Which HU should be moved? From where (source storage bin) should the HU be moved. SAP Extended Warehouse Management (SAP EWM) 510 407 . since they document movements in the warehouse. the HU WTs also have a documentation function.07. 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.

GR Zone High Rack Storage Area ID Point 1 2 For example. the HUs are loaded from a forklift onto a conveyor.07. Since EWM only assigns the destination storage bin after the HU arrives at the ID point. ● Changing the mode of transport A conveyor equipment change can occur at an ID point. if you have assigned the ID point storage type 0081 to the storage type 0080.SAP Online Help 20. For example. 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. you have to use the ID point to execute the putaway of all handling units (HUs). and want to put away goods in the storage type 0080. then EWM proposes the ID point storage type 0081. The following figure illustrates the transfer of products from the goods receiving zone to a high rack storage area using an ID point. Use In many warehouses. the ID point is a physical place in a HU-managed warehouse at which you identify goods receipts for further processing. In Extended Warehouse Management (EWM). EWM determines the location of the storage bin based on the most current information about the storage type's space availability. ● To determine the final destination EWM determines the destination storage bin in the final storage type at the ID point. In these warehouse types. certain storage types (such as high rack storage areas) require identification points (ID points).2007 Identification Point Definition Place in an automated warehouse at which you identify newly-arrived goods. SAP Extended Warehouse Management (SAP EWM) 510 408 .

see Layout-Oriented Storage Control [Seite 340]. by choosing Cross-Process Settings → Warehouse Task → Define Layout-Oriented Storage Control.. b. ● . assign your IDpoint to a storage type. d.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. Select the storage type to which you want to assign the ID point. Choose ID Point Active. c. For more information about layout-oriented storage control. 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.07.. SAP Extended Warehouse Management (SAP EWM) 510 409 . by setting the storage role Storage Type Is ID Point. choose Master Data → Define Storage Types. see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings → Warehouse Task → Define Layout-Oriented Storage Control. For more information about Customizing for layout-oriented storage control. In Customizing for EWM.SAP Online Help 20.

you bring the HU to the HU-managed pick point to carry out the actual picking. choose Master Data → Work Center → Define Work Center.07. EWM determines a new storage bin in the storage type and creates a corresponding HU warehouse task with the destination storage bin. Use If you cannot execute partial stock picks in a storage type. for example due to physical restrictions in a high rack storage area.SAP Online Help 20. A pick point can also be a marked floor area to which you bring entire pallets for removal of products. because you have a special storage type for partial HUs. ● You have determined a fixed storage type for the return transfer of HUs. At the 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 pick the required product quantity from the HU and remove the required products to the goods issue zone. ● You putaway the partial HU back into the same storage type in which you previously removed it. Return Transfer of HUs You can putaway partial HUs back into the warehouse after picking at the pick point. In an automated high rack storage area (HRSA). In the Implementation Guide (IMG) for Extended Warehouse Management (EWM). The following graphic illustrates how a partial stock pick occurs using a pick point. 2. SAP Extended Warehouse Management (SAP EWM) 510 410 . the pick point can be a certain point on the conveyor line along which you move the HUs for picking. for example.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). 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.. you use pick points to pick partial quantities or to repack. 1.

2007 You do not determine a fixed storage type for the return transfer of HUs. 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. ● For more information about layout-oriented storage control.SAP Online Help 20. see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings → Warehouse Task → Define Layout-Oriented Storage Control. b. SAP Extended Warehouse Management (SAP EWM) 510 411 . choose Master Data → Work Center → Define Work Center. c. by choosing Cross-Process Settings → Warehouse Task → Define Layout-Oriented Storage Control. In Customizing for EWM. EWM determines the storage type as well as the destination storage bin by using putaway strategies [Seite 375]. d. ● You set your pick point as work center. see Layout-Oriented Storage Control [Seite 340]. For more information about Customizing for layout-oriented storage control. Select the storage type to which you want to assign the pick point. assign your pick point to a storage type. Integration ● You define a pick-point in EWM as the “pick point“ storage type in Customizing for EWM. by setting the storage role Storage Type Is Pick Point. choose Master Data → Define Storage Type. In Customizing for EWM. Specify Pick Point Active.07. under Master Data → Define Storage Type.

07. EWM creates warehouse orders pursuant to the warehouse tasks. you can also create a warehouse task as follows: ● ● Manually. Activities When EWM creates a warehouse task for a warehouse request. ● By default.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. see Storage Bin Determination for Putaway [Seite 291] or Stock Determination [Seite 341]. EWM determines this time for each warehouse task. For more information. Based on this. to assemble work packages for the individual warehouse workers. if resource management is used. either automatically or manually depending on the release methods you have defined for the wave or wave template. ● Instead of this standard creation of warehouse tasks through wave release.SAP Online Help 20. with the user interface Automatically. EWM simultaneously creates warehouse tasks [Seite 405] for stock removal or internal stock movements. In addition. it simultaneously updates this warehouse request. it uses putaway strategies [Seite 375] to determine the storage bin. you can also create a warehouse task as follows: SAP Extended Warehouse Management (SAP EWM) 510 412 . or stock removal strategies [Seite 396] to determine the stock. The warehouse order includes the sum of these times. The parameters of extract time determination formulas for a warehouse task are dependent on the product. you or EWM create warehouse tasks by releasing a wave. EWM updates this change in the warehouse request as well. warehouse order creation supplements the extract time determination with a setup time that is defined in the warehouse order creation rule. Instead of this standard creation of warehouse tasks through wave release. After a wave is generated. If the document flow update leads to a change in status. see Processing of Waves [Seite 771]. the unit to be transported. EWM carries out this update by updating the document flow. For more information. by calling a Post Processing Framework action (PPF action) Features When EWM creates a warehouse task for a warehouse request. For more information about Customizing for extract time determination. Optionally. and geographical dependencies. see the implementation guide (IMG) for EWM under Cross-Process Settings → Warehouse Task → Define Extract Time Determination. EWM determines the latest start time of a warehouse order. the quantity. Extract Time Determination The extract time determination calculates the target time effort to execute a stock movement. it can be released immediately. a route time is determined based on the resource used. Warehouse order creation [Seite 419] adds up the extract time of the individual warehouse tasks for a warehouse order.

SAP Online Help ○ 20. If you want to create warehouse tasks automatically by calling a PPF action. choose Extended Warehouse Management → Print → Display and Process PPF Actions. on the SAP Easy Access screen. 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).07.2007 If you want to create warehouse tasks manually using the user interface. ○ SAP Extended Warehouse Management (SAP EWM) 510 413 .

Results SAP APO has calculated the priority points and has communicated this to EWM via the ERP system .. EWM saves the priority points for an inbound delivery at item level. EWM or you activate the inbound delivery request. SAP APO sends the result of this recalculation to EWM via the ERP system. Provided the Warehouse Activities status is not Completed.SAP Online Help 20. 1. Process . EWM triggers an asynchronous request for the recalculation of priority points in SAP APO via the ERP system. For more information. EWM has updated priority points in the inbound delivery. EWM calls the Business Add-In (BAdI) /SCWM/EX_DLV_DET_LOAD to display the inbound delivery. EWM updates the priority points in the inbound delivery. At the same time. EWM aggregates the priority points at transportation unit level using the BAdI /SCWM/EX_SR_PRIOP. 4. 5.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.07. EWM updates the inbound delivery until the Warehouse Activities Status is Completed. EWM updates the priority points in the inbound delivery and aggregates the priority points at transportation unit level. EWM creates an inbound delivery from the active inbound delivery request. 6. SAP Extended Warehouse Management (SAP EWM) 510 414 . see the report documentation. You can start the report /SCWM/PRIOP_UPDREQ for the recalculation of priority points from the SAP Easy Access display. SAP APO calculates the priority points at item level. under Extended Warehouse Management → Delivery Processing → Inbound Delivery → Update Priority Points. 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. You can see this on the user interface for unloading. Based on the notification. The ERP system notifies SAP APO and EWM about this. b. which then communicates them to EWM. SAP APO communicates the calculated priority points to the ERP system.. 3. EWM creates an inbound delivery request. As with the first calculation (step 4). This BAdI calculates an aggregated priority at header level. The ERP system receives an advanced shipping notification (ASN) and creates an inbound delivery. 2. the system executes the following: a.

SAP Online Help 20.2007 Ad Hoc Movement Use Ad hoc movements are unplanned goods movements that you create manually within a warehouse. If you do not want the product to be removed from a specific storage bin. you manually create a product warehouse task (product WT) or a handling unit warehouse task (HU WT). For more information about prerequisites. You want to take a product to the appropriate storage bin for scrapping. You want to perform unplanned rearrangement movements. If you do not enter a source or destination storage bin for ad hoc movement and want the system to determine this automatically. You have defined a warehouse process type in Customizing for EWM under CrossProcess Settings → Warehouse Task → Define Warehouse Process Type. you move the stock of products from one storage bin to another. for example for a quality inspection. Prerequisites ● ● ● Stock is available for the product to be moved. If you work with HUs. Warehouse process type Destination storage data (optional) Reason (optional) – SAP Extended Warehouse Management (SAP EWM) 510 415 . you can control the determination of the source storage data using stock removal strategies. An ad hoc movement may be necessary for the following reasons: ● ● ● ● ● ● The wrong product is located in the storage bin. Instead. You have to clear away stock lying around in the warehouse. you can control this using stock removal and putaway strategies. This means that the decision to make an ad hoc movement is not controlled by the system.07. see Putaway and Stock Removal Strategies [Seite 374]. Ad hoc movements do not have a preceding document. you can also unpack or repack the products belonging to an HU by creating a product WT in the HU WT. To be able to reproduce these movements. You have to take the product to another storage bin due to damage. Features In an ad hoc movement. it is triggered manually. 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. 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. You have to empty an aisle or storage bin for safety reasons.

You can. storage section. in other words. Depending on the warehouse process type. for example. For the values entered manually. you can also perform ad hoc movements for products and HUs.SAP Online Help 20. see Ad Hoc Movements Using Radio Frequency [Seite 809]. cancel it. the system checks if they match the configuration of the storage type. you can confirm WTs directly after they have been created. on the SAP Easy Access screen. on the SAP Easy Access screen. the assigned product quantity is not available at the source storage bin nor at the destination storage bin. After you have confirmed a WT you can no longer delete it. choose Extended Warehouse Management → Work Scheduling → Create Warehouse Task Without Reference → Move Product. but belongs to reserved stock.07. Actions To create a product WT. choose Extended Warehouse Management → Work Scheduling → Create Warehouse Task Without Reference → Move Handling Unit.2007 You can manually overwrite the values determined by the system. if mixed storage or receipts are allowed. Radio Frequency Environment In a radio frequency environment. Immediate confirmation of the WTs is optional. To create an HU WT. For more information. however. SAP Extended Warehouse Management (SAP EWM) 510 416 . While a WT is still open. and storage bin in question. until you have confirmed it.

for example. You make these settings in Customizing for EWM under Internal Warehouse Processes → Default Values for Posting Changes. you can make a posting change for stock. but is no longer to be available for picking. In this case. see Serial Number [Seite 571]. whether a warehouse task (WT) is created automatically during the posting change. You can change the following stock attributes. For more information about serial numbers. Here you define. You have the following options that you can configure in Customizing. the system does not create a WT and the stock is simply given a different stock type. 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. ■ The stock is to remain in the storage bin. SAP Extended Warehouse Management (SAP EWM) 510 417 . In this case. The stock is booked out of the source storage bin and then the WT is created automatically. You want to take the stock to the quality department. the system creates a WT.SAP Online Help 20. 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. for example: ● ● ● ● Storage bin Stock type Batch Sales order or project You want to move stock from available stock to quality inspection stock.07. You have optionally defined destination data for stocks in conjunction with the warehouse process type that the system is to suggest for posting changes. or whether it is to be created before or after the posting change. for example: ● ● From available stock to blocked stock (for example. ● Features You make a posting change for stock by changing the relevant stock attributes and then creating the posting change.2007 Posting Change for Stocks Use In Extended Warehouse Management (EWM). ■ ○ You can make posting changes for stock for which serial numbers exist on a serial number basis.

you can choose and make a posting change for both available stock and the entire stock.07.2007 Activities To post stocks. SAP Extended Warehouse Management (SAP EWM) 510 418 .SAP Online Help 20. on the SAP Easy Access screen. In this transaction. choose Extended Warehouse Management → Work Scheduling → Make Posting Change for Product.

SAP Extended Warehouse Management (SAP EWM) 510 419 .2007 Warehouse Order Creation Use This function groups together warehouse tasks into warehouse orders. ● Storage Bins For more information about defining number ranges for warehouse orders. You can create locked warehouse orders resulting from the wave release. according to the warehouse order creation rules (WO creation rules) you have defined. then C. for example. choose Extended Warehouse Management → Master Data → Storage Bin → Assign Start/End Storage Bin for Activity Area. on the SAP Easy Access screen. Integration You assign warehouse orders to warehouse workers in resource management. EWM joins the warehouse tasks together into warehouse orders. 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]).SAP Online Help 20. If you want to release the lock on a warehouse order. see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Warehouse Order → Define Number Ranges for Warehouse Order. 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. You cannot initially continue to process these warehouse orders. ● Activity Areas For more information about defining number ranges for warehouse orders. For warehouse order creation. Warehouse order creation is particularly suitable for optimizing processes for picking. EWM works through the WO creation rules in sequence. you can select the Unlock WO method. ● Start Bins To do so. EWM creates warehouse tasks. according to your settings in Customizing for warehouse orders [Seite 423]. After the wave and wave item have been released (either automatically by EWM or manually by a user). Features A wave consists of a number of deliveries. 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. and thus creates optimum work packages for you. EWM uses the search sequence for WO creation. for example. first rule A. you define rules with their relevant criteria. then B. see the IMG for EWM under Master Data → Activity Areas → Define Activity Area. A warehouse order can contain warehouse tasks from more than one delivery. see the IMG for EWM under Master Data → Storage Bins. You can use a method in the warehouse management monitor [Seite 878] to release the lock on the warehouse orders. During this summarization of the warehouse tasks into warehouse orders.07.

● ● Packing mode Consolidation group During warehouse order creation.SAP Online Help 20.07. the consolidation group influences which warehouse tasks you are permitted to pack together. the system uses a remainder rule [Extern] .2007 The individual WO creation rule can contain sort rules [Extern]. it sorts the warehouse tasks according to these sort rules. see the IMG for EWM under CrossProcess Settings → Warehouse Order → Define Sorting Rules for Warehouse Tasks. As soon as EWM applies a WO creation rule. 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. If EWM has applied all the user-defined WO creation rules for the search sequence. 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. ● Filters For more information about item filters or subtotal filters. see Filters for Warehouse Order Creation Rules [Seite 424]. and transmits it to the relevant warehouse tasks. which you assign to a packaging specification. and there are still unprocessed 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. SAP Extended Warehouse Management (SAP EWM) 510 420 . EWM determines the consolidation group in the delivery. see the IMG for EWM under Cross-Process Settings → Warehouse Order → Define Packing Profile for Warehouse Order Creation. For more information about defining packing profiles. You define the maximum number of consolidation groups in a warehouse order as the definition of a limit value. Since the work packages for the warehouse employee are based on the complete summarization of warehouse tasks into warehouse orders. ● Limit value For more information. then after all user-defined WO creation rules have been applied. This rule creates warehouse orders for the remaining warehouse tasks. no warehouse tasks must be left over that are not assigned to a warehouse order. then warehouse order creation uses a standard rule [Extern] . You specify these parameters in a packing profile.

limit values. the monitor SAP and Open Documents → Warehouse Tasks. 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. v. and select an option for Split WT. and uses the wave as a basis for creating a suitable number of warehouse tasks. which contain the relevant warehouse tasks. Enter a warehouse order creation rule. then on the SAP Easy Access screen choose Extended Warehouse Management → Monitoring → Warehouse Management Monitor. For more information about setting the consolidation group. Define Packing Profile for Warehouse Order Creation. i. choose the warehouse task status Open and Execute. EWM groups the warehouse requests into a wave (for example. and the packing mode. and select an option for Split TO. Execute.. Select one or more open warehouse tasks and choose Other Methods → Simulate Warehouse Order. For example. parameters for packing. iv. filters. If you do not make an entry. a wave pick) and releases it.SAP Online Help You can simulate creation of warehouse orders for your warehouse tasks. ● If you want to simulate warehouse order creation for your warehouse tasks. EWM starts warehouse order creation. ○ For more information about making settings for the sorting rules. . then EWM executes the warehouse order creation rules according to the search sequence for warehouse order creation rules. EWM creates warehouse orders for each warehouse task. or specify the number of work processes depending on the warehouse number.. Choose warehouse number 0001.. Activities ● ● ● ● EWM creates a list of warehouse requests. according to your Customizing settings. 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. ii.07. iii. you can activate the log for WO creation for each warehouse number. The WO Create Rule dialog box appears. . 20. In the dialog box. SAP Extended Warehouse Management (SAP EWM) 510 421 . activity area or warehouse order creation rule.2007 You can define control parameters for warehouse order creation..

2007 If you want to define control parameters for warehouse order creation.07.SAP Online Help ● 20. SAP Extended Warehouse Management (SAP EWM) 510 422 . from the SAP Easy Access choose Extended Warehouse Management → Settings → Warehouse Order → Set Up Control Parameters for Warehouse Order Creation.

Example EWM creates warehouse tasks for an outbound delivery with four delivery items. Integration The warehouse groups together warehouse tasks or physical inventory items. SAP Extended Warehouse Management (SAP EWM) 510 423 .SAP Online Help 20. For more information about warehouse order creation rules. and makes them available for processing. You can adjust the scope and type of a warehouse order using the warehouse order creation rules that you have defined in Customizing. The warehouse order consists of warehouse tasks or physical inventory items. in other words you create physical inventory items. Use When you move products. EWM uses warehouse order creation to assign the resulting four warehouse tasks to a new warehouse order. see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Warehouse Order → Define Creation Rule for Warehouse Orders. in other words you or Extended Warehouse Management (EWM) create warehouse tasks.2007 Warehouse Order Definition Document that represents an executable work package that a warehouse employee should perform at a specific time. A warehouse employee receives this warehouse order as a work package to pick the items listed in the delivery. EWM also groups these physical inventory items together into warehouse orders.07. then EWM groups these warehouse tasks together into warehouse orders. When you perform a physical inventory.

If it does not fit. whether it should use another warehouse order creation rule to check the warehouse task that has not yet been processed. Item Filter You define item filters. EWM stops processing the warehouse tasks. according to your Customizing settings. For more information about Customizing for filter parameters for warehouse tasks. Warehouse order creation uses the filters on all warehouse tasks that you have not yet assigned to a warehouse order. EWM checks. whether it should use another warehouse order creation rule to check the warehouse tasks that have not yet been processed. During this. containing values you have defined.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. EWM works out the subtotal for each consolidation group. For more information about Customizing for filter parameters for warehouse tasks. according to your Customizing settings. EWM checks. During processing of a warehouse task. see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Warehouse Order → Define Filters for Warehouse Order Creation Rules. then EWM continues processing for the warehouse task. EWM checks whether the given item or subtotal filter fits. Use You can define two types of filters: Item Filters [Extern] and Subtotal Filters [Extern]. then EWM continues processing for the warehouse tasks. For more information about defining sorting rules.SAP Online Help 20. You must have defined sorting rules with the sort field DSTGRP (consolidation group). During processing of several warehouse tasks. If the filter fits the transfer orders. In the case of a subtotal filter. If the filter fits the warehouse task. so that EWM checks the individual warehouse task against the filter criteria defined in your Customizing settings. so that EWM can use the filter criteria defined in your Customizing settings to compare several warehouse tasks against a subtotal. EWM stops processing the warehouse task. for the warehouse tasks to process. SAP Extended Warehouse Management (SAP EWM) 510 424 . see the IMG for EWM under Cross-Process Settings → Warehouse Order → Define Filters for Warehouse Order Creation Rules. Subtotal Filter You define subtotal filters. and which WO creation should process. this means that EWM does not process the entire group of warehouse tasks for a consolidation group using the current filter. If it does not fit. see the IMG for EWM under Cross-Process Settings → Warehouse Order → Define Sorting Rules for Warehouse Tasks. EWM checks whether the given item filter fits.07.

07. Extended Warehouse Management (EWM) compares the warehouse tasks that passed the checks in the warehouse order creation rule (for example. EWM creates a warehouse order containing all the warehouse tasks that do not exceed the limit value.SAP Online Help 20. against the limit values defined in your Customizing settings. SAP Extended Warehouse Management (SAP EWM) 510 425 . As soon as the transfer orders exceed one of the limit values. filter criteria). It continues with this process until it has processed all the warehouse tasks. For more information about Customizing for limit values for warehouse orders. EWM creates new warehouse orders for the remaining warehouse tasks. see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Warehouse Order → Define Limit Values for the Size of a Warehouse Order.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.

according to your Customizing settings. the first printout is damaged.SAP Online Help 20.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. For example. you have defined the condition tables. 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. These lists contain information about the storage bin to and from which a warehouse employee should move specific goods. For more information about the structure and Customizing for the Post Processing Framework. Prerequisites You have made the settings in Customizing for PPF: ● You have defined the PPF action definitions with the relevant processing types. and the spool parameter.07. which also prints all corresponding warehouse tasks. in order to determine the printer. the form type. 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). In Customizing for the PPF action definition. You can use this function in the warehouse management monitor. from the user interface for warehouse tasks. Additionally. 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. EWM uses the Post Processing Framework (PPF) for message control. to manually print a warehouse order. or your require a second printout. EWM uses condition technique in the schedule condition for PPF. Integration ● ● ● Printing of warehouse orders and warehouse tasks is based on SAPscript texts and SAP Smart Forms as form templates. SAP Extended Warehouse Management (SAP EWM) 510 426 .

PPF triggers the executing method and therefore printing: SAP Extended Warehouse Management (SAP EWM) 510 427 . 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. then condition technique finds the matching condition record. you have defined the condition maintenance group.07. Features For printing warehouse orders. The condition schema specifies the conditions that you permit for determining data (such as printer. ● ● In Customizing. you have assigned the relevant condition schemas to your condition types. and therefore the access sequence to the condition tables to search.2007 In Customizing. packaging material type. In Customizing. The following table gives you an overview of the action definitions and their corresponding SAP Smart Forms forms. for example. transfer order confirmation. For each action definition there is also an SAP Smart Forms form. which SAP delivers. the following action definitions are supported in PPF in the application /SCWM/WME in the action profile /SCWM/HU. you have defined your condition tables from the field catalog. These fields represent the condition under which the condition technique finds the condition record. printing a warehouse order list and printing individual documents for the warehouse order. you have defined condition types. You have selected fields from the field catalog as key fields. you have assigned the condition schema to the application object (warehouse process type. These action definitions were created for each form type. then you automatically call up PPF. and activation of product warehouse tasks. ● ● You have defined the logical conditions that you want to use in the condition records. The assignment between action definition and SAP Smart Forms form is specified in the created condition records. ● ● In Customizing. In the following circumstances. and thus enable you to simultaneously print several different documents. The decision whether to print is dependent on the condition records that are found in the schedule condition. The condition maintenance group is required for creating condition records. work center). The system only supports printing of SAP Smart Forms. The condition maintenance group specifies the condition tables and therefore the key fields. form type) and specifies the sequence (access sequence) in which condition technique should consider them. if you attempt to print during storage control. In Customizing.SAP Online Help 20. If a data record transferred by EWM matches your key fields. You have defined warehouse-number-specific print settings (in particular the spool parameters).

and calls up the application data. Activities ● ● ● ● ● ● ● ● ● EWM automatically triggers the print run from processing. or you trigger it manually. During printing or repeat printing. To do this.07. In this case. you can also execute PPF action definitions for which there are no defined condition records. and spool parameters. PPF writes a determination log and a processing log. PPF determines the function module that corresponds to the SAP Smart Form form.SAP Online Help ● ● 20. and is fulfilled. SAP Extended Warehouse Management (SAP EWM) 510 428 . The PPF calls the schedule condition that corresponds to the PPF action definition. the PPF calls determination in the condition technique. the system cannot determine the necessary data such as printer. In the schedule condition. EWM calls the PPF and transmits the application data. During printing. and the SAP Smart Forms form. spool parameters. 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. PPF reads the current application data.2007 There is a condition record in which the PPF action definition matches the current PPF action definition. you can switch them on and off. The logical condition is entered in the condition record. and you must enter this data manually. Determination of the condition technique returns the relevant condition record. Since these logs can become extremely large. form name. use parameter /SCWM/WO_PRT_PROT. This determines the printer. PPF saves the action that was executed and the logs that were written.

07. the message only contains the number of warehouse orders. you have made sure that the warehouse activity area and queue for these warehouse tasks are identical (see Warehouse Order Creation [Seite 419]). ascending. but that no warehouse task exists for at least one of the products in the HU. ● Green means that you have specified a valid HU. In doing this. choose Save. For example. ● Activities ● ● On the SAP Easy Access screen. and increased the number of HUs in the new warehouse order that is to be created by one. Prerequisites ● ● You have made sure that putaway warehouse tasks exist and are active for the entire contents of the HU. Red means that you have specified an HU. and the HU scanned last to position three. and that warehouse tasks exist for all products in the HU.SAP Online Help 20. When you perform putaway. and Extended Warehouse Management (EWM) is able to determine the optimal putaway path. you can get the warehouse order number from the log. EWM shows you the specified HU in the lower part of the screen. EWM does not update the screen content for the total weight and total volume. one after each other. You can specify multiple HUs in the entry field. and does not include the HU in the new warehouse order that is to be created. the next HU to position two. If EWM is to generate a single warehouse order for all warehouse tasks that belong to the HUs you have specified. and saves the warehouse tasks in this order. EWM displays a success message if appropriate. EWM attempts to generate a warehouse order for all warehouse tasks. A traffic light shows the status of the warehouse task. EWM updates the screen content. This allows you to put away the HUs collectively. After you have specified all the HUs. EWM shows you the position in the Radio Frequency dialog (RF dialog). ● Features This function is optimized so that you can operate it using a hand-held scanner that is installed on a keyboard filter. In this case. you can take the warehouse order number directly from the message. EWM assigns the HU scanned first to position one. SAP Extended Warehouse Management (SAP EWM) 510 429 . If EWM generates one warehouse order only. and assigns the HU to a position field. EWM deletes all warehouse tasks of the HUs from your warehouse orders. you have scheduled a corresponding PPF action. EWM has updated screen content for the total weight and total volume. choose Extended Warehouse Management → Execution → Manually Assemble Warehouse Orders. you scan three HUs. If EWM generates multiple warehouse orders.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. If you want to print warehouse orders using a PPF action. Make sure that the position of the HU in EWM matches the physical position of the HU in the resource.

choose the PPF action you require for printing warehouse orders (see Printing Warehouse Orders and Warehouse Tasks [Seite 426]).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.07. Under Create Action. SAP Extended Warehouse Management (SAP EWM) 510 430 .SAP Online Help ● 20.

see Scenarios for Connecting Non-SAP Systems [Seite 432] and Description of the IDocs [Seite 459].07. In contrast to synchronous Remote Function Call (RFC). For more information. 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.SAP Online Help 20.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. SAP Extended Warehouse Management (SAP EWM) 510 431 . such as warehouse control units (WCU) to Extended Warehouse Management (EWM). the system saves the data in an intermediate storage area. Integration The interface allows communication between the connected systems on the basis of the transactional Remote Function Call [Extern] (tRFC).

the non-SAP systems always represent standalone systems for the SAP system. However.SAP Online Help 20.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. such as warehouse control units (WCU). see Modification Concepts: IDoc Receipt [Seite 484] and Modification Concepts: IDoc Issue [Seite 487]. SAP Extended Warehouse Management (SAP EWM) 510 432 . Activities You determine the task distribution. warehouse control and execution of driving commands are not part of EWM's tasks.07. The following scenarios give you an overview of typical ways in which this interface can be used. For this reason. The scenarios focus on the task distribution between EWM and the relevant connected nonSAP system. as well as other tasks such as optimizing the stock movenents or additional control mechanisms. For more information. between EWM and the non-SAP system. Non-SAP systems include warehouse systems dependent on EWM. which can take on control of the product flow. 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. The flexibility of the EWM-WCU interface enables you to make customerspecific adjustments and enhancements. according to your own requirements.

SAP Extended Warehouse Management (SAP EWM) 510 433 . You can only use this interface to tell EWM that stock movements have been performed.SAP Online Help 20. including: ● ● ● ● ● ● ● ● Managing product stocks and storage bins Triggering warehouse movements (stock removal. ● 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.07. 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. EWM performs all tasks relevant to warehouse management.2007 Connecting a Semi-Automated Warehouse Purpose In a semiautomatic warehouse. whilst a linked non-SAP system performs the actual stock movements. putaway. as well as to report the execution of stock movements to EWM. 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. The EWM-WCU interface is used to transfer pending stock movements to the non-SAP system. you manage the warehouse using Extended Warehouse Management (EWM).

EWM creates warehouse tasks (WTs) for the goods movements. You transport the pallet to the automatic conveyor. You print the warehouse tasks to use as a pallet receipt/issue slip. 2.. 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 Online Help 20. You scan in the barcode with the destination storage bin at the automatic conveyor. 1. 5. then the non-SAP system reports the stock movement for the WT using the message type /SCWM/WMTOCO to EWM. SAP Extended Warehouse Management (SAP EWM) 510 434 .07. 3. EWM confirms the warehouse task using the data reported using message type /SCWM/WMTOCO.. If the Customizing settings are such that the WT transferred from EWM must be reported to EWM. 7. 6. The automatic conveyor carries the pallet to the storage bin and puts it away. 4.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 . The destination storage bin for putaway is printed on the pallet slip in the form of a barcode.

. 2. If picking takes place directly at the storage bin.SAP Online Help 20. You print the warehouse tasks to use as a stock removal list. If the Customizing settings are such that the WT transferred from EWM must be reported to EWM.. 4. The non-SAP system constructs the warehouse task data in the form of an IDoc for the forklift guidance system. 6. The automatic conveyor removes the pallet from storage. You scan the barcode with the source storage bins into the automatic conveyor.07. SAP Extended Warehouse Management (SAP EWM) 510 435 . 1. the automatic conveyor goes directly to the relevant source storage bin when you scan in the stock removal slip.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 . EWM confirms the warehouse task using the data reported using message type /SCWM/WMTOCO. EWM creates warehouse tasks (WTs) for the stock removal. 5. and sends this IDoc to EWM. The source storage bin for stock removal is printed on the stock removal list in the form of a barcode. 3. then the non-SAP system reports the stock movement for the WT using the message type /SCWM/WMTOCO to EWM.

SAP Online Help 20. 3. 2. EWM creates warehouse tasks (WTs) for the goods movements. If the Customizing settings are such that the warehouse task transmitted from EWM must be reported to EWM. then you enter the stock movement in the forklift guidance system.07. or because you are collating remainder quantities to make more room). and sends this IDoc to EWM. EWM confirms the warehouse task using the data reported using message type /SCWM/WMTOCO.. due to a stock transfer within a warehouse. 5.. The forklift guidance system reports the stock movement to EWM using message type /SCWM/WMTOCO. 4. If you trigger stock movements manually (for example. 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. then the non-SAP system reports the stock movement for the warehouse task using the message type /SCWM/WMTOCO to EWM. The forklift control system monitors all of the movements. The external system executes the goods movements in the warehouse on the basis of the transferred data. 1. 2..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 . SAP Extended Warehouse Management (SAP EWM) 510 436 . The non-SAP system constructs the warehouse task data in the form of an IDoc for the forklift guidance system.. EWM transfers the warehouse tasks using the message type /SCWM/WMTORD to the non-SAP system. 1. Triggering warehouse movements manually via the external system .

07. and updates the stock data in the warehouse management system. SAP Extended Warehouse Management (SAP EWM) 510 437 .SAP Online Help 20.2007 3. EWM creates a warehouse task using the data reported using message type /SCWM/WMTOCO.

In fully automatic warehouses too.07. 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. The external system then takes on some of the warehouse management tasks. see Connecting a Semiautomatic Warehouse [Seite 433]. where the warehouse control can be used to optimize the stock movements triggered by EWM. you move products in this kind of storage type using identification points (ID points) and pick points. you should also take account of the scenario Connecting a Fully Automatic Warehouse as a Black Box [Seite 442]. For this reason. putaway. For more information. The non-SAP system only takes on warehouse control. you should take account of the warehouse technology at warehouse task creation. You have specified how warehouse management tasks will be distributed between EWM and the non-SAP system.SAP Online Help 20. Here. EWM takes on all warehouse management tasks.2007 Connecting a Fully Automated Warehouse Purpose If you want to use Extended Warehouse Management (EWM) in a fully automatic warehouse. EWM takes on the most important tasks of warehouse management: ● ● ● ● ● Managing the product stocks Managing storage bins Triggering warehouse movements (stock removal. the level of automation in the warehouse plays an important role: ● In simple automatic warehouses. 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 438 . 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. For warehouses with more complex warehouse automation.

SAP Extended Warehouse Management (SAP EWM) 510 439 . The non-SAP system reports execution of the stock movement for the handling unit to EWM. The destination storage bin for putaway is printed on the pallet slip in the form of a barcode. 9.SAP Online Help 20. the non-SAP system assigns the destination storage bin for the HU. and enter the pallet (handling unit) in EWM.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 . 8. The non-SAP system moves the HU to the destination storage bin and puts the HU away. EWM determines the destination storage type for the delivered handling unit [Seite 490] (HU). 7. If putaway is performed using an ID point. You receive an inbound delivery in the goods receipt interim storage area. 6. 4.. 10. The non-SAP system identifies the HU at the ID point using the bar code on the pallet slip. You print the WTs to use as a pallet receipt/issue slip. To optimize capacity utilization of the conveyor vehicles during putaway. You post the goods receipt for the inbound delivery.. using message type /SCWM/WMSUMO. then EWM creates a warehouse task (WT) from the goods receipt interface to the ID point. 5. 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. 1. 2. You transport the HU to the ID point. 3.

The non-SAP system optimizes the individual stock movements from the pick order. 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. 4. 11. EWM creates the warehouse task for putaway using the data reported using message type /SCWM/WMSUMO. 1. and sends this IDoc to EWM. 5. 3.2007 The non-SAP system constructs the warehouse task data in the form of an IDoc for the non-SAP system.. the system treats each warehouse task that is transferred as an independent pick order. which can consist of one or more transferred WTs. If you want to execute picking on the basis of outbound deliveries. SAP Extended Warehouse Management (SAP EWM) 510 440 . 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 . collating the picking of several outbound deliveries into one collective action. EWM transfers the WTs using the message type /SCWM/WMTORD to the non-SAP system. 2..07. to post the stock movement triggered by the non-SAP system. by specifying the sequence in which the required handling units should be removed from storage. If you want to control picking based on other criteria (for example.SAP Online Help 20. The non-SAP system can only collate the WTs into a wave after EWM has transmitted the wave release using message type /SCWM/WMRREF. based on a route). The external system processes the pick order. You trigger a stock removal or picking in EWM by. EWM creates warehouse tasks (WTs) for the outbound deliveries. for example.

Blocking Storage Bins In automatic warehouses. EWM creates the warehouse task for putaway using the data reported using message type /SCWM/WMSUMO.. Only the external system can ensure optimal pick point assignment. 7. to post the stock movement triggered by the non-SAP system. using message type /SCWM/WMTOCO. 5. The non-SAP system reports execution of picking for the handling units to EWM. 6. the non-SAP system assigns the destination storage bin for the HU.2007 If there is more than one ID point in the system. To tell EWM to unblock blocked storage bins.07. 3. or some bins cannot be reached by the warehouse technology. The non-SAP system moves the HU to the destination storage bin and puts the HU away. The non-SAP system transmits the storage bins to block using the message type /SCWM/WMBBIN to EWM. You confirm the pick and enter any differences that occured. using message type /SCWM/WMSUMO. 1. conveyor vehicles often cannot access certain storage bins. After picking. The external system identifies the HU at the ID point. you take the HUs with remaining quantities to the ID point for return transfer into the warehouse.. 8. You execute picking at the pick point. the non-SAP system transmits the storage bins or aisles affected to EWM using message type /SCWM/WMBBIN. Certain routes for the vehicles are no longer valid. 2. so that EWM cannot schedule any more stock movements for these storage bins. 6. and sends this IDoc to EWM. by way of a contour control.SAP Online Help 20. since the utilization of the warehousing equipment is at the fore. 4. then the non-SAP system also specifies the assignment of the individual picking transactions and HUs to the available pick points. Since you are performing warehouse management using EWM. The non-SAP system constructs the warehouse task data in the form of an IDoc for the non-SAP system. Return Transfer for Handling Units with Remaining Quantity . 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 441 . The external system displays the items to be picked on the screen at the pick point. you must block these storage bins as quickly as possible in EWM. EWM confirms the warehouse task using the data reported using message type /SCWM/WMTOCO. 9. The non-SAP system reports execution of the stock movement for the HU to EWM. To optimize capacity utilization of the conveyor vehicles during putaway.

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.07. EWM takes on all the standard functions.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] . If you want to connect this kind of storage type to your warehouse. In this storage type. In storage types not managed by the non-SAP system. For one or more of these storage types. EWM distributes the individual putaway and stock removal transactions to the various sub-storage-types. EWM hands over the entire warehouse management and warehouse control to the non-SAP system. SAP Extended Warehouse Management (SAP EWM) 510 442 . In storage types managed by the non-SAP system.SAP Online Help 20. an external system executes all of the warehouse functions and thus takes over the entire warehouse management and warehouse control for this storage type. Prerequisites You have defined the automated section of your warehouse as a separate storage type in EWM. 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. The automated storage type is connected as a black box to EWM. you can manage the entire warehouse complex (the warehouse number) using EWM. Since the automated storage type is only a part of your warehouse complex. EWM takes on the following functions: ● ● Management of summary stocks for each product Triggering and creating warehouse movements On the other hand. you should also take account of the scenario for Connecting a Fully-Automated Warehouse [Seite 438]. we recommend that you implement a system that combines warehouse controlling and warehouse management.

Alternatively. Optimizes material flow Performs goods movement Reports goods movement to EWM Performs physical inventory Reports differences to EWM Triggers and performs whse-int. 1. 2. you define several storage bins in the warehouse type. You post the goods receipt of the goods in Inventory Management. This means that a new product always occupies a new storage bin. SAP Extended Warehouse Management (SAP EWM) 510 443 . If you have selected the storage type managed by the non-SAP system for putaway.2007 You can define a fixed storage bin [Extern] for each product in this storage type.. ● The storage bins that you created in EWM for individual products have no meaning for the non-SAP system. EWM transmits the relevant WT items using the message type [Extern] /SCWM/WMTORD to the non-SAP system. 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.. The system cumulates the stocks of a product in a storage bin. which do not correspond to the physical storage bins. to manage the stocks of product in this storage type and to support physical inventory operations. Putaway . EWM creates warehouse tasks for putaway and specifies in which storage type the goods are put away.07. 3. You allow addition to existing stock for this storage type. 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.SAP Online Help ● 20. so that the system always places a product into this storage type.

EWM sends all stock removal WTs relevant for the storage type managed by the nonSAP system to the non-SAP system. to post the reported differences to a difference interface. EWM creates a warehouse task (WT) for the stock removal. 5. EWM confirms the individual items in the warehouse task. Stock Removal . The non-SAP system must not send product movements within the storage type managed by the non-SAP system. The non-SAP system decides the storage bin from which the required products should be removed. or using the transmitted HU number. then the non-SAP system reports the putaway to EWM using message type /SCWM/WMTOCO. 1. The non-SAP system transfers the transfer orders using the message type /SCWM/WMTORD to EWM. EWM uses the reported differences to create a warehouse task. 2.07.. using the reported data and actual quantities from the non-SAP system. If EWM reports execution goods movements. SAP Extended Warehouse Management (SAP EWM) 510 444 . 3.. 5. the non-SAP system reports these differences to EWM using the message type /SCWM/WMTOCO. 4. because EWM only manages the summary stocks for this storage type. 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 identifies the goods to put away using either the WT number and WT items.2007 4. using message type /SCWM/WMTORD.SAP Online Help 20.

Asynchronously to creation of the IDoc. 4. 3.07. The system can transfer individual IDocs or collect several IDocs and then transfer them to the external system later. When you create a warehouse task (WT) in EWM. 2. 1. in the form of an IDoc. For more information.. Prerequisites You have made the required TCP/IP settings [Seite 448]. The transmission is based on Remote Function Call. During creation of the WT. The system saves the created IDoc to the database. In Customizing.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. which receives the WT item.SAP Online Help 20. Process . see the Implementation Guide (IMG) for Extended Warehouse Management under Interfaces → Non-SAP Systems → Connect Subsystem. the Customizing settings define that the WT or WT item is relevant for transmission to the non-SAP system. the system prepares the data to be transmitted. and sends a receipt confirmation to the SAP system. The non-SAP system saves the received IDoc data. 6. For more information about the business background. the system uses ALE to trigger transmission of this IDoc to the non-SAP system. For more information.. see Scenarios for Connecting Non-SAP Systems [Seite 432]. For more information. 5. In Customizing. ● For each warehouse number. see Basis → Basis Services/Communication Interface → Remote Communications → The RFC API → Programming with the RFC API [Extern]. you have specified the circumstances in which a warehouse task (WT) is relevant for transmission to the non-SAP system. see BC – SAP Communication: Configuration [Extern]. 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. SAP Extended Warehouse Management (SAP EWM) 510 445 . see Description of the IDocs [Seite 459]. For more information about IDocs and their construction. you have defined the ALE interface. The non-SAP system must be ready to receive the transmitted data with a relevant program.

Note that an IDoc number is only unique within a single client in an SAP system. For more information. see Basis → Basis Services/Communication Interface → Remote Communications → The RFC API → Transactional RFC Client Programs.SAP Online Help 20. Error in the ALE interface: Transferred data is syntactically incorrect ALE adopts the IDoc and saves it. the SAP system automatically transfers all IDocs. which have not yet been sent. the IDoc number is no longer unique. The WT and the IDoc are creates in the same LUW. For more information. because the system only creates an IDoc once the source SAP system document exists. to ensure that transmission of the IDoc and processing of the transmitted data occur separately. If several clients of an SAP system or several SAP systems are involved in the communication with the external system. 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. The external system can also recognize double transfers from the IDoc number external system can also use the IDoc number to identify duplicate transfers. see IDoc Error Processing [Seite 477].2007 We recommend that you save the transmitted data in the non-SAP system first. Status management for the data received should prevent the external system from processing the data twice. In this case the external system cannot recognize IDocs that have been transferred twice from this number. For more information.07. As soon as the connection between the two systems exists again. You can also start this SAP Extended Warehouse Management (SAP EWM) 510 446 . 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. Error Processing If you receive an IDoc from EWM to a non-SAP system. 7. therefore they are updated synchronously. This is made possible by the unique transaction identification number (transaction ID). The external system should be able to recognize IDocs that have been transferred by the SAP system before. but cannot transfer the IDoc to the external system. which the SAP system assigns for each communication process.

For more information. SAP Extended Warehouse Management (SAP EWM) 510 447 .SAP Online Help 20.07.2007 report manually. see Processing Technical IDoc Errors [Seite 478].

sapgw00 and sapdp00. for example. see the documentation SAP Communication: Configuration [Extern]. In the standard system. For more information. SAP Extended Warehouse Management (SAP EWM) 510 448 . You work in registration mode.2007 Managing TCP/IP Settings As a prerequisite for communication. This means that the connection between the non-SAP system program and the gateway remains open. You have entered the name of the gateway and the dispatcher in the services file. IDocs are sent from the update transaction.07. you make the following TCP/IP settings: ● ● ● ● In order for the SAP system to find the target system.SAP Online Help 20. see Registering Server Programs with the SAP Gateway [Extern]. For details on the TCP/IP settings. you must fulfill the TCP/IP prerequisites. in particular the IP addresses must be known in the relevant hosts file. Ensure that the TCP/IP link was also created for the update machine. then the SAP gateway must have the authorization to start the external program (RFC server) using Remote Shell. If you do not work in registration mode.

2007 Managing Transaction Identifiers (TID) Purpose To ensure the security of the data to transfer.07.SAP Online Help 20. Process The following diagram shows the schematic process flow between the sending and receiving system: SAP Extended Warehouse Management (SAP EWM) 510 449 . 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.

SAP Online Help 20.07.2007 Sender Sender ( (Client ) ) Client Create/Get TID Create/Get TID Recipient Recipient ( (Server ) ) Server (worldwide unique number) (worldwide unique number) Save TID with data Save TID with data records to transfer records to transfer Call to the server: Call to the server: Transfer data and TID Transfer data and TID Save data and TID Save data and TID Everything OK Confirmation: Everything OK Confirmation: Update status Update status Not OK Not OK Send again Send again with same with same TID TID Delete TID and Delete TID and data data immediately or immediately or at later point at later point Confirmation: Confirmation: Receive data Receive data Check: Does TID exist/was itit Check: Does TID exist/was already processed? already processed? Do nothing Do nothing Yes Yes Process data Process data No No Update TID status Update TID status SAP Extended Warehouse Management (SAP EWM) 510 450 .

07. The processor would send the data again to ensure your update in the SAP system. the system must be able to recognize this.SAP Online Help 20. SAP Extended Warehouse Management (SAP EWM) 510 451 . communication could be terminated suddenly during the transmission of data for mobile entry of goods receipts.2007 Example For example. if the data had already been received and processed in the the SAP system after the first attempt at sending. However. It should not process the data a second time.

The SAP system should be able to recognize IDocs that have been transferred by the external system already. see SAP Communication: Configuration [Extern]. You have configured the ALE interface in Customizing for Extended Warehouse Management under Interfaces → Non-SAP Systems → Connect Subsystem. see Transactional RFC Client Programs [Extern]. the external system can transfer several IDocs. which the SAP system assigns for each communication process. If the non-SAP system cannot successfully transmit IDocs. then the non-SAP system must specify the same transaction ID again. The SAP system receives the transmitted IDoc using ALE.. The SAP system does not use the IDoc number to recognize a double transfer of IDocs from the external system. then the IDoc system documentation explicitly states this fact.SAP Online Help 20. For more information. The non-SAP system must always flag the transmitted data with this transaction ID. 5. The external system transfers the IDoc with an appropriate program. Status management for the data to be transferred should prevent the external system from not transferring data. 4. see Scenarios for Connecting NonSAP Systems [Seite 432]. If the non-SAP system re-transmits an IDoc due to a previous problem with communication. If an IDoc type only supports single transmission. The central function module is in the ALE layer. 3. see Programming with the RFC API [Extern]. The non-SAP system saves the data relevant for transmission to the SAP system.. For more information. and prepares this data for transmission as an IDoc. For more information.07. 6. Prerequisites You have defined the necessary TCP/IP settings. 2. As soon as the external system calls the function module on the SAP system side. ALE transmits the IDoc to EWM.2007 Data Flow: EWM Receives 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 data for the warehouse task (WT) from the non-SAP system to EWM. you must ensure that the non-SAP system transmits these IDocs again at a later point. Asynchronously to the receipt of the IDoc. saves the IDoc in the database. SAP Extended Warehouse Management (SAP EWM) 510 452 . which then takes over processing of the IDoc. 1. For more information about the business background. and reports the receipt of the IDoc to the non-SAP system. Process . This is made possible by the unique transaction identification number (transaction ID). The transmission is based on Remote Function Call (BC-ABA) [Extern].

SAP Online Help 7. For more information. see Processing Logical IDoc Errors in EWM [Seite 481]. For more information. EWM reports the processing status to ALE. the following problems can occur: Troubleshooting Symptom There is no connection between the external system and the SAP system What You Should Know The non-SAP system should use status management to ensure that the non-SAP system re-transmits the IDocs again at a later point.2007 Error Processing If you receive an IDoc from the non-SAP system in EWM. For more information. Error in the ALE interface: There are syntactical errors in the data that the external system sent to the ALE Error in the ALE interface: ● ● Inbound partner profile for the sending system IDoc message type are not defined Error in the application for EWM If processing of the received IDoc did not proceed correctly.07. For each IDoc. EWM uses the transmitted data as the basis for creating warehouse tasks. ALE cannot transmit the IDoc to EWM for processing. 20. see IDoc Error Processing [Seite 477]. 8. ALE uses the processing status to trigger error processing for the IDoc. SAP Extended Warehouse Management (SAP EWM) 510 453 . EWM transmits the relevant processing status. Although ALE copies the IDoc and saves it. see IDoc Error Processing [Seite 477].

but is not required during receipt. see Inbound Processing: Technical Realization [Extern]. this means that some fields are redundant for the EWM-WCU interface. but is not required at receipt.07. EDI_DD40 Field TABNAM MANDT Format CHAR 10 CLNT 3 Name Table structure name Client Relevant for Receipt Comments Not relevant Not relevant.SAP Online Help 20. X Unique communication number Sequential numbering of IDoc segments is transferred to the external system.2007 Data Formatting The system transfers data to structures EDI_DC40 and EDI_DD40. but the system transmits the field to the nonSAP system. Since EDI also uses these structures. For more information. but is not required at receipt. Not relevant X Actual application data in form of IDoc segment DOCNUM CHAR 16 IDoc number SEGNUM CHAR 6 SAP segment number SEGNAM PSGNUM CHAR 10 CHAR 6 SAP segment name Number of higher-level SAP segment HLEVEL CHAR 2 Hierarchy level of SAP segment DTINT2 SDATA CHAR 2 LCHR 1000 Empty field for EDI_DD Application data EDI_DC40 SAP Extended Warehouse Management (SAP EWM) 510 454 . X IDoc segment name The system transmits the field to the nonSAP system. The system transmits the field to the nonSAP system.

which is used to process IDocs. DOCREL CHAR 4 IDoc SAP release STATUS DOCTYP DIRECT RCVPOR RCVPRT RCVPRN CHAR 2 CHAR 8 CHAR 1 CHAR 10 CHAR 2 CHAR 10 IDoc status IDoc type Direction Recipient port Partner type of recipient Partner number of recipient X X Not relevant Value: LS For example: WM_SUB_0 0 1 for SAP to SUB Recommended as IDOCTYP RCVSAD RCVLAD STD STDVRS STDMES MESCOD CHAR 21 CHAR 70 CHAR 1 CHAR 6 CHAR 6 CHAR 3 EDI: Total SADR fields Logical address of recipient EDI standard Version of EDI standard EDI message type Logical message code * You can use both fields to specify a different function module than the standard function module in the ALE service level.2007 Field TABNAM MANDT DOCNUM Format CHAR 10 CLNT 3 CHAR 16 Name Table structure name Client IDoc number Relevant for Receipt Comments X Unique communication number The system transmits the field to the nonSAP system.SAP Online Help 20. but is not required at receipt.07. You can use both fields to specify a MESFCT CHAR 3 Logical message function * SAP Extended Warehouse Management (SAP EWM) 510 455 . in the table for inbound methods.

OUTMOD TEST SNDPOR SNDPRT SNDPRN CHAR 1 CHAR 1 CHAR 10 CHAR 2 CHAR 10 Output mode Test indicator Sender port Partner type of sender Partner number of sender X X Not relevant Value: LS For example: S11MAND000.2007 different function module than the standard function module in the ALE service level. which is used to process IDocs.SAP Online Help 20.07. in the table for inbound methods. if S11 is the sending SAP system SNDSAD SNDLAD REFINT REFGRP REFMES ARCKEY CREDAT CRETIM MESTYP CHAR 21 CHAR 70 CHAR 14 CHAR 14 CHAR 14 CHAR 70 DATS D 8 TIMS T 6 CHAR 6 EDI: Total SADR fields Logical address of sender Reference to transfer data Reference to message group Reference to message type EDI archive key IDoc creation date IDoc creation time Logical message type X For example WMTORD for warehouse tasks For example: WMTOID01 for WTs IDOCTYP CHAR 8 Name of basis IDoc Name of intermediate structure Partner function of recipient Partner role of X CIMTYP CHAR 8 RCVPFC SNDPFC CHAR 2 CHAR 2 SAP Extended Warehouse Management (SAP EWM) 510 456 .

. /SCWM/E2LTORI is release-dependent.. The system collates the four IDoc segments together under the unique number of the IDoc or the intermediate document. which the system numbers.. If you create IDoc in R/3 systems using transaction /nWE30. the system automatically creates three structures for each IDoc. (Item) .. We recommend choosing the E2 segment names during transfer of the segment name. for example. you send one EDI-DC40 record and four EDI_DD40 records per IDoc. Make sure that you initialize any fields in which you will not enter data. and /SCWM/E3LTORI. (Item) ... (Item) . (Item) . (Item) EDI_DC40 9000000000123456 9000000000123457 LS LS S11MAND002 S11MAND002 LS LS SUBSYSTEM1 SUBSYSTEM1 /SCWM/WM TORD /SCWM/WM TORD WMTOID01 WMTOID01 SAP Extended Warehouse Management (SAP EWM) 510 457 . The corresponding EDI_DC record is also identified from the DOCNUM.. You transfer two internal tables with the following construction: EDI_DD40 9000000000123456 9000000000123456 9000000000123456 9000000000123456 9000000000123457 9000000000123457 9000000000123457 9000000000123457 /SCWM/E2LTORH /SCWM/E2LTORI /SCWM/E2LTORI /SCWM/E2LTORI /SCWM/E2LTORH /SCWM/E2LTORI /SCWM/E2LTOR /SCWM/E2LTORI 00112345678905011 E 0001FRASCATI 0002BORDEAUX 0003CHIANTI 00112345678912011 A 0001CHATEAUNEUF 0002BORDEAUX 0003SOAVE .. since this is independent of the SAP release. /SCWM/E2LTORI.... (WT header data) . Example If..SAP Online Help sender SERIAL EXPRSS CHAR 20 CHAR 1 EDI/ALE: Serialization field Override during receipt 20.. you send a warehouse task with three items per IDoc from the non-SAP system to Extended Warehouse Management (EWM). you transmit one header segment and three item segments for each IDoc. /SCWM/E1LTORI is release-independent. For example.. (Item) .2007 You do not have to enter data in all fields of EDI-DC or EDI_DD.07... (WT header data) . In doing so. for the warehouse task item /SCWM/E1LTORI. and the system uses /SCWM/E3LTORI for documentation.

07.SAP Online Help 20.2007 SAP Extended Warehouse Management (SAP EWM) 510 458 .

07.SAP Online Help 20.2007 Description of the IDocs The interface between Extended Warehouse Management and non-SAP systems (EWMWCU interface) uses the following IDocs: IDocs for EWM-WCU Interface IDoc /SCWM/WMTOID01 /SCWM/WMTCID01 /SCWM/WMCAID01 /SCWM/WMBIID01 /SCWM/WMRRID01 /SCWM/WMSUID01 Partner Agreement Inbound and outbound Inbound Inbound and outbound Inbound Outbound Inbound Message type /SCWM/WMTORD /SCWM/WMTOCO /SCWM/WMCATO /SCWM/WMBBIN /SCWM/WMRREF /SCWM/WMSUMO Name Warehouse task Confirm warehouse tasks Cancellation/cancellation request WT Block storage bins Release waves Move handling unit SAP Extended Warehouse Management (SAP EWM) 510 459 .

for example. or a posting change. EWM transfers the warehouse task data to the connected external system in the form of IDoc /SCWM/WMTOID01. the system ● SAP Extended Warehouse Management (SAP EWM) 510 460 . Which IDoc the system fills and sends to the external system depends on several criteria: Criteria Warehouse movement type Details ● ● ● ● Warehouse process type Putaway Stock removal Stock transfer Posting change Defining the warehouse process type You define.SAP Online Help 20. the system transfers the HU number in field NLENR.07. the system transfers the numbers of the storage units involved. ● For putaway in HU-managed storage types. ● Based on the data in the warehouse task ○ ○ ○ ● Warehouse process type Transfer type Based on the storage types involved in the warehouse movement Based on the variant of the EWM message. you use IDoc /SCWM/WMTOID01 to send data from warehouse tasks from EWM to connected non-SAP systems. whether the goods receipt date should be set during putaway. stock transfer. Use EWM creates a warehouse task order for every warehouse movement. You should differentiate between the warehouse tasks according to the respective warehouse movement type. Cause of the warehouse task ● ● ● Manual WT WT for inbound or outbound delivery WT for warehouse process type Handling-unit-managed storage types If HU-managed storage types are affected by the warehouse movement. which you have defined in the definition of the movement for connection to the interface. stock removal. The external system requires a precise division of warehouse movements according to type. For stock removals from HUmanaged storage types. regardless of whether the movement is putaway.2007 IDoc for Sending WTs to a Non-SAP System Definition In Extended Warehouse Management (EWM).

which the system creates. We recommend creating test warehouse tasks for transmission to the external system. the system transfers both HU numbers involved. You determine the content on the IDoc for the individual customers.07. Structure Message Type You define the partner agreement outbound for message type /SCWM/WMTORD. so that you can check the content of the IDocs. Segments IDoc /SCWM/WMTOID01 is made up of the following segments: ● ● ● ● /SCWM/E1LTOIRH (warehouse task header) /SCWM/E1LTOIRH (warehouse task items) /SCWM/E1LPHUX (pick-handling unit) /SCWM/E1LCRSE (serial numbers for warehouse tasks) Segment definition /SCWM/E2LTORH0040 (WT header) Field LGNUM Format CHAR 3 Description Warehouse number Warehouse order Queue User name Required Entry X Comments Activate linkage in warehouse number first WHO QUEUE BNAME NUMC 10 NUMC 10 CHAR 12 Fields for segment /SCWM/E2LTORI0004 (WT items) Field TANUM PROCTY MATNR ENTITLED ENTITLED_ROLE Format NUMC 12 CHAR 4 CHAR 40 CHAR 10 CHAR 2 Description Warehouse task Warehouse process type Product Party entitled to dispose Partner role Required Entry Comments SAP Extended Warehouse Management (SAP EWM) 510 461 . ● For stock transfers between HUmanaged storage types. If you transfer the complete HU.2007 transfers the HU number in field VLENR. both HU numbers are the same. If you transfer material from one HU to another.SAP Online Help 20. the system transfers the HU number in both fields.

SAP Online Help 20.2007 OWNER OWNER_ROLE CHARG LETYP ANFME ALTME CHAR 10 CHAR 2 CHAR 10 CHAR 4 QUAN 31 UNIT 3 Owner Partner role Batch Handling unit type Requested quantity Alternative unit of measure (AUoM) Operative unit of measure (UoM) Target quantity in AUoM Target quantity in base UoM Base unit of measurement Source storage type Source storage section Source storage bin Destination storage type Destination storage section Destination storage bin Source HU Destination HU Warehouse process category External warehouse process Warehouse process GR date GR time Expiration date Certificate number OPUNIT VSOLA VSOLM MEINS VLTYP VLBER VLPLA NLTYP NLBER NLPLA VLENR NLENR TRART UNIT 3 QUAN 31 QUAN 31 UNIT 3 CHAR 4 CHAR 4 CHAR 18 CHAR 4 CHAR 4 CHAR 18 CHAR 20 CHAR 20 CHAR 1 PROCS CHAR 4 PRCES WDATU WDATZ VFDAT ZEUGN CHAR 4 DATS 8 TIMS 6 DATS 8 CHAR 10 SAP Extended Warehouse Management (SAP EWM) 510 462 .07.

SAP Online Help 20.2007 KOMPL SQUIT KZQUI MAKTX DOCCAT CHAR 1 CHAR 1 CHAR 1 CHAR 40 CHAR 3 Complete indicator Confirmation indicator Confirmation requirement Product description Reference document category Reference document number Reference document item Zero stock check Stock type Document category Document number Document item DOCNO CHAR 35 ITEMNO KZNKO CAT STOCK_DOCCAT STOCK_DOCNO STOCK_ITEMNO CHAR 10 CHAR 1 CHAR 2 CHAR 3 CHAR 35 CHAR 10 Segment definition /SCWM/E2LPHUX000 (pick-handling unit) Field LGNUM Data Type CHAR 3 Description Warehouse number Required Entry X Comments Switch on linkage in warehouse number WHO HUIDENT HUKNG PMAT ANZHU KZRTN CHAR 10 CHAR 20 NUMC 3 CHAR 40 NUMC 3 CHAR 1 Warehouse order Pick-handling unit HU identification Packaging material Number of pick-HUs to create Confirmation to subsystem Segment definition /SCWM/E1LCRSE (serial numbers for warehouse tasks) Field SERID Data Type CHAR 30 Description Serial number Required Entry Comments SAP Extended Warehouse Management (SAP EWM) 510 463 .07.

SAP Online Help 20.2007 SAP Extended Warehouse Management (SAP EWM) 510 464 .07.

You can also create warehouse tasks with incomplete entries in the non-SAP system and send these to EWM. You construct IDoc /SCWM/WMTOID01 in the non-SAP system to transfer the warehouse movement data to EWM. EWM receives the IDoc and creates a WT from it. Structure Message Type You define the partner agreement inbound for message type /SCWM/WMTORD. Only use warehouse process types for this IDoc. Use The external system triggers warehouse movements in a warehouse type and executes the physical transportation of products. which allow immediate confirmation. SAP Extended Warehouse Management (SAP EWM) 510 465 .2007 IDoc for Receiving WTs from a Non-SAP System Definition You use IDoc /SCWM/WMTCID01 to send warehouse-task-relevant data from the non-SAP system to Extended Warehouse Management (EWM).SAP Online Help 20. EWM. EWM creates a warehouse task from the IDoc data it received and immediately confirms it. The non-SAP system confirms the WT.07. the coordinates of the destination storage bin) and sends the complete WT back to the external system. The physical stock movement has already taken place when you receive information on a warehouse task from the non-SAP system in EWM. In this case. Only then does the non-SAP system transfer the data on the warehouse movements to EWM. in order to execute the physical warehouse movements and post the storage bins involved. Segments IDoc /SCWM/WMTOID01 is made up of the following segments: ● ● ● ● /SCWM/E1LTOIRH (warehouse task header) /SCWM/E1LTOIRH (warehouse task items) /SCWM/E1LPHUX (pick-handling unit) /SCWM/E1LCRSE (serial numbers for warehouse tasks) For more information in segment definition. as leading system. completing the warehouse movement. adds the missing entries (for example. see IDoc for Sending WTs to a Non-SAP System [Seite 460].

under Master Data → Define Storage Type or Cross-Process Settings → Warehouse Task → Define Warehouse Process Type. you report the WT item by item. During execution of the warehouse tasks. There can be several reports for each WT item. Prerequisites In Customizing for Extended Warehouse Management. you can confirm the WTs item by item. If the HU is a mixed HU and you move individual products. if you are putting away several pallets in your warehouse using one warehouse task. Confirmation of Handling Units If you work with handling units (HUs) in your warehouse and move the entire handling unit. Confirmation in a HU-Managed Bulk Storage Area You report the picked HUs to EWM when you confirm the warehouse task.07. Confirmation of Products Managed in Batches If you confirm batch-managed products during goods movements in a HU-managed bulk storage type. Use You use this IDoc to report executed warehouse tasks (WTs) to EWM. you can enter differences for individual WT items. Confirmation Without HU Management For stock removals. then you for this stock movement you confirm a warehouse task for the entire HU.2007 IDoc for Confirming Warehouse Tasks Definition You use IDoc /SCWM/WMTCID01 to send confirmations from the non-SAP system to Extended Warehouse Management (EWM). You use the CHARG field (report batch for bulk storage) in segment /SCWM/E2LTCCOI004. EWM uses this reported data to confirm this WT. set the BQUIT field in the segment /SCWM/E1LTCOI. EWM previously transmitted the data for the confirmation requirement in IDoc /SCWM/WMTOID01 in segment /SCWM/E1LTROI with field KZQUI to the non-SAP system. then you confirm the entire handling unit and enter the difference quantity for those items where you noticed a difference. In this case. When sending the WT data. If the reporting of individual HUs is completed for a WT item. For putaway. you confirm entire warehouse tasks. During confirmation of entire WTs. Only one report is allowed for each picked HU. you transmit the batch number of the removed products with the confirmation data. then there are several warehouse tasks for this handling unit. SAP Extended Warehouse Management (SAP EWM) 510 466 .SAP Online Help 20. if you notice differences in the handling unit. you have specified which warehouse tasks are subject to a confirmation requirement. You confirm the relevant warehouse task for each stock movement.

2007 If the products are managed in batches.0A) ○ ○ ○ ○ ○ ○ /SCWM/E1LTCOX: Confirm entire handling unit /SCWM/E1LTCOH: Confirm WT header /SCWM/E1LTCOI: Confirm WT items /SCWM/E1LCOHU: Confirm HU data for each WT item /SCWM/E1LEXCP: Exception during warehouse task confirmation /SCWM/E1LEXCP: Serial numbers for warehouse task confirmation Segment definition /SCWM/E2LTCOX002: Confirm handling unit Field LGNUM LENUM QNAME SQUIT NLPLA Data Type CHAR 4 CHAR 20 CHAR 12 CHAR 1 CHAR 18 Description Warehouse number Handling unit User name for the confirmation Confirm entire HU Destination storage bin X Value: ‘X’ The destination storage bin refers to the different storage bin for the complete HU (Customizing) Required Entry X X Comments NLENR CHAR 20 Destination handling unit Segment definition /SCWM/E2COHU000: HU data for each WT item Field LBNUM VONHU NACHU HUENT MENGA Data Type NUMC 12 CHAR 20 CHAR 20 CHAR 1 QUAN 31 Description WT number Source HU Destination HU Remove entire HU Quantity Required Entry Comments SAP Extended Warehouse Management (SAP EWM) 510 467 .07.SAP Online Help 20. Segments The IDoc for transferring confirmation is constructed as follows: ● /SCWM/WMTCID01 (as of SAP APO 3. Structure Message Type You define the partner agreement inbound for message type /SCWMWMTOCO. You use the CHARG field (report batch for bulk storage) in segment /SCWM/E2LTCCOI004. then you transfer the batch number of the products moved when you transfer the confirmation data.

2007 ALTME CHAR 3 Alternative unit of measure (AUoM) Difference quantity Sequential number of the HU data line within a WT item DMEGA PAPOS QUAN 31 NUMC 4 Segment definition /SCWM/E2LTCOH000: WT header (released as of SAP R/3 4.6A) Field LGNUM WHO QNAME SQUIT Data Type CHAR 4 CHAR 12 CHAR 12 CHAR 1 Description Warehouse number Warehouse order User name for the confirmation Indicator: Confirm entire warehouse task X If the entire warehouse task is to be confirmed. 3.SAP Online Help 20. and 5) Required Entry X Comments Segment definition /SCWM/E2LTCOI0004: WT items Field LBNUM SQUIT Data Type CHAR 12 CHAR 1 Description Warehouse task Indicator: Confirm without difference Destination actual quantity X If the item is to be confirmed without any differences If there are differences in the destination storage bin If there are differences in the destination storage bin If there is a zero stock check If quantity is entered If you want to post differences to certain interim record for differences In case of confirmation in bulk Required Entry Comments NISTA QUAN 31 X NDIFA QUAN 31 Destination difference quantity X KZNUL ALTME KZDIF CHAR 1 CHAR 3 CHAR 1 Indicator: Bin empty on zero stock check Unit of measure Differences indicator X X X LENUM CHAR 20 Handling unit number X SAP Extended Warehouse Management (SAP EWM) 510 468 .07. (Version 2.

SAP Online Help storage VQUIT CHAR 1 Confirmation in bulk storage area.07.2007 In case of confirmation in bulk storage If the destination storage bin differs from that suggested by the system NLPLA CHAR 18 PAPOS NUMC 4 Sequential number of the HU data line within a WT item Confirming a partial quantity for a WT item Report batch number for bulk storage area Only relevant for handling units (HUs) PARTI CHAR 1 CHARG CHAR 10 Segment definition /SCWM/E1LEXCP: (Exception during warehouse task confirmation) Field TANUM PAPOS Data Type NUMC 12 NUMC 4 Description Warehouse task Sequential number of the DB data line within a WT number Exception code Business context Execution step in business context Required Entry Comments EXCCODE BUSCON EXEC_STEP CHAR 4 CHAR 3 CHAR 2 Segment definition /SCWM/E1LEXCP: (Serial numbers for warehouse task confirmation) Field TANUM PAPOS Data Type NUMC 12 NUMC 4 Description Warehouse task Sequential number of the DB data line within a WT number Checkbox Serial number Required Entry Comments DIFF SERID CHAR 1 CHAR 30 SAP Extended Warehouse Management (SAP EWM) 510 469 . pick entire HU Destination storage bin X 20.

In this case. fill the following fields in IDoc /SCWM/WMCAID01: Segment /SCWM/E2LTCAH Field LGNUM WHO CANCL /SCWM/E2LTCAI LBNUM You can also cancel a warehouse task from the non-SAP system and send the cancellation to EWM. The non-SAP system then decides whether or not the movement has already been executed.2007 IDoc for Canceling Warehouse Tasks Definition Using IDoc /SCWM/WMCAID01. Structure Message type You define message type /SCWM/WMCATO for the inbound and outbound partner profile. the EWM can only send a cancellation request to the non-SAP system. or confirm execution of a cancellation movement to Extended Warehouse Management (EWM).07. even if EWM has not sent a cancellation request first. you make the necessary adjustments manually in the system. You can only cancel warehouse tasks (WTs) if they have not yet been confirmed.SAP Online Help 20. the external system confirms to EWM that the stock movement has already been completed and that cancellation is therefore no longer possible. In this case. SAP Extended Warehouse Management (SAP EWM) 510 470 . the user receives a corresponding message in EWM. For this reason. If the stock movement has already been executed. Use When physical stock movements are executed via the connected non-SAP system. You decide for each individual case what should happen with a WT item that cannot be cancelled. fill the following fields in IDoc /SCWM/WMCAID01: Segment /SCWM/E2LTCAH Field LGNUM WHO CANRQ /SCWM/E2LTCAI LBNUM Sending a Cancellation from the Non-SAP System to EWM To send a cancellation of a WT to EWM. EWM cannot determine whether the warehouse tasks (WTs) transferred to the non-SAP system have already been executed. you can send a cancellation request to an external system. Sending a Cancellation Request from EWM to the Non-SAP System To send a cancellation request from EWM.

2007 Segments IDoc /SCWM/WMCAID01 is made up of two segments: ● ● /SCWM/E2LTCAH (header data for the warehouse task) /SCWM/E2LTCAH (item data for the warehouse task) Segment definition /SCWM/E2LTCAH000 Field LGNUM WHO CNAME CANRQ Data Type CHAR 3 CHAR 12 CHAR 12 CHAR 1 Description Warehouse Number Warehouse order User name for WT cancellation Request cancellation warehouse task Response cancellation warehouse task X X for cancellation request X for cancellation from external system Required Entry X X Comments CANCL CHAR 1 X Segment definition /SCWM/E2LTCAI000 Field LBNUM VLENR NLENR SFEHL SFTXT Data Type CHAR 12 CHAR 20 CHAR 20 CHAR 1 CHAR 80 Description Warehouse task Source HU Destination HU Error during cancellation Error text for cancellation This text appears in the inbox for error messages Required Entry X X X Comments SAP Extended Warehouse Management (SAP EWM) 510 471 .07.SAP Online Help 20.

In this case. Segment definition /SCWM/E2LRRFX000 Field LGNUM WAVE DATUM UZEIT L2KSR LSKSO Data Type CHAR 3 CHAR 10 CHAR 8 CHAR 6 CHAR 1 CHAR 1 Description Warehouse Number Wave Date Time (clock-time) Relevance for two-step picking Two-step picking: Release approval level Required Entry Comments SAP Extended Warehouse Management (SAP EWM) 510 472 . You use the IDoc /SCWM/WMRRID01 to trigger the start of the stock movements for a certain wave by releasing the wave. you are not permitted to execute the goods movement immediately after the non-SAP system receives the warehouse task data.2007 IDoc for Releasing Waves Definition The IDoc /SCWM/WMRRID01 is used to release transfer orders for a wave pick that have already been sent to a non-SAP system. Features You group together the warehouse tasks into a wave so that you can execute the goods movements for these WTs in one step. Structure Message type You define the partner agreement outbound for message type /SCWM/WMRREF. Segments The IDoc is made up of segment /SCWM/E1LRRFX.07. Use Prerequisites You have transferred the wave number to the non-SAP system using IDoc /SCWM/WMTOID01 in segment /SCWM/E1LTORH for the WTs that have been grouped together into waves. The system sends the group number to the header data of the warehouse task to be created. For example. processing warehouse tasks for a certain shipping point or removing stock in the same interim storage type.SAP Online Help 20.

Use When. Segments IDoc /SCWM/WMBIID01 is made up of the following segments: ● /SCWM/E1LBINH (blocking storage bins IDoc header) You determine whether blocking or unblocking storage bins is involved. set the BLOCK indicator. To block storage bins. you block these storage bins in EWM so that they are not considered during storage bin determination. The non-SAP system initializes the block on the storage bins via IDoc /SCWM/WMBIID01. the external system triggers the unblocking of the non-SAP system by EWM via IDoc /SCWM/WMBIID01. you can send individual storage bin data or comprehensive storage bin data (for example all of the storage bins in one aisle) for blocking or unblocking from the non-SAP system to Extended Warehouse Management (EWM). As soon as the storage bins are available again. To unblock storage bins. Structure Message type You define the partner agreement inbound for message type /SCWM/WMBBIN. set the DEBLO indicator. Segment definition /SCWM/E2LBINH000 Field LGNUM LGTYP BLOCK DEBLO Data Type CHAR 4 CHAR 4 CHAR 1 CHAR 1 Description Warehouse Number Storage type Blocking storage bins Unblocking storage bins Required Entry X X X X Either BLOCK or DEBLO Either BLOCK or DEBLO Comments Segment definition /SCWM/E2LBINI000 Field LGPLA Data Type CHAR 18 Description Storage Bin Required Entry X Comments Entry also generic. for example.2007 IDoc for Blocking Storage Bins Definition Using IDoc /SCWM/WMBIID01. ● /SCWM/E1LBINI (blocking storage bins IDoc items) To block certain storage bins individually.07.SAP Online Help 20. transfer a /SCWM/E1LBINI segment for each storage bin. certain storage bins or aisles are inaccessible for the external system due to technical problems. for example 01 SAP Extended Warehouse Management (SAP EWM) 510 473 .

SAP Extended Warehouse Management (SAP EWM) 510 474 . For example. To block a range of storage bins. enter 01* to block all storage bins. use *.2007 SKZUA CHAR 1 Block indicator: For stock removal Block indicator: For putaway Blocking indicator: Current inventory Blocking reason x At least one of the three indicators At least one of the three indicators At least one of the three indicators SKZUE CHAR 1 x SKZSI CHAR 1 x SPGRU CHAR 1 Set at least one of the three indicators.SAP Online Help 20.07. which begin with 01.

and prints the pallet slip.SAP Online Help 20.2007 IDoc for Stock Movement with HUs Definition You use the IDoc /SCWM/WMSUID01 to report movements of handling units (HUs). 1. If the EWM has priority. . then instead of IDoc /SCWM/WMSUID01. the function module reads the relevant destination storage bin and reports it to EWM. This means that you can prevent accidental duplicate postings in EWM. The non-SAP system must report the movement performed for the HU to EWM. for example. from the non-SAP system to Extended Warehouse Management (EWM). The data for the HU is known in EWM. If the HU has already been put away from the ID point. Putaway Using an Identification Point (ID Point) If you put the HU away using an ID point. EWM reports the warehouse task for putaway at the ID point to the non-SAP system. 4.. you can call the function module /SCWM/_TO_CREATE_MOVE_SU synchronously in EWM. EWM subsequently posts the reported HU movement in the system. then the non-SAP system reports the stock movement data to EWM. then EWM reports the destination storage bin for the pallet to the non-SAP system. stock transfers. 3. or if the non-SAP system specifies that this HU should be put away in a final storage bin in the high rack storage area.07. which you want to move in the non-SAP system. a.. Structure Message type You define the partner agreement inbound for message type /SCWMWMSUMO. During putaway of pallet. b. 2. Use Prerequisites You have constructed the HU in EWM. or specifies the destination storage bin for the pallet in the high rack storage area. In certain cases it is necessary to trigger a stock transfer of HUs in the non-SAP system. The non-SAP system calls function module /SCWM/TO_CREATE_MOVE_SU synchronously. The non-SAP system identifies the pallet and performs a check of the pallet outline. Segments The IDoc consists of the segment /SCWM/E1LSUMX with the following fields: SAP Extended Warehouse Management (SAP EWM) 510 475 . then the non-SAP system transmits the destination storage bin in the high rack storage area to EWM. it can also be useful if the non-SAP system assigned the final storage bin of the product in the high rack storage area. The non-SAP system changes the HU type of the pallet according to the results of the outline check. Features If you trigger a stock transfer of HUs in the non-SAP system. If the non-SAP system has priority and is waiting for a successful posting of the destination storage bin in EWM.

SAP Online Help 20. NLTYP NLBER NLPLA NLENR CHAR 3 CHAR 3 CHAR 10 CHAR 20 Destination storage type Destination storage section Destination storage bin Destination HU SAP Extended Warehouse Management (SAP EWM) 510 476 .07.2007 Segment definition /SCWM/E2LSUMX001 (Move Handling Unit IDoc Segment) Field LGNUM LENUM PROCTY LETYP Data Type CHAR 3 CHAR 20 CHAR 4 CHAR 4 Name Warehouse Number Handling unit Warehouse process type HU Type Required Entry X X X You do not always need to transmit this field. Comments BNAME KZQUI CHAR 12 CHAR 1 User name Indicator: confirmation required You do not set this field. since the transmitted stock movement has already been performed and is therefore no longer subject to confirmation.

the user can analyze the error and post the document subsequently. SAP Extended Warehouse Management (SAP EWM) 510 477 . see Processing Technical IDoc Errors [Seite 478]. For more information. Technical Errors If errors occur in the ALE service layer during sending or receiving of IDocs. The system sends this message to all responsible users. see Processing Logical IDoc Errors in EWM [Seite 481]. Based on return codes in the RFC function used. the connection between the sending system and the receiving system is interrupted. If there are TCP/IP errors. then there is a logical error. If an error occurs during processing of an IDoc in the application system (EWM). Logical Errors The system saves a received IDoc in the database before the IDoc has actually been processed.07.SAP Online Help 20. EWM creates a workflow work item for each incorrect IDoc. In this case. Extended Warehouse Management (EWM) sends a workflow work item for each incorrect IDoc in the form of an error message. Based on the error message.2007 IDoc Error Processing TCP/IP Errors The basis for IDoc transmission between systems is TCP/IP. you can see in the sending system whether an RFC call has worked. The system breaks off communication with the external system before the transferred data is then processed. For more information. break the connection and send the IDoc again. If an error occurs during the transfer. then there is a technical error. If a technical error occurs.

the system triggers a workflow work item for the standard task Output: Error processing with IDoc and sends a message to the inbox of the corresponding user. The following errors can occur: ● ● ● ● Syntax error in the IDoc Missing partner profile The system did not transmit the IDoc to an asynchronous Remote Function Call at sending The system did not transmit the IDoc to an application at receipt Error During Outbound IDoc Processing IDoc status 07: Syntax error in IDoc On sending and receiving IDocs. proceed as follows: ● ● Define the missing partner profile. SAP Extended Warehouse Management (SAP EWM) 510 478 . errors can occur in the ALE layer. For this error. You correct the IDoc structure in the SAP system and send the IDoc again. the connected partner system) for sending the IDocs.07. on the SAP Easy Access screen. you must have defined the outbound section of the partner agreement for the message type and all relevant partners. to which the system adds the data from the partner agreement and transmits to the asynchronous RFC. During this subsequent sending. You activate the syntax check via the partner profile for one IDoc type and one particular partner. You retrigger sending of all pending IDocs that you could not send before. and copies the IDoc into a new IDoc. the system checks the syntax of the individual IDocs. the system flags the incorrect IDoc with the status 31. To do this. This syntax can include: ● ● ● The individual segments of an IDoc type The relationship between the individual segments How many segments you can send in an IDoc Incorrect syntax in IDocs often occurs during tests only. choose Tools → ALE → ALE Administration → Runtime Settings → Partner Agreement. IDocs with incorrect syntax cannot be repaired. choose Tools → ALE → ALE Administration → Runtime Settings → Partner Agreement. We recommend only switching on the syntax check during testing of IDocs created yourself.2007 Processing Technical IDoc Errors Use During communication between the non-SAP system and Extended Warehouse Management (EWM). You trigger subsequent sending of the IDocs that contained errors from the inbox.SAP Online Help 20. If the system cannot find the partner (that is. IDoc status 29: Missing or incorrect partner agreement When you send IDocs from the SAP system to the non-SAP system. on the SAP Easy Access screen. The IDoc definition specifies the syntax of the IDoc. To do this.

2007 Errors in partner profiles only occur in the test run. choose Tools → ALE → ALE Administration → Runtime Settings → Partner Agreement. You retrigger receiving of all pending IDocs that you could not process before. the system checks the syntax of the individual IDocs. For this error.SAP Online Help 20. you trigger the subsequent transmission of the IDocs which contained errors. the system cannot transmit the IDoc to the asynchronous RFC. the system triggers a workflow work item for the standard task Input: Error processing with IDoc and sends a message to the inbox of the corresponding user. or schedule a regular background job for the report. ● ● Outbound processing mode 2: The system sends the IDoc immediately Outbound processing mode 4: The system collects IDocs that have been created and sends them in packets of a predefined size. Choose Tools → Business Communication → IDoc Basis → Test → Outbound from IDoc. To do this. You correct the IDoc structure in the SAP system and send the IDoc again. IDocs with incorrect syntax cannot be repaired. and there is no official entry in the RFC valuation (/nSM58) for the relevant subsystem. on the SAP Easy Access screen. SAP Extended Warehouse Management (SAP EWM) 510 479 . you must have defined the inbound section of the partner agreement for the message type and all relevant partners. This syntax can include: ● ● ● The individual segments of an IDoc type The relationship between the individual segments How many segments you can send in an IDoc Incorrect syntax in IDocs only occurs during tests. IDocs are not intended to be sent directly. If the system cannot find the partner (that is. We recommend that you activate the syntax check for all IDocs you create yourself. Error During Inbound IDoc Processing IDoc status 60: Syntax error in IDoc On sending and receiving IDocs. From the inbox. the connected partner system) for receiving the IDocs. Check the outbound processing mode for the IDoc in the partner profile. proceed as follows: ● ● Define the missing partner profile. You activate the syntax check via the partner profile for one IDoc type and one particular partner. The IDoc definition specifies the syntax of the IDoc. IDoc status 63: Missing or incorrect partner profile When you send IDocs in the SAP system from the non-SAP system. IDoc status 30: System does not transmit IDoc to asynchronous RFC Although you have defined the partner agreement and the system has constructed the IDoc.07. to manually start the report. Status 30 in the IDoc can only occur if outbound mode is set to 4. The system cannot send the IDoc. You trigger transmission of the IDoc using report RSEOUT00.

IDocs are not intended to be transmitted directly to the application.SAP Online Help Errors in partner profiles only occur in the test run. plan a regular job in background processing for this report. Status 64 in the IDoc can only occur in conjunction with processing mode 3 and output mode 2.2007 IDoc status 64: System does not transmit IDoc to the application Although you have defined the partner agreement and the system has constructed the IDoc.07. You trigger transmission of the IDoc using report RBDAPP01. Check the processing mode for the IDoc in the partner profile: ● ● Processing mode 1: The system transmits the IDoc immediately after receipt in the application Output mode 3: The system collects received IDocs. To do this. SAP Extended Warehouse Management (SAP EWM) 510 480 . the system cannot transmit the IDoc to the application. 20.

Only correct the IDoc using the IDoc editor in exceptional cases. ● You make the corrections to the IDoc using the IDoc editor. You subsequently post the incorrect IDoc Either from the inbox of the assigned user Or via report RBDMANIN. which you schedule periodically in background processing. or whether a correction in the SAP system is useful and possible. However. you transmit a stock movement with a warehouse process type from the non-SAP system. because EWM responds to missing or incorrect Customizing settings beforehand. You correct the relevant Customizing settings. which is unknown in the SAP system. the warehouse process type in EWM does not permit immediate confirmation for this stock movement.. Missing or Incorrect IDoc Data If the data in the received IDoc is not complete.SAP Online Help 20. SAP Extended Warehouse Management (SAP EWM) 510 481 . Along with the IDoc. ● The received IDoc data does not match the Customizing settings in the SAP system. Procedure .2007 Processing Logical IDoc Errors in EWM Use If you receive an IDoc from the non-SAP system in the SAP system. 1. ● You can subsequently post IDocs of the type WMIVID01 on reporting physical inventory data and correct the data in the relevant transaction..07. the following errors can occur in Extended Warehouse Management (EWM): ● ● ● Missing or incorrect Customizing settings in EWM Missing or incorrect data in the IDoc Error Due to Blocked Objects Logical IDoc errors do not occur in IDoc outbound from the SAP system. The system flags the incorrect IDocs with status 51. The stock movement reported by the external system is defined for immediate confirmation. you decide whether the system should resend the incorrect IDoc. 2. Missing or Incorrect Customizing Settings Cause The SAP system cannot further process the received IDoc in the following circumstances: ● You have not defined certain data for the IDoc in the SAP system.

but rather complete the workflow work item.07. Schedule report RBDMANIN for periodical background processing. If the system can no longer confirm a warehouse task or handling unit because the confirmation has already been made. Workflow work items are also suitable for important notes ● ● ● ● Which the external system sends to the SAP system Which occur during IDoc processing in EWM. the system creates a workflow work item in the inbox of the person responsible.SAP Online Help 20. IDoc processing leads to an error.2007 Procedure You subsequently post the incorrect IDoc ● ● Either from the inbox of the assigned user Or via report RBDMANIN. Ensure that the system stores this information. the system terminates processing. since the confirmation can only be made by the non-SAP system. If there are concurrent attempts (by different users) to access the same SAP object. You can use the Error Status parameter in the report to specify that the system automatically reposts IDocs with the error message describing a lock error. see Rule Resolution in Exception Handling [Extern]. You do not process workflow work items for notes from the inbox as you do for errors. For more information. Important Error Notes in Inbox For the errors listed above. with an error note for the blocked object. These workflow work items Inform the user about a problem or a conflict situation Send on important messages from the external system to the SAP system. Error Due to Blocked Objects If blocking problems occur in the SAP system. the non-SAP system triggers an internal message. which you schedule periodically in background processing. SAP Extended Warehouse Management (SAP EWM) 510 482 . Procedure You do not need to intervene manually. The external system transmits the messages via message type WMINFO.

07.2007 Modification Options Use The interface between Extended Warehouse Management (EWM) and non-SAP systems (EWM-WCU interface) offers the following options for configuring processing at the interface according to each customer’s requirements: Modification Concepts: IDoc Inbound Processing [Seite 484] Modification Concepts: IDoc Outbound Processing [Seite 487] At this point you can also access multiple BAdI Methods for the Interface [Seite 489] .SAP Online Help 20. so that you can adapt and enhance the interface processing to meet your requirements. SAP Extended Warehouse Management (SAP EWM) 510 483 .

which you copy from the standard function module for the respective message type and adjust accordingly. In the standard IDoc. ● You use the standard IDoc but want to adjust the standard IDoc processing. you implement the BAdI /SCWM/WMIDOC with the method Error_Inbound. you can use the standard auxiliary function modules. You define customized IDoc segments in the standard IDoc and create a customized processing function module.SAP Online Help 20. SAP Extended Warehouse Management (SAP EWM) 510 484 . You define a user-defined IDoc and create a user-defined processing function module. You create a user-defined processing module. ● You use a modified IDoc with customized segments and want to define IDoc processing yourself. If you want to influence IDoc processing.07. You implement the Business Add-In (BAdI) in the standard function module: ○ ○ If you want to influence error processing. When you create the function module. see BAdI Methods for the Interface [Seite 489]. Features Adjusting the Standard Function Module As soon as the SAP system has received the IDoc and saved it. which takes over the processing of the IDoc. That is to say. you define your own IDoc segments and use the BAdI /SCWM/WMIDOC with the method Error_Inbound to process the data from your own segments. ● You use a user-defined IDoc with a new message type and have to implement processing of the IDoc on your own. you want to modify error processing or want to interpret the contents of the IDocs to suit your individual needs.2007 Modification Concepts: IDoc Inbound Processing Use The following modification scenarios are available: ● You use the standard IDoc but want to define the processing yourself. the system calls a main function module of the application. you implement the BAdI /SCWM/WMIDOC with the following methods: ■ ■ ■ ■ ■ WMTORD_INBOUND WMTOCO_INBOUND WMCATO_INBOUND WMSUMO_INBOUND WMBBIN_INBOUND For more information about the BAdI methods. ● You use a modified IDoc with user-defined segments and want to execute a particular process for the data from these segments.

You can use the BAdI method before the function module call. you can also enter an additional partner profile for a certain message variant or message function from the external system to differentiate processing in the SAP system. you have the first opportunity to intervene in the IDoc processing. to perform your own updates or to evaluate your own segments (that you have added in the IDoc definition). Defining User-Defined IDoc Segments You define your own IDoc segments from the SAP Easy Access screen. For more information. by choosing Tools → ALE → ALE Development → IDoc → IDoc Type Development → IDoc Types. as these can cause errors during IDoc processing and inconsistencies during error processing. Note that additional I/Os in the BAdIs can reduce performance. Main function modules for inbound IDoc processing Message type /SCWM/WMBBIN /SCWM/WMCATO /SCWM/WMSUMO /SCWM/WMTOCO /SCWM/WMTORD Function module /SCWM/IDOC_INPUT_WMBBIN /SCWM/IDOC_INPUT_WMCATO /SCWM/IDOC_INPUT_WMSUMO /SCWM/IDOC_INPUT_WMTOCO /SCWM/IDOC_INPUT_WMTORD_MULTIPLE Use Block storage bins Cancel TW Move Handling Unit Confirm TW Warehouse tasks (WT) The main function module filters out the data for each IDoc and calls the actual processing function module of the application in a loop. There. The system returns to the ALE layer following processing. Creating User-Defined Processing Function Modules The SAP system offers function modules for general use for the following tasks for using user-defined main function modules: Auxiliary function modules for inbound IDoc processing Function module Task SAP Extended Warehouse Management (SAP EWM) 510 485 . for example. Implementation of BAdIs A BAdI method is implemented both before and after each call of the function module: ● ● You can use the BAdI method after the function module call to update your own error status or to change the error status already set. and may even execute database rollbacks. make sure that you do not set any COMMIT WORK statements.07. You can find the name of the BAdI method in the source code for the main function module. where the system updates any application errors that have occured. You enter this function module from the SAP Easy Access screen under Tools → ALE → ALE Development → IDoc → Inbound Processing → Function Module → Assign IDoc Type and Message Type. see Segment Editor [Extern].SAP Online Help 20. by creating a user-defined function module. sets the IDoc status.2007 At this point. If you create your own function module or BAdIs.

07. You create a partner profile for this message type.2007 /SCWM/IDOC_CREATED_OBJECTS_SAVE /SCWM/IDOC_ERROR_SAVE /SCWM/IDOC_INPUT_REFRESH /SCWM/IDOC_OK_SAVE /SCWM/IDOC_RETURN_CREATE /SCWM/IDOC_ROLLBACK_SAVE /SCWM/IDOC_STATUS_CREATE /SCWM/IDOC_TIDOC_FETCH Continuously save the documents created from an IDoc Continuously save IDocs with errors Initialization for IDoc processing (table refresh) Continuously save processed IDocs Determine and construct status record for the IDoc Update IDoc tables after necessary rollback Determine and construct status record for the IDoc Fetch internal table for the purpose of status update Defining User-Defined IDocs If you define your own IDocs (intermediate structure). Standard task TS00008099 is available for error processing. For more information. To do this. SAP Extended Warehouse Management (SAP EWM) 510 486 .SAP Online Help 20. choose Tools → ALE → ALE Development → IDoc IDoc Type Development → IDoc Types. you assign this IDoc to a new message type. You define the tables for inbound processing for this IDoc under Tools → ALE → ALE Development → IDoc → Inbound Processing. on the SAP Easy Access screen. see Defining New IDoc Types [Extern].

you define your own IDoc segments and realize your own connection for the interface between EWM and the non-SAP system. You create a user-defined processing module. ● You use a modified IDoc with user-defined segments and do not want to use the standard flow of the interface. In this case. which you copy from the standard function module for the respective message type and adjust accordingly. You activate the user-exit in the standard function module to influence the standard IDoc construction. you have the first opportunity to intervene in the IDoc processing. ● You use the standard IDoc. You realize your own connection for the interface between Extended Warehouse Management (EWM) and the non-SAP system.07. and steers towards the ALE layer for further processing. Standard auxiliary function modules are available for this purpose. you do not use the standard flow of the interface.2007 Modification Concepts: IDoc Outbound Processing Use The following modification scenarios are available: ● You use the standard IDoc but want to influence the construction of the IDoc. At this point. SAP Extended Warehouse Management (SAP EWM) 510 487 . In the standard IDoc. ● You use a modified IDoc with a new message type and do not want to use the standard flow of the interface. you define your own IDoc segments and use the BAdI method to enter data into your own segments. ● You use an individually defined IDoc with a new message type and have to implement IDoc construction yourself. by creating a user-defined function module. which you copy from the standard function module of the relevant message type and adjust accordingly. You define your own IDoc segments in the standard IDoc and create your own processing function module.SAP Online Help 20. determines the partner (the connected system). You define your own IDoc. Features Adjusting the Standard Function Module EWM prepares sending the IDoc to the non-SAP system. The system constructs the IDoc in the relevant application function module. ● You use a modified IDoc with user-defined segments and you want to trigger userdefined processing to construct the data in the segments. In the standard IDoc. ● You use a modified IDoc with user-defined segments and want to implement IDoc construction yourself. You define an individual IDoc and create an individually defined function module. and realize your own connection for the interface between EWM and the non-SAP system. but want to specify when and to whom the system should send a warehouse task item.

see Segment Editor [Extern]. or to influence the structure of the standard IDoc. For more information. choose Tools → ALE → ALE Development → IDoc IDoc Type Development → IDoc Types. Defining User-Defined IDoc Segments You define your own IDoc segments from the SAP Easy Access screen. In this case. the interface must not be active in EWM. you assign this IDoc to a new message type. You use the BAdI method BAdI. see Defining New IDoc Types [Extern]. You create a partner profile for this message type. WT Confirmation.07. Defining User-Defined IDocs If you define your own IDocs (intermediate structure).2007 You enter this function module in Customizing for Extended Warehouse Management under Interfaces → Non-SAP Systems → Connect Subsystem. Realizing an individually defined interface connection You realize your own interface connection to decide for yourself when communication should take place to the non-SAP system. on the SAP Easy Access screen. you can use BAdI methods to add your own IDoc segments. EWM uses the following function modules to construct and send IDocs: Function modules for outbound IDoc processing Function module /SCWM/IDOC_CREATE_WMTOID01 /SCWM/IDOC_CREATE_WMRRID01 /SCWM/IDOC_CREATE_WMCAID01 Name Warehouse tasks Group release Cancellation request WT In the function modules. and to which non-SAP system you want to send the data. to realize your own connection between the systems.SAP Online Help 20. by choosing Tools → ALE → ALE Development → IDoc → IDoc Type Development → IDoc Types. To do this. For more information. SAP Extended Warehouse Management (SAP EWM) 510 488 .

/SCWM/WMBBIN.2007 BAdI Methods for the Interface Extended Warehouse Management (EWM) contains the following available BAdI methods: Enhancements to the EWM-WCU interface using BAdI /SCWM/WMIDOC Method ERROR_INBOUND Name Error processing in Idoc inbound for IDocs: /SCWM/WMTOCO. and /SCWM/WMSUMO jointly Message /SCWM/WMTOCO (confirm warehouse task) inbound Message /SCWM/WMCATO (cancel warehouse task) inbound Message /SCWM/WMBBIN (block storage bin) inbound Message /SCWM/WMSUMO (move handling unit) inbound IDoc /SCWM/WMTOID01 (warehouse task) outbound IDoc /SCWM/WMCAID01 (cancellation request for warehouse task) outbound IDoc /SCWM/WMRRID1 (release wave) outbound Message /SCWM/WMTORD (create warehouse task) inbound WMTOCO_INBOUND WMCATO_INBOUND WMBBIN_INBOUND WMSUMO_INBOUND WMTORD_OUTBOUND WMCATO_OUTBOUND WMREF_OUTBOUND WMTORD_INBOUND SAP Extended Warehouse Management (SAP EWM) 510 489 . /SCWM/WMCATO.07.SAP Online Help 20.

A handling unit is always a combination of products and packaging materials [Seite 492]. for example. and you can create a new handling unit from several other handling units. is retained in the handling units and is always available. 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. scannable identification number that you can construct according to industry standards such as EAN 128 or SSCC.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. 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.07. about batches. A handling unit has a unique. Handling units can be nested. All the information contained in the product 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 490 .SAP Online Help 20.

loaded. For more information about this overview. which are displayed in an overview. weighed. blocked. or posted for GI) for a handling unit.2007 For more information about the different detailed information. you can store a user schema for the packaging material type. or other handling units.SAP Online Help 20. Handling Unit Item The items of a handling unit can consist of products. see Packing at the Work Center [Seite 506]. Status The handling unit is connected to general status management.07. auxiliary packaging materials. SAP Extended Warehouse Management (SAP EWM) 510 491 . see Packing at the Work Center [Seite 506]. This enables you to document the various physical statuses (such as planned or realized) and other attributes (such as. If you want to use your own status.

Box Wire box Pallet Cont ainer Crat e Truck Use For each packaging material that you want to use. Structure If you choose the Global Data view in the product master record. for example.2007 Packaging Materials Definition Packaging materials are used to enclose or hold together the packaged goods. boxes. for example. and the gross weight and volume become the tare weight and/or tare volume of the handling unit. To do this. this is the tare weight of the unloaded container (the total weight of the container minus any goods and packaging materials packed into it). containers. choose Extended Warehouse Management → Master Data → Product → Maintain Product): Section Basic Data: Packing: ● ● Packing group Reference product for similarly packable products SAP Extended Warehouse Management (SAP EWM) 510 492 . The packaging material can be a load carrier. If you create a handling unit. In the case of a container. The gross weight and the volume that you enter in the product master are particularly important for packing. you must maintain product master data. the master data for the packaging material is automatically adopted.SAP Online Help 20. wire baskets. crates. The tare weight and tare volume refer to the gross weight and volume of the packaging material. you can maintain the following data in the Packing Data screen section (you access product maintenance from the SAP menu.07. You can pack the packaged goods into or onto the packaging material. and pallets. The most important packaging materials are.

07. Integration Packaging materials are a special type of product that can be used for packing or transporting goods.2007 Standard HU type Section Basic Data: Packaging Material: ● ● Packaging material type Handling unit type Section Capacities ● ● ● ● ● ● ● ● ● ● ● ● Maximum allowed weight Excess weight tolerance for the handling unit Tare weight variable Maximum allowed volume Excess volume tolerance for the handling unit Packaging material is closed packaging Maximum level (by volume) Maximum allowed capacity for the packaging material Excess capacity tolerance for the handling unit Maximum packing length of a packaging material Maximum allowed packing width for the packaging material Maximum packing height of a packaging material You can find exact details about the function of the individual fields in the field help. During packing. you must always enter a packaging material so that the system can create a handling unit [Seite 490] . SAP Extended Warehouse Management (SAP EWM) 510 493 .SAP Online Help ● 20.

The packaging specification defines all the necessary packing levels for a product in order. In this way you can. give the employee exact instructions as to where to place the label on a box. Pack. Use ● In printed form. a packaging specification is a set of instructions for the employee in the warehouse. mat.SAP Online Help 20. Work step Work step Work step Level n EG n Element 1 Pack. for example. Work step ● Header Attributes such as the name of the packaging specification. to put away or transport the product. mat. ● Structure Header Product Contents OR or Packaging specification Level 1 EG 1 Element 1 Element 2 Level 2 EG 2 Element 1 Pack. status. the work steps that you enter in a packaging specification are intended as information for the employee.07. SAP Extended Warehouse Management (SAP EWM) 510 494 . Processes that determine packaging specifications use only parts or specific attributes from the packaging specification. for example.2007 Packaging Specification Definition A packaging specification is master data. The system can determine packaging specifications during various processes (see below). For a product. Pack. More specifically. mat. or how a product should be stacked onto a pallet. user name of the creation user. mat. and so on. a packaging specification mainly describes in which quantities you can pack the product into which packaging materials in which sequence.

some packaging specifications contain more than one product. Status: New Contents: product A. Step A text with an identification.SAP Online Help ● 20. work step ‘Place 1 piece upright in each box’ Element E2: additional packaging material ‘Label’. ● Level You can map various packing levels in a packaging specification. Each level contains a target quantity. ● ● Elements Elements consist of a packaging material and/or a work step. ● Packaging material A product that is defined with a packaging material type in the product master. element group EG1 Element group EG1: ● ● Element E1: packaging material ‘Small box’. ● Element group For each level there is exactly one element group. element group EG2 Element group EG2: ● Element E3: packaging material ‘Pallet’. or refer to other packaging specifications. However. which you can use in one or more packaging specifications. However. work step ‘Place label on upper left’ Level 2: Target quantity 50. 1 piece Level 1: Target quantity one.07. shift quantity 10. which defines how many times you can pack the previous level into this level. and using which components: SAP Extended Warehouse Management (SAP EWM) 510 495 . work step ‘Place boxes layer by layer onto pallet’ Integration The following figure shows which processes use the packaging specification. Example for a Packaging Specification and Its Structure: Header: Name: PS1.2007 Contents A packaging specification contains a product. you can reuse element groups in several packaging specifications.

delivery/ASN Putaway-WT Stock-removal-WT Slotting Palletization Whse-int. Functions of the Packaging Specification The following functions are possible for packaging specifications: ● ● ● Create. you put away product A onto pallets for 50 pieces.SAP Online Help 20. For example. the system splits the quantity in the inbound delivery across multiple warehouse tasks. due to this packaging specification. SAP Extended Warehouse Management (SAP EWM) 510 496 .07. For this level. technique In both the Inventory Collaboration Hub (ICH) and in Extended Warehouse Management (EWM). enter the target quantity 50. Example Palletization data in EWM In your warehouse.2007 Processes for the Packaging Specification Inb. copy. Create a packaging specification with a level that contains the main packaging material Pallet and the contents Product A. if a quantity of 100 pieces is delivered. 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. processes Pick-HU proposal ATP sourcing MM deployment Automatic packing Warehouse order Rounding rules ICH EWM APO Packaging Specification iPPE Cond. and activate (see also: Creation of Packaging Specifications [Seite 497]) Determine (see also: Packaging Specification Determination [Seite 499]) in mehrere Systeme verteilen. then the system creates two warehouse tasks for 50 pieces. In the process ‘Putaway’ for the inbound delivery.

When you create a packaging specification that describes the packing for a product.. you can first edit the header attributes for packaging specification. you can enter a description or define the business key for the packaging specification (Determination tab page). ). If you work without level sets. On the detail screen. the element. then choose Change to access the detail screen.. On the SAP Easy Access screen. and display functions on the detail screen. 7. From the list. change.07. 1. This displays the structure of the packaging specification in the left screen area (in other words. The overview screen appears. or the contents). To create a new packaging specification. Activities . see the Implementation Guide (IMG) for SCM Basis under Packing → Packaging Specification. Features When you access the Maintain Packaging Specification transaction. you enter the product in the Contents area. for the level. 2. you can go to the create. You can define the structure of a packaging specification in Customizing (see also the IMG for SCM Basis under Packing → Packaging Specification → Maintain Structure of Packaging Specification → Define Level Set). choose Extended Warehouse Management → Master Data → Packaging Specification → Maintain Packaging Specification. select a packaging specification. The lower screen is a list in which you create new packaging specifications. The lower right screen area shows the detail data for the selected subobject of the packaging specification (in other words. Here you can access existing packaging specifications using the quick search or the advanced search. the overview screen appears first. For more information. This is divided into two parts: the upper screen is used to search for existing packaging specifications. and can display or change existing packaging specifications. 6.2007 Creation of Packaging Specifications Use You create a packaging specification to map in the system how you should pack a product. Prerequisites You have made the following settings in Customizing: ● ● ● Define a Number Range for the Packaging Specification Define General Packing Parameters Define Group for Packaging Specification SAP also recommends that you make the (optional) settings under Maintain Structure of the Packaging Specification and Determination of Packaging Specifications. You create levels and contents in the left screen area using the context menu (right mouse button). 5. for example. SAP Extended Warehouse Management (SAP EWM) 510 497 . then you should specify the structure of the specification in the packaging specification. Select the packaging specification. In the PS Group column.SAP Online Help 20. The upper right screen area shows the most important header data for the packaging specification. 8. the levels. 3. elements. and the contents). choose Add New Line (symbol 4.

For a level. Choose HU Check to make the system calculate the attributes Loading and Total Weight (and/or Volume. Target quantity 10 for level 2 means. the system adopts the attributes for tare and maximum weight (and/or volume. create an element with HU relevance Main Packaging Material. 10 boxes onto one pallet. 16. 10. you can activate one or more packaging specifications. New Version. 13. you close a packaging specification in the detail area. In other words. Print Preview. and enter the packaging material in the relevant field. and Delete. where required. you enter a target quantity and.07.SAP Online Help 20. for example. For this. In the overview area. that you should pack level 1 ten times into the main packaging material for level 2. and/or Capacity). If the packaging specification contains all the data and you can use the packaging specification for the process. 12. The prerequisite for being able to determine the packaging specification in other processes is activation of the packaging specification (see also: Packaging Specification Determination [Seite 499]). then you activate the packaging specification. for example. The attributes Weight. the minimum and layer quantity. The overview area also offers you the functions Copy. 14. Volume. and Dimensions (tab page) for the level are automatically determined by the system for the first main packaging material for a level. 11. When you save. For a level. and/or capacity) and the dimensions from the product master for the packaging material. Note that these quantities refer to the previous levels. 15. you can either create the elements manually. To specify the main packaging material for a level. or if you are working with a level set then the elements are proposed by the system. SAP Extended Warehouse Management (SAP EWM) 510 498 . Choose Back (F3) to go back to the overview area.2007 9.

You can define different condition types for different processes. you select those that are suitable for your processes (for example. In the SAP standard system. the system finds packaging specification PS. handling units are created on the basis of the packaging specification found. specified. SAP Extended Warehouse Management (SAP EWM) 510 499 . determination of the operative unit of measure) In Service Parts Planning (SPP): ● ● ATP sourcing rounding rules MM deployment rounding rules Prerequisites ● ● You have made the Customizing settings for packaging specification determination. you can make enhancements in the customer namespace.2007 Packaging Specification Determination Use You can use this function to determine a packaging specification using the business characteristics you have defined. After you have specified a condition type. Customizing settings for packaging specification determination have been predefined. For packaging specification determination. product and vendor). specify that for a product P. you require the following: ○ ○ ○ ○ ● Condition table Access sequence Condition type Determination procedure You have created. and process Automatic Packing in the Inbound Delivery. At the end of this process. for example. However. Integration The following processes use packaging specification determination: In Extended Warehouse Management (EWM): ● ● ● ● ● ● Automatic packing in the inbound delivery Packaging material determination during warehouse order creation Packaging material determination in the outbound delivery Packaging material determination during deconsolidation Slotting Internal warehouse processes (such as determination of palletization data. you can assign a packaging specification to these business characteristics. vendor A. A set of business characteristics forms a condition type. and activated determination records for a packaging specification.SAP Online Help 20.07. From the business characteristics predefined by SAP. This means that you can. The system uses the condition technique to do this.

without reference to specific packaging specifications. 7. SAP Extended Warehouse Management (SAP EWM) 510 500 . Depending on the condition table/key combination you selected. Choose Extended Warehouse Management → Master Data → Packaging Specification → Maintain Packaging Specification. Packaging specification determination runs using the same principles. If. This screen always displays all condition records that you have created for the packaging specification. then any condition record that is also displayed has the same key combination as the newly created record. 8. a yellow traffic light is displayed in the packaging specification overview.07. and the system takes this packaging specification into account during packaging specification determination. this results in an overlap of two condition records. Here you can also see an overview of all condition records. Save your condition record. The Packaging Specification Overview screen appears. Check whether there is an overlap of the two keys. You can use the Condition Maintenance transaction for activated packaging specifications. If the semantic key (in other words. you selected the key combination supply chain unit/product. then you activate the packaging specification.SAP Online Help 20. If at least one condition record for the active packaging specification contains an error (in other words. If there is an active version of the packaging specification. to change the sequence of the determination. 5. On the determination tab page (Details for PS Header).2007 Features For more information about condition technique. for example. 4. You can configure these combinations as you want using Customizing. and choose Change (if you have already activated the selected packaging specification. will not be included in the determination). or if no condition record exists for this packaging specification. make the mandatory entries (the current packaging specification number is entered automatically in the column). If the system shows you condition records for other packaging specifications. Choose a packaging specification that already exists.. 6. or create a new specification. perform this activity). to add new condition records. enter a condition type or use the proposed condition type (see Customizing Define Level Set). and the condition sequence) are the same within a validity period. Choose one of the proposed condition tables for which you want to create a condition record (If you have used the access sequence to assign more than one condition table to the condition type. 2.. then the subsequent mandatory entries are the supply chain unit and the product. 1. you must first create a new version of this packaging specification). or to change/delete existing records. If there are no active packaging specifications. Activities The following describes how to create determination records in the system: . If necessary. Choose OK. then you can activate a packaging specification. all fields of the condition table. 3. change the sequence number of the condition record. the condition table. If at least one condition record exists and it would not result in an overlap with condition records that already have active packaging specifications. then the condition records refer to the packaging specification number (regardless of the version). see the CA documentation for message control.

SAP Online Help

20.07.2007

SAP Extended Warehouse Management (SAP EWM)

510

501

SAP Online Help

20.07.2007

Distribution of Packaging Specifications
Use
If you want to use packaging specifications in multiple SCM systems, you must distribute these packaging specifications to the other systems so that you are able to work with the same master data in all systems.

Prerequisites
You have distributed the products and locations in all systems involved.

Features
You can distribute the packaging specifications to different SCM systems by qRFC.

Activities
...

1. In the distributing system, set up an RFC ABAP connection to them target system. To do this, on the SAP Easy Access screen choose Tools → ALE → ALE Administration → Runtime Settings → Maintain RFC Destinations (see also: Setting the RFC Destination [Extern]). 2. In the distributing system, register a logical destination for the RFC ABAP connection in the qRFC Monitor [Extern]. a. To do this, on the SAP Easy Access screen choose Advanced Planning and Optimization → APO Administration → Integration → Monitor → QRFC Monitor (Outbound Queues). b. Enter the client and choose Execute. c. Choose Goto → QOUT – Scheduler. d. Choose Edit → Registration. e. Enter the RFC ABAP connection in the Destination field and copy the other proposed values. 3. In the distributing system, enter the RFC ABAP connection in Customizing for distributing the packaging specification. For more information, see the Implementation Guide (IMG) for SCM Basis under Packing → Packaging Specification → Define RFC Connection for Packaging Specification Distribution. 4. In the distributing system, set the distribution indicator for the packaging specification groups for which you want to distribute packaging specifications to Source System. For more information, see the Implementation Guide (IMG) for SCM Basis under Packing → Packaging Specification → Define Group for Packaging Specifications. 5. In the target system, set the distribution indicator for the packaging specification groups for which you want to receive packaging specifications from other SCM systems to Target System. For more information, see the Implementation Guide (IMG) for SCM Basis under Packing → Packaging Specification → Define Group for Packaging Specifications. 6. If you do not want to work with only the distributed packaging specification in the target system, rather also with packaging specifications that you create in the target system,

SAP Extended Warehouse Management (SAP EWM)

510

502

SAP Online Help

20.07.2007

then you have to configure disjunctive number ranges to the number ranges in the source system in Customizing for the target system. The packaging specifications in the target system then receive different numbers and therefore cannot cause any conflicts with the distributed (or about to be distributed) packaging specifications. a. In the target system, create disjunctive number ranges for packaging specifications, work steps and element groups. For more information, see the Implementation Guide (IMG) for SCM Basis under Packing → Packaging Specification → Define Number Range for Packaging Specification. b. Enter the new number ranges for work steps and element groups. For more information, see the Implementation Guide (IMG) for SCM Basis under Packing → Packaging Specification → Define General Packaging Specification Parameters. c. Create a new packaging specification group, assign the new number range for packaging specifications to this packaging specification group, and set the distribution indicator to Local. For more information, see the Implementation Guide (IMG) for SCM Basis under Packing → Packaging Specification → Define Group for Packaging Specifications.

SAP Extended Warehouse Management (SAP EWM)

510

503

SAP Online Help

20.07.2007

Unique Identification of Handling Units
Use
Since a handling unit is a physical unit consisting of packaging materials (load carriers/packing material) and the goods contained on/in it, each handling unit must be uniquely identifiable. You can do this by assigning an identification number. Within a client, this uniqueness can be ensured using a number range object. Across systems, unique identification is only possible by assigning a SSCC18 [Seite 505] .

Prerequisites
Ensure that you have made the following Customizing settings: 1. To configure the type of number assignment, choose the IMG activity Assign Number Range Intervals to Packaging Material Types. 2. To configure number assignment of the HU identification using a number range interval, choose the IMG activity Maintain Number Range Intervals for HU Identification. 3. If you want to ensure unique identification across systems, choose the IMG activities in the section SSCC Number Assignment According to EAN128. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings → Handling Units → External Identification.

Example
If you want to edit or display a handling unit, you can only select the HU if this identification exists only once. If you permit multiple assignment of the same handling unit identification, then the system cannot find the handling unit you require, which means, for example, that scanner-supported processing is not possible.

SAP Extended Warehouse Management (SAP EWM)

510

504

SAP Online Help

20.07.2007

SSCC Number Assignment According to EAN128
Use
Because of global networking between manufacturers, transportation service providers, dealers, and consumers, communication between the instances involved in the supply chain is becoming more important. The basis of efficient processing is a common numbering standard, which is defined by international standardization organizations (UCC, EAN International). The UCC/EAN128 and one of its subcomponents, the Serialized Shipping Container Code (SSCC)/Number of the Shipping Unit (NSU), is defined as a part of these standards, and can be used to identify the handling units transported. This means that within the supply chain, the UCC/EAN128 and the SSCC can be used to transmit data about the handling unit from instance to instance, for example, via EDI with EDIFACT or EANCOM standards. You can uniquely assign SSCCs when you create handling units. SSCCs are used to identify and track handling units. You can collate the SSCC and other parts of the UCC/EAN128 into a valid bar code chain, or extract them from a bar code chain. The system generates the SSCC using a separate number range object.

Integration
EAN128 numbering is integrated into the packing functions.

Prerequisites
Before you can work with the EAN128 functions, you must request the basic number ILN2 (ILN = international location number) from either the UCC or EAN International.

Features
When constructing handling units, you can use the packaging material to control that the system automatically assigns an SSCC/NSU. The number range used for this is determined by the system using the warehouse number. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings → Handling Units → External Identification → SSCC Number Assignment According to EAN128 → Maintain SSCC Generation for Each Warehouse Number. You can also assign the SSCC/NSU can be assigned externally, and can be checked against an external number range, which the system finds using the same logic. At the same levels, you can enter the basis number for ILN2 that you require to generate the SSCC.

SAP Extended Warehouse Management (SAP EWM)

510

505

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

506

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 507

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

508

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

509

SAP Online Help

20.07.2007

Automatic Packing in the Inbound Delivery
Purpose
Your vendor sends you inbound deliveries that do not contain any packing information about handling units. You can specify that the system automatically packs any unpacked delivery items. The packed goods can then be included in process-oriented storage control [Seite 334].

Prerequisites
● ● You have created and activated a packaging specification [Seite 494] (see also: Creation of Packaging Specifications [Seite 497]). Determination for the packaging specification is configured for your business characteristics (for example, vendor and product). (see also: Packaging Specification Determination [Seite 499]) You have configured the determination procedure for automatic packing in Customizing. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Receipt Process → Inbound Delivery → Define WM-Specific Settings for Document Types.

If you have set the No Automatic Packing indicator in Customizing for EWM under Inbound Delivery → Manual Settings → Define Document Types for Inbound Delivery Process, the system does not perform automatic packing when it creates an inbound delivery. It does not perform automatic packing either if you configure a determination procedure for automatic packing.

Process
...

1. An inbound delivery notification arrives in EWM via the ERP interface. 2. When you activate the inbound delivery notification, the system simultaneously creates the handling units (HU), where the vendor has sent you the HU data. Moreover, at this time, the system calls packaging specification determination for the unpacked items, using the determination procedure you have defined. 3. If the system finds a packaging specification, it creates handling units according to the packaging specification. When creating packaging specifications, you should ensure that the HU Check function does not display any errors in the log. The system can only perform automatic packing successfully if the packaging specification contains all HUrelevant data (in particular, packaging material, target quantity, and product).

SAP Extended Warehouse Management (SAP EWM)

510

510

SAP Online Help

20.07.2007

Packing During Warehouse Task Confirmation.
Purpose
Packing during warehouse task confirmation offers you a transaction that supports you during warehouse task confirmation, in processes that use printed documents. During picking, you can assign product warehouse tasks and handling unit warehouse tasks to pick-handling units. You can divide a product warehouse task between several pick-handling units. The system can assign the pick-handling unit identification, or you can do this manually.

Process
...

1. Create a new entry for the pick-handling unit in the system. 2. Enter a default packaging material. 3. If required, enter a handling unit identification. 4. Create a handling unit. 5. During confirmation of the warehouse task, assign the pick-handling unit as the destination handling unit.

Results
The product or handling unit is included in the pick-handling unit.

Examples
A warehouse order contains 20 product warehouse tasks, and 4 pick-handling units proposed by the system. The picker identifies 4 boxes as pick-handling units. The picker performs picking and notes down the pick-handling unit into which he or she places each product. When you enter data in the foreground, you assign the proposed pick-handling units to the appropriate warehouse tasks during confirmation (for more information, see the input help).

SAP Extended Warehouse Management (SAP EWM)

510

511

SAP Online Help

20.07.2007

Deconsolidation Using Radio Frequency
Use
You are able to execute deconsolidation using a Radio Frequency (RF) presentation device.

Prerequisites
You are logged on [Seite 790] to the RF environment.

Features
● Logging on to a work center For most of the transactions within the main menu for deconsolidation you need to log on to a certain work center to get proposals for several input fields. ● Creating multiple handling units (HUs) The creation of multiple empty putaway HUs can be used as preparation for deconsolidation. ● Creating a single HU The creation of a single empty putaway HU can be used as preparation for deconsolidation. ● Deconsolidating HUs Deconsolidation is the repacking/sorting of items from the deconsolidation HU into several putaway HUs. Repacking is based on transfer order (TO) confirmation. After the TOs have been confirmed, a new TO is created that is then used for putaway. Sorting occurs by the consolidation group which is copied from the activity area of the final putaway bin to the product TO. ● Deconsolidating HUs manually Deconsolidation can also take place without you logging on to a work center. In this case, the system does not propose a putaway HU. Instead, you have to enter the putaway HU manually. The system still checks if the destination HU is valid for the selected TO. ● HU overview The HU overview screen provides an overview of the deconsolidation HU that you want to deconsolidate, for example, the number of open TOs, weight, and volume. ● Creating a single HU manually You can create a putaway HU without logging on to a work center. In this case, the system does not propose a packaging material or a bin. The creation of a single empty putaway HU can be used as preparation for deconsolidation. ● Changing HUs In this RF transaction, you can close a putaway HU, delete an empty HU, convert a deconsolidation HU into a putaway HU, and condense a deconsolidation HU. Whenever a putaway HU becomes full, you have to close the HU in order for it to be ready for the next process step such as putaway. If you have created a HU in the system that you no longer need, you can delete it. To deconsolidate nested HUs, you have to condense them first.

SAP Extended Warehouse Management (SAP EWM)

510

512

SAP Online Help

20.07.2007

Packing using Radio Frequency
Use
You are able to execute packing using a Radio Frequency (RF) presentation device.

Prerequisites
You are logged on [Seite 790] to the RF environment.

Features
● Logging on to a work center For most of the transactions within the main menu for packing, you need to log on to a certain work center. Especially if you work with the function ‘Repacking HUs automatically’ or the function ‘Repacking HU items automatically’, the system will consider all HUs located at the work center to propose destination HUs. ● ● Creating a single handling unit (HU) The creation of a single empty HU can be used as preparation for packing. Repacking HUs automatically Packing HUs means consolidating several pick HUs into a destination HU. The system proposes the destination-HU based on the consolidation group for a scanned pick HU. If all repacked HUs contain the same consolidation group, the destination HU is also assigned to that consolidation group. ● Repacking HU items automatically Packing HU items means deconsolidating several pick HU items into destination HUs. The system proposes the destination HU based on the consolidation group of the pick TO that belongs to the scanned HU item. If all repacked HU items contain the same consolidation group, the destination HU is also assigned to that consolidation group. ● Creating a single HU manually You can also create a new HU without logging on to a work center. In this case, the system does not propose a packaging material or a bin. The creation of a single empty HU can be used as preparation for repacking HU items or HUs. ● Repacking HUs manually You can also repack HUs without logging on to a work center. In this case, the system does not propose a destination HU. Instead, you have to enter the destination HU manually. The system still validates the consolidation group of the destination HU against the consolidation group of the pick HU. ● Repacking HU items manually You can also repack HU items without logging on to a work center. In this case, the system does not propose a destination HU. Instead, the user scans the destination HU. The system still validates that the consolidation group of the HU item matches the one of the destination HU ● HU maintenance You can use HU maintenance to check and/or change the weight and volume of a HU, for example.

SAP Extended Warehouse Management (SAP EWM)

510

513

SAP Online Help

20.07.2007

Printing Handling Unit Documents
Use
Extended Warehouse Management (EWM) can use this function to automatically print lists or labels according to your Customizing settings, when you work with handling units (HUs). The documents can contain information about the contents, destination, owner, and data necessary for further processing of the handling unit. You can use this function in the warehouse management monitor on the user interface for handling units to manually perform or repeat printing for a handling unit.

Integration
● ● ● Printing of handling unit documents 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 the condition technique in the schedule condition for the PPF to determine the printer, the form type, and the spool parameters.

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 Customizing settings for the 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 aggregation

You have defined the PPF conditions for the defined PPF action definitions. You have made the Customizing settings for the condition technique. ○ You have defined condition tables. 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.

SAP Extended Warehouse Management (SAP EWM)

510

514

SAP Online Help

20.07.2007

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 your condition types to the relevant condition schemas. 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 is to 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. You need the condition maintenance group to create 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 handling unit documents, the following action definitions are supported in the PPF in the application /SCWM/WME in the action profile /SCWM/HU. You have created these action definitions for each form type. This enables you to simultaneously print several different documents, for example, printing an HU content note and printing HU labels. An SAP Smart Form is available for each action definition. The system only supports printing of Smart Forms. The following table gives you an overview of the action definitions and their corresponding Smart Form forms. You specify the assignment between action definition and Smart Form form in the created condition records. Action Definition HU_CONTENT HU_EXPRESS HU_HAZARD HU_LABEL HU_SHPLABEL HU_TO HU_SERIAL Print hazardous goods label Print HU label Print shipping label Print HU warehouse tasks Print HU serial number label Description Print HU contents document with serial numbers Smart Form /SCWM/HU_CONTENT /SCWM/HU_EXPRESS /SCWM/HU_HAZARD /SCWM/HU_LABEL /SCWM/HU_SHPLABEL /SCWM/HU_TO /SCWM/HU_SERIAL

When you save handling units or confirm a warehouse task, the system calls the PPF and starts an attempt to print. The decision whether to print is dependent on the condition records that are found in the schedule condition. If there is a condition record in which the PPF action definition matches the current PPF action definition, the PPF triggers the executing method and printing. This only happens if the logical condition is fulfilled, if one is entered in the condition record. In the work center, you can also trigger this manually using a pushbutton. During printing or repeat printing, you can also execute PPF action definitions for which no condition records were created. However, since this means that the necessary data such as

SAP Extended Warehouse Management (SAP EWM)

510

515

SAP Online Help

20.07.2007

printer, form name, and spool parameters cannot be determined, you must enter this data manually. During printing, both the application and the PPF write data into tables. You must reorganize these tables manually. To do this, use report /SCWM/R_REORG_HU_WO_PRINT. During printing, the PPF writes a determination log and a processing log. You can switch these logs on and off, since they can become large. To do this, use parameter /SCWM/HU_PRT_PROT, where 'X' means that the system writes the log.

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 that you have defined in Customizing for the PPF application /SCWM/WME and the PPF action profile /SCWM/HU. 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 Smart Form form. The system reads the current application data. The system determines the function module that corresponds to the Smart Form form, and calls this function module using the application data. PPF saves the action that was executed and the logs that were written.

SAP Extended Warehouse Management (SAP EWM)

510

516

SAP Online Help

20.07.2007

Stock Identification
Definition
Unique number that you use to identify stock (that is, a product) with all its stock attributes, such as quantity, batch, or stock type.

Use
When you perform goods movements in your warehouse, Extended Warehouse Management (EWM) creates a new warehouse task (WT) with a unique warehouse task number (WT number) for every goods movement. If you have chosen the default value A (Stock Identification only if Externally Predetermined) or B (Create Stock Identification if None Exists) in your Customizing settings, EWM simultaneously copies or creates the stock identification in every product WT. You can use the stock identification to choose the corresponding product with its quantity in the various user interfaces. In contrast to the WT number, the stock identification remains unchanged even if you move the respective stock in the warehouse repeatedly. In this way, you can clearly identify stock during the goods receipt and goods issue processes. When you confirm the respective WT, EWM saves the stock identification in the target stock.

Structure
The stock identification does not use a separate number range, rather it consists of a 16 digit number. The first four digits represent the warehouse number. The other 12 digits represent the WT number. The following figure shows this.
Warehouse Number CFG1 WT Number 000000000159

CFG1000000000159 Stock Identification

You can use the Business Add-In (BAdI) /SCWM/EX_CORE_CR_STOCK_ID BAdI:Number Assignment Stock Identification to create your own numbering for stock identification. For more information, see the Implementation Guide (IMG) of Extended Warehouse Management under Business Add-Ins (BAdIs) for Extended Warehouse Management → Cross-Process Settings → Warehouse Task → BAdI: Number Assignment Stock Identification

SAP Extended Warehouse Management (SAP EWM)

510

517

SAP Online Help

20.07.2007

Stock Identification in the GR and GI Processes
Purpose
The aim of stock identification [Seite 517] is to uniquely identify a stock, that is, a product, with all its stock attributes, such as quantity, batch, or stock type. For example, you receive an inbound delivery with a mixed handling unit (mixed HU). In this case, the HU number is not sufficient for a unique stock identification. When Extended Warehouse Management (EWM) creates warehouse tasks (WTs), it can simultaneously create corresponding stock identifications.

Prerequisites
● In the Customizing settings for the warehouse process type, you have chosen the stock identification and there you have chosen the default value A (Stock Identification Only if Externally Predetermined) or B (Create Stock Identification if None Exists). For more information, see the Implementation Guide (IMG) for Extended Warehouse Management → Cross-Process Settings → Warehouse Task → Define Warehouse Process Type. You have carried out the prerequisites for Using Stock Identification [Seite 521].

Process
The following figure provides an overview of the use of stock identification in the goods receipt and goods issue processes (GR and GI processes) in a stock transfer between two warehouses.
Warehouse SPU1
Outbound Delivery for SPU1 GI Zone GI20
SID1 SID2 SID3 HU2 SID1 SID2 SID3 HU2

Packing Station WS20

Final Storage Bins JK01, JK02, JK03
SID1 SID2 SID3 HU1

SID1 SID2 SID3 HU2

SID1 SID2 SID3 HU1

Warehouse SPU2

Deconsolidiation Station DS10 GR Zone GR10
SID1 SID3 SID1 SID2 SID3 HU2 HU3

Final Storage Bins JK01, JK02, JK03

SID1 SID2 SID3 HU2

SID1 SID2 SID3 HU2

SID2

HU4

Inbound Delivery for SPU2

Inactive Product Warehouse Task Active Product Warehouse Task Handling Unit Warehouse Task

...

SAP Extended Warehouse Management (SAP EWM)

510

518

SAP Online Help

20.07.2007

In this process flow description, the names of the storage bins, the HUs, and so on, serve to provide a better understanding of the above figure. They are, however, merely examples. 1. EWM has created an outbound delivery and the corresponding active product WTs in warehouse SPU1. 2. You pick stock for the outbound delivery from the storage bins JK01, JK02, and JK03, pack it into HU1, and confirm the active product WTs. When you are picking, you can, if necessary, split the product WTs (see also Stock Identification When Splitting Warehouse Tasks [Seite 523]). 3. EWM creates an active HU WT so that you can transport HU1 to a packing station. You repack the contents of HU1 into HU2 for the outbound delivery. EWM creates corresponding product WTs that are confirmed immediately for repacking. You can use the stock identification to uniquely select the contents of HU1 that you want to repack. When you are repacking HUs, you can, if necessary, split the stock (see also Stock Identification When Splitting Stock in the GI Process [Seite 526]. 4. You transport HU2 from pack station WS20 to GI zone WA20. EWM correspondingly creates an active HU WT for this shipment that you then confirm. 5. You load HU2 on to the truck and transport it from warehouse SPU1 to warehouse SPU2. EWM creates an active HU WT for loading that you then confirm. 6. You receive the inbound delivery containing HU2 in warehouse SPU2. You unload the truck and transport HU2 to GR zone GR10. EWM creates an inbound delivery and the respective active HU WT that you then confirm. EWM creates different WTs for the GR and GI processes, for example, a putaway WT WTNo.10001 and a pick-WT WTNo.2002. However, EWM creates putaway WTs on the basis of the stock identification of the supplying warehouse, meaning that the stock identification does not change. You do not need to relabel. You can work with the putaway WT as well as selecting the corresponding putaway WT via the stock identification to confirm it in a putaway process. (See also Using Stock Identification [Seite 521]).

If you put two different stocks of the same product away, EWM transfers the unique stock identification, in other words each stock has a separate stock identification. You do not have to print new labels. A prerequisite for this is that (in your Customizing settings), you have chosen the default value A (Stock Identification Only if Externally Predetermined) or B (Create Stock Identification if None Exists). You transport HU2 from the GR zone to deconsolidation station [Seite 298] DS10. EWM correspondingly creates an active HU WT for the shipment that you then confirm. You deconsolidate the contents of HU2 into two new HUs (HU3 and HU4) on the basis of the consolidation group [Extern]. If necessary, you carry out a WT split. Using the stock identification, you choose the corresponding inactive product WT and confirm the product in a possible destination HU. 7. EWM creates corresponding active product WTs while closing the destination HU. 8. You transport HU3 and HU4 from the deconsolidation station to the respective final storage bin, in other words, the storage type has the Stor.Ctrl/Put.Compl. indicator, and you confirm the corresponding active product WTs. Here, EWM deletes the stock identification. When you start a new GI process, EWM creates new unique stock identifications.

If you have already picked stock, it might be that you cannot yet post the GI, for example, because the truck has not arrived yet. If you want to put your stock away first, you can carry this out using an ad-hoc WT [Seite 415]. EWM does not delete the stock identification from the stock, although EWM has set the indicator for the final storage type. This means that EWM checks whether the stock has another connection to an outbound delivery before the

SAP Extended Warehouse Management (SAP EWM)

510

519

SAP Online Help

20.07.2007

stock identification is deleted. If there is a connection, EWM does not delete the stock identification yet.

Results
You have carried out a GI process and a GR process (stock transfer between two warehouses) with stock identification.

SAP Extended Warehouse Management (SAP EWM)

510

520

SAP Online Help

20.07.2007

Usage of Stock Identification
Use
Instead of working with warehouse tasks (WTs) at various work centers in the warehouse, you can work with stock identification [Seite 517]. Extended Warehouse Management (EWM) finds the WT or stock that corresponds to the stock identification.

Prerequisites
● ● You have carried out the prerequisites for Stock Identification in the GR and GI Processes [Seite 518]apurl_link_0003_0002_0004. You have set up stock identification. You have set the SI Control indicator. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management → Cross-Process Settings → Warehouse Task → Define Warehouse Process Type. ● You have set the Delete Stock Identification indicator for final storage types. For more information, see the IMG for Extended Warehouse Management (EWM) under Master Data → Define Storage Type. ● If you want to print labels, you have carried out the Customizing for Printing Warehouse Tasks [Seite 426].

Features
● When you confirm WTs, you can select them using the stock identification. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Confirm Warehouse Task. ● When you are deconsolidate a handling unit (HU) in goods receipt, you can select the WTs that are to be confirmed using the stock identification. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Deconsolidation in Goods Receipt. Specify the organizational data Warehouse Number and Work Center and choose Execute. Scan the source HU and specify the stock identification in the Prd, SI, WT, HU field on the Deconsolidate tab page. EWM finds the corresponding product WT using the stock identification. EWM displays either a possible destination HU in the product WT, or you specify a possible destination HU. You confirm the product WT with the possible destination HU. ● If you want to repack stock, you can select it using the stock identification. EWM creates immediately confirmed WTs. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Packing - General. Specify the organizational data Warehouse Number and Work Center and choose Execute. Scan the source HU and the stock identification of the products, that is, the labels located within the HU. Go to the Repack Product tab page. EWM uses the stock identification to find the corresponding stock, in other words, EWM displays the corresponding quantity. EWM proposes a possible destination HU or a packaging material. If you choose Execute, EWM creates an immediately confirmed product WT containing the proposed destination HU as a destination storage bin. ● If you want to count stock, you can select it using the stock identification. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Quality Inspection and Count. Specify the organizational

SAP Extended Warehouse Management (SAP EWM)

510

521

If you want to enter quality inspection results. you can use stock identification for the following process steps: ○ ○ ○ ○ Deconsolidation Packing Counting Putaway To do so. Enter the count results on the Counting tab page. choose 05 Internal Processes → 04 Quality Management → 04 QM Counting → 03 QM Counting Results manually For putaway. choose Extended Warehouse Management → Monitoring → Warehouse Management Monitor. the labels located within the HU. If you want to enter count results. on the SAP Easy Acces Screen. such as findings or decisions. On this screen. choose 03 Goods Receipt Processes → 02 Deconsolidation → 04 Deconsolidate Automatically or 05 Deconsolidate Manually For packing. such as product name or quantity. When you log on to the RF environment. EWM uses the stock identifications to find the corresponding stock and displays the respective stock attributes. For example. you can search for WTs for the stock identification and for stocks for the stock identification. that is. Scan the stock identification of the products. Specify a stock identification in the Stock Identification field in the Warehouse Task screen area. SAP Extended Warehouse Management (SAP EWM) 510 522 . choose Documents → Warehouse Task in the navigation tree. choose the stock using the stock identification. In the warehouse management monitor. choose 03 Goods Receipt Processes → 03 Putaway → 01 Putaway by HU. we recommend that you create a userdefined index (Z index) for both the table for open warehouse tasks (/SCWM/ORDIM_O) and the table for stock (/SCWM/QUAN).07. choose 04 Goods Issue Process → 02 Packing → 04 Repack HU Item Automatically or 07 Repack HU Item Manually During counting. choose Extended Warehouse Management → Execution → /SCWM/RFUI . 03 Putaway by Warehouse Order or 04 Confirmation Correction ○ ○ ○ See Also: Work Processing Using Radio Frequency [Seite 797]. If you work with stock identification. ● In user interfaces that support radio frequency. ○ For deconsolidation. on the SAP Easy Access screen.SAP Online Help 20. 02 Putaway by HU (Clustered).Log On to RF Environment.2007 data Warehouse Number and Work Center and choose Execute. you can work with stock identification in the following logical transactions only. This allows EWM to carry out faster search queries. Go to the Stock Details tab page. choose the stock using the stock identification. Go to the Q-Inspection tab page and enter the inspection results.

You only confirm six pieces in the WT. for example WT 1001/001. a. 1001 / 002 … Product XYZ 4 Pieces Stock ID ANDI 1001 1. WT No. This means that the two different stocks have two separate stock identifications to ensure unique stock identification. 2.07. Process When you confirm a WT with a partial quantity. You have packed stock into a handling unit (HU). HU1. for example. b. You print new labels for both stock identifications and apply them. SAP Extended Warehouse Management (SAP EWM) Stock ID: 1001 Label 510 523 . . only six pieces fit into HU1 instead of the required ten. Here. 1001 / 001 … Product XYZ 6 Pieces Stock ID ANDI 9898 . a WT split occurs. You can print labels showing the new stock identifications. 1001 … Product XYZ 10 Pieces Stock ID ANDI Label Stock ID: WT No. EWM splits the WT and creates a new WT (such as 1001/002) with four pieces for the remaining quantity. WT No. EWM only retains the same stock identification as in the original WT for the WT that was confirmed last.. c.SAP Online Help 20. Extended Warehouse Management (EWM) creates WTs with new stock identifications. 3.2007 Stock Identification When Splitting Warehouse Tasks Purpose You can also use stock identification [Seite 517] for putaway when splitting stock for in the goods receipt process when splitting stock (GR process) and in the goods issue process (GI process). You only confirm part of the stock in the corresponding WT. For example. EWM assigns a new stock identification (such as AND198898) to the confirmed WT. Prerequisites See Stock Identification in the GR and GI Processes [Seite 518] and Using Stock Identification [Seite 521]. 4. You confirm WT 1001/002. The following figure provides an overview of the use of stock identification when splitting a WT in the GR and GI processes. Depending on your Customizing settings.. EWM assigns a new stock identification to the split quantity.

2007 Stock Identification When Splitting Stock in the GR Process Purpose You can also use stock identification [Seite 517] when splitting stock in the GR process. 3. When you confirm the putaway WT during deconsolidation for example. you use the stock identification to search for the unconfirmed putaway WTs for a stock. EWM creates the required putaway WTs in accordance with the putaway strategy. for example. You choose one WT and confirm it. you use the stock identification ANDI1001 to search for the corresponding putaway WTs. for example.SAP Online Help 20. Process The following figure provides an overview of the use of stock identification when splitting stock in the GR process. If you have not done so already. the contents of which has one stock identification. such as SPU24711 and SPU24712. You want to put this HU away and you determine that this requires two destination storage bins. 4712 … Product XYZ 4 Pieces Stock ID ANDI 1001 Target Stock ID SPU24712 1. you can still specify or scan the stock identification ANDI1001 that was printed on the original label.. EWM displays the putaway WTs 4711 and 4712 as the result. 4711 … Product XYZ 6 Pieces Stock ID ANDI 1001 Target Stock ID SPU24711 . Prerequisites See Stock Identification in the GR and GI Processes [Seite 518] and Using Stock Identification [Seite 521]. … Product XYZ 10 Pieces Stock ID ANDI 1001 WT No. EWM then displays the options WT 4711 and WT 4712. For example. EWM then transfers the target stock identification to the stock. you receive a handling unit (HU) from a supplier. 4. If you want to search for putaway WTs for a stock. putaway WT 4711 with six pieces and putaway WT 4712 with four pieces. For example. both of them receive the available stock identification. the stock identification ANDI1001 and a new target stock identification each.. 2. you receive an HU1 with ten pieces. For example. You receive an inbound delivery with an HU. Extended Warehouse Management (EWM) creates new putaway warehouse tasks (putaway WTs) with new stock identifications. SAP Extended Warehouse Management (SAP EWM) 510 524 .07. you must now print new labels with the new stock identifications and apply them. open putaway WTs. If you do not confirm the putaway WTs immediately. Here. EWM then displays all the corresponding. WT No.

2007 SAP Extended Warehouse Management (SAP EWM) 510 525 .07.SAP Online Help 20.

9898I WT No. You can carry out the stock split during repacking. 5. If. 2002 … Product XYZ 4 Pieces Stock ID ANDI .07. … Product XYZ 10 Pieces Stock ID ANDI Label Stock ID: WT No. The following figure provides an overview of the use of stock identification when splitting stock in the GI process. 3. while you are repacking products you realize that instead of being able to pack ten pieces of a product in an HU (HU1. EWM also creates an immediately confirmed WT (3003. for example) with the partial quantity of four pieces.2007 Stock Identification When Splitting Stock in the GI Process Purpose You can also use stock identification [Seite 517] when splitting stock for packing in the goods issue process (GI process). Process The process flow for using stock identification corresponds with the process flow for splitting WTs. EWM creates an immediately confirmed WT (2002. 4. that EWM creates a new stock identification for every stock that is split (see also Stock Identification When Splitting Warehouse Tasks [Seite 523].) EWM only assigns the same stock identification as in the stock to the WT that was created last and confirmed immediately. for example) with a new stock identification (AND19898. 3003 … Product XYZ 6 Pieces Stock ID ANDI Stock ID: 1001 Label 1001 1. This ensures unique stock identification. SAP Extended Warehouse Management (SAP EWM) 510 526 . for example) with the remaining quantity of six pieces with the original stock identification (ANDI1001. For repacking. For repacking. you must carry out a stock split. Prerequisites See Stock Identification in the GR and GI Processes [Seite 518] and Using Stock Identification [Seite 521]... Here. in other words. You print new labels for both stock identifications and apply them. 2. You reduce the default quantity from ten pieces to four pieces. Extended Warehouse Management (EWM) creates new warehouse tasks (WTs) with new stock identifications. You can print labels showing the new stock identifications. for example) you are only able to pack four pieces for example.SAP Online Help 20. thereby repacking with WTs that have been confirmed immediately. for example).

and to document them. the VAS order defines which product processing must be performed by warehouse employees in the work centers. In these interim steps.. Features You have created an inbound or outbound delivery.. In an ideal case. or kitting [Extern]. You can also use a VAS order in the goods issue process to assemble kits for your customers. and a valid packaging specification that you can assign to the VAS order also exists. You can use the VAS order to perform the following functions: Value-added services in the goods receipt process [Seite 530] Value-added services in the goods issue process [Seite 533] . and to pack them on a customer-specific basis using this VAS order. both the goods receipt process and the goods issue process in the warehouse change. see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings → Value-Added Services (VAS).2007 Value-Added Services (VAS) Purpose You can use a value-added service order (VAS order [Seite 528]) to perform value-added services (VAS) in the warehouse through VAS activities.SAP Online Help 20. Introductory Notes You have made settings in Customizing for Extended Warehouse Management (EWM) for the following IMG activities: ● ● ● ● Define Number Range for VAS Order Activate Order Document Management for VAS Define Relevance for VAS Warehouse-Number-Dependent VAS Settings For more information. Here. Typical VAS activities are assembling products. Integration Value-added services are integrated into EWM and the delivery.07. ● ● ● ● Kitting [Seite 353] as a VAS in goods issue Create VAS order automatically [Seite 231] Create VAS order manually [Seite 536] Process VAS orders [Seite 538] Record consumption of auxiliary products [Seite 542] SAP Extended Warehouse Management (SAP EWM) 510 527 . you can then use process-oriented storage control to execute interim steps before final putaway or before staging in the goods issue area. packing products. for example. labeling.

and with which products. SAP Extended Warehouse Management (SAP EWM) 510 528 . which you want to prepare for final putaway. You can also use VAS orders to log work that is done. The items contain quantity 10 and product Piston. note that you must always create a VAS order on the basis of a delivery with a packaging specification [Seite 494] (see Connection to Value-Added Service Order (VAS Order) [Seite 230]). Here. and box are listed in the auxiliary products.07. The VAS order now looks like this: ● ● ● ● The packaging specification is stored in the order header. A value-added service order (VAS order) links delivery items to a packing instruction and contains details from within the delivery and packaging specification. . You can use the data collected in the VAS order as a calculation basis for billing external and internal service providers. Protect piston from rust 2. yellow paint.. The system finds a packaging specification with the following activities for the product in goods receipt: 1. Structure A VAS order consists of the following levels: ● ● ● ● Order header VAS activities Items Auxiliary products Integration A VAS order is integrated into Extended Warehouse Management and the delivery.SAP Online Help 20. Example You have an inbound delivery with one item for 10 pistons. Use A VAS order is a document with which you can inform warehouse employees about what work they have to perform. The packaging specification uses the packaging specification levels to inform the VAS order about the VAS activities that the warehouse employees have to perform in the warehouse.2007 VAS Order Definition Instruction to perform a value-added service (VAS) for one or more products with reference to a delivery item. and Pack.. The rust protection material. Pack piston in special packaging material (box) for putaway The system creates a VAS order. You use this order to execute the activities listed in the packaging specification for each piston. The VAS activities include the three activities Protect from rust. for example. Paint yellow. Paint piston yellow 3. The delivery tells the VAS order about the exact amount of work to be performed.

2007 The warehouse employees must perform these three VAS activities for all 10 pistons at the respective work centers. SAP Extended Warehouse Management (SAP EWM) 510 529 .SAP Online Help 20.07.

the system determines the corresponding packaging specification. You can define as many interim steps for the products as you require... You are not using process-oriented storage control. You can perform the required VAS activities for a VAS order at special work centers in an interim step.SAP Online Help 20. the system determines the corresponding packaging specification. you must have already configured process-oriented storage control in Customizing for value-added services (see: Process-Oriented Storage Control [Seite 336]). After completing all value-added services. For each inbound delivery item.. Prerequisites An inbound delivery exists. d.. SAP Extended Warehouse Management (SAP EWM) 510 530 . each VAS activity represents a separate process step with a corresponding warehouse task. All of these interim steps are of the type VAS possible. d. c. as does a valid packaging specification. You have only defined the individual process steps. The system then creates product warehouse tasks that contain a work center as the destination storage location in accordance with the VAS order. The system creates a VAS order based on the inbound delivery. and are not using process-oriented storage control: a. ● . You print out the VAS order and the warehouse employees undertake the VAS activities at the work centers manually. the system determines the corresponding packaging specification. Here. After completing all value-added services. If you want to map automatic creation of warehouse tasks as an interim step in the system for the work centers where you are executing value-added services.. The system then creates handling unit warehouse tasks that contain a work center as the destination storage location in accordance with the VAS order. c. the following options are available to you in the goods receipt process for performing value-added services using a VAS order: . c..07. b. and you have not defined any process steps: a. the system puts away the products in the final storage bin. The system creates a VAS order based on the inbound delivery. before you complete the final putaway for the products. meaning that the system can create a VAS order. You can define as many interim steps for the products as you require. For each inbound delivery item. each VAS activity represents a separate process step. ● . The system creates a VAS order based on the inbound delivery. Process Depending on how you use storage control. b. b. Here. ● You are using process-oriented storage control: a. the system puts away the products in the final storage bin.2007 Goods Receipt Process with VAS Order Purpose The goods receipt process [Seite 263] changes when used in connection with value-added services. For each inbound delivery item.

As soon as the VAS activities are completed. and are put away. The following figure shows you a schematic overview of the goods receipt process with VAS order: VAS Using Storage Control Goods receiving area 9002 Truck arrives at warehouse HU warehouse task Final putaway bin VAS work center: Painting VAS work center: Packing Result The products are prepared for putaway following your requirements. you can enter a confirmation in the system. The system maps the packaging specification levels in the VAS order as VAS activities. The system then puts away the products in the final storage bin.2007 d.SAP Online Help 20.07. SAP Extended Warehouse Management (SAP EWM) 510 531 . Example The following figure shows you how the system forms the VAS order from the inbound delivery item and its related packaging specification in the goods receipt process with VAS order.

: Pyramid 3 pc Aux. 3 pc Aux.07. product: Blue paint Activity 2: Work center WC02 VAS item. Specification PS1 Content: Pyramid Level 1: Paint blue Level 2: Pack in case Goods receiving area Work center WC01 Painting VAS Order VO1 Activity 1: Work center WC01 VAS item: Pyramid.2007 VAS in Goods Receipt Truck Inb.SAP Online Help 20. X Item 10: Pyramid 3 pc Pack. product: Case 3 pc Work center WC02 Packing Final storage bin SAP Extended Warehouse Management (SAP EWM) 510 532 . Del.

you must have already configured process-oriented storage control in Customizing for value-added services (see also: Process-Oriented Storage Control [Seite 336]). Prerequisites An outbound delivery exists. for example. each VAS activity represents a separate process step with a corresponding warehouse task. The system then creates product warehouse tasks that contain a work center as the destination storage location in accordance with the VAS order.SAP Online Help 20. as does a valid packaging specification. The system creates a VAS order based on the outbound delivery.. ● You are using process-oriented storage control: a. You can define as many interim steps for the products as you require. The system creates a VAS order based on the outbound delivery. ● . meaning that the system can create a VAS order. and are not using process-oriented storage control: a. In goods issue. For each outbound delivery item. b. The system creates a VAS order based on the outbound delivery.. c. you can also use the VAS order to assemble kits at the work centers (see Kit to Order [Seite 349]).. You have only defined the individual process steps. You are not using process-oriented storage control. The system then creates handling unit warehouse tasks that contain a work center as the destination storage location in accordance with the VAS order. After completing all value-added services. d. the products reach the goods issue area.. All of these interim steps are of the type VAS possible. d. before shipping the products to your customers. You can perform the required VAS activities for a VAS order at special work centers in an interim step. After completing all value-added services. Here.. You can use this process to pack products for your customers on a customer-specific basis.2007 Goods Issue Process with VAS Order Purpose The goods issue process [Seite 314] changes when used in connection with value-added services. the following options are available to you in the goods issue process for performing value-added services using a VAS order: . the products reach the goods issue area. Process Depending on how you use storage control. the system determines the corresponding packaging specification. each VAS activity represents a separate process step with a corresponding warehouse task. Here. the system determines the corresponding packaging specification. b. ● .07. and you have not defined any process steps: a. If you want to map automatic creation of warehouse tasks as an interim step in the system for the work centers where you are executing value-added services. SAP Extended Warehouse Management (SAP EWM) 510 533 . For each outbound delivery item. c. You can define as many interim steps for the products as you require..

you can enter a confirmation in the system. You print out the VAS order and the warehouse employees undertake the VAS activities in the work centers manually. The products then reach the goods issue area. . c. You are using the VAS order for kitting. Example The following figure shows you how the system forms the VAS order from the outbound delivery item and its related packaging specification in the goods issue process with VAS order... As soon as the VAS activities are completed. The following figure shows you a schematic overview of the goods issue process with VAS order: VAS Using Storage Control Staging area Truck leaves warehouse Picking bin HU warehouse task VAS work center: Packing Result The products are prepared for stock removal following your requirements. a. The system creates a VAS order with corresponding kit components based on a packaging specification for the kit header and the kit items in the outbound delivery.07... the system determines the same packaging specification for SAP Extended Warehouse Management (SAP EWM) 510 534 . ● . For each outbound delivery item. .SAP Online Help 20. d..2007 b. You can use the VAS order at the work center provided to assemble the kit components into a kit (see Kitting at a Work Center with VAS Order [Seite 353]). the system determines the corresponding packaging specification... In the following example. ..

The system maps the packaging specification levels in the VAS order as VAS activities. 3 pc VAS aux. The system therefore creates one VAS order only. 3 pc VAS aux.07. VAS in Goods Issue Pick-HUs Outb.2007 the delivery items. PS3 Content: Cycle 1 pc Pump 1 pc Level 1: Gift wrapping Pack. Spec. Spec.: gift wrap paper SAP Extended Warehouse Management (SAP EWM) 510 535 . 3 pc VAS item. prod.: cycle.: pump.:20: Pump 3 pc Pack.: case. prod. Delivery Z Item. PS3 Content: Cycle 1 pc Pump 1 pc Level 1: Gift wrapping Work Center: Customer-Specific Packing Loading VAS Order VO3 Activity 1: Work center CUST VAS item.:10: Cycle 3 pc Item.SAP Online Help 20.

for example. however you notice in the goods receipt area that the products are not packaged.07. The system creates a VAS activity in the VAS order for each level of the packaging specification. Enter the delivery in the Warehouse Request field. If you leave the Packaging Specification field empty. For more information. double-click the level and then choose the Warehouse tab page. Choose VAS Order → Save. Activities . However. you can use this function to create VAS orders [Seite 528] manually. the system attempts to find a suitable packaging specification. Create VAS Order . choose Extended Warehouse Management → Work Scheduling → Value-Added Services (VAS) and either: ○ ○ VAS in Goods Receipt Process VAS in Goods Issue Process 2. 3. your supplier ships products to you packaged. and enter the item in the Item Number field.SAP Online Help 20. if you have restricted the performing entity in the Entity field. A corresponding packaging specification exists (see also: Packaging Specification [Seite 494]). You can also use this function to print out VAS orders again and to delete VAS orders.2007 Create and Edit VAS Orders Use If. the system only writes packaging specification levels as VAS activities into the VAS order that are also provided for this entity. If you notice that a VAS order does not have a work center. you can also use this function to change this data. 2. Integration If you want to implement VAS orders using process-oriented storage control [Seite 336].. you have already specified a determination procedure for packaging specifications in Customizing. choose Goto → Create VAS. see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings → Value-Added Services (VAS) → VAS Integration with Storage Control. 1. Prerequisites An inbound delivery or outbound delivery exists. If you want to create VAS orders.. Enter the warehouse number. To find the Entity in the packaging specification.. If you want to implement automatic packaging specification determination.. SAP Extended Warehouse Management (SAP EWM) 510 536 . on the SAP Easy Access screen. Depending on whether you want to create and manage VAS orders in the goods issue or goods receipt process. for example. see the IMG for Extended Warehouse Management under Cross-Process Settings → Value-Added Services (VAS) → Define Relevance for VAS. 1.

SAP Extended Warehouse Management (SAP EWM) 510 537 . Choose the PPF Actions tab page. 2.. The system deletes the VAS order. Enter either the VAS order number or the delivery number. 2. Here you can use the Post-Processing Framework to print the VAS order or manage other print-specific parameters. Choose Change..07. 1.. You can now change the work center in the VAS order.. Enter either the VAS order number or the delivery number. Enter either the VAS order number or the delivery number. Print VAS Order . 1. Delete VAS Order . 1.2007 Change VAS Order ... or the VAS status. You can also display the packaging specification or the delivery. Choose Delete. 2. for example.SAP Online Help 20.

the system displays all stock that is available in this storage bin. To do this. you can create new kits. The system also displays detailed data about the storage bin. see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Master Data → Work Center → Define Work Center Layout. the stock that also physically exists in the work center is displayed (Stock Section). as well as the following detailed data for the HU: ■ ■ ■ Packaging material Stock in this HU All open warehouse tasks (WTs) for this HU ● ○ SAP Extended Warehouse Management (SAP EWM) 510 538 . For each VAS order. In this section. Prerequisites You have configured a work center where you can process VAS orders. The work center screen is split up into the following sections: ● In the upper left section. In this IMG activity. If you double-click the HU ( ) in the Stock Section. You can also use the same functions as in packing in the work center [Seite 506] for valueadded services (VAS). Features You can display all VAS orders for further processing for each warehouse number and work center. the system displays the weight and dimensions. You can also confirm the work progress of the VAS order (at VAS order header level. VAS item level. see the IMG for Extended Warehouse Management (EWM) under Master Data → Work Center → Define Work Center. you can see all the VAS orders that match your selection criteria (VAS Section). In the bottom right section. You have assigned a work center layout with the transaction type Execute VAS to the work center. you can see the following tab pages. and VAS auxiliary product level).2007 Processing a VAS Order Use You can use this function to document work in progress for a VAS order [Seite 528] in the system and to create kits. and therefore configure which tab pages are displayed on your screen. you have configured transaction type Execute VAS in Customizing. you can see all the VAS activities along with their respective VAS items and VAS auxiliary products. you can also adjust the respective layout of the work center.07. For more information. depending on your selection: ○ If you double-click the storage bin ( ) in the Stock Section. For more information. ● In the upper right section. VAS activity level. for example ( ● ). In the bottom left section. you can use keyboard scanners to pack products into handling units (HUs) and HUs into HUs (see Packing at the Work Center [Seite 506]).SAP Online Help 20.

choose Extended Warehouse Management → Execution → Create Confirmation for VAS. serial numbers for this delivery item. all VAS items.07. the system displays all VAS order header data. and delivery texts. enter a warehouse number and the work center for which you want to enter value-added services using VAS orders. you can also use an additional tab page to display possible destination HUs for repacking.2007 Confirmed WTs with this HU as a source HU If you are working with consolidation groups. Under Organizational Data. ○ ○ Changes in the VAS Section do not automatically affect the Stock Section. for example. and all VAS auxiliary products for this VAS activity. the system displays specific VAS item data. The Filter section allows you to restrict the VAS orders even further. If you double-click the VAS activity ( ) in the VAS Section. Activities On the SAP Easy Access screen. If you double-click the VAS item ( ) in the VAS Section. 2.. dangerous goods texts. On the Serial Number tab page. 1.. ○ If you double-click the stock item ( the following information: ■ ■ ■ ■ ■ All product-specific data Information about serial numbers All open WTs for this item Confirmed WTs for this item Existing dangerous goods texts and delivery texts ) in the Stock Section. and additional data for the VAS order header. all VAS activities. you can enter the serial numbers for the corresponding delivery item. the system does not automatically create an HU when you set the status of the VAS order to Completed. ○ If you double-click the VAS order header ( ) in the VAS Section. the system displays specific data for the VAS auxiliary products. you can also use an additional tab page to display possible destination HUs for repacking. the system displays If you are working with consolidation groups. the system displays VAS activity data. SAP Extended Warehouse Management (SAP EWM) 510 539 . Selection Screen The following work center screen is displayed: Entering Value-Added Services.SAP Online Help ■ 20. . If you do not enter any data here. the system displays all the VAS orders with the status Not being processed. ○ If you double-click the VAS auxiliary product ( ) in the VAS Section. since a VAS item always refers to one delivery item. The system displays all the VAS orders for the work center you have entered that match your selection criteria. For this reason.

if you only confirm the VAS item with 6 pieces or the VAS auxiliary products with 12 pieces as completed. SAP Extended Warehouse Management (SAP EWM) 510 540 . When confirming VAS auxiliary products. 4. The system automatically adjusts the quantities and status for a confirmation as follows: ○ ○ ○ If you confirm using the VAS order header ( ).. it does not automatically adjust the quantities for the VAS activity or VAS order header. For example. The VAS activity has a warehouse request quantity of 5 pieces. you must enter the quantity in the Quantity of an Auxiliary Product to Be Consumed field. enter the quantity that you want to confirm.07. the system automatically adjusts the quantities. Save your entries.SAP Online Help 20. In this case. This enables you to confirm the corresponding quantities according to the level of detail you require in the confirmation process. only data for the VAS orders you selected is displayed. The VAS auxiliary product has a warehouse request quantity of 20 pieces. VAS item. if you have previously entered a greater quantity at VAS item level than now. the system automatically adjusts the quantities of the VAS item and VAS auxiliary products. However. the system automatically sets the status of all previous VAS activities to Completed – Without Quantity Variance. If you confirm the VAS item ( ) or the VAS auxiliary products ( ). In the Completed Quantity field. depending on which level you want to confirm the work progress: ○ ○ ○ ○ VAS order header ( VAS activity ( VAS item ( ) ) ) ) VAS auxiliary product ( 2. Confirm Work Progress for a VAS Activity . You enter confirmation of 3 pieces at VAS activity level. the system does not automatically update the VAS activity. the system automatically adjusts the quantities of the VAS activity. the system saves this quantity without automatically adjusting the other levels. and VAS auxiliary products. If you set the status of the VAS order to Completed – Without Quantity Variance. 3. If you set the status of the VAS activity to Completed – Without Quantity Variance. and 12 pieces as completed quantity for the VAS auxiliary products. You can double-click the following levels. the system automatically sets the status of all VAS activities to Completed – Without Quantity Variance. 1.. If you confirm using the VAS activity ( ).2007 In the Stock Section. ○ If the entered quantity represents a quantity increase. the system only saves these quantities. The VAS item has a warehouse request quantity of 10 pieces. the consumed quantity is displayed in the Consumed Quantity field for the VAS auxiliary product after saving. The system then updates 6 pieces as completed quantity for the VAS item.

. In the Stock Section. 2. Confirm Using a Keyboard Scanner . Save your entries. Save your entries. 4. see Packing at the Work Center [Seite 506]. In the alternative unit of measure field. 1.SAP Online Help 20..2007 Create Kit . 5.07. select the HUs for which you want to create kits.. Choose Create Kit from the application toolbar. 4. 2. Choose the tab page for the level at which you want to confirm (VAS header. The generated kits are displayed below the HU in the tree display when you choose . you can change the number of kits created before saving. VAS activity.. VAS item or VAS auxiliary product). The system checks the components of the HU and uses this to calculate the complete number of kits that can result from them. 3. 1. Scan the VAS order for which you want to perform the confirmation. 3. SAP Extended Warehouse Management (SAP EWM) 510 541 . and creates these kits. The system performs the confirmations using the same logic as described under Confirm Work Progress for a VAS Order. Pack Using a Keyboard Scanner For more information. Enter the completed quantity.

You can also change quantities of auxiliary products that have already been posted. To create a packaging specification. You have assigned a storage bin to a work center or to a warehouse number from where you post the auxiliary products in goods issue. and in what amounts.07. you can also use your own movement types. on the SAP Easy Access screen. You have maintained a packaging specification and have assigned auxiliary packaging materials to the packaging specification levels (such as preservation. on the SAP Easy Access screen. you can also manually overwrite the quantity determined by the system (such as for unplanned overconsumption or underconsumption). choose Extended Warehouse Management → Master Data → Assign Storage Bins for VAS Consumption Posting. Posting reduces the auxiliary product stock in Extended Warehouse Management (EWM) and the stock in the connected ERP system. To do so. the consumption is reduced and the system increases the stock in the storage bin. If you enter a negative value for the quantity of auxiliary product being posted. SAP Extended Warehouse Management (SAP EWM) 510 542 . For more information.SAP Online Help 20. you can increase the consumption at a later time. The standard movement types 291 and 292 are used for consumption posting in the ERP system. Prerequisites You have set the Consumption-relevant for VAS indicator in the storage data of the product master for the products for which you want to record consumption posting. you can record which auxiliary products you used for particular activities. packing into individual containers). choose Extended Warehouse Management → Master Data → Product → Maintain Warehouse Product. and have assigned a special storage bin for the auxiliary products. the system performs consumption posting for the auxiliary products. However. To assign a storage bin. The system uses the following criteria to automatically determine the quantity of respective auxiliary products that is to be posted: ● ● ● The status confirmation for a VAS order The VAS activity confirmation The quantity confirmation for a VAS activity The system determines the respective quantities by using the quantity ratios in the packaging specification of the products being processed. Features If you have set the consumption relevance for the required auxiliary products for value-added services. you can define these in Customizing. However. and this stock is then also consumed by this storage bin as part of the valueadded services. The stock of the auxiliary products is located in this storage bin. see the Implementation Guide (IMG) for Extended Warehouse Management under Interfaces → ERP Integration → Goods Movements → Define Customer-Specific Movement Types. on the SAP Easy Access screen. If you enter a quantity to be posted additionally.2007 Auxiliary Product Consumption Posting Use For the value-added services performed at the work centers. When you save the confirmation. you can record consumption of all auxiliary products in the system. If you want to use customer-specific movement types in the ERP system. choose Extended Warehouse Management → Master Data → Packaging Specification → Maintain Packaging Specification.

SAP Online Help 20.2007 SAP Extended Warehouse Management (SAP EWM) 510 543 .07.

You transport the products or HUs from goods receipt to goods issue without putaway occurring in between. Reducing the time in storage in the warehouse enables you to reduce stockholding costs. see the IMG for EWM under Cross-Process Settings → Warehouse Task → Define Warehouse Process Type. you can also optimize transportation costs. The ERP system sends this delivery pair to Extended Warehouse Management (EWM). we recommend that you define separate warehouse process types in Customizing. for example. see the IMG for EWM under Cross-Process Settings → Cross-Docking (CD) → Basic Settings for Transportation Cross-Docking (TCD) and Basic Settings for PD and Pick From GR. SAP Extended Warehouse Management (SAP EWM) 510 544 . the ERP system generates a corresponding delivery pair. For more information. In the case of Transportation Cross-Docking [Seite 547] (TCD). that is. you define in Customizing how the cross-docking process (CD process) is to proceed. to increase the number of processed HUs and fulfill urgent sales orders. such as searching for CD-relevant inbound deliveries.SAP Online Help 20. In the case of push deployment (PD) and pick from goods receipt (PFGR) [Seite 559]. For more information. Prerequisites ERP system For a description of the prerequisites in the ERP system. For more information. then you can use this process in a distribution center or warehouse. In the case of a TCD. In TCD. The routing guide uses these CD routes to decide whether a TCD process would be advantageous. see the IMG for EWM under Cross-Process Settings → Cross-Docking (CD) → Basic Settings for PD and Pick From GR. meaning you perform unplanned CD. You work with cross-docking routes [Seite 644] (CD routes). you only work with HUs. see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Cross-Docking (CD) → Basic Settings for Transportation Cross-Docking (TCD). see the SAP Help Portal under mySAP ERP → Logistics → Logistics .2007 Cross-Docking (CD) Purpose If you are aiming to process products and handling units (HUs) as efficiently as possible. The CD relevance is therefore defined before stock arrives and before you release the outbound delivery or warehouse task. which executes the TCD process. and to minimize unnecessary load transfer activities in the warehouse.General (LO) → Service Parts Management (LOSPM) → Transportation Cross-Docking. You have defined separate warehouse process types where required.07. Extended Warehouse Management (EWM) Prerequisites for TCD and PD/PFGR: ● ● You have defined the mapping of the document types from the ERP system in EWM. For more information. meaning you perform planned CD. an inbound delivery and an outbound delivery that contain the same TCD operation number. In the case of TCD. If you want to work more quickly with CD-relevant inbound deliveries. or reduce processing and storage costs. Using cross-docking enables you. you start by working with a standard goods receipt process [Seite 263]. You determine the CD relevance after the goods have physically arrived in the warehouse.

. For PD and PFGR. Prerequisites for PD/PFGR: ● You have defined separate document types for the outbound delivery where required. see Updating the Inbound Delivery in the GR Process [Seite 271]. For a detailed process flow description of this overview process. For more information. see the SAP Help Portal under SAP ERP → Logistics → Logistics General (LO) → Service Parts Management (LO-SPM) → Transportation CrossDocking → Push Deployment or Pick From Goods Receipt.2007 You have defined separate document types for the inbound and outbound deliveries where required. ● Process The following gives you an overview describing the simplest CD process without using storage control. The following graphic shows you the simplest instance of cross-docking. You have performed the corresponding Customizing in SAP APO. see TCD. see the IMG for EWM under Cross-Process Settings → CrossDocking (CD) → Basic Settings for Transportation Cross-Docking (TCD) and Basic Settings for PD and Pick From GR. For more information. . You have performed the corresponding Customizing for Route Determination with the Routing Guide [Seite 638]. see Event-Driven Quantity Assignment [Extern]. In this simple case. You receive an inbound delivery. For more information about updating the inbound delivery in cross-docking. 1. Push Deployment and Pick From Goods Receipt. For more information. the ERP system generates a corresponding delivery pair and sends it to EWM. such as the goods issue zone.07. For more information..SAP Online Help Prerequisites for TCD: ● ● 20. If a TCD is required. For more information. 2. When EWM generates a pick-warehouse task. directly in the outbound delivery. EWM specifies the destination storage bins. it determines the destination storage bin from the outbound delivery. EWM receives the CD information from the ERP system. The routing guide uses the route to decide whether a TCD process is required. Here it uses a warehouse task for cross-docking that updates both the inbound and the outbound delivery. see the SAP Help Portal under SAP ERP → Logistics → Logistics . see the IMG for EWM under Cross-Process Settings → Cross-Docking (CD) → Basic Settings for Transportation Cross-Docking (TCD) and Basic Settings for PD and Pick From GR. SAP Extended Warehouse Management (SAP EWM) 510 545 .General (LO) → Service Parts Management (LO-SPM) → Transportation Cross-Docking.

2007 SAP Extended Warehouse Management (SAP EWM) 510 546 .SAP Online Help 20.07.

a sales order in SAP Customer Relationship Management (SAP CRM) forms the basis for TCD. For more information about the complete process for stock transfer orders in the ERP system. a subordinate HU can contain either TCDrelevant delivery items only. In EWM. For more information. to consolidate multiple deliveries to new transports. The monitor only gives you information about the current process status.General (LO) → Service Parts Management (LO-SPM) → Transportation Cross-Docking → Process Flow for Stock Transfer Orders. If you use nested mixed pallets in TCD. In this case. You can deactivate this call for all outbound delivery orders or for outbound ● ● SAP Extended Warehouse Management (SAP EWM) 510 547 . you can use the warehouse management monitor [Seite 878] to display the TCDrelevant inbound deliveries and outbound delivery orders for the warehouse in which you are currently working.General (LO) → Service Parts Management (LO-SPM) → Transportation CrossDocking → Monitor for Transportation Cross-Docking. or non-TCD-relevant delivery items only.General (LO) → Service Parts Management (LO-SPM) → Transportation Cross-Docking. In a supply chain in TCD. For more information about the complete process for sales orders in SAP CRM. see the SAP Help Portal for SAP ERP under SAP ERP Central Component → Logistics → Logistics . As standard procedure. see the SAP Help Portal for SAP ERP under SAP ERP Central Component → Logistics → Logistics . EWM calls SAP Global Trade Services (SAP GTS) in the TCD process for each outbound delivery order or each outbound delivery in the supply chain. the Transportation Cross-Docking Monitor in the ERP system gives you an overview of the complete process that has already run up to that point. see the SAP Help Portal for SAP ERP under SAP ERP Central Component → Logistics → Logistics . You have performed Customizing for Route Determination with the Routing Guide [Seite 638] and defined CD routes [Seite 644].SAP Online Help 20. However. Examples for this are to switch the means of transport. or to process export activities centrally. However.General (LO) → Service Parts Management (LO-SPM) → Transportation Cross-Docking → Process Flow for Sales Orders. a stock transfer order forms the basis for TCD. see the SAP Help Portal for SAP ERP under SAP ERP Central Component → Logistics → Logistics .07. Prerequisites ● You have performed Customizing in the ERP system. Restrictions ● ● ● TCD does not support returns.2007 Transportation Cross-Docking (TCD) Purpose Transportation cross-docking [Extern] (TCD) supports the transportation of handling units (HUs) across different distribution centers or warehouses. Extended Warehouse Management (EWM) uses a stock removal HU-warehouse task (stock removal HU-WT) to update both the corresponding inbound delivery and the corresponding outbound delivery order simultaneously. only the final place of destination can be located abroad. For more information. you can also use TCD to transport HUs to your own final warehouse. up to the final place of destination. If the final place of destination is a distribution center or warehouse at the customer site. When you pick a TCD-relevant HU.

For more information.SAP Online Help 20. The ERP system generates the outbound delivery out of the delivering warehouse from the SAP CRM sales order. which makes settings for Customizing in the delivery.2007 deliveries in Customizing for each document type. see the IMG for EWM under Cross-Process Settings → Warehouse Task → Define Warehouse Process Type. For more information. see the documentation of the BC set. However. see the IMG for EWM under Interfaces → ERP Integration → Delivery Processing → Map Document Types from ERP System to EWM. The check criterion is the existence of a final ship-to party. ● You have defined separate document types and warehouse process types where required. For more information about the warehouse process type. such as searching for TCD-relevant inbound deliveries. For more information. the goods are sent to the customer after posting goods issue from the last CD warehouse.07. meaning EWM only calls SAP GTS for a document type if no final ship-to party has been specified. see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Cross-Docking (CD) → Basic Settings for Transportation Cross-Docking. the process flow in EWM is more or less identical. ● You have defined the mapping of the document types from the ERP system in EWM. You have to deactivate SAP GTS for TCD-relevant document types manually. EWM can use TCD-relevant document types to find TCD-specific warehouse process types. Process The following graphic provides an overview of the process flow in EWM for stock transfer orders in the ERP system. we recommend that you define separate document types and warehouse process types for TCD in Customizing. For more information. SAP Extended Warehouse Management (SAP EWM) 510 548 . We deliver Business Configuration Set (BC Set) /SCWM/DLV_TCD. For sales orders from SAP CRM. If you want to work more quickly with TCD-relevant inbound deliveries. in Customizing. see the IMG for EWM under Goods Receipt Process → Inbound Delivery → Manual Settings → Define Document Types for Inbound Delivery Process and Goods Issue Process → Outbound Delivery → Manual Settings → Define Document Types for Outbound Delivery Process.

SAP Online Help 20.07.2007 SAP Extended Warehouse Management (SAP EWM) 510 549 .

It proposes a corresponding route.07. However. The ERP system generates an inbound and outbound delivery for CD warehouse EWM2. For more information about updating a warehouse request. a. SAP Extended Warehouse Management (SAP EWM) 510 550 . If you have defined only one CD route. such as EWM2. If you attempt to generate an active HU WT for an inbound delivery. The ERP system copies the route for the CD warehouse into the outbound delivery as a proposal. 6. This additional call also ensures that the routing guide can take into account any changed situations. You post goods receipt in CD warehouse EWM2. You or EWM2 generate an active pick-HU WT for the outbound delivery order. You execute your warehouse activities in CD warehouse EWM2. such as picking or posting goods issue. EWM displays a corresponding error message. in delivering warehouse EWM1. such as a date/time change. EWM1 calls the routing guide again via SAP APO. see Creation of Warehouse Tasks for Putaway [Seite 302] or Creation of Warehouse Tasks for Stock Removal [Seite 319] under Activities. 5. so that the transportation in a CD route is more reasonable. it calls the routing guide again via SAP APO. 1. corresponding to the stock transfer order from SAP APO or MM. When EWM2 creates the outbound delivery order. EWM2 creates a related inbound delivery and outbound delivery order for both the ERP inbound delivery and the ERP outbound delivery. and updates the stock transfer order. Here. If the routing guide determines that a CD warehouse lies between these two warehouses. and this route is valid. it informs the ERP system (see Cross-Docking Route [Seite 644]). 8. as for a standard outbound delivery order. The ERP system saves the changed route in the ERP1 outbound delivery if required.SAP Online Help . then the routing guide always uses this CD route. When the ERP system generates the outbound delivery. EWM1 creates a related outbound delivery order. or whether the goods are to be transported directly to the final ship-to party. This checks whether there is another warehouse after the CD warehouse. For a description of TCD with storage control. 3. there are no products that have to be put away. The routing guide determines the route from the delivering warehouse to the receiving warehouse. EWM2 updates the inbound delivery and sends the delivery information and stock information to the ERP system. The routing guide checks whether the outbound delivery is to be transported to a CD warehouse or to the final ship-to party.. Since this is a TCD process. For more information about determining the CD relevance in the ERP system. 4.General (LO) → Service PartsManagement (LOSPM) → Transportation Cross-Docking. it calls the routing guide together with the ATP check via SAP APO. The ERP system generates a related replenishment delivery. see the SAP Help Portal for SAP ERP under SAP ERP Central Component → Logistics → Logistics . 20. see Example Scenario for TCD with Storage Control [Seite 553].2007 The process flow description represents the simplest TCD scenario without using storage control [Seite 334]. You execute your warehouse activities. 10. 9.. 2. 7. EWM1 sends the updated EWM1 outbound delivery to the ERP system. If you have defined multiple CD routes that are valid. EWM2 gets the required data from the corresponding mapping information for the CD-relevant HU. such as whether weight restrictions have been exceeded. SAP Advanced Planning & Optimization (SAP APO) or materials management (MM) generate a stock transfer order in the ERP system. EWM1 takes into consideration the route proposal that has already been determined from the ERP system. the routing guide works with dynamic criteria.

the system determines the destination storage bin. EWM2 sends the updated EWM2 outbound delivery to the ERP system. 11. You have posted goods receipt and goods issue in the respective warehouse. Steps 7 to 10 are then repeated. then the ERP system generates the inbound delivery for receiving warehouse EWM3. EWM updates the plan data and actual data for the status and quantity.07. ● ● ● ● SAP Extended Warehouse Management (SAP EWM) 510 551 . e. You post goods issue in CD warehouse EWM2. it can happen that the CD-relevant HU is located within the nested HU. In EWM3 you post goods receipt and execute your warehouse activities. If you are working with nested HUs. you receive frozen goods and want to store them immediately in a freezer warehouse to preserve the goods. The intermediate storage bin must not be a final storage bin. 14. The CD route went from delivering warehouse EWM1 to receiving warehouse EWM3 via CD warehouse EWM2. EWM2 and EWM3 have all sent the updated data of the inbound and outbound delivery to the ERP system. You load a truck with the HU. 12. SAP APO updates the stock information. such as the staging area in goods issue. If the routing guide does not have any further TCD-relevant steps planned. Otherwise the ERP system generates another inbound and outbound delivery for the next CD warehouse. for example the goods issue area.2007 You use an ad-hoc warehouse task if required to move the HU to another storage bin. EWM1. You confirm the pick-HU WT for the outbound delivery order. In the inbound delivery. When EWM2 generates the pick-HU WT. EWM has updated the status and quantities for putaway for the inbound delivery and for picking for stock removal. EWM3 informs SAP APO about the updated inbound delivery. EWM uses a stock removal HU WT to update both the corresponding inbound delivery and the corresponding outbound delivery order simultaneously in EWM. When you pick a TCD-relevant HU. 13. see HU Integration in Delivery Processing [Seite 136].SAP Online Help 20. Result ● You have performed a TCD process and moved the delivered HU directly from the goods receipt area to the goods issue area. d. The ERP system has generated an inbound and outbound delivery for the CD warehouse. for example. For more information about updating quantities and status in putaway and stock removal. otherwise the TCD process would be finished. see Creation of Warehouse Tasks for Putaway [Seite 302] or Creation of Warehouse Tasks for Stock Removal [Seite 319] under Activities. EWM also updates the plan data and actual data for the status and quantity. For more information about updating quantities in HUs. c. b. In the outbound delivery order. For example. EWM always use the highest-level HU to generate the HU WT. You move the HU to the specified destination storage bin. EWM2 updates the inbound delivery and the outbound delivery order with the picking data.

07.2007 SAP APO has updated its stock information. SAP Extended Warehouse Management (SAP EWM) 510 552 .SAP Online Help ● 20.

you are working with a nested handling unit (HU) and Process-Oriented Storage Control [Seite 336] in this more complex TCD scenario. To do so. unloading and deconsolidating). ● ● Process . You receive an inbound delivery with a nested putaway HU that contains two further products. You defined warehouse processes. you can create the pick HU WT by releasing the wave [Seite 771]. you unpack the TCD HU and the lower putaway HU from the highest-level putaway HU and then pack both of them into a further HU. either you or EWM can create a pick WT for the TCD HU. To do so. choose Storage Process Definition. you can also create the pick HU WT manually. During deconsolidation. SAP Extended Warehouse Management (SAP EWM) 510 553 . You move the TCD HU to the GI zone after deconsolidation. 3. Extended Warehouse Management (EWM) determines that TCD is necessary for an HU (TCD HU) and that the other HU is for putaway (putaway HU). EWM does not create a pick HU WT.2007 Example Scenario for TCD with Storage Control Purpose In contrast to the basic Transportation Cross Docking [Seite 547] scenario (TCD scenario). the current process step must be indicated with the Prod/HU WT indicator. EWM creates the pick HU WT automatically. Select the Auto. If you have set the Prod/HU WT indicator in the Customizing settings for the current process step. WT indicator for automatic follow-up WT creation. see the implementation guide (IMG) for EWM under Cross-Process Settings → Warehouse Task → Define Process-Oriented Storage Control.. This means that you always pick the whole HU in TCD. you have set the Auto. After the GR posting. 1.SAP Online Help 20. Storage Process Definition. You perform the further steps of putaway for the putaway HU. Select the Prod/HU WT indicator. in Customizing for EWM under Cross-Process Settings choose Warehouse Task → Define Process-Oriented Storage Control and in the navigation tree.. Since you are working with nested handling units (HUs) and process-oriented storage control in TCD. and performs the necessary putaway steps for it. 2. Since only packed products are relevant in TCD. WT indicator. Select a definition and choose Assign Storage Process Step in the navigation tree. The highest-level putaway HU correspondingly runs through all steps of the GR process.. Select a definition and choose Assign Storage Process Step in the navigation tree. including Deconsolidation [Seite 298]. EWM processes the individual steps according to the warehouse process. . EWM determines a goods receipt (GR) storage process for the highest-level putaway HU. EWM determines the putaway steps for the highest-level HU first (for example. However. For more information..07. If EWM determines a storage process for process-oriented storage control in goods issue (GI) for this TCD HU after deconsolidation. in Customizing for EWM under Cross-Process Settings choose Warehouse Task → Define Process-Oriented Storage Control and in the navigation tree. If EWM is to create the pick HU warehouse task (pick HU WT) automatically. If the corresponding outbound delivery was assigned to a wave beforehand. Prerequisites ● ● You have carried out the Customizing for Transportation Cross Dockingapurl_link_0004_0004_0006. EWM creates HU warehouse tasks (HU WTs) that move the highest-level HU. If EWM is to create follow-up WTs.

after you have deconsolidated the highest-level HU). EWM activates the pick HU WTs. If the putaway steps of the highest-level HU have been completed (for example.2007 If the putaway steps of the highest-level HU have not yet been completed. EWM creates inactive pick HU WTs. SAP Extended Warehouse Management (SAP EWM) 510 554 .07. see Detailed Process Description [Seite 555].SAP Online Help 20. For a detailed process flow description.

You defined warehouse processes. ● ● Process The following figure provides an overview of the example scenario for TCD with storage control. To do so. in Customizing for EWM under Cross-Process Settings choose Warehouse Task → Define Process-Oriented Storage Control and in the navigation tree. To do so. in Customizing for EWM under Cross-Process Settings choose Warehouse Task → Define Process-Oriented Storage Control and in the navigation tree. choose Storage Process Definition. WT indicator. you have set the Auto. see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings → Warehouse Task → Define Process-Oriented Storage Control. SAP Extended Warehouse Management (SAP EWM) 510 555 . Prerequisites ● ● You have carried out the Customizing for Transportation Cross-Docking [Seite 547]. For more information. Select the Auto. choose Storage Process Definition. If EWM is to create the pick handling unit warehouse task (pick HU WT) automatically.07. the current process step must be indicated with the Prod/HU WT indicator. WT indicator for automatic follow-up